Shared platform
Reusable public pages, admin tools, components, import pipelines, reporting, permissions, documentation, and operational controls.
Reusable multi-community platform
[Town] Today
[Town] Today is a reusable community information platform designed to give each town a focused public site while sharing one maintainable application, data model, administration system, import architecture, and operating model.
Platform model
One application, town-specific experiences
The platform separates reusable application behavior from town configuration and town-owned data so additional communities can be added without copying the application.
Architecture
Built to generalize without hiding the real production work
The platform grew out of Mt. Pulaski Today and is being refactored into a clear platform + town configuration + shared data model.
Reusable platform source is separated from town configuration and generated deployment output. Production URLs remain clean and never expose repository structure.
Supabase/PostgreSQL provides structured data, authentication, row-level security, auditing, and controlled server-side boundaries. Town/site ownership is treated as a first-class authorization concern.
One production system owns scheduled imports, notifications, maintenance, analytics support, migrations, and background work to avoid duplicate or competing jobs.
Work is tracked beyond code merge through source, CI/build, preview, deployment, production-data, browser, print, and permission verification as applicable.
Live implementation
Mt. Pulaski Today
The first production town demonstrates the platform across public information, local events, seasonal experiences, organizer workflows, administration, and production operations.
Community information in one place
- Events, schools, parks, directory profiles, local guides, public notices, and discovery tools
- Major-event experiences including Fall Fest, Halloween, Christmas on Vinegar Hill, and other local programs
- Responsive mobile-first public pages with stable town-domain URLs
Scoped operational tooling
- Town-aware administration and delegated organizer access
- Submissions, source review, imports, workspaces, schedules, flyers, maps, sponsors, and reporting
- Audit history, permission boundaries, contextual help, and production support workflows
Structured intake and review
- Global source administration with town-owned canonical events
- Staging and review when town/location resolution is uncertain
- Utility notices, source monitoring, event status, and recurring operational checks
Moving beyond one town
- Mt. Pulaski provides the parity baseline
- Lincoln is the second-town architecture proof
- New towns should require configuration and data, not a copied application tree
Documentation
[Town] Today Platform Wiki
The Platform Wiki documents architecture, administration, operations, security boundaries, verification standards, and troubleshooting practices. It shares the same source documentation system used by the town Help and Admin Help surfaces.
Direction
Where the platform is headed
The current phase is production hardening and continued multi-town generalization, while preserving stable behavior for the live Mt. Pulaski deployment.
Continue generalizing
- Remove remaining shared-code assumptions tied to one town
- Continue town-scoped settings, branding, and authorization work
- Use Lincoln to prove the second-town model
- Keep public URLs independent from repository/build structure
Continue hardening
- Core Web Vitals and field verification
- Production/browser/print/permission QA
- Security and MFA rollout validation
- Reusable major-event persistence and permissions
- Utility notice and public-safety reliability work