Description:
As DevPath-Web scales with massive, multi-node learning paths, navigating the platform exclusively via mouse clicks becomes tedious for developers and breaks standard web accessibility (A11y) practices. Currently, there is no quick global navigation option (like a command palette shortcut or structural navigation via keypresses).
Describe the solution you'd like
Introduce a centralized global keyboard shortcut engine (using native React listeners or a lightweight utility like react-hotkeys-hook) inside the core Next.js client layout layer.
The initial mapping sequence should support:
Cmd + K / Ctrl + K: Automatically trigger focus/open on the Global Search platform bar.
Escape (Esc): Instantly close open modals, side drawers, sliding interactive windows, or active UI overlay cards.
ArrowRight / ArrowLeft: Move forward or backward between interconnected sequentially structured learning nodes on active roadmap panels.
Describe alternatives you've considered
Leaving the platform purely pointer-driven, which decreases the Developer Experience (DX) and hurts the accessibility audit scores of the platform.
Proposed Implementation Steps:
Create a custom reusable hook useKeyboardShortcuts or setup a centralized listener matrix in the root provider.
Bind action callbacks cleanly without intercepting native input typing contexts (ensure shortcuts are ignored if input fields or textareas are focused).
Append a subtle keyboard shortcuts hint legend modal/tooltip somewhere accessible on the dashboard wrapper.
Description:
As DevPath-Web scales with massive, multi-node learning paths, navigating the platform exclusively via mouse clicks becomes tedious for developers and breaks standard web accessibility (A11y) practices. Currently, there is no quick global navigation option (like a command palette shortcut or structural navigation via keypresses).
Describe the solution you'd like
Introduce a centralized global keyboard shortcut engine (using native React listeners or a lightweight utility like react-hotkeys-hook) inside the core Next.js client layout layer.
The initial mapping sequence should support:
Describe alternatives you've considered
Leaving the platform purely pointer-driven, which decreases the Developer Experience (DX) and hurts the accessibility audit scores of the platform.
Proposed Implementation Steps: