Tinymce Nova Laravel Package

Product Decisions This Supports

• Build vs. buy for admin rich text: A maintained Nova field that wraps TinyMCE removes the need to hand-roll an editor integration (asset loading, lifecycle, config plumbing) for internal content authoring. v1.2.2 makes the "buy" case stronger because the reliability work is exactly the unglamorous maintenance a team would otherwise absorb.
• Upgrade readiness (Laravel 13 / Nova 5): The release is validated against Laravel 13 and Nova 5, so it can be used as evidence in planning the framework/admin upgrade roadmap rather than a blocker to be scheduled around.
• Editor availability as a product risk: Local-or-CDN script loading, shared concurrent loads, and an editable fallback on failure/timeout convert a hard failure ("editor won't load, content can't be edited") into a degraded-but-usable state. This supports decisions about acceptable uptime/SLO for internal tooling without building custom resilience.
• Content fidelity for editorial workflows: Preserving paragraph/list line breaks in Nova's detail view and restoring the labeled detail row means reviewers and approvers see content as authored. That supports decisions to use Nova detail views for review/QA steps instead of pushing reviewers into a separate preview.
• Configuration flexibility: Correct defaults when switching between local and CDN sources lets us decide per-environment (e.g., CDN in production, local/self-hosted where egress or CSP restricts external assets) without code changes.
• Low-risk incremental adoption: Stored recipe content is unchanged and tests cover lifecycle behavior — no data migration or content backfill is implied, so this can ship in a routine release rather than a coordinated migration.
• Lifecycle cleanup during navigation reduces stale-editor bugs in long editing sessions, which supports keeping multi-field, multi-tab content forms in Nova rather than splitting them into separate screens.

When to Consider This Package

Adopt when:

• The product needs rich text authoring inside Laravel Nova (Nova 4/5) and the team wants a field, not a bespoke front-end integration.
• You are on, or planning, Laravel 13 / Nova 5 and want a dependency already validated there.
• Your environments differ in asset delivery (CSP restrictions, air-gapped or egress-limited setups vs. CDN), and you need configurable local vs. CDN sourcing with sane defaults.
• Editorial review happens in Nova detail views, so display fidelity (line breaks, labeled rows) matters to the workflow.
• You want predictable failure behavior — an editable fallback beats a blank field when a third-party script is slow or blocked.

Look elsewhere when:

• The admin surface is not Nova (Filament, custom Vue/Inertia, headless CMS) — this field is Nova-specific.
• You need structured/block-based editing, collaborative editing, or review/approval state machines — TinyMCE is a classic WYSIWYG; those are separate product bets.
• You require a content sanitization/security policy beyond the editor (server-side HTML sanitization, allowed-tag governance). This package is not positioned as that control; treat sanitization as a separate decision.
• You need file/media management or upload pipelines as a first-class capability — evaluate the broader editor/media stack, not this field alone.
• Your team cannot accept a third-party admin dependency in the critical authoring path (e.g., strict vendor-review or long-term-support requirements).

How to Pitch It (Stakeholders)

To executives: This is a small, low-risk maintenance release for the rich-text editor in our admin tool. It doesn't change stored content or require a migration; it reduces the chance that content editors get blocked by an editor that fails to load, and it's already verified against our next Laravel/Nova versions. Net effect: less internal-tooling downtime and a smoother platform upgrade.

To engineering: v1.2.2 is a bug-fix release — no breaking changes, no schema or stored-content impact. It hardens the TinyMCE field: local-or-CDN script loading with shared concurrent loads and an editable fallback on timeout/failure, initialization tied to field readiness, saving current editor content and reliable instance teardown on navigation, correct config forwarding and defaults when switching sources, and restoration of Nova's labeled detail row with escaped-text line-break preservation. Coverage includes editor lifecycle tests, Nova field tests on Laravel 13/Nova 5, browser smoke tests, and production asset builds. Recommended action: bump the dependency in the next routine release and confirm the local-vs-CDN setting per environment; no coordinated rollout needed.