Event Proposals

6 proposals

1. Proposed

   Architecture Archaeology: Map a System From Traffic, Logs, and Source

   Reverse-engineer a messy service so newcomers can understand how it really works.

   Difficulty: Mixed Duration: 2 hours Target date: October 23, 2026 #architecture#documentation#systems
2. Proposed

   Documentation Test Kitchen: Prove the Guide Works Before Publishing

   Treat documentation like software by testing setup guides, examples, and failure paths.

   Difficulty: Mixed Duration: 1 hour 30 minutes Target date: August 11, 2026 #developer-experience#documentation#testing
3. Proposed

   Knowledge Base Rescue: Make Support Articles Findable, Current, and Useful

   Fix stale help content using search logs, support tickets, ownership, and publishing rules.

   Difficulty: Mixed Duration: 2 hours Target date: November 24, 2026 #documentation#knowledge-base#support
4. Proposed

   Runbook Fire Drill: Follow the Instructions Exactly and See Where They Fail

   Test operational runbooks under realistic pressure, missing context, and partial outages.

   Difficulty: Mixed Duration: 2 hours Target date: January 28, 2027 #documentation#incident-response#runbooks
5. Proposed

   Service Catalog Rescue: Help Teams Know What Exists, Who Owns It, and What Breaks It

   Map services, dependencies, owners, runbooks, and risk signals into a useful operating catalog.

   Difficulty: Mixed Duration: 2 hours Target date: December 9, 2026 #documentation#ownership#service-catalog
6. Proposed

   Static Site Release Readiness: Builds, Assets, Redirects, and Rollbacks

   A practical two-hour session on Static Site Release Readiness, focused on Builds, Assets, Redirects, and Rollbacks. Attendees work through concrete engineering tradeoffs, review examples, and leave with a checklist they can apply in real team projects.

   Difficulty: Intermediate Duration: 2 hours Target date: October 8, 2026 #deployment#documentation#static-sites