Real World Content Modeling: A Field Guide to CMS Features and Architecture

Real World Content Modeling: A Field Guide to CMS Features and Architecture

<p>Too often, content models are developed with no consideration of the system in which they have to operate. This book is an examination of how content actually gets modeled inside a CMS -- what features and architectures are available to translate a theoretical domain model into something that a CMS can manage. If you're looking for a CMS, what features should you look for? Does your current CMS measure up to the state of the market? What is possible in content modeling at this point in the industry?</p><p><b>Table of Contents</b></h2><ul><li>Introduction</li><li>About this Guide</li><li>How a CMS Helps (Or Hinders) Your Content Model</li><li>The Anatomy of a Content Model</li><li>Eval #1: What is the built-in content model?</li><li>Timeout: What's the difference between built-in and custom?</li><li>Eval #2: Can the built-in model be extended with custom content types?</li><li>Timeout: Opinionated Software</li><li>Eval #3: What built-in attribute types are available?</li><li>Timeout: How Content Is Stored</li><li>Eval #4: How is content represented in the API?</li><li>Eval #5: How can attribute values be validated?</li><li>Eval #6: How is the model supported in the editorial interface?</li><li>Eval #7: Can an attribute value be a reference to another object?</li><li>Timeout: Let's Evaluate the Current Level of Functionality</li><li>Eval #8: Can an attribute value be an embedded content object?</li><li>Eval #9: Can custom validation rules be built?</li><li>Eval #10: Can custom attribute types be created?</li><li>Eval #11: Can attribute values repeat?</li><li>Eval #12: Can types be formed through inheritance or composition?</li><li>Eval #13: Can content objects be organized into a hierarchy?</li><li>Eval #14: Can content objects inherit from other content objects?</li><li>Eval #15: What is the relationship between "pages" and "content"?</li><li>Eval #16: Can access to types and attributes be limited by user permissions?</li><li>Eval #17: How can rich text fields be structured?</li><li>Eval #18: What options are available for dynamic page composition?</li><li>Eval #19: What aggregation structures are available to organize content?</li><li>Timeout: What Is and Isn't Considered "Content"?</li><li>Eval #20: How can types be changed after object creation?</li><li>Eval #21: How does the system model file assets?</li><li>Eval #22: By what method is the content model actually defined?</li><li>Eval #23: How does the system's API support the model?</li><li>Conclusion</li><li>Postscript: Thoughts on Model Interoperability</li><li>About the Author</li></ul>