Content Model
A conceptual term for the collection of content types, attributes, relationships and datatypes in place to accurate describe a logical domain of content.
Content types are modeled in two ways:
- Discrete: the self-contained internal structure of that type
- Relational: how an object of the type relates to other objects and types
“Content modeling”, as a verb phrase, describes the process of defining the content model.
The content model might be a formal document, but it usually just refers to the known collection of configuration or code in a CMS that establishes the types, attributes, datatypes, and relationships available.
The term structured content generally means content which has been designed and internally organized according to the rules of a content model. Content without such structure is referred to as unstructured content.
Related Chapter Sections:
-
Defining the Content Model
Chapter 11: Model Your Content
So, what exactly IS a content model? Before we begin planning a content model, let's take some time to define it.
-
Inputs and Outputs
Chapter 11: Model Your Content
Inputs and outputs for Chapter 11: Model Your Content.
-
Implementing the Content Model
Chapter 11: Model Your Content
And now, let's make the content model REAL. Let's build it within the structure of the content management system.
-
Model Implementation
Chapter 20: Implement the Back-End Functionality
Remember that content model you created? It's time to convert that model into something your CMS can manage.
-
Planning the Content Model
Chapter 11: Model Your Content
A content model is all about connecting objects and defining fields. Here, we'll start looking at what that means for you content and your system.
-
Writing for Accessibility
Chapter 12: Write for People and Machines
Writing for accessibility – much like writing for search engine optimization – boils down to writing clear, scannable, well-structured content.
-
The Functional Question
Chapter 21: Migrate and Populate the Content
How will functional or logical aspects of the content work in the new CMS?
-
Inputs and Outputs
Chapter 13: Develop the Graphic and Interface Design
Inputs and outputs for Chapter 13: Develop the Graphic and Interface Design.
-
Inputs and Outputs
Chapter 10: Organize Your Content
Inputs and outputs for Chapter 10: Organize Your Content.
-
Inputs and Outputs
Chapter 16: Select a Content Management System
Inputs and outputs for Chapter 16: Select a Content Management System.
-
Writing for Machines
Chapter 12: Write for People and Machines
Finally, there's one audience you can never please — because they care only for data: search engines and screen readers.
-
What is Design?
Chapter 13: Develop the Graphic and Interface Design
Design covers a lot of ground. So what do we mean when we talk about design for your web project?
-
Beyond Google Analytics: Other Ways to Measure
Chapter 8: Gather Insight From Your Metrics
It's not all about clicks and views — you may want to better understand how users interact with language, and where specific terms rank within the larger picture.
-
Aggregations
Chapter 20: Implement the Back-End Functionality
Content objects don’t exist in a vacuum. They usually have to be organized into larger structures — feeds, directories, listings — in order to provide some value. Here's where we talk about those aggregations.
-
Other Development Tasks
Chapter 20: Implement the Back-End Functionality
Beyond the main back-end development tasks there's quite a few other details to be handled.
-
The Editorial Question
Chapter 21: Migrate and Populate the Content
What content is moving, and how does it need to change on the way over?
-
Navigation
Chapter 10: Organize Your Content
Like a well-worn map, site navigation should balance familiarity with discovery.
