Editorialthemev4 Laravel Package

Getting Started

• Install with Composer: composer require jeffersongoncalves/editorialthemev4. The 4.14.0 release simply tracks Filament v4.14.0 — there are no theme-level API changes, so an existing lockfile can usually be bumped safely with composer update jeffersongoncalves/editorialthemev4 filament/filament.
• Look first at the package's service provider and README (src/EditorialThemeV4ServiceProvider.php or similar). Theme packages in this family either auto-register assets or expose a Filament plugin class you must add to your panel.
• Publish anything the package exposes before customising. Check available tags with php artisan vendor:publish --provider="JeffersonGoncalves\\EditorialThemeV4\\EditorialThemeV4ServiceProvider" (tag names vary by minor release).
• Register the theme on your panel. If it ships a plugin: add ->plugin(EditorialThemeV4::make()) to your AdminPanelProvider. If it ships a prebuilt stylesheet instead, follow the README's asset-registration or viteTheme() instruction — do not do both.
• First use case: apply it to a single admin panel, run php artisan filament:assets && php artisan optimize:clear, open /admin, and confirm the login screen and dashboard pick up the editorial styling before rolling it out to other panels.

Implementation Patterns

• Single panel, minimal wiring. Keep the theme registration in one PanelProvider and rely on Filament's panel-scoped asset loading. This avoids leaking the theme into customer-facing or secondary panels.
• Multi-panel rollout. Register the plugin/theme per panel provider rather than globally. If you want a shared look, extract a PanelTheme helper or base provider and call it from each panel.
• Layered customisation. Treat the package's CSS as a base layer and put brand overrides in your own theme.css or a panel-specific stylesheet, loaded after the package assets. This survives package upgrades far better than editing published vendor CSS.
• Version alignment. Pin the package alongside Filament in composer.json ("filament/filament": "^4.14") so the theme's compiled classes stay in sync with the Filament version it targets.
• CI pattern. Run composer update --locked, then php artisan filament:assets in the deploy pipeline. Include a smoke test that boots the panel (php artisan about / route check) to catch missing asset manifests.
• Combining with other Filament plugins. Register the theme plugin first in the panel's plugins([...]) array so subsequent plugins can layer their own assets on top.

Gotchas and Tips

• Dependency-bump releases deserve a visual check. A "bump Filament" release changes the underlying Tailwind classes and component markup. Even with no theme code changes, the compiled CSS can drift; open the dashboard, tables, and forms in both light and dark mode after upgrading.
• Clear caches aggressively. Filament caches assets and Blade components. php artisan filament:assets, php artisan view:clear, and php artisan optimize:clear resolve most "styles disappeared" reports.
• Don't mix theme mechanisms. Using both a package-provided stylesheet and a local viteTheme() is the most common cause of duplicate or conflicting styles. Pick one per panel.
• Vite manifest errors (Unable to locate file in Vite manifest) usually mean you registered a local theme without running npm run build, or you are pointing at a manifest from a different panel. Check public/build/manifest.json.
• Dark mode is easy to miss. Filament v4 relies on CSS variables and the .dark class; verify any custom brand overrides include dark variants rather than hard-coded hex values.
• Extension points: prefer the panel's ->colors() and ->brandLogo() APIs over CSS overrides for simple branding, and use the package's published config (if present) for layout options. Reach for raw CSS only for structural changes.
• Upgrade sequencing. When Filament ships a minor, bump Filament and this theme together in the same PR so reviewers can see the visual diff against a single, coherent dependency set.