Content design Guides, templates and articles
Guides, templates and articles about content design, government communications, digital experience with a few case studies thrown in for fun.
Turn your house style into rules a machine can check
Your house style only works if people apply it. How to turn your mechanical style decisions into rules a browser tool checks on every page before it goes live.
WCAG 2.2 for writers: what you can fix without a developer
You don't need a developer to fix most content accessibility issues. What WCAG 2.2 asks of writers: headings, link text, acronyms, direction-free wording, more.
The Style Manual rules that slip through review
Single quotes, sentence case, numerals from 2: the small Style Manual conventions that slip through careful review, and ways to catch them before you publish.
Hidden verbs: the quiet bloat in government writing
Hidden verbs quietly bloat government writing. How to spot the pattern in phrases like 'make an application', and turn them back into verbs readers can act on.
Passive voice isn't a crime. It's usually just fog.
Passive voice has legitimate uses in government writing. The problem is the fog it creates everywhere else. How to spot it, fix it and learn when to keep it in.
How to run a 10-minute readability check before you publish
A practical pre-publish routine: check reading grade, passive voice and Style Manual basics in about 10 minutes, using one free checker built into your browser.
Your content reads at year 12. Your readers are at year 7.
Most government content is written three reading levels above its audience. Why year 7 is the Style Manual's target, and how to know where your pages now stand.
Why's it called Confetti?
Confetti is named after what you see on screen: a page in 8 colours, one per kind of problem. Why that mess is the work, and what that name obliged us to build.
Confetti flags. You decide.
A checker can prove your page is mechanically spotless. It cannot know if the page works. How to use Confetti, its flags and its checklist, with real judgement.
Retrofitting existing services to the Digital Inclusion Standard
Digital Inclusion Standard existing services: how to retrofit a live estate you cannot take down, triage the gaps by harm, and know when to apply for exemption.
Digital Inclusion Standard content checklist
A content checklist for the Digital Inclusion Standard: the content decision inside each of the five criteria, what good looks like, and who records it.
The Digital Inclusion Standard is not an accessibility job. Content owns part of every criterion.
The Digital Inclusion Standard covers every existing public-facing government service. What each of the five criteria asks, and the share content teams own.
AI procurement for government content
DTA AI procurement guidance covers risk, not content. Here are the accessibility, plain language, and accountability requirements to put in the contract itself.
What your privacy policy must say about automated decisions
From 10 December 2026, privacy policies must describe significant automated decisions. It is a transparency rule, and it will fail without content design.
Content audit starter template for government websites
A minimum viable content audit spreadsheet for government websites. Eight columns, one row per page, every row ending with a clear action. Free download.
You cannot outsource accountability for accessible content
When a vendor builds your government website, the agency still owns accessibility. Put accessibility requirements in the brief and contract before you sign off.
Using AI in government content: what to try, and what to leave alone
A model shows you what your content does. It cannot decide what it should say. What to try, what to leave alone, and what decides whether it works.
How to write an Alternate Access Plan
An Alternate Access Plan names each unresolved accessibility barrier and how people can still complete the task. The AHRC named the artefact. Template below.
Plain language does not fail at the draft. It fails after launch.
Government writers are not the problem. Readability fails after launch, because no role owns the whole site. Here are the four roles that fix it.
The eight decisions a content governance model has to make
Content governance for Australian government is eight decisions, not a document. Who owns, who approves, what standard, what triggers retirement, and who answers.