Each situation is unique based on specific organizational needs and issues. Although the benefits may be difficult to quantify at times, at some point, your company will simply decide that, ROI or not, it can't live any longer with the (likely growing) pain of not effectively managing your content.
DISCOVER Magazine, one of the most widely read science mags in the US, had out grown its dated Web Content Management infrastructure for www.discovermagazine.com. Times were changing, multi-media was big and in general Web and CMS technology had moved forward significantly. After analyzing current needs and taking stock of the Web CMS landscape DISCOVER ultimately selected the open source Plone platform. This is a two-part series where we look at the CMS features which convinced DISCOVER to chose Plone.
Open source delivers on the basics. The move to Plone delivered on the basic value proposition of open source: we got a very sturdy platform that worked well for our editors and didn't have to pay a dime in license fees.
The worldwide ecosystem of interested parties involved in website and web application development has become enormous. Accordingly, there are few unifying themes among the various parties other than the mutual goal of having a “good” website as the final product. However the definition of what is good is entirely subjective. Many other requirements such as the ability to leverage existing resources and a desire to integrate the new project with existing enterprise applications contend for attention in the decision process. To get a clear idea of how we might increase the buzz and attention for Plone and Zope, let's profile some of the interested parties.
Back in 2008, Pydanny and I presented at the Plone Conference in DC on NASA Science, the Science Mission Directorates' outreach site. In case you didn't know, we did it in Plone, and everyone seemed to want to know why and how. We decided to tell the world with a presentation, and not long after, were asked to write up a case study. Here it is.
An article was recently published comparing the usability of Joomla with Wordpress for simple tasks. The article argues that whilst Wordpress is not necessarily as powerful as Joomla, it does many of the simple, common tasks that one might want a CMS for and does them in a much simpler, easier manner. So just for completeness and to see how Plone stacks up doing the same things I'm going to present how Plone fares doing the exact same tasks in that original article.
Recently, my colleagues and I decided that we needed to replace our public website's content management system. After some preliminary evaluation, we determined that we would evaluate Plone and Drupal. In the end, we went with Plone at work, and I've been working with it a lot for the past few months. However, I was impressed by Drupal, and that's what I use to run this blog. Having seen both worlds a bit, I see a lot of comparison of the two systems. Here, I'd like to present my take on their similarities and differences.
CMS software selection with Plone and Microsoft Office Sharepoint Server (MOSS) as finalists seems to have become a pretty common case. This is true especially for “intranet/extranet” projects in which the primary focus is on web publishing and collaboration features. I’ve been asked several times to work on comparing the two and I’d like to share some of this experience. Also note that this can’t be a “vendor neutral” comparison because of my involvement in Plone; but I’ll do my best to highlight differences and strenghths of the two solutions.
An organization we at Reflab work with recently re-evaluated Plone against Sharepoint 2007; their main requirements are related to document management, where Sharepoint is for sure quite strong. What’s interesting is that they made the comparison also considering the different platforms and browsers their organization uses. Here are the results of their analysis and tests, they where so kind to share them with us, I checked them and translated them. I hope you’ll find them useful.
As an experienced Plone front end developer, people are often surprised when I often decide not to use Plone, in favour of something like Drupal or Wordpress. I thought it would be useful to explain why and how I make this decision. I know some of these points won’t be popular in the Plone community, but they are based on experience, and think this blog post will be useful to people deciding whether to use it or not.