@gurupanguji

April 20-21 Snippet Batch Design

Objective

Migrate the unblogged April 20 and April 21, 2026 notes from the Obsidian rr vault’s lit/snippets folder into Jekyll blog posts, then schedule the resulting posts one per day starting on 2026-04-25.

Scope

• Source only notes in lit/snippets created on 2026-04-20 or 2026-04-21.
• Include only notes where is_blogged: false.
• Preserve the body text exactly as written in Obsidian.
• Convert each note into a Jekyll _posts/YYYY-MM-DD-slug.md file.
• Generate matching companion snippet files in _snippets/YYYY-MM-DD-slug.md.
• Schedule the batch one post per day, in created-time order, starting with 2026-04-25.
• Sync the source notes back to mark them as blogged with is_blogged: true and blogged_at set to the scheduled publish timestamp.

Source Set

The current vault scan shows six eligible notes. The April 20 Gemini note is already blogged and stays out of this batch.

• 2026-04-21-Celebrating computers at Omacon.md
• 2026-04-21-Another Day Has Come.md
• 2026-04-21-Human Error is OK! Machine Madness is a No-No! Why?.md
• 2026-04-21-Eat Your Words.md
• 2026-04-21-Tim Cook Well done.md
• 2026-04-21-Framework-13-Pro-the-developer-laptop.md

Schedule

Map the notes in chronological created order to these publish dates:

• 2026-04-25
• 2026-04-26
• 2026-04-27
• 2026-04-28
• 2026-04-29
• 2026-04-30
• 2026-05-01

Each scheduled post should use the repository’s standard future-post timestamp convention: 05:00 PT, which validates as 12:00:00 +0000 during daylight saving time.

Post Shape

• Use the existing snippet-post format already present in this repo.
• Keep the 🔗 title prefix for the Jekyll post title.
• Preserve the source excerpt and body content exactly.
• Infer categories and tags from nearby link-post patterns in the repository instead of inventing a new taxonomy.
• Keep front matter valid for Jekyll and compatible with scripts/validate_posts.py.

Workflow

1. Create or reuse the GitHub issue that tracks this batch.
2. Work on a feature branch, not main.
3. Write the implementation plan in docs/superpowers/plans/.
4. Transform the seven source notes into _posts/ and _snippets/ files with the scheduled publish dates above.
5. Update the source notes in Obsidian so the blogged flags and timestamps match the generated posts.
6. Verify filename/date alignment, body preservation, and scheduled timestamp compliance.
7. Commit, push, and open a PR.

Risks and Constraints

• Obsidian CLI access is unavailable unless the app is running, so the batch may need to use the vault files directly for read/write work.
• The repo does not currently contain scripts/migrate_snippets.py, so the batch must use an equivalent local transform if that script remains absent.
• The schedule must stay chronological. Do not compress or reorder the dates once the batch mapping is set.

Success Criteria

• Six posts exist in _posts/ with dates from 2026-04-25 through 2026-04-30.
• Six matching files exist in _snippets/.
• The source notes in the vault show is_blogged: true and the expected blogged_at values.
• scripts/validate_posts.py accepts the staged or committed posts.