I like Contribute—since its introduction in 2002 it’s always been a cheap and reliable application that enables content editors to push their material to websites without any programming or coding skills. It’s been my go-to choice for the content management of small websites that can’t justify the cost and complexity of an online content management system (CMS). Contribute has been upgraded to CS4 with the rest of Adobe’s web applications, but CMSes are getting cheaper and cheaper, and more and more users are becoming adept at HTML, so for the first time I wonder if Contribute’s days are numbered. After looking through Contribute CS4’s new features, I don’t see how it will retain its niche.
Contribute CS4 has been designed with web creators, administrators and content contributors in mind, same as every version of Contribute that preceded it. The most important improvement involves workflow: administrators can now specify a workflow routine so authors or reviewers cannot publish without the proper approvals. Four workflows are possible:
Contribute CS4 is smart enough to hide and reveal tools dynamically depending on the workflow and the user, and it’s practically foolproof. Workflows can be created and edited by administrators for complete control. It works well, and I’m surprised this hasn’t been incorporated in Contribute until now. If you were wary of Contribute due to lax workflow restrictions, look into Contribute CS4 because workflow can be as strict as you need.
It’s a cool feature: you can edit pages with Contribute controls right in your web browser! It is very slick and with it you don’t necessarily need to work with pages in Contribute in order to edit pages with Contribute. However, there are a few requirements and general issues:
The In-Browser Editor has competition from all the content management systems out there—and Dreamweaver CS4’s InContext Editing feature, which does basically the same thing. In-Browser Editing is cool to see and use but in practice I’m not sure it is practical. Users must also connect to the website with the Contribute application before they can work with the site in the browser, which in itself is not a problem but users don’t necessarily need In-Browser Editing if they have Contribute CS4 available.
Contribute CS4 now works more effectively with Flash CS4 Professional and Dreamweaver CS4:
Contribute CS4 also has a great new “content expiration notice” feature that will let you know when content needs to be updated based on a date the user specifies. Contribute can execute a default action if no user intervention occurs—the content can be removed, for example. The downside is that “content” refers only to whole pages, not to text in a particular region.
Compared to other CS4 apps, Contribute CS4 has relatively few new features. Here are the rest of them:
All these feature work properly, but it’s an underwhelming set of features. Very little is groundbreaking here—I probably like the Word-to-PDF conversion the most. These are all good improvements to Contribute, and Contribute CS4 is probably a better application than Contribute CS3, but there are many products out there that do what Contribute does and I think it needs something more if it’s to remain relevant.
I recently shopped around for a developer who would produce a content management system for a client of mine, and his cost for a simple CMS coded in PHP was not much more than a copy of Contribute CS4. Contribute was a valuable product in 2002 but since then open-source content management systems have proliferated and Contribute CS4 needed something to separate itself from its competitors. Contribute CS4 does not have this, and the set of new features is relatively weak.
I do think Contribute CS4 is a good piece of technology and does its job well, but the reasons for choosing it over other options are dwindling.
Contribute CS4
Adobe Systems
US$199 full/$99 upgrade/$799 5-user
Rating: 6/10


Let’s start with who is most likely to benefit from a CMS … it is a non-technical (probably a techna-phobe) who just wants to update their website or web section. The problem with the vast majority of home grown developer apps are two fold: first, the vast majority of the developers are very weak at creating user friendly interfaces (adobes been at it for awhile). Secondly, support. I have supported many small business websites and have used some low cost cms applications and trying to teach the techniphobe to use them is a far bigger challenge than designing a site. Though I am not a big contribute user, I would definately chose it over a low dollar cms sytems.