How one Laravel app uses Blade, Inertia, and Filament for three distinct purposes

A development team building a Laravel 13 application deliberately chose three different frontend approaches — Blade, Inertia with React, and Filament — each selected to best solve a specific problem. The public-facing site uses 26 server-rendered Blade views with minimal JavaScript, keeping SEO-critical data like breadcrumbs and JSON-LD in sync from a single source. The audit tool relies on Inertia and React 19 for its complex, interactive UI, with controllers passing readonly DTOs directly to pages, eliminating the need for a separate API layer. The admin console is handled entirely by Filament 5, where standard CRUD interfaces are generated with minimal custom code and tested via Pest integration. All three worlds share one application, one origin, and one CSS token sheet, though the team notes that mismatched client-side state — such as dark mode storage keys — can cause subtle inconsistencies when users move between sections.