BookStack vs. Salesforce Experience Cloud

BookStack is fantastic for having business users and not-so-technically-savvy IT users. It enables them to create a documentation they like in a visual way while still forcing them to adhere to logical structure of a document. It works fine even for more technical matters such as integration guidelines, especially when these concern some of the more obscure technologies. The exported docs are presentable but lack any interactivity. Where it lacks is generating heavily technical documentations. Heavier REST or GraphQL integrations should for example be documented through other means. As for developer documentations, there are definitely more suitable alternatives, also.

Incentivized

For well-suited, this product is great for your external clientele groups that you would not necessarily want to have a high user fee rate for. So basically general public or a group that will be authorized to come in and just do a few things here and there, but you don't necessarily want them access to all of your systems and your data points for groups that it would not be a great use for. I'd say probably your high level internal staff, they're going to be using a lot of the backend functionality automations, evaluating data, managing data, and doing custom inputs. That's just not what's intended for.

Incentivized

• Documentation
• Guides
• Knowledge-base
• Version control

Incentivized

• Complete integration with the Salesforce ecosystem. Data displayed in your Community portal reflects records from a Sales Cloud organization
• Highly customizable. A Community Cloud portal can be totally customized both visually and with different funcionalities with little to no coding skills required

Incentivized

• Continuity in backward compatibility
• Dark mode
• Absent tree view

Incentivized

• The documentation for implementing Experience Cloud can be a bit confusing as their rebranding hasn't made it's way into all articles, resulting in different terminology being used to refer to the same thing
• Some things are not as intuitive regarding their customizability, so there's a bit of a learning curve (i.e. Lightning apps can't be used to customize layouts in Experience Cloud)

Incentivized

Usability is pretty streamlined, especially if you're familiar with other Salesforce products, but even if not, take it from me, as I just entered the technological space about two years ago, that this product is pretty simple to learn. You don't have to jump in with your head underwater. Small wins and learnings along the way are what foster long-term understandings and enable your evolution alongside the product. I definitely recommend Salesforce Trailhead along with it

Incentivized

It's delivered on our original requirements and we've found ways to grow its usage. We continue to build on our original success and we can report our data out to leadership to show a true return on investment which is great for growing support and expanding uses for the system.

Incentivized

We have weekly calls with our Salesforce reps. They bring new ideas to the table and help with taxonomy builds. They have also answered many questions and connected us to the right people for us to grow our knowledge and utilization of the platform. They are a good partner overall in comparison.

Incentivized

Confluence, having only a slight advantage in terms of features compared to BookStack, really only makes sense to procure as a part of the Jira bundle. It requires much more maintenance from my experience and does not really deliver any extra value aside from the very strict certifications like HIPAA. DokuWiki and MediaWiki both provided way too much in terms of customizability, not really focusing on the business need. Of course, MediaWiki was conceived for a whole different purpose but is very often seen being used for both internal and public documentation delivery. DokuWiki did not provide the authors with the user-friendly environment that BookStack has and integrated most poorly with LDAP. As for OneNote, which was used for support docs prior to BookStack, it provided the authors with too much of a user-friendly environment, rendering the product of their work very inconsistent. Also, the sharing model was either peer-to-peer or within Teams, neither of which made it easy to audit and supervise.

Incentivized

Salesforce Experience Cloud was selected due to its tight integration with our existing Salesforce CRM platform. Customization of the portal was much, much simpler compared to Sharepoint - especially with role-based security parameters that are ultimately inherited based on attributes within the Salesforce CRM platform. Salesforce Experience Cloud was a natural fit for this customer-facing purpose.

Incentivized

• Spillover within Business IT staff up, nearly double substitutability. This is through the ability of a support technician servicing a different product to find a guide describing how to solve the more frequent issues the way a product lead would do it.
• Time to draft and publish a documentation down some 20% compared to previous solution.
• OpenSource that integrates fine with enterprise-grade software and somehow even passes security audit. 20 times cheaper to implement compared to Confluence, almost free to maintain.

Incentivized

• Improved online admission application completion rates from mid-60%s to mid-80%s.
• Positive user experience from start-to-finish to leverage one data system for all prospective student data
• Fewer data integrations transforming and loading sensitive student data by leveraging Salesforce Community Cloud to access already existing data

Incentivized