Redactor Widget Laravel Package

Product Decisions This Supports

• Build vs. buy for rich-text editing: This package is the "buy/adopt" option only inside the Victoire DCMS ecosystem — and it's a dormant one. Use it as evidence to build or select a maintained editor rather than adopt this wrapper.
• Roadmap and migration scoping: If any legacy Victoire/Symfony surfaces exist in the portfolio, treat this as an inventory item for migration, not a foundation for new features. It informs how much editor parity work a migration will require.
• Platform fit check: Despite the "Laravel/PHP" framing, this is a Symfony bundle for Victoire DCMS, not a Laravel package — no service provider, no Laravel-facing API. It should not enter a Laravel build-vs-buy evaluation at all.
• Use-case validation: The only scenario it serves is extending an existing Victoire instance that already uses Imperavi Redactor and needs matching widget UX. That's a narrow, legacy-only use case.
• Risk and cost modeling: 2 stars, 0 dependents, last release 2016-11-10 signals abandonment. Also note Redactor itself is commercial — the "free" wrapper doesn't remove license cost, so total cost of ownership includes a paid editor license plus fork maintenance.
• Feature prioritization: Editor requirements (accessibility, mobile, paste handling, sanitization, collaborative editing) are better served by actively maintained editors; this package sets the baseline at 2016 capabilities.

When to Consider This Package

Consider it only when all of the following hold:

• You are maintaining an existing Victoire DCMS application that already depends on Redactor widgets.
• You are pinned to the 2016-era Symfony/PHP versions this bundle targets and have no near-term upgrade path.
• You need UX parity with existing content-editing workflows and are willing to fork and own maintenance.
• You already hold a valid Redactor license.

Look elsewhere when:

• You're building on Laravel — there is no native integration; use a first-class Laravel/Filament/Nova editor integration instead.
• You need PHP 8+, Symfony 5+, or Laravel 10+ compatibility, security patching, or any form of vendor support.
• You need modern editor capabilities: accessibility, mobile-first UX, structured/headless content, multi-language, or sanitization guarantees.
• You don't already own a Redactor license — start with CKEditor 5, Tiptap, TinyMCE, or Quill and evaluate commercial licensing separately.
• You want a dependency with an active maintainer and a release cadence you can plan around.

How to Pitch It (Stakeholders)

For executives: Recommendation is do not adopt. There is no adoption cost and no ongoing support burden — which is exactly the point: this is a 2016 Symfony/Victoire widget wrapper with 2 stars, zero dependents, and no release in nearly a decade. Adopting it creates a fork-and-own liability and locks editor UX to a dormant codebase. Redirect the effort to a maintained editor with clear ownership and an explicit licensing line item.

For engineering: This is a Symfony bundle for Victoire DCMS, not a Laravel package; integrating it into our stack would mean a fork plus an upgrade campaign before the first feature ships. It wraps Imperavi Redactor, so a commercial license is still required. Treat it as legacy inventory only — if a Victoire instance exists, catalog it as a migration dependency; otherwise exclude it from the dependency review.

Proposed next step: One-to-two week spike comparing CKEditor 5 and Tiptap against our editor requirements (accessibility, mobile, sanitization, licensing), with a decision memo on build vs. buy for the editor layer.