In AEM 6.2, you can use content fragments that let you create original content in AEM, enabling copy writers to create editorial content before it is being authored in a page, and to further allow curating such content by creating channel specific variations and by associating collections with relevant media content. As a result, web producers receive content that is prepared and "ready to go”, enabling them to focus on assembling content across channels, globally and on a local level.
Tuesday, 14 June 2016
Thursday, 2 June 2016
Bulk Editor in AEM
The Bulk Editor allows for very efficient editing when the visual page context is not needed as it lets you:
- search for (and display) content from multiple pages; this is done using GQL (Google Query Language)
- edit this content directly in the bulk editor
- save the changes (to the originating pages)
- export this content to a tab-separated (.tsv) spreadsheet file
Wednesday, 1 June 2016
Saturday, 28 May 2016
Using Custom Tag Libraries to search for AEM Content Tags
You can create custom tag libraries for Adobe Experience Manager (AEM) and use them to search for AEM content tags. Tags are a quick and easy method of classifying content within your website. In technical terms, a tag is a piece of metadata assigned to a content node within AEM (usually a page). A custom tag library uses an OSGi component. Within the OSGi component, the AEM Tag Manager is used to search for the content tags, For information about the API, see TagManager API.
A custom tag library is implemented as an OSGi bundle that contains a Java class that extendsTagSupport. For information, see Class TagSupport.
You also need to define a tag library descriptor (TLD) file and bundle that within the OSGi bundle. For information, see Tag Library Descriptors.
After you develop an AEM custom tag library, you can invoke its actions from an AEM component. For example, the component can display information about tag usage (for example, the number of times it is used). In this article, a Tags xtype is used to let the author select a tag from an AEM dialog, as shown in the following illustration.
Sunday, 15 May 2016
Integrating AEM with Adobe Analytics and Target using DTM
You can create Adobe Experience Manager (AEM) solutions that integrate with these Ditigal Marketing products: Adobe Analytics, Adobe Target, and Dynamic Tag Manager (DTM).
Adobe Analytics is the industry-leading solution that lets digital marketers analyze and optimize integrated data from all online initiatives across multiple marketing channels. It provides marketers with actionable, real-time web analytics intelligence about digital strategies and marketing initiatives.
Adobe Target is a personalization solution that lets you easily identify content through tests that are easy to execute. Therefore, you can deliver the best experience to your web visitors. In this article, personalization of the landing page is driven by Target. AEM will import Audiences from Target so that they can be used right within AEM to create activities to personalize our page. AEM then synchronizes the activity to Target.
DTM is a Digital Marketing cloud service that allows a marketer to manage Adobe and third-party tags used for tracking or other analytic purposes. It is done through client-side scripting that injects tag related code throughout the pages of the site.
By using these products together, you can build engaging solutions that let you deliver the best content to a given web site visitor. That is, you display content from AEM DAM that meets the interest of the visitor. This development article walks you through how to build a solution that uses AEM, Analytics, Target, and DTM.
The following illustration provides an overview some of the Marketing Cloud solutions (AEM, DTM, Analytics, and Target) used in this article.
Thursday, 28 April 2016
Top Features in Adobe Experience Manager 6.2: Sites
- Find Anything Anywhere
Adobe has introduced an updated Touch UI. This is actually a great enhancement, but once again Adobe is changing the user interface. It’s hard on authors to constantly need to learn a new way of doing things and navigating around, and it means additional training for people when they upgrade from one version to another. But let’s not get bogged down with negativity. The new update to AEM is called OmniSearch and this is a really decent way of getting around. No longer do I have to do multiple clicks to find my tags. I just type “tags” and then the page loads. It also comes with search suggestions that show you all the possible destinations within AEM and the ability to do filtered searches. Also, they removed the need to go to a “selection mode” to select multiple items (pages, assets, etc.) when you need to activate them or update their properties. That’s great. - Templates for Everyone
This is the new Template Editor. Last year when they teased this I mentioned how reluctant I was about it. Put the template in the hands of the authors and not the developers, are you insane? I still feel that way, but not as strongly now. An author can still royally screw things up, if you give them the permissions to do so. And that is the key. You can tie down this functionality by only giving it to people who actually know what they are doing. I was able to chat a bit with Gabriel Walt during Summit and that was his big piece of advice. So, we can still be happy, authors can still feel empowered, and developers won’t have to do as much. I had a chance to play around with it a bit in one of the Summit lab sessions and it certainly shows some promise.
Subscribe to:
Posts
(
Atom
)