A department editor starts from approved content types with required metadata.
CMS and Platform
A platform behind every page.
Attachment D asks for more than a website. It asks for a platform: editor workflow, search, accessibility, hosting, security, records, meetings, integrations, domains, support, and room to grow. Here is how Stoa keeps them working together.
Editor Workflow
Non-technical publishing, with guardrails.
A reviewer checks facts, accessibility, records retention, and translation needs.
Scheduled release, with an audit trail, rollback, and linked source records.
Search misses, broken links, and stale pages become editorial tasks.
Integration Map
Named systems get named ownership.
Content and notification channel
Records and document archive
Permit lookup and handoff
Service request lifecycle
Account and service data connection
Programs, rooms, and passes
Embedded code and ordinance lookup
Secure resident and staff continuity
Security and Hosting
Evidence, without overclaiming.
The prototype shows the control model the proposal has to substantiate: MFA, audit logs, secure SDLC, backups, breach-notice workflow, data ownership, export, and continuity.
- AlignmentSOC 2 evidence and FedRAMP/GovRAMP principles mapped, without claiming authorization.
- CapacityAt least twice the stated current scale: 25GB, 2,000 folders, 35,000 files, plus traffic logs.
- DomainsThe main Dover site plus named related domains, with SSL/certificate tracking and routing ownership.
- SupportWarranty, monitoring, incident response, training, and a content-governance cadence.
Domain Stewardship
A multi-domain city web estate.
The domain spellings above follow Attachment D, including the listed doverarean.com string. The intended domain inventory would be confirmed with the City during discovery.