Hi Justin You might want to try the following sites:
http://www.opensourcecms.com/ This site has open source CMS's that are php/mysql based. They have actually set up and installed CMS's on their server and allow you to go and use their system. Since you will be making a choice of what CMS your organisation will use, you might want to see http://www.cmsreview.com/index.html to help choose which CMS might be right for you... And if you really have some spare time on your hands, check out Column Two archives found at http://www.steptwo.com.au/columntwo/archives/cat_content_management.html which should keep you busy for some hours :) Ralph -----Original Message----- From: Justin French [mailto:[EMAIL PROTECTED] Sent: Wednesday, 28 January 2004 5:10 PM To: [EMAIL PROTECTED] Subject: [WSG] New CMS / Framework Hi all, Inspired by the needs, comments and wishes of Dave Shae's "Wanted: CMS" post on Mezzoblue <http://www.mezzoblue.com/archives/2004/01/09/wanted_cms/>, I'm taking up the challenge, and building the CMS I've always wanted (which it looks like Dave and others wanted too). Off the top of my head, with no warranty whatsoever, I'd like it to be distributed under a license similar to MT's multi-license for personal/commercial/pro use, or even GPL. More (and less) than a CMS, what I'm aiming at is a framework which provides a simple CMS, but more importantly offers a killer API for plug-ins and extensions. I'm 100% convinced that the perfect CMS doesn't exist, but I hope that I can build one that meets basic needs, with unlimited scope for extensions. I'm NOT building another blog tool (although there will be a blog plug-in), and I'm not building a bloated portal system that can do everything and anything (although the plug-in API would allow for it all)... what I'm building is a system that answers *my* common requirements, and hopefully those of a large number of developers out there in the process. My assumption (and my need) is a system where the developer (me for example) sets up the site, creates the content models and templates, creates the CSS, hooks in new plug-ins (or even builds a new one), then hands it over to content writers and editors to run on a day-by-day basis. As such, my target market isn't really website owners, but website developers acting on behalf of website owners. Naturally the content-adding back-end will need to be usable by regular office staff, but the areas that the developers deal with (creating new content models and templates) will be quite raw (no need to write a template engine when PHP already is one, etc). It's quite possible I've got this all wrong, and this isn't what other people want at all, but that's OK, because I still want it for me and my clients. Even so, I'm keen to get the ball rolling on a wish-list of features (keeping in mind that this is supposed to be lightweight, allowing as much freedom as possible to develop add-ons) from everyone out there. To start the ball rolling, here are a *few* of mine: - LAMP based (possibly with a DB abstraction layer) - page (rather than post) oriented, with regular dir & file hierarchy, simple SE friendly URLs, etc - extensibility through a simple but open plug-in API - works on a basic install of PHP (no recompiles and external libs) - different content models (a news post is different to a recipe, blog post, tech article, etc etc) Feel free to keep emails private or public, and if you want to be involved in Beta testing etc (and get a freebie in the process), just let me know. Thanks, Justin French ***************************************************** The discussion list for http://webstandardsgroup.org/ ***************************************************** ***************************************************** The discussion list for http://webstandardsgroup.org/ *****************************************************
