Web Content Management: A Collaborative Approach
Product Description
A book about developing, managing, maintaining and deploying Web content solutions across the enterprise. Addresses the common questions that all small, medium and large enterprises encounter as they grow. Softcover.
$8.90 
Web Content Management: A Collaborative Approach
Related Posts:
Well written book by one of the pioneers – good for technophiles as much as “technophobes”. Can’t wait for his next venture (Global Advantage)…
Rating: 5 / 5
If you believe that Interwoven’s software is the way to go, then read this book. Otherwise, save your money and look elsewhere.
Rating: 1 / 5
This book is based on the sloppy assumption that a website is somehow different from some other type of software project, that there are rules and methods that distinguish web pages from code. Thats false. Follow time-tested methods for revisioning and releasing software (which includes analogues for staging and releasing) and you will have a better understanding of release management.
Better yet, let me boil it down for you since I have spent six years engineering at the world’s busiest website:
1. Keep all html in a source-control system like SourceSafe or CVS.
2. Back this system up to tape periodically.
3. Allow users some sort of access to make changes to these files and commit the changes if and only if the resulting edits maintain the well-formedness constraints for the page (use any of the free HTML checkers for this). If you use a dynamic templating system, make sure your constraints bear this in mind.
4. Use your web servers configuration files to allow your production servers to also provide staging areas via different URLs. Use the staging area to check pages visually. These staging URLs can be blocked from outside view.
5. Use scripted release mechanisms to push your content out to multiple machines. Never host your content on one machine.
6. As long as you set up some simple constraints for your pages and enforce them through the edit and release cycle, you are good to go.
7. If you need more information, read about software revisioning.
Thats it!
Rating: 1 / 5
This book can commonly be found used for [a low cost ]. I think that says a lot.
Coming from an editorial and project management background, I found this book to be worthless. It’s terribly written, the topics are covered in a very general way, and it ignores important topics such as information modeling.
A much better book on the subject is “Managing Enterprise Content: A Unified Content Strategy” by Ann Rockley. However, Rockley’s book goes beyond Web content management to include all forms of enterprise content (print, etc.). I plan to read Boiko’s “Content Management Bible” next, which I hope will answer some of the questions I still have.
Rating: 1 / 5
I donot like the style of this book. Same story or same meaning was told again and again. Anybody who wants to work for a big/medium website (targetd audience of this book) would definitely understand what is the problem. But the book doesnot clearly mention the solution to the key points or any very very interesting stuff. In fact only the summary of each chapter is the best part and worthy of reading. I regret buying this book.
Rating: 2 / 5