Repository navigation
feat(docs): make official support discoverable across the site - #280
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
Docs readers do not have a clearly labeled official support route in persistent navigation, the mobile drawer, or the end of an article.
User Impact
Readers can choose Support or Get support to reach https://community.openclaw.ai/, OpenClaw's official support pathway, without relying on the temporary social invitation.
Why This Change Was Made
The shared renderer adds support discovery in the desktop header, desktop/mobile sidebar, footer and article-end handoff. Existing documentation, source feedback, GitHub issue reporting, social Discord and Ask Molty remain intact. The callout is excluded from the search body so it does not dominate unrelated results.
This PR owns website rendering only. English help and FAQ changes belong in
openclaw/openclawand sync downstream; no generateddocs/**, translations, hosting or dependency changes are included here.Evidence
npm test: 290 passed, 0 failed.npm run docs:build:preview -- --page help --page help/faq: passed, bounded 30-page English preview.git diff --check: passed.dcae1d62aa950846332d429e0b83028cdbd18811..6a2cae78965d1072bf0021ccc9161f9e00357616: checkout verified, no actionable correctness or security findings. Its missing-proof note is addressed by the independently captured browser checks and images below; this is not a merge approval.Desktop before and after
Mobile drawer before and after
Article-end support handoff
No merge or deployment is requested by this PR.