IIRC, someone was working on a WYSIWYG CMS not too long ago.
Extensive use of AJAX etc. sounded just like what 'the people' want.. FrontPage in a web-browser.
My Rant For Content Management System
Moderator: General Moderators
- jimthunderbird
- Forum Contributor
- Posts: 147
- Joined: Tue Jul 04, 2006 3:59 am
- Location: San Francisco, CA
AJAX today, Java in the past
Well said, extensive use of AJAX, that reminds me years ago when java is the big word, they try to do everything in java, Corel even try to build an office-like application out of pure java, but as I remember it turns out to be a failure somehow...
I think a website should be considered as a publication and we should rethink the position of php,javascript,html,css in the process of creating this publication...
Also, seperating presentation with logic doesn't mean that we need to have yet another template engine. We can
1. let a designer do the template prototype first (more from a visual point, I found designers really like photoshop)
2. a html/css coder put this prototype into html template and even better design a good style sheet for that
3. a php (or perl, ruby... what ever) coder figure out how to generate server side code to generate pages based on the templates in step 2
Clear-defined roles sometime is more important...
Also, I found many of the CMS(System/Framework, more to me as website pulishing system) out there are pull-based, data pulled from database, with website as a publication in mind, such system should be push-based, generate pages from database... doing that we can even avoid using the ugly mod_rewrite/pathinfo tricks to generate search-engine friendly urls...
There's an article talking bout this: http://www.sitepoint.com/article/push-pull-best-cms which i think is very good...
--Jim
I think a website should be considered as a publication and we should rethink the position of php,javascript,html,css in the process of creating this publication...
Also, seperating presentation with logic doesn't mean that we need to have yet another template engine. We can
1. let a designer do the template prototype first (more from a visual point, I found designers really like photoshop)
2. a html/css coder put this prototype into html template and even better design a good style sheet for that
3. a php (or perl, ruby... what ever) coder figure out how to generate server side code to generate pages based on the templates in step 2
Clear-defined roles sometime is more important...
Also, I found many of the CMS(System/Framework, more to me as website pulishing system) out there are pull-based, data pulled from database, with website as a publication in mind, such system should be push-based, generate pages from database... doing that we can even avoid using the ugly mod_rewrite/pathinfo tricks to generate search-engine friendly urls...
There's an article talking bout this: http://www.sitepoint.com/article/push-pull-best-cms which i think is very good...
--Jim
Re: My Rant For Content Management System
That contradicts your post saying a cms = stock management etc and merely makes my point even more relevant. A CMS systems does ONLY Content Management. Training is required to set up the workflows and user management and other rules but for the actual content creators it could be as easy as pie. Some metadata to make the content accessible to the right people and in the right places and the content. Anyway, my previous posts illustrates all this and a lot more and I hope it helps in some way.onion2k wrote:If your content editting system requires training then it's too complicated.freefall wrote:What we're doing is creating sub-proprietry systems that need their own specially trained drones.
Re: My Rant For Content Management System
Yea I agree to a point, but that is a little too generalized. You have to remember some people need training to use Word... in that case, hope is lost for your CMS to be completely intuitive.onion2k wrote:If your content editting system requires training then it's too complicated.
To quote hawley jr's signature's quote (what a mouthful!)...
"The only 'intuitive' interface is the nipple. After that, it's all learned." -Bruce Ediger