Weave Code
Filament Bookmarks Menu Laravel Package
tomatophp/filament-bookmarks-menu
A Filament plugin that adds a bookmarks menu to your admin panel, letting users save and quickly revisit favorite pages, resources, and records from a convenient header dropdown.
Add bookmarks and tags to your resources records and access theme form your sidebar
Frequently asked questions about Filament Bookmarks Menu
- What is tomatophp/filament-bookmarks-menu used for?
- It is a Filament plugin that lets users save and quickly revisit favorite pages, resources, and records from a header dropdown or sidebar menu. It also adds bookmark folders, links, tags, and navigation to your Laravel admin panel. It is useful for internal resource curation, knowledge bases, and dashboard shortcuts.
- How do I install filament-bookmarks-menu in a Laravel app?
- Install it with Composer using tomatophp/filament-bookmarks-menu, then publish the package config and migrations as directed by the package. Register the plugin in your Filament panel provider and run migrations. Confirm your Laravel and Filament versions match the package requirements before installing.
- Which Laravel and Filament versions does this package require?
- The release notes require Filament v5 and Laravel 12 or 13. Teams on Filament v3 should use the package's v3 branch instead. Confirm the exact PHP version and dependency constraints from the package's composer.json before adopting it.
- Is this package compatible with Filament v4 or v3?
- v5.0.0 targets Filament v5, while Filament v3 users should stay on the v3 branch. Compatibility with Filament v4 is not explicitly confirmed; the release notes mention fixing a v4 install error, but that does not clearly state full v4 support. Confirm v4 compatibility with the maintainer before adopting v5.0.0 on a Filament v4 application.
- How do I register the bookmarks plugin in a Filament panel provider?
- Register the plugin in your Filament panel provider, typically inside the panel configuration method, following the package documentation for the exact plugin class and namespace. After registration, publish and run any required migrations and configuration. Then verify that the bookmarks menu appears for the intended users.
- Are bookmarks and private folders visible only to their owner?
- Private folder visibility is enforced at the query and action level according to the technical evaluation, which is important for multi-user environments. Because privacy logic is security-sensitive, you should test private folder access with multiple user roles in staging before rolling out. Monitor for regressions after upgrades.
- Can users organize bookmarks with folders and tags?
- Yes. The package adds bookmarks and tags to resource records and provides folder-based organization and sidebar navigation. Users can save favorite pages, resources, and records and revisit them from the bookmarks menu. The redirect behavior sends users to the first visible folder or the panel home when needed.
- What are the breaking changes when upgrading from v4.x to v5.0.0?
- No explicit breaking-change list is provided in the available information, but v5.0.0 is a major version bump tied to Filament v5, so treat it as potentially breaking. Review the changelog, run the upgrade in staging, and test private folder visibility, link removal, and redirect behavior. No official upgrade guide is mentioned, so confirm details with the maintainer if needed.
- Does filament-bookmarks-menu support multi-tenant or team-based scoping?
- Multi-tenant or team-based scoping is not documented in the provided evaluation. Private folder visibility is enforced at the query and action level, but that does not confirm tenant or team isolation. Ask the maintainer directly before relying on the package in a multi-tenant application.
- Is the package actively maintained and how should I test it in production?
- The package is active, with a recent release and a new test suite that lowers integration risk. Support relies on open-source GitHub issues, and no commercial support is mentioned. Test in staging first, run migrations, verify private folder access and redirects, and monitor for privacy or performance issues after rollout.
Weaver
How can I help you explore Laravel packages today?