Picturecomparator Widget Laravel Package

Product Decisions This Supports

• Choosing an image-comparison interaction pattern. A "picture comparator" is the before/after slider (draggable handle revealing two overlaid images). This package represents one implementation of that pattern and is useful mainly as a reference for requirements: drag handle, touch support, responsive sizing, keyboard/accessibility behavior, alt text per image, and editor-configurable labels.
• Build vs. buy scoping. The honest answer here is "build small or buy a JS component." The core interaction is a well-solved front-end problem; a handful of mature JS libraries (img-comparison-slider, BeerSlider, Juxtapose) cover it in a few KB. This package does not represent a meaningful buy option.
• CMS editor experience decisions. Its real scope is narrow: it lets a content editor drop a comparator widget into a page inside Victoire CMS (a Symfony CMS) without developer involvement. That is a content-ops decision, not a product-platform decision — relevant only if your editors need to self-serve this block.
• Framework fit check — an important correction. Despite being catalogued as a "Laravel/PHP package," this is a Symfony bundle tied to the Victoire CMS. It has no Laravel service provider, no Blade views, no Laravel integration surface. Any roadmap item that assumes "drop this into a Laravel app" is based on a false premise and should be corrected before it reaches a sprint.
• Not a roadmap enabler. With 1 GitHub star, 0 dependents, and no release since May 2018, it carries no ecosystem signal. Its adoption (or not) tells you nothing about market demand for the feature.

When to Consider This Package

Consider it only if all of these are true:

• You are already running Victoire CMS on Symfony, and the widget registry/asset pipeline is already in place.
• The need is genuinely editor-facing: non-technical staff must insert before/after comparisons without a deploy.
• You have accepted that the code is unmaintained since 2018 — PHP 7-era, likely Symfony 2/3-era APIs — and you are prepared to vendor/fork and patch it yourself for PHP 8 and current Symfony.
• Your security review tolerates an abandoned, single-maintainer dependency in the content-rendering path.

Look elsewhere in essentially every other case:

• Any Laravel application — this does not integrate. Add a JS comparator library and a Blade partial (roughly half a day of work, including accessibility and responsive handling).
• Any modern Symfony app (Symfony 5+) — the Victoire widget contract and this bundle's era are a mismatch; the integration cost likely exceeds a from-scratch Twig block.
• You need it maintained, patched, or supported — there is no release cadence, no dependents, and no visible issue triage. Treat it as archived code you found, not a dependency you adopt.
• You need analytics, A/B testing, lazy loading, or CDN image variants on the comparator — none of that is in scope here; you would be wrapping it anyway.

Low score (0.035) interpretation: the score is consistent with a dormant, single-purpose CMS widget with no downstream adoption. It should not be read as "low quality code" so much as "no evidence of viability."

How to Pitch It (Stakeholders)

For executives — one line: This is an abandoned 2018 widget for a niche Symfony CMS; we should not take it on as a dependency, but the interaction (before/after image slider) is worth ~1 day of in-house work if a customer-facing use case appears.

For engineering:

• Correct the framing first: this is a Victoire/Symfony bundle, not a Laravel package. There is no integration path into our Laravel stack.
• Health check: last release 2018-05-24, 1 star, 0 dependents, no maintenance signal. Adopting it means adopting ownership of every future PHP/Symfony compatibility fix.
• Recommendation: do not adopt. If the before/after pattern is on the roadmap, ship it as an ~80-line Blade/Twig component wrapping a maintained JS comparator, which gives us Laravel/Vite integration, lazy loading, alt-text enforcement, keyboard accessibility, and analytics hooks — all of which this package lacks.
• Effort comparison: wrapper build ≈ 0.5–1 dev-day and no ongoing maintenance risk; retrofitting the bundle to a current PHP/Symfony runtime ≈ 2–5 dev-days plus indefinite ownership.

Decision to record: Not adopted — architectural mismatch (Symfony/Victoire, not Laravel) plus abandonment risk. Keep as a UI reference only; revisit the underlying interaction as a first-party component if a concrete use case (real estate, renovation, cosmetic/aesthetic, insurance claims, photo editing) enters the roadmap.