The way I'm programming this, it wouldn't be too hard for the user to custom tailor it to his old needs via modifications made to modules and static pages created. This thing is fully themeable and with the use of smarty for the designer you can control how your output will look in the smallest ways.
A few updates: The core now properly handles errors thrown by the page loader.
I have implemented an authentication class which sets a variable in the template so that users can see if you are logged in.
Now as Sidoh said there are some issues with what should be a template, what should be a module, and whatever.
I'm thinking about having the "bare" essentials as part of the core such as Authentication and User registration. But another issue comes to mind like managing user information and how to extend that with the use of modules. Perhaps write a module to dynamically fetch rows and things to update as they are added. Dunno just scribbling some thoughts down.
I have also started implementing my modules subsystem into the core. So far it just reads the modules directory and locates all the files needed and if it is not found then it throws and error to the core (most likely will be a fatal one too).
Todo list:
Design some user interfaces for when a user logs in, maybe have modules marked as "List only when logged in" or something I'll think more into this
Fidn a way to isolate all the cores function from the modules since currently I am exposing the entire core. Perhaps create sort of a "Communication pipeline" as in Module grabs Core's anttention Module does the requested data and Module closes stream. This could be overcompliating things but whatever.
