Community Site creation employs a wizard which guides you through the steps of creating a community site. It is possible to move forward to the
Backto the previous step before committing the site in the final step.
To get started creating a new community site:
Using the author instance
Sign in with administrator privileges
Navigate to Communities > Sites
On the Site Template step, enter a title, description, the name for the URL, and select a community site template, for example:
Community Site Title:
Community Site Description:
A site for enabling the community to learn.
Community Site Root: (leave blank for default root
Cloud Configurations: (leave blank if no cloud configurations are specified) provide path to the specified cloud configurations.
Community Site Base Language: (leave untouched for single language: English) use the pull down menu to choose one or more base languages from the available languages- German, Italian, French, Japanese, Spanish, Portuguese (Brazil), Chinese (Traditional), and Chinese (Simplified). One community site will be created for each language added, and will exist within the same site folder following the best practice described in Translating Content for Multilingual Sites. The root page of each site will contain a child page named by the language code of one of the languages selected, such as ‘en’ for English or ‘fr’ for French.
Community Site Name:
the initial URL will be displayed underneath the Community Site Name
for a valid URL, append a base language code + “.html”
for example, http://localhost:4502/content/sites/
Reference Site Template: pull down to choose
Reference Structured Learning Site Template
The Design step is presented in two sections for selecing the theme and branding banner:
Select the desired style to apply to the template. When selected, the theme will be overlayed with a check mark.
(optional) Upload a banner image to display across the site pages. The banner is pinned to the left edge of the browser, between the community site header and menu (navigation links). The banner height is cropped to 120 pixels. There is no resizing of the banner to fit the width of the browser and 120 pixel height.
On the Settings step, before selecting
Next, notice there are seven sections providing access to configurations involving user management, tagging, roles, moderation, analytics, translation, and enablement.
It is recommended that enablement communities be private.
A community site is private when anonymous site visitors are denied access, may not self-register, and may not use social login.
Ensure most checkboxes are unchecked for User Management:
Further, selecting Tag Namespaces for the community site limits the selection presented when defining catalogs and enablement resources. See Tagging Enablement Resources for important information.
Finding namespaces is easy using type-ahead search. For example,
Community member roles are assigned through the settings in the Roles section.
To let a community member (or group of members) experience the site as the community manager, use the type-ahead search and select the member or group name from the options in the drop-down.
Tunnel service allows selection of members and groups existing only in the publish environment.
Accept the default global settings for moderating user generated content (UGC).
From the pull-down menu, select the Analytics cloud service framework configured for this community site.
The selection seen in the screenshot,
Communities, is the framework example from the configuration documentation.
The Translation settings specify whether or not UGC may be translated and into which language, if so.
For an enablement community, it is necessary to identify one or more Community Enablement Managers.
(required) Members of the
Community Enablement Managers group are available to be selected to manage this community site.
Marketing Cloud Org Id
(optional) The ID for an Adobe Analytics account which is necessary when including Video Heartbeat Analytics in the enablement reporting.
When the process completes, the folder for the new site is displayed in the Communities - Sites console.
The created site should be managed from the Communities - Sites console, the same console from where new sites may be created.
After selecting the community site’s folder, hover over the site icon such that four action icons appear:
On selecting the ellipses icon (More Actions icon), Export Site and Delete Site options show up.
From left to right they are:
Select the pencil icon to open the community site in author edit mode, to add and/or configure page components
Select the properties icon to open the community site for modification of properties, such as the title or to change the theme
Select the world icon to publish the community site (to localhost:4503 by default)
Select the export icon to create a package of the community site that is both stored in package manager and downloaded.
Note that UGC is not included in the site package.
To delete the community site, select the Delete Site icon that appears on hovering the mouse over the site in Communities Site Console. This action removes all the items associated with the site, such as UGC, user groups, assets and database records.
Select the world icon to publish the community site.
There will be an indication the site was published.
Along with the new community site, new user groups are created which have the appropriate permissions set for various administrative functions. For details, visit User Groups for Community Sites.
For this new community site, given the site name “enable” in Step 1, the new user groups that exist in the publish environment may be seen from the Communities Members & Groups console:
On author, with the tunnel service enabled, it is possible to assign the users created during Initial Setup to the Community Members group for the newly created community site.
Using the Community Groups console, members can be added individually or added through membership in a group.
In this example, the group
Community Ski Class is added as a member of the group
Community Enable Members as well as member
Navigate to Communities > Groups console
Select Community Enable Members group
ski into the Add Members To Group search box
Select Community Ski Class (group of learners)
quinn into the search box
Select Quinn Harper (enablement resource contact)
Once a site has been configured and pushed to publish, configure login mapping (
Adobe Granite Login Selector Authentication Handler) on the publish instance. The benefit is that when login credientials are not entered correctly, the authentication error will redisplay the community site’s login page with an error message.
Login Page Mapping as
When working with the publish site for demonstration purposes, it might be useful to change the default home page to the new site.
To get started
On publish, access CRXDE and sign in with administrator privileges
In the project browser, expand
Select Create Node
(Do not use
With newly created
localhost.4503 node selected
(Must end with ‘$’ char)
Select Save All
(optional) Delete the browsing history
Browse to http://localhost:4503/
To disable, simply prepend the
sling:match property value with an ‘x’ -
xlocalhost.4503/$ - and Save All.
If unable to save changes, be sure the node name is
localhost.4503, with a ‘dot’ separator, and not
localhost:4503 with a ‘colon’ separator, as
localhostis not a valid namespace prefix.
The ‘$’ at the end of the regular expression
sling:matchstring is crucial, so that only exactly
http://localhost:4503/ is mapped, else the redirect value is prepended to any path that might exist after the server:port in the URL. Thus, when AEM tries to redirect to the login page, it fails.
After the site has been initially created, authors may use the Open Site icon to perform standard AEM authoring activities.
In addition, administrators may use the Edit Site icon to modify properties of the site, such as the title.
After any modification, remember to Save and re-Publish the site.
The community site template chosen for this community site should contain the catalog feature.
If not, the catalog function can easily be added. This would allow other members of the community, not assigned to enablement resources or a learning path, to select enablement resources from a catalog.
If the site structure does already contain the catalog feature, its Title can be changed.
To modify the site’s structure, navigate to the Communities, Sites console, open the
enable folder, and select the Edit Site icon to access the properties of
Select the STRUCTURE panel to add a Catalog or modify an existing Catalog:
Select All Namespaces: leave as default.
Use the Position Icon to move the Catalog function to the second position, after Assignments.
Select Save in the upper right corner to save the changes to the community site.
Then re-Publish the site.