Content Source Files

Source files are at least as important as templates. These files describe the page specific information that will be compiled together with a template to produce the actual target web page that will be seen. When you have a template, and a source then it is time for you to describe how these relate to one another and to what target they should be compiled. All of your source files should be located somewhere in the file hierarchy located in the subdirectory defined by the project configuration variable:

$GLOBALS['interJinn']['compileSourcePath']

The source file retrieval system supports a multilingual hierarchy. If you have declared your project as multilingual via the multilingual configuration variable, then the retrieval system will attempt to resolve the correct language source file. The process that occurs is to first check for the source file in a subdirectory by the name of the current language, if that fails then it will fall back on the original path. To clarify the point - if the current language were fr and you had the following source file path:

/navigation/admin/secondary.source

Then the retrieval system will first attempt to load the source file from the following path:

/navigation/admin/fr/secondary.source

If the source file was not found then the system would fall back on the original path for retrieval. By using this mechanism an entire multilingual site can be defined if the content and source files are located in the appropriate language directories, then the site will compile all language versions without the need for any special logic other than what is contained within the templating system.