Community and contribution - Feedback or share insights

Take part in the discussion and help us improve things for everyone.

We want to hear how you and your users experience things in the service manual. You can do this by taking part in discussions on GitHub, which is the open collaboration space we use.

1. Find the thing you want to feedback on

If the thing is already published in the service manual, go to the relevant page. You'll find a link to the GitHub issue at the bottom of the page.

Or you can go directly to GitHub and look in 1 of the 3 project boards in the community backlog:

If the thing has not been published, it may be in one of the backlogs as a proposed item. (If it's not in a backlog, you can propose a component or pattern or other issue yourself.)

You can use search to find things in the backlogs, for example "buttons".

A screenshot of the search bar in the design system backlog

Click on the issue to see the discussion and scroll to the bottom if you want to comment.

2. Leave a comment

You need to sign up to GitHub if you want to comment. Anyone can sign up for free.

Use the textbox at the bottom of the page to give your feedback or share insights.

A screenshot of the text box at the bottom of a GitHub page

If you can, please share:

  • some information about your service or use case
  • your design thinking, with screenshots if you have them
  • any research findings you have

Even if your findings do not lead to a change in the service manual, it's helpful to share anyway. People across NHS digital teams read the discussions on GitHub to see how others have approached things and what they've learned.

Important: Share information responsibly

Remember that all the information on GitHub is open to the public.

3. What happens next

After you have submitted your comment, the service manual team will:

  • get a notification from GitHub
  • review the issue as part of the weekly service manual community rota
  • let you know if the team will take any action

The service manual team does not usually act immediately on feedback. We sometimes need to see evidence across several teams before we can be sure that something is a problem.

If you have any problems or questions, feel free to get in touch.

Updated: March 2024