Skip to main content

Guidance and regulation

Skip to results
285 results sorted by Most viewed
From Government Digital Service (GDS)
  • How to find digital outcome, specialist and user research services on the Digital Outcomes and Specialists framework.

  • Central government organisations are expected to use the GOV.UK website for their publishing, unless there’s a good reason not to.

  • Data security control principles to use when processing and sharing personal data in your service.

  • Use this guidance to make sure that you choose an appropriate .gov.uk domain name.

  • Make sure your technology, infrastructure and systems are accessible and inclusive for all users.

  • Consistent and standards-based comma-separated values (CSV) files help make data more effective and easier to share across government.

  • Check if your organisation is eligible for a non-government domain name and how to get one.

  • Understand your users and their needs. Develop knowledge of your users and what that means for your technology project or programme.

  • Publish your code and use open source to improve transparency, flexibility and accountability.

  • Configure email services securely using encryption and anti-spoofing.

  • All codes of practice to accompany data access measures in the Digital Economy Act 2017.

  • Find out if your organisation is eligible for a .gov.uk domain name and what to do if it’s not.

  • These principles describe how the government should manage legacy technology.

  • Guidance for businesses and organisations holding EU trade marks at the end of the transition period.

  • Find out who to get permission from to apply for a .gov.uk domain name.

  • Good Practice Guide (GPG) 44 helps you choose the authenticator that will give you the right level of protection for your service.

  • Spreadsheets are a common way to share data. Use this information to help you avoid common errors, improve interoperability and create more accessible spreadsheets.

  • What to do when your .gov.uk domain name is approved.

  • Make sure that domains that do not send email cannot be used for spoofing.

  • Increase sustainability throughout the lifecycle of your technology.