AEM Communities

You are reading the AEM 6.2 version of AEM Communities.
This documentation is also available for the following versions:  AEM 6.3  AEM 6.1 

This section provides more detailed information on the improvements to AEM Communities since the 6.1 release.

Additional improvements and new features are available in AEM Communities feature pack (FP) releases.

To obtain the latest release, see the Deploying Communities section of the documentation.

6.2 GA

Storage Resource Providers

There are three persistence options for storing user generated content (UGC):

  • ASRP: Adobe Storage Resource Provider: store your content in a cloud service provided and supported by Adobe - suitable for moderate volumes of UGC and/or TarMK publish farm topologies
  • MSRP: MongoDB Storage Resource Provider: store your content in a dedicated MongoDB instance - suitable for large volumes of UGC and/or TarMK publish farm topologies
  • JSRP: JCR Storage Resource Provider: store your content in the JCR repository of your publish servers - requires the use of a publish cluster (MongoMK or RDBMK)

JSRP is now supported for production use, making use of OAK indices for better performance.

Community Sites

It is now possible to:

  • Edit the settings and the structure of a community site after being created with the community site creation wizard
  • Select the language for a new community site created via the community site creation wizard, then adding new sites and languages later on
  • Select the root content path for the community site to be created via the community site creation wizard

See the Communities Sites console section of the documentation.

Community Functions

Privileged Members

The "privileged members" feature allows community administrators to restrict which community members can create new top level content, such as blog articles, QnA questions or calendar events for each individual component.

See the Privileged Members Group and Community Functions sections of the documentation.

Blogs

The new publish-side blog community function provides an easy to use blogging feature with support for:

  • Publish-side creation of blog articles and comments
  • Rich text editing
  • Inline images (with support for drag and drop)
  • Embedded social networking content (oEmbed support)
  • Draft mode
  • Scheduled publishing
  • Compose on-behalf (Privileged Member can create content on behalf of a different communty member)
  • In-context and bulk moderation of blog articles and comments

See the Blog Essentials and Blog Feature sections of the documentation.

QnAs

The new QnA community function allows community members to ask questions with the ability to indicate the best answer with support for:

  • Rich text editing
  • Inline images (with support for drag and drop)
  • In-context and bulk moderation of QnA questions and answers

See the QnA Essentials and Q&A Forum Feature sections of the documentation.

Calendars

The new calendar community function allows community members to post community events with support for:

  • Rich text editing
  • Multiday events
  • Attaching files to the event
  • Selecting a cover image for the event
  • Finding and filtering calendar events via full text search, tags, and dates
  • In-context and bulk moderation of calendar events and comments

See the Calendar Essentials and Using Calendars sections of the documentation.

Member Management

The new member management feature allows community administrators to manage members (publish-side users) and member groups (publish-side user groups) directly from the author environment in order to:

  • Create, edit or delete community member accounts
    • Profile information
    • Profile picture
    • Sites membership
    • User groups membership
    • Password reset
    • Account status (banning)
    • Add or remove community members from groups
  • Create, edit or delete member groups

Note: This feature is particularly useful for group-based assignment of enablement resources.

See the Members and Groups Management consoles section of the documentation.

Analytics and Reporting

The new Adobe Analytics instrumentation for most community components allows for native data collection of the following events using the AEM Analytics integration framework:

  • Posts
  • Views
  • Follows
  • Votes

In the author environment, reports on views and posts are available from the "Communities" area.  See the Reports console section of the documentation.

From the publish environment, the Communities Activity List component provides the ability to add trending information regarding posts and views by members as well as posts and views of content on the publish environment.  See Activity Trends in the documentation.

Aggregated KPIs for various time periods (last 24 hours, last 7 days...) are periodically imported back into the UGC common store and associated:

  • To each community member
  • To each UGC fragment - for instance the number of views is now presented when listing forum topics, blog articles and QnA questions

Notifications

The new notification features allow community members to follow specific community content or members, resulting in immediate notifications when new contributions are made, e.g.:

  • When a reply is posted to one's own posts
  • When a new contribution is made in some area when notifications have been explicitly enabled
  • When a new contribution is made by a community member for which notifications have been explicitly enabled

Notifications are broadcasted via pluggable "notification channels".  Notifications are available in the Web user interface within a dedicated area.

See the Communities Notifications section of the documentation.

Scoring and Badging

The new scoring features allow for automatically scoring community members' participation. Each action can be associated with a configurable amount of points (for example, each answer to a question might be worth 5 points). Sample scoring rules are provided under /etc/community/scoring in the repository.

The new badging features allow for manually or automatically awarding badges to community members based on scores and configurable thresholds. Sample badging rules are provided under /etc/community/badging. Whether badges are to be displayed under the avatar image for each community member is configurable at the community component level.

Scoring and badging rules can be associated with any arbitrary path of the content structure.  For instance, 2 forums within a single site might operate with different scoring and badging rules, resulting in a different score and a different set of badges for each community member.

Six sample badges are provided OOTB under /etc/community/badging/images:

  • Awarded badges (quantity based) : gold, silver, and bronze badges
  • Assigned badges (role based) : publish-side moderator, group manager, and privileged member badges

See the Communities Scoring and Badges section of the documentation.

Enablement Features

The new enablement features allow for the management of training materials and their publishing to community members.

Two types of enablement materials are supported and created via a 4-step wizard:

  • Enablement resources: videos, documents, links to external URLs, links to Adobe Connect recordings or SCORM-compatible content types with associated metadata like title, description, due date and tags
  • Learning paths: ordered list of resources with associated metadata like title, description, due date, enforced order or prerequisites learning paths

Two community functions are provided for community members to access this content:

  • Assignments: each enablement resource and learning path can be assigned to any number of community members or community member groups. When assigned, these resources are listed to the current community member along with the current progress status (started, completed...)
  • Catalog: each resource and learning path can be tagged with values coming from a configurable AEM tag namespace for a particular community site. When tagged, these resources are listed to all community members in a catalog also allowing for filtering for a particular tag

Each resource and learning path is equipped with reporting features:

  • Some are based on the use of Adobe Analytics, allowing to report on the number of views, plays, comments and ratings for each resource over time
  • Some are based on the assignments, allowing to report on the progress status for each resource or learning path, along with the associated score if implementing the SCORM standard
  • Reporting on assignments for a particular member of member group is also provided
  • All reports can be exported in .csv format for subsequent processing

Important note: the use of the assignments feature requires the additional SCORM package for AEM Communities and some additional licensing. 

To get started, visit the Getting Started with AEM Communities for Enablement tutorial.

Details are provided in these sections of the documentation :

Critical Changes

  • The SocialUtils API was deprecated in 6.1
  • The JSRP persistence option is now supported for production use as long as a publish-side cluster can be deployed
    • UGC entered in publish environment will not be visible in author (and vice-versa)
  • The assigments function is one of the enablement features and requires the installation of MySQL and the optional SCORM package and some additional licensing.  See the Configuring Enablement Features and Assignments Function sections of the documentation.

Demonstrations

All these features can be demonstrated using the AEM Demo Machine available publicly on GitHub.com when using the AEM Communities demo scenario and also within the new We.Retail reference implementation.

Feature Pack 1

This feature pack includes fixes, new features, and improvements for the AEM 6.2 Communities release.  

Key new features include :

  • Nested groups and sub-communities
  • Multilingual sites
    • ability to setup global shared store to enable single threaded conversation for UGC
    • ability for site visitor to select preferred language for browser
    • inline translation options automatically shown to user when selected language differs from content
  • Leaderboard component
  • Email subscriptions
  • UGC content fragments
  • Badge console

This feature pack also includes several improvements and changes for :

  • Community sites
    • one-click export of community site as package
    • improved search with hints and quick tips
    • new sorting mechanisms
    • improved pagination
  • Calendars
    • creation of events by privileged members
    • event page supports social sharing
  • Member Management
    • added columns showing member activity
    • exportable as CSV
  • Notifications
    • new settings for activities to follow
    • new email notification
  • Enablement Resource Catalog
    • can be made available to anonymous site visitors
    • improved controls from Resources console
    • ability to specify images to represent resource in published catalog
  • Forums
    • ability for community manager to pin posts to top of forum
  • Moderation console
    • ability to transform UGC post into content fragment for use in various web experiences

Demonstrable in new We.Retail AEM sample.

Feature Pack 2

This feature pack includes fixes, new features, and improvements for the AEM 6.2 Communities release.

  • For Community Members
    • Prevent spam and flooding
    • View assigned and earned badges
    • View, like and comment on ideas
    • Submit new ideas
  • For Community Moderators
    • Review ideas
    • Feature relevant content
    • Bulk moderation using Coral3
  • For Brand Managers
    • Add featured content components
  • For Community Administrators
    • Edit Community Groups structure from author
    • Manage badges for Community members
    • Configure contribution limits for new members
    • Configure SRP for database support (DSRP, MySQL)
    • Configure dispatcher support for guest users with TTL

Feature pack 2 encompasses all enhancements released in the previous feature pack.

Feature Pack 3

This feature pack includes fixes, new features, and improvements for the AEM 6.2 Communities release.

  • improved member self-registration
  • recover password/ID
  • email verification
  • migration tool
  • ability for allow any member to view enablement resources and learning paths in the catalog
  • social login update for Facebook API change (v2.2 not supported as of 3/25/2017)
  • all fixes and improvements from previous versions

Any questions?

Have a question about this or any other AEM topic? Ask our Community.
Learn more about AEM topics on our help hub.
Was this helpful?

By submitting your feedback, you accept the Adobe Terms of Use.

Thank you for submitting your feedback.