Richlist Widget Laravel Package

Product Decisions This Supports

• Editorial content-block roadmap (Victoire DCMS only). This is a widget that gives content editors a reusable "rich list" block — formatted bullet/numbered lists with inline styling — inside Victoire's page-builder. If your roadmap includes "editors can compose richer landing pages without developer help," this is a small, pre-built increment toward that goal, at zero licence cost.
• Build vs. buy for a single UI component. If you are already on Victoire, the build cost of a list widget is low but non-zero (widget registration, form type, template, tests). Adopting an MIT-licensed package is the cheaper path only if it still works with your Victoire/Symfony version.
• Scope triage / deprioritisation signal. Zero stars, zero dependents, and a last release in August 2016 are strong evidence that this component has no community momentum. That is itself a product decision input: it should not become a dependency you plan a roadmap around, and it should never be a blocker for a launch.
• Platform-ecosystem fit check. A useful forcing function: this is a Symfony/Victoire package, not a Laravel one. The decision it most directly supports is "are we standardising on Laravel, or do we have legacy Victoire/Symfony surfaces we still need to serve?" — which is a portfolio question, not a feature question.
• Legacy maintenance budgeting. If a Victoire site is in your estate, this is one more unmaintained leaf dependency to account for in refresh/upgrade planning.

When to Consider This Package

Adopt it only when all of the following hold:

• You actively run a Victoire DCMS site (Symfony-based), and editors have a validated, repeated need for formatted list blocks.
• Your Victoire/PHP versions are pinned close enough to 2016-era Symfony that the widget's form type and template contracts still resolve — or you are willing to fork and maintain it yourself.
• The alternative (a custom widget, or a generic rich-text block) genuinely costs more than forking this one.
• You accept that you will be the maintainer. With no stars, no dependents, and no release since 2016, there is no upstream support, no security patching, and no one to escalate to.

Look elsewhere when:

• You are a Laravel shop. This package will not integrate without building a bridge that costs far more than the component is worth. Use a native Laravel solution — Filament/Blade components, a Nova field, or a rich-text editor (Tiptap, ProseMirror) with list support — and treat this repo as a UX reference only.
• You need a maintained dependency with an SLA, security disclosure process, or an active maintainer.
• You are on a modern CMS (Statamic, Craft, Wagtail, Contentful, Storyblok) — the list-block need is already covered natively.
• Your list formatting requirements are simple enough that a rich-text field with list support eliminates the widget entirely.

How to Pitch It (Stakeholders)

For executives: This is a tiny, free, MIT-licensed widget for a niche Symfony CMS called Victoire. It lets editors insert formatted list blocks into pages. It costs nothing to licence, but it has had no release since 2016, no stars, and no known users — so the real cost is the engineering time to keep it alive. Recommendation: do not adopt as a strategic dependency. It is only worth touching if we already own a Victoire site that needs the capability.

For engineering: Scope it as a fork-and-own, not a dependency. Expect to validate widget registration, form types, and templating against our Symfony version; expect zero upstream patches; budget a small maintenance line if we ship it. If we are on Laravel, decline — the integration cost dwarfs the component.

Bottom line: a low-risk, low-value component. Green-light only inside an existing Victoire footprint; otherwise close it out and move on.