Accessing Communities Components

When authoring page content, if the underlying template permits changes to the design of the page, it is possible to enable components that are not already available in the components browser as part of the site design.

If not familiar with the touch-optimized UI, view the documentation on basic handling.

Entering Design Mode

If a Communities component is not found in the components browser (sidekick), it will be necessary to enter Design Mode to add other Communities components. Required client-side libraries (clientlibs) may also need to be added.

Following are images of using the touch-optimized UI to select a few Communities components and viewing them in the components browser :

The selected components are now available in the components browser :

Required Clientlibs

Client-side libraries (clientlibs) are required for the proper functioning (JavaScript) and styling (CSS) of a component.

When adding a Communities component to a page, if the result is an error or an unexpected appearance, the first thing to try is adding the required clientlibs for the Communities component. For details, see Clientlibs for Communities Components.

Example : initially placed reviews without client libraries ...

... and with client libraries

Tagging

Many Communities features may be configured to allow members to tag content entered (posted) in the publish environment.

If tagging is allowed, the community site's configuration may be set to limit the namespaces presented to members in the publish environment. See the Community Sites console.