I've built a number of apps on various CMS systems, and the biggest thing that sticks out in my mind is the affect of content-writing WYSIWYG editors on the rest of the framework. You can spend months building the perfect interface to display and navigate around your content, but if the WYSIWYG editor overwrites your stylesheet, people can really screw things up with embedded tables, bizarre font selections & sizes. I agree with Ari...CMS's come in many flavors, and it's easy to slip into a "well let's not customize it too much" mode, esp if they paid a lot for the CMS. On the other hand, at some point you may determine you've picked the wrong CMS for the job and it costs more to customize it than to build it from scratch.
I'd say BEA Aqualogic's was pretty nice, and I recall they were a good source of info on CMS-as-enterprise-portal. I'm working on a site built with a proprietary PHP CMS now, and miss the predictability afforded by Aqualogic's documentation. *sigh*. Best of luck on you project =] Bryan http://www.bryanminihan.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cindy Blue Sent: Thursday, December 06, 2007 10:47 AM To: [EMAIL PROTECTED] Subject: [IxDA Discuss] Designing for CMS I'd love to hear about your experiences! ________________________________________________________________ *Come to IxDA Interaction08 | Savannah* February 8-10, 2008 in Savannah, GA, USA Register today: http://interaction08.ixda.org/ ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
