This guide covers the organizer console workflows used to prepare and run DevCongress meetups.
Open the organizer console and sign in with the prototype organizer password:
/organizer-console/login
The base path can be changed with VITE_ADMIN_BASE_PATH.
Use the event list to create, edit, publish, and remove meetups. If a Luma import comes in with the wrong event shell, remove it from the organizer list and import the corrected public URL again.
Event outlines are optional. When a meetup has a known run of show, add time/title/type/lead rows on the event overview; otherwise leave the outline empty and continue with the event checklist, talks, attendance, and feedback flows. Organizers can paste a plain text program outline and let the editor split it into rows before saving or publishing.
Use the System design outline type for the monthly architecture scenario. The System Design tab reads from those outline rows and lets organizers keep the public prompt link and recap notes updated after the event.
Each event overview includes a chronological checklist. The checklist is the primary shared source of truth for event preparation and can advance event status when milestones are completed.
Quarterly meetup checklists are intentionally short: create the event shell, then update it with the G-Meet link from Edem.
Before an event is published publicly, organizers can disable incomplete checklist milestones that do not apply to that event. Disabled milestones stay visible, cannot be checked off, and do not count toward checklist progress.
The Talks section is split into a workflow: CFP, Proposals, Program, and Legacy Backfill. Use CFP to open or close the public proposal form and copy the share link for upcoming monthly meetups only. Use Proposals to review public CFP submissions, select or reject speakers, then copy selected-speaker slides links from the shared link shelf once speakers are selected. Use Program to manage confirmed talks, slides, reminders, and publishing. Legacy Backfill is temporary cleanup for confirmed or past talks that did not go through the CFP flow; it generates speaker archive links and keeps newly generated links available to copy/open until organizers remove them. Speaker links are tied to the event month and close after one successful submission.
The Speakers section keeps the invite/access list aligned with the program. Adding a manual talk also keeps that speaker email available for speaker access.
The Attendance section accepts a Luma guest CSV export for the event. After import, organizers can review:
- Approved registrations
- Recorded check-ins
- Approved no-shows
- Check-in rate
- Registered people who did not check in
The global Attendance Hub gives a month-by-month ledger for venue planning.
The Feedback section lets organizers prepare event-scoped feedback forms, choose required questions, preview the public form, and review responses.
The Feedback Hub also includes route-level app feedback from testers.
The Quiz section supports building questions and hosting a live quiz. Quiz is currently a preview/phase-two area and still uses polling rather than a production realtime channel.
The System Design tab is the monthly scenario workspace. Add the scenario as a System design row in the event overview's program outline, then use the tab to publish the prompt link and short recap notes. Public meetup schedules link that row into the archive entry for the same meetup, where attendees can read the recap and open the prompt deck.