Overview
CONTENIDOs filesystem structure seems a bit overwhelming for the novice developer but follows a quite straight forward scheme. This article describes this scheme and should help to find the files you're looking for.
The location of many folders can be configured to suite your needs. This can be achieved by editing several configuration files (TODO exlpain which). This article assumes that all folders have their default locations!
When installing CONTENIDO you have to define where to install it. On a usual *nix box running no other sites this is probably /var/www. Lets assume this folder as ROOT.
After a successfull installation you will find some folders in ROOT which I like to explain first:
| name | required | description |
|---|---|---|
ROOT/cms/ | yes | This folder is often called frontend or client folder. All files contained in this folder are related to a single client. |
ROOT/contenido/ | yes | The CONTENIDO backend is located in this folder. |
ROOT/data/ | yes | Configuration files and other stuff is located in the data folder. |
ROOT/docs/ | no | This folder contains some documentation files. It could be deleted when read. |
ROOT/setup/ | no | The setup folder should be deleted immediatly after a successfull installation. |
ROOT/test/ | no | Could be deleted when you're not interested in developing and testing the CONTENIDO core. |
Frontend
The frontend or client folder contains files which are related to exclusivly a single client. When creating additional clients you will have several of these frontend folders. The default client is named cms, but can be renamed to an arbitrary name, as long as it does not collide with existing folders in ROOT.
| name | description |
|---|---|
ROOT/cms/cache | Contains cached images, style sheets and JavaScript files. Images that are scaled using CONTENIDOs image functions (TODO include link to article describing image functions) are stored in this folder using a hash as name. Module specific style sheets and JavaScripts that are used for a template are merged to a single file each and stored using the templates name. |
ROOT/cms/cache/code | This folder contains the code cache (TODO add link describing the code cache functionality). When displaying an article in frontend, the PHP code of all its modules is merged into a single file, that is stored in this folder. TODO describe the naming conventions for these files. |
ROOT/cms/cache/templates_c | Smarty cache for templates that are used with the class cSmartyFrontend when using the Smarty plugin. Smarty usually precompiles its templates and stores them in this folder. |
ROOT/cms/css | When developing a layout, its style sheets are often outsourced (which is really a good idea!) and should be located in this folder. This folder can have arbitrary subfolders. You can e.g. put all files for a single layout in its own folder. This folder should also be used to store any CSS framework (e.g. Blueprint et.al.) you might use. |
ROOT/cms/data | This folder contains client specific files that change on a regular basis. It contains no files on its own but has a set of subfolders which are described below. |
ROOT/cms/data/config | The config folder contains client specific configuration files. These are structured by defined environments as subfolders. By default there is just the production environment, but this can e.g. be extended by development, testing or staging. |
ROOT/cms/data/layouts | Layouts that can be created using the CONTENIDO backend are stored in this folder. They have each an own folder with a single HTML file, both having the same name as the layout. |
ROOT/cms/data/logs | This folder is used for client specific log files. TODO explain how to enable client specific logs. |
ROOT/cms/data/modules | This is probably one of the most important folders in each client folder. It contains the installed modules which have a folder structure on their own. |
ROOT/cms/data/version | When editing style sheets, JavaScripts, layouts, modules or templates in CONTENIDOs backend, their previous content is versioned and stored in this folder. |
ROOT/cms/images | When developing a layout, its images should be located in this folder. This folder even can have arbitrary subfolders. You can e.g. put all files for a single layout in its own folder. |
ROOT/cms/includes | When developing modules that share functions or classes these could be located in this folder, although it might be a good idea to create another folder classes for these. |
ROOT/cms/js | When developing a layout, its JavaScripts are often outsourced (which is really a good idea!) and should be located in this folder. This folder can have arbitrary subfolders. You can e.g. put all files for a single layout in its own folder. This folder should also be used to store any JavaScript framework (e.g. jQuery, prototype et.al.) you might use. |
ROOT/cms/templates | This folder contains cTemplate and Smarty templates. This could be either templates for content types as CMS_FILELIST or CMS_TEASER or even templates that are used by more than one module. |
ROOT/cms/upload | All files that are uploaded using CONTENIDOs file manager or the content types CMS_IMGEDITOR or CMS_LINKEDITOR are stored in this folder. This folder can have arbitrary subfolders. |
ROOT/cms/xml | When your modules or plugins need or create XML files, e.g. XML sitemaps or RSS feeds, these should be located in this folder. |
Backend
| name | description |
|---|---|
ROOT/contenido/classes | Contains one file for each CONTENIDO class. |
ROOT/contenido/cronjobs | Cron or pseudocron jobs are located in this folder. |
ROOT/contenido/external | External tools liek CodeMirror or TinyMCE can be found here. TODO the folders backendedit and frontend have to be described. |
ROOT/contenido/images | Images that are used in the CONTENIDO backend are located in this folder. |
ROOT/contenido/includes | Contains files with functions used in the CONTENIDO backend that can alos be used in plugins and modules. |
ROOT/contenido/jar | Contains the Java package org.contenido that is used for the file upload drag and drop feature. |
ROOT/contenido/plugins | CONTENIDO plugins are located in this folder. |
ROOT/contenido/scripts | This folder contains JavaScripts that are used in the CONTENIDO backend. This also includes the jQuery library. |
ROOT/contenido/styles | This folder contains CSS style sheets that are used in the CONTENIDO backend. This also includes the style sheets for jQuery. |
ROOT/contenido/templates | Templates that are used to render pages in the CONTENIDO backend. |
ROOT/contenido/templates_c | Smarty cache for templates that are used with the class cSmartyBackend when using the Smarty plugin. Smarty usually precompiles its templates and stores them in this folder. |
ROOT/contenido/tools | Command line tools (CLI) that are used for certain CONTENIDO related tasks e.g. automatic creation of the autoloader configuration file or the detection of PHP dependencies. |
ROOT/contenido/xml | This folder contains some XML files required for the CONTENIDO backend. legend.xml contains descriptions of the icon legend shown in Content | Article. navigation.xml defines the structure of the main- and subnavigation. system.xml defines settings which will be displayed on the system configuration page in Administration | System. |
Data
| name | description |
|---|---|
ROOT/data/cache | This folder is used for caching of client independant files that are created by some plugins (e.g. PIFA or PIXI) and modules. Also the CONTENIDO UpdateNotifier uses this folder for its files. |
ROOT/data/config | Client independant configuration files are located in this folder. |
ROOT/data/cronlog | When cronjobs are setup, these usually store *.job-files containing a timestamp in this folder to signal that and when they have been run last. |
ROOT/data/locale | This folder contains gettext files used to localize the CONTENIDO backend. |
ROOT/data/logs | Depending upon configuration settings some log files are maintained that can be found in this folder. |
ROOT/data/temp | This folder is intended to be used for any temporary data. When using this folder it might be a good idea to create a subfolder for each task in order to avoid name collisions. |