Nova Hugerte Laravel Package

Product Decisions This Supports

• Editor choice for Nova-based back office. This package is the integration layer that lets Laravel Nova resources use HugeRTE (an MIT-licensed fork of TinyMCE) as a rich-text field. It supports the decision "our admin/CMS surface runs on Nova, and editors need a familiar WYSIWYG."
• Build vs. buy for rich text. Buying (adopting this wrapper) replaces weeks of custom editor wiring — sanitization, toolbar config, file/image handling, Nova field lifecycle — with a composer dependency. The build alternative only makes sense if editorial workflow is a core differentiator.
• Licensing strategy. TinyMCE's move to GPL/commercial licensing is a real procurement and legal question for closed-source products. Standardizing on HugeRTE via this package is a low-effort way to keep the admin editor MIT-licensed and out of license-review cycles.
• Roadmap / platform-upgrade timing. v1.2.0 adds Laravel v13 support. That's a compatibility signal, not a feature: it tells you the package intends to track the framework, which de-risks scheduling your own Laravel/Nova upgrade.
• Content-heavy use cases fit best: marketing copy, knowledge-base and help-center authoring, CMS entries, product descriptions, internal ops forms where non-technical staff write formatted text.

When to Consider This Package

Adopt when:

• You are already committed to Laravel Nova — this package has no value outside Nova.
• You need a standard WYSIWYG field quickly and don't want to maintain editor integration code yourself.
• Avoiding TinyMCE's GPL/commercial terms matters to your legal or distribution model.
• You are comfortable pinning a small, single-maintainer package and can vendor or fork it if needed (the surface area is small, so forking is realistic).
• You are planning or currently executing a Laravel 13 / Nova upgrade — v1.2.0 is the first release that explicitly claims that compatibility.

Look elsewhere when:

• You are not on Nova (Filament, plain Blade, Inertia/Vue front-ends, or headless/API-only architectures). Evaluate HugeRTE directly, or a Tiptap/ProseMirror-based stack.
• You need editorial workflow features this package does not provide: revision history, editorial approval states, structured content blocks, collaborative editing, or a managed media/asset library. Those are product decisions, not editor-field decisions, and belong in a different layer.
• You require vendor SLAs, security response commitments, or a broad contributor base. Treat this as a community dependency, not a supported platform component.
• You need front-end (non-admin) authoring — this is a Nova field, not a general-purpose editor package.

On this specific release: v1.2.0 is a compatibility-only change (Laravel v13 support, first contribution from a new contributor). No breaking changes, no deprecations, no new features. It does not change the adoption calculus — it only widens the supported framework range. Pin the version you validate against and confirm your Nova version is covered before bumping.

How to Pitch It (Stakeholders)

To executives: We can give content editors a proper rich-text experience in our admin tool for the cost of one small dependency instead of custom development. It uses HugeRTE, an MIT-licensed editor, which keeps us clear of TinyMCE's GPL/commercial licensing — a recurring legal and procurement cost we avoid entirely. Risk is contained: the package is small and replaceable, and the latest release is a compatibility update with no functional or breaking changes.

To engineering: This is a thin Nova field wrapper around HugeRTE. v1.2.0 adds Laravel v13 support and nothing else — a composer constraint change plus a new contributor's first PR. Practical guidance: pin the version, add it to the dependency-review list given the single-maintainer profile, and verify against our Nova version in CI when we move to Laravel 13. If maintenance stalls, the fork cost is low — the integration surface is a field class and a small JS asset, and HugeRTE itself is independently maintained.

To design/content stakeholders: Expect a standard WYSIWYG toolbar in Nova forms. Anything beyond formatting — approvals, versioning, shared media libraries — is out of scope for this package and should be scoped as separate product work rather than assumed as part of the editor.