Fill the shell

The site you deployed in chapter 02 is structurally complete but full of placeholders. This chapter is about replacing those placeholders with the real you.

How content is organized

Two folders matter:

content/shell.yaml — your identity. Name, headline, bio, contact, experience bullets, tone tags, admired sites. One file, one source of truth. Every layout reads from here. When you change it, the home page updates everywhere.
content/articles/ — your writing. One markdown file per article, with title, date, summary in the frontmatter and your prose underneath.

A rule that matters later: when you spawn design variants in chapter 04, the variant agents only edit layout and styling. They never touch content/. So your bio survives every redesign untouched.

Edit the shell

Open Claude Code from inside ~/Code/megmude-site and ask:

Open content/shell.yaml. Help me rewrite my bio in three different tones — confident, warm, editorial — keeping it to 3 to 4 sentences each, so I can pick.

When you have a version you like, paste it in or ask Claude to update the file with your choice. Then update the rest of the fields:

identity.name — your name as it should appear at the top of the site.
identity.headline — one short line. “Operations executive.” “CFO and operator.” “Founder and writer.” Match the way you’d introduce yourself in a meeting.
identity.location — city, state, or country. Optional but nice.
contact.email — the address you want recruiters to use.
contact.linkedin — full URL.
contact.phone — leave null unless you want it public.
experience — 3 to 5 bullets. Role, company, year span, one-line impact.
tone_tags — pick 3 to 5 from the curated list (warm, confident, modern, editorial, minimal, playful, serious, bold). The variant agents read these in chapter 04 to choose a design direction.
admired_sites — 2 to 3 personal or professional sites whose feel you respond to. Variant agents fetch these for inspiration.

Add real writing

Drop one or two articles into content/articles/. Frontmatter shape:

---
title: "The article title"
date: 2026-05-07
summary: "One sentence describing the article."
---

The body of the article in plain markdown.

Filenames are YYYY-MM-DD-short-slug.md. Example: 2026-05-07-on-leadership-transitions.md.

If you want help with a draft, ask Claude:

I want to write a short article about [topic]. Help me outline it in 5 beats, then draft each beat in 2 to 3 sentences. Conversational tone, executive audience.

Iterate until you’re happy, then save the result into content/articles/.

See it locally

In Claude Code or Terminal:

npm run dev

Visit http://localhost:4321/. Your home page should reflect every field you edited and list every article you added. Stop the dev server with Ctrl+C when you’re done.

Push and redeploy

When you’re ready to update production:

Paste into Claude Code:

Stage and commit my shell and article changes with a clear message. Push to GitHub. Then run npm run build and wrangler pages deploy dist --project-name=megmude-site --branch=main --commit-dirty=true.

Within ~30 seconds the new content is live at https://megmude-site.pages.dev.