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

[WIP] Bring in new toolkit with new input fields #444

Closed
wants to merge 6 commits into from

Conversation

pcraig3
Copy link
Contributor

@pcraig3 pcraig3 commented Feb 16, 2017

This won't actually be ready to go until the pull request in the frontend toolkit is merged


This pull request

  • updates the govuk_frontend toolkit to the latest
  • updates the digitalmarketplace frontend toolkit to the latest
  • updates the homepage beta header colours (blue text on a white background)
  • treats links with a role="button" as buttons (ie, "Apply for this opportunity" link)
  • removes some unused classnames
  • brings the forgotten password link closer to the password input field on the login screen

💥 Boom 💥

Brings in the latest govuk_frontend_toolkit available
on NPM, and the latest digitalmarketplace toolkit.

Also:
- removes external link styles, as these will no longer compile
- removes custom focused/selected classes for radios/checks
The govuk_frontend_toolkit stuff uses different javascript
formatting than us where they begin their files with
semicolons but don't end files with them.

Our JS does the opposite, and so concatenating the files
results in a compilation bug somewhere in the middle.
The phase banner is now always dark blue, which
doesn't work on our homepage.
Reversing the colours (white background, blue text) instead.
Javascript will automatically treat links with a
`role="button"` and a `.link-button` class as buttons.

This is part of the govuk_frontend_toolkit, not the
digitalmarketplace one.
The digitalmarketplace toolkit is no longer using this
class, so let's get rid of it.
Our secondary action links have a few context dependent
styles, so I've added a new one and I've pulled them
into their own file.

Also removed a duplicated import.
@pcraig3 pcraig3 force-pushed the pc-try-terrific-new-toolkit branch from a0085ea to e2213ae Compare February 20, 2017 16:08
@pcraig3 pcraig3 closed this Feb 20, 2017
@pcraig3 pcraig3 deleted the pc-try-terrific-new-toolkit branch February 20, 2017 16:09
@pcraig3 pcraig3 restored the pc-try-terrific-new-toolkit branch February 20, 2017 16:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant