[Evangelism] [Plone-developers] Looking for talking points comparing Plone vs. Wordpress

Armin Stroß-Radschinski developer at acsr.de
Fri Oct 26 10:01:04 UTC 2012

Lennart you are right,
but Plone giving WordPress a challenge as a simple blog or simple  
workflow website tool is like the tiger wanting to eat whiskas all days.

Our target is more catching all the upcoming tigers and cure them from  
trying to start with cat food or cheese.

There is line between these markets WP cannot cross until now. For a  
lot of agencies praising WP as easy and fast / cheap solution, there  
is a point the customer grows his business. Lets catch them there!  
Maybe before they are addicted to cat food. This is our strenght.  
Security, deployment, scaleability, access control, workflows etc.


Am 26.10.2012 um 11:01 schrieb Lennart Regebro:

> On Thu, Oct 25, 2012 at 3:25 PM, Ed Manlove <devPyPlTw at verizon.net>  
> wrote:
>> I'm attending a local WordCamp [1] in a couple of days - proudly  
>> wearing
>> my Plone T-Shirt - and wanted to brush up on my Plone vs. WordPress
>> talking points.  All of my Plone work has either been on my own  
>> project
>> or within Plone core (RTL, UI testing, i18n, etc) so I've never  
>> really
>> looked outwards too closely. I going to do some searching around but
>> wanted to see if anyone, in particular our Plone development shops,  
>> have
>> any notes when they talk/work with customers on showing the value of
>> Plone as compared to Wordpress.  Thanks.
> My opinion on the matter:
> They are just different. Wordpress is a blog/WebCMS. If you are OK
> with using finished templates, making a website with Wordpress is fast
> and relatively painless. It works fine for a small "poster-type"
> website where you have products and a blog for news/pressreleases. And
> if you have a custom design there are tons of HTML hackers that can
> skin it. So wordpress is good, if what wordpress does is what you
> want.
> Plone is an "enterprise" CMS, where you can have custom content types,
> custom workflow and you can make loads of things happen automatically.
> You can make it do anything you want, as long as what you want is a
> content management system. I have customers who use it essentially as
> a workflowed document management system, where PDF's with actual
> scanned papers are moved throughout stages and approvals, all done
> with TTW configuration.
> Plone therefore is what you use if Wordpress *doesn't* do exactly what
> you want. The benefit here with Plone is that you can use it for the
> type of sites you use Wordpress for as well, which means by starting
> with Plone you don't paint yourself into a corner. However, there are
> few finished skins to choose from, so you are likely to want your own
> custom design, and implementing it takes more work, and you generally
> can't host it at the really cheap PHP-type hosts that Wordpress can be
> on. So the cost is higher.
> //Lennart
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_sfd2d_oct
> _______________________________________________
> Plone-developers mailing list
> Plone-developers at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/plone-developers

More information about the Evangelism mailing list