Weave Code
Layout Widget Laravel Package
friendsofvictoire/layout-widget
A PHP package from Friends of Victoire for adding reusable layout widgets to your projects. Define configurable widget areas, compose page layouts more cleanly, and render consistent blocks across templates with minimal setup.
At a glance
Frequently asked questions about Layout Widget
- Can I install friendsofvictoire/layout-widget in a Laravel application?
- No. friendsofvictoire/layout-widget is a Symfony bundle (WidgetLayoutBundle) built for Victoire DCMS, not a Laravel package. Laravel has no analogue to Symfony's bundle system or Victoire's widget registry, so Composer resolution will likely fail or the bundle will never boot. Treat it as reference code rather than a dependency.
- What is friendsofvictoire/layout-widget used for?
- It provides a reusable layout/grid widget for Victoire, a Symfony-based CMS. Editors can define configurable widget areas and column arrangements that render through Twig templates. The reusable surface is presentation-layer layout composition, not infrastructure for a Laravel app.
- Is this package compatible with modern Laravel or PHP versions?
- Very unlikely. The bundle is era-appropriate for Symfony 2.8/3.x and Twig 1.x, both long EOL, and its Composer constraints will almost certainly conflict with a current Laravel application. Check the composer.json require block before making any feasibility claim.
- How do I port this layout widget to Laravel?
- Extract, don't install. Pull the layout/column configuration schema and Twig templates as a specification, then rebuild rendering as a Blade component backed by a validated config array or a layout JSON column. Replace Symfony form types with Laravel validation and request handling, and discard the Victoire widget registration entirely. Assume a rewrite rather than an integration.
- Does this bundle depend on Victoire core?
- It is built as a Victoire widget bundle and assumes Victoire's widget contract, registration, and Twig rendering pipeline. The layout grid may be extractable, but that depends on whether the data contract is serialized config, a separate table, or CMS content attributes. Inventory the files and dependencies first.
- Are there maintained Laravel alternatives for page layout or content blocks?
- Yes. Evaluate maintained Laravel page-builder or block packages, Filament or Livewire block builders, or a simple column-config Blade component before building bespoke layout logic. Buying or adopting a supported package is usually cheaper than maintaining a port. Compare admin UI and front-end rendering costs separately.
- Is the package abandoned or safe for production?
- Treat it as abandoned. It has zero stars, zero dependents, and no observable maintenance cadence, so there is no community validation or downstream smoke test. There is also no security response process, meaning any CVE in the transitive Symfony/Twig graph is yours to handle. Do not ship it in a production Laravel app.
- How should I test a port of this widget?
- Separate tests into three concerns: the layout data model, the admin UI for choosing layouts, and front-end rendering. Use unit tests for config validation and feature tests to assert that column arrangements produce expected markup. Twig-to-Blade conversion needs markup or snapshot assertions because macros, blocks, and inheritance do not map one-to-one.
- What is the licensing and can I copy the layout templates?
- Confirm the repository license before copying any code or Twig templates as reference. Licensing should be verified before extraction, especially if the layout logic is small enough to reuse. The evaluation explicitly flags this as a step to complete before any code is copied.
- What is the difference between this widget and a Laravel page builder?
- This package is a narrow Symfony/Victoire presentation widget for choosing column layouts, not a general Laravel page builder. A Laravel page builder typically includes an admin UI, a block registry, and front-end rendering. Scope any port into three separate concerns: layout data model, admin UI, and rendering, because each has a different cost and different off-the-shelf options.
Weaver
How can I help you explore Laravel packages today?