- How do I install kisame76/filament-advanced-rich-editor in a Laravel Filament v5 app?
- Install it with Composer using composer require kisame76/filament-advanced-rich-editor. It is a Filament v5 form field that extends the built-in RichEditor, so you swap the field class in your form schema. Check the package README for any service provider registration or asset publishing steps, since the supplied overview does not list them.
- Does this package work with Filament v5, and will it support Filament v6?
- The package is built for Filament v5 and extends the core RichEditor field. There is no stated compatibility policy or LTS branch for Filament v6, so treat a major Filament upgrade as a breaking-change risk. Verify the current support window in the repository before adopting it.
- How do I customize the toolbar in the Filament advanced RichEditor?
- The package's main feature is a toolbar you arrange yourself, but the supplied material does not specify whether the API is a fluent typed builder or a config array. Review the README and source for the exact toolbar API and how it has changed across 1.x minors. Then configure the buttons you want per field.
- Can I use Spatie Media Library with this Filament RichEditor?
- Yes. Spatie Media Library is one implementation of the package's MediaSource abstraction, referenced alongside the ReplacesMedia interface in the v1.6.0 notes. You still need to install and configure Spatie Media Library, including disk, conversions, and queue settings. The abstraction is a pluggable seam, so you can front another media source later without forking.
- How does the media browser and document registry configuration work?
- The mediaLibraryDocuments() method and media_library.documents config declare which models and columns embed media references. That registry defines the blast radius of delete and replace operations, so enumerate every content model and column carefully. Authorization for mediaLibraryDeletable() and mediaLibraryReplaceable() must also be defined.
- Is this Filament rich text editor safe to use in production with only one maintainer?
- The package currently has around eleven stars, zero dependents, and a single maintainer, so there is little downstream validation or community troubleshooting. The release notes show engineering discipline such as translation parity tests and typed interfaces, but that is not a support commitment. Pilot it on one resource behind a flag and measure the JavaScript payload before wider rollout.
- How do find and replace and the accessibility check work in this editor?
- Find and replace is included as a toolbar feature, but the supplied material does not describe whether reference rewriting is tree-based or string-based. The accessibility check's scope is also unclear and may be heuristic linting rather than an axe-core-class audit. Do not present it internally as a compliance control until you verify it.
- Can I replace the default RichEditor with this package per field or per resource?
- Yes. Because the field extends RichEditor, it inherits the standard schema-component lifecycle including make(), state binding, validation, and Livewire dehydration. Adoption is a per-field class swap rather than a panel-level rearchitecture. That lets you introduce it resource by resource behind a flag.
- Do the slash menu and browser drafts affect performance or data residency?
- A rich editor plus media browser adds a meaningful JavaScript payload to every admin page load, so measure it. Browser drafts use client-side persistence, which raises data residency and PII questions if editors handle sensitive content. Users may also assume drafts are server-saved when they are not.
- What editor engine does this package use, and how do I track security advisories?
- The supplied material does not name the editor engine, though the slash menu, callouts, document tree, and find and replace strongly suggest Tiptap or ProseMirror. Confirm the engine and version in the bundle, who patches its advisories, and the licenses of any vendored plugins. Also ask about the package's security disclosure process before adopting it.