City of Auburn, AL
MyGov Design Documentation
Living design documents for the MyGov platform. Organized by what something is — a cross-cutting layer, a platform dependency, or an integrated module — rather than one doc per feature.
Start Here
The system map is the entry point — it names every module, describes its responsibility, and maps the integration seams that connect them.
Cross-Cutting Concerns
Shared conceptual layers that multiple modules consume. Not a feature of any single module — rather the connective tissue that lets modules interoperate around location, time, and presentation.
Location In Progress
The spatial authority boundary, the Facility → FacilitySpace model, canonical FK decisions, and ArcGIS / address service integration.
Calendar & Time Draft
The time registry. Programs, Boards, Holidays, Reservations, and ICS imports all feed into shared Calendars. Independent of any single module.
Distribution & Publishing Draft
Where data becomes visible — the CMS/WebPages channel, eNotifier, web components, and transactional email. The Org → CMS entity/contact bridge.
Infrastructure & Integration Platform
Shared infrastructure that is not a business module — answers to "how do we accomplish X?" before writing any module-specific code.
Microsoft Platform In Progress
The guiding principle for M365 integration. Entra auth, Exchange resource mailboxes, Graph API patterns, Outlook calendar sync, and WCAG tradeoffs.
Workflow Engine In Progress
Config-driven automation. Triggers, handler library, context model, and the FormAction / ServerJob pattern that powers cross-module automations.
Complex Integration Modules
Business modules where the integration surface is deep enough to warrant a design document — covering data model, layer relationships, audit findings, and open decisions.
Reservations In Progress
Facility space booking — FacilitySpaceReservationConfig, occupancy types, availability rules, conflict detection, and Workflow Engine integration.
Programs & Registration In Progress
Parks and Library programs — session data model, calendar push, FacilitySpace location linkage, registration, and the external platform integration direction.
Forms Undocumented
The primary trigger source for the Workflow Engine and the input layer for most cross-module automations. Relationships documented; module audit pending.