Weave Code
Title Widget Laravel Package
friendsofvictoire/title-widget
friendsofvictoire/title-widget is a lightweight Laravel/PHP package for reusable, configurable title widgets. It helps compose page titles from parts, apply separators or suffixes, and render consistent headings and browser titles from views with minimal setup.
At a glance
Frequently asked questions about Title Widget
- Is friendsofvictoire/title-widget a Laravel package?
- No. Despite being listed in some Laravel package catalogs, friendsofvictoire/title-widget is a Symfony bundle built for the Victoire CMS. It exposes no Laravel service provider, no Illuminate contracts, no config publish tags, and no Blade views. There is no architectural seam through which it can attach to a Laravel application.
- Can I install friendsofvictoire/title-widget in a Laravel application?
- Practically no. Composer constraints will conflict with Laravel 10 or 11 dependency sets on both the php and symfony/* axes. Even an install with --ignore-platform-reqs would autoload classes that reference Victoire namespaces absent from your tree, causing a ClassNotFoundError at the first widget render. It has no runtime fit with Laravel.
- What Laravel versions does friendsofvictoire/title-widget support?
- None. The bundle targets Symfony 2.8 and 3.x-era applications and likely pins PHP to ~5.6 or ~7.0. Its last release was 2017-05-03, long before modern Laravel versions. It was never designed for Laravel and has no Laravel version support matrix.
- What does the friendsofvictoire/title-widget actually do?
- It provides a configurable title widget for Victoire CMS pages. The functional surface is a heading rendered into a CMS page: heading text, tag level, and some style options. That is essentially a text field plus a Twig template. It is not a general-purpose title component for Laravel.
- How do I install friendsofvictoire/title-widget?
- The normal path would be composer require friendsofvictoire/title-widget, but it requires Victoire CMS core as a transitive dependency. That pulls in a heavy, equally stale Symfony-based framework. For a Laravel evaluation, do not install it; read the bundle source to capture design intent instead.
- Is friendsofvictoire/title-widget actively maintained?
- No. It has a composite health score of 0.035, one star, zero dependents, and no downstream validation. The last release was 2017-05-03, making it roughly eight years unmaintained. Symfony 2.8 and 3.x are long end-of-life.
- What are the security risks of depending on friendsofvictoire/title-widget?
- The risk is high and non-mitigable. You would inherit an end-of-life Victoire/Symfony dependency tree with unpatched CVEs and no security-patch commitment. PHP version ceilings may block Composer resolution on PHP 8.2 or 8.3. Installing it puts an EOL framework into your dependency graph just to obtain a heading tag.
- What is a good Laravel alternative for reusable page titles?
- Build a small in-house solution. Model titles as first-class content blocks with a blocks table containing type, payload JSON, and order, then render them through a Blade component. Configurable tag level and text become validation rules rather than framework features. This takes about one to two days including tests and avoids the dependency entirely.
- How do I migrate a Victoire title widget to Laravel?
- Extract the design intent, not the code. A 30-minute read of the bundle's widget definition and Twig template is enough to capture fields, tag levels, escaping, and accessibility defaults. Then write a one-page internal spec and implement a Blade component plus an admin field. The preferred path is reimplementation, not adoption.
- Should I fork friendsofvictoire/title-widget for Laravel?
- No, unless you are already a Victoire shop. Forking would mean pinning Symfony 3, freezing PHP, and accepting permanent maintenance of an abandoned CMS. The reimplementation effort is measured in hours, not days, so pulling in an unmaintained dependency is unjustifiable. Retain the bundle as a reference read only.
Weaver
How can I help you explore Laravel packages today?