- What is Filament Italia and what problem does it solve?
- Filament Italia is a presentational theme package for Filament v5 admin panels. It ports the AGID .italia Design System and Bootstrap Italia design language into Filament using Blade views and CSS custom properties such as --bsi-*. It also provides Italian translations and locale defaults so you can build Italy-focused admin interfaces without manual language setup.
- How do I install Filament Italia in a Laravel Filament panel?
- Install it with Composer using robyconte/filament-italia, then register the package theme on the Filament panel you want to style. The described adoption path is Composer require plus panel theme registration, with asset publishing if required by the package documentation. It ships no migrations, models, jobs, or middleware to install.
- Which Laravel, PHP, and Filament versions does Filament Italia support?
- The evaluation lists Laravel 10, 11, and 12 plus PHP 8.1+ as the stack fit, and the package is described as a Filament v5 theme. The exact minimum supported Filament and Laravel/PHP versions are not documented in the provided material, so confirm them in the README or with the maintainer before pinning it. Filament v4 support is listed as an open question rather than a confirmed feature.
- Does Filament Italia provide Italian translations and locale defaults out of the box?
- Yes. Filament Italia is intended to bring Italian localization to Filament panels with ready-to-use translations and locale defaults. That reduces the need to manually set up Italian language files for the panel UI. Check the package configuration if you need to override the default locale per panel or application.
- Do I need Node, Tailwind, or compiled assets to use Filament Italia?
- The package is a CSS and Blade presentational layer, but the provided evaluation does not state whether compiled assets are shipped or whether the host app needs a Node/Tailwind build step and safelist configuration. Treat that as a verification item before adopting it in CI or a locked-down production build. If assets are not precompiled, plan for your normal Laravel asset pipeline.
- How do I override the --bsi-* design tokens or customize the theme?
- The theme is built around --bsi-* CSS custom properties, so customization is expected at the token layer rather than through PHP APIs. The provided material does not confirm whether the package bundles those tokens or expects the host application to provide them, so check the fallback behavior if --bsi-* values are absent. Avoid layering local CSS overrides on top of the theme unless you have confirmed they are still needed.
- Is Filament Italia accessible and does it meet AGID or WCAG requirements?
- The package ports AGID .italia styling, but the provided evaluation does not include a documented AGID/WCAG conformance statement or accessibility audit for the shipped components. The v1.4.1 icon-color inheritance change can reduce icon/label contrast on custom brand palettes, so verify contrast against WCAG AA per palette. Run axe or Pa11y on filled colored buttons with icons and icon-only topbar actions after upgrading.
- Does Filament Italia support dark mode or high-contrast themes?
- Dark mode and high-contrast support are not documented in the provided evaluation. Because the theme relies on CSS custom properties, any such support would depend on the shipped token set and any host-app overrides. Confirm this in the package documentation or test it directly in a panel before relying on it.
- Can I combine Filament Italia with another Filament theme or my own CSS?
- Filament Italia is a theme layer, so it will conflict with another Filament theme that owns the same Tailwind layers or CSS variables. Pick one theme owner per panel and remove local CSS shims that previously worked around badge radius or button icon colors, or those overrides may double-apply. If you need a corporate skin, evaluate whether you can extend the --bsi-* tokens instead of stacking themes, or consider a different Filament theme as the alternative.
- How should I test and upgrade Filament Italia safely in production?
- Pin the current version and record a visual baseline with screenshot tests across list, form, and topbar views before upgrading. Upgrade in a branch, diff screenshots to separate intended from unintended changes, and run an accessibility scan on affected views. Also grep for .rounded-pill, fi- color overrides, and topbar action classes so obsolete local CSS is removed; release cadence and upstream Bootstrap Italia tracking are not documented in the provided material.