ADSDEV-2383: add support to OnwardJourneyLink #111
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
todor-videv1
requested changes
Oct 9, 2025
There was a problem hiding this comment.
issue: As already mentioned in Slack, the preferred approach from C&M side would be to incorporate the data-asset-style attribute as an actual attribute on the existing Link node. This is ideal in terms of the future transformations that need to happen so we can support a smooth transition away from the Internal Content API and start using Content Tree instead of XML.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Anchor tags can include the
data-anchor-styleattribute to identify an onward journey link that appears exclusively on partner content articles. As we don't expect this variation to appear in standard articles, we've implemented it as a separate component within the content tree