<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Building Block Definitions (Containers)</title>
	<atom:link href="http://boxesandarrows.com/building-block-definitions-containers/feed/" rel="self" type="application/rss+xml" />
	<link>http://boxesandarrows.com/building-block-definitions-containers/</link>
	<description>Boxes and Arrows is devoted to the practice, innovation, and discussion of design; including graphic design, interaction design, information architecture and the design of business.</description>
	<lastBuildDate>Mon, 20 May 2013 13:09:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: florisontwerpt</title>
		<link>http://boxesandarrows.com/building-block-definitions-containers/#comment-6819</link>
		<dc:creator>florisontwerpt</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/building-block-definitions-containers/#comment-6819</guid>
		<description><![CDATA[Thanks for a great addition to the series Joe. 

I&#039;m trying to convert your theoretical approach to a -for me- more tangible example. Would it be fair to translate your top level stacking orders like this (for most situations):
- Portal Suite = Website (as in top navigation like &quot;consumer, business
- Portal = Main category
- Section = Subcategory

One other thing I was wondering was: Why 7 levels?
Some websites have more structural levels than the &#039;portal&#039; and &#039;section&#039; level. Also, the tile building blocks could be split up in even smaller tiles (like the header, body and footer section) and even those could be split up etc... Is your definition based on being &quot;workable&quot; or is there another reason?

Keep up the good work. Waiting for #4 :)]]></description>
		<content:encoded><![CDATA[<p>Thanks for a great addition to the series Joe. </p>
<p>I&#8217;m trying to convert your theoretical approach to a -for me- more tangible example. Would it be fair to translate your top level stacking orders like this (for most situations):<br />
- Portal Suite = Website (as in top navigation like &#8220;consumer, business<br />
- Portal = Main category<br />
- Section = Subcategory</p>
<p>One other thing I was wondering was: Why 7 levels?<br />
Some websites have more structural levels than the &#8216;portal&#8217; and &#8216;section&#8217; level. Also, the tile building blocks could be split up in even smaller tiles (like the header, body and footer section) and even those could be split up etc&#8230; Is your definition based on being &#8220;workable&#8221; or is there another reason?</p>
<p>Keep up the good work. Waiting for #4 <img src='http://www-boxesandarrows-com.zippykid.netdna-cdn.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tonant</title>
		<link>http://boxesandarrows.com/building-block-definitions-containers/#comment-6820</link>
		<dc:creator>tonant</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/building-block-definitions-containers/#comment-6820</guid>
		<description><![CDATA[yes, yes, I can use this :)]]></description>
		<content:encoded><![CDATA[<p>yes, yes, I can use this <img src='http://www-boxesandarrows-com.zippykid.netdna-cdn.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joelamantia</title>
		<link>http://boxesandarrows.com/building-block-definitions-containers/#comment-6821</link>
		<dc:creator>joelamantia</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/building-block-definitions-containers/#comment-6821</guid>
		<description><![CDATA[@Floris:  You could translate the blocks to this sort of situation (if I understand correctly) - though I recommend keeping in mind the idea that the blocks are aimed at tile-based modular design and development situations, rather than categories in an information structure.

Very true that the blocks can be split into smaller elements; if introducing further granularity suits your purposes, I encourage doing so.  The blocks are meant to be an open system that grows with adoption by the community, so I also encourage sharing any sorts of &#039;extensions&#039; that come about.

Seven levels provides considerable potential for scaling with structure, while retaining flexibility.  

@Patrick:  I&#039;m glad to hear it&#039;s useful to you!]]></description>
		<content:encoded><![CDATA[<p>@Floris:  You could translate the blocks to this sort of situation (if I understand correctly) &#8211; though I recommend keeping in mind the idea that the blocks are aimed at tile-based modular design and development situations, rather than categories in an information structure.</p>
<p>Very true that the blocks can be split into smaller elements; if introducing further granularity suits your purposes, I encourage doing so.  The blocks are meant to be an open system that grows with adoption by the community, so I also encourage sharing any sorts of &#8216;extensions&#8217; that come about.</p>
<p>Seven levels provides considerable potential for scaling with structure, while retaining flexibility.  </p>
<p>@Patrick:  I&#8217;m glad to hear it&#8217;s useful to you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tboll</title>
		<link>http://boxesandarrows.com/building-block-definitions-containers/#comment-6822</link>
		<dc:creator>tboll</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/building-block-definitions-containers/#comment-6822</guid>
		<description><![CDATA[Joe,  Thank you for develolping this series.  I have found them very very useful.  This takes all of the conceptual talk about containers and building blocks and applies it which is what allows for further thought.  I am very happy to have found this series.

Thanks a lot

I wish that I could publish this to my LinkedIn account for my contacts and others that ask me questions to see.

Trevor Bollers]]></description>
		<content:encoded><![CDATA[<p>Joe,  Thank you for develolping this series.  I have found them very very useful.  This takes all of the conceptual talk about containers and building blocks and applies it which is what allows for further thought.  I am very happy to have found this series.</p>
<p>Thanks a lot</p>
<p>I wish that I could publish this to my LinkedIn account for my contacts and others that ask me questions to see.</p>
<p>Trevor Bollers</p>
]]></content:encoded>
	</item>
</channel>
</rss>
