Fieldtype Richtext Laravel Package

Product Decisions This Supports

• Feature Expansion for CMS/Editorial Tools:

  • Enable structured rich-text content (e.g., marketing pages, blogs, or documentation) with WYSIWYG editing (tables, images, links, custom tags) while maintaining structured data storage (XML format).
  • Replace or augment existing plain-text or basic HTML fields with a feature-rich editor to improve content quality and authoring experience.

• Roadmap Priorities:

  • Phase 1: Integrate into Ibexa DXP (or a Laravel-based CMS) to replace legacy text fields with a modern, extensible RTE.
  • Phase 2: Leverage custom tags/plugins (e.g., embeds, callouts) to differentiate from generic editors like TinyMCE or CKEditor.
  • Phase 3: Extend with AI-assisted content suggestions (e.g., auto-formatting, tone adjustments) by hooking into the editor’s API.

• Build vs. Buy:

  • Buy: Avoid reinventing a WYSIWYG editor with structured data storage (XML schema, validation, and Ibexa’s ecosystem integrations).
  • Customize: Extend Ibexa’s existing plugins (e.g., tables, images) or add domain-specific tools (e.g., legal disclaimers, product highlights) via custom tags.
  • Avoid: Rolling out a vanilla TinyMCE/CKEditor without Ibexa’s structured data layer or content modeling capabilities.

• Use Cases:

  • Enterprise CMS: Replace ezplatform/ezpublish or Laravel-based CMS text fields with a scalable, enterprise-grade RTE.
  • Multi-language Support: Use Ibexa’s siteaccess-aware linking for localized content (e.g., internal links to translated pages).
  • Compliance/Structured Data: Enforce XML schema validation for regulated industries (e.g., healthcare, finance) where content must adhere to strict formats.
  • Headless CMS: Serve structured rich-text via APIs for frontend frameworks (React, Vue) while keeping editing in Ibexa’s UI.

When to Consider This Package

• Adopt If:

  • You’re using Ibexa DXP or building a Laravel-based CMS and need a rich-text field type with structured data storage (XML).
  • Your team requires deep customization of the editor (e.g., custom plugins, validation rules, or UI tweaks) beyond what TinyMCE/CKEditor offers out-of-the-box.
  • You need enterprise features like:
    • Multi-site/multi-language support (via Ibexa’s siteaccess system).
    • Schema validation (XML-based) for structured content.
    • Seamless integration with Ibexa’s content modeling (e.g., linking fields, versioning).
  • Your content authors require advanced formatting (tables, nested lists, custom tags) with user-friendly tooling (e.g., image editing, link balloons).

• Look Elsewhere If:

  • You’re not using Ibexa DXP or Laravel/Symfony: This package is tightly coupled to Ibexa’s ecosystem. Alternatives like TinyMCE, CKEditor, or Quill may suffice for generic needs.
  • You need real-time collaboration: Ibexa’s RTE lacks Google Docs-style co-editing (consider CKEditor 5 Collaborative Comments or OnlyOffice).
  • Your budget cannot accommodate Ibexa’s licensing (dual GPL/Ibexa BUL). The GPL license may be restrictive for commercial closed-source projects.
  • You prioritize minimal setup: Ibexa DXP requires complex installation (vs. standalone packages like laravel-tinymce).
  • You need markdown support: This package is HTML/WYSIWYG-only; consider EasyMDE or ProseMirror for markdown.

How to Pitch It (Stakeholders)

For Executives:

*"We’re evaluating ibexa/fieldtype-richtext to modernize our content creation workflow. This package provides a premium WYSIWYG editor (tables, images, custom tags) integrated with Ibexa DXP, ensuring structured, validated content while reducing reliance on manual HTML. It aligns with our roadmap to:

• Improve author productivity with a user-friendly, feature-rich editor (vs. legacy text fields).
• Future-proof our CMS with enterprise-grade features (multi-language, schema validation, API-first output).
• Cut development time by leveraging Ibexa’s proven ecosystem (no need to build a custom editor from scratch). The dual GPL/Ibexa BUL license ensures compliance while allowing commercial use. ROI: Faster content updates, better quality, and scalability for global teams."*

For Engineering:

*"This is a batteries-included RTE solution for Ibexa DXP/Laravel, offering:

• Structured XML storage (not raw HTML) for predictable data modeling.
• Extensible plugins (tables, images, custom tags) with active maintenance (recent 5.x releases).
• Symfony/Laravel compatibility (uses Symfony 7.4 LTS) and Ibexa’s content API for seamless integration.
• Performance: Optimized for large-scale content (e.g., multi-language sites). Trade-offs:
• Tight Ibexa coupling: Not a drop-in for generic Laravel apps.
• Licensing: GPL requires open-sourcing if not using Ibexa BUL. Recommendation: Use for CMS projects where structured rich-text is critical. Pair with Ibexa’s content modeling for maximum value."*