Coding Guidelines coding-guidelines
CAUTION
AEM 6.4 has reached the end of extended support and this documentation is no longer updated. For further details, see our technical support periods. Find the supported versions here.
Guidelines, Tips and Tricks guidelines-tips-and-tricks
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:
Code code
- 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.
Scripts scripts
- 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.
IDE ide
- Using Maven for Communities - how to include the Communities API jar.
- SocialUtils Refactoring - utility methods for SRP that replace SocialUtils.
recommendation-more-help
5d37d7b0-a330-461b-814d-068612705ff6