Header.php

Used to format POST/GET parameters

(move include_only to individual action files?)

Config file

remove directory “config”

Configuration variable set in “config.php”, including loading of config data from database

Hosting for multiple URL requires tweaking of “config.php”

Modulation?

Thanks to Saq for the brilliant suggestion of making cctiddly modular, it gets me thinking what and how does modulation programming (is this the right term?) achieved. The first thing I come up with so far is index.php manage all the action required thus index.php is usually visit (when action required) as index.php?action=save for saving. This would trigger the save module which is registered in the database by default. Users can then add customised modules through an admin interface making customising cctiddly a very simple process.

Ideal install process

My idea install process is as follow:

1. edit the config file
2. visit index.php
3. the installation process will be invisible and the user will be able to start using

note that only the bold steps require user interaction

As for installing workspace, either use the backstage panel or visit a desired workspace. there should be a setting in the config file to allow for workspace creation or not, and can limit to only certain users to be able to creat them