Utility Bundle Laravel Package

Product Decisions This Supports

• Build vs. buy: The real decision is not "adopt this package" but "keep investing in the eZ Publish / ezpublish-kernel lineage." This package is a thin Laravel adapter; the dependency bump in v0.4.1-alpha confirms its value and risk both track the upstream kernel.
• Roadmap sequencing: At 0.x alpha, this belongs in a time-boxed spike or internal tooling slot — not on a customer-facing roadmap with delivery commitments.
• Replatform vs. integrate: Useful only if you have existing eZ Publish content and want Laravel-side access without a full migration. It does not justify choosing eZ Publish for anything greenfield.
• Use cases: Legacy content migration/extraction, internal admin prototypes over an existing content repository, short-lived bridging services during a CMS transition.
• Vendor/supply-chain posture: A dependency-only alpha release is a signal to treat version pinning and upstream kernel lifecycle as first-class product risks, not an afterthought.

When to Consider This Package

Consider it when:

• You already operate eZ Publish / ezpublish-kernel and need Laravel-side access without replatforming first.
• You have a bounded migration window (roughly 12–18 months) and no intention of a long-term commitment to the kernel.
• Your team can absorb alpha-level API churn and is willing to vendor or fork if upstream stalls.
• You have in-house PHP ownership for the legacy kernel, including security patching.

Look elsewhere when:

• The product is greenfield, or you need stable public API guarantees and a maintained dependency tree.
• You actually want modern Ibexa (v4+) headless capabilities rather than the legacy kernel.
• Security/compliance review requires actively maintained upstream dependencies with clear EOL policy.
• The package would become a long-lived integration surface — the adapter is small, but the platform underneath it is the liability.

How to Pitch It (Stakeholders)

To executives: This is a low-cost, time-boxed experiment to de-risk a migration off a legacy CMS — not a platform bet. v0.4.1-alpha is a maintenance release (dependency update only), so there are no new capabilities to sell internally, but it does confirm the package is tightly coupled to the legacy kernel's release cadence.

To engineering: Expect a small Laravel adapter over ezpublish-kernel with alpha-grade stability. Pin the exact alpha version, track upstream kernel EOL, and define exit criteria and a fork/vendor plan before any production exposure. Treat the dependency bump as the headline risk, not the headline feature.