- How do I install the Filament Tailscale theme in my Laravel app?
- Install it with Composer using composer require vlados/filament-tailscale-theme, then register the theme's CSS in the panel provider you want to restyle. It is a presentation-layer package, so there are no migrations or service-layer changes to worry about beyond the theme registration and making sure the CSS is present at deploy time. Confirm whether the tagged release ships the compiled dist file before you deploy, because that decides whether your pipeline needs a Node step.
- How do I register the Tailscale theme in a Filament panel provider?
- The theme is registered as panel CSS, typically by pointing the panel's theme configuration at the package's compiled filament-tailscale-theme.css file. Because it is an overlay skin, you can scope it to a single panel and leave your other panels on Filament's default styling. Register it in the panel provider for the panel you actually want to restyle rather than applying it globally.
- Which Filament versions does this Tailscale theme support?
- The theme targets Filament v5 admin panels and depends on Filament's CSS class names, including the .fi-outlined selector introduced upstream. There is no published compatibility matrix covering Filament version, theme version, and PHP or Laravel version, so pin the exact theme version in composer.json and check release notes against your Filament line. Treat any Filament minor upgrade as a potential silent visual regression rather than an obviously breaking change.
- Do I need to run npm run build, or is the compiled CSS shipped?
- The package includes a Vite build that produces resources/dist/filament-tailscale-theme.css, and v1.0.2 re-released the earlier CSS fixes alongside that build step. Whether the compiled dist file is committed in the tagged release is the deciding factor for whether your app needs a Node toolchain at all. Verify this before adoption: if consumers must build from source, a previously PHP-only dependency now requires Node in onboarding and CI.
- Will this theme break my existing Filament admin panel styling?
- Yes, it changes the look of every page in the panel by design: sections, widgets, tables, and cards are flattened with shadows removed, and secondary buttons are restyled. CSS regressions are invisible to PHP tests, so a green test suite does not prove the UI is intact. Do a side-by-side screenshot pass over buttons, inputs, badges, cards, tables, and widgets before rolling out.
- Can I customize the Tailscale colors and styling in this Filament theme?
- The theme is a skin built from compiled CSS, so customization usually means overriding CSS custom properties or loading your own stylesheet after the theme. If you plan to fork or rebuild the source, keep the Vite pipeline in mind because changes require a build step. For light branding tweaks, prefer an additional override stylesheet over editing the package's dist file directly.
- What changed with .fi-btn-outlined and .fi-outlined in this theme?
- Filament renamed the upstream selector from .fi-btn-outlined to .fi-outlined, and the theme follows the new name. That is upstream selector drift, not a styling preference, which means the theme is tightly bound to a specific Filament major or minor line. Unless the old selector is kept as a fallback, anyone on the prior Filament line gets a hard break rather than graceful degradation.
- Is vlados/filament-tailscale-theme safe to use in production?
- It carries effectively zero domain logic and no service-layer coupling, so runtime risk is low; the real risk is visual. Pin the exact version, deploy to staging or a non-customer-facing panel first, and keep the previous tag as your rollback target. Also watch release hygiene: v1.0.1 and v1.0.2 shipped the same CSS fixes, which suggests the dist artifact was stale or the build pipeline was not reproducible.
- How do I roll back if a Filament upgrade breaks the theme?
- Because the coupling is to Filament's CSS class names, an upgrade can silently break styling without throwing an error. Pin the theme to an exact version in composer.json and document the previously working theme tag alongside its matching Filament version as the known-good pair. If a selector rename is the cause, you may have to roll back Filament itself rather than just the theme.
- What are the alternatives to this Filament theme, and is it worth using?
- The alternatives are Filament's default styling, another community panel theme, or a custom theme built on Filament's own theme scaffolding. This package is worth it if your platform has standardized on Filament and you have design or front-end capacity to review visual changes, since its failure mode is aesthetic and needs a human to catch it. If nobody owns the UI, the cost of tracking upstream selector renames may outweigh the branding benefit.