<?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: Considering Switching &#8211; ExpressionEngine versus WordPress</title>
	<atom:link href="http://douglasstridsberg.com/blog/entries/considering-switching-expressionengine-versus-wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://douglasstridsberg.com/blog/entries/considering-switching-expressionengine-versus-wordpress/</link>
	<description>--- web consulting, following you every step of the way</description>
	<lastBuildDate>Tue, 07 Feb 2012 18:17:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: MKH</title>
		<link>http://douglasstridsberg.com/blog/entries/considering-switching-expressionengine-versus-wordpress/#comment-288</link>
		<dc:creator>MKH</dc:creator>
		<pubDate>Tue, 24 May 2011 15:34:10 +0000</pubDate>
		<guid isPermaLink="false">http://douglasstridsberg.com/blog/index/considering-switching-expressionengine-versus-wordpress#comment-288</guid>
		<description>I agree with the above sentiment. I used EE for a couple of years but got frustrated a) by the 2.0 drama and b) by the increasing cost of extensions that in many cases should be basic functionality of the CMS. 

The only thing that held me back was all the talk of &quot;you have to know PHP to use WP&quot;, and I&#039;m very much a front-end kind of gal, whose experience with PHP was includes and date formatting. 

Nudged by an IT coworker who loved WP, I made the switch and it&#039;s been great! WP is always improving and a heck of a lot cheaper. It&#039;s so much easier to find resources and if there isn&#039;t a plugin for something, just wait a month, or learn to write on yourself.
What I also appreciate is how using WP has given me the need to learn some PHP, a lot of it copy-pasted, but not always. I have a far greater understanding of it after a year of using WP which seems valuable for the long-term, more so than knowing a bunch of EE tags.
EE was OK but I never really got all the hype. WP gets slagged more than it deserves by naysayers ... it&#039;s impressive and so nice to use.</description>
		<content:encoded><![CDATA[<p>I agree with the above sentiment. I used EE for a couple of years but got frustrated a) by the 2.0 drama and b) by the increasing cost of extensions that in many cases should be basic functionality of the CMS. </p>
<p>The only thing that held me back was all the talk of &#8220;you have to know PHP to use WP&#8221;, and I&#8217;m very much a front-end kind of gal, whose experience with PHP was includes and date formatting. </p>
<p>Nudged by an IT coworker who loved WP, I made the switch and it&#8217;s been great! WP is always improving and a heck of a lot cheaper. It&#8217;s so much easier to find resources and if there isn&#8217;t a plugin for something, just wait a month, or learn to write on yourself.<br />
What I also appreciate is how using WP has given me the need to learn some PHP, a lot of it copy-pasted, but not always. I have a far greater understanding of it after a year of using WP which seems valuable for the long-term, more so than knowing a bunch of EE tags.<br />
EE was OK but I never really got all the hype. WP gets slagged more than it deserves by naysayers &#8230; it&#8217;s impressive and so nice to use.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Xavi</title>
		<link>http://douglasstridsberg.com/blog/entries/considering-switching-expressionengine-versus-wordpress/#comment-287</link>
		<dc:creator>Xavi</dc:creator>
		<pubDate>Wed, 04 Aug 2010 11:15:35 +0000</pubDate>
		<guid isPermaLink="false">http://douglasstridsberg.com/blog/index/considering-switching-expressionengine-versus-wordpress#comment-287</guid>
		<description>ExpressionEngine not being Open Source was the main reason why I decided to go with Wordpress.
I&#039;ve now been several years working with Wordpress and am proud of my decission: started just blogging with default themes and little by little I&#039;ve been learning how WP worked (without any books, just reading blogs and the Wordpress Codex is enough).
During these past years I&#039;ve coded several themes, pluguins and extended WP converting it into a powerful CMS full of features (i.e. communicating with private company APIs, some features that appeared recently in version 3.0, AJAX functionality, etc.) and automatizations like thumbnail image creation, custom RSS feeds, intelligent 404 error handling, automatic resizing and labeling of images, SEO...
So Wordpress may require some PHP expertise but it is very well documented in the WP Codex and there&#039;s a very huge community around. Also, it has a great support and upgrades are available surprisingly fast.
My advice is to go for Wordpress. Very easy installation and management while keeping everything SEO and clear plus the flexibility to build anything you can ever think of upon it.
Cheers,
Xavi
 </description>
		<content:encoded><![CDATA[<p>ExpressionEngine not being Open Source was the main reason why I decided to go with WordPress.<br />
I&#8217;ve now been several years working with WordPress and am proud of my decission: started just blogging with default themes and little by little I&#8217;ve been learning how WP worked (without any books, just reading blogs and the WordPress Codex is enough).<br />
During these past years I&#8217;ve coded several themes, pluguins and extended WP converting it into a powerful CMS full of features (i.e. communicating with private company APIs, some features that appeared recently in version 3.0, AJAX functionality, etc.) and automatizations like thumbnail image creation, custom RSS feeds, intelligent 404 error handling, automatic resizing and labeling of images, SEO&#8230;<br />
So WordPress may require some PHP expertise but it is very well documented in the WP Codex and there&#8217;s a very huge community around. Also, it has a great support and upgrades are available surprisingly fast.<br />
My advice is to go for WordPress. Very easy installation and management while keeping everything SEO and clear plus the flexibility to build anything you can ever think of upon it.<br />
Cheers,<br />
Xavi<br />
 </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Coofindinia</title>
		<link>http://douglasstridsberg.com/blog/entries/considering-switching-expressionengine-versus-wordpress/#comment-286</link>
		<dc:creator>Coofindinia</dc:creator>
		<pubDate>Sat, 12 Dec 2009 02:24:42 +0000</pubDate>
		<guid isPermaLink="false">http://douglasstridsberg.com/blog/index/considering-switching-expressionengine-versus-wordpress#comment-286</guid>
		<description>Great article, amazing looking weblog, added it to my favs.</description>
		<content:encoded><![CDATA[<p>Great article, amazing looking weblog, added it to my favs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Douglas</title>
		<link>http://douglasstridsberg.com/blog/entries/considering-switching-expressionengine-versus-wordpress/#comment-285</link>
		<dc:creator>Douglas</dc:creator>
		<pubDate>Thu, 10 Dec 2009 14:11:06 +0000</pubDate>
		<guid isPermaLink="false">http://douglasstridsberg.com/blog/index/considering-switching-expressionengine-versus-wordpress#comment-285</guid>
		<description>Interesting, so what do you currently use? WP or EE?

Although I wrote this a month or two ago I am still very undecided concerning whether to stay with EE or go to WP. I guess we&#039;ll all have to see what EE2.0 brings, right?</description>
		<content:encoded><![CDATA[<p>Interesting, so what do you currently use? WP or EE?</p>
<p>Although I wrote this a month or two ago I am still very undecided concerning whether to stay with EE or go to WP. I guess we&#8217;ll all have to see what EE2.0 brings, right?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brett Munro</title>
		<link>http://douglasstridsberg.com/blog/entries/considering-switching-expressionengine-versus-wordpress/#comment-284</link>
		<dc:creator>Brett Munro</dc:creator>
		<pubDate>Wed, 09 Dec 2009 20:02:44 +0000</pubDate>
		<guid isPermaLink="false">http://douglasstridsberg.com/blog/index/considering-switching-expressionengine-versus-wordpress#comment-284</guid>
		<description>Personally, I find Wordpress painful.

I&#039;m a front-end only kind of guy and its templating system is a nightmare compared to EE/Textpatterns.

Widgets are fine, but they also seem limited - 15 post limit for the &quot;Recent Posts&quot; widget for example. I&#039;m guessing you&#039;ll have to mess with PHP to edit that. Also, it&#039;ll automatically stick them in unordered lists whether you like it or not.

I always check out WP now and again because of all the great plugins/widgets I would like to use, but then I try to port my site design over and fail every time.</description>
		<content:encoded><![CDATA[<p>Personally, I find WordPress painful.</p>
<p>I&#8217;m a front-end only kind of guy and its templating system is a nightmare compared to EE/Textpatterns.</p>
<p>Widgets are fine, but they also seem limited &#8211; 15 post limit for the &#8220;Recent Posts&#8221; widget for example. I&#8217;m guessing you&#8217;ll have to mess with PHP to edit that. Also, it&#8217;ll automatically stick them in unordered lists whether you like it or not.</p>
<p>I always check out WP now and again because of all the great plugins/widgets I would like to use, but then I try to port my site design over and fail every time.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  douglasstridsberg.com/blog/entries/considering-switching-expressionengine-versus-wordpress/feed/ ) in 0.47992 seconds, on Feb 10th, 2012 at 9:25 am UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 10th, 2012 at 10:25 am UTC -->
