Voice and tone
We build templates for fun and we don’t take ourselves too seriously. The writing should sound like a friendly senior developer explaining something over coffee: plain words, short sentences, the occasional wink.
Where the jokes go
Section titled “Where the jokes go”| Place | Tone |
|---|---|
| Home pages, hero text and taglines | Playful |
| Tutorials and explanations | Friendly, with a joke where it helps |
| Reference pages, steps and error messages | Straight. Nobody wants a pun when their build is broken |
The tagline
Section titled “The tagline”Every template uses the same line, with its own subject:
Clean Architecture for subject, minus the ceremony.
So it’s “Clean Architecture for AWS Lambda, minus the ceremony” and “Clean Architecture for GraphQL on Hot Chocolate, minus the ceremony”.
House style
Section titled “House style”- Use Australian spelling: colour, organisation, licence (the noun).
- Call things what people recognise. Say “logo” or “mark”, not “brand asset”.
- Use active voice and lead with the point.
- Write numbers as digits, and units the way developers write them: 512px, 1280 × 640, .NET 10.