To use GatherContent for any white papers or eBooks you may be writing, you need to structure your project in a way that reflects the structure of your white paper or eBook. Hierarchy is the first step. You’ve probably got chapters, for example. You can create parent pages for those chapters and then you can create sub pages in GatherContent for any content within those chapters.

It’s also worth thinking about structures that repeat themselves. Maybe all of your introduction pages are the same. Or maybe you have key learning sections at the end of every chapter that are the same. You can easily create a Template for those repeating page types and use them as and when needed.

The benefit of this is that it makes sure your output is consistent with the same structure, guidelines, word counts and so forth. Once you have all of your Templates in GatherContent, you can then create all of the custom structures. You might do this as you go about writing your eBook or your publication because the structure can be quite organic with frequent changes and GatherContent allows you to be flexible with changing and updating your structure.

Further flexibility can be achieved by giving everyone involved in the project the ability to edit structures. That’s a Permission given to everyone so they can add new fields as needed such as image fields. This allows a flexibility that’s required.

Where possible assign someone to oversee all of this activity so that no damage is done to the overall and agreed structure.

Then you simply add your content as needed into each section and pass that through your designated workflow until it is ready for exporting or publishing.

Did this answer your question?