Packages of the Exponential ecosystem
Almost everything in the Exponential world is a package: the kernel, each extension, each theme, each server, each fork of an upstream library. "Every package is a GitHub repository under se7enxweb and a Composer package" (Releases and version numbers).
Contents
The pages of this part
| Page | What it answers |
|---|---|
| The bundled extensions | What arrives with a new installation and what is switched off |
| Composer and Packagist | How packages are installed and published |
| How packages are versioned | Version numbers, permanent tags, the ~ constraint |
| Site packages and the package server | Ready-made sites for the setup wizard |
| Themes and designs | Site themes and admin designs as packages |
| Finding an extension | Where to look and how to judge what you find |
| Compatibility and dependencies | Checking that a package fits your installation |
Three kinds of package
| Kind | Installed with | Example |
|---|---|---|
| Composer package (kernel, extension, theme, server) | composer require or a Git clone | se7enxweb/exponential, se7enxweb/eztags |
Site package (.ezpkg) | The setup wizard, the kickstarter or the console | The 7x Simple site package |
| Fork of an upstream package | Composer, replacing the upstream name | The Symfony, Twig and Doctrine forks of the platform line |
Related pages
- Ecosystem: start here
- The default extension distribution
- Extension development
- Site packages
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.