- How do I install the Aurum theme in a Laravel Filament panel?
- Install it with composer require thalysjuvenal/aurum-filament-theme, then run php artisan filament:assets to publish the theme assets. Register the plugin in your PanelProvider with ->plugin(AurumTheme::make()), which is the only required code change. Requirements are PHP ^8.2 and filament/filament ^5.0, and the package ships a publishable configuration file for presets and branding.
- Which Filament and Laravel versions does Aurum support?
- Aurum targets FilamentPHP v5 only; its Composer constraint is filament/filament ^5.0 and the maintainer validates against Filament 5.6.8. It requires PHP 8.2 or newer. There is no stated plan or support window for Filament v6, so budget for a fork or re-theme if you plan to stay on Filament long term.
- Does Aurum work with multiple Filament panels in one application?
- Yes. Aurum is panel-scoped: only panels that call ->plugin(AurumTheme::make()) are themed, and panels that do not are left untouched. That makes incremental rollout or A/B comparison across panels inexpensive within a single Laravel application.
- How do I switch between the gold, emerald, sapphire and ruby presets?
- Choose a preset per panel through the published configuration, which ships with Gold as the default plus Emerald, Sapphire, Ruby and other ready-made palettes. Each preset includes matched dark and light variants, so switching presets does not require separate theme registrations. Presets inject colors through $panel->colors() from OKLCH palettes.
- Can I create a custom Aurum preset with my own brand colors?
- The README documents a custom-preset extension path, so you can define your own accent and palette values rather than being limited to the bundled presets. Be aware that the WCAG contrast gate in tests/PresetContrastTest.php applies to the maintainer's bundled presets, not automatically to presets you write. Treat accessibility compliance as a per-preset obligation and verify contrast yourself. Customization beyond accentHex() and palette() means working against the package rather than with it.
- Do I need Vite or Tailwind changes to use Aurum?
- No. Aurum is zero-build: it registers its CSS through Filament's panel asset pipeline, so you do not need to modify Vite, Tailwind or your app's build configuration. This removes the usual integration and long-term maintenance cost of Filament themes. The tradeoff is that deep customization beyond the exposed palette helpers is harder.
- Does Aurum style the login and authentication screens?
- Yes. Aurum ships branded login and authentication screens with a configurable brand block, so the auth experience matches the panel rather than falling back to stock Filament styling. Configuration is handled through the published config file. The README also documents a logo gotcha around trimmed logo assets and dark-mode logo preference, so check both light and dark variants after setting your brand assets.
- Is Aurum WCAG accessible out of the box?
- The bundled presets pass a WCAG contrast gate in tests/PresetContrastTest.php, so the shipped palettes are held to a documented standard. That harness does not automatically cover presets you define yourself, so compliance becomes your responsibility once you customize. If you need enforceable accessibility, extend the contrast tests to your own presets.
- Will Aurum conflict with other Filament plugins that ship their own CSS?
- Aurum is panel-scoped and registers its CSS through Filament's asset pipeline, so it is designed to compose with the framework rather than shadow it. However, the package does not publish guidance on CSS specificity conflicts with other Filament plugins that ship their own views or styles, or on whether plugin registration order is load-bearing. Validate coexistence in your own stack, especially if you run several UI-affecting plugins on the same panel.
- Is Aurum maintained, and what is the risk of using a low-adoption package?
- Aurum is MIT licensed, CI-backed and actively maintained, but it has one author, roughly 10 stars and zero dependents, so the bus factor is effectively one. The larger technical risk is CSS-level coupling to Filament internals: a Filament 5.x minor that renames Tailwind tokens or restructures markup could cause visual regressions across every panel at once. Treat adoption as taking ownership of the code and plan to fork or re-theme rather than relying on a long support window.