Weave Code
Layouts Ibexa Laravel Package
netgen/layouts-ibexa
Netgen Layouts integration for Ibexa brings block-based layout management to Ibexa CMS, letting editors compose and reuse page layouts, manage blocks, and override templates through Netgen Layouts within the Ibexa admin interface.
Netgen Layouts & Ibexa DXP integration
Frequently asked questions about Layouts Ibexa
- Is netgen/layouts-ibexa a Laravel package?
- No. netgen/layouts-ibexa is a Symfony bundle that integrates Netgen Layouts with Ibexa DXP, formerly eZ Platform. It has effectively zero fit in a Laravel codebase because the parent stack is Symfony and Ibexa. If you are evaluating it against Laravel, treat that as a false positive and close it unless you plan to run Ibexa as a separate service.
- What does netgen/layouts-ibexa do in an Ibexa project?
- It registers Netgen Layouts management into the Ibexa admin surface, maps Ibexa content views and locations into Netgen's layout resolver, and exposes Ibexa content as blocks and content lists inside layouts. Editors can then compose and reuse page layouts through Netgen Layouts while working inside Ibexa. The bridge is glue between the layout engine and Ibexa's content model, not a standalone CMS feature.
- How do I install netgen/layouts-ibexa?
- Install it with Composer alongside netgen/layouts, netgen/layouts-standard, and the Ibexa kernel. You then register the bundles, wire routing and configuration, run the Netgen layout schema migrations, and publish assets for the admin UI. It is feasible in a clean Ibexa 3.x or 4.x environment, but the real effort is configuration and content-model mapping rather than the install itself.
- Which Ibexa and Symfony versions does netgen/layouts-ibexa support?
- The bridge sits between Ibexa, Symfony, and Netgen Layouts core, so your supported combination is the intersection of all three constraint sets. Confirm the documented support window for your exact Ibexa version rather than assuming it from the core packages. Pin exact versions in composer.json and verify the PHP minor version against all three at once, because that intersection is narrower than any single package's constraints.
- Is the GPL-2.0 license of netgen/layouts-ibexa a problem for commercial products?
- GPL-2.0 is copyleft, so if this ships inside a distributed commercial product you inherit an obligation to release the combined work. Internal-only deployments are usually tolerable, but SaaS or customer-deployed components need legal review, not an engineering decision. Make legal sign-off on GPL-2.0 against your distribution model the gate before any technical work.
- Can I use netgen/layouts-ibexa headless without the Ibexa admin UI?
- The package's default value is registering layout management into the Ibexa admin surface, but one of the key evaluation questions is whether you actually need that UI. A headless approach, where you run layout resolution and own the editor experience separately, may be possible. Confirm that path in writing with the vendor before committing, because the bridge's documented behavior centers on the admin integration.
- How do I map Ibexa content views and locations to Netgen Layouts layouts?
- You configure layout resolver rules and block definitions so Netgen can bind layouts to Ibexa content trees. The bridge maps Ibexa content views and locations into the resolver and exposes Ibexa content as blocks and content lists inside layouts. For existing sites, migrate one content type at a time and keep native Ibexa view templates as the fallback until each layout is validated in staging.
- Is netgen/layouts-ibexa actively maintained and does it have community support?
- Adoption signals are very low: the project has two stars, zero dependents, and a score of 0.3, so it is effectively a single-vendor integration bridge. Assume there is no community safety net and budget for the possibility of forking. Netgen is a credible shop with commercial support for Netgen Layouts core, but confirm in writing whether support covers this bridge specifically.
- What are alternatives to netgen/layouts-ibexa for layout management in Ibexa?
- The native alternative is to stay on Ibexa's own content views and view templates and build custom block rendering yourself. You can also run Netgen Layouts core with commercial support and own more of the integration, or run layout resolution headless and build your own editor experience. If your actual stack is Laravel, use Laravel layout or block packages instead; this bridge is not adaptable to Laravel.
- What are the production and upgrade risks of netgen/layouts-ibexa?
- The bridge couples three moving targets, Ibexa, Symfony, and Netgen Layouts core, and it leans on Ibexa's view builder and content-view internals, which have historically churned across major versions. Upgrade breakage is likely and will surface at the admin UI and template-rendering layer. Pin exact versions, treat upgrades as discrete projects, and test each migrated layout and content type in staging with native templates as a fallback before production rollout.
Weaver
How can I help you explore Laravel packages today?