Conventions

Here is a list of things KISSCMS "takes for granted" and assumes its users will comply with these assumptions:

• The CMS has priority over any other script/function that names variables. For this reason, KISSCMS does not use prefixes for the cms variables ($id, $title, $content)....
• Controllers have a priority over all other logic patterns. If there is a views sub-folder named "archive" that's expected to be used by a controller named "archive". Same thing goes for templates, assets etc.
• Some controllers may require a special template - to automate that requirement, if a template has the same file name as the controller (ex. archives.php), it will automatically become the selected tempalte for that controller.
• There is the ability to have custom presentation for the body of each page. A page at "somedir/pagename" will look for a view named "somedir_pagename.php" in the views folder - if not available it will revert to the "default.php" (not tested)
• The index page (and homepage of the site) will always have a path equals to "" (empty). This entry is already available in the database when you first use the cms and by default cannot be deleted. If this page is deleted then the website might cease to function.
• There is a "helpers" folder that contains supporting classes: The base Model-View-Controller, some of the main Sections and a Template engine, among other things.