Appearance
Source:
docs/adr/0001-monolith-architecture.md. Edit it there; this page is generated at build time.
Monolith: Blade + Livewire frontend, Filament admin, one codebase
We considered a decoupled setup (Laravel as an API-only backend behind a separate JS frontend like Next.js) versus a single Laravel app serving both the public site (Blade + Livewire) and the Filament admin panel. We chose the monolith: Filament is Laravel-native and shares auth/models/routing with the public site, canonical tags and other SEO metadata are trivial to render server-side, and one codebase means one deploy target. A decoupled frontend would only have paid off if we specifically needed a non-PHP frontend team or app-like client interactivity this content site doesn't call for.