Monday, 31 July 2017

Creating a custom Image Text component for Experience Manager 6.3

As an Adobe Experience Manager component developer, you can create custom components to address project requirements. For example, you can create a custom image/text component that can let an author dynamically set the position of the image on a web page.  A author can set the image on the left side of the page, as shown here.


Likewise, the author can set the image on the right side. 



Benefits of creating this custom text/image component are as follows: 
  1. No need to merge everything into one single component.
  2. An author can drag and drop additional components as required.
  3. This component has a custom image, heading and button component. which can be added or deleted from the parsys.
  4. It is responsive so as per screen resolution, it is adjusted.
  5. In the main div, you can first select the image position i.e left/right.
To read this development article, check back on Fri Aug 11, 2017.

NOTE: this component does not make use of backend Java code, only front end HTL logic. 




Tuesday, 25 July 2017

Working with Experience Fragments and the Experience Manager ContextHub

When working with Adobe Experience Manager ContextHub and Personalization use cases, you can use Experience fragments to change the content that is displayed. Experience Fragments is a new feature introduced in AEM 6.3. It allows content authors to reuse content across channels including Sites pages and 3rd party systems. For more information, see Using AEM Experience Fragments.

Using Experience Fragments, you can display content based on the audiences. For example, some users may see this content:


While others may see this content. 


This development article walks you through how to use experience fragments when using the ContextHub, 


Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner





I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 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 @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel




Monday, 24 July 2017

Creating Adobe Experience Manager 6.3 Sling Model Components

You can work with Sling Models when developing with Adobe Experience Manager (AEM) 6.3. That is, when developing an Experience Manager project, you can define a model object (a Java object) and map that object to Sling resources. For more information, see Sling Models.

A Sling Model is implemented as an OSGi bundle. A Java class located in the OSGi bundle is annotated with @Model and the adaptable class (for example, @Model(adaptables = Resource.class). The data members (Fields) use @Inject annotations. These data members map to node properties.

Consider the following Java class named UserInfo.

package SlingModel63.core;
  
import javax.inject.Inject;
  
import org.apache.sling.api.resource.Resource;
import org.apache.sling.models.annotations.Model;
   
@Model(adaptables = Resource.class)
public class UserInfo {
    @Inject
    private String firstName;
    @Inject
    private String lastName;
    @Inject
    private String technology;
       
    public String getFirstName() {
        return firstName;
    }
    public String getLastName() {
        return lastName;
    }
    public String getTechnology() {
        return technology;
    }
   
}

As you can see in the code example, the @Model annotation is used. Likewise, each data member in the UserInfo class is annotated using the @Inject annotation. This Java class is mapped to a Sling resource, like the one shown in the following illustration.


Notice that the class members in the UserInfo class map to the String properties that belong to the /content/testsling/slingmodel node. This article walks you through creating a Sling Servlet that uses a Sling Model to map to this resource.

The following illustration shows the output of the Sling Servlet that uses Sling Models. Notice that the values in the node properties are displayed.



Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner





I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 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 @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel



Friday, 14 July 2017

Ask the AEM Community Experts for July 2017

Join the July version of Ask the AEM Community Experts where Peter Nash and Axis 41 community members will discuss AEM and Dispatcher topics focusing on real world topics.





To watch this session, click : http://bit.ly/ATACE0717.

Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner





I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 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 @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel

Wednesday, 12 July 2017

Using the Adobe Experience Manager ContextHub to work with Personal Experiences

You can work with the Adobe Experience Manager ContextHub to work with personalized experiences.  A personalized experience presents the visitor with a tailor-made environment displaying dynamic content that is selected according to their specific needs; be this on the basis of predefined profiles, user selection, or interactive user behavior.

That is, personalized content is what web site visitors want to see. It can be categorized, and therefore made available to users according to predefined rules and it must be dynamic; in other words the content must, in some way, be dependent upon the user. If every user would see the same content, then personalization would be redundant.

This article illustrates how to use the Contenthub to work with personalization, That is, the value of the components (or even which components are rendered) that are displayed depends on the user. Consider the following user, whom is a seller (the Business Segment).



Likewise, if a user whom is a buyer is selected from the Contexthub, then the contents of the web page reflects this, as shown in this illustration. 


This article walks you though how to setup personalization data and display the results using the AEM ContextHub.

To read this article, click https://helpx.adobe.com/experience-manager/using/contexthub_personal.html.

Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner





I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 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 @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel

Tuesday, 11 July 2017

Configuring Experience Manager Rich Text Editor Plugins in a Touch UI Component Dialog

You can create an Adobe Experience Manager (AEM) Touch UI component dialog which contains the Rich Text Editor (RTE) . As a component developer, you can configure the RTE when developing the component. The RTE provides authors with a wide range of functionality for editing their textual content. That is, providing them with icons, selection boxes and menus for a WYSIWYG experience.



Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner





I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 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 @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel