How It’s Built

This domain used to run on a GoDaddy website and CMS.

paulmress.com used to be hosted on GoDaddy’s Website Builder — a SaaS website-and-CMS product with a drag-and-drop editor, no version history, and no way to make a change without editing the live site directly. What replaced it is a system: a content brief becomes a prompt, a prompt becomes a governed, version-controlled page, and a change ships live in about a minute. This is that system, explained.

~1 min

from a written brief to a live, deployed page

100%

of changes tracked with a real commit history

$0

in CMS or website-builder license fees

Before & After

What actually changed

Not just a redesign — a different platform, and a different way of making changes at all.

Before

GoDaddy Website & CMS (SaaS)

A hosted website builder with a drag-and-drop editor. Every change was made by hand, directly on the live site — no version history, no design system, no record of what changed or why. Consistency depended entirely on remembering what the last version looked like.

After

A system I run

A content brief in Google Docs becomes a prompt. AI writes the page. A design system decides what’s allowed. GitHub records every change with a real commit history. GitHub Pages deploys it automatically — live in about a minute, every time.

How A Change Happens

Five steps, every time

The same process for a typo fix as for a brand-new page — that’s the point.

Write the brief

A content brief lives in Google Docs — what the page should say, how it’s structured, what’s changing and why.

Hand it to AI

The brief becomes a prompt. AI writes the actual HTML, CSS, and copy — not a mockup, the real page.

The design system governs it

Every new component has to match the tokens and patterns already documented on the Design System page — nothing gets built from scratch.

Committed to GitHub

The change ships as a real commit with a real message — a permanent, reviewable history. Nothing is ever silently overwritten.

Live in about a minute

GitHub Pages rebuilds and deploys automatically. No IT ticket, no agency, no waiting on anyone.

Why It Matters

This isn’t a chatbot demo

It’s a small, production system with the same constraints a marketing org has to solve for at scale.

Governance you can point to

A design system plus a full commit history isn’t paperwork — it’s how AI-driven changes stay consistent and reversible instead of ad hoc.

Proven on myself first

Before asking a team to trust AI with their workflows, I built and shipped a real production system with one, end to end.

What AI-fluent actually looks like

A live system with real constraints: brand consistency, a version history, and a deploy pipeline that just works.

See the design system that governs it

Every token, component, and pattern this site runs on — documented, and still growing.

View the Design System