Layouts Sylius Laravel Package

Product Decisions This Supports

• Build vs. buy for storefront composition. The core question this package answers is whether to hand-roll a page/layout builder inside a Sylius storefront or adopt Netgen Layouts. The integration is thin glue (MIT) between Netgen Layouts' layout engine and Sylius resources, so the real buy decision is on Netgen Layouts itself, not this repo.
• Merchandising velocity roadmap. Supports a roadmap item of "marketing can compose and change landing pages, category layouts, and campaign pages without a deploy." Layouts are resolved dynamically against rules (channel, locale, route, taxonomy), which maps directly to Sylius channels.
• Multi-channel / multi-store differentiation. If the product plan includes per-channel or per-region storefront variants, a rule-driven layout layer is a cheaper path than forking Twig templates per channel.
• Feature scoping for CMS-lite vs. full page builder. Helps a PM draw the line: Sylius's built-in CMS pages and blocks cover static content; Layouts covers composed, reusable, rule-targeted page structures. That boundary is a scoping decision, not an engineering one.
• B2B and catalog-heavy use cases. Customer-specific or segment-specific catalog and portal layouts (per customer group, per contract) are a recurring B2B commerce ask that a template-only approach handles badly.
• Support/maintenance budgeting. With 23 stars and zero dependents, adopting this is a "we own the glue" decision. That belongs in the roadmap as a maintenance line item, not a silent dependency.

When to Consider This Package

Consider it when:

• You are already committed to Sylius on Symfony — this package has no value outside that stack.
• Marketing or merchandising has a recurring, quantified backlog of layout/landing-page requests that engineering is currently absorbing.
• You need rule-based layout resolution (by channel, locale, route, product taxonomy) rather than simple editable content fields.
• You are comfortable operating Symfony bundles and their version matrix — verify compatibility against your Sylius and PHP versions before committing.
• You can vendor or pin the integration and accept ownership of upgrades; treat it as source you may need to patch.

Look elsewhere when:

• You are not on Sylius, or you are on a hosted SaaS commerce platform.
• Your storefront has a small, stable set of pages — Sylius CMS pages/blocks plus Twig templates will be cheaper and simpler than introducing a layout engine.
• You need a vendor SLA and commercial indemnity out of the box. Check Netgen's commercial offering and support terms separately; this MIT repo carries no support commitment.
• Your team has no appetite for a niche dependency — low stars, zero dependents, and a small contributor pool mean bus-factor risk sits with you.
• You need a React/Vue visual page builder for a headless frontend. Netgen Layouts is a server-rendered Symfony-centric model; confirm it fits a headless architecture before scoping.
• Time-to-market is measured in weeks and the team cannot absorb integration and evaluation effort.

How to Pitch It (Stakeholders)

To executives: Marketing's page and campaign requests currently queue behind engineering. This integration lets non-engineers compose storefront layouts — homepages, category pages, campaign landing pages — per channel, without code changes or releases. The software is MIT-licensed glue over an established Symfony layout engine, so the direct cost is low; the real investment is a short integration sprint plus ongoing ownership. The decision to make is not "is this free" but "do we want to own a niche integration, or fund a build." Recommend a time-boxed spike against one channel before committing roadmap capacity.

To engineering: This is a small MIT integration between Netgen Layouts and Sylius — layout resolution hooks into Sylius channels, routes, and resources, with templates rendered through the existing Symfony/Twig stack. It is Symfony-native and does not introduce a separate frontend runtime. Caveats to price in: 23 stars, zero dependents, so treat it as code you own — pin versions, review the compatibility matrix against our Sylius and PHP versions, and budget for patching on Sylius upgrades. Confirm the Netgen Layouts licensing and support tier separately, since that is the actual product dependency.

To marketing/merchandising: You would get a layout editor where you define reusable page structures and target them by channel, locale, or section of the store, instead of filing tickets for template changes. Trade-off to accept: it is a structured layout system, not a freeform drag-and-drop website builder — page structure and available blocks are defined by engineering up front.