Structure

Content templates aren't forms to fill in

Templates are decision frameworks, not paint-by-numbers

You've seen the bad content template: a Word doc with brackets like [Insert Benefit Here] and [Add Customer Quote]. Someone fills in the blanks, ships it, and wonders why every page sounds identical.

The problem isn't templates themselves. It's templates that treat writing like data entry.

A good content template does three things: it names the structural decisions you've already made, it shows what belongs where, and it gets out of the way when the content needs to breathe. It doesn't script sentences. It maps the chassis.

What belongs in a structural template

Start with the decisions that shouldn't change page to page:

  • **Hierarchy anchors**: Where does the primary heading go? What comes before the first H2?
  • **Required elements**: What can't ship without? (Not "nice to have" — actually required.)
  • **Sequence logic**: Does the problem always precede the solution? Does proof always follow the claim?
  • **Content type signals**: How does someone know this is a guide vs. a reference vs. a walkthrough?

These are structural. They create consistency without dictating voice.

Then add the optional layer: **guidance, not fill-in-the-blanks**.

Instead of "[Describe the main feature]", write "What does this do that the previous version didn't?" Instead of "[Insert benefit]", write "Name the specific problem this solves — not the category of problem."

Questions force thinking. Brackets invite laziness.

The template audit you can run this afternoon

Pull up your three most recent pages built from the same template. Read them in sequence.

If you can swap paragraphs between pages without anyone noticing, your template is too prescriptive. If the pages have identical sentence structures in different sections, same problem.

Now check the opposite failure: do the pages feel like they're from different sites? If yes, your template isn't doing enough structural work.

The fix is usually the same: **strengthen the chassis, loosen the copy**.

Add more specific structural guidance ("This section names the three steps — always three, always steps"). Remove any sentence-level scripting ("Our solution helps you [verb] your [noun]").

When to break your own template

Templates shouldn't be sacred. They're useful until they're not.

If you're contorting content to fit the template, the template is wrong. If you're inventing new brackets every third page, the template is too narrow.

Build in explicit escape valves: sections marked "optional if X" or "replace with Y when Z." Make it clear that breaking the template for good reason is fine — breaking it out of laziness isn't.

The goal isn't uniformity. It's structured flexibility: pages that feel like they're from the same site, built by people who know what they're doing, without sounding like they were written by the same algorithm.

Templates for people who will ignore them anyway

If your team doesn't use the template, that's data.

Maybe it's too rigid. Maybe it's not rigid enough. Maybe it solves yesterday's problem. Don't make the template more emphatic — make it more useful.

Watch where people diverge. If everyone skips the same section, cut it. If everyone adds the same thing the template doesn't include, add it.

Templates should evolve as your content does. Freeze them and they become obstacles. Maintain them and they become infrastructure.

The best content template is the one your team actually uses because it makes their work faster and better — not because someone mandated it in a Monday meeting and never looked back.

← All posts