Content management
- Managing configuration
Web site elements may require custom configuration, for example an API key for an external service or a date format to use when rendering dates. Configuration is centrally managed and published from the Content Manager so that Web applications do not require site-by-site manual configuration on localization. - Creating Folder structure in Content Manager
A custom module implements a distinct piece of functionality that is only relevant to some implementations. When you want to add a module to SDL Digital Experience Accelerator, create the following Module Folder structure in Content Manager. - Creating Content Manager items
Schemas, Component Templates, and Components are the Tridion representations of elements that appear on your Web site Pages. Create these Content Manager Items to enable Editors to manage the Web site element from within the Content Manager. - Managing resources
Resources are snippets of content reused across a Web site. Manage these bits of text as custom resources that you can edited and translate in the Content Manager. - Managing page includes
Includes are common elements that appear across the whole Web site. These elements are not managed on the Page directly but via Page Includes. The Page Template Page Template Metadata Schema is used to define which includes are shown on which page layouts. - Refreshing Web application settings
Most Web application configuration and resources are managed and published from the Content Manager to avoid custom configuration in the Web application configuration files and allow you to update configuration centrally without having access to the Web application servers. If you have changed a configuration or resource setting, republish the Publish Settings page. - Creating new Web site layouts
SDL Digital Experience Accelerator comes with a set of Page Layouts and Region Layouts which allow you to build a variety of Pages. It is likely, however, that you will need to create your own page and/or region layouts to provide additional options for your editors when creating pages for the Web sites. - Reusing Views
Regions allow editors to determine where on a page a piece of content is shown and with what column layout. When you have created a View and Component Template, you can simply create new templates which reuse the same view but in a different region and using a different layout. - Specifying semantics on Schemas
You can map existing Schemas to existing View Models without changing the View Model semantics by applying Semantic annotations on the Schema and Schema fields.