Skip to main content

Search the Commons

Type at least 2 letters. Use the arrow keys to move through results, Enter to open, Escape to close.

Ask a question instead: answers drawn from across the Commons, with links to the source. Or browse the site map.

Contribute and get help · Help us build this

Help us build the Commons

In short: a plain English summary
  • This page shows how to help build the Commons.
  • You can vote for new features.
  • You can contact us using a form. We never show an email address.

Everything on this page runs on GitHub: votes are 👍 reactions, suggestions and messages are GitHub issue forms that open already filled in. You need a free GitHub account to vote or send; if you don't have one, ask a colleague.

Ways to help

Roadmap

The stages below come from the backlog. For the scores behind each priority, delivery objectives, government strategy and capacity, see the open roadmap and priorities. To help decide what comes next, take part in user research.

Backlog

Every item is also a GitHub issue labelled backlog, so you can comment, follow or pick it up. Priority uses MoSCoW: must, should, could, won't (this time).

ItemPriorityAreaStatusWhy it matters

Wishlist and votes

Vote for the features you need most by giving the wish a 👍 on GitHub. Votes help set the order of the backlog, and you can change them at any time.

Suggest something new
Describe the task and who it is for, not the solution.

Co-design

Every method has an alternative: if a live session doesn't suit you, use the asynchronous route or the contact form. We provide captions, transcripts and materials in advance.

MethodWhenHow

Session times that work across time zones

Live sessions rotate between three times, so no region always gets the early or late slot. Pick the partners taking part to see each slot in their local time. Times in grey fall outside 8am to 7pm local time; the asynchronous route is always open.

Who is taking part?

Charter, rules and safeguards

Principles

House rules

    Guidelines

      Safeguards

      Read the full charter, code of conduct and contributing guide on GitHub.

      How we keep content trustworthy

      The Commons checks itself. These routines run automatically or on a schedule; "planned" ones are on the backlog.

      RoutineWhat it doesWhenStatus
      Open findings from the latest content health report

      Where our content comes from

      Who masters the real thing

      Where another body keeps the authoritative version, the Commons links to it rather than keeping its own copy.

      WhatAuthoritative sourceUsed on
      Examples, templates and estimates, and how each is labelled
      WhereKindWhat it isHow you can tell

      The provenance audit runs on every change: if anything that looks like an example appears without being registered here, the build fails. Spotted something that looks invented? Tell us.

      Contributors

      See the contributors list. Credit is by GitHub username or organisation, never personal details.

      GitHub resources

      Releases and change log

      The same notes are in CHANGELOG.md, and each release is tagged in Git. Open from any page.

      Solution build and development bundle

      Every product, architecture and delivery document for this version in one standalone page: product requirements, theory of change, user research, architecture (solution, high-level and low-level design), functional, technical and integration requirements, build manifest, README, change log, decisions and build log.

      Open the bundle (repository copy)

      The bundle is generated from the repository's docs by scripts/build_bundle.py, so it always matches the build.

      Give feedback

      Choose the route that suits you. None of them asks for your name or email, and we never show an email address.

      The Microsoft Form: questions and set-up (for the Commons team)

      Questions

        Download the questions as a Word document (for Microsoft Forms' Quick import, where your organisation allows it).

        Settings

          Set-up steps

            About another portal?

            Contact us

            Send us a message through this form. It is the only way to contact the team: we never publish an email address, which keeps spam and impersonation down, and you never need to give yours. The form opens a pre-filled GitHub contact issue (a free GitHub account is needed; if you don't have one, ask a colleague) and we reply there.

            Up to 2,000 characters. Please don't include personal data, or anything official-sensitive.

            See contact issues and our replies on GitHub.

            Security problem? Report it privately through GitHub's vulnerability reporting, not here.