About

About Aviwebsquad

Aviwebsquad (aviwebsquad.in) is an independent side project: a technical blog and text-based content management site where I publish long-form writing, experiment with publishing workflows, and document software I am building in public.

This is not a client services agency. It is a personal publication and playground for ideas that might grow into small SaaS utilities over time.

What this site is

At its core, Aviwebsquad is three things:

1. A blog — original articles on Laravel, PHP, developer tooling, hosting, security basics, and related topics I actually use.
2. A custom CMS — the site runs on Laravel, Inertia, and Svelte with markdown posts, static pages, menus, media, search, and comments. I extend it as I learn.
3. A build log — as small tools or experiments ship, they are documented here first so readers can follow along without hype.

What I write about

Most articles fall into a few buckets:

• Laravel and PHP — packages, patterns, admin panels, testing, and deployment lessons from real projects.
• Developer tools — honest notes on software that speeds up development, monitoring, or content work.
• Building in public — architecture decisions, trade-offs, and post-mortems from this codebase and future experiments.

I prioritise depth and usefulness over volume. A single tutorial that saves someone an afternoon is worth more than ten generic “What is X?” summaries.

Editorial standards

• Original writing. Posts are drafted for this site, not copied from elsewhere.
• Corrections welcome. Technical content ages; if something is wrong, use the Contact page and I will update the article.
• Attribution. Stock images and external references are credited where used.
• No paywall for fundamentals. The blog is free to read; monetisation may include display advertising (see our Advertising policy) in line with Google programme policies.

About the author

Aviwebsquad is operated and written by Avina as a personal project. I work with Laravel and modern web stacks in production-style environments and use this site to share what I learn along the way—not as corporate marketing.

If you want to know what I am working on, start with the blog or browse categories. For direct messages, use Contact.

Technology

The public site and admin back office are built with:

• Laravel for routing, auth, APIs, queues, and content models
• Inertia.js + Svelte for the reader-facing UI
• Filament for internal content management
• Spatie packages for media, settings, and permissions where they fit

I write about this stack because I maintain it—not because it is the only valid choice.

Roadmap

Near-term goals for the project:

• Continue publishing fewer, stronger technical articles
• Improve search, author pages, and on-page SEO for readers
• Prototype small SaaS-style tools and document them here before any wider launch

There is no fixed commercial roadmap. The site earns trust by being useful first.

Contact

Questions, corrections, collaboration ideas, or feedback:

• Use the Contact form — I read messages when I can, typically within a few days.
• For privacy-related requests, see the Privacy Policy.

Thank you for reading.