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>
1.8 KiB
1.8 KiB
aliases, Is A, Belongs to, Status, Owner
| aliases | Is A | Belongs to | Status | Owner | |
|---|---|---|---|---|---|
|
Task | 24q2 | Done | person-luca-rossi |
Update editorial guidelines for Sara
With person-sara-ricci joining as editor through the 24q2-hire-editor project, the existing informal editorial guidelines needed to be formalized into a comprehensive document. Sara needed clear guidance on tone, style, content structure, and the editorial review process so she could edit independently without constant back-and-forth with person-luca-rossi.
The guidelines cover everything from headline formatting conventions and paragraph length preferences to the handling of code snippets, the voice for different content types (deep dives vs. opinion pieces vs. interviews), and the approval workflow. The document also includes a "red lines" section covering topics and framings to avoid.
Acceptance criteria
- Document the newsletter's voice and tone with concrete examples
- Define the editorial workflow (draft -> edit -> review -> publish)
- Create a style guide covering formatting, code blocks, image usage, and link conventions
- Include a section on content types and their distinct editorial requirements
- Review the guidelines with person-sara-ricci and incorporate her feedback
Notes
- Sara's feedback significantly improved the guidelines. She flagged several areas where the implicit rules in Luca's head were inconsistent or contradictory, which helped clarify the actual editorial standards.
- The guidelines document is maintained in the vault as procedure-editorial-guidelines and is updated whenever a new editorial decision sets a precedent.
- This investment paid off immediately -- Sara's first independent edit required only minor revisions, compared to the extensive back-and-forth expected without guidelines.