- Can I use this package in a standard Laravel project without AlphaLemon CMS?
- No, this bundle is tightly coupled with AlphaLemon CMS. For Laravel-only projects, you’d need to rebuild its menu logic (e.g., using Spatie’s menu packages or custom Eloquent models) or create a proxy layer, which adds significant effort. Evaluate alternatives like `spatie/laravel-menu` if AlphaLemon isn’t already in your stack.
- What Laravel versions does this bundle support?
- While built on Laravel, the bundle relies on AlphaLemon CMS internals, not Laravel’s native features. Check the package’s `composer.json` for PHP/Symfony version constraints (likely PHP 8.x and Laravel 8.x–10.x via Symfony compatibility). Test thoroughly, as direct Laravel integration isn’t guaranteed.
- How do I install and configure this in AlphaLemon CMS?
- Run `composer require alphalemon/app-business-menu-bundle`, then follow AlphaLemon’s app installation docs (likely involves registering the bundle in `config/bundles.php` and running migrations). The bundle should auto-configure its content type and editor UI. Check the GitHub repo for CMS-specific setup steps.
- Does this bundle support multilingual menus or dynamic nesting?
- The bundle’s capabilities depend on AlphaLemon CMS’s core features. Review the AlphaLemon documentation or test the bundle’s editor to confirm support for multilingual menus, nested items, or dynamic rules. If missing, customization may require modifying the bundle’s source or building extensions.
- What’s the maintenance status of this package? Is it actively updated?
- The package has no stars or dependents and relies on `dev-master`, indicating low community adoption. Check the GitHub repo for recent commits or contact the maintainers to confirm long-term support. For production use, consider forking or building a maintained alternative.
- How does caching work in this bundle? Will it impact performance?
- The bundle likely uses AlphaLemon’s caching layer (e.g., Doctrine cache or Symfony’s HTTP cache). Test under load to measure overhead, especially if menus are frequently updated. Poor caching could degrade performance at scale; consider adding Laravel’s cache drivers (Redis/Memcached) if needed.
- Are there Laravel-native alternatives to this bundle?
- Yes. For standalone Laravel projects, consider `spatie/laravel-menu` (simple nested menus), `orchid/navigation` (admin-friendly), or custom solutions with Eloquent + Blade. These avoid AlphaLemon’s dependencies and integrate natively with Laravel’s ecosystem. Compare features like editor UIs and caching.
- Can I customize the menu editor UI without modifying the bundle’s source?
- Customization depends on AlphaLemon’s templating system (likely Twig). Override Twig templates in your project’s `templates/` directory or extend the bundle’s admin panel via AlphaLemon’s hooks. Deep UI changes may require forking the bundle or building a wrapper.
- Does this bundle include database migrations, or do I need to write my own?
- The bundle should auto-migrate its database schema when installed via Composer. For non-AlphaLemon systems, you’d need to manually adapt the schema or reverse-engineer the migrations from the bundle’s source. Check the `migrations/` directory in the package for details.
- How do I handle menu items with attached media (images, icons) in this bundle?
- Media handling depends on AlphaLemon’s asset management system. If you need Laravel-native features (e.g., Spatie Media Library), you’ll need to either integrate a third-party package into the bundle or rebuild the media logic separately. Test the bundle’s editor to confirm supported file types and storage backends.