<?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: Time for WordPress theme standards?</title>
	<atom:link href="http://www.lynx-marketing.com/2009/09/time-for-wordpress-theme-standards/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lynx-marketing.com/2009/09/time-for-wordpress-theme-standards/</link>
	<description>Connect and Convert ™</description>
	<lastBuildDate>Tue, 10 Jan 2012 12:58:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Tom Pick</title>
		<link>http://www.lynx-marketing.com/2009/09/time-for-wordpress-theme-standards/comment-page-1/#comment-16</link>
		<dc:creator>Tom Pick</dc:creator>
		<pubDate>Tue, 22 Sep 2009 19:45:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.lynx-marketing.com/?p=364#comment-16</guid>
		<description>Scott - great post, couldn&#039;t agree more. WordPress newbies in particular would really benefit from this, and gravitate toward free or paid themes that they could be confident met stringent WordPress standards.</description>
		<content:encoded><![CDATA[<p>Scott &#8211; great post, couldn&#39;t agree more. WordPress newbies in particular would really benefit from this, and gravitate toward free or paid themes that they could be confident met stringent WordPress standards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Pick</title>
		<link>http://www.lynx-marketing.com/2009/09/time-for-wordpress-theme-standards/comment-page-1/#comment-12</link>
		<dc:creator>Tom Pick</dc:creator>
		<pubDate>Tue, 22 Sep 2009 15:45:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.lynx-marketing.com/?p=364#comment-12</guid>
		<description>Scott - great post, couldn&#039;t agree more. WordPress newbies in particular would really benefit from this, and gravitate toward free or paid themes that they could be confident met stringent WordPress standards.</description>
		<content:encoded><![CDATA[<p>Scott &#8211; great post, couldn&#39;t agree more. WordPress newbies in particular would really benefit from this, and gravitate toward free or paid themes that they could be confident met stringent WordPress standards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Pick</title>
		<link>http://www.lynx-marketing.com/2009/09/time-for-wordpress-theme-standards/comment-page-1/#comment-11</link>
		<dc:creator>Tom Pick</dc:creator>
		<pubDate>Tue, 22 Sep 2009 14:45:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.lynx-marketing.com/?p=364#comment-11</guid>
		<description>Scott - great post, couldn&#039;t agree more. WordPress newbies in particular would really benefit from this, and gravitate toward free or paid themes that they could be confident met stringent WordPress standards.</description>
		<content:encoded><![CDATA[<p>Scott &#8211; great post, couldn&#39;t agree more. WordPress newbies in particular would really benefit from this, and gravitate toward free or paid themes that they could be confident met stringent WordPress standards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott DeToffol</title>
		<link>http://www.lynx-marketing.com/2009/09/time-for-wordpress-theme-standards/comment-page-1/#comment-10</link>
		<dc:creator>Scott DeToffol</dc:creator>
		<pubDate>Tue, 22 Sep 2009 03:38:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.lynx-marketing.com/?p=364#comment-10</guid>
		<description>I agree that the Theme Directory is a good place to start for free themes. But what about the thousands of free and premium themes that don&#039;t take the time to submit to the official directory? &lt;br&gt;&lt;br&gt;Also, the guidance is for authors not users. The Theme Directory presentation does not define the tags as elements of a self-reporting standard. And the tags seem under-reported. To be useful in this suggested context, they should list what features are supported and which are not.&lt;br&gt;&lt;br&gt;In short, I agree that the Theme Directory is a decent start. Now these self reported &quot;standards&quot; should be made useful to theme users (especially novice users) and extended out into all the legitimate Theme sites and companies around the Internet.</description>
		<content:encoded><![CDATA[<p>I agree that the Theme Directory is a good place to start for free themes. But what about the thousands of free and premium themes that don&#39;t take the time to submit to the official directory? </p>
<p>Also, the guidance is for authors not users. The Theme Directory presentation does not define the tags as elements of a self-reporting standard. And the tags seem under-reported. To be useful in this suggested context, they should list what features are supported and which are not.</p>
<p>In short, I agree that the Theme Directory is a decent start. Now these self reported &#8220;standards&#8221; should be made useful to theme users (especially novice users) and extended out into all the legitimate Theme sites and companies around the Internet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Devin Price</title>
		<link>http://www.lynx-marketing.com/2009/09/time-for-wordpress-theme-standards/comment-page-1/#comment-9</link>
		<dc:creator>Devin Price</dc:creator>
		<pubDate>Mon, 21 Sep 2009 19:19:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.lynx-marketing.com/?p=364#comment-9</guid>
		<description>If anyone would like to see what &lt;a href=&quot;http://WordPress.org&quot; rel=&quot;nofollow&quot;&gt;WordPress.org&lt;/a&gt; actually requires to be in the repository see this link:&lt;br&gt;&lt;br&gt;&lt;a href=&quot;http://wordpress.org/extend/themes/about/&quot; rel=&quot;nofollow&quot;&gt;http://wordpress.org/extend/themes/about/&lt;/a&gt;&lt;br&gt;&lt;br&gt;I like the idea of requiring your html/css to validate- though that does bring up some issues if your are using -moz-border-radius or other unique cases.  Hopefully there is enough community involvement with the repository that authors of bad code can be notified quickly and helped in the process of creating clean valid themes.&lt;br&gt;&lt;br&gt;Thanks Ian for twittering this.</description>
		<content:encoded><![CDATA[<p>If anyone would like to see what <a href="http://WordPress.org" rel="nofollow">WordPress.org</a> actually requires to be in the repository see this link:</p>
<p><a href="http://wordpress.org/extend/themes/about/" rel="nofollow">http://wordpress.org/extend/themes/about/</a></p>
<p>I like the idea of requiring your html/css to validate- though that does bring up some issues if your are using -moz-border-radius or other unique cases.  Hopefully there is enough community involvement with the repository that authors of bad code can be notified quickly and helped in the process of creating clean valid themes.</p>
<p>Thanks Ian for twittering this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Huson</title>
		<link>http://www.lynx-marketing.com/2009/09/time-for-wordpress-theme-standards/comment-page-1/#comment-8</link>
		<dc:creator>Ben Huson</dc:creator>
		<pubDate>Mon, 21 Sep 2009 18:55:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.lynx-marketing.com/?p=364#comment-8</guid>
		<description>There is already a lot of guidance for WordPress theme authors. There is a fairly comprehensive checklist at:&lt;br&gt;&lt;a href=&quot;http://codex.wordpress.org/Theme_Development_Checklist&quot; rel=&quot;nofollow&quot;&gt;http://codex.wordpress.org/Theme_Development_Ch...&lt;/a&gt;&lt;br&gt;&lt;br&gt;&quot;...list of standard features that theme developers would self identify that they include...&quot;&lt;br&gt;&lt;br&gt;The WordPress Themes Directory already provides a solution for this. When creating a theme, it is already possible to add tags to identity key features of the theme such as &quot;one-column&quot; and &quot;fixed-width&quot;. See:&lt;br&gt;&lt;br&gt;&lt;a href=&quot;http://wordpress.org/extend/themes/about/&quot; rel=&quot;nofollow&quot;&gt;http://wordpress.org/extend/themes/about/&lt;/a&gt;&lt;br&gt;&lt;a href=&quot;http://wordpress.org/extend/themes/tag-filter/&quot; rel=&quot;nofollow&quot;&gt;http://wordpress.org/extend/themes/tag-filter/&lt;/a&gt;&lt;br&gt;&lt;br&gt;Is it just a case of encouraging theme authors to use of other tags such as:&lt;br&gt;&lt;br&gt;&quot;xhtml&quot; if your theme is valid XHTML&lt;br&gt;&quot;threaded-comments&quot; if you have a designed threaded comments template&lt;br&gt;&quot;theme-options&quot; if you can customise the theme with settings in the admin&lt;br&gt;&quot;seo&quot; if your site adheres to good SEO principles&lt;br&gt;&quot;widget-enabled&quot; if widgets are supported&lt;br&gt;etc...&lt;br&gt;&lt;br&gt;These tags also get displayed in the WordPress Theme directory on each themes&#039;s page which should mean that users can make an informed decision. For example:&lt;br&gt;&lt;a href=&quot;http://wordpress.org/extend/themes/thematic&quot; rel=&quot;nofollow&quot;&gt;http://wordpress.org/extend/themes/thematic&lt;/a&gt;&lt;br&gt;&lt;br&gt;So if a set of useful tags as outlined above could be decided upon and adopted by some of the major theme frameworks and more popular themes, it may hopefully encourage other theme authors to do the same.</description>
		<content:encoded><![CDATA[<p>There is already a lot of guidance for WordPress theme authors. There is a fairly comprehensive checklist at:<br /><a href="http://codex.wordpress.org/Theme_Development_Checklist" rel="nofollow">http://codex.wordpress.org/Theme_Development_Ch&#8230;</a></p>
<p>&#8220;&#8230;list of standard features that theme developers would self identify that they include&#8230;&#8221;</p>
<p>The WordPress Themes Directory already provides a solution for this. When creating a theme, it is already possible to add tags to identity key features of the theme such as &#8220;one-column&#8221; and &#8220;fixed-width&#8221;. See:</p>
<p><a href="http://wordpress.org/extend/themes/about/" rel="nofollow">http://wordpress.org/extend/themes/about/</a><br /><a href="http://wordpress.org/extend/themes/tag-filter/" rel="nofollow">http://wordpress.org/extend/themes/tag-filter/</a></p>
<p>Is it just a case of encouraging theme authors to use of other tags such as:</p>
<p>&#8220;xhtml&#8221; if your theme is valid XHTML<br />&#8220;threaded-comments&#8221; if you have a designed threaded comments template<br />&#8220;theme-options&#8221; if you can customise the theme with settings in the admin<br />&#8220;seo&#8221; if your site adheres to good SEO principles<br />&#8220;widget-enabled&#8221; if widgets are supported<br />etc&#8230;</p>
<p>These tags also get displayed in the WordPress Theme directory on each themes&#39;s page which should mean that users can make an informed decision. For example:<br /><a href="http://wordpress.org/extend/themes/thematic" rel="nofollow">http://wordpress.org/extend/themes/thematic</a></p>
<p>So if a set of useful tags as outlined above could be decided upon and adopted by some of the major theme frameworks and more popular themes, it may hopefully encourage other theme authors to do the same.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: scribu</title>
		<link>http://www.lynx-marketing.com/2009/09/time-for-wordpress-theme-standards/comment-page-1/#comment-7</link>
		<dc:creator>scribu</dc:creator>
		<pubDate>Mon, 21 Sep 2009 18:50:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.lynx-marketing.com/?p=364#comment-7</guid>
		<description>I don&#039;t think you can actually set any meaningfull standards, besides the ones already imposed by the official theme directory. It would only hinder creativity, in my opinion.</description>
		<content:encoded><![CDATA[<p>I don&#39;t think you can actually set any meaningfull standards, besides the ones already imposed by the official theme directory. It would only hinder creativity, in my opinion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Stewart</title>
		<link>http://www.lynx-marketing.com/2009/09/time-for-wordpress-theme-standards/comment-page-1/#comment-6</link>
		<dc:creator>Ian Stewart</dc:creator>
		<pubDate>Mon, 21 Sep 2009 17:49:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.lynx-marketing.com/?p=364#comment-6</guid>
		<description>Good post. I think the official WordPress Themes Directory is the answer to this. It&#039;s tough to standardize what (in a lot of cases) boils down to style issues. But if you want your Theme included in the official directory you have to commit to what are the really important standards with WordPress Themes. Things like important function calls for plugins and widgetized sidebars. Basically the catastrophic stuff. Anything else is, again, a style issue. Luckily there are a lot of themes to choose from!</description>
		<content:encoded><![CDATA[<p>Good post. I think the official WordPress Themes Directory is the answer to this. It&#39;s tough to standardize what (in a lot of cases) boils down to style issues. But if you want your Theme included in the official directory you have to commit to what are the really important standards with WordPress Themes. Things like important function calls for plugins and widgetized sidebars. Basically the catastrophic stuff. Anything else is, again, a style issue. Luckily there are a lot of themes to choose from!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Time for WordPress theme standards? &#124; ShareFavorite</title>
		<link>http://www.lynx-marketing.com/2009/09/time-for-wordpress-theme-standards/comment-page-1/#comment-5</link>
		<dc:creator>Time for WordPress theme standards? &#124; ShareFavorite</dc:creator>
		<pubDate>Mon, 21 Sep 2009 03:32:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.lynx-marketing.com/?p=364#comment-5</guid>
		<description>[...] is the original post:  Time for WordPress theme standards?       Related [...]</description>
		<content:encoded><![CDATA[<p>[...] is the original post:  Time for WordPress theme standards?       Related [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

