Statamic Tinymce Cloud Laravel Package

Product Decisions This Supports

• Build vs. buy for rich-text editing: Confirms whether to adopt TinyMCE Cloud (hosted, API-keyed editor) as the authoring surface inside Statamic's Control Panel rather than building or maintaining a custom WYSIWYG.
• Editor standardization across content types: Informs whether writers get a consistent, vendor-supported editing experience for entries, globals, and other publish forms — one config surface instead of per-field bespoke setups.
• Vendor dependency / licensing decisions: TinyMCE Cloud is a paid, key-gated SaaS. This package makes the integration trivial, which shifts the real decision to editor licensing, API-key management, and domain allow-listing — budget and procurement inputs, not engineering effort.
• Roadmap scoping for version 4.x: This release (4.0.2) only adjusts the Vue setup — i.e., how the addon's Control Panel assets are wired. Treat it as build/tooling hygiene: no breaking changes, no new features, no deprecations. No migration work, no user-visible behavior change, no re-testing of authoring workflows required beyond a smoke test of the fieldtype in the CP.
• Upgrade planning: 4.0.2 is a safe patch bump. If the team is already on 4.0.x, it can ride along with routine maintenance; it does not justify a dedicated release window.

When to Consider This Package

Consider it when:

• You run Statamic (v4/v5-era Control Panel) and want TinyMCE Cloud as the editor for one or more fieldsets without writing a custom fieldtype.
• You already have (or are willing to buy) a TinyMCE Cloud API key, and accept the SaaS dependency for the editing experience.
• You want minimal integration surface — configuration over custom code — and are comfortable relying on a small, single-maintainer addon.
• You are on the 4.x line and need a low-risk patch; 4.0.2's Vue setup change is a drop-in.

Look elsewhere when:

• You need a fully self-hosted / air-gapped editor (TinyMCE Cloud requires outbound access and a key) — prefer self-hosted TinyMCE or a Redactor/Bard/ProseMirror-based path.
• You require long-term vendor support, SLAs, or multiple maintainers — this is a community addon; assess bus-factor risk.
• Your editing needs are structural/content-modelling rather than freeform HTML — Statamic's native Bard set may be the better default.
• You are on a pre-4.x version — the 4.x line implies a Statamic/PHP baseline change; verify compatibility before assuming this patch applies.

How to Pitch It (Stakeholders)

For executives: This is a small integration package that lets our Statamic CMS use TinyMCE Cloud as its editor. The business decision isn't the package — it's the TinyMCE Cloud subscription and the editorial experience it buys us. The latest release (4.0.2) is a maintenance patch with no functional or breaking changes, so there's no cost, risk, or migration impact from taking it.

For engineering: mitydigital/statamic-tinymce-cloud wires TinyMCE Cloud into Statamic's Control Panel as a configurable fieldtype. 4.0.2 changes only the Vue asset setup (PR #21) — no public API, config schema, or behavior changes; a routine composer update plus a quick CP smoke test is sufficient. The notable operational dependency is the TinyMCE Cloud API key and its domain allow-list, which should be managed as a secret per environment. Track the addon's maintenance cadence given its single-maintainer profile, and keep a fallback editor path in mind if the upstream project stalls.