Weave Code
Block Bundle Laravel Package
enhavo/block-bundle
Enhavo Block Bundle is a subtree split of the open-source Enhavo CMS, built on the Symfony PHP framework. It provides flexible block components for managing complex data structures through a clean, usable interface. See the main repository for details.
[READ-ONLY] EnhavoBlockBundle
Frequently asked questions about Block Bundle
- Is enhavo/block-bundle a Laravel package?
- No. It is a Symfony bundle extracted from the Enhavo CMS monorepo and published as a read-only subtree split. There is no Laravel service provider, facade, config bridge, or framework-agnostic layer. Its runtime contract assumes Symfony HttpKernel and dependency injection, Symfony Form, Twig, Doctrine ORM, and several sibling Enhavo bundles.
- Can I install enhavo/block-bundle with Composer in a Laravel application?
- Composer may resolve and download it, but the package will not function in Laravel. Block types are Doctrine entities in an inheritance hierarchy with a discriminator column, and rendering depends on Enhavo's resource, form, routing, and backend bundles. Making it work would require running Symfony's container and form component inside Laravel, replacing Eloquent with Doctrine for the block entities, and reimplementing the block renderer and admin UI.
- What does EnhavoBlockBundle actually do?
- It provides flexible block components for managing complex data structures through a clean, usable interface inside the Enhavo CMS. Blocks are modeled as Doctrine entities with a type discriminator, edited through Symfony forms and rendered through Twig within Enhavo's backend pipeline. The value only materializes when the full Enhavo resource and backend layer is present.
- Which Symfony, PHP, and Doctrine versions does it require?
- The bundle targets the fullstack Symfony framework, so a Symfony 6 or 7 application with Doctrine ORM and Twig is the realistic baseline. Exact PHP and Symfony constraints are inherited from the Enhavo release the split was cut from, not from an independent version guarantee. Check the composer.json of the specific tag and pin against a matching Enhavo release set, because the subtree split carries no separate semantic versioning promise.
- How do I install and configure EnhavoBlockBundle?
- Do not require enhavo/block-bundle in isolation, because you will end up with an unresolvable or mismatched dependency graph. Install the Enhavo metapackage or application skeleton at a pinned version and let dependency resolution pull the matching block-bundle split transitively. Configuration then happens through Enhavo's own backend and resource configuration rather than a bundle-level config file.
- Where is the documentation for EnhavoBlockBundle?
- The README is a logo, a one-paragraph description of the Enhavo CMS, and a note that this is a subtree split. There is no bundle-level usage documentation, so you read the main Enhavo repository docs or the source itself. Plan on source reading for anything beyond a basic install.
- Can I open issues or pull requests against this repository?
- No. This repository is a read-only mirror generated from the main Enhavo monorepo, so issues and pull requests belong upstream in the main repository. Anything filed here can silently disappear, and subtree splits also make local patching awkward because changes must be carried upstream or maintained as your own fork. Decide who owns the fork before you depend on the bundle.
- Is enhavo/block-bundle production ready and what are the maintenance risks?
- The upstream Enhavo project is a legitimate, longstanding Symfony CMS, and the license is clean MIT, so the risk is engineering and support rather than legal. However this split has no community signal, with zero stars and zero dependents, meaning no third-party field testing, no Stack Overflow corpus, and no independent security triage or CVE response path you do not create yourself. The bundle also depends on internal Enhavo APIs that are not stability-guaranteed, and Doctrine schema changes in a block-type refactor can require content migrations.
- How do I test a project that uses EnhavoBlockBundle?
- Testing is done inside a Symfony kernel with Doctrine, typically using PHPUnit functional tests that boot the Enhavo backend bundles and load fixtures for block entities. Because editing and rendering depend on Enhavo's admin UI and Twig pipeline, unit-testing the bundle in isolation gives little confidence. There is no Laravel-style package test harness or facade fake available.
- What are the alternatives if I need block-based page content in Laravel?
- For Laravel, treat this bundle as out of scope and build or evaluate a Laravel-native content model instead, using Eloquent models, Blade components, and your own block registry. A port would mean running Symfony's container and form component inside Laravel and reimplementing the renderer and admin UI, which is a multi-week effort with a permanent dual-framework maintenance burden. Only the goal of adopting a full CMS justifies pulling in Enhavo, and only on Symfony.
Weaver
How can I help you explore Laravel packages today?