Comments on: Design for CMS http://gregwolejko.com/design-for-cms/ Web2.0 evangelist on his way to greatness Wed, 07 Jan 2009 04:33:39 +0000 http://wordpress.org/?v=2.6.1 By: SBala :: CMS-Based Design http://gregwolejko.com/design-for-cms/#comment-781 SBala :: CMS-Based Design Mon, 17 Nov 2008 23:59:32 +0000 http://gregwolejko.com/?p=62#comment-781 [...] found this article recently which covers a rather interesting topic. CMS design is much different from normal XHTML [...] [...] found this article recently which covers a rather interesting topic. CMS design is much different from normal XHTML [...]

]]> By: CMS-Based Design | SBala http://gregwolejko.com/design-for-cms/#comment-538 CMS-Based Design | SBala Fri, 11 Jul 2008 17:07:06 +0000 http://gregwolejko.com/?p=62#comment-538 [...] found this article recently which covers a rather interesting topic. CMS design is much different from normal XHTML [...] [...] found this article recently which covers a rather interesting topic. CMS design is much different from normal XHTML [...]

]]> By: Shantanu http://gregwolejko.com/design-for-cms/#comment-537 Shantanu Fri, 11 Jul 2008 16:59:20 +0000 http://gregwolejko.com/?p=62#comment-537 That is very interesting. I actually do some work with CMS-based design and the ways a CMS generates markup varies from page to page, and keeping a consistent style is often very hard because sometimes the ID's and classes of the elements change very dynamically from page to page. When 3rd party extensions and components are added to the mix, it is a very complicated issue that most people do not really take into serious consideration. I personally think that the reason IE6 still has market share is because designers are too afraid to not support it. If the web works in IE6, its users see no reason to upgrade even with the numerous security flaws. Some CMS's have easier templating systems than others, and I tend to like CMS's that allow me to replace my "lorem ipsum" paragraphs with a single line of code, be it PHP or a templating engine, instead of having to rework the entire template with various different pieces of code. I find TinyMCE to be one of the best WYSIWYG editors I can find because it is easily themable and works well with Copy/Paste. When reusing design, I also think people should reuse as much of the images, JavaScript, and CSS so that a browser may cache at least the images and JS. This will provide a more responsive page as well. That is very interesting. I actually do some work with CMS-based design and the ways a CMS generates markup varies from page to page, and keeping a consistent style is often very hard because sometimes the ID’s and classes of the elements change very dynamically from page to page. When 3rd party extensions and components are added to the mix, it is a very complicated issue that most people do not really take into serious consideration.

I personally think that the reason IE6 still has market share is because designers are too afraid to not support it. If the web works in IE6, its users see no reason to upgrade even with the numerous security flaws.

Some CMS’s have easier templating systems than others, and I tend to like CMS’s that allow me to replace my “lorem ipsum” paragraphs with a single line of code, be it PHP or a templating engine, instead of having to rework the entire template with various different pieces of code.

I find TinyMCE to be one of the best WYSIWYG editors I can find because it is easily themable and works well with Copy/Paste.

When reusing design, I also think people should reuse as much of the images, JavaScript, and CSS so that a browser may cache at least the images and JS. This will provide a more responsive page as well.

]]>