Filament on Aviwebsquad: why the admin is Filament (and the public site is not)

Short answer: Aviwebsquad’s admin is Filament v5; the public site is Inertia + Svelte. Filament won for CRUD speed (posts, pages, banners, settings). Inertia won for branded reading UX and crawlable SEO control.

Generic “what is Filament” intros are everywhere. This is how we use it.

Why Filament here

I needed:

Filament ships that in days. Details: Filament dashboard patterns and Filament vs Inertia for admin.

What a BlogPost resource looks like in practice

Editors set:

  1. Title / slug / category / tags
  2. body_markdown (source of truth)
  3. status + published_at for scheduling without cron
  4. Featured image → Spatie featured collection (media workflow)

MCP agents upsert the same rows Filament edits—same model, different door (MCP Sanctum).

Livewire vs public Inertia

Admin traffic is low; Livewire cost is fine. Public blog needs:

Mixing both in one app is intentional, not confusion.

Plugins and packages we lean on

FAQ

Should every Laravel app use Filament?

No. Marketing sites often skip it. CMS admin panels are Filament’s sweet spot—ours included.

Filament for the whole public UI?

I tried that mentally; brand layout and SEO control pushed me to Inertia for readers.

Orchid / Nova?

We evaluated Orchid early and stayed on Filament. Orchid posts on this site are noindexed—they are not our stack.

Day-to-day admin tasks Filament owns

Without Filament I would rebuild half of that in Svelte for an audience of one—bad ROI.

FAQ (extra)

Does Filament appear on the public blog?

No. Public routes are Inertia pages. Filament is under /admin and disallowed in robots.txt.