Title Widget Laravel Package

Product Decisions This Supports

• Block-library scoping for a page builder / CMS roadmap. A "title" block is table stakes in any block-based editor. This package shows the minimum viable surface area of one block — admin form, front-end template, model/entity, and registration with the widget registry — which is useful sizing input when deciding whether to build our own block library or buy one. It argues the marginal cost of a block is low once the framework exists, and that the framework is the real investment.
• Build vs. buy for CMS platform. It is a data point against betting on a niche CMS ecosystem: individual widgets carry their own maintenance lifecycle, and this one has been dormant since June 2017. Platform bets should be evaluated on the health of the widget ecosystem, not the core alone.
• Extension-contract design reference. Useful when defining our own plugin/widget API — what a host CMS must expose (registration metadata, admin form contract, render hook, i18n) to let third parties ship blocks cheaply.
• Explicitly not a demand signal. 2 stars and 0 dependents means no market validation. Do not cite adoption, community, or popularity as evidence for prioritizing heading/content-block work.

When to Consider This Package

Consider it only if:

• You are already running Symfony on the Victoire CMS and need a heading block, and you are prepared to vendor or fork the code.
• You need a compact worked example of a Victoire widget for a spike, migration archaeology, or contract design.
• Your runtime matches its 2017-era constraints (older Symfony majors, pre-PHP 8).

Look elsewhere when:

• Your stack is Laravel. This is a Symfony bundle, not a Laravel package — it will not integrate or autoload meaningfully in a Laravel application. The framing "Laravel/PHP package" does not hold here; the only transferable value is conceptual.
• You require maintained dependencies, security patching, or current PHP/Symfony support.
• You are selecting a CMS or page-builder platform with a multi-year horizon.
• You need a heading block with rich text, accessibility semantics (heading-level hierarchy), SEO controls, or localization beyond the basics — this is deliberately minimal.

How to Pitch It (Stakeholders)

Executives: A small, single-purpose CMS widget for the Victoire/Symfony ecosystem. Adoption is effectively zero (2 stars, 0 dependents) and there has been no release since 2017, so it carries no vendor leverage and no community support. Recommendation: do not adopt as a dependency; treat it as a design reference at most. No budget, roadmap, or risk-register impact.

Engineering: It is a Symfony bundle — not Laravel — comprising roughly a form type, a template, and widget registration. Worth about an afternoon of reading as a pattern reference for our own block/widget contract. Not worth adding to composer.json given the abandoned state and version drift; if Victoire ever becomes a target, fork and pin it rather than depend on it.