In the first installment of our series on intelligent content management we explored methods for developing an effective content strategy. In the second installment, we’ll focus on content modeling.
The main component of intelligent content management is the content model. A content model defines the type of content you create, how to structure that content, and how to create metadata to associate with the content.
We call this an “intelligent content model,” and when you build your content model following this structured approach, you create content that is reusable across channels. With an intelligent content model, a single piece of content can be used in many different formats and publishing channels – including your website, a mobile app, a web application, a chatbot and more.
Defining Content Types
To create an intelligent (or structured) content model, you start by defining content types such as an article, image, news story, press release, knowledge base article, and so on.
Next, for each content type you define a set of elements, also called attributes, such as title, description, summary, media file (image, video), author, main body. You also define the format of that element (date, text – 50 characters, number, image, etc.). The number of elements you have will depend on the content type and how you envision using it across the organization. The key to creating structure is to break down the content into its key elements, but you don’t necessarily want to break it down into too many discrete elements that you will not use.
For example, when you create a press release content type, you might define elements including title, subtitle, summary, main body, etc. You wouldn’t need to go further by breaking down the “main body” into separate elements for each paragraph because you wouldn’t use the individual paragraphs. However, you might want to create a separate element for a quote so that you can use it for different purposes.
Deciding how to break down a content type into its elements depends on two primary factors: how you want to layout the content in different channels and how you want to reuse the content in different channels.
After you define the content type elements, you then define the metadata associated with each content type.
Metadata are content type elements that you don’t see and include things like Create Date, Publish Date, SEO description, author. Metadata comes in several flavors:
- Descriptive Metadata: title, abstract, author, keywords
- Administrative Metadata: date created, file type, access/permissions
- Structural Metadata: version, relationship to other content types
Once you have defined all your content types, you need to define the relationships between content types. For example, the Content Type, Author, is related to the Author element in the New Article content type.
Using a Content Model with Your CMS
Every content management system supports a different approach to creating content, but only a few support a structured, intelligent content model. Ingeniux CMS is a solution that supports this unique and powerful model.
Here’s how you would use a Content Model with Ingeniux CMS:
Once you have your model defined, you can set it up in the CMS using the Schema Designer. Without a schema designer like the one in Ingenux, you may be required to modify your content model to fit the capabilities of the CMS.
The Schema Designer creates XML schemas that are then natively available as XML or JSON. It supports over 25 standard element types, such as Text (string), XHTML (WYSIWYG editing), image, media file, database query, navigation, etc. The Schema Designer allows content models to change and web administrators to selectively update existing content with those changes through versioning as well as syncing and replication to propagate changes across existing content items.
You have your Content Strategy defined and your Content Model created. Next, we’ll look at storing content in your intelligent content management system.
Subscribe to the Ingeniux blog for the latest in web experience management.