Content Organization Strategies
Organizing files in your content library in a consistent way makes it easier, to manage find, and reuse content.
Content Library Overview
Heretto CCMS enables you to browse, filter, create, upload, and manage files and folders in the content library.
Content Library Structure
Category-Based Folder Structure
- Category_A (for example, “Installation and Configuration”)
- Category_B (for example, “Troubleshooting”)
- Category_C (for example, “Integrations”)
- Category_A (for example, “API”)
- Category_B (for example, “Deployment_Models”)
- Category_C (for example, “Feature_Flags”)
Asset-Based Folder Structure
The following is a sample folder structure that distributes files based on their association with an asset (for example, a guide or a course).
- Contains global reusable content, including: content
warehouse topics, variable warehouse topics, and DITAVALs.
For more information, see Conditional Processing Strategies.
- Contains internal business-related information divided into several subfolders that correspond to different departments.
- Contains customer-facing technical documentation and learning content divided into subfolders.
- Internal technical documentation and learning content divided into subfolders.
- Contains files that are being developed.
- Contains multimedia files like screenshots, GIFs, or diagrams.
Content Organization Guidelines
Keep the following guidelines in mind when creating a folder structure in the content library:
- To avoid cluttering your production branches and search results, keep any sandbox or testing content on a separate branch.
- To display a folder at the top of the folder tree, add an underscore “_” before the
For example: _Shared or _Media.
- Depending on the architecture of content that you develop, you can create more
_Shared folders on lower levels.
For example, there may be a separate _Shared folder for documentation and business.
- Depending on the architecture of content that you develop, you can keep _Media folders on higher or lower levels. Keeping _Media folders on low levels may hinder reuse.