- What is eekes/sulu-admin-ux-bundle?
- It is a Composer package that adds user-experience improvements to the Sulu 3 administration interface. It ships as a Sulu bundle built on Symfony, so it plugs into the Sulu admin rather than into a Laravel application. Check the README on GitHub for the exact list of UX tweaks it provides in the current release.
- Is this package for Laravel or for Symfony/Sulu?
- It is a Symfony/Sulu bundle, not a Laravel package. Sulu 3 runs on Symfony, and the bundle hooks into the admin UI layer there. You can still pull it in with Composer, but there is no Laravel service provider, facade, or config file to publish.
- How do I install eekes/sulu-admin-ux-bundle?
- Run composer require eekes/sulu-admin-ux-bundle in your Sulu 3 project. Then register the bundle in your Symfony bundle configuration, typically config/bundles.php, and clear the cache. If the bundle ships admin assets, rebuild them with your usual Sulu admin build command.
- Which Sulu versions does this bundle support?
- The package targets the Sulu 3 admin, so it is not intended for Sulu 1.x or 2.x projects. Always confirm the exact constraint in the package's composer.json before upgrading Sulu. If you are still on Sulu 2, you would need to migrate first or look for an alternative.
- Do I need to configure anything after installing?
- Configuration is likely minimal, since the bundle's purpose is to adjust admin behaviour and presentation out of the box. Review the README for any bundle-level options or asset-build steps that apply to your setup. After registering it, clear the Symfony cache and reload the admin to confirm the changes appear.
- Will this bundle change the frontend of my website?
- No. It is scoped to the Sulu admin interface, so the public-facing website rendering should be unaffected. Any visible difference should be limited to editor screens, admin navigation, or other back-office UI elements. Still smoke-test key pages after deploying in case admin-side templates overlap with your own customisations.
- Does it break my existing Sulu admin customisations?
- It can interact with admin templates or JavaScript you have already overridden, so test on a staging environment first. Compare the admin screens you have customised before and after installing the bundle. If something conflicts, check the bundle's views for override points or open an issue on the repository.
- What should I watch out for in production deployments?
- Treat it like any Symfony bundle change: run composer install with the lock file, rebuild admin assets as part of your deploy pipeline, and clear the cache. No database migrations are expected from a UX-focused bundle, but confirm that in the README. Because it affects editor workflows, do a quick manual check of the admin after the first production deploy.
- What alternatives exist for improving the Sulu admin UX?
- You can override admin templates and styles yourself, write a small custom Sulu bundle, or use community admin plugins for specific features. This bundle is convenient when you want a ready-made set of small improvements instead of maintaining your own overrides. Compare the feature list in the README against your needs before adding another dependency.
- Is this bundle actively maintained and how can I contribute?
- Activity is best judged by the releases, commits, and open issues on the GitHub repository at eekes/sulu-admin-ux-bundle. Since it is a small, focused package, check that its Sulu version constraint matches your project before relying on it. Bug reports and pull requests are usually welcome via the repository's issue tracker.