Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document how to use the legacy palette #1439

Merged
merged 1 commit into from
Jun 13, 2019
Merged

Conversation

36degrees
Copy link
Contributor

It’s hard to talk about this option without also talking about compatibility mode, so this also splits the documentation on compatibility mode out from the installation instructions and adds more detail about what it actually does.

There is some duplication between this and the compatibility mode Sass documentation updated in #1438 – it feels like it does need to be explained in both places. Open to ideas on how to reduce that duplication.

Closes #1432

@36degrees 36degrees requested a review from m-green June 7, 2019 13:55
@govuk-design-system-ci govuk-design-system-ci temporarily deployed to govuk-frontend-review-pr-1439 June 7, 2019 13:56 Inactive
@36degrees
Copy link
Contributor Author

@m-green would you have any time to review this? Happy to talk it through in person.

Copy link
Contributor

@NickColley NickColley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Factually this looks great :)

@govuk-design-system-ci govuk-design-system-ci temporarily deployed to govuk-frontend-review-pr-1439 June 10, 2019 15:07 Inactive
@aliuk2012 aliuk2012 added this to the v3.0.0 milestone Jun 11, 2019
@govuk-design-system-ci govuk-design-system-ci temporarily deployed to govuk-frontend-review-pr-1439 June 12, 2019 12:09 Inactive
@m-green
Copy link
Contributor

m-green commented Jun 12, 2019

@36degrees I've rejigged for style and conciseness - let me know what you think. Happy to chat through!

Copy link
Contributor Author

@36degrees 36degrees left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very concise, good stuff 👍

There are a couple of changes I'm not sure are quite right.


## Compatibility mode
GOV.UK Frontend components in your pages will:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not just the components – this would also apply to anything styled using GOV.UK Frontend, for example headings, paragraphs and links.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah good to know, thanks - tweaked in f621496.

- include adjustments to the CSS to 'counter' specific CSS rules in the legacy
frameworks
- use the previous version of the font included with GOV.UK Template
Set a variable to `false` to turn off compatibility mode for that framework.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we'd generally encourage people to omit the variable entirely if they're not changing it from the default.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you - fixed in f621496.

@govuk-design-system-ci govuk-design-system-ci temporarily deployed to govuk-frontend-review-pr-1439 June 13, 2019 08:33 Inactive
@36degrees 36degrees force-pushed the document-legacy-palette-config branch from f621496 to 093e2a2 Compare June 13, 2019 08:48
@govuk-design-system-ci govuk-design-system-ci temporarily deployed to govuk-frontend-review-pr-1439 June 13, 2019 08:48 Inactive
It’s hard to talk about this option without also talking about compatibility mode, so this also splits the documentation on compatibility mode out from the installation instructions and adds more detail about what it actually does.

Co-authored-by: Mark Green <[email protected]>
@36degrees 36degrees force-pushed the document-legacy-palette-config branch from 093e2a2 to 1402166 Compare June 13, 2019 08:49
@36degrees
Copy link
Contributor Author

Squashed into one commit and wrapped at 80 characters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

5 participants