Skip to content

[Tracking] PRD 4: Nested Navigation and Command Palette #11

Description

@Vonng

Tracks PRD 4 delivery across the OINK theme and its consumer regression site.

Product constraints

  • Hugo Menu remains the global-navigation authority.
  • The Hugo content tree / existing docs nav remains the sidebar authority.
  • The root switcher remains the product/domain switcher.
  • The local search index becomes the shared discovery and command entry point.
  • No second docs.json / navigation.yaml information architecture.
  • Offline operation, language-separated indexes, CJK substring matching, and zero telemetry remain hard requirements.

Work breakdown

Dependency graph

#12 Contract
 ├─> #13 Runtime ─┬─> #14 Navbar
 │                         ├─> #16 Search ─┐
 │                         └─> #17 Actions ├─> #18 Palette
 └─> #15 Sidebar                    ┘
          Navbar + Sidebar + Palette ─> consumer regression ─> #19 release gate

The runtime issue is intentionally two PRs (asset isolation, then surface coordination). The consumer issue is intentionally two PRs (navigation/sidebar, then search/Palette).

Epic exit criteria

  • Flat menus remain compatible.
  • Nested desktop and mobile navigation are keyboard and screen-reader operable.
  • Search metadata, boosts, groups, and CJK paths are covered by deterministic tests.
  • Page actions and Palette commands share one registry.
  • Disabling local search emits no Palette runtime or local index.
  • EN/ZH, subpath, home/docs/blog/project roots, shell, print, and external-link behavior pass consumer regression.
  • No default telemetry request is introduced.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestprd4PRD 4: nested navigation and Command Palette

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions