Weave Code
Menu Bundle Laravel Package
integrated/menu-bundle
A Laravel bundle for defining, organizing, and rendering application menus, giving you a structured way to manage navigation items and integrate menus cleanly into your PHP project.
Provides MenuEvents to allow adding navigation menu items to the Integrated backend and a database provider to read navigation items from the database (which allows front-end navigation menu editing when used with the website-bundle)
Frequently asked questions about Menu Bundle
- Is integrated/menu-bundle a Laravel package or a Symfony bundle?
- Despite being described as a Laravel/PHP package, integrated/menu-bundle is a Symfony bundle. It uses bundle registration instead of service providers, Symfony event subscribers instead of Laravel listeners, Doctrine instead of Eloquent, and bin/console instead of artisan. In a Laravel codebase that makes it an adapter project rather than a normal Composer install.
- Can I install integrated/menu-bundle in a Laravel app with Composer?
- You can add it with Composer, but it will not work out of the box in Laravel. Expect to build or validate a service-provider bridge, confirm the Symfony and PHP constraints in its composer.json, and own the menu-item schema and migrations. A timeboxed spike is the cheapest way to establish whether the bridge is viable.
- Which Laravel and PHP versions does integrated/menu-bundle support?
- There is no published Laravel support matrix for this bundle. Its Composer constraints are the source of truth for PHP and Symfony versions, and Laravel compatibility is something your team must validate. Check whether installing it pulls Symfony components you do not already run, and test against your target Laravel and PHP versions before committing.
- How do I define nested or hierarchical menu items with integrated/menu-bundle?
- Menus and nested items can be defined in configuration or in code, with flexible labels, URLs, and item attributes. A database-backed provider is also available for persistence, but the package supplies the provider rather than the full editing workflow. You remain responsible for schema design, ordering, nesting depth, validation, and cache invalidation.
- Does integrated/menu-bundle include an admin UI for editing menus?
- No, the package does not give you a complete admin UI for editing menus. It provides a database-backed provider, but the editing surface, authorization on menu edits, validation, and sanitization at render time are yours to build. The related website-bundle may supply front-end editing semantics, but adopting it adds another dependency and tight coupling.
- How does access-based visibility work in integrated/menu-bundle?
- The bundle supports access-based visibility and active-state handling for menu items. In Laravel you will need to bridge your authorization model into whatever access rules the bundle expects and verify the exact contract in source. Also enforce authorization at write time for menu edits and escape output when rendering labels and URLs.
- What is MenuEvents used for in integrated/menu-bundle?
- MenuEvents is an event-based extension seam that lets modules register navigation items instead of editing one central config file. That can reduce merge-conflict load as modules ship, and the contract is framework-agnostic in principle, so it can be bridged through a Laravel service provider. Treat the event payload as a versioned API and test contributors against it.
- Is integrated/menu-bundle production-ready and actively maintained?
- Treat it as high-risk until proven otherwise: it has zero stars, zero dependents, no external docs or tutorials, and no visible production validation. Assume a bus factor of one and an unclear release cadence. The defensible mitigation is to vendor or fork it under your control and treat upstream as a reference implementation, not a live dependency.
- Do I need other Integrated packages such as website-bundle to use this menu bundle?
- The bundle appears to sit inside the wider Integrated suite, and hard coupling to website-bundle semantics is a stated risk. Confirm whether sibling Integrated packages are required at runtime and how tightly versions are pinned. If installing it pulls in packages you would not otherwise accept, that changes the adoption decision.
- What are the best alternatives to integrated/menu-bundle for Laravel menus?
- For Laravel teams, spatie/laravel-menu or a simple menus and menu_items pair are usually lower-risk alternatives. They avoid the Symfony-to-Laravel adapter work and give you a native Eloquent and authorization story. Compare the opportunity cost of building the adapter, schema, admin UI, and caching against adopting a maintained Laravel-first package.
Weaver
How can I help you explore Laravel packages today?