Button Widget Laravel Package

Product Decisions This Supports

• Legacy CMS maintenance vs. migration: This is a Symfony bundle that provides a button/CTA widget for the Victoire CMS — not a Laravel package. The decision it informs is whether to keep supporting a Victoire-based site (adding or patching CTA widgets) or to budget a migration to a maintained CMS/framework.
• Build vs. buy for a trivial UI primitive: A button widget is a ~100-line front-end component (label, URL, target, style variant, maybe an icon). The package's only real value is its integration with Victoire's block editor and templating conventions — not the button itself.
• Content-editor autonomy roadmap: If the roadmap depends on marketers composing landing pages with reusable CTA blocks without engineering involvement, this bundle is a data point on whether the current CMS can deliver that or whether an editor-experience investment is needed.
• Not a candidate for a new build: With 2 stars, 0 dependents, and no release since May 2019, this does not belong on any shortlist for new product work, Laravel or otherwise.
• Risk/technical-debt register: Any product still shipping this bundle should be flagged as carrying an unmaintained dependency (no security patching, no PHP 8/Symfony 5+ guarantees), which affects support SLAs and upgrade planning.

When to Consider This Package

Consider it only if all of the following hold:

• You are already running Victoire CMS on a compatible, pinned Symfony version, and the site is in maintenance mode rather than active feature development.
• You need the standard Victoire backend editing experience for CTA blocks and want to avoid re-implementing the widget's admin form, templates, and block registration.
• You have vendored or forked it, or you accept that you own maintenance — the upstream has been quiet since 2019.
• The scope is genuinely a button: no analytics hooks, A/B testing, localization workflows, or design-system token integration required.

Look elsewhere — i.e., write it yourself or use your design system's component — when:

• You are on Laravel, or any framework other than Symfony/Victoire. This package will not install or function there; the "Laravel/PHP package" framing is a mismatch.
• You need maintained dependencies, PHP 8.x/Symfony LTS support, or a security review trail.
• You need accessible, themeable, testable CTAs — most modern front-end stacks ship this as a component, and a CMS block is a thin wrapper over it.
• You are evaluating a CMS for a new product; the ecosystem signals here (single-maintainer, stalled releases, zero dependents) argue against building on Victoire at all.

How to Pitch It (Stakeholders)

For executives: This is a small, unmaintained add-on that renders a button inside an older Symfony-based CMS called Victoire. It is not a Laravel package and cannot be reused outside that CMS. Its adoption cost is low but its ownership cost is not: with no releases since 2019 and no downstream users, we would inherit the maintenance burden entirely. Recommendation: do not add it to any new product; if we already depend on it, treat it as technical debt and fold it into the CMS migration or replacement conversation rather than funding a standalone upgrade.

For engineering: Treat as a reference implementation, not a dependency. If we need the capability on Victoire, fork and vendor the block definition and templates (~a day of work) so we control compatibility; otherwise implement the CTA as a first-class component in our design system and expose it to the CMS through a thin, tested adapter. Either path is cheaper than absorbing an abandoned third-party bundle into our upgrade path.

Bottom line: Low opportunity, low adoption signal. The decision this package actually drives is when to leave the platform it serves — not whether to install it.