Use the author instance to create a new community site
The Communities Sites console provides a wizard to guide one 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:
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:
Getting Started Tutorial
Community Site Description:
A site for engaging with the community.
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: engage
Template: pull down to choose
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, moderation, group management, analytics, translation and enablement.
Visit the Getting Started with AEM Communities for Enablement tutorial to experience working with the enablement features.
Check all checkboxes for User Management
For a production environment, it is necessary to create custom Facebook and Twitter applications. See Social Login with Facebook and Twitter.
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).
If Adobe Analytics is licensed and an Analytics cloud service and framework have been configured, then it is possible to enable Analytics and select the framework.
The Translation settings specify the base language for the site as well as whether or not UGC may be translated and into which language, if so.
Leave empty when creating an engagement community.
For a similar tutorial to quickly create an enablement community, see Getting Started with AEM Communities for Enablement.
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 to open it, hover over the site icon such that four action icons appear:
On selecting the fourth ellipses icon (More Actions), 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 (for example if your publish server is running on your local machine, then 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.
select the delete icon to delete the community site from within Communities > Sites console. This action removes all the items associated with the site, such as UGC, user groups, assets and database records.
If not using the default port 4503 for the publish instance, then edit the default replication agent to set the port number to the correct value.
On the author instance, from the main menu
For example, to use port 6103:
Force Retry to reset the replication queue
After ensuring the publish server is running, select the world icon to publish the community site.
When the community site has been successfully published, a message briefly appears:
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 “engage” in Step 1, the four new user groups may be seen from the Groups console (global navigation: Communities, Groups):
Notice that Aaron McDonald is a member of
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, sign in with administrator privileges
Browse to http://localhost:4503/crx/de
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.