<?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: Now in Wordpress</title>
	<atom:link href="http://www.webscaped.com/articles/2008/10/now-in-wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webscaped.com/articles/2008/10/now-in-wordpress/</link>
	<description>Website of Michael Adams, Australian web developer</description>
	<lastBuildDate>Fri, 26 Feb 2010 12:46:19 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Michael</title>
		<link>http://www.webscaped.com/articles/2008/10/now-in-wordpress/comment-page-1/#comment-8</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Tue, 07 Oct 2008 02:23:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.webscaped.com/?p=69#comment-8</guid>
		<description>&gt; The biggest hiccup was moving the content into Drupal.

Hehe, Drupal on the mind.  I&#039;d imagine moving the content to Drupal would be even more difficult.  The import/export part of Wordpress is really easy.  

Getting plugins installed is also too easy.  I have to stop myself from heading over to the wordpress site and installing every plugin I can find.

&gt; This is strange at first but actually faster later on when used to. Since the
&gt; Wordpress post/page form is rather long, it makes sense to put the button 
&gt; next to the content area rather than having to scroll down to publish an item.

Indeed, the commonly changed fields are up the top of the page, I hardly go down to the bottom to fill out the more advanced options.  With screens getting larger and wider, a submit button on the side makes sense.</description>
		<content:encoded><![CDATA[<p>> The biggest hiccup was moving the content into Drupal.</p>
<p>Hehe, Drupal on the mind.  I&#8217;d imagine moving the content to Drupal would be even more difficult.  The import/export part of Wordpress is really easy.  </p>
<p>Getting plugins installed is also too easy.  I have to stop myself from heading over to the wordpress site and installing every plugin I can find.</p>
<p>> This is strange at first but actually faster later on when used to. Since the<br />
> Wordpress post/page form is rather long, it makes sense to put the button<br />
> next to the content area rather than having to scroll down to publish an item.</p>
<p>Indeed, the commonly changed fields are up the top of the page, I hardly go down to the bottom to fill out the more advanced options.  With screens getting larger and wider, a submit button on the side makes sense.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Antti</title>
		<link>http://www.webscaped.com/articles/2008/10/now-in-wordpress/comment-page-1/#comment-7</link>
		<dc:creator>Antti</dc:creator>
		<pubDate>Mon, 06 Oct 2008 23:48:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.webscaped.com/?p=69#comment-7</guid>
		<description>Gonrats on making the change, Michael! I am really happy with Wordpress myself as a blogging platform. It is easy enough for the developer as well as the user.

&gt; The biggest hiccup was moving the content into Drupal.

Getting Drupal and Wordpress mixed here? :)

&gt; The one thing that bugs me</description>
		<content:encoded><![CDATA[<p>Gonrats on making the change, Michael! I am really happy with Wordpress myself as a blogging platform. It is easy enough for the developer as well as the user.</p>
<p>&gt; The biggest hiccup was moving the content into Drupal.</p>
<p>Getting Drupal and Wordpress mixed here? <img src='http://www.webscaped.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>&gt; The one thing that bugs me</p>
]]></content:encoded>
	</item>
</channel>
</rss>
