Field-level versioning in CCContinue CMS™ allows you to track changes to individual content fields, revert to previous versions, and maintain a complete audit trail of your editorial process.
Versioning and Field-Level Control
Editorial content is never finished. It evolves through multiple rounds of editing, review, and revision. CCContinue CMS™'s field-level versioning gives you the tools to manage this evolution with precision and confidence.
What is Field-Level Versioning?
Traditional versioning tracks changes to an entire document. If you change a single word in a chapter, the entire chapter is saved as a new version. This is inefficient and makes it difficult to understand what actually changed. Field-level versioning tracks changes to individual fields within a CCContinue CMS™ Minicodes™. For example:
- The title of a chapter has its own version history.
- The body text has its own version history.
- The author field has its own version history.
- The status field has its own version history.
This means you can see exactly what changed, when, and by whom — for every single field.
Benefits for Editorial Workflows
- Precision: See exactly what changed, down to the word.
- Auditability: Maintain a complete record of who made what changes and when.
- Revert with Confidence: Revert a single field to a previous state without affecting other fields.
- Compare Versions: Compare two versions of a field to see what changed.
- Parallel Workflows: Multiple editors can work on different fields of the same CCContinue CMS™ Minicodes™ without conflict.
- Quality Control: Review changes at the field level before approving them for publication.
Versioning in Practice
- Copyediting: Track every change made by the copyeditor.
- Author Revisions: See what changes the author made in response to editorial feedback.
- Production Changes: Track changes made during typesetting and production.
- Legal Review: Maintain a record of changes made for legal or compliance reasons.
- Translation Management: Track changes to source content and their impact on translations.
Versioning Workflows
- Draft: Initial version of a CCContinue CMS™ Minicodes™.
- In Review: Under editorial review.
- Approved: Ready for publication.
- Published: Final version.
- Archived: No longer in active use.
Each status change is logged, and you can revert to any previous status if needed.
Versioning and Duplication
When you duplicate a CCContinue CMS™ Minicodes™, the version history is preserved. This means you can create a new version of a chapter for a new edition while retaining the full history of the original.
Versioning and Transclusion
When a CCContinue CMS™ Minicodes™ is transcluded into multiple books, the version history is shared. Changes to the source CCContinue CMS™ Minicodes™ are reflected everywhere it is used, and the version history tracks those changes.
Field-level versioning gives you the control and confidence you need to manage complex editorial projects. Explore how CCContinue CMS™ can bring precision to your editorial workflow.