Comments on: The joy of separating style from content! http://www.0xcafefeed.com/2004/07/joy-of-separating-style-from-content/ Thoughts on Java™, Java EE™ and web application development Tue, 06 Jan 2009 11:03:02 +0000 http://wordpress.org/?v=2.6.3 By: Mike http://www.0xcafefeed.com/2004/07/joy-of-separating-style-from-content/#comment-41 Mike Mon, 19 Jun 2006 13:29:00 +0000 http://www.0xCAFEFEED.com/?p=9#comment-41 Very nice post. I've always thought that separating style from content and giving web-sites a "skinnable" property would be neat thing to have. Similar to what you did with the setActiveStyleSheet() function, I'm currently developing a project called 'Webskins' (<a HREF="http://sourceforge.net/projects/webskins" REL="nofollow" rel="nofollow">http://sourceforge.net/projects/webskins</a>) that will let users choose their own CSS for particular web pages (all with Javascript/CSS).<br/><br/>Pretty neat, GPL/free/etc. I'll be releasing the source in a day or two. Until then, you can check out a demo at <a HREF="http://webskins.blogspot.com/" REL="nofollow" rel="nofollow">http://webskins.blogspot.com/</a>.<br/><br/>--Mike Very nice post. I’ve always thought that separating style from content and giving web-sites a “skinnable” property would be neat thing to have. Similar to what you did with the setActiveStyleSheet() function, I’m currently developing a project called ‘Webskins’ (http://sourceforge.net/projects/webskins) that will let users choose their own CSS for particular web pages (all with Javascript/CSS).

Pretty neat, GPL/free/etc. I’ll be releasing the source in a day or two. Until then, you can check out a demo at http://webskins.blogspot.com/.

–Mike

]]> By: Sachin http://www.0xcafefeed.com/2004/07/joy-of-separating-style-from-content/#comment-15 Sachin Fri, 16 Jul 2004 06:17:00 +0000 http://www.0xCAFEFEED.com/?p=9#comment-15 Thanks for introducing me to CSS. I have been dabbling with it ever since you showed me what I could do with it and the results have made me like my HTML pages a whole lot more! Thanks for introducing me to CSS. I have been dabbling with it ever since you showed me what I could do with it and the results have made me like my HTML pages a whole lot more!

]]> By: Doug http://www.0xcafefeed.com/2004/07/joy-of-separating-style-from-content/#comment-14 Doug Mon, 12 Jul 2004 16:22:00 +0000 http://www.0xCAFEFEED.com/?p=9#comment-14 Ah, the enthusiasm of the newcomer. I was there once, myself. But there is a growing movement away from CSS-P (positioning, aka layout) because it takes an awful lot of effort and produces almost no value. You already *have* separation of content and presentation: the presentation is in your Blogger template. What HTML/CSS does is give you separation of "semantic markup" and presentation. That's nice, but not really of much value for a weblog. And CSS-P is a bugbear to get working right in more than one browser. CSS *styles* (colors, fonts, etc.) are definitely useful, although if you think "you no longer have to depend on complex search and replace regular expressions" you've never tried to *change* an existing design of any complexity. A simple change of font color or typeface requires locating every font rule and updating it. Still, it beats doing it in the HTML. Ah, the enthusiasm of the newcomer. I was there once, myself. But there is a growing movement away from CSS-P (positioning, aka layout) because it takes an awful lot of effort and produces almost no value.

You already *have* separation of content and presentation: the presentation is in your Blogger template.

What HTML/CSS does is give you separation of “semantic markup” and presentation. That’s nice, but not really of much value for a weblog. And CSS-P is a bugbear to get working right in more than one browser.

CSS *styles* (colors, fonts, etc.) are definitely useful, although if you think “you no longer have to depend on complex search and replace regular expressions” you’ve never tried to *change* an existing design of any complexity. A simple change of font color or typeface requires locating every font rule and updating it. Still, it beats doing it in the HTML.

]]>