Recent changes
Wednesday November 04 2026
-
Roles and policies of sevenx_multisite Updated Markdown page
The roles, policies, sections, user groups and role assignments a sevenx_multisite install creates, and the administrator preferences it sets, as written in the installer.
-
sevenx_classes, the content classes package Updated Markdown page
Every content class of the sevenx_classes package with its name, group and datatypes, how the package is installed, and how the installer changes some classes afterwards.
-
Siteaccesses and languages of sevenx_multisite Updated Markdown page
Every siteaccess a sevenx_multisite install creates, the settings the installer writes for each, how the sites are matched, and how the languages chosen in the setup become siteaccesses.
-
The clean variant and sevenx_site Updated Markdown page
How sevenx_multisite_clean differs from sevenx_multisite, and what the simpler sevenx_site and sevenx_site_clean site packages install instead, so you can choose the right one.
-
The demo content packages Updated Markdown page
What sevenx_multisite_democontent and sevenx_multisite_democontent_clean contain - the 31 ng_* content classes, the content objects of Fit & Healthy and Bold Agency, the binary files - and how the two differ.
-
The multisite installer script Updated Markdown page
What sevenx-multi-site-installer.php does during an install, in order - its settings, the pre-install, the settings and roles the setup asks it for, and the 50 post-install steps.
-
What sevenx_multisite is made of Updated Markdown page
The files inside the sevenx_multisite site package and the packages it requires, what each settings file does, and which parts of the installation come from outside the packages.
-
Making your own site package Updated Markdown page
The path from an existing site package to your own one - fork, change the installer and the content, rebuild the archives, version them, publish them on a package server, point an installation at it, test - and where…
-
Changing classes and content Updated Markdown page
Where a site package's content classes and demo content live, how their XML files are listed as install items, the two ways to change them (edit the files, or build on a test site and export), why remote IDs must stay…
-
Changing the installer script Updated Markdown page
How a site package's PHP installer is wired into CreateSites - the settings files, the eZSite* hook functions and when they run, the installer class and its post-install steps, the extensions and tables it sets up - and…
-
Creating packages with ezpm Updated Markdown page
Build the packages your site package requires from a shell with ezpm.php - create, add classes, content or an extension, set the vendor and other fields, export, validate and check - in a form you can script and run…
-
Creating packages with the wizard Updated Markdown page
What the package wizard in the administration can make for your site package (content classes, content, extensions, site styles), what it cannot make (the site package itself), and how to move its output into your…
-
Forking a site package Updated Markdown page
Start your own site package from a working one - which package to copy, how the source repositories are laid out, what to rename in package.xml and the installer files, and which names must be unique so an installation…
-
Pointing a site at your package server Updated Markdown page
Make the setup wizard, the kickstarter and exp:install read your package server instead of the 7x one (a package.ini override), choose your site package in kickstart.ini or on the command line, add the server to…
-
Rebuilding with build.sh Updated Markdown page
How the 7x package archives are built from the source repository - packages/build.sh and bin/pack.sh line by line, what they leave out, where the .ezpkg files land - and how to check an archive before it is published.
-
Running your own package server Updated Markdown page
A package server is a static HTTPS folder with index.xml, the .ezpkg archives and their thumbnails. This page gives the folder layout, a complete index.xml, how to host it on GitHub Pages as 7x does or on any web…
-
Testing in a sandbox Updated Markdown page
Test a site package where nothing can be lost - a separate checkout with its own SQLite database - in four rounds - check the archives, a dry run, a full install, a look at the result - and clean up afterwards.
-
Versioning your own packages Updated Markdown page
Where a package's version lives (version number and release number in package.xml, the version attribute in index.xml, the release folder on the server), how Exponential compares versions, how min-version decides…
-
API design: REST, ezjscore and headless Updated Markdown page
The interfaces Exponential offers to other systems and front ends - the REST content API of ezprestapi at v1 and v2, OAuth 2.0 and personal API keys, the ezjscore call interface and expservices, outgoing audit webhooks…
-
Application servers Updated Markdown page
The three ways Exponential is served - a web server with PHP-FPM, Exponential Velocity with persistent workers and a response cache, and FrankenPHP in classic mode - compared by process model, state between requests…