Start tracking your progress
Trailhead Home
Trailhead Home

Configure a Page Designer Page

Learning Objectives

After completing this unit, you’ll be able to:
  • Explain the difference between the Page Structure and Components views.
  • List three important Page Designer configuration settings.
  • Note two ways you can control how you display or hide a component.
  • Explain how to upload content files.


Brandon is eager to scope out Page Designer’s Visual Editor, which is in Business Manager, the Salesforce B2C Commerce configuration and management tool.

In this module, we assume you are a B2C Commerce merchandiser with the proper permissions to perform these tasks. If you’re not a B2C Commerce merchandiser, that’s OK. Read along to learn how your merchandiser would take these steps in a staging instance. Don’t try to follow our steps in your Trailhead Playground because B2C Commerce isn’t available in the Trailhead Playground.

If you have a staging instance of B2C Commerce, you can try out these steps in your instance. If you don’t have a staging instance, ask your manager if there is one that you can use.

Brandon uses the page and component types that come with the Storefront Reference Architecture (SFRA) to create a page with two components: a banner and a carousel.

Create a Page

Here’s how he creates and configures his page.

  1. Open Business Manager.
  2. Select your site, or if you are reviewing what comes in the reference code, select RefArch.
  3. Click Merchant Tools > Content > Page Designer. In Business Manager, the Page Designer main page. You see the Page Designer landing page with a list of the pages created.
  4. Click New. A Page Designer new page.
  5. Select the language: default (already selected).
  6. Enter a name: Cloud Kicks Homepage. Page Designer creates the ID as you type the name.
  7. Enter an optional description: Cloud Kicks Homepage.
  8. At least one page type displays. If your developer created customized page and component types, you see other page types. For now, select the page type: Storefront Page. (This is the sample page type that comes with SFRA.)
  9. Click Save & Create.

Configure General Settings

Now that Brandon created his page, he can configure the general settings.

  1. Click the Page Settings icon. Page Settings icon.
  2. The Page settings dialog opens. Page Designer, Page settings dialog.
  3. On the General tab (already selected) select Searchable in storefront, and then rebuild the content index.
    • Select Merchant Tools > Search > Search Indexes.
    • Select Content Index.
    • Click Rebuild.
  4. Select Included in sitemap.
    • Set the change frequency to Weekly. This indicates to search engines how frequently the page might change.
    • Enter a priority of 1. This helps search engines determine which pages to crawl first. The highest priority is 1. The number must be from 0.0 to 1.0.
  5. Click the Localization tab and select that the page is visible for this locale. The locale is default. You can use this setting to test new locales. We get into more details about locales soon. In Page Designer, select the local and visibility for that locale.
  6. Click the Targeting tab. In Page Designer, select the customer groups and schedule.
    • Select a Customer Group: Big Spenders
    • Select the Display to and from dates. The times correspond to the shopper’s browser time, and not the storefront’s instance time.
  7. Click the SEO tab. This is how you can make sure external search engines find your awesome new pages. Configure pages for search engine optimization (SEO) by specifying the URL, title, description, and up to 10 metadata keywords. In Page Designer, select the seo settings.
  8. Click Save.

Add a Component

Brandon adds a component to his new page. As you follow along with him in Business Manager, some of the component types you see can be similar to those that your developer created. Brandon uses the SFRA sample component types for now.

Here are the steps he takes.

  1. Open Business Manager and Page Designer.
  2. Select the Home Page Cloud Kicks page.
  3. Click the Components Components icon. icon.
  4. Select the component Main Banner, and drag it into a region on the page. Page Designer component list.
  5. In the right pane, configure the attributes.
  6. Click the folder icon and add an Image. For the Main Banner component, add a graphic.
  7. Scroll down and add the overlay text. For the Main Banner component, add overlay text and select a category for a category link.
  8. You can format the text using Heading1, Heading2, Heading3, Heading4, and Paragraph tags. When the browser displays the page in the storefront, it formats the text specified by the styles in the CSS files.
  9. Add a category.
    • Click the plus sign beside the Category Link field to select a category.
    • Drill down to find the category.
    • Click the plus sign beside the one you want. The check mark indicates success.
  10. Click Add to Page. The new page displays in the center pane. This is what appears on the storefront. Page Designer’s three panes, showing Brandon’s picture.

You can see how excited Brandon is to use this capability.

Notice the little circle on the graphic in the right pane. You can move the circle to change the focus.

Target a Component

Brandon can control when B2C Commerce displays his page and to whom. Here’s how he does it.

  1. In Page Designer, open the Main Banner Component.
  2. Click the dropdown at the top of the component editing pane. In the Page Designer Component page, configure customer groups and a schedule.
  3. Click Customer Group, and select one or more customer groups.
  4. Click Schedule and specify the to and from dates. You can also rename or delete the component.

What About Locales?

Cloud Kicks is expanding internationally, and that means reaching shoppers in their own language. B2C Commerce is designed for localization, and Page Designer uses this capability. Brandon starts by defining a fallback hierarchy in Business Manager. For example, he configures this hierarchy.

fr_CA (French Canadian) > fr (French) > default

It’s a best practice to create text in your base language, and name it default. Then, when you create a page, B2C Commerce adds a variant of the page to its database for each locale in the fallback hierarchy as configured in Business Manager. You can use these page variants to localize components for each locale.

Brandon creates his content in his base language, which is English, and leaves localization to the experts. When he creates a Page Designer page in the default locale, B2C Commerce also creates page variants for fr_CA and fr. He can localize content for each page variant at the component level, or show the content for a component according to the fallback hierarchy.

Until he receives the localized French Canadian text and images for a component on the French Canadian (fr_CA) page from his translator, B2C Commerce displays French (fr) content on that page. If he doesn’t have the French (fr) content, B2C Commerce automatically shows the default content.

Brandon finds it easy to check what's happening with his locales in Page Designer as he takes the next steps.

  1. Open Business Manager and Page Designer.
  2. Select the Home Page Cloud Kicks page.
  3. Select the Main Banner Component. In Page Designer, the Main Banner Component.
  4. Select the fr-CA locale and enter localized text. The page banner displays the fallback hierarchy for the locale.
  5. Move your mouse over each component on the page. A pink box encloses Page Designer components with no localized content, and labels them Fallback.
    • A pink box encloses components with no localized content, and labels them Fallback, which means that the content displays according to the fallback hierarchy.
    • A blue box encloses localized components.
  6. Select the component that you want to localize.
  7. In the right pane, change the text or images.
  8. Click Save. A blue box encloses the localized component.
  9. To delete the localized component and use content from the fallback hierarchy, select Revert to fallback beside the name of the component in the right pane. Reverting to fallback permanently deletes the localized version of the component.
  10. To hide or show the page for a locale, select Visible for this locale or Hidden for this locale.

Next Steps

In this unit you followed along with Brandon as he created a new Page Designer page with the first of two components. You also learned how to specify customer groups and a schedule for the component to control when and to whom it’s visible. Next, Brandon adds another component with a different set of attributes to his page. He also learns how to upload content assets from his local machine.