Filament Editorjs Laravel Package

Product Decisions This Supports

• Rich-content editing inside Filament admin panels: Supports decisions about whether to standardize editorial workflows on Editor.js block-based content (structured JSON) rather than a traditional WYSIWYG/HTML field. This matters for CMS-like admin tools, internal documentation, marketing content, and product catalogs.
• Build vs. buy for form-field integration: The package is a thin Filament adapter around Editor.js. Buying/integrating it avoids building and maintaining Filament state binding, validation integration, and Editor.js lifecycle handling in-house. The v2.0.0-beta.2 fix restoring statePath is directly relevant here — it indicates the package is still stabilizing its integration with Filament’s form-state system, which is core to save/validate/reactive behavior.
• Roadmap sequencing: If Filament is already the admin framework, this is a low-effort enabler for content-authoring features. If Filament is not already in the stack, this package should not drive an adoption decision for Filament itself.
• Risk tiering for beta dependencies: v2 remains in beta. Product should treat it as suitable for internal tools, pilots, and non-critical editorial flows until a stable 2.x release exists. Avoid committing critical publishing workflows to a beta field component without a fallback plan.
• Data-model decision: Editor.js stores structured JSON blocks, not HTML. This supports downstream reuse (web, mobile, exports) but requires a rendering layer and content-migration planning. PMs should factor in the cost of block renderers and schema evolution, not just the field component.

When to Consider This Package

Consider adoption when:

• Your team is already building on Filament and needs an Editor.js-style block editor as a form field.
• You want structured block content (JSON) rather than flat HTML, and you are prepared to own rendering and block-schema governance.
• The use case is an internal admin tool, pilot, or non-critical content workflow where a beta dependency is acceptable.
• You can pin versions, run upgrade testing, and absorb pre-GA API changes. The statePath regression fix in beta.2 shows why regression testing around form fill/save/validation is necessary.
• You need Editor.js’s block/plugin ecosystem and are comfortable managing Editor.js configuration and custom blocks yourself.

Look elsewhere when:

• You need a stable, supported, enterprise-grade editor with SLAs; this is a beta community package.
• You need a WYSIWYG/HTML authoring experience rather than block JSON.
• You are not on Filament, or you are on a Filament version not supported by the 2.x line. Compatibility must be verified before adoption.
• You need real-time collaboration, advanced publishing workflows, or built-in content rendering — this package is a field adapter, not a full CMS.
• Your team cannot tolerate pre-stable churn or does not have capacity to test form-state behavior and Editor.js output on every upgrade.

How to Pitch It (Stakeholders)

For executives: This is a small, low-cost Filament component that lets internal admin users author rich, block-based content without us building an editor integration from scratch. It can accelerate delivery of CMS-like admin features. However, the current 2.x line is still in beta; the latest release is a regression fix, not a feature release. Recommendation: pilot it on an internal or non-critical workflow, pin the version, and defer broad rollout until a stable 2.x release.

For engineering: It wraps Editor.js as a Filament form field and persists structured JSON. v2.0.0-beta.2 restores statePath, fixing form-state binding that was apparently missing in beta.1. That is important for validation, reactive fields, and saving content through Filament’s form lifecycle. Treat the beta as unstable: pin v2.0.0-beta.2, add regression tests for create/edit/save/validate flows, and verify Filament version compatibility. Expect possible breaking changes before 2.0.0 stable. Budget for a renderer and block-schema ownership; the package does not solve front-end rendering or content migration.