Weave Code
Filament Bookmarks Menu Laravel Package
stafe-group-ab/filament-bookmarks-menu
Add a bookmarks menu to Filament admin panels so users can save frequently used pages and records, then reopen them from a convenient dropdown. Easy to install and configure, it gives each user personalized shortcuts and faster navigation across existing interfaces.
Create global and user defined bookmarks menus for your Filament users.
Frequently asked questions about Filament Bookmarks Menu
- How do I install filament-bookmarks-menu in a Laravel app?
- Install it with composer require stafe-group-ab/filament-bookmarks-menu, then publish and run the package migration and register the plugin in your Filament panel provider. Before running Composer, check that the version constraints resolve against your Filament, Laravel, PHP, and Livewire versions with composer why-not. The package is a thin panel plugin, so installation is quick, but the version check is the gating step rather than an afterthought.
- Does filament-bookmarks-menu support Filament v3 or v4?
- Almost certainly not. The last release was 2023-06-03, which places it in the Filament v2 era, before the v3 plugin API changes. If your estate runs Filament v3 or v4, treat this package as a reference implementation and plan a fork-and-port or internal rebuild instead of a direct dependency.
- What is the difference between global and user-defined bookmarks?
- User-defined bookmarks are saved per user and persisted in the database, so each person builds their own shortcut list. Global bookmarks are defined centrally and exposed to users through the same menu. Be careful with globals in multi-role setups, since a global bookmark can expose navigation to users who should not see that page.
- Will filament-bookmarks-menu work with Laravel 11 or Laravel 12?
- Support is unverified. There has been no release in over a year, so Laravel 11 and 12 compatibility is untested and PHP constraint sets may not resolve in a modern lockfile. Run composer why-not against your target Laravel and PHP versions, then review and test the migration before committing.
- Is filament-bookmarks-menu safe to use in production?
- It is reasonable for a low-stakes convenience feature, but not for anything the business treats as load-bearing. Adoption is low at around 24 stars from a single GitHub org, there is no recent release, and there is no visible signal of ongoing security or compatibility maintenance. If you adopt it, time-box the decision and write an exit criterion with an internal owner.
- How are bookmarks scoped per user, per panel, or per tenant?
- The core model is per-user persisted state stored via the package migration. Per-panel and per-tenant scoping are not verified, so audit the migration and model before using it in a multi-tenant or multi-panel application. Global bookmarks in particular deserve a review for navigation leakage across tenants or roles.
- Should I fork filament-bookmarks-menu or rebuild the feature myself?
- For a Filament v3 or v4 estate, rebuilding is often the better route because the feature surface is small: a model, a migration, a Livewire menu component, and Blade views. Porting it into a local package or an app/Filament module gives you ownership of compatibility and data cleanup. Produce a build-versus-adopt estimate before any composer require is merged.
- How do I clean up stale bookmark data over time?
- Bookmarks are per-user persisted state, so they outlive the package and create retention obligations. Plan a pruning job or admin cleanup for bookmarks that point to deleted records or removed pages. Also confirm the migration supports rollback and fits your zero-downtime migration strategy before deploying.
- Is Livewire 3 compatible with this package?
- Unlikely without changes. Filament v2 pins Livewire 2 while Filament v3 pins Livewire 3, and the Livewire menu component is exactly where that breakage surfaces. Treat the Livewire version as part of your compatibility matrix alongside the Filament major version.
- What are the alternatives to filament-bookmarks-menu?
- There are few direct drop-in alternatives for a Filament bookmarks dropdown, so most teams either implement it internally or adapt an existing navigation or favorites plugin. If bookmarks are a genuine product requirement, owning the code is the safer long-term choice. If they are a nice-to-have on Filament v2, adopting as-is with a written exit criterion is acceptable.
Weaver
How can I help you explore Laravel packages today?