Content without complexity
Pages, documents, media, news and knowledge bases across every property, in one place — organised, searchable, and version-controlled.
Built for editors who need autonomy and for IT teams who need control. Create, publish and manage content across multiple sites and languages without the chaos of scattered systems.
The content layer
Menus, pages, documents and media for all your sites, served through a clean API to whatever front end needs them.
One system, every property
One interface for every site in the estate. A brand change doesn't mean twelve separate rebuilds.
Real version control
One active version alongside multiple drafts; expired versions archived. Edited content doesn't appear publicly until it's approved. Up to ten stored versions per record, restorable to any point.
Block-based editing
Assembling a more complex page is an editorial task, not a development ticket.
Predictable editing
The same editor everywhere, formatting that behaves the same way whether you typed it or pasted it, and a preview that shows the real rendering rather than an approximation.
Media library
If the library is awkward to use, people download files and keep them in folders. That is how a brand ends up with uncontrolled copies in circulation.
One authoritative source
Insert the same image or document anywhere across your sites. Update it once and it changes everywhere. No broken links, no outdated versions in circulation.
Images and documents, one logic
The same organisation, search and permission model for images and documents, rather than two systems that behave differently.
Automatic derivatives
Upload once; the system generates the crops and sizes each context needs — desktop hero, mobile thumbnail, social preview — from a single source file.
Protected delivery
Files are reachable only through generated links on our own content delivery network, and the stored file list cannot be enumerated from outside.
Forms and events
A form that emails its submissions is a form that loses them. Forms are where personal data enters your organisation, which makes them the most compliance-critical part of a content platform.
One field set, two places
The same central field library serves internal data structures and public forms alike, with the same validation in both.
Submissions that go somewhere
Submissions are stored as records and routed to the right people — not emailed and forgotten.
Events with a lifecycle
Registration, ticketing, check-in and attendee communication, with the attendee list as data rather than a spreadsheet.
Data handling that survives an audit
Sensitive fields masked, exports restricted to named data owners, and automatic purging after a defined period.
Access control
Not everyone needs access to everything, and proving who accessed what shouldn't require a forensic investigation.
Define roles that match your organisation — editor, reviewer, administrator, department head — and assign permissions that make sense for it. Control what users can see, edit, publish or delete, down to individual content types or specific fields.
A marketing team member can manage one site's news without seeing another site's content. Regional editors see only their territory. A single permission can be granted to a single user.
Adding users, teams or entire departments doesn't require rebuilding the permission structure.
History and versioning
Every edit is recorded automatically: who changed what, when, and exactly which fields were modified — captured without manual effort. Any previous state can be restored in one step, not just the last save.
This isn't only convenience. Regulated industries need proof that content was accurate at a specific point in time; auditors ask for change logs; legal wants to know what the terms said six months ago. Retention is configurable per content type — keep everything, or clean automatically after a defined period.
News and knowledge base
Structured content that answers questions before they are asked.
News and articles
Write and format without HTML knowledge, schedule publication, organise by category and tag. Meta titles, descriptions and URLs are part of the workflow, not a plugin.
Knowledge base
A clean question-and-answer format, grouped by topic, product or audience — and the answers appear in the site's own search results rather than in a separate knowledge-base tool.
Where this module ends
Nitrogen Content handles content and the data that arrives through it. What happens after that — approval chains, handovers, internal requests, work items moving through defined states — is a separate module with its own engine.
Neither contains the other. You can run Content without Works, and Works without Content.