Purpose
Use this guide to describe the practical workflow focus behind Codex SF events and resources. It supports the public story around TatianaSF, Codex SF, HackKit, and builder-friendly community programming in San Francisco.
Workflow principles
- Start with a real user, workflow, or community need.
- Keep the first demo small enough to build and explain.
- Use Codex to speed up scaffolding, refactoring, documentation, tests, and iteration.
- Track what is real, mocked, manual, or incomplete.
- Keep private data out of public demos and public repositories.
Event workflow
1. Frame the builder challenge in plain language.
2. Pick a small useful outcome.
3. Create a working artifact or demo path.
4. Use public-safe templates for judging, promotion, and follow-up.
5. Capture lessons learned that future organizers can reuse.
How this connects to Codex SF
Codex SF publishes resources that make these workflows repeatable. HackKit gives organizers the event structure, while the resource library gives participants and volunteers public-safe templates they can use before, during, and after a hackathon.
Related public pages
- [TatianaSF creator profile](/TatianaSF/)
- [Codex SF creator notes](/resources/codex-sf-creator-notes/)
- [HackKit start here](/hackkit/start-here/)
- [Event checklist](/resources/event-checklist/)
- [Post-event follow-up templates](/resources/post-event-follow-up-templates/)
Public-safe boundaries
Do not include private attendee data, sponsor conversations, internal plans, credentials, or unpublished event logistics in this public workflow guide.