A public website your own staff edit and publish.

Document types with their own forms. A staff member fills one in and the entry appears.

• Pages, news, notices, events, places and service links each have their own form.
• Content is live the moment it is saved.
• Service links reorder by drag, pages reorder in the navigation tree, and bulk actions apply to a selection.
• Content keeps a revision history. Compare versions and restore an earlier one. Deleting content is recoverable.
• Publishing can be scheduled ahead, and items can be set to expire on their own.
• Images and documents upload into a shared library and are reused across content types. The upload enforces a size limit for each kind.
• Navigation derives from the page tree. Redirects are managed in the admin, and canonical URLs, structured data and the sitemap are generated.
• Site-wide search ranks across published pages, notices, events and documents.

See the screen

Who can edit, who can publish, and how they prove who they are.

• Staff accounts are created and managed in the admin, as editors or administrators.
• The workflow mode is a setting. Turn review on where it matters and leave it off where it does not.
• An editor submits and an administrator decides. A rejection goes back to draft with a reason, and the editor is notified either way.
• Two-factor authentication is available on staff accounts.
• The admin is behind an authentication wall and excluded from search indexes. Password reset runs through email.

The site renders your brand. Aptli's name appears nowhere on the public surface.

• Name, tagline, logo and crest in light and dark, tab icon and footer copyright are edited by staff.
• The contact block, office hours and the after-hours emergency line are staff-editable.
• Brand colours are validated on entry and refused below a 4.5 to 1 contrast ratio.
• Hero photos and page imagery are edited by staff.
• Fonts and the full theme token set stay deployment configuration, because a rebrand is a coordinated change across the deployment.

Getting an announcement to people away from the site, and seeing what they read.

• An RSS 2.0 feed carries published posts, notices and events, newest first. Each configured language has its own feed.
• Web push notifications reach anyone who subscribed from the browser.
• A contact form arrives in a staff inbox in the admin.
• A QR endpoint turns a page into a printable code for a sign or a notice board.
• Analytics are first-party and cookie-free, and figures export for a report.
• Zero-result searches are recorded, showing where content is missing.

Built into the shared templates every content type inherits.

• AODA under O. Reg. 191/11 sets the standard at WCAG 2 Level AA. The templates are built to WCAG 2 Level AA.
• Content types inherit keyboard navigation and screen-reader support from the shared shell.
• English and French are mirrored across the document types as separate indexable pages. Assistive technology reads each in its declared language.
• A draft can be machine-translated into the other language and then reviewed before it publishes.

Optional. Pair the site with an Aptli instance and the public services appear inside it.

• An administrator pastes the hub address and a one-time code. The two systems exchange a key and pair themselves.
• Service request forms, issue reporting and submissions are served by the platform and appear under the same domain.
• The live community map is embedded in a page and its data comes from the platform.
• An AI search widget answers on your own published content, and editors can draft a summary of a long page.
• The two run as separate deployments with separate databases. Unpaired, the site runs on its own.