Repository navigation
feat: attribute docs Discord entry links by placement - #300
Merged
Merged
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
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
Discord entry requests need to distinguish the docs placement readers selected.
User Impact
Header, sidebar, footer, homepage, and invitation links keep opening the community through the first-party Discord redirect. Official support continues to use community.openclaw.ai.
Why This Change Was Made
Use registered placement tags without introducing acquisition UTMs, while preserving the existing Discord social-selection analytics contract. Only the canonical renderer and its checks change, not mirrored English content or generated translations.
Evidence