Thursday, 22 May 2014

Customizing Your First Adobe Experience Manager 6 Social Component

Adobe Experience Manager (AEM) 6 supports social components that let you build web sites that contain social functionality that lets you engage with your customers. For example, you can add functionality that lets your users leave comments on your website. AEM supports out of the box socials components. For information, see Introduction to Social Communities.

AEM also supports the ability to customize these social components to meet your business requirements. You can use the AEM Social Component Framework Java API to create a custom social component. An user can interact with an AEM web site by interacting with functionality exposed by your custom social component.







An AEM social component forms the basis of HTTP API responses and the context made available to a front end component. Sometimes you need to add more information or hide information to the default social component to meet your business requirement. You can achieve this use case by writing an AEM OSGi bundle that uses the AEM Social Component Framework Java API located in the com.adobe.cq.social.commons.client.api package. For information about this API, see Package com.adobe.cq.social.commons.

For example, you can modify the appearance of the AEM comment system by using AEM Java APIs.



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


2 comments:

  1. The dependencies listed in the article in the pom.xml are not yet available in the public Adobe Maven repo causing the build to fail.

    ReplyDelete
  2. Thxs for pointing that out - they were suppose to be there.

    ReplyDelete