Explainer
Single-Source Publishing: One Source, Every Output
What It Means
Write It Once, Publish It Everywhere
Single-source publishing, or single sourcing in technical writing, means keeping one maintained source of content and producing every output from it. The PDF manual, the web help, the interactive viewer, and the portal are all generated, not copied and adapted. It usually covers variants as well: the same source producing the version for each product, model, or audience.
The alternative is the one most teams start with. Each output gets its own copy, and each copy is corrected separately, so every change is made several times and one of them is eventually missed. Single-sourcing is not a tool you buy; it is a set of properties your content has to have.
What It Takes
Five Properties of a Single Source
- Content separated from formatting
- The source says what things are (a step, a warning, a part number), and each output decides how they look. Formatting typed into the source, from manual line breaks to layout tables, has to be undone for every output that isn't the one it was typed for. How XML becomes a PDF.
- Units smaller than a document
- Topics in DITA, data modules in S1000D: self-contained pieces that can be assembled into more than one deliverable. A source that only exists as whole documents can be converted to many formats, but not recombined. DITA topic types.
- Reuse by reference, not by copy
- A warning written once and referenced everywhere it applies, instead of pasted into forty places. Change it once and every output that uses it changes with it. Keys and content references.
- Variants as metadata
- Differences between products, models, or audiences marked as conditions or applicability rather than written into separate copies, so one source can produce each variant on demand. S1000D applicability.
- A publishing pipeline for each output
- Stylesheets or plug-ins that turn the source into PDF, HTML, an interactive viewer, or a data feed. They are maintained assets: every branding change and toolkit upgrade lands in them. The DITA Open Toolkit.
Standards and Tools
What Teams Build It With
Three open standards were designed for it. DITA builds deliverables from typed topics assembled by maps. S1000D stores data modules in a common source database and assembles publications from them. DocBook profiles book-shaped content for different outputs; our DocBook and DITA comparison covers where each fits.
Around the format sit four kinds of tool: an editor that works in it, a component content management system to store, version, and track reusable pieces, a publishing engine for each output, and a delivery layer. Our guide to buying publishing software covers how to choose. Teams can approximate single-sourcing in Word with disciplined templates, which holds until reuse and variants multiply; we explain where that line falls in why Word breaks at scale.
Where It Fails
Single Sources Drift Back Into Copies
Programs rarely fail at the technology. They fail when habits reintroduce the copies the source was meant to remove:
- Reuse without ownership
- Shared content edited for one context quietly breaks another. Every reused component needs an owner and a rule for who may change it.
- Conditions nobody can read
- Variants nested inside variants until no writer can say what a given reader will see. When filtering logic outgrows a person's head, the model needs simplifying, not more conditions.
- Formatting smuggled back in
- Writers under deadline force a page break or a bold run to make one output look right. Each one is a small fork in the single source.
- The pipeline as an afterthought
- The PDF stylesheet built once during the project and maintained by nobody after it. Outputs degrade until someone starts fixing PDFs by hand, which is where single-sourcing ends.
- Delivery left out
- One source, many outputs, and every one of them still lands as a file on a share drive. Readers never see the benefit if the last step is a copy nobody can update.
The last failure is the most common. A single source that ends in uncontrolled PDFs has moved the copying problem downstream. The Content Portal is our answer to that step: one controlled, searchable, version-aware destination instead of another file.
Is It Worth It
When Single-Sourcing Pays
It pays when content is published several ways, comes in several variants, changes often, or has to be revision-controlled for a regulator or customer. The more of those apply, the faster the copies cost more than the structure. It rarely pays for a short document in one format that seldom changes.
If you are unsure which side you are on, the structured content readiness checklist lists the symptoms that say the copies have started costing more.
FAQ
Questions We Hear
What is single-source publishing?
Maintaining one source of content and generating every output from it (print manuals, web help, interactive viewers, portals, data feeds) instead of maintaining a separate copy for each. In technical writing it is often called single sourcing, and it usually covers variants too: one source producing the versions for different products or audiences.
What is the difference between single-source and multichannel publishing?
Multichannel publishing is about the destinations: the same content reaching print, web, and mobile. Single-source publishing is about where it comes from: one maintained source. You can publish to many channels from many copies, which is multichannel without single-sourcing, and it is the expensive way to do it.
What tools do you need for single-source publishing?
A structured format (DITA, S1000D, or DocBook are the common standards), an editor that works in it, usually a component content management system to store and track reusable pieces, a publishing engine for each output, and somewhere controlled to deliver the results. The format and the governance matter more than any single tool.
Can you do single-source publishing in Word?
Up to a point. Templates, styles, and fields can keep one document consistent, and some outputs can be generated from it. It breaks down when content has to be reused across many documents, filtered for variants, or published to formats Word was not built to produce, which is where structured formats take over.
Is single-sourcing the same as content reuse?
Reuse is one of the mechanisms; single-sourcing is the outcome. Reuse lets one component appear in many places. Single-sourcing also needs content separated from formatting, variants handled as metadata, and a pipeline that produces each output without manual work.
Get In Touch
Publishing the Same Content Five Ways?
We build single-source pipelines in DITA and S1000D, from converting what you have to the outputs your readers use, and deliver them through the Content Portal.