Content as a System

Most organisations accumulate content rather than building it. Articles are published when someone has time and an idea. Product copy is updated when a complaint is received. Documentation falls out of date and no one notices until a user reports a discrepancy. Microcopy varies by team, because different teams added it at different times with no shared standard. The content exists, but it does not work as a coherent system.

Content strategy is the practice of treating content as a system — something designed, maintained, and governed — rather than as a series of individual publishing events.

The content lifecycle

Every piece of content has a lifecycle: it is created, published, consumed, updated (or not), and eventually removed or replaced. Content strategy makes this lifecycle explicit rather than leaving it to chance.

Creation — what content will be created, by whom, to what standard? Creation should be guided by a content model (what fields are required?), a voice guide (how should this be written?), and a brief or plan (why is this content being created, and who is it for?).

Review and publication — who approves content before it is published? What is the editorial standard? For high-stakes content (pricing, legal, medical), what subject-matter review is required?

Maintenance — when will this content be reviewed again? Every piece of content should have a review date, particularly if it contains time-sensitive information. Content that is not actively maintained becomes inaccurate content.

Removal — when is content removed or archived? Outdated content that remains published is worse than no content: it misinforms users and creates trust problems when they act on it.

The content audit

A content audit is the systematic evaluation of all existing content: what exists, how it performs, and what should be done with it (keep, update, consolidate, remove). It is the starting point for any content strategy work, because strategy requires knowing what you have before deciding what to do next.

Audits are unglamorous but essential. They consistently reveal content that is duplicated (the same topic covered in five different articles), content that is outdated (still referring to a product feature that was removed two years ago), content that is missing (a topic users ask about frequently that is not covered anywhere), and content that performs — being found, read, and completing its purpose — versus content that does not.

Content governance

Governance is the set of rules, roles, and processes that determine how content is created, reviewed, published, and maintained. Without governance, content reverts to accumulation: whoever publishes most recently wins, consistency erodes, and the quality of the content as a whole cannot be maintained or improved.

Governance does not need to be bureaucratic. For a small team, it might be:

• A voice guide that anyone writing content is expected to read
• A content review checklist applied before publication
• A shared list of content types with character limits and required fields
• A quarterly review of all live content against a set of criteria

For larger organisations, governance includes editorial workflows, role definitions (who can create, who can review, who can publish), and content calendars aligned to product and marketing objectives.

Content quality compounds

The most important argument for treating content as a system is compounding. A well-maintained content system produces returns that accumulate over time: an article that answers a common question reduces support volume. A consistent voice builds brand recognition. A rigorous content model enables new presentation formats without requiring content rewriting.

Content that is not systemised does not compound — it costs. Outdated documentation generates support requests. Inconsistent voice erodes trust. Unmaintained articles rank for queries and deliver a poor experience to the readers who find them.

The choice between content as accumulation and content as system is a choice about whether the work you do today will still be working for you in two years. A system makes it possible. Accumulation makes it increasingly unlikely.

Internationalisation and localisation

Content that works well in English may not translate — not because the translation is poor, but because the content was designed only for English. Internationalisation (i18n) is the design of content to be locale-independent; localisation (l10n) is the adaptation of content for a specific locale. Both require planning from the start, not retrofit.

String length variation is the first structural concern. German and Finnish text is typically 30–50% longer than its English equivalent. “Sign in” becomes “Anmelden” (German) or “Kirjaudu sisään” (Finnish). UI elements with fixed widths, truncated containers, or pixel-precise button widths will break. Test every UI string at 150% of its English length before shipping.

Reading direction affects layout, not just text. RTL languages — Arabic, Hebrew, Farsi — require mirrored layouts: navigation on the right, directional icons flipped, text anchoring reversed. The CSS dir attribute and logical properties (margin-inline-start rather than margin-left) manage this technically, but the layout must be designed with RTL in mind, not retrofitted.

Cultural assumptions embedded in content are invisible until they fail. Date formats (DD/MM/YYYY vs MM/DD/YYYY), number separators, currency symbols, colour associations, and idioms that rely on cultural knowledge unavailable to the target audience all require explicit decisions.

Practical implementation: separate all user-facing strings from code into localisation files from the beginning; test layouts at 150% string length; design for both LTR and RTL; write plain language that travels better than idiomatic English; and for significant markets, commission native speakers to review localised content — automated translation produces grammatically correct but culturally tone-deaf copy.

This completes the Content Hub. The hub covers what content is, through writing for screens, microcopy, content models, and voice, tone, and strategy. Each section builds on the one before it — from the material, through the craft, to the system.