<- cd /workbench
> cat ./workbench/rebuilding-steveedmund-com-next-js-supabase-and-zero-git-field-publishing.md_

Rebuilding steveedmund.com: Next.js, Supabase, and Zero-Git Field Publishing

Nov 12, 2026•2 min read
DevelopmentPostgreSQLNext.js

For a while, steveedmund.com was static enough that updating it felt like a chore. Every time I wanted to post a quick note, I had to sit down at my desk, edit lib/dispatches.ts by hand, run a local build, and push a commit to GitHub. Working as a Field Service Engineer means I am not always at my desk, and good ideas usually show up on-site or in transit rather than in front of an IDE.

Over the past few days, I rebuilt the site from the ground up as a dynamic Next.js 16 application backed by Supabase and deployed on Vercel. This post is the first live test sent straight through the new /compose terminal without touching Git.

The Architecture Shift

Moving away from hardcoded TypeScript arrays meant splitting the presentation layer from the data layer while keeping the dark terminal look fast and lightweight.

  • Next.js App Router: Rebuilt the frontend with React Server Components, Markdown rendering (react-markdown), and tag-based cache invalidation so new posts go live the second they hit the database.
  • Supabase PostgreSQL: Moved all dispatch records into a locked-down Postgres schema using Row Level Security for public reads and server-only keys for writes.
  • Vercel Edge & DNS: Pointed DNS resolution for steveedmund.com and www.steveedmund.com to Vercel with automatic 308 redirects, encrypted environment secrets, and a daily keep-alive cron route so the database never sleeps during quiet weeks in the field.

Publishing From Anywhere

The real goal of this overhaul was building /compose, a passphrase-protected web terminal designed for mobile browsers and pinned as a standalone home-screen app.

Authentication runs through timing-safe SHA-256 verification and issues a 30-day signed HttpOnly cookie, keeping admin routes off the public client bundle. Keystrokes back up automatically to localStorage in case cellular signal drops mid-thought, and Server Actions calculate slugs, excerpts, and read times automatically on submit.

After sorting out a duplicate deployment project in Vercel and wiring the production environment variables into the main build, the pipeline is officially live. Now I can jot down rough hardware notes on my phone, stash private drafts, or publish straight to the main feed from anywhere.