<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Technology of Content &#187; oocss</title>
	<atom:link href="http://blog.technologyofcontent.com/tag/oocss/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.technologyofcontent.com</link>
	<description>Ramblings on the technology of content management</description>
	<lastBuildDate>Sun, 25 Apr 2010 21:45:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>OOCSS and Mashable Design</title>
		<link>http://blog.technologyofcontent.com/2009/03/oocss/</link>
		<comments>http://blog.technologyofcontent.com/2009/03/oocss/#comments</comments>
		<pubDate>Sat, 07 Mar 2009 14:20:01 +0000</pubDate>
		<dc:creator>justin</dc:creator>
				<category><![CDATA[design]]></category>
		<category><![CDATA[css]]></category>
		<category><![CDATA[oocss]]></category>

		<guid isPermaLink="false">http://blog.technologyofcontent.com/?p=1</guid>
		<description><![CDATA[Overview of OOCSS, and the Squiz mashable design process. This later turned into a slightly longer talk at the London web standards meetup.]]></description>
			<content:encoded><![CDATA[<p>I posted recently <a href="http://www.squiz.co.uk/resources/open-source-cms-blog/yahoo!-and-mashable-design">over at the Squiz site</a> about how the ideas in what we named <a href="http://www.squiz.co.uk/services/web_site_design/mashable_design">Mashable Design</a> were starting to spread around.</p>

<p>Out of Yahoo we have <a href="http://www.stubbornella.org/content/2009/02/12/css-doesn’t-suck-you’re-just-doing-it-wrong/">a strong opinion</a>, although Nicole seems to have got there from a different starting point from us (strictly CSS maintainability) the <a href="http://www.slideshare.net/stubbornella/object-oriented-css">conclusions are almost identical</a>. (She also has a potentially useful <a href="http://www.stubbornella.org/content/2009/02/28/object-oriented-css-grids-on-github/">toolkit on github</a></p>

<p>This is an area that I will be coming back to quite a bit over the next few months. The key points from the design point of view are modularity and reusability (and grids, the technology that helps these parts be reusable while still making a coherent whole). From the technical point of view a templating structure that encourages recursive modular thinking is needed (in MySource Matrix, the Squiz CMS these are encapsulated through paint layouts).</p>

<p>Page based design is weak for more complex content management problems. It works quite well for some things &#8211; a Wordpress blog like this for example, but not an enterprise content management system, where content reuse is a key requirement.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.technologyofcontent.com/2009/03/oocss/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
