Skip to content

feat(pagebar): add '?' guide affordance + per-page tutorial drawer#1150

Open
psdjungpulzze wants to merge 1 commit into
mainfrom
feat/page-guide-affordance
Open

feat(pagebar): add '?' guide affordance + per-page tutorial drawer#1150
psdjungpulzze wants to merge 1 commit into
mainfrom
feat/page-guide-affordance

Conversation

@psdjungpulzze

Copy link
Copy Markdown
Contributor

What

Adds a ? guide affordance to the right side of the standardized PageBar and a per-page tutorial presentation component — a right-hand slide-over drawer that renders page-specific how-to content.

Changes

  • GuideContent model (page-registry.ts): intro sentence + ordered steps (each { heading, body }), plus a PageMeta type and a PAGE_META registry keyed by page segment.
  • resolvePageMeta(pathname) resolves guide content for the active page. Segment resolution is factored into resolvePageSegment, which inferTitle now reuses so the title and guide always agree on the active page.
  • PageGuide (page-guide.tsx): a ? button + slide-over drawer built on Radix Dialog — keyboard-accessible open/close (Esc, focus trap, restored focus) for free. Reuses the existing side-sheet slide-over pattern and the guided-tour visual language (green accent bar, numbered steps) with design-system styling.
  • PageBar renders the ? only when authored guide content exists; pages without a guide hide the affordance entirely (graceful empty case).
  • Authored guides for a representative set of core pages (dashboard, my-tasks, phases, sprints, roadmap, drift, flags, change-requests, approvals, sow, discussions, feedback, ai); other pages simply have no guide yet.

Testing

  • npm run typecheck
  • eslint on changed files ✅

Agent config

No PM Agent update needed — this is a UI help affordance and does not add tools or change agent-visible domain data/workflows.

🤖 Generated with Claude Code

Add a help affordance to the standardized PageBar that opens a right-hand
slide-over drawer with page-specific tutorial content.

- Define the GuideContent model (intro + ordered heading/body steps) and a
  page metadata registry resolved via resolvePageMeta(pathname).
- Factor segment resolution into resolvePageSegment so the title and guide
  always agree on the active page; inferTitle now reuses it.
- Build PageGuide on Radix Dialog (Esc/focus-trap keyboard accessible),
  reusing the existing side-sheet slide-over and guided-tour visual language.
- Hide the '?' when no guide content exists for the page.

No agent config update needed: this is a UI help affordance and does not add
tools or change agent-visible domain data/workflows.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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