Weave Code
Filament Mail Templates Laravel Package
codedor/filament-mail-templates
codedor/filament-mail-templates is a Filament plugin that brings mail template management into your Laravel admin panel, letting you create, edit, and organize email templates through a simple, user-friendly interface built for Filament.
A package to create customizable mail templates in Filament
Frequently asked questions about Filament Mail Templates
- What is codedor/filament-mail-templates used for?
- It is a Filament plugin for managing customizable mail templates inside a Laravel admin panel. It gives developers and operations teams a UI to create, edit, and organize email templates instead of building custom CRUD screens. It complements Laravel's mail and notification layer rather than replacing transport, queueing, or deliverability tooling.
- How do I install codedor/filament-mail-templates in Laravel?
- Install it with Composer using composer require codedor/filament-mail-templates, then register the plugin in the Filament panel where template management should appear. After that, clear caches and verify the panel loads the mail-template management screens. For existing installations, align dependencies with your Laravel, Filament, and translatable-tabs versions before deploying.
- Does this package require Filament?
- Yes. It is a Filament admin-panel plugin, so the host Laravel application should already use Filament for back-office administration. Adopting it in a non-Filament app would also mean introducing or expanding a Filament panel, which is a larger architectural change.
- Which Laravel and Filament versions are supported?
- The v2.2.0 release notes do not publish a full compatibility matrix for PHP, Laravel, or Filament. Check the package's composer.json and README for exact constraints before updating. Pay particular attention to the Filament major version and translatable-tabs support in your target application.
- How do I register the Filament mail templates plugin?
- Register the package's Filament plugin class in the panel provider used for administration, following the package README. Then clear config and cache and confirm the mail-template management screens appear. If you use multiple panels, register it only where template editors should have access.
- Can I manage multilingual mail templates with this plugin?
- The package is intended for mail-template management, and v2.2.0 adds support for translatable-tabs v3, which points to localized template editing. Validate locale configuration and fallback behavior in your Filament panel after upgrading. Test each locale's editing and preview workflow before releasing to content teams.
- Does v2.2.0 require translatable-tabs v3?
- The release notes say v2.2.0 adds support for translatable-tabs v3, but they do not clearly state whether v2 is still supported. Confirm whether the Composer constraint is additive or now requires v3. If your host app is on translatable-tabs v2, check for dependency conflicts before running composer update.
- Are there database migrations or config files to publish?
- The v2.2.0 changelog is thin and does not describe schema changes, config publishes, or rendering changes. Review the package install docs and run migrations in a staging branch before production. Treat any unpublished migration or config step as a release checklist item.
- Can I test email template previews and test sends?
- The assessment specifically calls for regression checks on template listing, editing, localized tabs, preview, and test sends. The release notes do not confirm test coverage for localized fallback or preview behavior. Build your own staging tests around those workflows before upgrading.
- Is codedor/filament-mail-templates maintained and safe for production?
- The package is actively released at v2.2.0, but the assessment notes a thin changelog and no explicit support model. For production use, review repository activity, issue response, and your team's ability to pin and patch dependencies. Treat it as a low-risk plugin with low-to-moderate dependency risk, not as a fully documented enterprise support product.
Weaver
How can I help you explore Laravel packages today?