Repository navigation
fix: attribute official Discord links in rendered docs articles - #301
Merged
Merged
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What Problem This Solves
Translated docs article links still bypass placement attribution even though the shared Discord navigation is tagged.
User Impact
Official plain Discord invite links in rendered articles use the first-party redirect with the canonical page placement, independently of language. Link text, support wording, code examples, event-specific invitations, and generated source content stay unchanged.
Why This Change Was Made
Apply the migration in the canonical article HTML renderer after its cache, rather than rewriting mirrored English or generated translations. FAQ, updating, and building-plugins use fixed page tags; other official article contexts use the registered generic docs tag.
Evidence