vendors' marketing materials decidedly do not help
if you're paying someone by the day to come up with a recommendation
Vendor Subway Map
features they have in their product arsenal
Plone sits on the intersection of the "Web content management", "Social software & collaboration" and "Enterprise portal" lines
cost (both licensing and likely implementation costs), fit with your existing IT architecture, and usability/end-user experience become a lot more important
focus on getting a list of requirements for your end solution
Vendor demos have a tendency to gloss over the warts
The word "CMS" - Content Management System - is quite overloaded
Plone is really a Web CMS
vendors sometimes focus mainly on content production
Other vendors include a dedicated presentation server
Some systems, like Plone, accommodate both in a single server
away from tight integration
towards federation of services on heterogeneous platforms
The "federated" view of IT is more realistic as an option these days
better support for standards
more use of higher level "glue"
Deliverance
plone.org, for example, "deliverates" Plone and Trac
federated architecture that presents a unified user experience
In the Java world, there are more formal standards (notably JSR168 and it's successor JSR186)
in theory
built once and deployed onto different portal containers
An intranet or public website should largely present
a stable, well-thought-out information architecture
a richer, more bespoke, less application-like user experience
a shift away from this one-platform-to-rule-them-all mentality
some of the "platform" arguments are red herrings
External Editor
training your in-house staff
pick a solution that is supportable
specialist vendor
Most modern systems are so complex that you can't just expect your IT staff to be able to support them without at last some investment in training
Bake vs. fry
Assets vs. content
In Plone, there is a structured hierarchy
content tree
mirrors how files are managed on the desktop
Folders and taxonomy
Plone is comparatively weak
Pages and fragments
Managing code and content
Zope and Plone communities have done a lot of work to move development out onto the filesystem
The contenders
Below is a list of systems I think are worth looking at and learning from.
Usability is king
Even Open Text/RedDot, which says in every "datasheet" that Gartner calls its usability "legendary", is confusing to use at times, and many of the other systems - especially the older ones - are downright shocking
just to install the system and click
most enlightening evaluation
If I can't figure it out easily, it's not good enough
What Plone can learn
All in all, this evaluation exercise has confirmed my belief that Plone can hold its head high in the web content management world.
support for the "bake" model
file representation of all content
upload content easily
browse the site via WebDav
IT support staff need to be able to feed and water the servers your CMS runs on
I work at CENTRIM — the Centre for Research in Innovation Management. Beyond work: I enjoy solitude, letting go, camping getaways and dreaming. I have great family and friends, and two gorgeous cats. Take not too much notice of my bookmarks — hundreds are unread!