Nova Quill Field Laravel Package

Product Decisions This Supports

• Feature enablement (build vs. buy): A Quill-based WYSIWYG field for Laravel Nova that shortens the path to rich-text authoring in admin resources — CMS pages, blog posts, FAQs, product descriptions, internal docs. The buy side is credible because the integration surface is one field declaration plus one longText column; the realistic saving is days, not a sprint.
• Roadmap unblocking: Right call when rich-text editing is supporting capability, not a differentiator. It lets an internal-tool or admin-workflow roadmap proceed without committing product and engineering time to editor infrastructure or a bespoke Quill/Nova integration.
• Scope containment: Architecturally it is a UI convenience only — not a content platform, sanitization layer, media pipeline, or public-facing editor strategy. Scope it as a tactical component inside one or a few Nova resources and the risk stays bounded and reversible.
• Explicit product requirements the package does not solve (budget for these): server-side HTML sanitization at write time, a plain-text companion column for search/excerpts/word counts, an image-handling policy (Quill's default inserts base64 data URIs — disable or replace it), validation that measures stripped text rather than markup, and content QA. If Nova draft resources are in scope, require 0.1.2+ for the draftId attachment fix.
• Strategic caution as a decision input: 4 stars, 0 dependents, single 0.x line, last release May 2023. Treat it as a tactical accelerator with a planned exit path, not a platform bet. Adopt only where the blast radius is small enough that fork-or-swap remains feasible.
• Known behavior to design around: Quill normalizes markup on round-trip — it strips classes, most inline styles, and unsupported elements, and merges adjacent tags. Imported legacy or Word-pasted HTML visibly changes the first time someone opens and saves, so decide up front whether imported content enters this field at all.

When to Consider This Package

• You are already on Laravel Nova and need a working WYSIWYG field without custom editor work.
• Requirements are simple: basic rich text, HTML storage, admin-side editing, and a small number of editors and resources.
• Blast radius is limited — one or a few Nova resources — so replacement or forking stays cheap.
• You accept the stale maintenance signals and are prepared to pin the exact version, smoke-test on every Nova upgrade, and patch locally if needed.
• You can fund the surrounding work: sanitization (purifier + allowlist + write-time mutator or observer), a derived content_text column, image-upload handling or a disabled image button, and validation rules.
• You can live with Quill's HTML normalization and will keep ->onlyOnForms() / ->hideFromIndex() so index pages don't render heavy HTML per row.
• Look elsewhere if: you need active maintenance or security responsiveness; rich-text authoring is customer-facing, publicly visible, or business-critical; you need accessibility guarantees, advanced media/embeds, or collaboration; you are not on Nova; Nova's native fields or a better-maintained package already meet the need; or your first use case is user-submitted content displayed publicly — stop and resolve XSS and image handling before shipping.

How to Pitch It (Stakeholders)

• Executives: A low-cost, low-commitment way to add rich-text editing to our Nova admin and avoid custom development for routine content workflows. It unblocks admin tooling without platform investment. Treat it as a tactical accelerator, not a strategic platform choice — validate maintenance risk before any wider rollout, and fund the sanitization work that keeps stored HTML safe across API, mail, and RSS consumers.
• Engineering: The package wraps Quill as a single Nova field — a thin Quill PHP class plus a Vue component, no service provider, no migrations, one column, one field declaration. Integration is straightforward, but adoption is near zero and the last release is from 2023, so: pin the exact version, isolate usage behind a field subclass (presets via withMeta()), sanitize on write rather than only on render, disable or replace the base64 image handler, add the plain-text companion column, and keep a fork-or-swap fallback (override component() or swap the field). Test the create/draft attachment flow separately from edit, and smoke-test on every Nova major upgrade — check the compiled dist assets are being served.
• Recommendation: Pilot in one internal, admin-only resource with a detail-page render. If it meets the need, document the exit path and the tested Nova/PHP version matrix; if requirements grow beyond basic editing, evaluate maintained alternatives or build a thin internal wrapper around Quill directly.