Content Strategy
What it is
Content strategy decides what content exists, for whom, in what voice, and how it is maintained after launch. It covers the pages and strings a product ships, the help and policy text behind them, and the rules that keep them consistent when several people write them.
Why it matters
Content is the part of a product nobody owns, so it rots. Screens are redesigned around copy written for the previous structure; help pages describe two releases ago; the same concept appears under three names. The cost shows up as support calls and as quiet abandonment. A written strategy is small — a page of rules and an owner — and it is the difference between content that is maintained and content that accumulates.
In this track
- Content audit and inventory (03-design-ux/08-content-strategy/01-content-audit-and-inventory) — finding out what content exists, who reads it and what is out of date.
- Voice, rules and maintenance (03-design-ux/08-content-strategy/02-voice-rules-and-maintenance) — writing down the voice and the naming rules, and deciding who owns the content afterwards.
Prerequisites
None.
Go deeper
- UX Writing & Microcopy (03-design-ux/07-ux-writing-microcopy) — the sentence-level craft this strategy governs.
- Information Architecture (03-design-ux/09-information-architecture) — where the content sits and how it is found.
- Design Systems (03-design-ux/32-design-systems) — keeping the words as consistent as the components.
- Notion (03-design-ux/14-notion) — where strategies and content rules are commonly kept.