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

Creating a Docker container for a NodeJs application: Express + Mongo + Docker Compose

This is a Docker tutorial for creating a NodeJs container using expressjs and mongoose, above is the vid and below you will find the steps followed.
StepsPre-reqsHave node.js installedAnd docker installed (make sure you have docker-compose as well)Create an simple node app using expressjs and mongooseModify your container and create a docker-compose fileBuild and Run your new container Create your simple node appInitialize the node appnpm initInstall the dependencies for our appnpm install --save express mongoose Create the database.jsCreate the index.js Create a dockerfileInclude container with node preinstalled: FROM nodeCreate default/working directory: WORKDIR /usr/src/appCopy package.json to workdir and install dependencies (which we will need in this case😊): COPY package.json .RUN npm install Copy the rest of the app (just the index.js file in this case)COPY . .Expose the port required for reaching our expressjs appEXPOSE 3000Add a command to run when this container is star…

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.
StepsPre-reqsHave node.js installedAnd docker installed (make sure you have docker-compose as well)Create a container for defining configurations for a mongo instanceCreate a container for setting up the replica setCreate 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 setBuild, 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 mongoCreate default/working directory: WORKDIR /usr/src/configsCopy mongo's configurations file into the container

How to organize your clientlibs JavaScript files by Integrating Adobe Experience Manager and System.Js

Some simple steps to organize your clientlibs javascript files using System.js

Repository with the final code
Pre-requisitesAn Adobe Experience Manager (AEM) InstanceJava  MavenSystemJs Creating the appAEM project archetypeCreating your first Adobe Experience Manager 6.2 Project using Adobe Maven Archetype 10Assuming you that have maven in the path, if not change "mvn" to for example "c:\program files\maven3.3.9\bin\mvn"
mvn archetype:generate -DarchetypeGroupId=com.adobe.granite.archetypes -DarchetypeArtifactId=aem-project-archetype -DarchetypeVersion=10 -DarchetypeRepository= -DgroupId=AEM62App -DartifactId=echo62 -Dversion=0.1.0-SNAPSHOT -DappsFolderName=AEM62App -DartifactName=AEM62App -DcomponentGroupName=AEM62 -DcontentFolderName=AEM62App -DcssId=AEM62CSS -DpackageGroup=AEM62App  -DsiteName=AEM62App Add the import-package element with javax.inject;version=0.0.0,* inside the instruc…