Atomic design changed the way people thought about web design. Brad Frost and others made the case that designing smaller, reusable components made more sense than starting with whole-page layouts.
That was over a decade ago. Atomic thinking is now settled wisdom for designers. For content, the page still mostly rules.
Pagethink
The page is a ubiquitous, deeply ingrained way of working and thinking. It’s been around for thousands of years: even when words were scratched onto papyrus or slate, the concept was much the same. Here’s a blank space; start at the top, fill it with words and keep going until you reach the bottom. The page has been the default chunk for a very long time, and it’s lodged deep in how we think about content.
Even in a digital-first world, people think and create page-first. Word processing has done little to change that. Open Word or Google Docs and you’re still met with something that looks like a blank sheet of A4. But the page is a poor starting point for digital content.
Pages are hard to repurpose. Editors can deconstruct a finished page and pull out the useful bits, but it takes time. And the extracted pieces usually work less well than they would have if they’d been designed as adaptable components from the start.
Considering the chunks
Modular content is not a new idea. Dickens’ Pickwick Papers, serialised in periodicals through the 1830s, changed the way people thought about the structure of the novel: each instalment stood up on its own and worked as part of a greater whole. TV series do the same. Even films are increasingly chapters in longer franchises.
Digital content enables modularisation on another level. Long-form content and page builders like Divi and Elementor changed the way people assemble rich, multi-format pages. WordPress rebuilt its editor around blocks. Paragraphs in Drupal do something similar. The drag-and-drop toolbox got very powerful.
Breaking out of the paradigm
Good digital content broke out of the body-text-and-hero-image convention long ago. Drag-and-drop interfaces put real power in the hands of content creators.
Statistics, quotes, graphs, video, audio, maps and images can all be combined to tell engaging stories, to educate and to persuade. But too often these are treated as design elements: part of the presentation layer, not the content itself.
Page builders are brilliant at imposing atomic design patterns across a website, but they’re far less good at modularising the content underneath.
Designing for adaptability
A case study might be just a photo and a short paragraph. But it could appear in an opinion piece, in a report and on a landing page. It might make a good social media post too.
An author might also be a speaker at an event. The price of a product might be needed in an article and on a product page.
Treat these as structured components – tagged, defined once, used many times – and content gets cleverer. Correcting a mistake or adding a link in one place corrects it everywhere. This was always the dream of COPE (Create Once, Publish Everywhere), but it’s only now really becoming a reality.
When we build websites and content systems, thinking from the outset about the smallest sensible reusable components is what makes content flexible and sustainable. Which makes life better for the people who create content, and the people who use it.
Headless content management systems – such as Storyblok or Sanity – are built for exactly this: structuring content so it isn’t welded to a single page.
Atomic content grew up
When we first wrote this, “atomic content” was our coined phrase. The idea now has a proper name and an industry around it: composable content. Structured pieces, held independently of any one page or channel, assembled on demand wherever they’re needed.
The principle is essentially the same. What’s changed is that the tools, the vocabulary and the urgency have finally caught up. Content held as components, not pages, is no longer a nice-to-have for tidy-minded editors; it’s becoming the price of entry to a far more complex, multi-layered, omnichannel system.
Then the machines started reading
Urgency has arrived because while pages are written for humans, chunks are legible to machines.
Generative and answer engines don’t read your carefully art-directed page the way a person does, starting at the beginning and working through in a neat line. They pull pieces – a definition, a statistic, a quote, a step – and reassemble them into an answer you don’t control, in a place you may never have been. Content locked inside a page is harder to lift cleanly. Content held as well-structured components is ready to be found, quoted and reused.
AI is changing the other end too. It has made producing content extraordinarily cheap, and a lot of that content is slop: poor quality, made without much care or thought. When volume costs almost nothing, volume stops being a differentiator. What sets you apart moves upstream: the structure, the judgement and the things only you and your organisation know.
And AI scales whatever you feed it – including the mess. Loose, page-bound content was just about survivable when a human was there to fill the gaps with judgement. Hand the same material to an agent and the cracks expand. Structure used to be good manners; now it’s load-bearing.
Part of a bigger system
Atomic content was never really about the atoms. It was about treating content as infrastructure, rather than treating each page as a one-off.
That’s the heart of what we now call the content operating model: the system that makes content work – coherently, efficiently and at speed, for people and machines alike. Composable, structured content is how its content layer actually gets built. The atoms are how the model runs.
We’ve long argued that content is a better lens than digital for approaching organisational change. Atomic content is a small, practical expression of that bigger idea. Design the smallest repurposable pieces well, and you avoid chaotic complexity. You also hand people, systems and AI the raw material to make something brilliant, sustainable and genuinely adaptable.
