Skip to content

feat(docs): make official support discoverable across the site - #280

Merged
hannesrudolph merged 2 commits into
mainfrom
hannes/official-support-20261020
Oct 20, 2026
Merged

hannesrudolph merged 2 commits into
mainfrom
hannes/official-support-20261020

Conversation

@hannesrudolph

@hannesrudolph hannesrudolph commented Oct 20, 2026 •

Copy link
Copy Markdown
Member

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/openclaw and sync downstream; no generated docs/**, translations, hosting or dependency changes are included here.

Evidence

  • npm test: 290 passed, 0 failed.
  • Focused preview, home-layout and community-invite tests: 32 passed, 0 failed. The new support assertion failed against the baseline before implementation, then passed.
  • npm run docs:build:preview -- --page help --page help/faq: passed, bounded 30-page English preview.
  • git diff --check: passed.
  • Browser checks on the candidate: light/dark desktop and mobile, visible/focusable mobile Support link, exact forum URL, no horizontal page overflow, and retained article support after navigating from Help to FAQ.
  • Completed pinned local ClawSweeper review of 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.
  • CI follow-up: reproduced the existing header keyboard-order failure, included Support in the tab order and checked its exact URL. The same header visual check now passes across eight widths, including mobile-drawer and social hit-target/overlap checks. No production bytes changed in the follow-up; no executable cases added. Syntax and diff checks pass. The final full range was re-reviewed before this update.
  • Full publishing/translation/R2 build was not run for this bounded shell change. Existing CI smoke now checks all support placements.

Desktop before and after

Before: docs header and sidebar without a labeled support route
After: persistent Support in the docs header and sidebar

Mobile drawer before and after

Before: mobile documentation navigation without Support
After: Support at the top of the mobile navigation drawer

Article-end support handoff

After: official support handoff remains distinct from source feedback and social links

No merge or deployment is requested by this PR.

@hannesrudolph
hannesrudolph requested a review from a team as a code owner October 20, 2026 21:56
@hannesrudolph
hannesrudolph merged commit d0e3e14 into main Oct 20, 2026
4 checks passed
@hannesrudolph
hannesrudolph deleted the hannes/official-support-20261020 branch October 20, 2026 23:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant