Filament Italia Laravel Package

Product Decisions This Supports

• Market entry / positioning for Italian PA deals. If any part of the pipeline is Italian public administration or PA-adjacent buyers, AGID / Designers Italia conformance is frequently a procurement and accessibility checkbox, not a nice-to-have. A Filament theme built on the AGID design system lets the back office look continuous with a Bootstrap Italia public site for roughly zero build cost. That is an RFP-scoring asset, not a user-visible feature.
• Build vs buy. Theming is undifferentiated work. Borrowing an MIT-licensed port of a public design system saves a front-end theming sprint; the price of admission is a recurring visual-QA pass per upgrade, not engineering headcount.
• Roadmap sequencing. This is a presentation-layer dependency. It should never gate a roadmap item; it is an enabler to schedule when we commit to Italian-market or PA-facing deals, and it lands as a theme swap (days), not a migration project.
• Use cases worth naming: PA-facing SaaS back office; white-label panels sold to Italian public bodies; tender demos where visual conformance shortens evaluator review.
• Scope decision that must be made first — the package's own story is inconsistent. The repo tagline and the v1.4.1 release notes describe a theme (badge radii, topbar icon shapes, button icon color). The package blurb promises administrative data — province/comune/CAP selects, codice fiscale and partita IVA validation. Only one of those can go into a customer commitment. Verify against the source before scoping: if the data fields don't exist, that's a separate build item (ISTAT/comuni dataset ownership, update cadence) and it materially changes the estimate.
• Marketing/claims decision. Do not ship the words "AGID-compliant" or "WCAG AA" on the strength of a README. There is no published audit. In Italian public procurement an accessibility claim is legal-adjacent; use "built on the AGID Design System" until we run our own axe/Pa11y pass on our actual views and palettes.
• Risk posture to accept consciously. Zero stars, single maintainer, no SLA, Italian-only docs. Acceptable for a skin we can vendor and fork; not acceptable as a load-bearing dependency.

When to Consider This Package

Consider it when:

• The admin is Filament on Laravel, and the buyer or tender explicitly references AGID / Designers Italia or accessibility conformance.
• The public-facing product already uses Bootstrap Italia — continuity between citizen-facing site and back office is a genuine demo and evaluation advantage.
• There is a front-end developer who can own Tailwind/Filament theming (~1–2 days to productivity; a backend developer should not own this).
• The team can pin the version, vendor or publish compiled assets, and commit to a screenshot + accessibility gate on theme upgrades.

Look elsewhere or skip when:

• The panel must carry a customer's own corporate brand — two themes cannot own the same Tailwind layers; pick one owner per panel.
• There is no front-end capacity for visual QA. The failure mode is silent: missing or renamed --bsi-* tokens fall back to default radii and colors, producing an "off-brand but functional" panel that passes every automated test.
• A vendor SLA, support contract, or formal accessibility certification is contractually required.
• Filament v4 support is needed and unconfirmed by the maintainer.
• What we actually need is the Italian data fields and validation the blurb advertises. That is a different sourcing decision — a maintained dataset with its own update cadence — and should not be conflated with a CSS theme.

How to Pitch It (Stakeholders)

To executives: "A free, MIT-licensed theme that makes our Filament admin look like the Italian public-sector design system. It costs no build time and strengthens our position in Italian PA tenders where AGID conformance and accessibility are scored. The caveats are honest ones: it is a one-person open-source project with no support contract, so we treat it as a skin we can fork and vendor — not a platform. And we will not claim 'AGID certified' until we run our own accessibility check."

To engineering: "Presentational only — a service provider, Blade views, and --bsi-* CSS variables. No migrations, models, jobs, or middleware; no architectural coupling. Adoption is composer require plus theme registration. The cost isn't integration, it's stewardship: a design-token dependency that changes pixels in patch releases, so we need a screenshot baseline and an axe scan as the upgrade gate, and exactly one theme owner per panel."

The ask: approve a short spike — pin the version, install it in one panel, capture a visual baseline, run an accessibility scan, and confirm what the package actually ships (theme vs. Italian data fields) — before any proposal language references it. Then decide explicitly whether we maintain a fork.