Astro

Astro is the framework I reach for when I build a site from scratch. A framework, in this context, is a set of tools and conventions for turning components, the header, the footer, a pricing block, into finished web pages. What makes Astro different from most of the frameworks a small business runs into is when that turning happens.

A WordPress site or a page builder assembles the page at the moment a visitor asks for it. The server pulls content from a database, runs a template engine, and sends back HTML, every single time, for every single visitor. Astro does that assembly once, when the site is built, and then serves the already-finished HTML file to everyone who asks. Nothing is computed on the fly unless a specific piece of the page genuinely needs it.

That one design decision is why an Astro site tends to load in a fraction of a second rather than a second or two. It is also why there is far less attack surface: no database sitting behind the page, no server-side templating engine to exploit, no admin login guessing its way toward compromise.

Why it matters to you

Speed is not a nice-to-have. It is a ranking factor, and it is the difference between a visitor who waits for your page and a visitor who bounces to a competitor. A framework that ships flat files by default gives you that speed without a caching plugin or a CDN configuration you have to babysit.

The security side matters just as much, especially if you have been burned before. A site with no database and no server-side code running per request has almost nothing for an attacker to break into. That is a real answer to a real threat, not a marketing line.

How I set it up

I write the site as version controlled code in a GitHub repository, build it with Astro, and deploy the output to hosting that just serves files. There is no dashboard to log into on the live site, no plugin list to keep patched, and no database credentials sitting somewhere waiting to leak.

Content that genuinely needs to be dynamic, a contact form, a booking widget, gets its own small, isolated piece of code rather than putting the whole site back on a server-rendered model. Everything else stays as the plain, pre-built page.

What it looks like in practice

You will not notice Astro directly. What you will notice is a site that opens instantly on a phone with a weak signal, that search engines crawl cleanly because there is no rendering delay for them to wait through, and that keeps working during a traffic spike because serving a flat file does not get slower under load the way a database query can.

When I hand the project over, you get the source code in a repository you own, not a black box tied to one vendor’s editor. If you ever want another developer to pick up the work, the code reads like code, because it is.