Add blog post: Test Archaeology

[JosephWardDotTech]

Content Guidelines

Post content must have a strong technical focus with other engineers being the primary audience.
There are other communication channels for non-technical content and delivery or service updates such as dvladigital.blog.gov.uk.

Content Guidelines - Security

Consider if the content of your post, including and images, has any security concerns:

• would the information be revealing to an attacker?
• is the content too revealing of backend processes?
• do we need to make specific details public?

Post content must not include:

• identifiers for production infrastructure e.g. IP addresses, network ranges, cloud provider IDs etc
• data relating to real customers or staff members

If you have any doubt please seek support from the cybersecurity team before publishing your content.

Content Guidelines - Communication

You must consider if the content of your post could cause damage to the reputation of the organisation.

Your post content should not describe, or be directly related to:

• changes that impact staff experience e.g. automation of work, changes to the types of work undertaken
• changes that impact customers experience e.g. changes to customer process, customer waiting times
• specific DVLA internal or external services

If you have any doubt please seek support from the External Communications team before publishing your content.

Content Guidelines - Accessibility

All content must be accessible to all users. This includes:

• using appropriate headings to structure content
• using descriptive alt text or captions for images and figures
• using descriptive link text for hyperlinks
• using appropriate contrast for text and images
• using helpful formatting such as lists and tables to structure content

While not DVLA-specific, the GOV.UK Content and Publishing Service has some useful guidance on formatting content to be accessible and clear.

Given our audience is primarily other engineers, consider the use of technical language and jargon.

Aim to use clear and concise language that is accessible to a wide range of readers, including those who may not be familiar with specific technologies or concepts.