Validation flow

From change to publication

Every change to the brand system follows the flow below. Nothing reaches production without validation.

1. Proposal

A communication officer or designer submits a change via:

• Pull request in the Git repo (for technical users)
• Theme Wizard for non-technical users (automatically generates a PR)
• Frontify portal (for broad catalogue content)

2. Automated checks

On every PR, CI runs:

• WCAG 2.1 AA contrast check on all changed tokens
• Schema validation against DTCG 2025.10
• Lint rules (no hardcoded colours, no unauthorised font names)
• Build test (all outputs render without errors)

A failing check blocks the merge.

3. Human review

A reviewer from the Chancellery team assesses:

• Strategic coherence with the system
• Application boundaries (does this change touch multiple institutions?)
• Documentation quality

4. Publication

On merge, all outputs are automatically rebuilt and published:

• npm packages tagged and published
• Brand portal refreshed
• Email notification to subscribers (“new templates available”)
• Change logged in the public changelog

5. Semi-annual audit

Twice a year, the Chancellery team conducts an audit:

• Are tokens actually used? (telemetry via Brand portal)
• Which exceptions are still in force and remain justified?
• Which institutions are lagging in adoption and need additional support?

The audit is published as a public annual report.