Skip to content
tracend edited this page Jul 29, 2011 · 30 revisions

KISSCMS

Changelog * Credits * History

Objectives

  • To produce a CMS with minimal fingerprint
  • Complete seperation of app/data/templates
  • Free from set setup structures and server dependencies

Features

  • Search Engine friendly URLs
  • No Installation (works out of the box / Portable)
  • MVC structure
  • Wiki-style CMS
  • Automatic sitemap generator

Convensions

  • 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 an "inc" folder that contains supporting scripts: A language file, a modules container and common funtions loader.

Wishlist

  • Automaticaly insert markup code (ex.

    tags for paragraphs). Ideally implement a wiki style syntax for inserting markup.

  • Directory of all available pages
  • Use a more universal ORM instead of CRUDE.
  • Support more than one administrators
  • Externalise all text to a language file
  • Better validation feedback (error messages) and/or JavaScript validation of user input.
Clone this wiki locally