BookStack vs. RWS Tridion Sites

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

Love the product and I really like how we use it for public sites. The only negative aspect is that it is just hard to find Tridion devs that understand the tool, grasp .net, react, and understand the blueprint, etc.

• Documentation
• Guides
• Knowledge-base
• Version control

Incentivized

• Makes it easy to spin up a new site quickly
• Allows for numerous users to work on the same site without conflicting with each other's changes
• Allows you to unpublish changes or revert to old versions if you make a mistake
• Allows you to time publishing actions (for example, you can set it to happen overnight)

Incentivized

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

Incentivized

• Tridion is complicated in enough ways that it makes it difficult to train new users. Therefore, we have to limit the number of people with access to the system since we have not yet implemented Workflow.
• When something goes wrong (items fail to publish, or there is unexpected behavior with components), there is little explanation provided that would point us in the right direction to troubleshoot. As a result, content Authors and Editors have to frequently ask for IT assistance.

I am giving this a semi-high rating because we have already got Tridion up and running and we are still in the process of moving the sites over to Tridion. It is unlikely we will be moving things to a new CMS AGAIN in the near future as the cost to get Tridion was high.

The editor user interface is very user friendly and in-site editing makes simple updates fast and easy. The extensibility of Tridion is a big plus and the ability to add our own options into the default Tridion interface helps us integrate with external systems. Finally, the user permissions and security system helps us deploy it within our large organization.

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

It is a nuclear missile compared to the other handguns and knives on the market today. But it also requires nuclear technicians and expertise that a handgun doesn't require. Do you need to decimate your competition and you have the investment capabilities necessary to put a nuclear missile into the sky? Then definitely do it. Especially if you need a very good multi-lingual blueprint provider like Tridion.

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

• SDL is a very complex system. Creating custom components by external vendors turned out to be expensive.
• The learning curve is very slow, so training takes a lot of time and cost.
• The revamped corporate site looks clean, modern, and is mobile-friendly.

Incentivized