What is content modelling

Content modelling is a process of exploring and defining how content types can be chunked and linked to add value to customers and businesses.

In math terms:
Chunked content + business rules = customer and business value

For example, if a recipe (content type) is chunked to include availability of ingredients at home, then the following scenario is not too far fetched:

I’m in a bus returning home one late evening thinking of what to make for dinner. I browse for recipes on my favourite recipe app and what I get is not any universal recipe list—it is list of only those recipes that I can actually make when I get home. How? The app checks with my refrigerator on the ingredients available and then filters the recipes to show only those I can make (or can make if I pick up a few missing ingredients).

Now that is value made possible by chunked content!

Benefits of content modelling

Content modelling has many benefits as shown below.

Benefit Description Example
Amplify infoseeking Allow for more granular and precise search Filter a recipe collection by ingredients
Widen distribution Offer third parties access to your data Offer access to recipe ingredients through an API
Improve usability Elegantly adapt the right content to the right device Have a different interface for browsing cooking instructions on a mobile device
Increase reusability Reuse a chunk from one collection in another collection Use the same baking instructions across recipes
Improve management Target improvements to specific chunks Just change the cooking instructions
Be future friendly Make your content ready for future devices Refrigerators and smart watches

The benefits are really about sweating your content to provide business value. Not all content needs to be modelled, but if there is something out there that can be modelled to enhance business value and it is not being done, then that is a sad waste of digital resources.

4 views of content models

Content models can be thought as having 4 views:

  1. Map
  2. List
  3. Table
  4. Authoring

The 4-view approach helps us think about content models both in a divergent way (map and list views) and a convergent way (table and authoring views).

1. Map view

The first step is to explore and map the content ecosystem you are interested in. An example is shown below. The boxes represent the selected content types and lines show the relationships between them. If you do this kind of ecosystem mapping you’ll see relationships you might not otherwise consider, such as the relationship between the ‘Supermarket’ and ‘Refrigerator’. Maybe my smart app can check with the refrigerator and tell me to pick up missing ingredients at the next supermarket (after checking the availability) on my journey home.

2. List view

Next, break up the content types into logical chunks. The chunking should be meaningful; it should add value. Don’t add a chunk just because it seems intuitive to do so. Always seek out the value. In the example below, the ‘recipe’ content type has chunks to account for ‘availability at home’ because we want our smart app to check the refrigerator at home before suggesting recipes.

3. Table view

It’s time to get into the details. The table view is all about individual chunks; it’s about metadata. In the table view, you’ll nail the technical specs that will make development easier. For example, what is the format of ‘cooking time’? What schema element will it follow? Where is the data going to come from? Is the field required or optional?

Item Definition Schema Source Type Field Required?
Name Name of recipe thing.name author text text yes
Description Short description of recipe thing.description author text textarea yes
... ... ... ... ... ... ...

4. Authoring view

Not all elements shown in the table view will be automatically populated; for example, chef’s tips need to be created by the author. In a large organisation there will be many authors responsible for content, so how do we make sure that they know how to create content that is correct and of a high quality?

The answer: creating a better authoring experience.

We need to take control of the authoring interface. In the sketch below, the examples and wordcount help authors create quality content within constraints. One can imagine having other things like video tutorials, non-examples, autosuggestion of categories etc. to help improve the quality of content.

Conclusion

Content models open up a whole new perspective on content design that cuts across devices and formats. There are many smart folks exploring this frontier already (see links below) and we hope that the 4-view approach gives people a simple way to approach this fascinating opportunity!

Resources