CMS design
Posted: Tue Jun 27, 2006 9:15 pm
Many of todays CMS applications are complex monolithic beasts...requring weeks in training before doing anything useful...
This was the very incentive to write my own...within minutes *anyone* can start making content changes...
My CMS is faaaaaaar from perfect...but uses a fairly different approach to solving CMS problems...following a KISS principle...and cutting back on advanced features...
Pagination of articles and sub articles, etc...
Although this could be added...
What I like about my CMS...the reason I started it...was actually a long time ago...I was trying to build a sorta RAD tool for PHP developers...
Tired of having to create a new page for a web site, with some pages requiring complex contact forms and others, requiring a dynamic list pulled from some web site other than my own...
My CMS solved this problem by basically using a *model* PHP script to generate new web pages - which are actually PHP scripts so once created you could go in and add the custom code required to build an interesting web site/application...
Albeit it's more handy for web sites where content in of concern...
Anyways...
Because the core of the system relies solely on the file system and no DB...it's difficult to add plugins like, search...but trivial to include third party solutions like phpDig as it knows how to search files on a web site...not DB articles...
Does anyone see this as a short fall? How about advantage?
Over the years (i've re-built it numerous times but it's still v1.0) I have considered both the positives of DB and the negatives...
I must say DB usually wins, but I still like my idea (there is no reason I could start using a DB to store content - it's a trivial hack)...the simplicity behind it all appeals to maybe
I would like the ability to add news sections, etc...using nothing but the CMS itself...but because of the design...simplicity...that would make things much more complicated from a end user perspective...beating the purpose...
Yet fairly advanced web sites could be quickly throw togather using this as a tool...
I'd like to hear opinions, comments, etc...
This was the very incentive to write my own...within minutes *anyone* can start making content changes...
My CMS is faaaaaaar from perfect...but uses a fairly different approach to solving CMS problems...following a KISS principle...and cutting back on advanced features...
Pagination of articles and sub articles, etc...
Although this could be added...
What I like about my CMS...the reason I started it...was actually a long time ago...I was trying to build a sorta RAD tool for PHP developers...
Tired of having to create a new page for a web site, with some pages requiring complex contact forms and others, requiring a dynamic list pulled from some web site other than my own...
My CMS solved this problem by basically using a *model* PHP script to generate new web pages - which are actually PHP scripts so once created you could go in and add the custom code required to build an interesting web site/application...
Albeit it's more handy for web sites where content in of concern...
Anyways...
Because the core of the system relies solely on the file system and no DB...it's difficult to add plugins like, search...but trivial to include third party solutions like phpDig as it knows how to search files on a web site...not DB articles...
Does anyone see this as a short fall? How about advantage?
Over the years (i've re-built it numerous times but it's still v1.0) I have considered both the positives of DB and the negatives...
I must say DB usually wins, but I still like my idea (there is no reason I could start using a DB to store content - it's a trivial hack)...the simplicity behind it all appeals to maybe
I would like the ability to add news sections, etc...using nothing but the CMS itself...but because of the design...simplicity...that would make things much more complicated from a end user perspective...beating the purpose...
Yet fairly advanced web sites could be quickly throw togather using this as a tool...
I'd like to hear opinions, comments, etc...