Building a Serverless Portfolio on Cloudflare Workers with Astro

The Quest for Modern Edge Performance

When designing my personal developer platform at joshsimpson.dev, I wanted a solution that combined strict security posture, low latency, and zero operational overhead. Standard static site generators often lack server-side extensibility, while full traditional node servers require constant patching and container orchestration.

Enter Astro & Cloudflare Edge

Astro 4 provides an ideal architecture: zero JavaScript shipped to the client by default, HTML-first component hydration, and native edge adapters like @astrojs/cloudflare.

// astro.config.mjs
import { defineConfig } from 'astro/config';
import cloudflare from '@astrojs/cloudflare';

export default defineConfig({
  site: 'https://joshsimpson.dev',
  output: 'server',
  adapter: cloudflare(),
});

Continuous Git-Driven Workflows

With Cloudflare Pages connected to GitHub, every git push automatically triggers an isolated build pipeline. Edge workers distribute static assets to 300+ data centers worldwide in seconds.

Key Takeaways

• Sub-100ms Latency: Assets and edge functions execute near the user.
• Security Hardened: Minimal attack surface with static output and edge validation.
• Frictionless Publishing: Adding a new post or lab project requires only a git commit or an edit in /admin.