Recent changes
Wednesday November 04 2026
-
Setting up the Approve event Updated Markdown page
Every field of the Approve event (affected sections, languages and versions, approving users and groups, excluded groups) with the choice a public body usually makes for each, and the trigger and cronjob that make it…
-
Style guide governance Updated Markdown page
How a public body keeps its editorial and design style guide effective on an Exponential site - what the system enforces (classes, fields, the rich text editor, templates, approvals) and what the style guide and its…
-
Two-person rule for publishing Updated Markdown page
How to make sure no single person can publish content on a public website alone - an approval workflow on every public section and version, approvers kept out of authoring, a small documented bypass group and audit…
-
Version history and accountability Updated Markdown page
What the version history of a page and the audit trail tell a public body about who changed what and when, how many versions are kept (45 by default), and how to keep earlier versions longer when records rules require…
-
Workflow troubleshooting Updated Markdown page
What to do when approved content is not published, an approval waits for an approver who left, "Send for publishing" seems to do nothing, or processes fail - with the Setup > Workflow processes page, the cronjob…
-
Hosting Exponential in the public sector Updated Markdown page
Index of the hosting pages for public bodies: where and how to run Exponential (own data center, government or sovereign cloud, containers), which database and web server, separate environments and administration, data…
-
Configuration under version control Updated Markdown page
For public-sector IT teams that must control and trace every change to a live site. How to keep Exponential's code and settings in version control, lock the administration against settings changes with…
-
Containers and orchestration Updated Markdown page
For platform teams in public bodies that run Exponential in Docker, Podman or Kubernetes. What the sources say about containers, what must be on a persistent volume, the one-writer rule for SQLite, and how a container…
-
Data location and what is stored where Updated Markdown page
For public bodies that must know and document where the data of an Exponential site is kept. Every place the software stores content, files, accounts, logs and keys, which of them hold personal data, and what leaves the…
-
Choosing a database in the official order Updated Markdown page
For public-sector architects and IT teams choosing the database of an Exponential site. The six supported databases in the project's official order, how they compare for availability, backups and procurement, and how to…
-
Environments for development, test and production Updated Markdown page
For public-sector IT teams that keep separate development, test (acceptance) and production copies of an Exponential site. How EXP_ENV gives each machine its own settings, how to keep test copies from sending mail or…
-
Government and sovereign cloud hosting Updated Markdown page
For public bodies that must or want to run Exponential in a government cloud, a sovereign cloud or a national provider's virtual machines. What the software needs from such a platform, which hosting models the sources…
-
Hardening the host Updated Markdown page
For public-sector IT and security teams preparing a server for an Exponential site. The hardening layers the software expects from the host, the checks that prove them, and how to map them to a security baseline or an…
-
A hosting decision record Updated Markdown page
For project managers and architects in public bodies who must document how an Exponential site is hosted. A decision record template with every choice the software asks for, the options and where each option is…
-
On-premise hosting in your own data center Updated Markdown page
For in-house IT teams that run Exponential on their own servers. What a site needs from your data center, which operating systems the project tests, how to split the work between teams, and where the detailed server…
-
Separating the administration from the public site Updated Markdown page
For IT teams that must keep the editing interface of a public-sector site off the public internet. How siteaccesses separate the administration from the public site, how to give it its own host name, restrict it to your…
-
Velocity for public-sector teams Updated Markdown page
For in-house IT teams that run Exponential Velocity, the recommended engine. How it is started, kept running after a crash, deployed to, watched and secured, with the points an internal security assessment usually asks…
-
Web server choices for public-sector sites Updated Markdown page
For IT teams that decide what serves an Exponential site in a public body. Velocity, FrankenPHP and Apache or nginx with PHP-FPM compared, the questions that decide between them, and how to fit the choice to your…
-
Incidents Updated Markdown page
Index of the incident runbooks for public-sector Exponential sites - the common frame, site down, database unreachable, defacement, account compromise, data breach framing, floods, broken deploys, mass content errors…
-
Broken deploy rollback Updated Markdown page
Runbook for a site that broke right after a deployment - confirm the change is the cause, roll back code and settings, decide whether the database must be restored, redeploy in the right order, and record it for the…