Aviwebsquad: a Laravel CMS documented in public
Aviwebsquad is the product itself: a Laravel + Inertia + Svelte content management site with a Filament admin, Sanctum-secured MCP publishing, and long-form build logs written from the same production stack you are reading.
Build logs for the Aviwebsquad Laravel + Inertia CMS: Filament admin, MCP publishing, deploys, SEO crawlability, and Pest tests from production.
This is not an agency landing page or a content farm. I ship features on aviwebsquad.in, then document what broke, what I kept, and how to reproduce it—deploys on aaPanel, queue discipline with Horizon, crawlable HTML for SEO, and Pest smoke tests before release. When early “what is X?” posts hurt quality signals, I expand, niche-lock, or noindex them rather than leave thin pages as the site’s identity.
What you will find here
- CMS build logs: Filament resources, Inertia + Svelte public pages, markdown posts, media, menus, and MCP content APIs used to publish this site.
- Ops runbooks: GitLab CI, aaPanel PHP paths, release folders, Horizon workers, Pulse, Postgres backups, and the pre-deploy Pest subset I actually run.
- SEO that matches the app: crawlable HTML fallbacks, FAQ JSON-LD, sitemaps that skip empty categories, and lessons from Search Console 404 cleanup.
- Security of this stack: Sanctum abilities for agents, token rotation, 2FA/passkeys roadmap for admin accounts—not generic consumer tips disconnected from the CMS.
The stack behind this site
Aviwebsquad runs on Laravel with Inertia and Svelte on the front end. Content lives in a custom CMS: blog posts with categories and tags, static pages, menus, Spatie media, and SEO fields per page. Admin work happens in Filament; public reading happens in Inertia. Agents write through a Sanctum MCP API with audited tools—documented in the blog when those pieces change.
Editorial standards
Posts are original, revised when facts change, and credited when they use external sources or stock imagery. Build logs and runbooks outrank glossary stubs. Tutorials include enough context to reproduce results on this project. Thin or off-topic pages are expanded, redirected, or marked noindex so they do not define the site for readers or reviewers.
Who this is for
Readers are Laravel developers and solo builders who want concrete notes from a real CMS—not generic encyclopedia pages. If you maintain Filament admins, Inertia apps, or a single-VPS deploy, you should find actionable detail. If you need commercial services, use the contact page; this project is documented first as a product and codebase.
Frequently asked questions
Is Aviwebsquad a company or an agency?
No. It is a personal Laravel CMS and technical blog published under the Aviwebsquad name. Articles reflect my own production experiments unless stated otherwise.
Can I reuse code snippets from the blog?
You may reference short excerpts with attribution and a link to the original article. For larger reuse, contact me through the site so we can agree on terms.
How often is new content published?
Roughly two posts per week when the queue is healthy, scheduled with
published_at so cadence stays steady. Quality and first-hand detail
come before volume.
Does this site use cookies or advertising?
Yes, where configured. Analytics, reCAPTCHA on forms, and Google AdSense may load after you accept cookies. Details are in the Privacy Policy and Cookie Policy.
How do I get in touch?
Use the contact form for corrections, questions, or collaboration ideas. I read messages when I can but cannot guarantee a response time.