Block Bundle I18N Laravel Package

Product Decisions This Supports

• Multilingual CMS/Editorial Workflows: Enables dynamic, inline-editable HTML blocks with native i18n support, reducing reliance on third-party SaaS tools (e.g., Storyblok, Contentful) for localized content management.
• Composable UI for Marketing Teams: Accelerates A/B testing, localized landing pages, or promotional content by allowing non-technical users to edit blocks directly in the frontend (via TinyMCE).
• Legacy System Modernization: Justifies "build vs. buy" for teams maintaining Symfony 3.x apps by avoiding costly migrations to newer stacks (e.g., Symfony 6+) while adding i18n capabilities.
• Roadmap for Decoupled Architectures: Serves as a proof-of-concept for headless CMS patterns, where editable blocks could later be exposed via GraphQL/REST APIs.
• Localization at Scale: Supports markets with 10+ languages by leveraging a2lix/translation-form-bundle for granular translation management (e.g., per-block, per-field).

When to Consider This Package

• Avoid if:
  • Modern Stack Required: Using Symfony 4/5/6+ (package is abandoned; Symfony 3.x only).
  • Active Maintenance Needed: No updates since 2017; risk of compatibility issues with newer PHP/Symfony versions.
  • Advanced Features Needed: Lacks modern features like:
    • Collaborative editing (e.g., real-time cursors).
    • Versioning/history tracking.
    • Plugin ecosystems (e.g., Figma/CMS integrations).
  • Alternative Exists: Prefer established solutions like:
    • Symfony UX Turbo (for live updates) + EasyAdmin (for admin panels).
    • CKEditor 5 or TinyMCE Cloud for standalone WYSIWYG.
    • API-first CMS (e.g., Strapi, Directus) if decoupling is the goal.
• Consider if:
  • Symfony 3.x Constraint: Must stay on this legacy version for business/cost reasons.
  • Quick Prototyping: Need a lightweight, multilingual block editor without heavy dependencies.
  • Internal Tooling: Building a niche editorial system (e.g., for intranets) where customization outweighs maintenance risks.

How to Pitch It (Stakeholders)

For Executives:

"This package lets our marketing team edit localized HTML blocks directly in the browser—no dev hand-offs—while keeping costs low. Think of it as a lightweight, self-hosted alternative to $10K/year CMS tools. Since it’s tied to our existing Symfony 3.x stack, it avoids migration risks. The trade-off? We’d need to monitor for updates (none in 6 years), but for a proof-of-concept or internal tool, it’s a high-leverage bet."

Key Ask: "Approvals to allocate 2 dev weeks for integration and a plan to sunset/replace it in 12–18 months if we scale."

For Engineering:

"This is a Symfony 3.x-only fork of ArkounayBlockBundle with i18n via a2lix/translation-form-bundle. It gives us:

• Inline TinyMCE editing for HTML blocks (like a mini-CMS).
• Multilingual support at the block/field level (e.g., translate a hero section per language).
• Doctrine behaviors for soft-deletes/timestamps out of the box.

Risks:

• Abandoned: Last release in 2017; may need forks for PHP 7.4+.
• Symfony 3.x Lock-in: Hard to upgrade later.
• Limited Features: No API layer, no collaborative editing.

Proposal:

1. Pilot: Use for a non-critical section (e.g., blog posts) to test UX.
2. Mitigate Risk: Wrap in a feature flag and plan to replace with Symfony UX + CKEditor in 2025.
3. Customize: Extend TinyMCE plugins or add a simple API layer if needed.

Alternatives:

• Short-term: Use easycorp/easyadmin-bundle + custom TinyMCE fields.
• Long-term: Migrate to Symfony 6 + API Platform + Strapi."