When different people publish content in different styles, the site starts to feel like several organisations sharing one address. Consistency isn't about rigid rules — it's about trust. A site that feels coherent feels reliable.
| Thing | How to write it |
|---|---|
| Organisation name | Middleton Co-operating (note the hyphen in Co-operating) |
| Dates | Wednesday 25 June 2025 (no commas, no st/th/rd) |
| Times | 7pm, 10.30am (no space before am/pm) |
| Free events | Always say "Free to attend" explicitly |
| Headlines | Sentence case (only first word and proper nouns capitalised) |
| Links | Descriptive text, never "click here" or "read more" |
| Addresses | The Lighthouse Project, Middleton Shopping Centre, M24 4EL |
Add to this as questions come up. The style guide belongs to the whole team.
Even a simple two-step process prevents most errors from reaching the live site.
The review doesn't need to be formal. It just needs to exist. Ask one other person:
In Drupal: save your content as Draft rather than Published until it's been checked. Ask your trainer to show you where this setting lives in the workflow.
Content design is problem-solving. Start with your reader's question.
People scan. Write short, front-loaded, plain-English sentences.
Paste plain. Use headings for structure. Alt text every image.
Consistency builds trust. Draft, review, publish — every time.