Go live with the content model

Ensure the right division

1. Group content elements based on their purpose

In your content model diagram, go through each content type once more and group elements that are related together into content groups. Content groups make it easier for content creators because of two main reasons:

• They can focus on related elements only. If they’re writing, they can see only the main content. If they’re filling in metadata, they see metadata only. Avoid forcing your users to scroll under the main content that has a different length in each content item.
• Let people in a given role in the project focus on relevant elements only. With content groups, you can set different permissions to different parts of content items so that authorized people can only make changes where they have access.

2. Crumble content into smaller pieces

In coffee, the smallest assembly pieces are coffee grounds. In insurance, they can be insurance parameters. In content modeling, the smallest reusable pieces are chunks. Chunks are another content type that holds a piece of content that’s reused in multiple places. If you reuse content or find an embedded set of elements with a strong intent (for example, CTAs, tasks, steps, diagrams, infographics, or quotes), chunk it.

1. Create a content type, for example, named Chunk.
2. If you set limitations to different elements, typically in rich text, ensure that Chunk is allowed.

Then, when you create content that will be reused or when you want to copy and paste content from an existing content item:

1. Create a chunk instead – a content item based on the Chunk content type.
2. Create the content in the chunk.
3. Link both target content items to the chunk.

However, try to keep 2–3 levels of content nesting (for chunks and content items) at most. More levels lead to losing the context when going through a content item.

Stay relevant

3. Verify your content model responds to your needs

Once you create the first iteration of your model, take a step back and check if the content model addresses your requirements. Both re-platforming and new implementations usually come with a checklist of pain points or requirements. Double-check if the new model is addressing them. Use a spreadsheet to list:

• Requirements
• Pain points
• Internal and external stakeholder needs
• Usability
• Support of the customer journeys

Then, map your content types (or even content items) to them. This way, you can keep track of how, for example, your metadata can help you support your customer journeys. Remove everything non-essential.

4. Ensure your content model won’t become a burden

As needs change over time, scheduling yearly content audits and reviews of the content model is important. Audits prevent content to ROT (to become redundant, outdated, and full of trivial content), which is essential so that you don’t need to repeat the whole process from the beginning, and the model still brings you the most significant value possible.

What’s next?