claude
f47ccee96d
A standalone blog/ folder (not course content) with drafts for jpaul.me: an announcement, a getting-started piece, then a hybrid weekly series — one post per module for Units 1-2 (posts 03-13) and one per unit for the back half (14-16) plus a capstone finale (17). Each post carries WordPress metadata, a [COURSE LINK] placeholder, and [insert screenshot] blocks for Justin to fill before publishing. README.md holds the manifest + checklist. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015EghAChc9UbcF78t55mfdf
54 lines
3.7 KiB
Markdown
54 lines
3.7 KiB
Markdown
# Blog posts (jpaul.me)
|
||
|
||
Drafts of blog posts for **jpaul.me** that promote and add value around *The Workflow*
|
||
course. **This folder is not course content** — it lives here only so the drafts are
|
||
version-controlled alongside the material they describe. Pull it out before any public
|
||
GitHub mirror push if you don't want the drafts shipped publicly.
|
||
|
||
## Conventions
|
||
|
||
- One Markdown file per post, numbered in intended publish order: `NN-slug.md`.
|
||
- Each file opens with a metadata block (suggested title, slug, meta description, tags)
|
||
for easy paste into WordPress — delete it before publishing or keep it as notes.
|
||
- Screenshots are left as `[insert a screenshot referencing XYZ here]` placeholders for
|
||
Justin to fill before publishing.
|
||
- Voice: conversational, first-person, value-first. Course link is a soft CTA, not the
|
||
whole point — each post should stand on its own for a reader who never takes the course.
|
||
|
||
## Publishing cadence & manifest
|
||
|
||
**Structure:** announcement + getting-started, then a weekly series. Hybrid granularity —
|
||
one post per *module* for the durable core (Units 1–2), one post per *unit* for the
|
||
faster-moving back half (Units 3–5), plus a capstone finale. 17 posts total.
|
||
|
||
| # | File | Covers | Working title |
|
||
|---|------|--------|---------------|
|
||
| 01 | `01-announcing-the-workflow.md` | Announcement / thesis | Your AI Already Writes Good Code. That's Not Your Problem. |
|
||
| 02 | `02-getting-started-the-copy-paste-problem.md` | Module 1 + setup | The Copy-Paste Problem (and How to Actually Get Started) |
|
||
| 03 | `03-version-control-safety-net.md` | Module 2 | Git Is Undo for the AI (and Memory It Can Read Back) |
|
||
| 04 | `04-version-control-for-words.md` | Module 3 | Version Control Isn't Just for Code — Start With Your Words |
|
||
| 05 | `05-getting-the-ai-out-of-the-browser.md` | Module 4 | Let the AI Edit Your Files (Yes, Really — Here's Why It's Safe) |
|
||
| 06 | `06-commit-the-ai-config.md` | Module 5 | Commit the AI's Config, Not Just the Code |
|
||
| 07 | `07-branches-sandboxes.md` | Module 6 | Let the AI Try Something Reckless — On a Branch |
|
||
| 08 | `08-worktrees-parallel-agents.md` | Module 7 | Stop Making Your Agents Take Turns: Git Worktrees |
|
||
| 09 | `09-remotes-and-hosting.md` | Module 8 | Your Repo Lives on One Disk. That's One Spilled Coffee From Gone. |
|
||
| 10 | `10-issues-task-layer.md` | Module 9 | Who Picks This Up? Writing Issues for a Team of Humans and Agents |
|
||
| 11 | `11-reviewing-code-you-didnt-write.md` | Module 10 | The AI's Code Looks Right. That's the Problem. |
|
||
| 12 | `12-collaboration-humans-and-agents.md` | Module 11 | Half Your Teammates Aren't Human (and the Loop Doesn't Care) |
|
||
| 13 | `13-revert-reset-recovery.md` | Module 12 | Your AI Just Force-Pushed Over a Day of Work. Now What? |
|
||
| 14 | `14-unit3-automate-checking-shipping.md` | Unit 3 (M13–19) | AI Made Writing Code Cheap. Now Automate the Catching. |
|
||
| 15 | `15-unit4-extend-the-ai.md` | Unit 4 (M20–23) | Giving the AI Hands: Extending It Into Your Real Systems |
|
||
| 16 | `16-unit5-ai-in-the-loop.md` | Unit 5 (M24–27) | Letting the AI Off the Leash (Without Getting Bitten) |
|
||
| 17 | `17-capstone-the-full-loop.md` | Capstone | The Full Loop: One Feature, End to End |
|
||
|
||
Each file's top-of-file HTML comment holds the suggested title, slug, meta description,
|
||
and tags for WordPress. Titles above are starting points — every post also carries an
|
||
alt title in its metadata block.
|
||
|
||
## Before publishing — checklist
|
||
|
||
- Replace every `[COURSE LINK]` placeholder with the public course URL (the GitHub mirror
|
||
once it's live, or the git.jpaul.io repo).
|
||
- Fill every `[insert a screenshot referencing XYZ here]` placeholder with a real image.
|
||
- Decide whether to keep or strip the top-of-file metadata comment block.
|