Ubiqus’ Translation connector to AEM

We @ExperienceLabs take great pride in announcing that Ubiqus now has their translator connector for AEM. It indeed is a matter of great satisfaction to us to be able to enable this synergistic ecosystem for Adobe, Ubiqus and ourselves.

To Adobe and the users of AEM, it enables the usage of services of a world class translation vendor. To Ubiqus, it opens up a whole new market in the form of AEM users subscribing to their translation services. And for us, it adds yet another feather in the hat of our great engineering talent @ExperienceLabs. To be able to seamlessly connect the AEM and Ubiqus translator via the northbound and southbound APIs, is yet another testimony to our subject matter expertise when it comes to translation services.

The entire project for was delivered using Agile methodology, through a series of well sequenced Sprints enabling most cost optimal and high quality deliverables for Ubiqus. The development comprised of two main phases – Basic features and Advanced Features. This enabled Ubiqus to incrementally add on features to the connector once a basic implementation was in place.  Each phase was delivered as a series of sprints with each sprint spanning 2 weeks. The basic features comprised the vanilla implementation of the connector with authentication capabilities, Ability to create a project in Ubiqus backend, Import of translated content for completed projects etc.  The Advanced features comprised Add-ons such as MT Workflows, Additional capabilities (Accept/Reject workflows, Scope), Submission to Adobe & getting it approved to be hosted on Adobe exchange etc.

Having successfully carried out the implementation of another connector with AEM, we firmly believe that each translation engine has got its own unique set of nuances to be taken care of and appropriately handled, when implementing the connector. Our engineering team equipped with this expertise, would be very keen to help you with any queries/implementation requirements that you may have for us!

We have evolved in response to Covid-19

Over the last several weeks, Covid-19 pandemic with its deep Global impact, has emerged as a very significant challenge that is causing disruption across the world. As the world responds to the outbreak of COVID-19, our thoughts are with the people affected and the medical professionals and first responders working around the clock to help those most in need. It indeed is quite heartening to see these professionals risking their own safety while selflessly working in the pursuit of a Covid-19 free world.

At Experience Labs, we continue to work closely with our partners, clients, employees and community organisations to rise to the occasion.

Backed by a strong Business Continuity Plan and Technology Infrastructure, we have been able to continue to delivery un-interrupted services to our esteemed clients. The transition of our employees from office to their homes, could only be made possible through the stupendous efforts from the Admin and IT Infrastructure teams who worked round the clock to ensure that all our employees were sufficiently enabled to be able to work from home. We deeply appreciate that working outside of office has been a paradigm shift for our employees as well. The HR team backed by strong sponsorship from our execs has ensured that this transition is as smooth as can possibly be, through various initiatives like Webinars (on Health and fitness, Ergonomics etc), Yoga sessions, counselling and parenting sessions etc. Initiatives taken by the finance team has ensured that the associates are adequately supported during these testing times. In addition, initiatives from Learning and training department has ensured that our employees make the most of this time saved in daily commute to learn something new and to build competencies in various domains and technologies. We thank all our employees, partners, clients for their great support and cooperation.

While we are still to understand the complete impact of the lockdown and the changes that it might trigger in terms of business and operating models, however, it gives us great satisfaction to have put our employee’s safety and well being at the top priority and at the same time providing them with the right ecosystem to prepare for the changes ahead. I would also like to assure all our clients, partners that we stand committed to your success and would be keen to hear from you if we could further help in any manner!

Adobe Marketing Summit

I am happy to share with you all that the ExperienceLabs team will be at Adobe Summit this year as well. We are looking forward to having face to face conversations with all of you at Las Vegas, from March 19-23.

For those of us who have been to the Summit, it is no secret that the Summit brings together the latest insights from the world’s leading digital marketing experts, marketing professionals and technologists. No wonder, the ever-evolving participation in the summit every passing year truly gets symbolized in the venue change from Salt Lake City until 2015 to Las Vegas in 2016. (Year 2016 saw 10000+ Marketers attend the summit)

In case you have never been to the Adobe Summit yet, and are considering it this time; I would encourage you to just go for it.It is only right to say that there is everything there for everyone:

Marketing experts – A great opportunity to better understand the insights made possible through the digital world and of-course to Socialize

Technologists – Sneak peek to the coolest technologies on the anvil and to benefit from the focussed training sessions.

Adobe Partners/System Integrators/Platform Development Partners – An understanding of the feature roadmaps, collaboration opportunities.

Add to it the distinguished hosts, keynote speakers, celebrities great food and the Summit Bash; you can look forward to a week long celebration of everything that the digital world has to offer.

If you are attending, just drop me an email <gaurav@experiencelabs.in> and I would like to have some face time with you. See you there @ the Summit!!

Content Fragments Templates

Today, I will focus on Content Fragment templates. This post is in continuation of the previous post, where I talked about new Content Fragment feature introduced in AEM 6.2. In order to understand Content Fragment templates, it is important you understand the basic structure and capabilities of Content Fragment. Please refer my previous blog post for the same: https://experiencelabs.wordpress.com/2016/10/29/content-fragments-an-introduction/

AEM 6.2 ships with a standard Content Fragment template. However, for you to use Content Fragments for your project, you will need to create a Content Fragment template. Before we go deeper into defining our own template, we will first look at the template that ships with AEM 6.2. The template name is “Simple Fragment” and it is defined in libs under this path: /libs/settings/dam/cfm/templates

Let’s browse this location in CRXDE. You will see the following structure:

+ <template-name>

– jcr:primaryType

– jcr:title

– jcr:description

– initialAssociatedContent

– precreateElements

– version

+ elements

– jcr:primaryType

+ <element-name>

– jcr:primaryType

– jcr:title

– defaultContent

– initialContentType

– name

… + other element definitions

+ variations

– jcr:primaryType

+ <variation-name>

– jcr:primaryType

– jcr:title

– jcr:description

– name

… + other variation definitions

The key elements of the template are:

  • Elements
    A list of elements that would define the structure of the the fragment. This field is mandatory and needs to have at least one child node for the “Main” element. For each element, we can define the bootstrap content (the default text) as well as a the content type. AEM 6.2 allows three content types out of the box (html, plain text and markdown)
  • Variations(optional)
    It defines the default variations for each Content Fragment. Please note, variations are defined at the Content Fragment level and this apply to all elements.
  • initialAssociatedContent (optional)
    A array of paths to LightBox collections, that would be associated by default with each Content Fragment.

Now, we will go ahead and create a template of our own. As you know, /libs is reserved for items that ship with the product. Hence, you should never write anything in /libs. All custom Content Fragments should be either defined in /apps or /config. Let’s look at these two options more carefully.

Apps: here is the complete path /apps/settings/dam/cfm/templates, it doesn’t exist, you will need to create it. Create Content Fragment templates here for overlaying out-of-the-box template (Simple Fragment) and creating general purpose templates.

Config: here is the complete path /conf/global/settings/dam/cfm/templates, it doesn’t exist and you will need to create this as well. Create Content Fragment templates here for instance-wide customer-specific templates that may be configured to be unavailable. Use this location for defining folder specific templates.

For the purposes of this blogpost, we will create a template under /apps.

Step by Step Instructions:

  1. Prepare basic structure under /apps
  • Open up CRXDE lite, and browse to /apps/settings
  • Create node of type cq:Page and name it dam
  • Select the newly created dam node and create another node of type cq:Page and name it cfm
  • Select newly created cfm node and create another node of type cq:Page and name it templates
  • Select the newly created templates node and once more create node of type cq:PageContent and name it jcr:content.
  • Now we need to specify that the templates in this location should be merged with those from /libs/settings/dam/cfm/templates. To do this, create a new boolean property under jcr:content named mergeList and set it’s value to true.
  • Select “Save All” to save the changes we have made so far. Here is a snapshot of the CRXDE lite, after you complete these steps.


  1. Create a shell Content Fragment Template
  • Browse to /libs/settings/dam/cfm/templates and expand the node.
  • Select “simple” node and Copy it.
  • Browse again to /apps/settings/dam/cfm/templates.
  • Select templates and Paste to create a copy of the “simple” node structure from /libs.
  • Select “Save All” to save all the changes. Here is a snapshot of the CRXDE lite, after you complete these steps.


  1. Now we will modify the copied structure based on our needs. We will create three elements – Header, Main and Footer, and define three Variations – Desktop, Tablet and Mobile Phone.
  • First, select “simple” node and rename it to “simple-topic”
  • Next, select “jcr:content” under “simple”. Change the value of “jcr:description” to “A fragment, containing three elements and three variations” and “jcr:title” to “Simple Topic Fragment”
  • Now, select elements and create two new elements – header and footer. To do so, create a new node and name it header. Add new properties “jcr:title” as “Header”, and “name” as “header”. Follow the same process to create “Footer” element.
  • Lastly, select node “jcr:content” under node “simple” and create a new node of type nt:unstructured and name it variations.
  • Now define all three variations – desktop, tablet and mobile, by creating a new node for each one of them of type nt:unstructured. Also set at least two properties, jcr:title and name.
  • Select “Save All” to save all the changes. Here is a snapshot of the CRXDE lite, after you complete these steps.


We have now successfully defined a new template called “Simple Topic Template”. Let’s test and use it in creating a new Content Fragment.

To create a new content fragment using the newly created template,

  • Browse to AEM Assets (DAM): http://localhost:4502/assets.html/content/dam
  • Click on “Create” and select “Content Fragment” to create a new Content Fragment
  • In the “New Content Fragment” wizard, you shall see two templates. Select the newly created “Simple Topic Fragment” and click next. Provide a name for the new template say first topic and click “Create”. Next choose “Open”.


  • We can now check and see that the newly created first topic template has three elements called – main, header and footer. We can select each one of these options to author these three sections separately.


  • Next, click on Variations and see that all the three default variations (desktop, tablet and mobile) that we defined in the template are also available.


We have successfully created and used a content fragment template.

Do share your thoughts/comments/feedback for the post.

Content Fragments – An Introduction

AEM 6.2 took a giant leap towards channel independent authoring by introducing Content Fragments. Now using AEM 6.2, one can author content without creating a Page. The text content is authored and managed in AEM Assets and is called a Content Fragment. Content Fragments can then be used in various channels like web pages, mobile apps, screens or campaigns.

What constitutes a Content Fragment?

A Content Fragment contains text segments and references to assets, likes images, videos, and/or fragments. They are independent of the delivery mechanism (i.e. page, channel) and can have variations of master elements to adjust fragment text according to the specific editorial or channel requirements. Think about these as content variation for various channels. I like to think of them as Responsive content!! Though Content Fragments are channel agnostic, they have a well defined content structure. One can define the structure in a Content Fragment template – structure is completely configurable.

Why should one use a Content Fragment?

As we know, in a professional setup, most of the times, content is authored by editorial staff and then it is layout by a production layout specialist. Content fragments allows authors to write content without having to worry about the layout. While writing one should write independent of the layout. In addition, one should think about how the same message gets conveyed on multiple channels – that’s all what Content Fragment authoring is all about.

Later, a Layout/Production specialist can associate the content fragment with components according to the channel and make sure the content is layout looks appealing. In addition, while binding a content fragment with the component, one can choose amongst the available content variations.

How to create a Content Fragment?

Content Fragments can be authored using AEM Assets. To create a Content Fragment, browse to the Assets Home and choose to create a Content Fragment (refer screenshot below)



Next, select the template and click Next. Out of the box, AEM ships with a “Simple Fragment” template. For any meaningful Content Fragments, one will need to create a template according to one’s needs.


Once a Content Fragment has been created, you can Edit it to author text.


You shall see the WYSIWYG text editor. You can author content here.


In addition to Rich text, you can also author content in either of the other two additional text formats supported in AEM 6.2  – a) Plain text and b) Markdown (https://en.wikipedia.org/wiki/Markdown)

How can I author Variations?

You can click on the Variations in the left hand panel and create as many variations as you want. In the screenshot below, you shall see that I have created four variations, one each for Mobile, Tablet, Screens and Web (Master).


Each Variation can have different text.

How can I add images in the Content Fragments?

Unfortunately, AEM 6.2 doesn’t allow you to add inline images. Instead, you can add images as references. In order to do so, select “Edit” on the top left corner and select “Associated Images”.


As the name suggests, you can associate any “Lightbox Collection”, managed in AEM Assets.

Next, we will deep dive into Content Fragment templates and see how you can create them and use them for authoring Content Fragments. I will cover that in the next Blog post.

Creating a new language site in AEM

Today, I am going back to basics and talk about something that I get asked for quite often – How to replicate an existing site in AEM in a new language.

Before we deep dive into how, let’s map a list of activities that one has to do to this procedure. As you are aware, a site in AEM is a collection of cq:pages which has components, and then text authored in those components and referenced images, videos, pdfs from DAM (Assets) etc. When we create a site, what we are essentially going to do is create copy of all of these cq:Pages, including all the references (you can choose if you wish to translate the references as well) first. Then, we will collect all the content (human readable text, images) and send those out for translation, to a translation vendor. Once everything is translated, we will import these back into our AEM site. So here is the flow:

  • Create the new language site (new path) and create a copy of the content.
  • Send out content for translation from this new path. Usually translation happens outside of AEM, unless you want to machine translate content.
  • Import back translated content.

AEM has built in functionality for managing all the three steps of the process. Let’s give it a spin.

Step1: Create new language site

Let us use Geometrixx Demo Site for this exercise. You will observe that the site is already supported in multiple languages. Let’s add a new language – Russian (ru).

  • Create language root: In order to create a language copy in a brand new language, you need to first create a dummy page, and name it as a valid ISO language code. So we will create a new page, and name it ru (ISO code for Russian).


  • Please ensure that you name it “ru”. Naming it correctly is key


  • Once the page has been created, we will go back and select the source (we are just going to select “Products” for illustration) and open References panel and select language copy


  • The Language copies shows all the languages in which “Product” page exists. Please note, it does not care about what is under that specific page though.
  • Next we will access the “Create Language” option to create “Products” in Russian. To do so select “Russian” from the list of languages. The drop down shows a list of languages that are configured for the site, in which the selected source page doesn’t exist. If you want to create a site in a new language, and don’t see the language in the drop down, first go and add a new language root. As soon as you add a language root, it will start appearing in the drop down.


  • Next, we can choose if we wish to just create the structure or send the content out for translation as well. There are three options:
    • Create structure, in which case Products page including all sub-pages will be copied over to Russian branch.
    • Create new Translation Project, in this case the content is copied over and additionally sent out for translation as well. For sending out content, we create a Translation Project, which is a special kind of an AEM Project.
    • Add to existing Translation Project, in this scenario, the content is copied over and is added to an existing Translation Project.

In our case, we are going to create a new Translation Project. Let’s call it “Products-russian”


Send content for Translation

Now that we have created the language copy, as well as created the Project, we will go ahead and send the content out for translation.

  • As first steps, we will go to AEM Projects and open up the Products-russian Project


  • When you open the Project, you shall see sections – a) Translation Summary, b) Translation job, c) Tasks and d) The Team.


  • Translation Summary is where you will set all the translation properties. Be default, AEM ships with “Microsoft Translator” machine translation connector. You can click on the three dots at the bottom and look all the Properties and change them as well.


  • Translation Job lists all the content that will be sent out for translation. You can add or delete content in this section.


  • Tasks and Team can be configured as well – I shall cover them in a separate post.
  • In order to send out content for translation, click on the Translation Job, and select “Start”. The process is completely automated and the content will be sent out for translation.


Import Content back for Translation

The import is completely seamless and integrated. When the content has been translated at the translator end, it comes back in AEM automatically. You will see the Status of the Translation Job change from “Committed for Translation” to “Ready for Review”.



Preview Feature

Today, I am going to talk about the brand new “Preview” functionality added by Adobe in AEM 6.2 as part of the Translation API. This support is geared at providing exact context to the translators as they translate the XML/XLIFF content – content without presentation.

Starting AEM 6.2, the translation connectors can additionally send out marked up HTML file as supporting documents in addition to the XML/XLIFF files that were available earlier for translation. This enables translation technology providers to use this file to generate real time preview of partially translated files without having to send back content to AEM – basically by replacing the translations in this marked up HTML file on their end.

Under the hood

Here is the API for fetching the Preview of the page sent out for translation.


* Gets a zip input stream containing the preview of Translation Object. This zip contains all the files required

* for offline preview of the translation object.

* @return Zip input stream, containing the preview of Translation Object.


ZipInputStream getTranslationObjectPreview();

The preview is actually a zip file which has all the relevant information. The most important file in the zip package is the HTML file, which has additional markup that helps connect translated strings to exact spots in the HTML file for generating a translated preview.


The highlighted markup above has links to the AEM XML/XLIFF file – see below.


You can refer to the implementation of the API in the Bootstrap connector here: https://github.com/Adobe-Marketing-Cloud/aem-translation-framework-bootstrap-connector/blob/master/bundle/src/main/java/com/adobe/granite/translation/connector/bootstrap/core/impl/BootstrapTranslationServiceImpl.java

Remember this Preview is for Translation purposes only – for folks who do not have access to AEM. For folks who have access to AEM, they can preview the translations in AEM itself.



Community Site Wizard

AEM Communities now comes with an out of the box easy to use wizard that customers can use to quickly create a branded community site without writing even a single line of code. Today, I will try to provide an overview of the Community Site Wizard. Let’s go over the wizard one screen at a time.

You can launch Community Site Wizard by accessing Sites, under Community Section. Here is a quick url to access Community Sites:

http://<hostname>:<port-number>/communities/sites. On the Community Sites Admin, click Create to launch the wizard.It is a four step wizard – General Settings (Site template), Design, Settings and Preview step.

Site Template:

In this step, one has to provide general settings about the Community and most importantly pick the Site Template. A site template, defines the structure of the Community Site. There are a few templates that are available out of the box. One can edit the existing templates or create a new template from accessing Sites Templates Console (Tools, Communities, Site Templates).


For this blog post, I will go ahead and create a Discussion Forum Community Site. Let’s go over these fields one by one:

Community Site Title: Self Explanatory

Community Site Description: self explanatory

Community Site Root: In case you want the Community Site to be a sub-site of a bigger site, you can specify the root path here. The Community Site is created at the specified path.

Community Site Base Language: Language of the Community Site Language. This creates the language node in the path name.

Community Site Name: This gets added to the path of the website. Think this through carefully as it gets added to site path and has impact on SEO.

Template: This is the most important field. Here you pick up the template for the Community Site.



In the first section, we pick the theme. All the themes are Twitter Bootstrap themes. You can go ahead and customize or add your own theme. In the next section, you can upload an image and brand your community website.


This is the section, where we get to do all the settings. There are multiple sections:


User Management:

In this section, we pick up options pertaining to User Management. All the fields are pretty self explanatory. You can turn on Social Logins via Twitter and Facebook, to use federated logins.


In this section, you pick up all the namespaces defined in the Tags Manager that apply to this Community Site. One can access the existing tags (and namespaces), modify, edit, remove or add new tags under a new namespace by manage tags in the Tags Manager (Tools > Tags).


In this section, you can choose the moderation settings.

Content is Premoderated: If this option is selected, the content will be visible to the community on the site only when a moderator approves of it. So, if a community member posts something, it wouldn’t be visible automatically. Use this option with caution – ensure that you have staffed moderators adequately so that they do not become a bottleneck.

Flagging threshold before content is hidden: Another common scenario is where you can use the community to moderate the forum. Community members can flag any post to be inappropriate. If the same post is flagged by multiple community members – if the number is greater than than the threshold, the post will be hidden and will require a moderator to approve of it before it becomes visible again.

Community Moderators: You can select Community Moderators using this settings.

Group Management:

Here in this section, you choose who is allowed to create Groups. Refer Managing Users and Groups for more information on this topic.


This setting is useful only if you have licensed Adobe Analytics for collecting key metrics. Refer this page for configuring and settings up Analytics.


These settings are useful if you wish to setup a Global Community, where we allow your users to contribute to the forum in different languages. You can choose different translation related settings in this section:

Allow machine translation: turn on this option if you want to allow your users to translate content in their preferred language. Be default, out of the box, AEM has a connector to MS translator and comes bundled with a trial license for 2 Million characters/month limit. You can buy a commercial license to get higher volumes of translation. You can also select other machine translation services likes Systran, Google Translate by writing an AEM connector to those service providers.

Select Languages to offer Machine Translation: You can tightly control all the language in which you want to offer Machine translation. At times you want to try out with a few languages before you go expand the list of supported languages. In addition, you can invest in improving the quality of machine translation by training the engines in specific languages.

Persistence Options: You can choose if you wish to store the translations in the AEM repository, once they have been translated. There are three options:

  • Do not persist: if selected, the machine translations are never saved in the AEM repository

Translation Contributions on User request and persist afterwards: if selected, when first user requests for the translation, AEM calls the machine translation service and then persists the translation thereafter. This option is useful if you wish to control machine translation costs and worry about the repository size.

  • Automatically translate new contributions and persist them: when this option is selected, the translations are requested as soon as a contribution is made in all supported languages – and then persisted thereafter. This option is useful if you wish to provide the best user experience to your community. This option also helps community members search for content, when it is not posted in their native language. Another feature, covered in this Blog post: https://experiencelabs.wordpress.com/2016/08/23/multilingual-searchmls-breaking-the-language-barrier/


Enablement is different kind of content, which is produced by the internal folks rather than being produced by Community. It is targeted for structure learning and training. We shall cover this in a different blog post.


The last step of the Wizard is Preview. All you can do here is click on the “Create” button and wait for the site wizard to put together a site for you. You need not worry too much about the settings, we will be able to come back to these settings (some of them) and change them using the “Edit Site” functionality.

Once the Wizard finishes processing, you will be navigated to the Community Site Admin, where we had started in the first place. However, you will see a folder and a newly created Community Site under it.


The Site offers three options:

  • Open Site: You can access this to Preview the site and make sure that it looks the way you wanted.
  • Edit Site: Click this to make modifications and change some of the settings that we had initially chosen in the wizard.
  • Publish: this is the final step. When you are ready and everything looks good, you can publish the site to the Publish instance. After this operation your Community can start accessing the Community site and start collaborating.

As you saw, we were able to put together a branded functioning site without writing a single line of code.

Please share your experiences with us and let us know if you find these blogs helpful.

Smart Rendering – Enhancing User Experience

Adobe Experience Manager (AEM) comes equipped with the powerful ‘Communities’ feature. It enables the development of a relationship with the site visitors that informs through blogs, Q&A and event calendars, while gaining insights through forums, comments, and other community content, often referred as User Generated Content (UGC).

With the release of AEM 6.2, users would further get an enhanced experience in translating the UGC. This has become possible because of this new feature – Smart Rendering. It lets one translate the complete User Generated Content, present on a community site, while loading the page.

In this blog, I would explain how to enable this feature and how to manage what language you’d see after the translation.

Let us start by learning as to How to enable Smart Rendering

When a user creates a community site in the ‘Author’ instance, using the Community site Creation Wizard and publishes it, Smart Rendering is not set. To do so, we need to publish and open the site in ‘Publish’ instance.

  1. Go to ‘Profile’ tab on the community as depicted below:


  1. Click on ‘Edit Profile’ button and you will find an option that says ‘Always show contributions in my preferred language’. Choose ‘On’ from the drop down menu


Now, we have successfully enabled the Smart Rendering.

Let us now learn as to how do we manage the ‘Target Language’

There are various factors that can affect the outcome you are going to see after the translation. To decide it, the system considers three options

  • User Language (ul)
  • Browser Language (bl)
  • Page Language (pl)

The User language is given highest priority. If you open ‘Profile’ tab for the first time, you’d notice that the user language (ul) is not set. If you click on the ‘Edit Profile’ settings, the system will set the user language to English (en) by default. You can choose from the drop down menu any language as your preferred language and the UGC will get translated into that language.


Suppose, at first, the User Language is not set, the system gives preference to Browser Language (bl). It can be found under the language settings in your respective browsers.

Page language (pl) is the language of the page or technically, the language of the community site. It is set while creating community site and given the least priority while translation happens.

This feature that makes it very convenient to enable Smart Rendering and set-up language preferences. Stay tuned for more on this!!

This blog post has been authored by Arun Rajan (AEM Translation Team).

XML Documentation Add-On for Adobe Experience Manager

Adobe recently launched a new Add-On Package to Adobe Experience Manager, specifically targeted at bringing technical communication closer to Adobe Experience Manager. The new package is being marketed as “XML Documentation Add-on for Adobe Experience Manager” and on Adobe.com. The Add-On provides the capability of managing DITA content and publishing it from AEM. If you have ever worked on Technical Documentation, you would be conversant with DITA. From a very long time, AEM did not have a solution for natively handing Technical Communication content. However, this Add-On seems to be a step in this direction. It will open doors for large enterprises that manage documentation in DITA to publish directly via AEM without having to go through the conversion process – which was one off and had to be repeated.

Apart from the basic ability of publishing DITA content, Adobe seems to be positioning this as a CCMS (Component Content Management System). This is very interesting and intriguing. In some form, AEM with it components was already a Component Content Management System. However, AEM has always pushed the envelope when it comes to web and connected experiences. It would be really interesting to see how this evolves and helps promotes content reuse. There was a key feature added in AEM 6.2 called Content Fragments, which could also be looked as a step in the direction of content reuse. From a strategy perspective, it is very clear that Content reuse is something that Adobe is now serious about.

What I like the most is the idea of a single Content Management System for both Marketing and Technical Communication. It is a huge benefit for large enterprises and system integrators like us offering the following key benefits:

  1. Standardizations of content platform and processes: Enterprises can now think about putting AEM at the center of all things Content. They can invest in building standardized content workflows and processes across the organization – Review workflows, SEO/SEM workflows, Translation workflows and Publishing workflows. This opens up immense opportunities for standardization.
  2. Reduction in Costs: Develop once and use across all sites and content. No duplication of assets (templates); look and feel etc. Integrate once and with one platform. Integration of other services like Analytics, SEO/SEM, personalization, translation is a huge effort and cost. By having one platform, we are saying that it needs to be done once.
  3. Consistency:There is consistency at both levels – for users of the Platform and end customers. For authors (marketing content authors and Technical documentation authors), it is the same system. The experience is consistent and same. The reports and processes are the same. For an end customer, it is going to provide a consistent experience when they move from Marketing section to Help and Learning section. We are already seeing the boundaries blur and this is going to help even more.
  4. Upsell Opportunities: One trend that we see in the market is the option to upsell offering while you are struggling with a problem – In-context Upsell offers. One single platform opens up the possibility of sharing Technical Documentation insights with the marketing side of the house to provide Upsell offers.

The more I think about this option, the more excited I get. I am going to peel this onion in next few days and will continue to share insights here in this blog.