- Version history as accountability How Exponential's version history shows what a published page said at an earlier time and who saved each version, how to compare two versions, who may see them, and where the history stops being a complete record.
- Versioning and updating datasets How to update, correct, supersede and withdraw datasets in Exponential without breaking addresses or losing the record: versions and their limit, periods as separate distributions, change notices, and withdrawal instead…
- Advocate checklists All advocate checklists in one place to copy - before posting, before a talk or demo, before publishing a tutorial or case study, when answering, when someone reports a vulnerability, for events, and a monthly routine.
- One-page fact sheet A one-page, sourced fact sheet about Exponential that advocates can print or share - what it is, who stands behind it, releases, license, where it runs, headline features, security, community and how to try it - with…
- Glossary for advocates Plain-language definitions of the terms advocates meet and use - product names, organizations, technical terms like siteaccess, extension, override and draft, community and license terms - with links to the full…
- Advocate reading path Every advocate page in a sensible reading order, in seven stages from orientation to leadership, with a rough reading time per stage, so a new advocate can work through the whole section step by step.
- Advocate FAQ Quick answers to the questions advocates themselves ask - do I need permission, is there a program, can I use the logo, may I be paid, what if I am wrong, how much time does it take, where do I propose ideas - with…
- A CSP audit for every release Check before each release that the theme still works under a strict Content Security Policy - report-only mode on a test siteaccess, the browser console, a grep for inline code, and external resources.
- Admin access reviews A periodic review of who holds which rights on a public website - administrators, role changers, account administrators, auditors and departments - using the role list badges, role pages, Check user accounts, the CSV…
- Admin designs overview The administration designs (admin, admin2, admin3, admin4, admin4l, editor, adminui), how they stack, what admin4 adds (tokens, components, dark mode) and the rules every template change in an admin design must follow.
- Backup readiness A checklist that proves an Exponential site of a public body can be restored - database and files taken together, keys that cannot be recreated, storage and retention, restore tests, recovery objectives and who does…
- By hand: a datatype Add the rating datatype by hand: the four files and two settings in build order, a check after each step, and a test plan in the class editor.
- Cancel or postpone an event For editors - cancel or postpone a published event without breaking its page, make the change visible in the calendar and lists, tell people who follow or signed up, and hide it afterwards.
- Card payments and PCI basics Basics, not compliance advice - how card payments reach an Exponential store, the difference between redirect gateways and an on-site card form, what the ezauthorize extension does with card data according to its code…
- Certification ideas (proposals) Proposals, not programs - ideas for how Exponential certifications could be built, examined and kept current, written for the Foundation and 7x to consider and for partners to comment on.
- Class naming and the exp prefix How to name PHP classes, files, functions, settings and tables in Exponential - your own prefix, exp for code contributed to the project, sevenx for 7x, why kernel eZ identifiers are never renamed, file names…
- CLI scripts and ezexec for integrations Running integration code on the Exponential server from the command line - quick scripts with bin/php/ezexec.php, proper commands with eZScript in your extension, how the console finds them, siteaccess and user, exit…
- Composer and Git on servers How Exponential's code arrives on a server with Composer and Git, why extensions are Composer packages, which install way fits which plan, what a host must provide for Composer, and what never to run casually on a live…
- Composer packages and source on GitHub How Exponential's code reaches a public body (GitHub repositories and Composer packages on Packagist), why published versions never change, how to keep your own copy of every source you depend on, and how to check what…
- CSP: javascript: links, eval and string timers The remaining kinds of inline code a Content Security Policy blocks - javascript: links, eval(), new Function(), string timers, scripts inserted as HTML and JSONP - and how to replace each in an old extension.
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