# Event Recap Process An event recap works best as a cross-team publishing loop that begins before the event, captures evidence during it, and keeps refining one canonical recap after publication. <!-- atomicity: 1 idea ✓ --> ## Process An example process could be: 1. **BEFORE event....** publishing team create an outline for the SEO optimized pre-event post 2. Community/event team fills in things we miss and drafts some bits 3. pub clean it up and add sparkles 4. community team signs off and publishes pre-event post 5. pub provide tentative SEO-based outline for recap 6. **DURING event....** community team swarms on notes 7. **AFTER** event... one person consolidates the notes and arranges in an outline, ideally taking from the SEO outline 8. community team (or pub if topic is easy for us) drafts based on notes. Community may be better for specific themes and importance we might miss. 9. pub cleans it up and add sparkles 10. community team signs off and publishes recap 11. we update it for the next week or so to keep a fresh date with Google, add more images, more context, stuff coming up in competing recaps... ## Links - [[3. Resources/Permanent Notes/Curated Mastery Conferences Serve Practitioners That Volume Conferences Cannot]] — applies-in: the recap process should preserve the practitioner depth and event purpose that justified the gathering. - [[3. Resources/Permanent Notes/Concentration Beats Coverage Under Retrieval]] — applies-in: continually improving one canonical recap concentrates authority instead of scattering near-duplicate event coverage. - [[3. Resources/Permanent Notes/The Four Objectives Framework Replaces Vanity Metrics in DevRel]] — constrains: recap choices should serve an explicit awareness, activation, engagement, or retention objective rather than freshness alone. - [[3. Resources/MOCs/DevRel MOC]] — applies-in: the MOC lists this note under Connected Permanent Notes (synthesis 2026-07-21 — run 16).