<?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>Mike Van WinkleIs the WordPress Theme Directory a Barrier to Acceptance as a CMS? | Mike Van Winkle</title>
	<atom:link href="http://www.mikevanwinkle.com/tag/wordpress-theme-directory/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mikevanwinkle.com</link>
	<description>New Media Consultant and Wordpress Freak</description>
	<lastBuildDate>Sat, 04 Sep 2010 14:48:12 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Is the WordPress Theme Directory a Barrier to Acceptance as a CMS?</title>
		<link>http://www.mikevanwinkle.com/wordpress/is-the-wordpress-theme-directory-a-barrier-to-acceptance-as-a-cms/</link>
		<comments>http://www.mikevanwinkle.com/wordpress/is-the-wordpress-theme-directory-a-barrier-to-acceptance-as-a-cms/#comments</comments>
		<pubDate>Wed, 21 Oct 2009 13:32:45 +0000</pubDate>
		<dc:creator>Mike Van Winkle</dc:creator>
				<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[Wordpress CMS]]></category>
		<category><![CDATA[Wordpress theme directory]]></category>
		<category><![CDATA[Wordpress Themes]]></category>

		<guid isPermaLink="false">http://www.mikevanwinkle.com/?p=347</guid>
		<description><![CDATA[I&#8217;ve grown a little frustrated with the WordPress Theme Directory. On the one hand I very much appreciate what they are trying to do, setting standards of excellence for theme development. Add to this the ez search-and-click install available since &#8230; <a href="http://www.mikevanwinkle.com/wordpress/is-the-wordpress-theme-directory-a-barrier-to-acceptance-as-a-cms/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve grown a little frustrated with the <a title="WordPress Theme Directory" href="http://wordpress.org/extend/themes/">WordPress Theme Directory</a>. On the one hand I very much appreciate what they are trying to do, setting standards of excellence for theme development. Add to this the ez search-and-click install available since 2.8 and you have the most user friendly blogging system available.</p>
<p>Here&#8217;s the problem, I have a theme that is built to make <a title="WordPress Theme for Actors" href="http://www.mikevanwinkle.com/themes/onstage-theme-for-actors/">WordPress a CMS</a>, so it requires a few steps to set up. But I just got an email back from the WordPress clue in which it was clear that the theme tester, effectively the gate keeper, didn&#8217;t even bother going through the steps.</p>
<p>My <a title="WordPress Theme for Actors" href="http://www.mikevanwinkle.com/themes/onstage-theme-for-actors/">Onstage Theme for Actors</a> uses &#8216;/home.php&#8217; to display a headshot, and only a couple of excerpts from the blog. Users have to create a page for the blog template that is included. But the theme tester didn&#8217;t even bother to set it up. Instead he complained that the posts weren&#8217;t paged and there was no sidebar, both of which are part of the blog template.</p>
<p>So how is WordPress to become recognized as a full content  management solution when the WordPress theme directory seems to expect a cookie cutter installation process?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mikevanwinkle.com/wordpress/is-the-wordpress-theme-directory-a-barrier-to-acceptance-as-a-cms/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
