Weave Code
Slider Bundle Laravel Package
enhavo/slider-bundle
Enhavo Slider Bundle is a subtree split of the Enhavo CMS, an open source PHP project built on the Symfony fullstack framework with Sylius components. It adds slider support to the CMS's flexible, data-driven interface. See the main Enhavo repository for docs and more information.
[READ-ONLY] EnhavoSliderBundle
Frequently asked questions about Slider Bundle
- Can I install enhavo/slider-bundle in a Laravel application?
- No, not as a working dependency. It is a Symfony bundle for the Enhavo CMS and relies on Symfony's DI container, Doctrine ORM, Twig, and Enhavo's block, renderer, and admin abstractions, none of which exist in Laravel. Composer may resolve the package, but there is no service provider, no Laravel integration layer, and no way to render its sliders without the Enhavo stack. The realistic use is as a reference for a data model you reimplement with Eloquent and Blade.
- What Laravel versions does enhavo/slider-bundle support?
- None. The package has no Laravel support matrix because it is not a Laravel package; it targets the Symfony full-stack framework and Enhavo's own release line. Any Laravel version constraints you see would be incidental transitive constraints from Symfony or Doctrine components, not tested compatibility. Treat Laravel version support as not applicable.
- What does enhavo/slider-bundle actually do?
- It adds slider support to the Enhavo CMS, which typically means a slider entity with ordered slides, media references, admin editing screens, and a Twig renderer inside Enhavo's block system. The exact entity fields, service IDs, config schema, and template names are not documented in this split, so you must read the source in the monorepo. For a Laravel team, the portable value is the concept and field design, not the code.
- Why is there no README or documentation for enhavo/slider-bundle?
- Because this repository is a read-only subtree split of the enhavo/enhavo monorepo, published mainly so Composer can install the code. The README excerpt is only a project blurb and a pointer to the main repository, and issues or pull requests are not handled here. Documentation, release notes, and support live upstream in the Enhavo project, not at the package level.
- How do I install enhavo/slider-bundle?
- You would install it with Composer as part of an Enhavo application, not standalone in Laravel. The bundle expects to be registered in a Symfony kernel and configured alongside Enhavo's other bundles, Doctrine mappings, and admin assets. For a Laravel app there is no supported installation path, and manually requiring it will only add unused Symfony and Doctrine surface area.
- Can I reuse the EnhavoSliderBundle data model in Laravel with Eloquent?
- Yes, conceptually. You can read the bundle's entity definitions to see how slides, ordering, media references, and slider metadata are modeled, then recreate that schema with Laravel migrations and Eloquent models in a few days. What you cannot reuse directly is the Doctrine mapping, the admin UI, and the block integration. Selective porting is the reasonable middle path.
- Does enhavo/slider-bundle work with Symfony 6 or Symfony 7?
- There is no standalone compatibility statement in this package. Version support follows the enhavo/enhavo monorepo release you are tracking, so you must check the main repository's composer.json and release history for the actual PHP and Symfony version floor. Do not assume a Symfony version from the subtree split alone, and expect constraint drift without a package-level changelog.
- Is enhavo/slider-bundle maintained, and where do I report bugs?
- The split repository is read-only, so issues and pull requests there are not accepted; all activity happens in the main Enhavo repository. Enhavo is a small-community CMS, and this package shows no dependents, so adoption signals are weak. If you need a fix, you either upstream it to a project you do not control or vendor a patch locally.
- What are good alternatives to enhavo/slider-bundle for a Laravel project?
- For most Laravel teams, the best alternative is a small in-house slider: a slides table with ordering and media columns, an Eloquent model, and a Blade partial, which is roughly two to five days of work. If you want a package, look for Laravel-native slider or CMS packages that ship service providers, migrations, and Blade or Livewire components. Porting Enhavo's model is only worth it if its field design solves a specific problem you have.
- How should I evaluate enhavo/slider-bundle before adopting it?
- Start by reading the source in the enhavo/enhavo monorepo rather than this split, and separate portable data model pieces from Enhavo-specific admin and block code. Check the monorepo's release cadence, PHP and Symfony constraints, and license-compatible dependencies against your stack. Then decide between building a minimal Laravel slider, reimplementing the field model, or running Enhavo as a headless sidecar if you already operate it.
Weaver
How can I help you explore Laravel packages today?