How does content reuse work with Calenco?
Published on
How does content reuse work with Calenco?
Content reuse is the central mechanism of a CCMS (Component Content Management System). In Calenco, it means writing content once and then including it by reference in every document that needs it, without ever copying it. A document is no longer a continuous text but an assembly of reusable modules linked to their Single Source of Truth. This approach determines the consistency of the documentation corpus, the cost of updates and the cost of translations.
The reusable module: Calenco's basic building block
A module is a self-contained piece of content. It can be a paragraph, a safety warning, a maintenance procedure, a technical specification, a table of characteristics or an image.
Each module is stored just once in the platform, with its own identifier, within a content library shared across the organization.
Documents never contain copies of these modules. They contain references to them. This distinction separates genuine reuse from simple copying and pasting: in one case, information exists as a single instance; in the other, it is duplicated every time it appears.
Assemble rather than rewrite
When a writer creates a new document in Calenco, they do not start with a blank page. They draw from the library, insert the modules they need and only write content that does not already exist.
The nature of the work changes. A significant part of document production shifts from entering text to structuring content: choosing the right modules, organizing them and identifying what is missing.
Across a catalog of similar products, a considerable proportion of the content may already be available. Time is saved not by writing faster, but because much of the content does not need to be written a second time.
Granularity down to a single word
Calenco supports a level of detail that few tools reach. A module can cover anything from an entire chapter to a single word.
A commercial name, a product reference, a unit of measurement or the name of a standard can each be a module in its own right. When a name changes, it is corrected once and updated throughout the documentation catalog.
This fine granularity makes it possible to handle cases where two documents differ by only a few terms, without duplicating all their content.
Automatic propagation of updates
When a technical specification changes, the correction is made to the original module alone. All documents that reference it then regenerate automatically, in every language and every output format.
An entire documentation corpus can therefore be updated through a single operation. There is no longer any need to identify the affected documents, open them one by one, locate the passage and repeat the same correction.
This mechanism eliminates two risks that affect any large documentation set: overlooking a document during an update, and circulating divergent versions that provide contradictory information about the same data.
Reuse and product variants
Reuse delivers its full value in organizations that manage multiple variants of the same product, multiple versions of a software application or multiple equipment configurations.
These documentation sets share a substantial common foundation and differ only in specific areas. Without reuse, each variant requires a complete document and therefore full maintenance. With modules, the common foundation is shared, and only the specific sections are unique to each variant.
Amphitech uses Calenco to update its product sheets automatically, dynamically reusing photos, diagrams and illustrations between sheets for the same models.
Reuse and multilingual management
Multilingual documentation is where the impact is most measurable, because the savings add up. Information written only once is translated only once, regardless of how many documents use it.
Calenco has a connector to CAT (Computer-Assisted Translation) tools equipped with translation memory, including integration with the Phrase platform. When source content changes, Calenco compares it with its latest language version to identify exactly what needs to be retranslated.
Pellenc publishes its technical manuals in twenty languages with Calenco and reduced its translation costs by 60% after moving away from InDesign.
Reuse and multi-format publishing
Reuse only works because content is independent of its presentation. This is the principle of separating content from presentation: the writer works on the content, and a stylesheet applies the layout automatically at publication time.
The same module can therefore be published as low- or high-resolution PDF, HTML, WebHelp, ePub or Word, or on tablets and smartphones, without ever being manually adapted.
Without this independence, each format would require its own version of the content, its own copies and therefore the same risks of divergence as copying and pasting.
Reuse and approval workflows
A module reused in twenty documents affects the reliability of all twenty. Reuse therefore increases the need for approval. To address this, Calenco integrates approval workflows (review cycles) directly into the documentation lifecycle.
Technical writers, engineering managers and quality managers each intervene at their own stage, working on the same version of the module. Automatic versioning preserves every state. A version comparison module makes changes between two states visible during review.
In sectors subject to regulatory requirements, such as industry, energy and healthcare, this traceability is a condition of compliance. It provides evidence of who approved which content, on what date and in which version.
Identifying reusable content
Reuse is not just a technical feature. It requires preliminary analysis to identify what existing documents actually have in common.
Til Technologies carried out this work with Calenco. The company identified what its technical documentation shared with its training materials, then converted those common passages into modules shared between both uses.
This stage often shapes the entire migration project. It reveals redundancies that no one had measured and determines the level of reuse achieved afterwards.
What reuse changes in practice
Consistency becomes a property of the system rather than a requirement imposed on writers. Two documents cannot diverge on shared information, because they point to the same module.
Reliability improves because copy-and-paste errors disappear along with the copies. Update times shrink because one correction replaces the work of replicating it.
EDF relies on Calenco for its regulatory documentation, where the volume requires every correction to reach all affected documents automatically.
Conclusion
Content reuse is more than a convenience. It is the mechanism that keeps technical documentation maintainable once it reaches a certain volume, with multiple variants, languages and distribution formats.
In Calenco, it rests on three inseparable elements: modules stored only once, documents that reference them instead of copying them, and layouts applied automatically at publication time. Together, these make it possible to correct information in one place and see the change propagate everywhere it is used.