Weave Code
Admin Ui Bundle Laravel Package
elasticms/admin-ui-bundle
Laravel admin UI bundle for building ElasticMS back-office screens fast. Provides ready-made layout, navigation, forms, tables, and common CRUD components with configurable styling and assets, streamlining integration into existing apps.
Admin ui bundle for elasticms
Frequently asked questions about Admin Ui Bundle
- Can I use elasticms/admin-ui-bundle without ElasticMS for a custom Laravel admin panel?
- The bundle is designed for ElasticMS integration, but you can cherry-pick reusable UI components like tables, forms, or navigation menus if your project shares similar needs. However, core functionality (e.g., media management, content CRUD) relies on ElasticMS services, so extraction requires careful dependency isolation.
- What Laravel versions does elasticms/admin-ui-bundle support?
- The bundle is optimized for Laravel 10+ and PHP 8.2+, though explicit versioning isn’t documented in the repo. Test compatibility by reviewing `composer.json` constraints and checking for ElasticMS-specific dependencies, which may introduce hidden version requirements.
- How do I customize the admin layout to match my brand?
- Override the bundle’s Blade templates in `resources/views/ems_admin/` to modify layouts, colors, or branding. Use Laravel’s view composers or service providers to inject custom logic. The bundle supports extensible theming via CSS variables and modular components.
- Does this bundle work with Livewire or InertiaJS for dynamic admin interfaces?
- The bundle assumes Blade for server-side rendering and Vue 3 for dynamic components. For Livewire/InertiaJS, you’ll need to wrap components in a shared layer or create custom adapters, as the bundle doesn’t natively support these frameworks.
- What are the alternatives to elasticms/admin-ui-bundle for Laravel admin panels?
- Consider FilamentPHP (modular, API-first), Backpack for Laravel (CRUD-focused), or Nova (Laravel’s official admin panel). These alternatives offer broader Laravel compatibility and less ElasticMS coupling, though they may require more setup for CMS-specific features.
- How do I handle authentication/authorization with this bundle?
- The bundle integrates with Laravel’s built-in auth (e.g., Sanctum, Passport) but may include ElasticMS-specific role/permission logic. Audit the bundle’s `AuthServiceProvider` or middleware to ensure compatibility with your existing auth system.
- Will this bundle slow down my Laravel application in production?
- The bundle adds minimal overhead if used selectively (e.g., only for admin routes). Profile performance by disabling unused components and checking for redundant queries in ElasticMS services. Optimize with Laravel’s route caching and Blade compilation.
- Can I test the bundle in a staging environment before full integration?
- Yes. Fork the repo, install it in a Laravel 10+ instance with ElasticMS (`composer require elasticms/elasticms`), and test core features like content CRUD, media uploads, and navigation. Compare it against alternatives like FilamentPHP for setup time and flexibility.
- How do I extend the bundle to add custom admin sections or workflows?
- Use Laravel’s service providers to register custom routes, controllers, or middleware. Extend the bundle’s navigation system via the `ems_admin.navigation` event or override its `MenuBuilder` class. For complex workflows, integrate with Laravel’s task scheduling or queues.
- What happens if ElasticMS updates and breaks compatibility with this bundle?
- Monitor ElasticMS’s changelog for breaking changes, especially in its core services (e.g., media, content). The bundle’s modular design allows partial overrides, but full ElasticMS migrations may require refactoring. Document dependencies early to isolate risks.
Weaver
How can I help you explore Laravel packages today?