Weave Code
Page Layout Bundle Laravel Package
it-blaster/page-layout-bundle
A PHP bundle for configurable page layout management, letting you define layout templates and reusable blocks to compose and render page structure consistently across your application.
Bootstrap page layout for sonata, based on gridstack.js
Frequently asked questions about Page Layout Bundle
- Can I install it-blaster/page-layout-bundle in a Laravel app with Composer?
- No. it-blaster/page-layout-bundle is a Symfony bundle built for Sonata Admin, not a Laravel package. It ships no service provider, no facades, no publishable config/page-layout.php file, and no Blade views, so Composer will pull the code in but nothing will boot or register. Trying to require it into a Laravel application is a cataloguing error rather than an integration task, and the real question is whether you want to port the layout concept.
- Is page-layout-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, and its documented integration target is Sonata Admin. Its job is to define and render reusable page layouts with flexible regions so layout structure stays separate from page content. That concept travels well to Laravel, but the package code and its Twig templates do not.
- How do Laravel developers build reusable page layouts without this package?
- Treat it as a reference implementation and rebuild the idea natively. The portable asset is narrow: the Gridstack.js drag-and-drop wiring over a Bootstrap grid plus the JSON layout-persistence shape behind it. In Laravel you would port the templates to Blade, rebuild the editing surface as a Livewire or Inertia component, and persist layouts to a first-class page_layouts model with a JSON column. Most teams scope this as a one to two day spike, not a release line item.
- Does it-blaster/page-layout-bundle support Laravel 10 or Laravel 11?
- No. There are no Laravel version constraints, no service provider, and no Blade or Livewire integration of any kind, so Laravel 10 and Laravel 11 support does not exist and is not on any roadmap. The package does not even align cleanly with current Symfony and Sonata Admin releases. If you need Laravel support, plan for a vendored reimplementation rather than a dependency.
- What does it-blaster/page-layout-bundle actually do?
- It provides a lightweight way to define reusable page layouts and compose page content into flexible regions. Layout structure is kept separate from content so templates stay consistent and easier to maintain. Setup is minimal and the bundle is extensible for custom layout needs, with a Bootstrap-based grid editor driven by Gridstack.js for arranging blocks.
- Is it-blaster/page-layout-bundle maintained and safe for production?
- Assume no upstream patches. The project is single-vendor with no visible CI, no test suite signals, no security policy, and no release cadence, and it has roughly five stars and zero dependents. The MIT license is clean, so there is no legal blocker, only engineering ones. Pulling an unmaintained wrapper over a fast-moving JavaScript library into production is effectively scheduling a future migration.
- Can I reuse the JSON layout persistence format from this bundle?
- Yes, and that is the most reusable part, along with the Gridstack event handlers and configuration. The JSON shape describes how blocks map onto grid positions, which is straightforward to model yourself. Before copying it, decide who owns your layout schema and make sure it survives a future Gridstack upgrade. Persisting to a dedicated page_layouts table with a JSON column gives you that independence.
- Is Gridstack.js pinned in page-layout-bundle, and does that matter?
- It very likely pins a legacy Gridstack version from the Symfony 4 and 5 era, possibly buried inside a compiled asset rather than exposed. Gridstack is now at v10 and v11 with breaking API changes, so a pinned copy means no fixes on the drag-and-drop layer. If you build on the pattern, use a current Gridstack release directly and keep your persistence schema decoupled from its internals.
- Does it-blaster/page-layout-bundle work with Symfony and Sonata Admin?
- It is feasible in principle, but only if Sonata Admin is already running in production and your Symfony, Sonata Admin, Twig, and Bootstrap versions all align. Adopting a heavy admin generator just to gain a layout editor is a bad trade that outlives the feature itself. Also flag the asset pipeline early, because an Encore-era build assumption becomes a rewrite under Vite or asset-mapper rather than a config change.
- What are the alternatives to it-blaster/page-layout-bundle for Laravel?
- The realistic alternatives are a vendored reimplementation on Blade plus Livewire or Inertia, or wiring Gridstack.js directly in a small front-end module. Before choosing either, ask whether freeform drag-and-drop is truly required, since a fixed-slot block or template picker is cheaper and wins on accessibility and responsive behaviour. For most teams the slot picker is the answer that ships.
Weaver
How can I help you explore Laravel packages today?