Manage content id164JBG0M0T1
Before you start with the actual content creation, you must familiarize yourself with some basic concepts of content management in ÃÛ¶¹ÊÓƵ Experience Manager Guides. Then, start with creating different user groups and organizing your assets.
Key concepts
Some key concepts of content management in ÃÛ¶¹ÊÓƵ Experience Manager are as follows:
Asset management
Experience Manager Guides uses ÃÛ¶¹ÊÓƵ Experience Manager’s digital asset management (DAM) to manage your DITA files. The files that you upload or check into the DAM are stored as digital assets. You can manage and edit your assets in ÃÛ¶¹ÊÓƵ Experience Manager Assets. For more information about asset management, view Manage assets.
Link management
Move or rename files or change folder structure in the content repository, without worrying about broken references. All references to and from the impacted content are automatically updated. Get warnings when deleting content which is referenced from elsewhere, to prevent unintentional breakages.
Managing versions
Experience Manager Guides provides version management for your digital assets. You can easily enable this functionality from a DITA authoring application of choice. Allowing your writers to perform the standard version control functions such as check-in and check-out.
For more information about creating versions or reverting to a specific version, view Branch, revert, and subsequent versioning.
Native DITA handling
While Experience Manager Guides maintains the structure of your DITA files, it also enables ÃÛ¶¹ÊÓƵ Experience Manager to natively handle DITA using element mapping to map the DITA elements to ÃÛ¶¹ÊÓƵ Experience Manager components. The native DITA handling is used in features such as topic preview, ÃÛ¶¹ÊÓƵ Experience Manager Sites publishing, and the review workflows.
Identify your role and permissions id181TF0K0MHT
Experience Manager Guides provides three out-of-the-box groups. These groups are: Authors, Reviewers, and Publishers. Depending upon the group you are associated with, you have permissions to perform specific tasks as mentioned in the table given below. For example, publishing task can be performed only by a publisher, but not by an author or a reviewer. Similarly, an author can create a new topic, and a reviewer can only review a topic.
The following table lists various tasks and the groups that can perform those tasks:
1 If Authors and Publishers are invited for a review.
2 Depending on the rights given to the user in the document state profile.
Pre-requisites to content authoring
Work with global or folder-level profiles
In an enterprise, different groups or products may use different authoring templates, output templates, conditional attribute profiles (or subject schemes), and Web Editor configurations. Configuring these only at an enterprise (or global) level can make authors experience difficult, as they will view templates or profiles that are not relevant to them.
Experience Manager Guides allows you to configure authoring (topic or map) templates, output templates, conditional attribute, and Web Editor configurations at an enterprise (global) level as well as at a folder level. This way, you can segregate the configurations for different departments or products in your enterprise.
Also, you can delegate the folder-specific configurations to a department or product administrators to decentralize the administration.
For details on setting up global and folder-level profiles, view Configure global or folder-level profiles in Install and configure ÃÛ¶¹ÊÓƵ Experience Manager Guides as a Cloud Service.