Content Manager implementation
Content Manager features encompass the Content Manager items you need to create and secure so that end-users can create, assemble, and publish content.
- Publications
Publications, the main organizational units in Content Manager, group content and layout items that represent the building blocks of a Web site. A Publication's organizational structure and security model let you create and organize content. You can create a hierarchy of Publications, a BluePrint, in which Publications share content. - Setting up Site Types for the Site Wizard
Set up the Site Wizard to enable users to create a new site quickly without having to run PowerShell scripts. In the Site Wizard, users combine one BluePrint Publication (the Site Type) with another BluePrint Publication (the Content Publication). You need to map each Site Type to a Web application on the delivery side. - BluePrinting
A BluePrint is a hierarchy of Publications in which Parent Publications share content to Child Publications. Child Publications can contain: shared content from a Parent Publication, localized content, and local content. - Schemas
Schemas define the structure of content and metadata. - Metadata
Metadata is data about data. You can use metadata, for example, to enhance Web site indexing or enable Users to change the behavior of templates without having to modify template code. - Categories and Keywords
Categories and Keywords define taxonomies which are used to classify content (list values in Components and metadata): a Category is a general classification defining the root of a taxonomy and a Keyword defines a value within the taxonomy hierarchy. - Virtual Folders
A Virtual Folder is an item that can contain different types of content items located in different locations in Content Manager. - Bundles
Bundles are containers for items in different locations for collective workflow processing or other collective use. End users can work with Bundles in the Content Manager Explorer user interface, but you can also work with Bundles programmatically using the Core Service or the TOM.NET API. - Workflow
Implement Workflow to apply workflow to the creation and use of Components, Templates, and Pages. Workflow is the movement of tasks through a work process. Workflow ensures that specific individuals perform activities in a specific sequence. - Configuring the SDL Web user interfaces
You can configured the contents of the Sites slide-out navigation screen, accessible from both Content Manager Explorer and Experience Manager. You can also add Custom Pages to SDL Web. Beyond these basic changes, you can also extend the user interfaces. - Purging and reindexing data
SDL Web exposes a number of Windows PowerShell commands for purging or reindexing data in the Content Manager database. Use these commands to maintain your search index, and to prevent your Content Manager database from filling up. - Users and Groups
In the Content Manager, you create Users and User Groups. Then you grant them access to the items and actions they need to perform by setting rights and permissions. - Business Process Types
A Business Process Type is a collection of configuration settings describing how your organization works with its content, both before it is published and when it is published. Business Process Types reside in a Publication. Any Publication can contain multiple Business Process Types, but a publishable Publication must select exactly one of those Business Process Types to use. Not only that, in most scenarios, the publishable Publications in a BluePrint structure all have the same Business Process Type. So if your Content Manager instance contains only one BluePrint structure (as is typically the case), it will typically have only one Business Process Type altogether. - Content configuration
System administrators can define system fonts, Multimedia Types, and Format Area configurations for use in all Content Manager Publications. - Device Preview
- Safeguard
Safeguard is a product that integrates various SDL products with ActiveStandards™. Before you can use Safeguard, Safeguard needs to have been set up for you by a Safeguard team including, for example, a compliance profile for your company. You then need the account and API key information to configure Safeguard for SDL Web.