The state of Ohana for Salesforce Commerce Cloud

Within Salesforce, the Ohana (Hawaiian for Family) has a pretty significant meaning. Over the past decade, people passionate about Salesforce have built up an enormous community around the platform.

The number of people helping each other every day on Trailblazer Communities, Twitter, Stackexchange, OhanaSlack, and more is just amazing.
But then again, how does this reflect on the Salesforce Commerce Cloud B2C community?

Demandware

Let us start with a little bit of history. Salesforce Commerce Cloud B2C didn’t exist before 2016, and then it was still known as Demandware.

It is no secret that Salesforce is known for buying companies to take under its wing, and Demandware was no different. A bit of rebranding later, and “boom,” it’s Salesforce!

The older Demandware logo, from before the acquisition of Salesforce.

A big Difference in Ohana

I listed a few places where the community was active within the #ohana of Salesforce, so how do the different platforms compare? Based on my personal experience, the used communication channels show a big difference.

Note: This is a “personal feeling” pie chart as I did not use any scientific methodology by comparing numbers etc. So take it with a grain of salt! I also left out LinkedIn as it is more business than questions/answers than socializing on Twitter.

Core Platform

SFCC

Looking at the above charts, it is pretty clear that there is a significant difference in the way people ask questions and communicate within the #Ohana. 

Twitter

I became active on Twitter a little less than a year ago to get in contact with more people who have an interest in Salesforce.

And boy, a lot is going on there:

  • Ohana Pears: Helping to grow & nurture friendships within Ohana 
  • shirtforce: Giving through tees
  • SnailMailStickerSwap: Exchanging Salesforce related stickers through Snail Mail
  • And the list goes on and on…


Of course, the main drivers of these are Salesforce CRM Administrators. But does it end at the Salesforce platform? No! All of the groups mentioned above have a target group containing all clouds! So don’t be afraid to mingle 😁.

Maybe we should turn in a design for #shirtforce?

A second class citizen of Salesforce Ohana

Over the years, a part of the community has felt they are not part of the “bigger” Ohana picture. Things like voting on the feature prioritization and MVP seem like an impossible/pointless task as the smaller B2C community can not even make a dent in the “Salesforce CRM” vehicle.

But is it also so surprising? The B2C community is also more isolated and not by its fault looking at the history.

Xchange

The first community within Demandware / SFCC is undoubtedly the Xchange, discontinued and all of its histories erased! It has left many people annoyed as it contained a vast amount of knowledge that people were willing to share with their peers.

A screenshot of Account Manager roles & permissions showing the old Xchange.

I found this community (even though it was not as active as the Trailblazer Community is) a beneficial tool to find my way in the world of Salesforce Commerce Cloud. I still find myself assigning the role to every account in Account Manager in nostalgia, even though it does not do anything anymore.

Commerce Cloud Developer Site

In replacement of the Xchange came the communities on the developer site. A group of communities separated from the Trailblazer Communities, and it is far less active than the Trailblazer ones.

But why is that? Is it because people don’t know it exists? It is pretty hidden. If people even know the site exists at all. 

If you are not actively working with the headless SCAPI/OCAPI options, you wouldn’t be searching on this site.

Daily, people are asking questions, but not many people are answering (besides people from Salesforce) and a few others, including me. So maybe people get discouraged from asking more questions because it is always the same people answering?

Salesforce Developer Portal

The logo of the Trailblazer Community Groups

And this year (2022), all of that information is moving again! The Commerce Cloud Developer Site did not live a long life, but that might be for the best as it had its issues.

And we will also be merging more and more into the “General Population” together with all of the other products, which might bring some more exposure within the main #Ohana!

Also, some good news: this time, the Community Groups will not disappear and will also be migrated into the Trailblazer Community!

Yeeey, all of the work I put in answering people’s questions is not going into the Garbage Bin!

Slack to the rescue

Looking back at this blog post, it all seems to have a “negative” tone. But all of this has had a tremendous impact on our primary communication channel: Slack!

A large community of people active in the Salesforce Commerce Cloud world chatting away with each other and sharing their wins, challenges, and grievances. Questions are asked on an hourly basis on different topics and get answered quickly, or at least getting pointed in the right direction.

In the past year, many people of the mothership have joined in as well—a big shout out to the Salesforce Commerce Cloud team for being active within the community (headless, PWA-kit, documentation, business manager, Page Designer, …). And not to forget our excellent admin team for bringing everyone together!

All I want to say to the Slack community is

A drawing of Salesforce mascots waving with a

Join the Slack Community

Take this moment to join a growing community of Salesforce Commerce Cloud enthusiasts!

A picture of the booths at Salesforce Connections 2019 in Chicago

Table of Contents

Facebook
Twitter
LinkedIn