Layouts Ibexa Laravel Package

Product Decisions This Supports

• Build vs. buy for editorial layout/page composition in Ibexa: whether to adopt Netgen Layouts plus this integration instead of custom landing-page tooling or Ibexa’s native Page Builder.
• CMS/DXP modernization roadmap: decoupling content authoring in Ibexa from presentation/layout composition in Netgen Layouts, especially for multi-site, multi-brand, and campaign-driven properties.
• Editorial autonomy investment: enabling marketing/content teams to assemble pages from reusable blocks without engineering tickets for every campaign page.
• Cross-property reuse: if Netgen Layouts is already used in other Symfony applications, this package supports consistent layout management across Ibexa and non-Ibexa sites.
• Risk posture: with 2 stars and 0 dependents, treat this as a targeted integration/reference implementation, not a default strategic platform choice without due diligence.

When to Consider This Package

Consider it when:

• You run Ibexa and already use, or explicitly plan to use, Netgen Layouts as the layout engine.
• You need shared or consistent layout definitions across Ibexa and other Symfony/Netgen Layouts applications.
• You can accept GPL-2.0 copyleft obligations, or your distribution model is compatible with them.
• You have in-house Symfony/PHP capability to own integration maintenance, upgrades, and security review.
• You validate compatibility with your Ibexa and Netgen Layouts versions, plus test coverage, commit activity, and maintainer responsiveness.

Look elsewhere when:

• You need vendor-supported, SLA-backed page building: use Ibexa’s native Page Builder/Experience capabilities or a commercial alternative.
• GPL-2.0 is incompatible with your proprietary product or licensing model.
• You require broad adoption, active community support, or long-term maintenance guarantees; 2 stars and 0 dependents is a weak signal.
• You lack Symfony expertise or cannot absorb the maintenance burden of a thin integration package.
• Your needs are simple enough for native Ibexa templates or a lighter CMS-native approach.

How to Pitch It (Stakeholders)

Executives: This is a small integration bridge, not a standalone product. It could reduce custom development for marketing landing pages and campaign sites by letting editors compose layouts from reusable blocks while Ibexa remains the content system. That supports faster time-to-market for multi-site and multi-brand content without building a bespoke page builder. The risks are material: tiny community, GPL-2.0 licensing, and no vendor support. Recommend a time-boxed proof of concept against native Ibexa Page Builder before committing roadmap budget.

Engineering: The package wires Netgen Layouts into Ibexa’s content model so layout resolution can use Ibexa content and site context. Evaluate code quality, version compatibility, test coverage, and upgrade paths. Budget for ownership: dependency pinning, security review, and possible fork/maintenance. Start with a spike on a non-critical site, confirm GPL obligations with legal, and compare total cost against native Page Builder or a custom implementation.