Idea Delivered Partially

Syntax highlighting for rich text is included in Experience Space in SDL Tridion Sites 9.5.

This newer interface is focused on daily editorial actions and will not include source view tabs for the other items requested. These XML-based views might be considered in a future update, though we might instead consider showing different versions or even formats for the existing XML data.

Syntax highlighting

I wrote an extension for syntax highlighting but I'm really bad at keeping it updated.

Ideally I would like to see syntax highlighting and working TAB key wherever there is Razor, XML or HTML displayed.

  • Component Source tab
  • RTF source tab
  • Schema source tab
  • Component template source tab
  • TBB source tab (Razor, XSLT)
  • etc

This would give HTML savvy editors a better experience and also make it easier for developers to debug or change the source of items with less margin for error.

Parents
  • We would appreciate examples of when the source tabs are useful to editors or implementers.

    For example, do users manipulate or change the XML directly? And if so, do customers want to encourage or limit such behavior? :-)

    Do you copy and use this data elsewhere?

    And is it the XML that's particularly interesting or the identifiers, structure, or something else?

    And in this process, are there pros or cons related to the source (e.g. XML namespaces, paths, ability to see Content and Metadata XML, etc.)?

Comment
  • We would appreciate examples of when the source tabs are useful to editors or implementers.

    For example, do users manipulate or change the XML directly? And if so, do customers want to encourage or limit such behavior? :-)

    Do you copy and use this data elsewhere?

    And is it the XML that's particularly interesting or the identifiers, structure, or something else?

    And in this process, are there pros or cons related to the source (e.g. XML namespaces, paths, ability to see Content and Metadata XML, etc.)?

Children
No Data