b3126044e8
- Simplify flatten_vault API to return usize instead of MigrationResult struct - Add KEEP_FOLDERS: attachments/ and _themes/ alongside type/, config/, theme/ - Use HashSet for collision tracking in unique_filename - Update wikilinks from path-based [[folder/slug]] to title-based [[slug]] - Clean up empty directories after flattening - Flatten demo-vault-v2: move all notes from type-based subfolders to root - Update smoke tests for flat vault structure - Remove migrate_to_flat_vault from repair_vault (one-time migration only) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2.5 KiB
aliases, Is A, Belongs to, Has Measures, Has Procedures, Status
| aliases | Is A | Belongs to | Has Measures | Has Procedures | Status | |||
|---|---|---|---|---|---|---|---|---|
|
Responsibility | area-building |
|
Open |
Content Production
Content production is the engine behind Refactoring. Every week, the newsletter and supporting essays need to ship on time, at a quality bar that keeps readers coming back. This responsibility covers the full lifecycle of written content — from ideation and outlining through drafting, editing, and publishing — and it is the single most important operational commitment in the business.
Scope
- Writing and publishing the weekly Refactoring newsletter edition
- Producing standalone essays and deep-dive articles on engineering leadership topics
- Maintaining and executing the monthly content calendar and pillar plan
- Running A/B tests on subject lines, formats, and send times to optimize engagement
- Coordinating with person-sara-ricci on editorial review and copy quality
- Auditing and refreshing evergreen content to keep the archive valuable over time
Current state
The production cadence is stable: one newsletter edition plus at least one standalone essay ships every week. Reader feedback consistently lands above 4.5 out of 5 on quality, and the editorial pipeline with Sara has reduced last-minute scrambles significantly. The main challenge right now is balancing depth with consistency — some weeks the essay ideas demand more research time than the schedule allows, which can push social distribution to the back burner.
Pillar planning has helped front-load topic selection, but there is room to improve the feedback loop between measure-essay-quality-score data and future topic choices. The evergreen content audit is running quarterly but could benefit from being more systematic.
Key procedures
- procedure-weekly-newsletter
- procedure-monthly-pillar-planning
- procedure-content-calendar-review
- procedure-editorial-review
- procedure-newsletter-ab-testing
- procedure-social-media-scheduling
- procedure-evergreen-content-audit
- procedure-newsletter-metrics-weekly