Layouts Ezplatform Relation List Query Laravel Package

Product Decisions This Supports

• Editorial self-service in layout composition. This bundle registers a Netgen Layouts query type that pulls content items into a block from a relationlist field on any eZ Platform content item. That turns an existing content-modeling primitive into a curation tool: editors pick related articles, featured products, or campaign items on a content item and those selections populate a layout block—no developer involvement per page change.
• Build vs. buy for layout query types. If we are already on Netgen Layouts + eZ Platform and need relation-list-driven blocks, this replaces a small but real custom integration (a query type implementation, block definition wiring, and tests). Buy/adopt here; it is a thin, single-purpose bundle rather than a framework commitment.
• Roadmap input for content-driven pages. It supports features like "related content" rails, editor-curated landing page sections, cross-sell blocks on product/content pages, and campaign pages where merchandising is manual rather than algorithmic. If those are on the roadmap, this is a cheap enabler; if our roadmap is search- or personalization-driven blocks, it solves the wrong problem.
• Scope boundary for content modeling. Adopting it signals a product decision that relation lists are our curation mechanism of record, which affects how content types are designed and how editors are trained.
• Deprioritization signal. Six stars, zero dependents, and a low opportunity score indicate a narrow ecosystem tool. It is a tactical enabler, not a strategic platform bet—size the decision accordingly.

When to Consider This Package

Adopt when:

• The stack is already eZ Platform (Ibexa) with Netgen Layouts installed and in production; this is an additive query type, not a platform change.
• Content types already use relation / relationlist field types, so editors have an existing, understood curation workflow.
• The requirement is explicitly manual curation—an editor decides what appears in a block.
• We can accept a small, GPL-2.0-licensed community bundle maintained as part of the Netgen Layouts family, with no independent community base to fall back on.

Look elsewhere when:

• We are not on Netgen Layouts, or we are evaluating Ibexa's own layout/page-builder tooling—this has no value outside that pairing.
• Blocks need dynamic or rule-based selection (tags, taxonomy, search queries, personalization, recency) rather than hand-picked items; a relation-list query is the wrong abstraction.
• We require vendor SLAs, active maintenance guarantees, or a security-response commitment. With 6 stars and 0 dependents there is no ecosystem safety net; treat it as code we may need to own.
• License posture matters: GPL-2.0 is copyleft, which needs legal review if the surrounding product is proprietary or if we would redistribute a derived bundle.
• We are planning an Ibexa DXP upgrade path where compatibility of small Netgen bundles is unverified—validate against the target version before committing.

How to Pitch It (Stakeholders)

For executives: This is a small, low-cost capability unlock rather than a platform investment. It lets our editors populate page blocks with content they hand-pick—related articles, featured items, campaign selections—using content relationships they already maintain, which reduces engineering tickets for landing-page and merchandising changes and shortens time-to-publish. Cost and integration effort are minimal if we are already running Netgen Layouts on eZ Platform; outside that stack it has no applicability. The main caveats are governance, not capability: it is a niche GPL-2.0 community bundle with very limited adoption, so we should assume we may need to maintain it ourselves and have legal confirm the license is acceptable for our distribution model.

For engineering: A single-purpose bundle that registers a Layouts query type reading relationlist fields from any eZ Platform content. Integration surface is small—install, enable, and configure blocks to use the query—and it composes with existing content types rather than requiring new ones. Risks to flag in the technical review: minimal external usage means little battle-testing beyond Netgen's own deployments, no dependents to validate upgrade paths, GPL-2.0 obligations, and unclear compatibility with newer Ibexa DXP releases. Recommend a short spike against our target version and a decision on whether we fork and own it if we adopt.