<?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: Some pleas to reduce WordPress misery</title>
	<atom:link href="http://adrianshort.co.uk/2008/10/13/some-pleas-to-reduce-wordpress-misery/feed/" rel="self" type="application/rss+xml" />
	<link>http://adrianshort.co.uk/2008/10/13/some-pleas-to-reduce-wordpress-misery/</link>
	<description>Design, citizenship and the city</description>
	<lastBuildDate>Mon, 31 Oct 2011 09:12:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Adrian Short</title>
		<link>http://adrianshort.co.uk/2008/10/13/some-pleas-to-reduce-wordpress-misery/comment-page-1/#comment-140</link>
		<dc:creator>Adrian Short</dc:creator>
		<pubDate>Mon, 13 Oct 2008 17:13:42 +0000</pubDate>
		<guid isPermaLink="false">http://adrianshort.co.uk/?p=134#comment-140</guid>
		<description>Of course you can&#039;t please everyone all the time but that&#039;s all the more reason to be explicit about who you&#039;re trying to please most and to create beautiful defaults for them. I&#039;m not suggesting that WP should be characterless and impersonal. More that it should favour what I imagine to be the mass of users -- people who get a few dozen visitors a day, a handful of comments per post if they&#039;re lucky and whose overwhelmingly most common reason for logging in is to write a new post. The mass aren&#039;t developers or even tweakers, they just want to post and go. 

One-click plugin installs and core upgrades in 2.7 will be a big step forward. It&#039;d be better still to see writing rather than monitoring put at the heart of the application. If you&#039;re after character, start being &quot;cool blog software&quot; rather than a &quot;state-of-the-art publishing platform&quot; and strip the power user features out into plugins or options in the admin UI. WordPress Lite?</description>
		<content:encoded><![CDATA[<p>Of course you can&#8217;t please everyone all the time but that&#8217;s all the more reason to be explicit about who you&#8217;re trying to please most and to create beautiful defaults for them. I&#8217;m not suggesting that WP should be characterless and impersonal. More that it should favour what I imagine to be the mass of users &#8212; people who get a few dozen visitors a day, a handful of comments per post if they&#8217;re lucky and whose overwhelmingly most common reason for logging in is to write a new post. The mass aren&#8217;t developers or even tweakers, they just want to post and go. </p>
<p>One-click plugin installs and core upgrades in 2.7 will be a big step forward. It&#8217;d be better still to see writing rather than monitoring put at the heart of the application. If you&#8217;re after character, start being &#8220;cool blog software&#8221; rather than a &#8220;state-of-the-art publishing platform&#8221; and strip the power user features out into plugins or options in the admin UI. WordPress Lite?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://adrianshort.co.uk/2008/10/13/some-pleas-to-reduce-wordpress-misery/comment-page-1/#comment-139</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Mon, 13 Oct 2008 15:46:41 +0000</pubDate>
		<guid isPermaLink="false">http://adrianshort.co.uk/?p=134#comment-139</guid>
		<description>Ouch!

Some of the things you hate are the favorite features of others. We&#039;ve never tried to be bland or generic in our approach, which means that some people will be horribly offended and some will be delighted by some choices big (news feed) and small (howdy), but I&#039;d prefer that than something generic and soulless with no personality, character, or ties to the larger community.

Second I&#039;d say if these things bother you so much it might be worth investing in some minor changes like bookmarking the write page, using the setting to change the news feed, or &lt;a href=&quot;http://wordpress.org/extend/plugins/better-howdy/&quot; rel=&quot;nofollow&quot;&gt;one of the plugins&lt;/a&gt; to de-howdify your admin and relieving you from significant misery. If you need help with any of these just drop me an email and I&#039;ll arrange for someone to walk you through everything.

The beauty of WordPress is in its customization, not its defaults. The average WP blog has 4.96 plugins active and the distribution is huge. My WordPress is probably completely different from your WordPress, and that&#039;s a beautiful thing. There is no one size fits all.</description>
		<content:encoded><![CDATA[<p>Ouch!</p>
<p>Some of the things you hate are the favorite features of others. We&#8217;ve never tried to be bland or generic in our approach, which means that some people will be horribly offended and some will be delighted by some choices big (news feed) and small (howdy), but I&#8217;d prefer that than something generic and soulless with no personality, character, or ties to the larger community.</p>
<p>Second I&#8217;d say if these things bother you so much it might be worth investing in some minor changes like bookmarking the write page, using the setting to change the news feed, or <a href="http://wordpress.org/extend/plugins/better-howdy/" rel="nofollow">one of the plugins</a> to de-howdify your admin and relieving you from significant misery. If you need help with any of these just drop me an email and I&#8217;ll arrange for someone to walk you through everything.</p>
<p>The beauty of WordPress is in its customization, not its defaults. The average WP blog has 4.96 plugins active and the distribution is huge. My WordPress is probably completely different from your WordPress, and that&#8217;s a beautiful thing. There is no one size fits all.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
