The next big step: Content mapping
All the research and conceptual design we’ve talked about so far has been focused on a top-down approach to defining a structure that will accommodate your business mission, users, and content. Now, moving into production, you step into the bottom-up phase. Content mapping is where top-down meets bottom-up.
In content mapping, you separate all your content from its existing containers, breaking it down into logical ‘chunks’ that merit or require individual consideration. As you’ll have learned in the content inventory, your content comes from a wide variety of sources and is in a multitude of formats. All this content must now be mapped onto the information architecture. Separating content from containers is essential, because it allows it to be used across multiple pages.
To define your content ‘chunks, ask these questions:
- Can this document be segmented into multiple chunks that users might want to access separately?
- What is the smallest section of content that needs to be individually indexed within the particular solution you are implementing?
- Will this content need to be repurposed across multiple solutions or as part of multiple processes?
Once you have your chunks, it’s relatively simple to map them onto your solutions.