Recent changes
Wednesday November 04 2026
-
Backing up everything you need to leave Updated Markdown page
What a complete backup of an Exponential site contains, so a public body can hold its own copy and leave a supplier at any time - database and files taken together, settings, generated keys, code, audit records - and…
-
Data export formats for leaving or changing supplier Updated Markdown page
Every way to get data out of an Exponential site and the format each one writes - the xrowextract site archive, CSV/XML/JSON per class, packages (.ezpkg), database dumps, storage files, layouts, form submissions…
-
Documentation handover at exit Updated Markdown page
What documentation a supplier must hand over so another party can run an Exponential site - system report, content model, roles, settings, integrations, custom code, operations runbooks and editorial guides - with the…
-
Exit plan template for an Exponential site Updated Markdown page
A copy-and-fill exit plan for a public website or intranet on Exponential - inventory, deliverables with formats, roles, timeline, verification, personal data rules, redirects and sign-off - to attach to the contract…
-
Handing over keys and secrets at exit Updated Markdown page
Which keys, passwords and secrets an Exponential site depends on, which of them cannot be recreated (audit signing keys, the mail preferences secret, certificate keys), how to transfer them privately, and which ones to…
-
Lock-in clauses to avoid, and clauses to ask for Updated Markdown page
Contract terms that tie a public body to one supplier of an Exponential site - ownership of custom code, closed extensions, held backups and keys, private forks, exit fees - and model wording that keeps the freedom the…
-
Personal data at exit Updated Markdown page
How to handle personal data when an Exponential site moves to a new supplier or system - finding where personal data lives, exporting only what the receiver needs, passwords, consent and audit records, secure transfer…
-
Transition to another provider, same software Updated Markdown page
How a public body moves its Exponential site to a new hosting provider or support partner without changing the software - roles of the old and new provider, the documented move procedure, settings that name the old…
-
Transition from Exponential to another system Updated Markdown page
How a public body moves its content from Exponential to a different content management system - the seven-step export, rich text, files, users, addresses and the guides per target system - and how to run the old and new…
-
Keeping public addresses working after an exit Updated Markdown page
Why the public addresses of a government site must keep working after a change of system, where Exponential keeps every address (main aliases in the site archive, other aliases and wildcards in two tables), how to build…
-
Why plan the exit before you sign Updated Markdown page
Why a public body should plan how it leaves a supplier or a CMS before it signs the contract - the risks of not doing so, what Exponential's open formats and license make possible, what still needs contract terms, and…
-
The product lifecycle Updated Markdown page
The lifecycle view of Exponential for a public body - release policy, supported versions, PHP and platform support, the roadmap, upgrade budgets, security patching, a yearly rhythm and the end of a contract.
-
The end of a contract Updated Markdown page
What a public body does when a contract for an Exponential site ends - renew, re-tender with the same software, or leave it - and the handover of code, data, keys, documentation and knowledge that each choice needs.
-
Keeping a site current over a multi-year contract Updated Markdown page
A yearly rhythm for a public body to keep an Exponential site current through a contract of several years - updates, platform, access, content checks, documentation and training - with the admin pages and commands that…
-
PHP and platform support over the contract term Updated Markdown page
Which PHP versions, databases, web servers and operating systems Exponential 6.0 supports, why the platform under the software has its own lifecycle, and how a public body plans PHP and operating system upgrades…
-
Planning upgrades in the budget Updated Markdown page
How a public body budgets for Exponential upgrades over a contract term - routine 6.0.x updates, upgrades from older lines, platform upgrades - with the steps each involves, the tools that reduce the effort, and a…
-
Reading the roadmap as a public body Updated Markdown page
Where the Exponential roadmap lives, why a public body should read it as a statement of intent rather than a commitment, how to check roadmap items against the changelog, and how to request or fund a feature the…
-
Release policy and version numbers Updated Markdown page
What a version number of Exponential promises to a public body - permanent tags, the next release as the only fix, the last position counting on, changelogs per version - and how to use that in a contract and an asset…
-
Security updates and patching cadence Updated Markdown page
How security fixes reach an Exponential site - private reporting, fixes on main, the next release - how a public body learns about them, and how to agree a patching time with a supplier or host without inventing the…
-
Supported versions Updated Markdown page
Which Exponential versions receive security fixes according to SECURITY.md, what "supported" means for a public body, what happens to older lines, and how to require a supported version in a contract.