<?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>Foliovision &#187; cms</title>
	<atom:link href="http://foliovision.com/tag/cms/feed" rel="self" type="application/rss+xml" />
	<link>http://foliovision.com</link>
	<description>Making the web work for you</description>
	<lastBuildDate>Mon, 14 May 2012 12:40:30 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
<image><title>Foliovision</title><url>http://foliovision.com/site/wp-content/themes/foliovision/images/foliovision-logo-380.gif</url><link>http://foliovision.com</link><width>240</width><height>66</height><description>Making the web work for you</description></image>		<item>
		<title>Drupal vs Joomla vs WordPress: Developer&#8217;s Perspective</title>
		<link>http://foliovision.com/2011/04/02/drupal-vs-joomla-mambo-vs-wordpress</link>
		<comments>http://foliovision.com/2011/04/02/drupal-vs-joomla-mambo-vs-wordpress#comments</comments>
		<pubDate>Sat, 02 Apr 2011 22:12:18 +0000</pubDate>
		<dc:creator>alec</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[cms]]></category>
		<category><![CDATA[drupal]]></category>
		<category><![CDATA[foliopress]]></category>
		<category><![CDATA[joomla]]></category>
		<category><![CDATA[magento]]></category>
		<category><![CDATA[mambo]]></category>
		<category><![CDATA[marketing]]></category>

		<guid isPermaLink="false">http://foliovision.com/?p=2157</guid>
		<description><![CDATA[In a CMS discussion group I belong to, someone recently asked: Is there someone with experience with Drupal, Joomla/Mambo and WordPress who can tell what the differences are? What are the strong and weak points? For better or worse, I am that person. So here's my summary of the advantages and disadvantages of each of [...]<h3 class="related_posts_title">You might also like</h3>
<ol class="related_posts">
			<li><a href="http://foliovision.com/seo-tools/other-cms/mambo-joomla" rel="bookmark">
            <div class="noimage-1"></div>
      Mambo / Joomla</a><!-- (20.3)-->
    </li>
			<li><a href="http://foliovision.com/seo-tools/other-cms/mambo-joomla/mambo-embedded-page-menu" rel="bookmark">
            <img src="http://foliovision.com/images/mambo-plugins/100/calum-ross-mortgage-website.gif" />
      Mambo Embedded Page Menus</a><!-- (12.4)-->
    </li>
			<li class="last"><a href="http://foliovision.com/seo-tools" rel="bookmark">
            <div class="noimage-3"></div>
      Foliovision Tools</a><!-- (11.4)-->
    </li>
	</ol>
<div class="related_posts_clear"></div>
]]></description>
			<content:encoded><![CDATA[<p>In a CMS discussion group I belong to, someone recently asked:</p>
<blockquote>
<p>Is there someone with experience with Drupal, Joomla/Mambo and WordPress who can tell what the differences are? What are the strong and weak points?</p>
</blockquote>
<p>For better or worse, I am that person. So here's my summary of the advantages and disadvantages of each of the above CMS platforms.</p>
<h3><a href="http://drupal.org/" class="liexternal">Drupal</a></h3>
<h4>Advantages</h4>
<ul>
    <li>Very clean core code.</li>
    <li>Good project leadership from <a href="http://acquia.com/about-us" class="liexternal">Acquia</a>.</li>
    <li>Some very good developers available for hire.</li>
    <li>Fewer clowns available for hire (you can either code Drupal or you can't, it's harder to fake it).</li>
    <li>Can be made very server efficient in the right hands (scaleable).</li>
</ul>
<h4>Disadvantages</h4>
<ul>
    <li>Less ready made drop-in plugins. You're going to &#160;have to get your hands dirty almost every time.</li>
    <li>More imposing default user interface.</li>
    <li>Fewer developers.</li>
    <li>More expensive developers.</li>
</ul>
<h3><a href="http://www.joomla.org/" class="liexternal">Joomla</a>/<a href="#" class="liinternal">Mambo</a></h3>
<h4>Advantages</h4>
<ul>
    <li>Good menu system.</li>
    <li>Strong static page structure (cf. weblog).</li>
    <li>Built-in membership/community features.</li>
    <li>Long time on the market.</li>
    <li>I'm searching here.</li>
</ul>
<h4>Disadvantages</h4>
<ul>
    <li>Built-in performance pretty sluggish/clunky.</li>
    <li>Horrid built-in URLs.</li>
    <li>Weak weblog section.</li>
    <li>Hard to theme. A Mambo/Joomla site looks like Mambo/Joomla, like it or not.</li>
    <li>Crappy built-in SEO. Leading SEO plugin belongs to a very peculiar developer and is encrypted (have fun repairing the SEO plugin, we reverse engineered and decrypted it for our site to make our changes even after paying for it).</li>
    <li>Nasty, nasty core code. Very difficult to fix broken items.</li>
    <li>Fractured community (never healed after Joomla/Mambo split back in 2006).</li>
    <li>Most good plugins are pay.</li>
    <li>Rather mediocre developers. Anyone who likes to code in Joomla/Mambo in 2011 ought to see a psychiatrist.</li>
    <li>Developer pricing is all over the map as there are many old-school Mambo/Joomla developers still ought there churning out convoluted future-resistant code quite affordably.</li>
</ul>
<h3>WordPress</h3>
<h4>Advantages</h4>
<ul>
    <li>Huge community.</li>
    <li>Easy to optimise for performance thanks to <a href="http://ocaoimh.ie/wp-super-cache/" class="liexternal">Donncha O Caoimh</a> and&#160;<a href="http://www.w3-edge.com/wordpress-plugins/w3-total-cache/" class="liexternal">Frederick Townes</a>. Great work guys.</li>
    <li>Easy to theme in a unique way. A WordPress site does not have to look like a WordPress site.</li>
    <li>Great plugin architecture.</li>
    <li>Plugins for everything.</li>
    <li>Lots of great professional developers.</li>
    <li>Fast development cycle. Improvements every year.</li>
    <li>Active leadership from Automattic and founding team. Particular thanks to <a href="http://markjaquith.com/" class="liexternal">Mark Jaquith</a> for keeping the community running with less nepotism and more fairness than most collective human endeavour.</li>
</ul>
<h4>Disadvantages</h4>
<ul>
    <li>Fairly weak core code (in comparison to Drupal, but not Joomla!) but core getting better every year.</li>
    <li>Lots of really crap faker developers in the pool who couldn't build a working website to save their mother's life.</li>
    <li>Lots of popular but seriously broken plugins which will cripple your website performance forever and make it nearly impossible for you to cleanly upgrade (NextGen Gallery, I'm looking at you but not just you).</li>
    <li>Really <a href="http://foliovision.com/2011/03/28/paid-wordpress-themes-woo-vs-elegantthemes" class="liinternal">crappy commercial themes</a> which are heavily marketed but compromise your ability to either upgrade or switch themes and compromise performance for the life of your site.</li>
    <li>Weak static page management without adding plugins. Easily fixed with said plugins.</li>
    <li>Too fast an upgrade cycle. You have to keep upgrading your site, whether you like it or not, for security reasons. There are no security releases only new versions. Feel the pain for a commercial site with running a full complement of plugins. Corollary: choose your plugins and plugin developers very, very carefully for cleanliness of code and frequency of update.</li>
</ul>
<h3>Conclusion</h3>
<p>For a very large commercial project, I can see a justification for choosing Drupal. On a big project, most of your expense will be custom development anyway - everything has to be optimised and integrated - so you don't much care one way or another about a myriad of plugins which you will probably not use. I still wouldn't make that trade-off: slightly better core code for a vast pool of community contributed code. But it's a defensible position.</p>
<p>Joomla/Mambo should die a violent death. We did our first CMS project in Mambo and last year redeveloped a couple of existing sites in Joomla. Our best developers - very platform agnostic - threatened to quit if I accepted anymore Joomla work. Such crappy, convoluted spaghetti code they'd never seen. And these developers have had ample chance to see the worst side of WordPress.</p>
<p>The only justification for a site in Joomla/Mambo is that it's legacy (i.e. you already did a lot of custom development on it six years ago and don't have the budget to migrate) or that you are part of an international network standardised on Joomla/Mambo and the mothership discourages anyone from leaving the central platform (our client's situation). For everyone else, just migrate out and count your blessing that you got your site out alive. Enjoy the fresh air and clean code of WordPress (or Drupal).</p>
<p>WordPress is the platform of choice in my opinion for the small, medium or large business. Whatever holes you can find in WordPress (editorial management process, page management, ecommerce, membership site) are easily solved with high quality plugins.</p>
<p>The cool part about WordPress is that the core is kept clean so that you aren't forced to load code you don't need if you want a simple weblog. Thus WordPress can be a weblog, a corporate information site, a membership site, a store or an international news network.</p>
<p>We regularly develop <a href="http://ilovetoronto.com" class="liexternal">advanced</a> <a href="http://juliekinnear.com" class="liexternal">real estate</a> <a href="http://jaybanks.ca" class="liexternal">sites</a> <a href="http://ellidavis.com" class="liexternal">in WordPress</a>, maintain a very sophisticated <a href="http://lsminsurance.ca" class="liexternal">insurance site</a>, have developed elaborate <a href="http://stagersource.ca" class="liexternal">furniture rental</a> systems and develop the <a href="http://theshiksa.com" class="liexternal">most</a> <a href="http://kitchenmusings.com" class="liexternal">delicious</a> <a href="http://thismamacooks.com" class="liexternal">cooking</a> sites as well as <a href="http://opencity.org" class="liexternal">gorgeous online</a> <a href="http://mrbellersneighborhood.com" class="liexternal">literary reviews</a>. Not to mention <a href="http://mondoweiss.net" class="liexternal">political</a>, <a href="http://juancole.com" class="liexternal">news</a> and <a href="http://dirtblawg.com" class="liexternal">law</a> sites. All in WordPress.</p>
<p>The danger with WordPress include the overhyped commercial themes which don't solve your problems but pretend to (I'm looking at you DIYthemes.com and Thesis, <a href="http://foliovision.com/2011/03/28/paid-wordpress-themes-woo-vs-elegantthemes" class="liinternal">WooThemes and ElegantThemes</a>). A related danger are the weak developers and hangers on who have infested the huge WordPress community and enthusiastically give bad advice, whether about SEO or gallery plugins. These clowns will happily break your website for pay or into a defective by design commercial theme. Forewarned is forearmed.</p>
<p>Just like any other serious professional endeavour you need steady hands on deck when you want to take your site to the next level if you want to maintain performance, appearance and compatibility. Once you have substantial traffic or need ecommerce, WordPress is no longer a DIY venture for the non-programmer.</p>
<p>We personally recommend people start a new site on WordPress.com unless they are developing for an established business. Once you have an audience or a functioning business, self-hosted WordPress is the way to go. Even the sky is not a limit. There are few sites we could not develop better and faster in WordPress.</p><h5 class="byline"><img height="48" width="48" src="http://foliovision.com/images/authors/alec-kinnear.jpg" alt="Alec Kinnear" title="Alec Kinnear" /><br /> By Alec</h5><p><a href="http://foliovision.com/2011/04/02/drupal-vs-joomla-mambo-vs-wordpress">Drupal vs Joomla vs WordPress: Developer&#8217;s Perspective</a></p>
<p>Post from: <a href="http://foliovision.com">Foliovision</a></p>
<img src="http://foliovision.com/site/?ak_action=api_record_view&id=2157&type=feed" alt="" /><h3 class="related_posts_title">You might also like</h3>
<ol class="related_posts">
			<li><a href="http://foliovision.com/seo-tools/other-cms/mambo-joomla" rel="bookmark">
            <div class="noimage-1"></div>
      Mambo / Joomla</a><!-- (20.3)-->
    </li>
			<li><a href="http://foliovision.com/seo-tools/other-cms/mambo-joomla/mambo-embedded-page-menu" rel="bookmark">
            <img src="http://foliovision.com/images/mambo-plugins/100/calum-ross-mortgage-website.gif" />
      Mambo Embedded Page Menus</a><!-- (12.4)-->
    </li>
			<li class="last"><a href="http://foliovision.com/seo-tools" rel="bookmark">
            <div class="noimage-3"></div>
      Foliovision Tools</a><!-- (11.4)-->
    </li>
	</ol>
<div class="related_posts_clear"></div>
]]></content:encoded>
			<wfw:commentRss>http://foliovision.com/2011/04/02/drupal-vs-joomla-mambo-vs-wordpress/feed</wfw:commentRss>
		<slash:comments>248</slash:comments>
		</item>
		<item>
		<title>Why WordPress? &#8211; the Tumblr Question</title>
		<link>http://foliovision.com/2008/01/05/why-wordpress-tumblr</link>
		<comments>http://foliovision.com/2008/01/05/why-wordpress-tumblr#comments</comments>
		<pubDate>Sat, 05 Jan 2008 15:06:16 +0000</pubDate>
		<dc:creator>alec</dc:creator>
				<category><![CDATA[WordPress]]></category>
		<category><![CDATA[cms]]></category>
		<category><![CDATA[weblogs]]></category>
		<category><![CDATA[wordpress admin]]></category>

		<guid isPermaLink="false">http://foliovision.com/2008/01/05/why-wordpress-tumblr/</guid>
		<description><![CDATA[I just read the strangest apologia for a new service: Uh, why’s the official Tumblr blog on&#160;WordPress? (broken link - http://blog.davidville.com/2007/02/23/why-wordpress/#comments) Simply - all the CMSy stuff it comes with. Blogs are an awesome platform. WordPress lets our entire staff contribute to the same blog, maintain tags and slugs, save and give feedback on drafts, [...]<h3 class="related_posts_title">You might also like</h3>
<ol class="related_posts">
			<li><a href="http://foliovision.com/seo-tools/wordpress/plugins/wysiwyg" rel="bookmark">
            <img src="http://foliovision.com/images/2009/11/100/foliopress-wysiwyg-guide-13-2.png" />
      True WordPress WYSIWYG: Foliopress</a><!-- (6.5)-->
    </li>
			<li><a href="http://foliovision.com/2007/10/19/lost-wordpress-admin-password" rel="bookmark">
            <div class="noimage-2"></div>
      Lost WordPress Admin Password and Email? How to get back into your weblog&#8230;</a><!-- (6)-->
    </li>
			<li class="last"><a href="http://foliovision.com/2008/01/03/wordpress-admin-theme" rel="bookmark">
            <img src="http://foliovision.com/images/2008/100/Tiger-Admin-Page-Management.jpg" />
      Current WordPress 2.4 Admin Theme a Disappointment</a><!-- (5.4)-->
    </li>
	</ol>
<div class="related_posts_clear"></div>
]]></description>
			<content:encoded><![CDATA[<p>I just read the strangest apologia for a new service: Uh, why’s the official Tumblr blog on&#160;WordPress? (broken link - http://blog.davidville.com/2007/02/23/why-wordpress/#comments)</p>
<blockquote>
<p>Simply - all the CMSy stuff it comes with. Blogs are an awesome platform. WordPress lets our entire staff contribute to the same blog, maintain tags and slugs, save and give feedback on drafts, upload and store media, back and forward publish posts, group our archive by month, lets our audience comment, lists trackbacks, et cetera, et cetera. It’s awesome! Blogs rock! But we knew this. WordPress is the perfect way for a business like ours to communicate with our audience.</p>
</blockquote>
<p>Sounds good to me. David Karp goes on to write about the advantages of <a href="http://www.tumblr.com" class="liexternal">Tumblr</a>: "posting with zero obligations, little or no comment". Great for wisecracking, difficult for communicating.</p>
<span id="more-271"></span>
<h5><a href="/images/2008/sample-tumblr-weblog-blogwi-se.jpg" title="sample tumblr weblog blogwi se" rel="lightbox" class="liimagelink"><img width="400" height="651" src="/images/400/sample-tumblr-weblog-blogwi-se.jpg" alt="sample tumblr weblog blogwi se" /></a><br />
sample tumblr weblog blogwi.se</h5>
<p>&#160;But why not have it both ways? Low overhead posts along with the ability to post more substantial piece.</p>
<p>It sounds to me like Tumblr should be a WordPress plugin or two. I'll probably sign up to see what it is I'm missing out on. I'd like maintaining a weblog to be easier as well. Still at the end of the day, what should be taking the time up is the thinking and writing.</p>
<p>I do agree with David that posting into the default interface on a WordPress weblog is a lot more complicated and unpleasant than it should be. Genuinely distressful for a design sensitive individual. Here's what WordPress Admin default post template looks like:&#160;</p>
<h5><a href="/images/2008/wordpress-default-post-template.gif" rel="lightbox" title="wordpress default post template" class="liimagelink"><img width="400" height="661" alt="wordpress default post template" src="/images/400/wordpress-default-post-template.gif" /></a><br />
wordpress default post template</h5>
<p>Here's what the Foliopress post interface looks like:&#160;</p>
<h5><a href="/images/2008/foliiopress-edit-template-sample.gif" rel="lightbox" title="foliiopress edit template sample" class="liimagelink"><img width="400" height="526" alt="foliiopress edit template sample" src="/images/400/foliiopress-edit-template-sample.gif" /></a><br />
foliiopress edit template sample</h5>
<p>This is just the backend but if you are reading this you are looking at the front end of Foliovision.com. No excess of noise to signal here (5 January 2008). A lot like Tumblr.</p>
<p>The Foliopress Edit Suite does a lot to make running a WordPress weblog easier. It's great for clients as well who don't want to see a bunch of fields they don't need. But I like it as well as it gives a cleaner environment in which to write and think.</p>
<p>What WordPress needs is:</p>
<ul>
    <li>custom simplified edit templates with only the fields you need</li>
    <li>a WYSIWYG editor which actually works</li>
    <li>really simple image posting in the exact format you need</li>
</ul>
<p>Since we've cracked those with Foliopress Edit Templates, <a href="/seo-tools/wordpress/plugins/wysiwyg/" class="liinternal">Foliopress WYSIWYG</a> and Foliopress SEO Images, I'm not sure I'd want to have a Tumblr as well.</p>
<p>In terms of posting passing links, WordPress could still use some help. We should probably design a links posting template for our Foliopress Edit Templates plugin. If we hook that up the Foliopress Dashboard with a default link to posting link with commentary we are a long way to Tumblr simplicity.</p>
<p>An alternative would be the del.icio.us plugins for WordPress that already go along way to making posting links with one line comments easier.</p>
<p>One thing I do like about Tumblr is the really straightforward and attractive design. Apparently <a href="http://davidville.wordpress.com/2007/11/01/tumblr-3/#comments" class="liexternal">another 110,000 people do too</a>.</p>
<p>The archive view is awesome as well. But behind those beautiful archives there is very little useable information. Just links to other sites. Pretty pictures with links could be useful for running a photographer of the day site.</p>
<h5><a href="/images/2008/projectionist-tumblr-archive.jpg" rel="lightbox" title="projectionist tumblr archive" class="liimagelink"><img width="400" height="251" alt="projectionist tumblr archive" src="/images/400/projectionist-tumblr-archive.jpg" /></a><br />
projectionist tumblr archive</h5>
<p>As far as I can tell, Tumblr is running on free.</p>
<p>Free is not a good long-term solution for a service. Monetisation needs to be in there somewhere.</p>
<p>If a service isn't collecting money front up from the users, then the owners need to collect it selling ads or data or both.</p>
<p>Of course, Tumblr may just be a pure play for users, to be made popular at a loss but sold forward at a huge gain to somebody who will be able to monetise the original popular service (Google - YouTube, Yahoo - Flickr).</p>
<p>For those who would like to keep a weblog, my advice is if you don't like writing or making photographs or painting - or something which creates original content - don't bother. An ongoing uncommented scrapbook of links is too ephemeral to be worth the candle. In terms of content aggregrators, there are enough machines out there doing it and those programs work faster than you or I ever will - 24/7.</p>
<p>And if you are going to create substantial content, then you want a communication platform with at least the option for comments from users. My suggestion&#160; is stick with WordPress/Foliopress.</p><h5 class="byline"><img height="48" width="48" src="http://foliovision.com/images/authors/alec-kinnear.jpg" alt="Alec Kinnear" title="Alec Kinnear" /><br /> By Alec</h5><p><a href="http://foliovision.com/2008/01/05/why-wordpress-tumblr">Why WordPress? &#8211; the Tumblr Question</a></p>
<p>Post from: <a href="http://foliovision.com">Foliovision</a></p>
<img src="http://foliovision.com/site/?ak_action=api_record_view&id=271&type=feed" alt="" /><h3 class="related_posts_title">You might also like</h3>
<ol class="related_posts">
			<li><a href="http://foliovision.com/seo-tools/wordpress/plugins/wysiwyg" rel="bookmark">
            <img src="http://foliovision.com/images/2009/11/100/foliopress-wysiwyg-guide-13-2.png" />
      True WordPress WYSIWYG: Foliopress</a><!-- (6.5)-->
    </li>
			<li><a href="http://foliovision.com/2007/10/19/lost-wordpress-admin-password" rel="bookmark">
            <div class="noimage-2"></div>
      Lost WordPress Admin Password and Email? How to get back into your weblog&#8230;</a><!-- (6)-->
    </li>
			<li class="last"><a href="http://foliovision.com/2008/01/03/wordpress-admin-theme" rel="bookmark">
            <img src="http://foliovision.com/images/2008/100/Tiger-Admin-Page-Management.jpg" />
      Current WordPress 2.4 Admin Theme a Disappointment</a><!-- (5.4)-->
    </li>
	</ol>
<div class="related_posts_clear"></div>
]]></content:encoded>
			<wfw:commentRss>http://foliovision.com/2008/01/05/why-wordpress-tumblr/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

