Rich Editor Fullscreen Laravel Package

Product Decisions This Supports

• Editor UX investment in admin surfaces. If your product has a content-authoring surface built on Filament (CMS, blog/marketing console, knowledge base, support macros, internal ops tools), this package directly answers "is a fullscreen writing mode worth shipping?" — it's one Composer dependency instead of a frontend sprint.
• Build vs. buy for narrow editor extensions. Concrete data point for the ledger: an in-house Tiptap/ProseMirror fullscreen toggle is days of JS + CSS plus perpetual upkeep against Filament upgrades; this is MIT and installs in an afternoon. Bias toward buy for anything this narrow and this removable.
• Roadmap sequencing — polish vs. features. Lets you slot a visible, low-cost UX win into a release without displacing roadmap commitments. Useful when editor complaints appear in tickets but don't justify a dedicated epic.
• Scope control on "better editor" requests. A fullscreen toggle absorbs much of the "the editor is too cramped" feedback without committing to a rich-text overhaul (collaboration, media library, custom blocks). Use it as a cheap stopgap while the real editor roadmap stays deferred.
• Vendor-risk posture. A 9-star package with 0 dependents is a deliberate low-blast-radius bet: it touches one field's presentation layer, is trivially removable, and can be forked. A reasonable vehicle for exercising your team's small-dependency process before adopting bigger ones.
• Adoption/contribution signal. Zero dependents and a single maintainer means you'd likely be an early production user — factor in whether you contribute back (e.g., PRs for Filament V5 compatibility) or vendor a fork.

When to Consider This Package

Adopt when:

• You are on Filament V4 and already use RichEditor for long-form content where default field height is the bottleneck (articles, policy docs, email bodies, ticket replies).
• Authoring happens in constrained layouts — modals, slide-overs, sidebars, narrow columns — where fullscreen materially changes writing comfort.
• Your team has no frontend capacity to build and maintain a Tiptap fullscreen extension, or the work would be perpetually deprioritized.
• The requirement is genuinely "make the field bigger," not "give me a richer editor."
• You can pin the version and accept that a Filament major upgrade may require a fork or patch.

Look elsewhere / skip when:

• You are on Filament V3 or a non-Filament stack (Livewire-only, Nova, custom admin) — the package is scoped to V4 RichEditor.
• You need real editor capability: collaborative editing, comments, asset management, markdown round-tripping, custom node types, slash commands. Fullscreen is cosmetic by comparison and won't move the satisfaction needle.
• Procurement or security review requires maintained, widely-adopted dependencies — 9 stars, 0 dependents, one maintainer will not clear a stricter bar.
• The underlying problem is page design. If editors are cramped because the admin layout wastes screen width, fix the layout; a per-field fullscreen toggle is a band-aid.
• You need vendor SLAs, support contracts, or guaranteed upgrade paths.
• You'd rather consolidate on a broader editor package that already bundles fullscreen with other features.

Due diligence before committing: the listed last-release date (2026-09-27) is inconsistent with a normal cadence — verify the tag, read the diff, and confirm it works against your Filament patch version. Treat the package as a pilot: install behind a feature flag, validate in staging, and budget a 1–2 day fork-and-maintain fallback.

How to Pitch It (Stakeholders)

Executives: Our content and operations teams write long-form text inside the admin app, in fields that are physically small on screen. This is a free, MIT-licensed add-on that gives that editor a fullscreen mode — a visible quality-of-life improvement for the people producing content, installable in a day with no infrastructure change and no vendor contract. It is a narrow, fully reversible dependency that improves authoring speed and removes low-grade friction complaints without touching the roadmap. It is not a platform bet; it is polish we can ship this sprint and remove in an hour if it disappoints.

Engineering: Add mdobes/rich-editor-fullscreen via Composer, register the plugin on the relevant panel(s), pin the version, and confirm behavior against our Filament V4 patch level. Expect no custom JS to maintain and no database changes. Caveats to record in the PR: single maintainer, 9 stars, 0 dependents — so pin it, isolate it behind a feature flag if the surface is customer-facing, and keep a small fork budgeted if a Filament upgrade breaks it. If review rejects the dependency, the fallback is a scoped CSS/JS tweak on the existing RichEditor — roughly 1–2 days of frontend work plus ongoing upkeep.

Design/Product: Frame it as "authoring comfort," not "new editor." Success looks like fewer complaints about the writing surface and faster time-to-publish for long-form content; it does not unlock new content types or workflows, and it should not be sold as such.