This is version 13.16 of the GOVUK Prototype Kit.
Go to the GOV.UK Prototype Kit site to get the latest documentation.
The Prototype Kit provides a simple way to make interactive prototypes that look like pages on GOV.UK. These prototypes can be used to show ideas to people you work with, and to do user research.
Read the project principles.
If you publish your prototypes online, they must be protected by a password. This is to prevent members of the public finding prototypes and thinking they are real services.
You must protect user privacy at all times, even when using prototypes. Prototypes made with the kit look like GOV.UK, but do not have the same security provisions. Always make sure you are handling user data appropriately.
This kit runs on version 20 of node. To find out the version you have and how to install version 20 you can use the guidance [https://prototype-kit.service.gov.uk/docs/install/node-mac] We always recommend you use the current long term support (LTS) version of Node.js.
The Prototype Kit always supports at least the current and previous LTS releases.
Once you have cloned the repository and have version 20 of node installed, you need to run: npm install in the prototype folder in terminal
The GOV.UK Prototype Kit is maintained by the Government Digital Service. If you’ve got a question or need support you can:
- email govuk-design-system-support@digital.cabinet-office.gov.uk
- get in touch on Slack
- view known issues on GitHub
If you’ve got an idea or suggestion, you can:
The govuk-prototype-kit repository is public and we welcome contributions from anyone.
Contributors to alphagov repositories are expected to follow the Contributor Covenant Code of Conduct. Contributors working within government are also expected to follow the Civil Service code.
We are unable to monitor activity on this repository outside of our office hours (10am to 4pm, UK time). To get a faster response at other times, you can report abuse or spam to GitHub.
GDS is an advocate of responsible vulnerability disclosure. If you’ve found a vulnerability, we would like to know so we can fix it.
For full details on how to tell us about vulnerabilities, see our security policy.