How do <TCDL>
tags work with the GraphQL-based Content Delivery API(s)?
I understand historically customer Content Management code and/or the Default Building Blocks would transform Component links in Component fields or rich text format areas to the appropriate platform-agnostic <tcdl>
markup.
And depending if you're developing for .NET or Java, the appropriate attribute would be added (either in templating or publishing). Mainly 'runat="server"' was added for .NET.
Later we had REL, as a more platform agnostic version of TCDL.
Questions:
- With GraphQL, does
TCDL
still apply? - Or perhaps, it's better to ask can it still apply if using rendered/raw content?
- If so, can we still create custom TCDL tags? I can see the documentation for Sites 9.1, but not later versions.
- And does TCDL behavior differ between data pipeline (template-less) content or the Sites 9.6 semantic content modeling?
For background, I mentioned custom TCDL tags in this answer https://tridion.stackexchange.com/a/21797/46 but didn't know if this is still possible in recent versions, or even recommended going forward.