<?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: WordPress Menu Management</title>
	<atom:link href="http://ontekusuto.iamronen.com/2010/01/wordpress-menu-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://ontekusuto.iamronen.com/2010/01/wordpress-menu-management/</link>
	<description></description>
	<lastBuildDate>Fri, 14 May 2010 15:43:37 -0400</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ash Goodman</title>
		<link>http://ontekusuto.iamronen.com/2010/01/wordpress-menu-management/comment-page-1/#comment-15</link>
		<dc:creator>Ash Goodman</dc:creator>
		<pubDate>Sat, 30 Jan 2010 16:19:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.iamronen.com/ontekusuto/?p=264#comment-15</guid>
		<description>I think including drop down menus as a standard feature is not a good idea, unless there is an easy way for a theme builder to override the dropdown code built in with one of their preference. Otherwise we&#039;re stuck with whatever code base is built in. If its jquery and I like jqery fine,. but what if i like mootools, or what if I want to use a different piece of jquery for other effects? </description>
		<content:encoded><![CDATA[<p>I think including drop down menus as a standard feature is not a good idea, unless there is an easy way for a theme builder to override the dropdown code built in with one of their preference. Otherwise we&#39;re stuck with whatever code base is built in. If its jquery and I like jqery fine,. but what if i like mootools, or what if I want to use a different piece of jquery for other effects?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://ontekusuto.iamronen.com/2010/01/wordpress-menu-management/comment-page-1/#comment-13</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Fri, 29 Jan 2010 21:33:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.iamronen.com/ontekusuto/?p=264#comment-13</guid>
		<description>If you allow menus to be added to other menus the same way pages/categories/etc are, you could create your own sub-menus that way and have even more flexibility, since the submenu could be different than the actually hierarchy or pages/categories/etc. </description>
		<content:encoded><![CDATA[<p>If you allow menus to be added to other menus the same way pages/categories/etc are, you could create your own sub-menus that way and have even more flexibility, since the submenu could be different than the actually hierarchy or pages/categories/etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iamronen</title>
		<link>http://ontekusuto.iamronen.com/2010/01/wordpress-menu-management/comment-page-1/#comment-14</link>
		<dc:creator>iamronen</dc:creator>
		<pubDate>Fri, 29 Jan 2010 17:41:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.iamronen.com/ontekusuto/?p=264#comment-14</guid>
		<description>Are you suggesting that &quot;menus&quot; be added as another tab in the website contents?   
  
That could definitely open up interesting options - but it requires another level of complexity: managing menus. My gut is telling me this is a &quot;keep it simple&quot; moment. One menu is clear, simple, usually all that&#039;s really needed... but maybe it&#039;s something worth considering as an infrastructure in development?  
  </description>
		<content:encoded><![CDATA[<p>Are you suggesting that &quot;menus&quot; be added as another tab in the website contents?   </p>
<p>That could definitely open up interesting options &#8211; but it requires another level of complexity: managing menus. My gut is telling me this is a &quot;keep it simple&quot; moment. One menu is clear, simple, usually all that&#039;s really needed&#8230; but maybe it&#039;s something worth considering as an infrastructure in development?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keighl</title>
		<link>http://ontekusuto.iamronen.com/2010/01/wordpress-menu-management/comment-page-1/#comment-12</link>
		<dc:creator>Keighl</dc:creator>
		<pubDate>Fri, 29 Jan 2010 17:25:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.iamronen.com/ontekusuto/?p=264#comment-12</guid>
		<description>I agree with your last point. WP has the hierarchies already; I feel like folks will expect the menu management to parallel that at least.  </description>
		<content:encoded><![CDATA[<p>I agree with your last point. WP has the hierarchies already; I feel like folks will expect the menu management to parallel that at least.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iamronen</title>
		<link>http://ontekusuto.iamronen.com/2010/01/wordpress-menu-management/comment-page-1/#comment-11</link>
		<dc:creator>iamronen</dc:creator>
		<pubDate>Fri, 29 Jan 2010 17:05:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.iamronen.com/ontekusuto/?p=264#comment-11</guid>
		<description>It is tempting to cover children (which is why I mentioned it) but: 
 - I am not convinced it is a core need - I haven&#039;t encountered many sites that actually need this. 
 - I am not convinced it is a good approach at all for the web (I feel it&#039;s fairly outdated). 
 - It has a potential to open up many small corners and complications which can make a mess for development. 
 - It needs good front-end theme support &amp; implementation - which isn&#039;t obvious (to me!) 
 - Maybe by addressing straightforward scenarios which rely on core WordPress capabilities (such as subpages and subcategories) we can provide good enough coverage without unnecessary and unwarranted complications. </description>
		<content:encoded><![CDATA[<p>It is tempting to cover children (which is why I mentioned it) but:<br />
 &#8211; I am not convinced it is a core need &#8211; I haven&#039;t encountered many sites that actually need this.<br />
 &#8211; I am not convinced it is a good approach at all for the web (I feel it&#039;s fairly outdated).<br />
 &#8211; It has a potential to open up many small corners and complications which can make a mess for development.<br />
 &#8211; It needs good front-end theme support &amp; implementation &#8211; which isn&#039;t obvious (to me!)<br />
 &#8211; Maybe by addressing straightforward scenarios which rely on core WordPress capabilities (such as subpages and subcategories) we can provide good enough coverage without unnecessary and unwarranted complications.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keighl</title>
		<link>http://ontekusuto.iamronen.com/2010/01/wordpress-menu-management/comment-page-1/#comment-10</link>
		<dc:creator>Keighl</dc:creator>
		<pubDate>Fri, 29 Jan 2010 16:33:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.iamronen.com/ontekusuto/?p=264#comment-10</guid>
		<description>I think you&#039;ve got a great concept for dealing with the children. Ideally, the user should be able have a lot of control over what shows up in the submenus. It seems like leaving out children options would really be stopping short. </description>
		<content:encoded><![CDATA[<p>I think you&#039;ve got a great concept for dealing with the children. Ideally, the user should be able have a lot of control over what shows up in the submenus. It seems like leaving out children options would really be stopping short.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

