I Want Context!

I think we have all been there. I know I have certainly asked people to review and comment on a few topics og content components, only to be confronted with the fact that context is needed. Well, even though I have been working with components  for more than 15 years…to be honest, I have been doing updates of components myself and realized that I need more context to do a proper job. And sometimes it is bit of a clunky process to open or preview one component at a time from a map editor. So this has left me with two choices: I can provide the full document on the side, and ask the reviewer to update the componente while getting the context from the full document.Or I can provide the full document, and tell the reviewer to forget about the components. I’ll just ask the reviewer to write comments and amend the full document.  None of these solutions are ideal. If I go with the first solution, the reviewer will have to jump back and forth between the component and the full document. That will be a pain for the reviewer. If I go with the second solution I am left with the job of having to update the components myself when I receive the full document from the review including comments and changes. This is time consuming and prone to error. Fortunately, this problem is nolonger there. Now there is a third option. Now I can actually provide the reviewer with a full Word document for commenting and updating, and I can automate the process of getting...