This book provides a clear, unbiased overview of the entire web content management ecosystem, from platforms to implementations, without needing deeply technical knowledge. The information in "Web Content Management" will give you a foundation of understanding necessary to make better decisions about platforms, features, architectures, and implementation methods to ensure your project solves the right problems and positions your organizations for future success.
Are you trying to understand web content management without having to understand programming? Are you a project manager who wants to know how to manage an effective web content management implementation? Are you trying to select a CMS but are confused about the promises, terminology, and buzzwords? This book will help.Learn about what particular features of a website make CMS implementations expensive and how to measure riskEvaluate key questions relevant to platform and architectureUnderstand when to use pre-built CMS vs. building one in-house, as well as SaaS platforms vs. installed platforms
Very good book for individuals who deal with content management systems. I approached it from the perspective of a product manager, but I think this would be helpful for anyone in the cross functional team.
My only critique is that I think it could potentially be organized a little better BUT.. that's just being very critical. I would highly recommend this book to anyone in the field.
I sought this author in my local public library system after reading and appreciating a (now forgotten/lost) comment (possibly a blog or blog comment). This was a good choice.
I appreciated the thoroughness of this book. It explains concepts and offers a few examples of how the concepts get applied.
This book has thorough CMS insights from the perspective of editors, developers, and everyone in between. I don't understand everything yet, but it's kind of my jam.
My odyssey into data (and info) world continues. Content Management is another one of those terms I've gotten used to, but not in depth. I am glad I decided to dig in a little.
Obvious, yet my most profound take away is: Content is created through an editorial process. I always thought CMS as relational DB for text - so wrong. To heighten customer engagement, personalized web content is a popular pursuit. Now I have better appreciation of the complexity introduced to CMS (e.g., how to QA every personalized variation) and org (i.e., write and model personalized content variations). Throw in 3rd party contents and multi-channel, most companies would not have sufficient editorial capability. Throw in cognitive capabilities, CMS becomes even more interesting - another topic to dig into soon.
I didn't really learn much, although that might just be because the "field" of web content management systems isn't what I had hoped it would be. "Content" is a very broad category, and saying "software for putting content on the web" is similarly broad.