On The 8 Spot

From 3,370 old posts to a versioned writing workflow in three weeks

A case study in turning a long-running personal blog into something an AI collaborator can work with, without losing the author's voice

Download the long edition (EPUB, 29 KB)

At a glance

Situation A personal blog running since 2007, with about 3,370 posts, a WordPress export as the only structured copy, and a second site the author wanted to write on seriously
Approach Extract the archive to Markdown, write a style guide from the author's own posts, give each article a git history, and keep Claude as a drafting and research partner under written rules
Window 4 to 21 October 2026, with commits on 13 of those 18 days
Output A 3,381-file Markdown archive, a style guide, a post template, 7 published pieces on two sites, 4 drafts in progress, and 93 commits recording how each piece evolved

The situation

The blog, On The 8 Spot, started in 2007. By 2026 it held thousands of posts in one WordPress database, and the only portable copy was a 14 MB export file. A second site, a collaborative essay blog, was where the author wanted to write policy pieces in earnest.

Three problems stood in the way of writing well with an AI assistant:

How the work was run

  1. Read the export, don't load it. The export is too large to read whole, so it was parsed with a script and the posts were written out one per file, named by date and slug, with title, date, categories, tags and the original URL in the front matter.
  2. Sort by who wrote it. Using the blog's own categories, the 3,381 files were split into the author's own posts (1,124), reposted articles by other people (1,445), everything else (803) and the 9 pages. That split matters later: only the first group says anything about the author's voice, and the reposts must never be mistaken for it.
  3. Write the style guide from the evidence. A read of the author's own posts, plus guest posts on the second site, produced a guide covering the core voice, signature moves, habits to tighten, post types with rough lengths, and instructions for Claude. It states its own limits: most of the strongest first-person writing is from 2008 to 2011.
  4. Give each site a folder and each post a lifecycle. Each site has drafts/, published/ and assets/. One Markdown file per post carries a status, a publish date and the WordPress post ID once it is live.
  5. Commit at every stage. One post per commit, with messages like research:, draft:, revise: and publish:, so the history reads as the article's biography. A private remote keeps a backup.
  6. Write the rules down where the assistant reads them. A short project file tells Claude which site it is writing for, to read the style guide first, to suggest edits rather than rewrite, and never to publish without confirmation.

What the history shows

Of the 93 commits, the verb in the message gives a rough picture of the work:

Kind of commit Count
revise: 44
research: 17
draft: 11
publish: 8
docs: 3
Other (setup, tooling) 10

Revision outnumbered first drafts four to one. Many of the revisions are fact checks, such as confirming a figure against the full text of a government order, replacing a claim that could not be supported with a safer one, or adding a source. Others record the author's own corrections, such as a note that an unnamed friend's story should stay anonymous, or a replacement ending in the author's words.

The output so far is 11 posts and drafts totalling about 23,000 words, across the two sites. Seven are published and four are in draft.

Where it went wrong, and how it was caught

What was left open

Takeaways

  1. Know what you have before you write with it. Sorting the archive by authorship made the style guide possible and kept other people's words out of it.
  2. Put the voice in writing. A style guide drawn from the author's real posts, including its own limits, gave the assistant something to follow other than its defaults.
  3. Commit the thinking, not just the result. Stage-by-stage commits turned the history into a record of what was researched, checked and cut.
  4. Make the assistant suggest, not decide. The author keeps the final say, and nothing goes live without confirmation.
  5. Treat personal data as a first-class risk. Excluding the export, stripping comments and keeping private analysis local were set up on day one, not added after.

About these numbers

File counts come from the archive's own README and a directory count. Commit counts and dates come from the repository history. Word counts are from the post files and include drafts. This case study does not report session time or message counts, because the transcripts were not analysed.