Lightning Communities: Community Builder Improvements with Turnkey Themes, Progressive Rendering, and Audience Deletion

Change the look and feel of your Lightning community with a few clicks using ready-made themes in Lightning Builder. Control your community’s first impression by using Progressive Rendering to determine which components get priority loading. Delete audiences when you no longer need them.

Update Your Lightning Community to the Latest Template
We are always adding improvements to Lightning communities, but you can’t take advantage of them without the latest template. So if you haven’t updated yet, don’t get left behind.
Customer Service (Napili) Has a New Name
As part of the evolution and expansion of community templates, Customer Service (Napili) is now called Customer Service.
Update Your Community Look and Feel Quickly by Changing Themes
Admins and designers can now select from a library of pre-built themes and customize them with clicks, not code, using new controls in Community Builder.
Improve Your Customer’s Community Experience with Progressive Rendering
Now you have finer control of your community’s first impressions with Progressive Rendering. You can specify in which order components are displayed when the page loads to optimize your site’s speed. For instance, have material at the top of a long page display first while content that isn’t in screen view loads later.
Build and Distribute Business Solutions Using Lightning Bolt Solutions
To reflect its expanded capabilities, Lightning Bolt is now renamed Lightning Bolt Solutions. You can quickly and easily build a turnkey Salesforce solution that includes custom apps or flows, with or without a Lightning Community template or page. Distribute your solution to other orgs, or share or sell it on AppExchange.
Delete Audiences
Delete your unused or underused audiences to keep your list of audiences trimmed down to what’s current and active. When you delete an audience, all the audience assignments are also deleted. Not sure whether the audience is still in use somewhere? We’ve got you covered. We show you all the places where the audience is assigned in your published and unpublished communities so you know what to expect.
Save Navigation and Tile Menu Changes as Draft
Previously, anything you added to your live community’s navigation or tile menus published immediately. Efficient, but it did make it a bit tricky to experiment with items or try out new ideas because they went live right away. There are some things that you just don't want to go public. Now when you add items to the navigation or tile menus, they stay in a draft state until you are ready to publish. Changes to the navigation and tile menus publish along with everything else when you click Publish, and no sooner.
Display CMS Content in Your Community Using CMS Connect JSON (Generally Available)
You can now reuse blogs and articles that are already published in an external content management system (CMS). If your CMS supports JSON APIs, you can pull content into your community pages. If you used this feature in beta, we improved search engine optimization and usability. For content lists, we moved the node path from the Community Builder to the CMS Connect menu.
Configure Named Credentials for CMS Connect JSON (Generally Available)
You can access authenticated content via CMS Connect (JSON) using named credentials. If you used this capability in beta, it hasn’t changed, except that it’s available by default. No need to contact Salesforce Support to activate it.
Get Better SEO for Better Content Discovery
Public objects and fields can now be indexed by outside services for better discoverability. Get a larger audience with minimal effort by allowing external services to index public entities including content served from CMS Connect (JSON) feeds. You can control what's indexed.
Update Your <h1> Tag Overrides to <h3> for Topic Detail and Search Results Article Titles
To improve accessibility to our communities, we updated the <h1> tags for article titles in Topic Detail and Search Results components. If you’ve overridden the <h1> tags, make sure that you update them to <h3> so that they continue working.
Update Your <ui:button> Overrides for Some Lightning Community Components
We changed the <ui:button> to <lighting:button> in these Community Builder components: Case Deflection, Global Search for Peer-To-Peer Communities, Search & Post Publisher, Topic Articles by Topic, and Related Record List.

No matches found