-
Notifications
You must be signed in to change notification settings - Fork 20
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
Swap gem layout #2774
Swap gem layout #2774
Conversation
cab5e3d
to
2caf45b
Compare
2caf45b
to
9458eb7
Compare
9458eb7
to
ae8cb74
Compare
Updating frontend to use the gem_layout
ae8cb74
to
27cc40c
Compare
27cc40c
to
0fd597d
Compare
0fd597d
to
1274c00
Compare
Changing some templates to use the full-width layout. Change layout & dependancies - Remove redundant feedback element (appeared twice on page) - Example Page: /find-local-council Update to resolve visual differences for frontend swap, changes resolve a border that is around the lookup element Remove borders / padding from swap on: "/foreign-travel-advice" to maintain existing visuals.
1274c00
to
630c457
Compare
to include Design System class
630c457
to
fa4bb72
Compare
+ add margin to replace spacing between lookup and feedback. eg: /find-local-council
Adjust grid to match Design System + slight margin adjustments to mimic current design
- Update "/settle-in-the-uk" flow to use Design System grid, - Remove redundant CSS - Adjust Design to maintain or align.
Redundant as gem_layout_full_width replaces this.
fa4bb72
to
c0046ef
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few pithy comments and questions. I think quite a few of these are classes used for testing only, which is something we don't wanna do so we don't clutter our markup. Incredible cleanup job here!
Update to remove redundant classes and tags
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unofficially approved 👍 I reckon we should hold off on this until Ian's point on the heading is sorted out.
@@ -69,7 +69,7 @@ class LicenceTest < ActionDispatch::IntegrationTest | |||
end | |||
|
|||
within "#content" do | |||
within ".page-header" do |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Always big ❤️ to removing test-only classes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unofficially approved 👍 I reckon we should hold off on this until Ian's point on the heading is sorted out.
🙌🏼 Holding tight re the header visual.
What?
Update
frontend
app to usegem_layout
template fromstatic
.Why?
As part of on-going a11y work to align architecture & use Components to ensure consistency and future proof to allow a11y improvements to cascade across the site.
Visuals
Slight changes, some manual spacing adjustments have been made to mimic current design.
Selection of visuals:
Anything else?
Related PRs
Enhancement PR:
Remove duplicate
<headers>
Resolve e2e PR
alphagov/govuk_publishing_components#2101
Adding additional URLs to README for ref.
#2793
Converting the layout to the gem version resulted in the lookup pattern not inheriting the relevant styling correctly. Upon inspection, this is due to elements from the gem like
fieldset
not being utilised withinfrontend
and therefore not using the shared classes - this has been manually adjusted.Example page:
http://www.gov.uk/find-electoral-things
Solution
This ties into the issue raised here:
alphagov/govuk_publishing_components#2096
Should the lookup pattern be it's own Component or use a common combination of Components (
fieldset, input, button
etc) these discrepancies would reduce.