- How do I install johnrivera7/filament-mia-theme in a Laravel Filament panel?
- Install it with Composer using composer require johnrivera7/filament-mia-theme, then register the theme in your Filament panel provider and publish its assets. The release notes also require running php artisan filament:assets after installation, so add that to your deploy script. Check the README for the exact registration call, since Filament themes may use ->viteTheme() or a plugin depending on the major version.
- Which Filament, Laravel, and PHP versions does Filament MIA Theme support?
- The current release targets Filament v5, but the package's Laravel and PHP minimums are not clearly documented in the provided overview. Before installing, inspect composer.json for the Filament, Laravel, and PHP constraints and confirm they match your application. Treat Filament major upgrades as a hard gate because the theme reaches into Filament's page shell and modal layering.
- Does Filament MIA Theme support dark mode?
- Yes, Filament MIA Theme includes built-in dark mode support alongside its custom color palette and typography. The theme is designed to keep dashboards consistent in both light and dark appearances. You can still override the published CSS if you need brand-specific dark-mode values.
- How do I customize the colors and typography in this Filament theme?
- Publish the package assets and edit the published CSS to adjust the color palette, typography, surfaces, and spacing. The theme is lightweight and ships precompiled CSS with no extra dependencies, so no npm build is normally required. Because it also styles the Filament page shell, test modal and sidebar behavior after any customization.
- Why are my Filament Create and Edit modals clipped after installing this theme?
- Version 0.2.3 fixed a defect where a page-level transform and animation-fill-mode on .fi-page created a containing block and stacking context under a sticky sidebar, clipping Create/Edit modals and dropping their headers. If you are on an older 0.2.x release, upgrade to 0.2.3 and run php artisan filament:assets. If clipping persists, inspect any custom CSS that transforms .fi-page, panel wrappers, or modal/teleport containers.
- Is Filament MIA Theme safe to use in production?
- It can be used in production, but treat it as a pre-1.0 page-shell skin rather than a purely cosmetic color palette. Pin the constraint to 0.2.* and re-evaluate any 0.3.0 release instead of upgrading automatically, because 0.x minor bumps can be breaking. Add php artisan filament:assets to your deployment runbook and smoke-test Create/Edit modals after theme or Filament updates.
- Do I need npm or a build step to use this Filament theme?
- No, the package is described as lightweight CSS with no extra dependencies and no build step for normal use. You install it via Composer, register the theme, and publish assets. The required post-install step is php artisan filament:assets, which should be part of deployment rather than a manual afterthought.
- What are the alternatives to johnrivera7/filament-mia-theme?
- A custom Filament theme gives you full control and avoids depending on one maintainer, but it costs more setup and ongoing Tailwind work. Filament's default styling is the safest baseline if you do not need a branded look. This package is a drop-in MIA-styled skin, so choose it when speed matters and you can accept version sensitivity to Filament's layout internals.
- Is Filament MIA Theme actively maintained, and will ^0.2.3 auto-update?
- Maintenance is a single-maintainer, pre-1.0 effort: v0.2.3 shows patches are still shipping, which softens but does not erase earlier end-of-life signals. The ^0.2.3 constraint allows 0.2.x updates but treats 0.3.0 as a breaking event by convention. With zero known dependents, you should expect to be the first to encounter layout defects and should budget for upstream waiting or local patching.
- What license does johnrivera7/filament-mia-theme use, and can I copy its CSS?
- The license is not confirmed in the provided information, so do not copy or extract code from the package until you verify it. License clarity matters if you plan to fork the CSS, vendor it, or build a custom theme from its source. Check the repository LICENSE file and Packagist metadata before making it part of your codebase.