<?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: Replacing &#8220;sidebar&#8221; in WordPress</title>
	<atom:link href="http://justintadlock.com/archives/2009/02/14/replacing-sidebar-in-wordpress/feed" rel="self" type="application/rss+xml" />
	<link>http://justintadlock.com/archives/2009/02/14/replacing-sidebar-in-wordpress</link>
	<description>Life, Blogging, and WordPress</description>
	<lastBuildDate>Fri, 10 Feb 2012 12:19:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Sandro</title>
		<link>http://justintadlock.com/archives/2009/02/14/replacing-sidebar-in-wordpress#comment-258670</link>
		<dc:creator>Sandro</dc:creator>
		<pubDate>Thu, 02 Dec 2010 16:41:35 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=1464#comment-258670</guid>
		<description>The term sidebar doesn&#039;t sound too bad to me, and I guess it describes its function pretty well. I actually wouldn&#039;t like it to see it replaced. Among the other suggested terms, &quot;widget area&quot; would be fine to me, although a bit too much typing.</description>
		<content:encoded><![CDATA[<p>The term sidebar doesn&#8217;t sound too bad to me, and I guess it describes its function pretty well. I actually wouldn&#8217;t like it to see it replaced. Among the other suggested terms, &#8220;widget area&#8221; would be fine to me, although a bit too much typing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://justintadlock.com/archives/2009/02/14/replacing-sidebar-in-wordpress#comment-246560</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Tue, 02 Nov 2010 17:04:25 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=1464#comment-246560</guid>
		<description>I&#039;d like to throw &quot;precincts&quot; into the pot ;o)</description>
		<content:encoded><![CDATA[<p>I&#8217;d like to throw &#8220;precincts&#8221; into the pot ;o)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WhiskeyJim</title>
		<link>http://justintadlock.com/archives/2009/02/14/replacing-sidebar-in-wordpress#comment-234794</link>
		<dc:creator>WhiskeyJim</dc:creator>
		<pubDate>Thu, 30 Sep 2010 19:19:24 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=1464#comment-234794</guid>
		<description>Been awhile since I visited the great WP guru site:)

I like &#039;modules&#039; because it describes the true functionality of a sidebar&#039;s only half functional purpose.  Inspired developers are doing two things which are not necessarily connected; developing functionality in &#039;widgets&#039; and plug-ins, and making themes which define where that functionality is placed.  WP should more formally separate the two ideas and free up the whole design process.  

There is a basic core of functions (Heading, post article, footer, print function, zoom, menu, meta, comments) that should arguably be available out of the box in any theme so that users can utilize themes straight out of the box.

But the user or developer should be able to place website functions or elements (including headings, posts, footers, print functions, menus, meta, comments) in modules anywhere on the screen.  Themes would then be a set of predefined &#039;templates&#039; incorporating a combination of functions that users could choose for each page, or create additional ones themselves.  

Think of the Blogger design interface for a constrained illustration.  Headway gets a lot closer, allowing graphical drag and drop design, but it slows the site down because the functionality should be in the core (I also believe WP should be compilable, so to speak, into html without so many calls during page generation).

If you get my meaning, then even the posts area is really just a function to be placed inside a module.  The idea of a separate widget area in the WP core, separate from built-in functions, would disappear; developers would merely add their own inspirations to the base functions that are shipped with WP in the first place.  In other words, &#039;plug-ins&#039; would download into the same place that posts, etc. reside.  

In still other words, the post loop is just a widget treated differently and hard coded.  I believe the WP core structure ultimately slows down the WP engine, especially as plug-ins with varying quality are added.  The whole thing should be built with modularity in mind, which would naturally clean up a great deal of current widget and plug-in leaks and errors, and free up the whole website design process.  

This modularity approach would also provide developers like Justin with the potential for a fantastic leap forward in functionality:)</description>
		<content:encoded><![CDATA[<p>Been awhile since I visited the great WP guru site:)</p>
<p>I like &#8216;modules&#8217; because it describes the true functionality of a sidebar&#8217;s only half functional purpose.  Inspired developers are doing two things which are not necessarily connected; developing functionality in &#8216;widgets&#8217; and plug-ins, and making themes which define where that functionality is placed.  WP should more formally separate the two ideas and free up the whole design process.  </p>
<p>There is a basic core of functions (Heading, post article, footer, print function, zoom, menu, meta, comments) that should arguably be available out of the box in any theme so that users can utilize themes straight out of the box.</p>
<p>But the user or developer should be able to place website functions or elements (including headings, posts, footers, print functions, menus, meta, comments) in modules anywhere on the screen.  Themes would then be a set of predefined &#8216;templates&#8217; incorporating a combination of functions that users could choose for each page, or create additional ones themselves.  </p>
<p>Think of the Blogger design interface for a constrained illustration.  Headway gets a lot closer, allowing graphical drag and drop design, but it slows the site down because the functionality should be in the core (I also believe WP should be compilable, so to speak, into html without so many calls during page generation).</p>
<p>If you get my meaning, then even the posts area is really just a function to be placed inside a module.  The idea of a separate widget area in the WP core, separate from built-in functions, would disappear; developers would merely add their own inspirations to the base functions that are shipped with WP in the first place.  In other words, &#8216;plug-ins&#8217; would download into the same place that posts, etc. reside.  </p>
<p>In still other words, the post loop is just a widget treated differently and hard coded.  I believe the WP core structure ultimately slows down the WP engine, especially as plug-ins with varying quality are added.  The whole thing should be built with modularity in mind, which would naturally clean up a great deal of current widget and plug-in leaks and errors, and free up the whole website design process.  </p>
<p>This modularity approach would also provide developers like Justin with the potential for a fantastic leap forward in functionality:)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://justintadlock.com/archives/2009/02/14/replacing-sidebar-in-wordpress#comment-229259</link>
		<dc:creator>John</dc:creator>
		<pubDate>Fri, 10 Sep 2010 03:38:27 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=1464#comment-229259</guid>
		<description>&quot;siderbar&quot; is good for me!</description>
		<content:encoded><![CDATA[<p>&#8220;siderbar&#8221; is good for me!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Who&#8217;s Who in WordPress (50+ people you should be following) &#124; WPCandy</title>
		<link>http://justintadlock.com/archives/2009/02/14/replacing-sidebar-in-wordpress#comment-227035</link>
		<dc:creator>Who&#8217;s Who in WordPress (50+ people you should be following) &#124; WPCandy</dc:creator>
		<pubDate>Sat, 04 Sep 2010 07:09:09 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=1464#comment-227035</guid>
		<description>[...] Justin fills his blog with great stuff about WordPress, like recently when he shared his thoughts on how WordPress needs to adjust the &#8220;sidebar&#8221; name to be something more accurate. [...]</description>
		<content:encoded><![CDATA[<p>[...] Justin fills his blog with great stuff about WordPress, like recently when he shared his thoughts on how WordPress needs to adjust the &#8220;sidebar&#8221; name to be something more accurate. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony</title>
		<link>http://justintadlock.com/archives/2009/02/14/replacing-sidebar-in-wordpress#comment-181586</link>
		<dc:creator>Tony</dc:creator>
		<pubDate>Tue, 16 Mar 2010 04:26:17 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=1464#comment-181586</guid>
		<description>I&#039;d suggest &#039;auxiliary&#039;, or abbreviated to &#039;aux&#039;.
We use it for audio etc . . .

Otherwise, &#039;Supplementary&#039; is a good one.

auxBar? auxBlock?
suppBar? suppBlock?</description>
		<content:encoded><![CDATA[<p>I&#8217;d suggest &#8216;auxiliary&#8217;, or abbreviated to &#8216;aux&#8217;.<br />
We use it for audio etc . . .</p>
<p>Otherwise, &#8216;Supplementary&#8217; is a good one.</p>
<p>auxBar? auxBlock?<br />
suppBar? suppBlock?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://justintadlock.com/archives/2009/02/14/replacing-sidebar-in-wordpress#comment-177172</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Sat, 06 Feb 2010 03:06:25 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=1464#comment-177172</guid>
		<description>I like &quot;block&quot; as in main block, header block, footer block, widget block. Now maybe &quot;block&quot; is not the right word, but my point is this discussion really seems to be about is the lack of a common term for all the building blocks that make up a WordPress-generated page. The sidebar is just one of those building blocks.</description>
		<content:encoded><![CDATA[<p>I like &#8220;block&#8221; as in main block, header block, footer block, widget block. Now maybe &#8220;block&#8221; is not the right word, but my point is this discussion really seems to be about is the lack of a common term for all the building blocks that make up a WordPress-generated page. The sidebar is just one of those building blocks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://justintadlock.com/archives/2009/02/14/replacing-sidebar-in-wordpress#comment-171956</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Tue, 29 Dec 2009 17:14:08 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=1464#comment-171956</guid>
		<description>I personally quite like the term sidebar, and think it describes the function rather well. I guess something like &#039;widget space&#039; is a bit more web 2.0 and is also pretty apt.</description>
		<content:encoded><![CDATA[<p>I personally quite like the term sidebar, and think it describes the function rather well. I guess something like &#8216;widget space&#8217; is a bit more web 2.0 and is also pretty apt.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: andri</title>
		<link>http://justintadlock.com/archives/2009/02/14/replacing-sidebar-in-wordpress#comment-167682</link>
		<dc:creator>andri</dc:creator>
		<pubDate>Wed, 09 Dec 2009 17:20:08 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=1464#comment-167682</guid>
		<description>I still confuse using the theme... when i need to hide the widget where can i do that?</description>
		<content:encoded><![CDATA[<p>I still confuse using the theme&#8230; when i need to hide the widget where can i do that?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gstorm</title>
		<link>http://justintadlock.com/archives/2009/02/14/replacing-sidebar-in-wordpress#comment-162932</link>
		<dc:creator>gstorm</dc:creator>
		<pubDate>Tue, 17 Nov 2009 09:25:10 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=1464#comment-162932</guid>
		<description>I think modules would be better for when backpress is out.  Modules could then be the components that hook into the framework.  i.e. bbpress and wp would be modules.
Developers would then be able to create modules extending the basic framework.
This is where your other tutorials on custome taxonomies would really come in handy.
I think blocks better represent what the template is doing, creating widget blocks on the layout for the page.</description>
		<content:encoded><![CDATA[<p>I think modules would be better for when backpress is out.  Modules could then be the components that hook into the framework.  i.e. bbpress and wp would be modules.<br />
Developers would then be able to create modules extending the basic framework.<br />
This is where your other tutorials on custome taxonomies would really come in handy.<br />
I think blocks better represent what the template is doing, creating widget blocks on the layout for the page.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

