on 12 August 2002
This is the most comprehensive book you are likely to find on (the still emerging) subject of Content Management. It covers all aspects of content management (from collection through organisation to delivery) from all angles including planning and ROI, project management and technical development.
The book does not bother covering particular products nor computer languages. Instead it focuses on the principles and practicalities of implementation and provides the reader with relevant information whether building or buying a CMS.
I'm a web developer with experience of a number of B2C and B2B websites and found this book to be very useful and readable. If you are part of a team buying or building a CMS, I'd recommend everyone on your team read a copy.
on 25 June 2003
It's commonplace now to refer to reference works as "bibles" but this one lives up to its name. It has become a constant item on my desk through all stages of content management projects from business case, through selection, to implementation. The information is clear, comprehensive and very well organised, and well pitched to people in my position - content/project managers in the area where IT and business blur.
I have found the book to be particularly useful in helping to define and breakdown concepts in a way which is not only helpful to those involved in the implementation, but also useful in communicating those concepts to business users and management. It is also full of very helpful details on everything from staffing to how to deal with vendors.
It's worth mentioning that the book also gives access to the complete text online.
on 6 September 2004
This book covers just about anything you might need to know to get started in content management.
The main difficulty is that the author--or his editor--doesn't seem to be able to decide whom he is talking to. As a result, the work is much too long; whichever background you come from (e.g., project management, database management, system analysis or others) you'll find that about a third of the work could have been cut without any loss of coverage. Add to this a series of fully superfluous (and silly) digressions (e.g. about metadata), a rather mechanical--and resultingly redundant--construction of sections in a significant number of chapters (i.e., "Think/Plan/Integrate"), and you start having thoughts about how many trees might have been saved.
No question, however, about the author's knowledge and competence and, in the end, the wisdom buried in there is certainly worth going after.