Root

The Exponential root directory is divided into multiple subdirectories, each which their own role.

bin

Contains various executables and shell scripts for different operation systems.

design

Contains all design related files, such as templates, images, style sheets and template preparation scripts. These are categorized in site designs and can contain override files. The default site design is standard. It is also the default fallback design.

doc

Contains all documentation ranging from requirement documents to design documents and change logs. This is the place too look if you want information on how Exponential was designed and what has changed. The dynamic documentation can be found in the sdk directory.

kernel

Contains all classes, views, data types and related kernel files. This is the core of the system. You should not normally need to change anything here.

lib

Contains the general Exponential libraries. These libraries are collections of classes which perform various tasks. The libraries are highly reusable and are in no way dependent on the kernel. People looking for general PHP libraries should take a look here.

sdk

Contains dynamic PHP scripts for rendering the various documentation bits, such as change logs, API reference and kernel examples. The code found here is somewhat dependent on the kernel.

settings

Contains configuration files for Exponential, these files are meant to be changed by sites, and are unique for one site and should not be shared. It also has site access configuration. The size of this directory is generally small and never grows, see var for cache files.

share

Contains static configuration files such as code pages, locale information and translation files. Dynamic configuration can be found in settings. This directory can easily be shared among Exponential installations.

var

Contains various cache files, logs and stored images and files. This directory will grow in size as the site is used more and more, it is therefore a good idea to put this on a large partition, and monitor it's growth. Use the logs to solve configuration problems or other issues.