Filament patterns I use daily in the Aviwebsquad CMS dashboard

Short answer: Aviwebsquad’s admin is Filament v5 for speed; the public site is Inertia + Svelte. Filament owns CRUD, media, and publish state—Inertia owns brand UX.

I compared both approaches in Filament vs Inertia for admin panels. Here is what shipped.

Blog post resource: the fields that matter

Field	Why it exists
`body_markdown`	Source of truth; HTML rendered on save
`published_at` + `status`	Schedule without cron—see scheduling posts
SEO group	`meta_title`, `robots`, OG fields per post
Spatie featured	Card + OG images via Media Library

Filament’s DateTimePicker on published_at is how editors (and MCP) queue weeks of content.

Tables: how I avoid admin clutter

Default sort: updated_at desc
Filters: status, category, featured
Bulk actions: none for delete (too scary on production)

Media collections

Featured uploads land in featured; og copies automatically in BlogPostMcpWriter when empty. Public cards read conversions—no manual crop per platform.

Why not Filament for the whole site?

Marketing pages need bespoke layout. Building Aviwebsquad documents the split: Filament = operations, Inertia = reading experience.

MCP + Filament together

Agents upsert via API; humans polish in Filament. Same database rows. That hybrid is the whole point of Laravel Boost + MCP on this project.

FAQ

New to Filament?

Start with What is FilamentPHP?—then install a single BlogPostResource before abstracting.

Livewire performance?

Admin traffic is low. I optimize public Inertia routes first.

Can authors break production SEO?

They can set noindex—I default robots to index, follow in the writer when blank.

Policy and authorization in Filament

Blog authors see only their drafts unless they hold the blog:manage-any ability. I wire that through Laravel policies, not Filament magic—so Pest policy tests still matter (smoke tests).

Custom page: MCP audit tail

A read-only Filament page lists recent MCP requests (tool name, status, duration). Editors spot runaway agent loops without SSH.

Keyboard shortcuts editors asked for

Ctrl+S save (native browser) + sticky save button in header
Slug locked after first publish—prevents GSC 404 chains when renaming

When Filament feels slow

Enable table defer loading on posts >500 rows. Aviwebsquad is nowhere near that; the setting is documented for future-me.

FAQ (extended)

Export posts?

Markdown export is a planned Artisan command—not Filament—so Git diffs stay meaningful.

Multi-language?

Not yet. Single canonical URL per post simplifies sitemap rules.