Editorialthemev3 Laravel Package

Getting Started

Install the theme with Composer and align it to your Filament version:

composer require jeffersongoncalves/editorialthemev3

Then publish the package assets (check the exact tag with php artisan vendor:publish):

php artisan vendor:publish --tag=editorialthemev3-assets

Register the theme in your Filament panel provider. The package typically ships a CSS theme you either point Filament at directly or import into your panel’s theme CSS:

// app/Providers/Filament/AdminPanelProvider.php
public function panel(Panel $panel): Panel
{
    return $panel
        // ...
        ->viteTheme('resources/css/filament/admin/theme.css');
}

If the package provides its own CSS entrypoint, import it from your theme file:

@import '../../../../vendor/jeffersongoncalves/editorialthemev3/resources/css/theme.css';

First use case: apply the editorial look to an existing Filament v3 admin panel, then adjust brand colors via CSS variables rather than editing vendor files. The 3.3.56 release is a dependency-alignment bump (Filament 3.3.56 + npm deps) with no new API surface, so start by matching your Filament version to the theme version.

Implementation Patterns

• Version lockstep: keep filament/filament and jeffersongoncalves/editorialthemev3 on the same 3.3.x line. The theme version mirrors Filament’s version, so update both together in composer.json.
• Customize through CSS variables: override the theme’s design tokens in your own panel CSS instead of editing published assets. This keeps upgrades clean.
• Publish and override views: use vendor:publish --tag=editorialthemev3-views (or the package’s documented tag) to copy Blade components into resources/views/vendor/..., then adjust markup while preserving Filament’s component contracts.
• Multi-panel apps: register the theme per panel. You can use the editorial theme for an admin panel and leave a customer-facing panel on Filament’s default theme.
• Combine with Filament branding APIs: use ->brandName(), ->colors(), and ->favicon() alongside the theme. These are complementary; the theme handles layout/styling, Filament handles identity.
• Frontend workflow: if you customize the theme CSS, include it in your Vite input and run npm run build (or npm run dev during development). The package’s prebuilt assets are a starting point; your build pipeline should own the final CSS.
• Upgrade workflow: bump Filament and the theme together, re-publish assets if the package docs require it, rebuild frontend assets, then clear Filament’s caches.

Gotchas and Tips

• Version mismatch is the main failure mode: installing theme 3.3.56 against Filament 3.2.x (or vice versa) can produce missing CSS classes, broken layouts, or unresolved Blade components. Treat the theme version as a Filament compatibility pin.

• Re-publish after updates: dependency bumps can change published assets. After composer update, re-run the vendor publish command if the package’s release notes or README instruct you to. If you’ve overridden published files, diff them before overwriting.

• Clear caches aggressively: Filament caches components and Blade views. After theme or view changes, run:

  php artisan filament:clear-cached-components
  php artisan view:clear
  php artisan cache:clear
  

• Check the publish tags: php artisan vendor:publish lists available tags. The theme may separate assets, views, and config. Publish only what you need to override.

• Vite path issues: if you import the package CSS from vendor/, ensure the path is correct relative to your theme file and that Tailwind’s content globs include your published views. Missing content paths cause classes to be purged.

• Debugging styling: use browser devtools to inspect computed CSS variables and confirm the theme’s stylesheet is actually loaded. If styles are missing, verify the panel provider registration and that npm run build completed.

• Extension points: prefer CSS variable overrides and published view overrides over forking the package. If you need deeper changes, create a child theme CSS file that imports the package theme and layers your overrides.

• Release 3.3.56 is low-risk: it only bumps Filament to 3.3.56 and npm dependencies. No breaking changes or deprecations are indicated, but confirm your app’s Filament version matches before upgrading.