Midsummer Documentation¶

Welcome to the documentation for Midsummer, the independent convention management platform. This site is written for the people who use Midsummer to run a convention: attendees, event organizers, and event technical staff.

Tip

Midsummer shows friendly, descriptive errors directly in the app. Every error code links back to this site so you can read exactly what went wrong and what you can do about it. See the error reference.

Where to start¶

Getting started	Sign in, magic links, two-factor authentication, and the basics of navigating your event.
Module quickstarts	Step-by-step guides for every module: Register, Vendor, Schedule, Staff, Shop, Inventory, and Chat.
HR & permissions	How departments, roles, and per-module ownership turn into the four permission levels.
Error reference	What each error code means and how to fix it, broken down by who you are.

The seven modules at a glance¶

Register — registration forms, tiers, merchandise, check-in, and badges.
Vendor — the dealer’s-room: applications, jury selection, table payment, and at-show check-in.
Schedule — calls for papers, panel submissions, scheduling, digital signage, and the public schedule.
Staff — departments, volunteers, HR/personnel files, shifts, and time-clocking.
Shop — a standalone storefront with cart, Stripe checkout, and QR-code fulfillment.
Inventory — barcode-tagged asset tracking: check-out/in to staff, boxes, and logistics terminals for load-in and tear-down.
Chat — staff-only team chat: department channels kept in sync with rosters, group chats, and direct messages.

Three audiences¶

Where it matters, this documentation addresses three classes of reader:

Who	What they need to know
Attendees / Users	People registering, applying to vend, submitting panels, or shopping. Most pages lead with the attendee perspective.
Event Organizers	The people configuring the event and its modules (forms, tiers, schedules, departments). They resolve most configuration errors.
Event Technical Staff	The people operating Midsummer during the event (check-in terminals, kiosks, fulfillment) and triaging issues with Midsummer developers.