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 | 25q2 | Done | person-luca-rossi |
Set up community Discord structure
The newsletter audience had been requesting a community space for over a year. After evaluating options (Slack, Circle, Discord, custom forum), Discord was chosen for its familiarity with the developer audience, free tier capabilities, and strong bot ecosystem. This task set up the Discord server structure, moderation rules, and initial content to seed the community before a soft launch to engaged subscribers.
The community strategy was deliberately conservative: start with a small, invite-only group of the most engaged subscribers, establish healthy norms, and then gradually open access. The goal was quality of conversations over quantity of members.
Acceptance criteria
- Create the Discord server with appropriate channel structure (introductions, general, ask-anything, content-feedback, off-topic)
- Write community guidelines and pin them in the welcome channel
- Set up moderation bots and assign moderation roles
- Create a "beta invite" list of the top 200 most engaged subscribers
- Draft the launch announcement email for the beta invite group
Notes
- The beta launch went well -- 87 of 200 invited subscribers joined (43.5% acceptance rate), and initial conversations were high-quality. The invite-only framing created a sense of exclusivity that motivated engagement.
- The "content-feedback" channel has been particularly valuable. Subscribers provide early input on newsletter drafts, essentially serving as a focus group. This directly improved several editions.
- person-sara-ricci volunteered to moderate the community alongside her editing role, which has worked well given the manageable size.