- Communities Guide
- Introduction to AEM Communities
- Communities Sites
- AEM Communities Overview
- AEM Communities Release Notes
- Getting Started with AEM Communities
- Getting Started with AEM Communities for Enablement
- Initial Setup
- Author a New Community Site
- Experience the Published Site
- Authoring Nested Groups
- Initial Setup for Enablement
- Author a New Community Site for Enablement
- Create and Assign Enablement Resources
- Experience the Published Enablement Site
- Deploying
- Administering
- User and UGC Management Service in AEM Communities
- Communities Sites
- Communities Consoles
- Analytics Configuration for Communities Features
- Configuring Enablement Features
- Configuring Messaging
- Moderating Community Content
- Configuring Email
- Communities Notifications
- Communities Subscriptions
- Communities Scoring and Badges
- Managing Users and User Groups
- Community Groups Console
- Social Login with Facebook and Twitter
- SRP - Community Content Storage
- Communities Sites Console
- Members & Groups Management Consoles
- Moderation Console
- Communities Tools
- Site Templates
- Group Templates
- Community Functions
- Storage Configuration
- Badges Console
- Enablement Resources Console
- Reports Console
- MySQL Configuration for Enablement Features
- FFmpeg for Communities
- In-Context Moderation
- Advanced Scoring and Badges
- ASRP - Adobe Storage Resource Provider
- MSRP - MongoDB Storage Resource Provider
- How to Setup MongoDB for Demo
- DSRP - Relational Database Storage Resource Provider
- MySQL Configuration for DSRP
- JSRP - JCR Storage Resource Provider
- Solr Configuration for SRP
- Tagging Enablement Resources
- Tagging User Generated Content
- Translating User Generated Content
- Communities User Synchronization
- Member Contribution Limits
- Developing
- Developing Communities
- Social Component Framework
- Community Components Guide
- Component, Function and Feature Essentials
- Tutorials
- Troubleshooting
- Coding Guidelines
- Server-side Customization
- Client-side Customization
- SCF Handlebars Helpers
- Storage Resource Provider Overview
- Community Site Essentials
- Activity Stream Essentials
- Assignments Essentials
- Blog Essentials
- Calendar Essentials
- Catalog Essentials
- Clientlibs for Communities Components
- Comments Essentials
- OSGi Events for Communities Components
- Featured Content Essentials
- File Library Essentials
- Forum Essentials
- Community Group Essentials
- Ideation Essentials
- Leaderboard Essentials
- Liking Essentials
- Messaging Essentials
- QnA Essentials
- Rating Essentials
- Reviews Essentials
- Rich Text Editor Essentials
- Scoring and Badges Essentials
- Search Essentials
- Component Sideloading
- Social Graph Essentials
- SRP and UGC Essentials
- Tag Essentials
- Tally Essentials
- Voting Essentials
- Setup Website Structure
- Create an SCF Sandbox
- Initial Sandbox Application
- Initial Sandbox Content
- Develop Sandbox Application
- Develop Sandbox Content
- Add Clientlibs
- Overlay Comments Component
- Create Comments Page
- Create Nodes
- Alter the Appearance
- Create the Components
- Add Comment to Sample Page
- Extend Comments Component
- Alter the Appearance (HBS)
- Create a Sample Page
- Accessing UGC with SRP
- Using Maven for Communities
- Naming Conventions
- SocialUtils Refactoring
- Authoring
- Communities Components
- Communities Components Basics
- Activity Streams Feature
- Assignments Feature
- Blog Feature
- Calendar Feature
- Catalog Feature
- Using Comments
- Featured Content Feature
- File Library Feature
- Forum Feature
- Community Groups
- Ideation Feature
- Leaderboard Feature
- Using Liking
- Messaging Feature
- Q&A Forum Feature
- Using Ratings
- Using Reviews and Reviews Summary (Display)
- Search Feature
- Using Social Graph
- Activity Trends
- Using Social Tag Cloud
- Using Voting
- Create a Sample Page
Create Nodes
Overlay the comment system with a custom version by copying the minimal number of files necessary from /libs into /apps and modifying them in /apps.
The contents of the /libs folder are never edited because any re-install or upgrade may delete or replace the /libs folder while the contents of the /apps folder is left untouched.
Using CRXDE Lite on an author instance, begin by creating a path in the /apps folder which is identical to the path to the overlaid components in the /libs folder.
The path being duplicated is:
/libs/social/commons/components/hbs/comments/comment
Some nodes in the path are folders and some are components.
-
Browse to http://localhost:4502/crx/de/index.jsp
-
Create
/apps/social(if it does not already exist)- Select
/appsnode - Create > Folder …
- Enter Name:
social
- Enter Name:
- Select
-
Select
socialnode- Create > Folder…
- Enter Name:
commons
- Enter Name:
- Create > Folder…
-
Select
commonsnode- Create > Folder…
- Enter Name:
components
- Enter Name:
- Create > Folder…
-
Select
componentsnode- Create > Folder….
- Enter Name:
hbs
- Enter Name:
- Create > Folder….
-
Select
hbsnode- Create > Create Component…
- Enter Label:
comments - Enter Title:
Comments - Enter Description:
List of comments without showing avatars - Super Type:
social/commons/components/comments - Enter Group:
Communities - Click Next until OK
- Enter Label:
- Create > Create Component…
-
Select
commentsnode-
Create > Create Component…
- Enter Label:
comment - Enter Title:
Comment - Enter Description:
A comment instance without avatars - Super Type:
social/commons/components/comments/comment - Enter Group:
.hidden - Click Next until OK
- Enter Label:
-
Select Save All
-
-
Delete the default
comments.jsp- Select node
/apps/social/commons/components/hbs/comments/comments.jsp - Select Delete
- Select node
-
Delete the default comment.jsp
- select node
/apps/social/commons/components/hbs/comments/comment/comment.jsp - Select Delete
- Select Save All
- select node
In order to preserve the inheritance chain, the Super Type (property sling:resourceSuperType) of the overlay components are set to the same value as the Super Type of the components being overlaid, in this case:
social/commons/components/commentssocial/commons/components/comments/comment
The overlay’s own Type(property sling:resourceType) must be a relative self-reference so that any content not found in /apps is then looked for in /libs.
- Name:
sling:resourceType - Type:
String - Value:
social/commons/components/hbs/comments
- Select the green
[+] Add- Name:
sling:resourceType - Type:
String - Value:
social/commons/components/hbs/comments/comment
- Name:
- Select the green
[+] Add- Select Save All
Business.Adobe.com resources
Resources
Adobe Account
