If you are a frontend developer you may find this guide useful.
This application should be designed to pass a GDS service assessment
but it is not expected to be hosted on .gov.uk. The header and footer, for example,
do not carry the Crown logo.
- The GDS service manual
- GDS Elements - a collection of SASS repositories and a page template
- Design patterns
- Progressive enhancement
- Targeted browsers
- Accessibility
- Paypal Automated Accessibility Testing Tool
- WAVE plugin for Chrome
- Screen reader poll from RNIB
- Tink's blog
The UX language is efficient and simple. This is the result of much thought and synthesis from the UX team, and considerable research with the users.
The UX team have provided high fidelity mock-ups of the screens and interactions.
View the The demonstration site
You may want to consider using IntelliJ Ultimate with the Scala plugin.
Virtualbox and Microsoft's virtual machine images allow various flavours of IE to be run on the desktop.
If you use macOS it's worth finding out how to use VoiceOver.
On Windows you can use NVDS and JAWS.
The sass for the site is located here: stylesheets
Logically the application sass depends on GDS Elements which depends on GDS Frontend Toolkit, but the SBT sass plugin was unable to set the sass load-path. The following folder structure is the work-around, and it's important to note that because of this the vendor dependencies are actually checked into the source code.
Folder explanation:
colours- the colours folder from the GDS Frontend Toolkitdesign-patterns- also from the GDS Frontend Toolkitelements- files from GDS Elements SASS repostatic- files taken from AlphaGov static repo- The files in the
stylesheetsfolder itself are from the GDS Frontend Toolkit
The application.scss file pulls everything needed in.