You're viewing help content for version:
- 6.4
- 6.3
- 6.2
- Older Versions
Working with AEM Communities has evolved from being heavily dependant on Java Server Pages to flexibility in the choice of templating scripting languages where business logic, style, and page content are distinct from one another.
Further flexibility in working with user generated content (UGC) is through the SocialResourceProvider API, which eliminates the need for awareness of which SRP option was chosen for the deployment.
Following are various coding guidelines and best practices for AEM Communities developers :
- Accessing UGC with SRP - how to avoid writing an application that only works when UGC is stored in JCR (JSRP).
- SocialUtils Refactoring - utility methods for SRP that replace SocialUtils.
- Naming Conventions - naming conventions for custom Java classes.
- Sideloading Communities Components - how to dynamically add a component after the page loads.
- Rich Text Editor Essentials - how to customize the rich text UI provided to members for posting content.
- Using Maven for Communities - how to include the Communities API jar.
- SocialUtils Refactoring - utility methods for SRP that replace SocialUtils.
Twitter™ and Facebook posts are not covered under the terms of Creative Commons.