Repository navigation
For event staff
You edit the site. You do not deploy it. CCM (or another operator) handles Firebase, email sending, and tickets behind the scenes.
- Pages (about, travel, conduct, and anything else seeded for the event)
- Schedule, sessions, and bookmarks settings
- Speakers: invite, accept, profile, approval
- Attendees and the public directory
- Sponsors and organizations
- Live updates (from the admin form, not from Slack)
- Theme: colors and the bundled font sets
- Badges from the predefined list
Legal pages ship as templates. They stay flagged until your counsel signs off. Do not publish another organization's terms.
Draft and live are separate. Publishing copies the draft to what attendees see. It is not a code deploy. If a change is not on the public site, check that you published, not only saved.
Invite by email. They accept with a login code, the same way attendees sign in. Do not send them a magic link. One speaker record is the source of truth — if a name is wrong in three places, fix the speaker record.
Upload or link files on the session. Embargo holds them until the session ends. Prefer a real label ("Slides") over a raw URL as the link text.
Your operator chose Eventbrite, a spreadsheet import, or no ticketing. Signup email should match that choice. If a new person is told to "buy on Eventbrite" and you are not using Eventbrite, that is a product bug — file it.
- Someone needs admin
- Login codes are not arriving (sender domain / spam)
- The site is down
- You need a new day added after launch and the admin will not let you
An initiative of the Center for Cooperative Media at Montclair State University. Code is Apache-2.0. The Run of Show name is reserved to CCM.
Using a site
Reference
Code