Course 1 · operating manual
How connorclaire.ca works
Seven short lessons so you can expand and maintain the site yourself. Dashboards first. Official docs as homework. No command line, no React bootcamp.
Work the lessons in order. Finding the right screen is the skill. Editing can wait until you know what you are looking at.
You are done when you can
Name each box in one sentence
Cloudflare is the phone book. Vercel builds and hosts. GitHub keeps history. Next.js is the site code. Migadu is mail.
Trace a visit
A visitor types the name → Cloudflare looks it up → Vercel serves the page. Mail peels off at the MX row and never visits Vercel.
Trace a change
You edit → commit on main → Vercel deployment turns Ready → the live URL updates. Cloudflare’s records do not move.
Pick the right dashboard when it breaks
Wrong page → Vercel Deployments. Push missing → GitHub. Name or email → Cloudflare DNS. Inbox → Migadu.
The five boxes
Click a box. Then toggle the two journeys. Live site: connorclaire.ca
The site itself
Next.js
The code and pages that become connorclaire.ca. Files under app/ are routes; posts/ are blog posts.
- Browser
- Cloudflare
- Vercel
- Page
Mail peels off at Cloudflare (MX) and never enters Vercel. GitHub is not on this path.
Lessons
- 0.Five boxes, two journeysThis page, then https://connorclaire.ca
- 1.Type the name, get the houseThe browser address bar, then connorclaire.ca
- 2.The phone book: A/CNAME vs MXCloudflare dashboard → connorclaire.ca → DNS → Records
- 3.The factory: Deployments, Ready, ProductionVercel → connorclaire-next → Deployments
- 4.The cabinet: commits on mainGitHub → connorclaire-next → commits on main
- 5.Safety: Instant RollbackVercel project overview → Instant Rollback
- 6.Which dashboard?The card you keep: If X, open Y