Visit the NHS.UK prototype kit site to download the latest version and read the documentation.
The NHS.UK prototype kit enables you to make interactive prototypes that will look like pages on NHS.UK. The prototypes you make are a great way to show ideas to others and for conducting user research.
If you publish your prototypes online, they must be protected by a username and 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 NHS.UK, but do not have the same security provisions. Always make sure you are handling user data appropriately.
Start the kit with npm run watch.
If you want to contribute to the NHS.UK prototype kit, by reporting bugs, fixing bugs, suggesting new features or writing documentation, then read our contributing guidelines.
Before running Gitpod, you must install the Gitpod.io application on your GitHub account.
Gitpod also requires access to public repositories. Enable this via Gitpod integrations. (Click on the 3 dots to edit permissions for your GitHub account. Gitpod may pre-select permissions. You need read/write access to code in the repos.)
Using your own GitHub credentials you can create, change, commit and push to branches on our Gitpod container via the "ready to code" button below.
Read an introduction to Gitpod (on Gitpod's website).
The below is only for maintainers of the prototype kit source code - these instructions aren't relevant if you're building your own prototype using the kit.
Run unit tests locally with npm run test.
Code pushed to the main branch will deploy on the Preview environment.
The live NHS.UK prototype kit Live environment, accessible to the public.
Note: Live is behind a server side cache which results in changes not appearing immediately.
- Merge required changes via PR into
mainbranch- Ensure the version number in
package.jsonandCHANGELOG.mdmatch, with a summary of the changes included in the changelog
- Ensure the version number in
- Verify the changes in the Preview environment
- Pull down merged
mainbranch to your local repository - Create a tag with the version number from the latest commit on
main- If the latest version you're looking to push is version "1.2.3", you can do this on the command line with
git tag v1.2.3git push --tags
- If the latest version you're looking to push is version "1.2.3", you can do this on the command line with
- Github actions will spring to life and create a release which will be visible on the releases tab of the repository.
- Finally, edit the description of the release to match the content entered into the changelog.
- To deploy the changes to Live, the promotion to Live from the Preview environment must have the appropriate approval in Azure.
Code analysis results can be found in SonarQube.
The NHS.UK prototype kit is maintained by NHS England. Email us, open a Github issue or get in touch on the NHS digital service manual Slack workspace.