About

This website started as an experiment. I wanted to see how much of a site I could get AI to build without me doing anything more than writing prompts. It turned out to be quite a lot. At first I wouldn't even read the code that it produced but eventually I was forced to when it came to troubleshooting authentication issues that I was hitting on mobile phones. I participated in troubleshooting sessions and copied and pasted code fixes but I didn't actually author anything.

I don't know much about the tech stack behind this site. My background is in Java/JSF. I used to code in PHP, but haven't looked at that in a long time. So I asked ChatGPT to describe it. This is what it came back with:

Let’s unpack that clearly, using accurate technical terminology that you could use if describing it to other developers:

Type of Application

Your project would most accurately be described as:

A static-front-end, serverless web application built on Cloudflare Pages and Workers with a D1 (SQLite-based) database.

In plain developer language:

It’s a JAMstack-style app (JavaScript, APIs, Markup) that uses Cloudflare’s serverless platform for both the static front-end and dynamic backend logic.

Key Architectural Layers

Frontend (Static Assets)

HTML, CSS, and JavaScript files are served via Cloudflare Pages (a static hosting service).
You’re not using a framework like React or Vue — so it’s more of a vanilla JavaScript SPA (Single-Page Application) or multi-page app depending on your routing.
Tailwind CSS (via CDN or build process) handles styling.

Backend Logic (APIs)

The logic (like login, CRUD operations, etc.) runs as Cloudflare Workers functions.
These are serverless edge functions that execute globally at Cloudflare’s edge network, not on a traditional web server.

Database

Cloudflare D1 is used for persistent data (blog posts, users, etc.).
D1 is an SQLite-compatible database, also running at the edge.

Configuration

wrangler.toml is the configuration file for Wrangler, Cloudflare’s CLI tool. It defines:

Worker routes and bindings (like D1, KV, or environment variables)
Deployment settings
Compatibility flags

Modern Architectural Labels You Could Use

Here are a few terms developers would immediately understand:

Term	Meaning / Context
Serverless Web Application	No dedicated backend server — everything runs as functions on demand (via Workers).
JAMstack Application	Combines static files with JavaScript and APIs for interactivity.
Edge-deployed App	Logic runs on the edge network, close to the user, minimizing latency.
Cloudflare Full-Stack App	Entirely hosted on Cloudflare’s platform — Pages + Workers + D1.
Static-front-end with Serverless Backend	A traditional distinction that makes clear where logic runs.

If You Were Describing It in One Sentence

Here are a few options depending on your audience:

Technical audience:

“It’s a JAMstack-style blog application built on Cloudflare Pages and Workers, with a D1 edge database and serverless API endpoints written in JavaScript.”

Recruiter or portfolio version:

“A full-stack, serverless web application deployed globally on Cloudflare’s edge network using modern web standards (HTML, Tailwind CSS, and JavaScript).”

Simpler version:

“A fully serverless blog platform built with Cloudflare’s edge technology — everything from front-end to database runs without a traditional server.”

Read the development log