We Built This Site in an Afternoon. No CMS. No Agency. Here's the Architecture.

The V8 Global website you’re reading right now was rebuilt from scratch yesterday afternoon. No CMS. No agency. No design system to configure, no theme to customise, no admin panel to log into.

It was live before the end of the session.

That’s not a boast — it’s a product demonstration. Because what we built for ourselves is exactly what we build for Scaffold clients. And the fact that it took one afternoon to ship is precisely the point.

What the old setup looked like

The previous site was plain HTML files served directly from Cloudflare Pages. Fast, functional, but manually maintained. Every page update was a code edit. There was no blog. No RSS feed. No way to publish content without touching the repository directly.

It worked — until it needed to scale.

What we migrated to

Astro as the framework. Static site generation, zero JavaScript overhead unless a page needs it, and — critically — a content collections system that treats Markdown files as a database. Drop a .md file in the right folder, push to GitHub, and the page is live in under 45 seconds.

Cloudflare Pages for hosting. Auto-deploys from the GitHub repository on every push. No build server to manage, no deployment pipeline to configure. Cloudflare detects the Astro build command and handles the rest.

Cloudflare Pages Functions for form handling. Every inquiry form on the site — Axia, Nexus, Scaffold, the Hongkongers Magazine partnership page — posts to a serverless function that stores the submission in Cloudflare KV storage. No database to maintain. No third-party form service. Data sits in KV until we export it to the CRM.

GA4 with consent gating. Analytics only fire after a visitor explicitly accepts the cookie banner. Pre-consent, zero tracking requests leave the browser. The implementation is in a single shared layout file — one change propagates to every page on the site.

Here is how the full pipeline connects:

The part that matters for AI

The blog pipeline is built for Axia.

Every blog post is a Markdown file with structured frontmatter — title, description, publish date, tags, and a CTA that can point anywhere. When Axia is ready to publish content, it writes a .md file, commits it to the repository, and pushes. Cloudflare builds the site. The post is live, with correct SEO metadata, JSON-LD Article schema, RSS feed entry, and sitemap update — all automatic.

Axia never touches HTML. It writes Markdown. The infrastructure handles everything else.

The site also passes the isitagentready.com audit at the foundational level — discoverability, content structure, bot access control. An llms.txt file at the root tells AI crawlers exactly what V8 Global does, who we serve, and where to find key content. When AI systems cite sources, structured sites like this one get cited. Unstructured ones get ignored.

Why this matters for Scaffold clients

The architecture described above is the Scaffold deployment template.

Each client gets:

• An Astro site with their brand design
• Cloudflare Pages hosting with auto-deploy from GitHub
• Form handling via Pages Functions into their CRM
• GA4 with consent gating
• A blog pipeline ready for AI-generated content via Axia
• llms.txt and structured data for GEO and agent readiness

The setup cost is a Scaffold engagement. The ongoing cost is essentially zero — no CMS licence, no hosting fees beyond Cloudflare’s free tier for most sites, no platform dependency.

And once Axia is connected, content production is no longer a manual task. The site updates itself, based on signals Axia reads from GA4, the CRM, and the business itself.

The timeline

The migration happened the day before the V8 Nexus launch event. There was no slack in the schedule, no room for a CMS learning curve, and no appetite for platform risk the night before 30 executives were going to look up the website.

It shipped. It’s fast. It works. And it’s ready for what comes next.

That’s the Scaffold standard.