- Alerts in many languages and plain language How a public health body publishes an alert fast in Exponential, translates it into the languages people speak, keeps it plain, updates it during the event, and ends it - with the Alert class, translations, caches and…
- Anatomy of an extension Every directory and file an extension can have - modules, classes, autoloads, design, settings, datatypes, event types, cronjobs, bin, share, sql, translations, doc - plus extension.xml, ezinfo.php and composer.json…
- Annual value review One meeting a year in which the owner of an Exponential site decides what the site is worth and what to do next - who attends, what to prepare, a two-hour agenda, the decisions to record, and how it fits with the…
- A read-only content report A worked example of a safe agentic workflow - an agent with a read-only API key walks a folder through the REST API, reads the fields of each page, and writes a report for editors (missing summaries, outdated dates…
- Attribution and copyright notices Where credit goes in an extension - file headers, license files, ezinfo.php Includes, composer.json authors, README credits, Git history - and how to add your name without removing anyone else's.
- Audit alerts The seven alert rules shipped with Exponential's audit trail (brute force, an administrator role granted, settings written out of hours, mass deletes, the audit switched off, a broken chain), who receives them, how to…
- Automating provisioning A provisioning pipeline for new Exponential customer sites, step by step: system user and isolation, database, code from Git or Composer, exp:install with secrets from the environment, serving the site, cron, password…
- Backups from the administration with git_manager For site administrators in public bodies who have no shell on the server. How the git_manager extension's Setup > Backup page creates database and file backups, encrypts them, and makes sanitized dumps; its limits…
- Backups that restore What a business must back up on an Exponential site, how often, where to keep it, and the decisions a manager has to make, with links to the exact commands for each database.
- Budget: what a local business website costs The budget pages for a small business website on Exponential - the cost picture without invented prices, a worked example where every number is labeled an example assumption, a worksheet for your own numbers, and the…
- Cancellations and changes How to handle changed and cancelled events on an Exponential site - editing time or place, a visible status, keeping the address, telling people who follow or signed up, the history in versions, and hiding cancelled…
- Changelogs Write a changelog users can act on - grouped by Added, Updated, Fixed, Removed and Renamed, assembled from the commit messages since the last tag, upgrade notes first - and keep an old extension's changelog.
- Choosing a version number How to pick the next version number of a theme - from what is already published, raising only the last position for normal releases, and moving a higher position only as a deliberate decision about what the release…
- Clear caches after a settings change Step by step - make a changed INI setting take effect - clear the INI cache with the right tag, reload PHP-FPM or redeploy Velocity, then clear the page caches, and check the effective value with exp:ini.
- Cost of downtime worksheet A worksheet to work out what one hour offline costs your organization - lost sales, idle staff, recovery work, contract penalties and wasted marketing - with a worked example built from example assumptions, a blank form…
- Council meetings and local services How a municipality publishes its meeting cycle in Exponential - calendar, agenda and papers, the meeting itself, minutes after approval, decisions - and how it keeps service pages correct with owners, review dates and a…
- Dark mode and design tokens in themes Give a theme one set of design tokens with light and dark values, follow the visitor's system setting, add an optional toggle without inline scripts, and check contrast, as the admin4 design does.
- Database backups per engine The backup, check and restore commands for each database Exponential supports, in the official order (SQLite 3, PostgreSQL, MongoDB, MariaDB, Oracle, MySQL), with the traps of each engine and a portable schema dump for…
- Data breach notification framing How the technical team supports a public body's decision on notifying a personal data breach - establishing what data, whose, and when, with the audit trail, logs and exports Exponential provides - without giving legal…
- Deactivation and removal The three ways to end an account in Exponential - disable, deactivate and move, remove for good - what each keeps and deletes, mail preference erasure and audit pseudonymization on removal, and how to answer a request…
Documentation license
This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.
Exponential Copyright © 1998-2026 Exponential Foundation and 7x