Skip to main content Skip to list of get started
Service phase: Beta

This is a new service – give us your feedback to help improve it.

Get started

Design principles

Principles to follow when designing and building National Archives services.

Contents

  1. Showcase professionalism
  2. Grow trust
  3. Include everyone
  4. Think forwards
  5. Build robustness
  1. Avoid using cheesy graphics, generative AI, stock photography, icons and unnecessary animation to add visual interest.
  2. Enable more support for technologies that allow a pure browsing experience such as reader modes.
  3. Follow editorial and content guidelines and don't rely on AI to write copy.
  4. Don’t write titles that look like clickbait.
  5. Provide links and references to trusted sources.
  1. Respect the user's choices, including their preference to remain anonymous.
  2. Track only with explicit consent and assume an incognito browsing experience is needed unless beneficial to the user to offer otherwise.
  3. Give users full control and place them in the driving seat.
  4. Provide transparency about the use of data.
  5. Clearly declare where and how AI has been used.
  1. Design and build services that support everyone.
  2. Don’t limit inclusion to a checkbox exercise of WCAG compliance.
  3. Consider users without access to the latest technologies.
  4. Add simple introductions and explanations for non-expert users.
  5. Avoid using product names that don’t properly describe the service.
  1. Where possible, build services that can be more easily updated or replaced.
  2. Split complex functionality up into discrete services or pages.
  3. Explore and use new technologies as an enhancement but plan for their obsolescence.
  4. Push small, incremental updates often rather than large changes less frequently.
  5. Plan for the future and create content and structure under URLs that will stand the test of time.
  1. Design services that can work in any network conditions and optimise for performance.
  2. Consider users that have limited access.
  3. Where possible, make page URLs sharable and stateless.
  4. Be wary of relying on third party services and prepare for situations when they might not be reachable.
  5. Build services that inspire confidence.

Back to top