Tuesday, 31 January 2017

Creating an Adobe Experience Manager Newsletter HTL component

You can create an Adobe Experience Manager HTL component that renders a newsletter that you can distribute to an email audience. For example, consider a digital marketer that wants to promote events around a specific product. By creating an AEM newsletter, they can raise awareness of the product.

As an AEM developer, you can create an AEM HTL component that lets an author set all content for a newsletter, including images, text, links to other content such as videos, and so on. The following illustration shows the newsletter created in this development article.


As shown in the previous illustration, the HTL component renders a newsletter that consists of these sections:
  • text and image shown at the start of the newsletter
  • text that provides a summary of the newsletter
  • a repeating data section that contains the body of the newsletter. There can be many sections under the current issue section set by an author.
  • a section that lists previous editions.

 Content for each section can be set by using a different tab in the Touch UI dialog. The following illustration shows the tab that populates the text and image section. 


This article steps you through how to build this AEM newsletter component. To read this article, click https://helpx.adobe.com/experience-manager/using/htl_news.html

To watch the video - see:



Adobe Digital Marketing Community

Join the Adobe Digital Marketing Community. Start by clicking this banner



I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with over 18 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeMktgCare.

TwitterFollow me on Twitter @smac2020  


Friday, 27 January 2017

Learn how to build an AEM component that inherits from a foundation component

Here is a great community video that talks about how to build an AEM component that inherits from an foundation component.




Thursday, 26 January 2017

Integrating the Angular2 framework into Adobe Experience Manager

You can integrate the Angular2 Framework into Adobe Experience Manager thereby enabling you to build components that take advantage of the Angular2 framework. The Angular2 framework is a popular JavaScript library that simplifies the creation of powerful components. For example, you can build components that contain visual effects, data grids that display information, user forms that capture information from end users, and so on. For more information about AngularJS, see https://angularjs.org/.


This Experience Manager community article walks you through how to build an AEM component using Angular2. To read this article, click https://helpx.adobe.com/experience-manager/using/aem_angular21.html.

To watch the video, click: 




Adobe Digital Marketing Community

Join the Adobe Digital Marketing Community. Start by clicking this banner



I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with over 18 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeMktgCare.

TwitterFollow me on Twitter @smac2020  




Monday, 23 January 2017

Creating an Adobe Experience Manager HTL component that displays a repeating data set

You can create an Adobe Experience Manager HTL component that displays repeating information that can be set by an AEM author during design time. For example, consider a typical on-line section of a sports site. Each section that lists a story includes a digital asset (located in the Experience Manager DAM), a heading, and text.

The following illustration shows an Experience Manager HTL component listing various sport stories about a youth football club.




As shown in the previous illustration, the HTL component displays a repeating set of data where each section has a heading, text and an image. An author sets this information using a Touch UI dialog that contains a Multifield control. 



This community developer article steps you through how to build this AEM HTL component. To read this article, click https://helpx.adobe.com/experience-manager/using/htl_repeat.html

Video

Click the following to watch the video



Adobe Digital Marketing Community

Join the Adobe Digital Marketing Community. Start by clicking this banner



I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with over 18 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeMktgCare.

TwitterFollow me on Twitter @smac2020  

Friday, 20 January 2017

Retrieving Adobe Experience Manager ContextHub information using the ContextHub API

Adobe Experience Manager exposes a Java API named the ContextHub API that lets you programmatically obtain information about the Experience Manager ContextHub. The Experience Manager ContextHub contains data that displays information about users, known as context data. For more information about the Experience Manager ContextHub, including ContextHub stores, see Adding ContextHub to Pages and Accessing Stores.

For example, you can create a custom Experience Manager service that logs information about the ContextHub, as shown below.

9.01.2017 12:43:38.886 *INFO* [OsgiInstallerImpl] com.community.aem.core.ContextHubServiceImpl Size of stores list :14
19.01.2017 12:43:38.886 *INFO* [OsgiInstallerImpl] com.community.aem.core.ContextHubServiceImpl ---------Store----------
19.01.2017 12:43:38.886 *INFO* [OsgiInstallerImpl] com.community.aem.core.ContextHubServiceImpl contexthub.geolocation
19.01.2017 12:43:38.886 *INFO* [OsgiInstallerImpl] com.community.aem.core.ContextHubServiceImpl contexthub.surferinfo
19.01.2017 12:43:38.886 *INFO* [OsgiInstallerImpl] com.community.aem.core.ContextHubServiceImpl granite.profile
19.01.2017 12:43:38.887 *INFO* [OsgiInstallerImpl] com.community.aem.core.ContextHubServiceImpl granite.emulators
19.01.2017 12:43:38.887 *INFO* [OsgiInstallerImpl] com.community.aem.core.ContextHubServiceImpl aem.analyticsdata
19.01.2017 12:43:38.887 *INFO* [OsgiInstallerImpl] com.community.aem.core.ContextHubServiceImpl aem.pagedata
19.01.2017 12:43:38.887 *INFO* [OsgiInstallerImpl] com.community.aem.core.ContextHubServiceImpl aem.segmentation

To read this development article, click Retrieving Adobe Experience Manager ContextHub information using the ContextHub API.


Adobe Digital Marketing Community

Join the Adobe Digital Marketing Community. Start by clicking this banner



I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with over 18 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeMktgCare.

TwitterFollow me on Twitter @smac2020  






Wednesday, 11 January 2017

Ask the AEM Community Experts for Jan 2017 - Integrating Test and Target with Adobe Experience Manager for Personalization use cases

Join Varun Mitra, Tech Training Instructor and Developer, Adobe Worldwide Field Enablement  as he provides information about using Adobe Experience Manager and and Test and Target together for digital marketing solutions.

In this session, Varun will cover best practices on using AEM and Test and Target to setup personalization use case.

Date: Thurs January 26, 2017
Time: 11 AM EST

To watch this session, click  https://communities.adobeconnect.com/pnrm61xlhed9/?launcher=false&fcsContent=true&pbMode=normal


Adobe Digital Marketing Community

Join the Adobe Digital Marketing Community. Start by clicking this banner



I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with over 18 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeMktgCare.

TwitterFollow me on Twitter @smac2020  


Sunday, 8 January 2017

Creating an Adobe Experience Manager HTL Component that parses MS Word Documents

You can develop an Adobe Experience Manager HTL (used to be known as Sightly) component that can parse and display content from MS Word documents. Some Experience Manager use cases require integrating MS Word documents with Experience Manager. The HTL component developed in this article parses a MS Word document and displays the content in in a HTL component, as shown in the following illustration.

Consider the following Word Doc.


You can develop a custom HTL component to parse this Word doc and display the data in an AEM web page, as shown in the following illustration. 





To parse data from a MS Word document, you use Apache POI API.  To read this Experience Manager development article, click https://helpx.adobe.com/experience-manager/using/aem_msdoc.html.

Adobe Digital Marketing Community

Join the Adobe Digital Marketing Community. Start by clicking this banner



I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with over 18 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeMktgCare.

TwitterFollow me on Twitter @smac2020  






Thursday, 5 January 2017

Congratulations Lokesh Bangalore Shivalingaiah - our 2016 AEM Community Member of the year

I want to extend my congratulations to Lokesh Bangalore Shivalingaiah - our 2016 AEM Community Member of the year winner. This is the second straight year that Lokesh has won the AEM Community member of the year award.

This year, we are very pleased to award Lokesh with the following device.


Lokesh was awarded an IPhone 7 Plus 256 GB device.  I am sure you are going to love this device

You earned this awesome device by helping so many AEM community members:
  • contributing code for articles
  • participating in the AEM forums (you are second place),
  • giving 2 Ask the AEM Community Expert sessions
  • testing various HELPX articles

From all of the Adobe Digital Marketing Community team - we want to congratulate you! 


Adobe Digital Marketing Community

Join the Adobe Digital Marketing Community. Start by clicking this banner



I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with over 18 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeMktgCare.

TwitterFollow me on Twitter @smac2020  



Tuesday, 3 January 2017

Dynamically changing an Adobe Experience Manager Touch UI Dialog

You can develop an Adobe Experience Manager component that uses a dialog whose fields are dynamically update based on a selection of another field. Dynamically updating fields is important when you need to present an Experience Manager author different possibilibies based on the selection of another field. For example, assume that an author selects a value from a drop-down field. You can develop application logic that sets another field based on the selected value. Consider the following Experience Manager Touch UI dialog.


When an author selects Background Image, it dynamically sets a Pathfield field, as shown in this illustration.


Likewise, if the author selects another value from the dropdown (for example, Background Color), a second drop-down field is dynamically set, as shown in this illustration. 


To develop Touch UI dialogs, you use the AEM Granite API

This article walks you through how to develop this Dialog that dynamically sets fields. To read this article, click https://helpx.adobe.com/experience-manager/using/dynamic_touchui.html

NOTE: To learn how to dynamically work with AEM Classic UI dialogs, see Dynamically updating AEM custom xtype fields


Adobe Digital Marketing Community

Join the Adobe Digital Marketing Community. Start by clicking this banner



I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with over 18 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeMktgCare.

TwitterFollow me on Twitter @smac2020