Update Your Experience Builder Site’s Template

• Accessibility and performance improvements on the following components:
  • Navigation Menu
  • Reputation Leaderboard
  • Related Records
  • Trending Articles by Topics

If you’ve applied CSS customizations, migrate them in the upgraded components.

Overriding CSS isn’t recommended. The best way to update the styling of your components is to use the Theme panel in Experience Builder. To update existing CSS overrides see CSS mappings for updated components.

• Improvements to tooltip positioning by changing several panels, dialogs, and tooltips to use a shared container
• Updates to the Language Selector’s functionality and appearance (current preferences are maintained)
• Improvements to the property editor container
• All the changes that apply to subsequent updates
• If you’ve applied CSS customizations, migrate them to the upgraded components

Overriding CSS isn’t recommended. To update existing CSS overrides, see CSS mappings for updated components and Standard Design Tokens for Sites.

• A dropdown menu to set audiences at the component level
• Out-of-the-box UI enhancements, such as font sizing
• Upgraded Reputation Leaderboard, Trending Articles by Topic, and Related Articles. If you’ve applied CSS customizations, migrate them to the upgraded components.

  Overriding CSS isn’t recommended. The best way to update the styling of your components is to use the Theme panel in Experience Builder. To update existing CSS overrides see CSS mappings for updated components.

• A new User Profile Menu component that automatically replaces the Profile Header component in updated templates
• The base component on the Record Detail page for custom objects is replaced with a newer version for desktop view mode. If you currently have CSS overrides for record layout, keep them, and refer to CSS Overrides Migration for the Record Layout Component to add your styles and customizations to the new component
• A new Theme panel that redesigns the Branding Panel in Experience Builder.
• Additions to Theme settings that help you easily see which pages a theme layout is associated with
• More metadata options to improve discoverability of pages through SEO
• Query parameters in a site URL, other than language, no longer persist while navigating within a site
• Updates to CMS Connect (JSON) require manual updating to connections created with the Winter ’18 release.
  • CMS Connect (JSON) now autocreates detail pages. URL’s using query parameters pointing to your manually created pages continue to work. However, they aren’t accessible from the CMS Connect (JSON) Property Editor in Experience Builder.

    For better SEO and management, it is best to use the new, automatically created pages.

    • In Experience Workspaces, add a Content Type and the JSON path for both ID and Title.
    • In Experience Builder, open the Property Editor of the existing CMS Connect (JSON) component by selecting it.
    • Click Save to create and autoconfigure the new detail page.

      The standard page you created in Winter ’18 for navigation isn’t automatically deleted. If it’s not referred to by any other component, you can manually delete it from the Pages menu.

  • CMS Connect (JSON) has new configuration fields.
    • When editing an existing JSON connection, the Connection Type is Public by default and Content Type, Title, and ID are empty. Title and ID have to be filled before the connection can be saved again.

      You can have only one Content Item per Type and it’s necessary to define a Content Item for navigation support.

      • If you have multiple Content Lists and a single Content Item in an existing connection, when you edit your CMS Connection a single Content Type is created in the JSON section with the Content Item and Content Lists assigned to it.
      • If you have multiple Content Items and Content Lists, when you edit your CMS Connection you have one Content Type with a single Content Item and all of your Content Lists under it. The remaining Content Items are each in a separate Content Type.
• All the changes that apply to subsequent updates.

• Decoupling of the search box from the site header, making it easier to insert your own search experience within a site.

  The Search page in the Winter ’18 version of the Customer Service (Napili) template doesn’t include the Headline component out of the box. If your site’s Search page includes the Headline component, it’s removed as part of the upgrade.

• Sleeker header component improves your site’s mobile experience, leaving more room to show what’s important to your site.
• Out-of-the-box UI improvements, such as improved spacing in text fields.
• Streamlined new Global Search for Peer-to-Peer Sites.
• Upgraded, high-performance navigation menu that offers more styling options and reduces the need for CSS overrides. If you have applied CSS customizations, migrate them to the upgraded navigation menu.

  Overriding CSS isn’t recommended. The best way to update the styling of your navigation menu is to use the Theme panel in Experience Builder. To update existing CSS overrides see CSS mappings for updated components.

• Adoption of Lightning Design System principles in all content layouts.
• Two new branding options: Navigation Background Color and Navigation Text Color.
• All the changes that apply to subsequent updates.

• Login pages retain branding but lose custom code or component customizations.
• All the changes that apply to subsequent updates.

Most component customizations and properties are overwritten. However:

• For Koa and Kokua, general settings, such as Category Group Name, Top-Level Category, and Company Name, carry over.
• For Customer Service (Napili), topic definitions carry over.
• All the changes that apply subsequent updates.

Card Background Color (6)

Also controls card transparency