Guided event form
Best when you want prompts for every required detail. A draft event folder and pull request are prepared automatically for maintainer review.
Open the form
Community publishing / GitHub reviewed
Codex ambassadors can add a Meetup or Build Night without redesigning a page. Bring the facts, the story, and the evidence; the site takes care of the structure.
For invited repository collaborators
One path / Four clear moves
Every event follows the same content contract, including the six editions already in the archive.
Use the guided event form, or copy an existing dated event folder when you are comfortable working directly in GitHub.
Add verified dates, the Luma source, a concise account of the room, and web-ready photographs with meaningful alternative text.
GitHub validates the event structure, media references, site build, event routes, and existing archive before review.
A maintainer reviews the contribution, merges it into the community record, and republishes the approved site manually.
Choose your GitHub path
Best when you want prompts for every required detail. A draft event folder and pull request are prepared automatically for maintainer review.
Open the formCopy the template, name the folder with the Sydney event date and edition slug, add the local photographs, then open a pull request.
Follow the guideThe event folder
The Markdown file carries the verified event facts and story. The photographs stay beside it, with captions, alternative text, and credits declared in the same file.
public/events/
└── meetups/
└── 2026-09-16-meetup-04/
├── event.md
├── hero.webp
└── gallery-01.webpWhat stays protected
Add the next edition
Start with the guided form. The contribution becomes public only after the facts, media, and resulting page have been reviewed.