- What is jkharley/filament-trumbowyg used for?
- It provides a Trumbowyg rich-text WYSIWYG editor field for Filament forms, typically in Laravel admin panels. You can use it to give administrators a lightweight toolbar for editing HTML content. The package is aimed at Filament-based form building rather than standalone editor use.
- Does jkharley/filament-trumbowyg support Filament 3?
- Yes, the 3.0.0 release note states that it adds support for Filament 3. Treat Filament 3 as the documented target for that release. Confirm the package's composer constraints and README before installing in a mixed-version environment.
- Can I use this package with Filament 2 or without Filament?
- The available evidence points to Filament 3 support in version 3.0.0, and there is no stated justification for Filament 2 teams. It is not a justified dependency for applications without Filament unless it has separately valuable non-Filament functionality. Check the package metadata and release notes before assuming backward compatibility.
- How do I install jkharley/filament-trumbowyg?
- Installation is expected to follow the standard Composer workflow for Filament plugins, using Composer to require the package and then registering it in your Filament panel configuration. The exact service provider or plugin registration steps should be taken from the package README. Run the install in a branch or proof-of-concept environment first.
- Which Laravel, PHP, and Filament versions does this package support?
- The available release evidence only confirms Filament 3 support in version 3.0.0 and does not publish a Laravel, PHP, or Filament support matrix. You should inspect the package composer.json constraints and README before committing. Verify compatibility against your application's exact Laravel and PHP versions.
- How do I customize the Trumbowyg toolbar and buttons?
- The package description states that you can configure the editor and customize its buttons. The concrete configuration API and available button names should be confirmed in the README or package source. Test custom toolbar configurations in a non-production panel before rollout.
- Is version 3.0.0 a breaking change from earlier releases?
- The 3.0.0 release note only mentions adding Filament 3 support, but a major version bump can signal breaking changes. No upgrade guide or changelog was available in the evaluated evidence. Treat 3.0.0 as potentially breaking until you verify compatibility and regression-test existing forms.
- Can I use the editor across multiple Filament panels?
- Multiple-panel support is not documented in the available evidence, so it should be validated in your own Filament setup. Check whether the package registers global assets, routes, or panel-specific configuration that could affect multi-panel behavior. A proof of concept with each panel is the safest way to confirm.
- Is jkharley/filament-trumbowyg safe and maintainable for production?
- Production suitability depends on factors not covered in the limited evidence, including test coverage, security posture, license, maintainer responsiveness, and documentation quality. Pin the package version and track its support matrix against Laravel, PHP, and Filament releases. Run a time-boxed proof of concept and regression-test admin workflows before deploying.
- What alternatives should I consider to this Trumbowyg Filament field?
- Alternatives include Filament's built-in rich-text editor and other WYSIWYG field plugins for Filament 3. Compare toolbar features, asset size, configuration effort, maintenance activity, and compatibility with your Laravel and PHP versions. Choose based on documented support and a proof of concept rather than feature lists alone.