Weave Code
Layouts Ui Laravel Package
netgen/layouts-ui
netgen/layouts-ui provides the administrative web interface for Netgen Layouts, letting editors visually create and manage layouts, zones, and blocks. It integrates with the Layouts core to deliver an intuitive browser-based editing experience for PHP applications.
Netgen Layouts user interface
Frequently asked questions about Layouts Ui
- Is netgen/layouts-ui a Laravel package?
- No. netgen/layouts-ui is a Symfony bundle built around Twig, Symfony service wiring, and an admin asset pipeline; the context explicitly flags it as a poor fit for Laravel. It is commonly paired with Ibexa/eZ Platform or a plain Symfony application, not Laravel. A Laravel port would mean rebuilding the UI against the core Layouts APIs rather than integrating this package. Verify your framework before adding it to composer.json.
- What does netgen/layouts-ui do?
- It provides the administrative web interface for Netgen Layouts, letting editors visually create and manage layouts, zones, and blocks in the browser. It sits on top of the netgen/layouts core engine as the authoring and presentation layer. It is not a standalone layout library and has no value unless the core engine is already approved. Think of it as the editor-facing extension of a core adoption decision.
- Can I use netgen/layouts-ui without netgen/layouts core?
- No. The UI is a secondary dependency that requires the netgen/layouts core engine and a matching release. Install the core first, then pin the UI to the same minor version because the packages are released in lockstep. Without the core, the bundle has no layout engine to drive its controllers, templates, or block mappings.
- How do I install netgen/layouts-ui in a Symfony application?
- Install it with Composer alongside the matching netgen/layouts core release, register the bundle in your Symfony kernel or bundles config, and configure the layout, zone, block, and rule mappings. You will also need to publish or build the admin front-end assets for the UI theme. The work is mostly wiring and configuration, but it touches the admin theme and asset pipeline, so coordinate with the team that owns those areas.
- Which Symfony and PHP versions does netgen/layouts-ui support?
- The exact Symfony and PHP ranges are defined in the package's composer.json constraints and should be checked against your supported-version policy. The UI is tied tightly to the core package, so the supported ranges usually move with the matching core release. Do not assume compatibility from the UI package alone; verify both core and UI constraints together before upgrading.
- Do I need the UI to create layouts, or can I define them in YAML or PHP config?
- The UI is the browser-based authoring layer for editors, but the core Layouts engine can support configuration-driven layout definitions. Confirm whether your target core version exposes the layout, zone, block, and rule mappings you need without the admin UI. If your team only needs code-defined layouts, evaluate the core package first and treat the UI as optional. The UI is mandatory only if non-technical editors must compose layouts visually.
- Does netgen/layouts-ui require Ibexa or eZ Platform?
- The package is a Symfony/Twig bundle and is commonly paired with Ibexa/eZ Platform, but the context does not confirm that Ibexa is mandatory. A plain Symfony application may work if the core Layouts package and admin context are configured correctly. Validate this in a disposable Symfony spike before committing, because the UI may assume an admin theme or asset pipeline from that ecosystem.
- What asset build or publish steps does netgen/layouts-ui need?
- Expect a JavaScript and CSS build or publish step for the admin theme, similar to other Symfony bundles with front-end assets. The exact toolchain is not specified in the context, so inspect the package and its documentation for Encore, Vite, or another build path. Check whether that toolchain conflicts with your existing admin asset pipeline before rollout. Asset pipeline maintenance is one of the secondary risks of adopting this UI.
- Is netgen/layouts-ui production-ready despite low adoption?
- It is MIT-licensed and Composer-installable, but the context reports seventeen stars and zero dependents, which means a very narrow adoption base and little ecosystem support. The main risk is project viability and maintainer bus factor, not data corruption; a UI failure blocks content authors but does not corrupt layout data. Treat it as an extension of a core Layouts decision, run a timeboxed Symfony spike, and document the configuration surface internally. Consider commercial support from Netgen if you need production assurances.
- Are there alternatives or commercial support options for netgen/layouts-ui?
- Within the Netgen ecosystem, the primary alternative is to use the core Layouts engine with code-defined layouts and skip the visual admin UI. Netgen is a commercial vendor, so ask directly about support options, release cadence, and the maintainer team behind the UI. Outside this ecosystem, evaluate Symfony or Laravel-native page builders rather than porting this Symfony bundle. For a Laravel stack, a native Laravel solution is a better fit than netgen/layouts-ui.
Weaver
How can I help you explore Laravel packages today?