Replicate specific section of the article / Content reuse
backlog
Kesavan M
The customer is looking for a feature that allows creating a parent document that combines content from other articles—either entire documents or specific parts—and ensures any updates to the original content are automatically reflected in the parent document. This is especially important for generating documents like legal exports, where accuracy and consistency are critical.
Current Workarounds Explored:
Tags (not suitable for embedding content)
Variables, Snippets, Glossary terms (helpful but limited)
iFrame (not suitable for export)
Replicate Article (cannot combine multiple sources or partial content)
Looking for a structured way to reuse article blocks or tagged sections within another document, with export and sync support.
Log In
m
mehak saeed
Adding to what Kesavan M mentioned:
From a technical writing perspective, having the ability to replicate specific sections of content and reuse them across multiple articles, with automatic syncing, is going to solve so many content consistency issues especially when keeping track of all possible areas to update content is complicated.
For example,
- Configuration processes can be identical for the first several steps, but branch into separate workflows based on user selection. Say, the steps 1–5 to connect to an identity provider may be the same for SAML and OIDC integration, but after that, the steps diverge. Maintaining a shared block for the initial steps and separate blocks for the remaining steps would prevent maintenance errors.
- In products that support multiple deployment models (such as Cloud, On-Prem, FSA), some instructions, like initial commands, prerequisites, or basic configuration, are identical, but later steps vary.
In large knowledge bases with hundreds or thousands of articles, the absence of structured content reuse means writers must manually track and update multiple instances of the same information, a process that is prone to human error and likely to cause inconsistencies or outdated content.
Considering Document360 is also meant for big enterprises, not only small scale businesses, please reconsider this FR.
D
D360 Product Management
backlog
Mohamed Shakheen
Hi @victor Kesavan M
Thank you for outlining this requirement in detail.
We understand the need for a dynamic parent document that can combine content from multiple articles or specific sections, while maintaining synchronization with the source content. This is especially critical for use cases like legal documentation, where accuracy, version control, and consistency are non-negotiable.
We’ve reviewed the current workarounds (Tags, Variables, Snippets, Glossary, iFrames, and Replicate Article), and we agree that none offer the full functionality needed - particularly when it comes to structured reuse, partial content embedding, and maintaining live sync with export support.
At this time, this capability is not on our current roadmap. However, given the complexity and high-value use cases this could unlock, we will be tracking customer demand closely and prioritizing accordingly based on traction.
We truly appreciate your detailed input - it’s instrumental in shaping the evolution of our content management capabilities.
Kesavan M
++victor andersson