Weave Code
Layouts Sylius Laravel Package
netgen/layouts-sylius
Netgen Layouts integration for Sylius that lets store owners visually build and manage storefront page layouts, reuse blocks across pages, and edit content without touching templates, connecting Netgen Layouts' layout engine with Sylius themes and e-commerce pages.
Netgen Layouts & Sylius eCommerce integration
Frequently asked questions about Layouts Sylius
- What is netgen/layouts-sylius used for?
- It is an integration bridge that connects the Netgen Layouts layout composition engine with Sylius storefronts. It exposes Sylius frontend routes such as product, taxon and CMS pages as layout targets, and provides block types that render Sylius resources inside layout zones. The integration works at the presentation layer via Twig overrides, so it does not alter Sylius data models.
- Does netgen/layouts-sylius work with Laravel?
- No. netgen/layouts-sylius is built for Symfony and Sylius, not Laravel, and its dependencies are Symfony bundles rather than Laravel service providers. Laravel teams evaluating it would need a different layout or page-builder package.
- Which Sylius and Symfony versions does this package support?
- You need to audit the bundle's Composer require block for the exact PHP, Symfony, Sylius and Doctrine constraints before anything else. Because the package has low stars and no dependents, it likely does not track the latest Sylius 2.x and Symfony 6/7 releases. If it pins Symfony 4/5 or Sylius 1.x, adoption means freezing your upgrade path or forking the bridge.
- How do I install netgen/layouts-sylius?
- Install it with Composer alongside netgen/layouts-core, register the bundles in your kernel, and import the required configuration. Expect Twig template overrides in your Sylius theme to emit layout zones, plus asset and cache configuration. Confirm version constraints match your Sylius and Symfony versions first, because a mismatch will block installation.
- Is the Netgen Layouts admin embedded in the Sylius admin or a separate application?
- That is one of the first things to confirm in a spike. The Layouts admin may be embedded in the Sylius admin or run as a separate application sharing the same database. If it is separate, you inherit deployment topology, authentication and SSO work.
- What Sylius block types ship with this integration?
- The bridge supplies block types that render Sylius resources inside layout zones, typically covering product lists, taxon lists and content blocks. Merchandising requirements beyond those defaults will require custom block development. Scope that work before estimating the integration.
- How are layouts resolved and cached per request in Sylius?
- Netgen Layouts uses rule-driven layout selection per request, so the bridge resolves which layout applies to each Sylius route. You should verify how that resolution is cached and what invalidates it when a product or taxon changes. Getting invalidation wrong typically shows up as stale or empty zones rather than data corruption.
- Does the bridge support Sylius multichannel or multistore contexts?
- It is not clearly documented in the overview, so verify it directly in the code or with the maintainer. Sylius multichannel and multistore contexts raise the question of whether layout selection is global or per channel. If layouts are global, multistore merchandising may need custom work.
- Is netgen/layouts-sylius actively maintained?
- With 23 stars and zero dependents, treat maintenance as a real risk. Check the commit cadence, last release date and whether an identifiable maintainer could be contracted. Low downstream usage means the package will not be quietly kept current against new Sylius releases.
- What are the production risks of adopting netgen/layouts-sylius?
- Risk is medium to high and concentrated in abandonment, version drift and the Twig template override surface that Sylius changes most between minor releases. Functional risk is lower because layouts are additive, so failures usually mean an empty zone rather than corrupted data. A one-day compatibility spike, an incremental page-by-page migration and a fork contingency plan are the sensible mitigations.
Weaver
How can I help you explore Laravel packages today?