Ezplatform Site Api Laravel Package

Product Decisions This Supports

• Stack-fit validation. This is a PHP package, but it is not a Laravel package — it is a site-building productivity layer for eZ Platform / Ibexa DXP (formerly eZ Publish). Use it to decide whether the Ibexa-based product line justifies an approved exception to a Laravel-first standard.
• Build vs. buy for the content rendering layer. It replaces hand-rolled controller + query + template-resolution boilerplate with an opinionated Content/Location abstraction and configurable view resolution. The decision is "adopt this abstraction" vs. "maintain our own internal conventions."
• Multi-site / multi-brand roadmap. Standardizes how content types map to templates across sites, which directly informs whether brands can share one content model or need separate builds.
• Migration and replatform sequencing. If we are moving off legacy eZ Publish, this reduces rewrite effort. If we are moving toward a modern headless stack, it deepens commitment to Ibexa and should be sequenced as a deliberate exit risk, not an incidental dependency.
• Licensing posture. GPL-2.0 is copyleft; this feeds the decision on whether site front ends can ship as proprietary or must be distributed under compatible terms.
• Explicit non-fit: greenfield Laravel products, and any case where we intend to own the CMS/content layer ourselves.

When to Consider This Package

Consider it when:

• You are already on, or firmly committed to, Ibexa DXP / eZ Platform and have a genuinely content-heavy site to deliver.
• Your team keeps writing the same controller, query, and template-mapping code per content type and wants a tested abstraction instead.
• You need consistent rendering conventions across multiple sites, languages, or brands.
• You plan to pair it with Netgen Layouts or adjacent Netgen tooling — the value compounds inside that ecosystem.
• You can route a GPL-2.0 dependency through legal and accept self-support.

Look elsewhere when:

• Your product is Laravel-based. There is no Laravel integration; fit is effectively zero.
• You need active maintenance. Last release was 2023-02-17 with roughly 37 stars — a small specialist community. Budget for owning patches.
• You are standardizing on a headless-first CMS, where this layer adds indirection rather than removing it.
• Copyleft licensing cannot be isolated at arm's length from proprietary distribution.
• You depend on a large hiring pool and rich documentation; Ibexa specialists are scarce.

How to Pitch It (Stakeholders)

Executives: "We are evaluating a free, open-source productivity layer for our Ibexa/eZ Platform site builds. It removes repetitive custom code in how pages are assembled and rendered, which shortens delivery time per site and makes multi-brand rollouts more consistent. Two caveats: it is GPL-2.0, so legal must sign off before we ship anything proprietary on top of it; and the project is small, last released in early 2023, so we should assume we support it ourselves or buy vendor support rather than rely on a community. Recommendation: fund a short spike, not a commitment."

Engineering: "It gives us a stable Content/Location abstraction, configurable view resolution, and a query layer over Ibexa's Public API, so we stop reimplementing template-to-content mapping on every project. The cost is coupling to Netgen's conventions and to Ibexa's API version. It is not a Laravel package — if the roadmap assumes Laravel, this is a separate stack decision, not an add-on. Proposed next step: a two-week spike on one live site to measure boilerplate removed, confirm compatibility with our Ibexa version, and clear licensing. Fallback is Ibexa's native Twig/Public API with a thin set of conventions we own."