Content atomization
Breaking one large piece into small, labeled fragments that can stand alone and be found, reused, or recombined later.
See it
What it is
Content atomization breaks a large source into small, self-contained units: one claim, quote, chart, example, answer, clip, or checklist per atom. Each unit keeps enough context and source information to be found, reused, and recombined without reopening the whole report.
Reach for it when a research report, webinar, course, or long guide contains many ideas that different channels and teams will need later. Give every atom a clear label, audience, source pointer, usage rights, and expiry or review date. That turns fragments into managed content instead of a folder of mystery clips.
Gotcha: atomization splits; repurposing adapts. A paragraph lifted from a report is an atom, but it is not yet a good social post. The term is also unrelated to Brad Frost's Atomic Design, which breaks interfaces into reusable components rather than breaking source material into content fragments.
Ask AI for it
Atomize this source into reusable content blocks for a Contentful import. Return a JSON array of 20 to 30 objects using these fields: id, atomType, title, body, audience, topic, sourceSection, sourceQuote, rights, reviewDate, and suggestedChannels. Limit each atom to one claim, example, quote, chart, answer, or checklist; include enough context for it to stand alone. Do not rewrite an atom for a channel yet. Flag any fragment that depends on missing context or an unsupported claim.