How Claude Helps

Everything on this site that Claude has a hand in, collected in one place. Click any bar for the longer story. The list will grow as the experiment does.

A bit of context on me: I work in IT, so this isn't a complete leap into the dark, but I'm not a developer by trade either. I know enough to get by and ask decent questions. Most of what's below is really just me following that curiosity to see how far it goes.

Journal entriesA dictated recap becomes a post
  1. I dictate a quick recap of the day, most days.
  2. Claude drafts it into a readable post and strips out anything that shouldn't be public.
  3. I read it and either approve it or send it back. Every post, no exceptions.
  4. Once approved, it's committed and the site rebuilds itself.

Claude never invents what happened. If I didn't say it, it doesn't go in the post.

The site itselfBuilt in conversation, not from a template

There's no blogging platform under this. Claude wrote the little generator that turns my Markdown files into these pages, and the design too: the winding trail, the scrapbook patches, the pup that trots along as you scroll. I described what I wanted, Claude built it, and we went back and forth until it felt right.

MilestonesHer "firsts", spotted automatically

The milestones page mostly writes itself. Every time the site rebuilds, it works out how long Annie has been home and pulls any "first time she..." moments out of posts I've already approved, quoting them word for word. Nothing gets made up; it can only surface things I already wrote.

Keeping things privateWhat never makes it onto the page

Before anything is published, Claude strips location data out of every photo and holds back anything that could identify exactly where we live or when the house is empty. A public diary about our dog shouldn't double as a map to our front door.

← Back to About This Project