Cross-Platform Content Reuse
Approved
#3383
Story Statement
As a content strategist, I want content to be easily reusable across products and platforms so that we can publish consistent information without manual copying.
Business Value
- Lowers authoring cost through higher content reuse.
- Improves consistency across platforms and product lines.
- Reduces translation cost of duplicated / similar content.
- Shortens time-to-publish for updates and variants.
Acceptance Criteria
- Given content is shared across products, when source content changes, then dependent reuse references can be updated without duplication.
- Given authors create new outputs, when reuse options are selected, then existing approved components can be referenced directly.
- Given reused content is tracked, when teams review usage, then reuse relationships are visible and manageable.
Topic-to-Topic Linking (Authoring in CCMS)
Approved
#3368
Title: Create and manage topic-to-topic relationships in CCMS Story Statement:
As a Content Engineer, I want to create and maintain links between topics (including many-to-many and reciprocal links), so that related content is explicitly connected and discoverable in the CCMS
Business Value: Restores/modernizes relationship-table capability. Improves navigation and reuse across related topics. Reduces manual tracking of topic relationships.
Acceptance Criteria
- Given an author links topic A to topics B and E, when changes are saved, then all relationships are persisted and visible in the CCMS.
- Given relationships are configured, when validation runs, then the system supports or rejects them according to defined business rules with clear feedback.
- Given users view a topic relationship list, when the topic is opened, then inbound and outbound links are traceable and accurate