Ön a következő verzió súgóját látja::
- 6.3
- 6.2
- Korábbi verziók
Adobe Experience Manager 6.2 includes the classic and touch-optimized UI. Customers have to make the decision about which to use during the project implementation, or when updating from an earlier release.
This document is intended to help with finding the right choice. It will be updated as new updates and best practices become available.
Terms of interest:
- Classic UI
User interface based on ExtJS technology that was introduced with CQ 5.1 in 2008. - Touch-optimized UI
New(er) user interface that was introduced in 5.6.0 as a technology preview and extended in subsequent releases. It is based on the unified user experience for the Adobe Marketing Cloud. - Site Admin
Capabilities to manage the site hierarchy (move, activate, managed references) and create new pages. - Page Authoring
Capabilities to add/edit the content of a page. - DAM/Assets Admin
Capabilities to manage digital assets (including images, video, documents, downloads). - Client Context
Capabilities to aggregate information about the visitor and use it for various purposes. Provides an user interface to simulate persons visiting the site. Starting AEM 6.2, ContextHub is replacing the Client Context.
Adobe has updated all the Adobe Marketing Cloud solutions with a touch-optimized user interface. Users across the Marketing Cloud solutions (that includes Adobe Experience Manager) enjoy an unified experiences and common patterns on how to use and operate the applications.
The original user interface for Adobe Experience Manager (previously known as CQ5), introduced in 2008 and used by all customers running versions 5.0-5.6.1, is present in 6.2. This guarantees that customers can update to 6.2, and benefit from an updated platform with new capabilities while using the same user interface.
Adobe recommends customers to plan to switch to the touch-optimized UI in 2016/17. This can be done during an update to 6.2 - or in a separate projects after the update, that would include the necessary adjustments to the customizations and component dialogs.
Customers running 6.2 will benefit from full production support using the classic user interface.
The following is a list of recommendations from Product Management for Adobe Experience Manager 6.2:
| My project... | Recommendations |
|---|---|
| Is just starting to use Adobe Experience Manager. | Use the touch-optimized UI per default for all users. Be aware that limited admin and configuration tasks still need the classic UI. In future AEM updates these will be done in the touch-optimized UI. See list below of available updates. |
Has used AEM for a while. Has used the product UI out-of-the-box and developed custom components for the sites. |
Then, in a second phase:
|
| Has built a site that uses the ClientContext with integrations. |
Then, in a second phase:
|
Has used CQ/AEM for many years. Has extended the product UI (e.g Site Admin) and built components with extensive edit dialogs. |
Update to 6.2 and configure the classic UI as the default for page authoring for all users. See Selecting Your UI. Then start a project to apply customization and optimize component dialogs for the touch-optimized UI. See Resources to Help. |
| Uses Microsoft Internet Explorer 9 as default browser (without alternative browser). | Update to 6.2 and configure the classic UI as the default for all users. The touch-optimized UI requires Internet Explorer 11 or newer. |
See the Knowledge Base article, Touch UI Authoring FAQ, for details; including any information about the deprecation schedule for the classic UI.
See Selecting Your UI for information about configuring your system as required.
For details of the enhancements made to the touch-optimized UI in the AEM 6.2 see What's New in the Release Notes.
A complete overview see the Touch UI Feature Status page
For background information on basic handling:
For detailed development information:
- Touch-optimized UI architecture.
- Use the Dialog Conversion tool to convert component Edit dialogs from the classic UI to the touch-optimized UI.
- Structure of the touch-optimized UI.
- Customizing the consoles in the touch-optimized UI (includes sample code).
- Customizing page authoring in the touch-optimized UI (includes sample code).
- AEM Gem Session on touch-optimized customization.
- Granite UI documentation.
A Twitter™ és Facebook közzétételeket a Creative Commons jogi feltételei nem szabályozzák.