It started as a PDF — the kind you'd print and fold into a golf bag pocket.
I dropped in everything that mattered: the reservation details, notes from a call with Pinehurst directly, the flight info the guys sent over. Claude turned that into a polished itinerary — finding course logos, real photos of the courses and restaurants, the expected weather for those dates, and a link to each place so nobody had to guess where they were headed.
A few rounds of feedback later, the PDF looked right. But golf trips don't hold still — a tee time moves, a flight gets delayed, the forecast changes the morning of. Once it's been sent out, a PDF has no way to know any of that happened. So I rebuilt it as a website instead: one that checks in on itself. It also meant James and Kevin, watching from home, could actually follow along — a live link to the round in 18Birdies, and new photos landing on the right day as soon as someone in the group took them. I did the building inside Claude Code, Anthropic's AI coding tool — describing what I wanted, reviewing what came back, and going another round wherever it didn't feel right yet.
Three routines run in the background on their own schedule, and one more links straight out to something that's already live.
A routine checks a weather service for each day of the trip, so the numbers on the page are today's, not the day I built it.
On travel days, another routine checks each flight against live tracking data — on time, delayed, landed — through the day.
The scoring section just links straight through to our live 18Birdies round — that one's live on its own; ours is just the link.
A third routine scans our shared Apple photo album for anything new, works out which day it belongs to, and drops it in — no uploading through the site.
The whole thing started about three weeks ago. The PDF itinerary took an hour or two inside Claude. Turning it into a live website took a few hours across a couple of sessions, plus tweaks since — not a long build, just a very iterated one.
It's one page, built and maintained through Claude Code. Claude itself only shares pages within my own company account by default, which doesn't work for a group of friends and family — so I set it up on GitHub Pages instead, a free way to host a page at a normal public web address: twkenly.github.io/Pinehurst-2026. Anyone with the link can open it, no account or app required.
What you won't find here is the working file: every small design revision along the way. This is the short version.
Want the fuller technical rundown — detailed enough to hand to your own Claude and start asking it questions? Download the build notes (.md).
Curious about the actual back-and-forth — what got asked for, and how it changed the site each time? Read the build history (.md).
Want to actually build one of your own? the full source is public on GitHub, and this technical setup doc has the exact routine prompts and schedules, ready to paste into your own Claude Code account.