Under Community Review

Improve Change Tracking (Change Markup) in SDL Tridion Docs

The user group created a "task force" to revisit improving change tracking for SME reviewers. We defined which changes we would like to see marked up, and how we would like them to be formatted. I am attachingChange Tracking Requirements_June29meeting.xlsx the meeting notes for our meeting with SDL from July. We would like SDL to improve the way change tracking in handled in the product (potentially with a 3rd party tool like Delta XML and PS engagement... ). The current OOTB mark-up has been a sort spot for users for quite a while.

Parents
  • Both oXygen and XMetaL provide change tracking. Were the change tracking features of those tools and the processing instruction markup that they use a consideration? I would very much prefer SDL to non re-invent a new set of change tracking markup but to instead use or partner with the Authoring tool companies. We really would like to have the change tracking work across the tool stack and not just in SDL tools.

Comment
  • Both oXygen and XMetaL provide change tracking. Were the change tracking features of those tools and the processing instruction markup that they use a consideration? I would very much prefer SDL to non re-invent a new set of change tracking markup but to instead use or partner with the Authoring tool companies. We really would like to have the change tracking work across the tool stack and not just in SDL tools.

Children
No Data