Poll Widget Laravel Package

Product Decisions This Supports

• Build vs. buy vs. fork for a polling/voting capability. This package represents the "buy" (really "adopt") option for a single, narrow feature: an editor-facing poll widget placed into CMS content. Weigh it against a 1–3 day in-house build or a paid SaaS embed (e.g., a survey tool with an embeddable widget), which typically wins on analytics, targeting, and consent handling.
• Roadmap scoping for engagement features. Polls are usually a "nice to have" in a content/engagement roadmap, not a differentiator. This package confirms the feature is small enough that it should be scoped as a thin slice, not a platform investment.
• CMS platform strategy. The package is a Symfony bundle for Victoire CMS, not a Laravel package. Adopting it is effectively a decision to keep Victoire in the stack. If Victoire is in scope for the next 12–24 months, this is a cheap way to add interactive content for editors; if not, this is a non-starter and should be closed out.
• Editor autonomy / content-ops investment. A widget means non-technical editors can launch polls without engineering tickets. That has real value in content-heavy orgs and should be measured against the ongoing cost of owning unmaintained code.
• Maintenance-budget justification. With a last release of 2016-10-07, 1 star, and 0 dependents, this is a de facto abandoned dependency. The decision is not "adopt" but "adopt-and-own," which must be priced in as a permanent maintenance line item.

When to Consider This Package

Consider it only when all of the following hold:

• The product already runs Victoire CMS on Symfony, and the widget ecosystem is already wired in (this package is a widget plugin, not standalone functionality).
• The need is a simple, short-lived, single-question poll for editorial content — not surveys, branching logic, segmentation, or reporting.
• You are comfortable vendoring or forking under MIT and accepting full ownership: security patching, Symfony major-version upgrades, PHP version bumps, and accessibility fixes.
• The expected lifespan of the feature is bounded (e.g., a campaign or a season), so you can ship and retire it rather than maintain it indefinitely.
• A time-boxed spike (≤2 days) confirms it installs and works against your current Symfony/PHP versions; the 2016 release predates several Symfony majors and modern PHP.

Look elsewhere — or build in-house — when:

• The stack is Laravel or a modern Symfony app. The framework mismatch alone disqualifies it; a small Laravel package or a Livewire/Inertia component is a better fit if the product is Laravel, and this repo provides no Laravel integration.
• You need analytics, response export, deduplication, bot/abuse protection, or multi-language support — none of which a 2016 widget should be assumed to provide.
• GDPR/consent, accessibility (WCAG), or security review is a requirement. An unmaintained dependency with no dependents and no recent commits will not pass a modern review, and you will own the remediation.
• Community health matters — no stars, no dependents, and nine years of silence mean no upstream fixes. Any bug is your bug.
• You are evaluating this as part of a standardized vendor/dependency policy; it will fail typical thresholds (release recency, maintainer activity, adoption).

How to Pitch It (Stakeholders)

To executives: This is a small, MIT-licensed poll widget for the Victoire CMS. It is not a strategic asset — it is a shortcut. The package was last released in 2016, has essentially no users or maintainers, and is built for a specific Symfony CMS rather than our stack. If we want polls inside editorial content, the realistic options are (a) a short in-house build or a paid embeddable survey tool, both of which we control and can support, or (b) this widget, which we would have to fork and maintain ourselves indefinitely. My recommendation is to treat this as not a buy and either build the thin slice in-house or use a SaaS embed, unless we have a committed near-term plan to stay on Victoire.

To engineering: It is a Symfony bundle for Victoire, not a Laravel package — framework fit is the first gate. Health signals are poor: one star, zero dependents, last release October 2016, low composite score. If we proceed anyway, plan to vendor it, pin it, isolate it behind our own interface so it can be swapped, and budget for ongoing patching. A one-to-two day spike should confirm compatibility with our Symfony and PHP versions before we commit; if the spike is not clean, stop.