- How do I install Filament Mail Templates in a Laravel app?
- Install the package with Composer, register the plugin in your Filament PanelProvider, then publish and run its migrations. Because it is a Filament panel plugin, it assumes you already have a working Filament admin panel and outbound mail flowing through Laravel's mailer. A competent Laravel developer should be able to get a working prototype in under a day.
- Which Filament and Laravel versions does wotz/filament-mail-templates support?
- Verify this directly in the package's composer.json and service provider before installing. Filament v3 and v4 APIs diverge materially, and Laravel 10, 11, and 12 support matrices differ, so do not rely on implied compatibility. The available summary does not declare a definitive version matrix.
- How do dynamic variables work in Filament Mail Templates?
- The package is designed for reusable mail templates with dynamic variable interpolation, so editors can update transactional emails without code changes. Before relying on it, confirm the exact placeholder syntax and whether the variable namespace is whitelisted. Also check how missing or undefined variables are handled: exception, empty string, or silent pass-through.
- Does Filament Mail Templates render templates with Blade or token substitution?
- This is the most important security question to answer before granting template-edit rights. If templates are compiled through Laravel's Blade engine, anyone with panel access can execute arbitrary Blade directives and therefore PHP. A safer implementation restricts rendering to token replacement such as {{ customer_name }} with a whitelisted variable map, so inspect the service provider and rendering code first.
- Can I preview and validate email templates before sending?
- Look for save-time validation and a preview action, because template errors otherwise surface only at send time inside a queued job. Whether the package validates and previews at save time is a decisive quality signal for editor safety. Confirm this behavior in the code or a test environment rather than assuming it exists.
- Is it safe to let non-developers edit mail templates in Filament?
- Only after confirming the rendering model and access controls. If rendering is Blade-based, delegated admins or multi-tenant panel users could effectively execute arbitrary PHP, which is remote code execution by a non-engineer. Restrict template-edit permissions to trusted engineering staff unless the package uses a whitelisted token-replacement syntax.
- How do I send an email using a stored mail template?
- The package is intended to be wired into Laravel's Mail facade, so sending code points at a template resolver instead of a hard-coded mailable. That means replacing calls like Mail::to()->send(new X) with a lookup of the stored template and its variable data. Confirm the exact resolver API and failure behavior in the package source before integrating it into queued mail flows.
- Does Filament Mail Templates support per-locale template variants?
- Per-locale variants are not clearly established in the available information, so verify before depending on them. The technical evaluation flags localization as an unexplored edge case, including how locale is resolved at send time. If your app sends multilingual transactional email, test this explicitly or plan to add your own locale-aware resolver.
- Is Filament Mail Templates production-ready and actively maintained?
- Treat provenance as the main risk: the package has a single maintainer, no production evidence at scale, and limited dependents. The reported last release date is anomalous, so verify actual release cadence and commit history on Packagist and GitHub rather than trusting the summary. Also check for a test suite, CI coverage, and a clean composer audit before using it in production.
- What are alternatives to Filament Mail Templates, and what is the escape hatch?
- The conventional alternative is Laravel's built-in Markdown mailables plus published Blade views, which is more established but moves template edits into a deploy cycle. This package occupies that gap by making templates database-editable from Filament. Before adopting it, confirm the schema is simple enough for your team to own if the maintainer abandons the project.