Experience Manager implementation
Implementing Experience Manager involves modifying your Templates to add controls to the published Web site that let users modify, move or add content, configuring the look and feel, configuring an administrative user or an alternative BluePrint structure, and extending the user interface with custom controls.
- Enabling inline editing and moving of Components
Enable inline editing to enable users to modify or move existing Components on a Web page. - Enabling editing for a set of Web pages
Enable editing on a Web page to make it possible to start an editing session on that page. - Enabling the adding of Components to the Web page
By default, all users can add Components to a Web page, either by selecting one that exists in Content Manager, or by creating a new one on the fly. You can configure various aspects of this functionality. - Enabling the creation of new Web pages
You can enable the creation of new Web pages by using any Page as a Page Type. Users can use such a Page Type as the basis for a new Page. Turning a Page into a Page Type requires administrator-level rights. - Making a linked Component editable
To make the fields of a linked Component embedded inside another Component editable, render the inner Component and surround it with aStart Component Presentationcommand in which bothIsQueryBasedandIsRepositoryPublishedare set totrue. - Marking regions on a Web page
By marking regions on a Web page, you make explicit to the User Interface which combinations of a Schema and a Component Template are allowed in such regions. This affects where new Component Presentations are added, and how users can move Component Presentations around on the Web page. - Using or creating thumbnail icons for Templates
You can upload thumbnail icons for a Page Template or Component Template. The user sees those icons when changing the Page Template or Component Template in the gallery displayed in the Layout tab of the ribbon toolbar. The icons are intended to help the user decide which Template to select, and should visualize what the published Web page or Component Presentation would look like. - Configuring an alternative BluePrint structure
Change your Page Templates to configure where Pages and Components are created or localized to accommodate a specific BluePrint structure. If you created the current Web site using the Site Wizard, the Wizard already gave you the opportunity to specify an alternative BluePrint structure. You must be an administrator-level user or a user with Publication Administration rights to perform this task. - Integrating the Experience Manager Web site extension with your Web site
If your Web site is dynamic in nature and uses MVC principles to assemble Web content on the fly, the standard installation instructions for the Experience Manager Web site extension may be insufficient to make Experience Manager publishing work. If so, create a custom integration. - Experience Manager security
Various Experience Manager tasks require a specific Content Manager security setting to perform. This topic explains which security settings are needed for which task. If a task is not listed here, it has no security limitations. - Guidelines for item naming
Give Content Manager items meaningful names, to help users predict what will happen when they select them from a list. - Changing border colors
Change border colors for all users in the slide-out navigation Settings screen to fit your organization's preference, or to make colors that stand out on your Web page. By default, the colors of borders around editable items are blue, green, red and grey. You must be an administrator-level user to perform this task. - Changing border width and padding
Change border width and padding for all users in the slide-out navigation Settings screen to fit your organization's preference. You must be an administrator-level user to perform this task. - Extending Experience Manager
To add custom controls and functionality to the user interface, extend the user interface in the same way as the Content Manager Explorer GUI, changing only the names of the view, toolbar, and context menu. - Inline editing command language reference
This section explains the command language for inline editing. These commands are HTML comments in the published Web page. - Disabling Preview
If you wish, you can disable Preview functionality for all users in the slide-out navigation Settings screen. If you disable Preview, modifications to the current Web page do not appear to users until the modified content has been published. You must be an administrator-level user to perform this task. - Configuring which binaries are displayed in Preview
By default, as a performance optimization, while in Preview mode, users only see binary files of the GIF, JPG/JPEG, PNG, CSS, or JS (JavaScript) types. To change this behavior, either set a maximum file size below which users should see all binary files, or change the file types that are always displayed, regardless of file size. You must be an administrator-level user to perform this task.