Differences Between Lightning & Visualforce Communities

For awhile now, there’s been lots of chatter (pun intended!) around Salesforce Lightning Communities and the capabilities have only been growing stronger over time. In fact, with each release, the reasons you thought you needed a Visualforce Community are waning. In fact, I’m in total agreement with my colleague, Kara Allen, in predicting the end of use of Visualforce Communities, and you can read why below:

Reasons to Use Lightning Communities

Faster to Go-Live

With Template / Lightning Bolt solutions, custom themes, and pre-configured components, it’s as simple as dragging and dropping the right pieces in the right spots and clicking Publish. Admittedly, it’s not often that easy, but even if you require custom functionality, or extensive branding to be applied, it can still shave months off a project compared to a Visualforce solution.

Reduces Maintenance Costs

In most cases, you won’t need a developer to maintain your community, especially if you just want to update a description, a translation, or an image. It can all be done by a community admin with no coding experience required, and minor WSYIWYG training. Salesforce has continually improved the Builder user experience, including introducing the Community Workspaces in the Spring ’17 release, and centralized branding properties in the Summer ’17 release. Even with custom Lightning components, you can surface attributes that are editable within the builder – no need to go into the code!


Originally posted on Perficient’s Salesforce blog, I encourage you to read the rest of the article by clicking here.

Leave a Reply

Your email address will not be published. Required fields are marked *