- Can I use akyos/builder-bundle in a Laravel application?
- Not natively. The bundle is built directly on Symfony's dependency injection container, EventDispatcher, Twig templating, and HttpFoundation request parameter bags; the 8.0.2 release specifically replaced Request::get() with query and request bag calls. Laravel's Illuminate\Http\Request, Blade, and service provider model do not expose those APIs, so you would need a substantial adapter layer or a rewrite. For most Laravel teams a Laravel-native builder is the lower-risk choice.
- How do I install akyos/builder-bundle with Composer?
- Run composer require akyos/builder-bundle:^8.0 inside a Symfony 8 project. The package requires PHP 8.4 or newer, Symfony ^8.0, and akyos/core-bundle ^8.0, so those constraints must already be satisfied in your composer.json. The README and changelog are written in French, so budget time for translation during onboarding.
- What PHP and Symfony versions does akyos/builder-bundle require?
- Version 8.x requires PHP 8.4 or higher and Symfony ^8.0, plus akyos/core-bundle ^8.0. That PHP floor rules out most Laravel 10 and 11 applications, which typically run PHP 8.2 or 8.3. If you must stay on an older PHP version you would have to pin an earlier major, which uses a different Symfony request API contract.
- Does akyos/builder-bundle support Laravel 10 or Laravel 11?
- No. There is no Laravel service provider, facade, or Blade integration, and the 8.x branch targets Symfony 8 with a PHP 8.4+ floor. Laravel 10 and 11 projects on PHP 8.2 or 8.3 cannot install 8.x at all. Even on PHP 8.4, the framework coupling, not the version constraint, would remain the blocker.
- What features does akyos/builder-bundle provide out of the box?
- It is a visual page builder for Symfony: drag-and-drop page composition with modular blocks, reusable components, templates, translatable field values, and front-end rendering through Twig. It depends on akyos/core-bundle for shared CMS functionality. It is not a full CMS, so media management, user roles, and multi-site support are not included.
- Is akyos/builder-bundle actively maintained?
- Yes, but with a small footprint. The 8.0.2 patch fixed the removal of Request::get() in Symfony 8, showing the maintainers track upstream Symfony breaking changes promptly. However, the repository has essentially no stars or dependents, the release notes and documentation are French-only, and there is no visible automated test suite. Treat upstream bumps as scheduled work rather than routine updates.
- Can I render akyos/builder-bundle pages with Laravel Blade?
- Not directly. The bundle's front-end rendering is Twig-based and expects Symfony's templating and request lifecycle, so stored block data would have to be re-serialized into Blade or Livewire components. In practice you would rebuild the rendering layer and keep only the persisted block structure.
- How much work is it to port akyos/builder-bundle to Laravel?
- Significant. You would need to substitute Symfony's ContainerInterface with Laravel service providers, Twig with Blade, the EventDispatcher with Laravel events, and Symfony request query and request bags with Laravel input handling, including in the admin component-editing path that 8.0.2 touched. A more realistic route is extracting block storage, validation, and serialization into a framework-agnostic library and rebuilding the admin UI on Livewire or Inertia.
- What are Laravel-native alternatives to akyos/builder-bundle?
- Filament with a block or builder plugin covers most page-composition needs inside a familiar Laravel admin panel. Laravel Nova toolsets combined with Livewire or Inertia let you build a custom page builder without Symfony coupling, and Spatie Media Library handles assets. If you only need the data model, a small block schema of your own is usually less work than maintaining an adapter.
- Is akyos/builder-bundle safe to use in production?
- Use it with caution. The absence of a visible test suite is a real concern, and a Symfony 8 request-API regression reaching a tagged release suggests thin coverage on the admin editing path. Pin an exact version, prototype block serialization and admin editing in isolation before committing, and plan to resolve upstream issues internally since community support is minimal.