Filament Tomatophp Theme Laravel Package

Getting Started

This is a Filament panel theme package rather than a general-purpose Laravel library — it restyles Filament's own chrome (dropdowns, borders, corner radii, the theme switcher) rather than adding domain functionality. v5.0.1 is a visual patch, so treat it as the baseline for "what the theme looks like" going forward.

Minimal steps for a first evaluation:

1. composer require the package into an app that already has a working Filament panel, then register it where your other panel plugins/themes are registered in the PanelProvider.
2. Publish whatever assets/config the package ships, then rebuild front-end assets and republish Filament assets.
3. Open the panel and check the three surfaces v5.0.1 touched: the user menu, an action group on a table row, and a filter dropdown. You should see the theme surface background, hairline (1px) borders, and zero corner radius — not Filament's default rounded, shadowed panel.
4. Toggle the light/dark/system switcher and confirm the hatched ground and brand-colored active mode.

Where to look first: the theme's CSS entry / token file (border-radius, surface, shadow variables), then the panel provider registration, then the switcher config if the package exposes placement options.

Implementation Patterns

Register once, inherit everywhere. Registering at the panel level means every resource, page, and relation manager picks up the styling for free. If you run multiple panels (e.g. admin and app), register in each provider rather than trying to share a single theme instance — the theme is applied per-panel by design in Filament.

Drive the brand color from config, not CSS. The active switcher mode is now brand-colored, which means the switcher reads the same brand color your panel is configured with. Set it via the panel's ->colors() / brand config and the switcher follows. This is the intended lever — don't fork CSS to change the active-mode tint.

Match custom views to the theme tokens. Any custom Blade, custom widgets, or custom page headers that use bg-white rounded-lg shadow-sm will now be the only rounded, shadowed, non-surface element on the page. Swap them for the theme's surface variable and hairline border so they stay visually consistent when the theme updates again.

Style custom dropdown content with the surface token. Custom filter forms and action-group content render inside dropdown panels that the theme now controls. If you supply your own inner wrapper, use the surface background rather than a hardcoded white, otherwise dark mode breaks in exactly one spot.

Bake asset rebuilds into deploy. Because the theme ships compiled Filament assets, your deploy sequence should include the Filament asset publish step and a cache clear. Treat it like a migration — not optional, and not something to do by hand.

Gotchas and Tips

• No API surface changed in 5.0.1 — it's purely visual, so bumping is low-risk from a code perspective. The risk is that every dropdown in the app now looks different, which will diff any visual regression snapshots or design-review screenshots.
• Audit your own rounded-* and shadow-* classes. Square corners and removed shadows are global; your custom components are the ones that will look out of place. Layering previously conveyed by shadow now has to come from borders — check modals and notification toasts specifically, since those lean on elevation.
• Stale assets are the #1 false-positive bug report. If the panel still looks rounded after upgrading, you almost certainly didn't republish Filament assets or clear compiled views. Clear caches before filing anything.
• Tailwind purging. If you extend the theme with your own classes, put them in the theme's CSS entry point (or safelist them). Classes invented only in Blade may get purged and silently do nothing.
• Third-party plugins may not inherit. Plugins that ship their own dropdown or menu styling can bypass the theme surface entirely, leaving one rounded, white panel among square ones. Check each installed plugin's dropdowns after upgrading.
• Verify the hatched ground in both modes. A hatch pattern tuned for light mode can be invisible on dark surfaces, or visually noisy. Worth a five-minute check rather than discovering it in a support ticket.
• Extend via published CSS, never by editing vendor. If you need a different radius or border color, override the token in your published theme stylesheet so the next patch release doesn't clobber your change.
• Report visual regressions upstream. A patch release that only touches styling suggests active maintenance and fast turnaround — small visual bugs are worth an issue rather than a local workaround.