Filament Palette Laravel Package

Product Decisions This Supports

• Admin UX roadmap: The palette is a single, low-effort surface for power-user navigation (jump to resources, run commands). v2.3’s optional global-search records extend it into a lightweight “find anything” launcher, which can reduce clicks and context-switching for support, ops, and content teams.
• Build vs. buy: For Filament-based admin panels, adopting this package is usually cheaper than building and maintaining a custom command palette. The new record-search capability is a feature you would otherwise scope, design, and QA as a separate increment.
• Feature flagging and rollout: The new capability is off by default and configurable (global_search_results_limit, global_search_debounce_ms). This supports a staged rollout: enable internally, smoke-test the client-side behavior, then expose to power users before broad production use.
• Scope control: Because record search depends on an existing global search provider and is a debounced $wire round-trip, it is best treated as an enhancement to existing search, not a replacement for dedicated search/indexing. That helps keep roadmap expectations realistic.
• Use cases: rapid navigation across resources; running common admin commands; locating records by name during support or operations workflows; reducing dependency on menu depth in large panels.

When to Consider This Package

Consider it when:

• You are building or maintaining a Filament admin panel and want a command-palette-style launcher without custom development.
• Your users are repeat/internal operators who benefit from keyboard-driven navigation and fast access to commands.
• You already have a global search provider configured on the panel and want to optionally surface matching records in the palette.
• You can smoke-test new client behavior in a staging panel before enabling it for production users.
• You want the record-search enhancement to be opt-in and tunable rather than mandatory.

Look elsewhere or defer when:

• You are not using Filament, or your admin surface is not a Filament panel.
• You need deeply customized search relevance, indexing, permissions-aware result filtering beyond what the panel’s global search provides, or a full search product.
• You cannot validate the new client-side record-fetch behavior before production, or you have strict performance/UI stability requirements and prefer to wait for broader field validation.
• You need a guaranteed stable admin UX with no new client-side interactions; keep the feature disabled until tested.
• The package’s compatibility with your Filament/Laravel versions is unverified.

How to Pitch It (Stakeholders)

For executives: This is a small, optional enhancement to our Filament admin panel that makes it faster for internal teams to find records and run common actions from one keyboard-driven surface. The new record-search capability is off by default, so there is no change for existing users unless we explicitly enable it. The main cost is a short smoke-test in staging; the upside is less navigation friction and a more efficient admin experience without building a custom palette.

For engineering: v2.3.0 adds opt-in global-search records to the existing command palette. It uses a debounced $wire round-trip and is controlled by include_global_search_results, global_search_results_limit (10), and global_search_debounce_ms (300). No breaking changes are indicated. Upgrade is a minor Composer bump. Because the record-fetch UI is new client behavior, validate it in a panel before enabling in production; keep the feature flag off by default until tested.