Ir al contenido principal

Adobe Experience Manager version Differences: Touch UI

In this post I would like to point out some of the differences in the touch UI in terms of some of the most used features and where to find them for AEM 6.0, 6.1, 6.2 and 6.3.  I will focus mostly on where things like the Sites, Assets and CRXDELite consoles are located and some other options within some menus or authoring modes.

Main Menu

  • Access to the Classic UI welcome page clicking on the little monitor icon when you hover over the projects item.  For AEM 6.3 the icon is no longer there, but, you can still reach the classic UI by going to http://localhost:4502/libs/cq/core/content/welcome.html
  • Sites Console
  • Assets Console
  • Tools Submenu (For aem 6.2+ it is the hammer Icon)

Tools Menu

  • CRXDE Lite
  • In order to reach the Package Manager you will have to click on Operations for AEM 6.0/6.1 and on Deployment for AEM 6.2/6.3


  • For AEM 6.0/6.1 you will have to click on the Packaging item before you reach the package manager
  • For AEM 6.2/6.3 you will have to first click on the Deployment item on the left
  • Packages (Package manager console)

Edit page

When you are on the sites console
  • For AEM 6.0/6.1 Hover  over a page and then click on the pencil Icon to edit the page
  • For AEM 6.2/6.3 Click on the little thumbnail to the left of the page Name ("English" in this case) and then on edit at the top of the page

Author page

  • Options to Publish or Unpublish pages
  • Page properties
  • Open Classic UI.  AEM 6.3 seems to lack this option, to go into the classic UI just replace "/editor.html" with "/cf#" in the URL

Authoring modes

  • Edit (Pencil Icon for AEM 6.0)
  • Preview, for AEM 6.1+ it should be at the same level as the edit mode (Eye Icon for AEM 6.0)
  • Design. AEM 6.0 lacks this mode for the Touch UI, you will have to change first into the classic UI and make your changes there.


Entradas populares de este blog

Create a custom AEM workflow process step with a dialog

In this tutorial I talk about how to create a custom workflow step process with an additional dialog for configuring it, above is the vid and below you will find some useful notes. 1. Pre-reqs Have access to an Adobe Experience Manager instance. Have Maven installed, understand how it works and also understand how to use Adobe's archetype, you can watch my video about maven here: Creating an AEM application using Maven and Adobe's archetype 2. What is an AEM Workflow and workflow model Workflows allow you to automate different tasks inside AEM by defining a s

Creating Docker containers for Adobe Experience Manager

This is a Docker tutorial for creating a docker image for the Galen framework, above is the vid and below you will find some of the steps followed. Adobe experience manager is a content management system which in a nutshell is an application that allows us to create web sites to be consumed by end users. You might be familiar with other such applications like wordpress or drupal which serves the same purpose A typical deployment would be comprised of two AEM instances, the author instance used for creating and modifying content, the publish instance which serves the content and finally we have a dispatcher which is a static web server used for caching, load balancing and some security purposes. We can configure an AEM instance to work as an author or publish instance by either changing the file name

Creating a Mongo replicaset using docker: Mongo replicaset + Nodejs + Docker Compose

This is a Docker tutorial for creating a Mongo replica set using docker compose and also a couple more containers to experiment with the replica set, above is the vid and below you will find some of the steps followed. Steps Pre-reqs Have node.js installed And docker installed (make sure you have docker-compose as well) Create a container for defining configurations for a mongo instance Create a container for setting up the replica set Create a simple node app using expressjs and mongoose (A modified version from the previous video ) Create a docker-compose file with the mongo and setup containers and two additional containers for experimenting with the replica set Build, Run and experiment with your new containers Create a dockerfile for the first mongo container (not really needed but you could configure more stuff if needed) Include container with mongo preinstalled:  FROM mongo Create default/working directory:  WORKDIR /usr/src/configs Copy mongo