Filament Keyboard Shortcuts Laravel Package

Product Decisions This Supports

• Keyboard-first admin as a deliberate product bet. The package now has a coherent power-user surface: chord shortcuts (g c u), a hint mode that reveals available letters, a shortcuts sheet with searchable combos, and a live "keys typed so far" pill. That's a discoverable, learnable system rather than a hidden set of incantations — which is the difference between a feature a few engineers use and one that shifts how a whole ops team works. This is the data point that moves "keyboard navigation" from nice-to-have to a scoped initiative.
• Build vs buy for command/navigation UX. Chord parsing, prefix ambiguity resolution, hint badges, RTL mirroring, dark mode, reduced-motion fallbacks, and screen-reader announcements are each individually small and collectively a multi-sprint build. Adopting keeps that surface as a dependency you configure (->navigationHints(false)) rather than code you own and maintain through every Filament upgrade.
• Onboarding and time-to-productivity for internal tools. New hires in support, ops, or back-office roles live in these panels all day; shortcut discovery has historically required tribal knowledge or a wiki page nobody reads. Hint mode plus the grouped, searchable sheet turns that into in-product onboarding — a measurable lever on ramp time and tickets-per-hour.
• Internationalization roadmap. ~25 locales with terminology aligned to Filament's own translations and key labels matched to each locale's keyboard layout is a real signal for teams expanding admin tooling beyond English-first markets. It also de-risks "we'll localize later" by removing a blocker now.
• Accessibility and compliance positioning. Chord exposure via aria-description (with title as a fallback when no tooltip renders) plus a direction-agnostic focus ring is incremental but concrete WCAG-aligned work. Useful when an accessibility audit is on the roadmap and you need cheap wins in the admin surface.
• Scale thresholds for the navigation itself. Two-letter chord fallback built from the label before falling back to digits is the package telling you it has been tested against large, crowded sidebars. That informs whether it's viable for a 60-resource internal platform versus a 6-resource tool.
• Release-management and pinning policy. The aria-modal="true" fix is the single most decision-relevant line in this release: a closed sheet was advertising itself as a modal and silently disabling every Filament key binding on the page, including global search and ->keyBindings(). Anyone who evaluated v0.1.x and saw inexplicably dead keybindings should re-test on v0.2.0, and anyone shipping should pin a minimum version at or above it.

When to Consider This Package

Consider it when:

• You run one or more Filament panels that people use for hours a day, not minutes a week — internal ops, support consoles, back-office tooling, data entry.
• Your users are repeat operators with established workflows who would benefit from muscle-memory navigation, or your panel is large enough that hunting through a long sidebar is the dominant friction.
• Your nav tree is big enough to exercise the two-letter fallback path, or you already have teams asking for a command palette.
• You need multi-locale admin coverage — the breadth of translations here means you're not shipping an English-only interaction layer.
• You have an accessibility commitment (procurement, audit, or public-sector contracts) and want defensible keyboard and screen-reader affordances in the admin surface.
• You want the capability without owning the code: adopting a maintained dependency is cheaper than an in-house shortcut layer that must be re-validated against every Filament release.

Look elsewhere or defer when:

• The panel is customer-facing, touch-first, or mobile-dominant — chords and hint badges assume a physical keyboard.
• The panel is small and shallow (a handful of resources, one or two groups); the discovery overhead outweighs the navigation savings, and the sheet becomes another thing to learn.
• You're not on Filament, or you're on a version whose keybinding and tooltip contracts differ from what this targets.
• You need full modal editing (Vim emulation, operator/motion grammar, text-object editing) — this is navigation-speed tooling, not an editing model.
• Your accessibility bar is screen-reader-first beyond shortcut announcement: verify with your own assistive-tech testing rather than assuming aria-description coverage is sufficient.
• You require a long support track record. This is a 0.x package; the changelog shows meaningful behavioral churn between minors, so budget for upgrade reviews and pin deliberately.

Adoption gate: run it against your largest panel with real users for a sprint, watch whether hint mode gets used unprompted, and confirm no regressions to existing Filament keybindings before rolling out beyond a pilot group.

How to Pitch It (Stakeholders)

For executives (one paragraph): We're evaluating a small, focused add-on for our Filament admin panels that makes them dramatically faster for the people who use them all day. It adds keyboard shortcuts to jump anywhere in the panel, an in-product cheat sheet that teaches them, and a hint mode that shows what's available — so speed comes with discoverability instead of a training doc. It ships with roughly two dozen languages, works in dark mode and right-to-left layouts, and respects reduced-motion settings. The cost is a dependency and a configuration flag, not a build project; the return is measurable time-on-task for ops and support staff, faster onboarding for new hires, and a credible accessibility story for procurement. This release also fixes a bug where the feature could silently disable existing keyboard shortcuts in the panel — so if we trialed an earlier version and found keybindings broken, that was the cause and it's resolved.

For engineering leads: Drop-in Laravel package, no service container surgery. Integration is a plugin registration plus optional per-resource chords via protected static ?string $keyboardShortcut or a public static getKeyboardShortcut(), with one-character or two-character overrides. Hint mode is a single toggle (->navigationHints(false)). Notable engineering signals in this release: JavaScript unit tests and a Playwright end-to-end suite against a Testbench workbench, both running in CI, plus a test that keeps every locale in sync with English — this is a maintainer investing in regression safety, which is the main thing we'd otherwise worry about at 0.x. Two things to schedule: (1) pin a minimum of v0.2.0 and treat the aria-modal fix as a required upgrade if v0.1.x is anywhere near production, since the failure mode was silent global-search and action-keybinding breakage; (2) budget a compatibility check per Filament minor, as the package touches sidebar rendering, tooltips, and modal state.

For the design and accessibility partner: The interaction model is legible and well-considered — chord pills surface partial input, Enter disambiguates prefixes, Esc dismisses immediately, letter badges use the panel font so O and 0 stay distinct, and the focus ring is direction-agnostic rather than an inline-start bar. Motion is gated behind reduced-motion, and it holds up in RTL and dark mode. Worth a short review pass on the sheet's empty-state copy and the column-balancing behavior with our real navigation groups before we commit to a rollout.