Community Component Pack Quick Start

Getting started with the Community Component Pack.

Product Information

Release Notes

Slider

Introduction

Forcivity’s Community Component Pack gives you the ability to create impact experiences for your communities with clicks, not code.

Benefits

  • Allows more design freedom, without creating, and then maintaining, custom components, or HTML.
  • Create great looking designs and experiences for you Salesforce communities.
  • Simple to use; drag, drop, and configure.

How the Community Component Pack Works

Once installed, the new components are available with Builder under the Custom Components list.

  1. Open the page to edit in Builder.
  2. Select the from the Custom Component list.
  3. Configure the component using the attribute panel.
  4. Preview your changes.
  5. Publish the community.

Installation

Focivity’s Community Component Pack can be installed through the App Exchange in a matter of minutes with very little added configuration needed. 

Like any other native Force.com application, the Community Component Pack uses the Force.com standard installation process.

Install:

  1.  During installation, determine who should have access to the Community Component Pack by simply selecting either Full Access or No Access for each profile in the list.
    -OR-
    You can also elect to install the Community Component Pack for Admins Only (recommended) or All Users.
  2. The Community Component Pack will automatically install into your Salesforce.com organization in a matter of minutes.
  3. Once the installation is complete, simply click ‘Done’ to return to Salesforce.com.

Sandbox refreshes
All Community Component Pack settings will persist across a Sandbox refresh. There are no added steps needed to configure the Community Component Pack to work in your Sandbox.

Back to top

Creating and Configuring Components

While most of the components within the Community Component Pack are just drag and drop, the following components need additional configuration work.

Configuration Notes:

Create reusable configurations for use within Community Builder.

  • Changes made to configurations immediately update the component when the component is saved. That is why we recommend testing changes in a sandbox and deploying the changes.
  • Images need to be added to a changeset (Asset Files) when deploying to another org (production site).
  • Images are stored within the Asset Library under Libraries.
  • Blank fields are not shown unless a value is entered.
  • Best practice is to use relative links (e.g., /s/support) from community pages so you can move configurations between orgs. If you are linking to an external site, use and absolute link and open in a new window.

Images and Libraries

Certain components (Hero, Two Column with Image, Tiles) us images. These images are stored in the Files / Asset Library.

  • You can reuse images already stored in your Files / Asset Library folder.
  • Insure you can add a folder in the Asset Library. Recommended to create a folder (e.g., Community Components) to make these files easier to manage.
  • Insure you have public file sharing enabled and you have set your library member permissions appropriately. Note: If you use a Library_Adminstrator role for your library members, insure you have reviewed that role’s rights (this can only be done Classic, and search for Content Permissions).

Community Builder

Use the configurations to drive the community components.

  • All the Forcivity Community Components are located under the Custom Component section under the Components tab.
  • Once you drop the component on the page, you then can select the configuration.
  • If you make changes to the configuration, just refresh the page.
  • Configurations can be reused.
  • Each component has top and bottom margin setting to better help to align your components.

Testing and Deploying Components

While most of the components within the Community Component Pack are just drag and drop, the following components need additional configuration work.

Testing

  • Use a sandbox to test your component configurations.
  • When deploying, the community pages can be deployed via a changeset for community page changes.
  • The component configurations can be exported and then imported into your production org.
  • For more details, see Deploying Community Changes.

Additional Resources

Back to top

Need Help?

Have an issue or question with one of our products?