Home

Introduction

Changelog * Credits * History

Imagine if you could have a CMS without the complicated administration area?

• How many times have you avoided jumping into all the different option a CMS provides because you were afraid you'd break something or were just too overwhelmed with the number of variables?

• Or how many times have you installed a plugin/extension and let it setup with the default values because that was sufficient for what you wanted?

One of the main objectives in this CMS is to leave the "have to"s out of your way and devote all your energy in the "want to"s. We think owning a webpage should be a straightforward process (by now) and no more of a hassle than writing any other document.

Objectives

• To produce a CMS with minimal footprint
• Complete separation of logic/data/design
• Free from fixed setup structures and server dependencies

Features

• Search Engine friendly URLs
• No Installation / Portable
• MVC structure
• Wiki-style CMS
• Automatic sitemap generator

Conventions

• It is safe to assume that 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)....
• There is the ability to have custom presentation for the body of each page. A page at "somedir/pagename" will look for a fragment called "somedir_pagename.php" in the fragments folder - if not available it will revert to the default one "main.php"
• 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.
• The layout for CMS actions (create, edit, login etc.) have their own sub-folder "cms" in the "fragments".
• There is a "helpers" folder that contains supporting scripts: A language file, a sections class and common funtions loader among other things.

Wishlist

• Enable markdown and/or wysiwyg editors for the content area.
• Directory of all available pages
• Support more than one administrator
• Externalise all text to a language file
• Better validation feedback (error messages) and/or JavaScript validation of user input.