Hi everyone,
I'm currently just starting to develop a new site combining two of my current ones. I'm throwing ideas around in my head about how to approach it, especially the site architecture.
The big idea that I've got right now is to make the entire site's functionality consist only of 'modules'. These modules would basically be classes inherited from a generic module class, and provide all the functionality of an 'area' of a site (eg: 'articles' section of the site, or 'files', or 'links', or whatever), as well as their own methods to allow the user to GET to that module's area in the site, which would be called by some code that does the 'design/html' aspect of things. The modules would also have their own configuration options which could be set either editing plain config.inc.php type files or even having a web-based config editor where using something like xml i could define the possible configurations and have a script generate a module-specific config page for administrators of the site...
I could also setup small modules that would be things like, for example, a "top 10 downloads" box to be displayed along a sidebar... I'm not completely sure how this would be managed, but it's an idea...
Any comments/suggestions/feedback? Does this sound feasable? I'm slightly concerned about performance issues, but I think it could be done where it wouldn't really be noticeable.
Thanks,
David Goodlad
- webmaster: http://blackhole.thenexus.bc.ca | http://vbgaming.thenexus.bc.ca
