When comparing BookStack vs Trilium Notes, the Slant community recommends Trilium Notes for most people. In the question“What is the best single-user wiki?” Trilium Notes is ranked 6th while BookStack is ranked 19th.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Clean & simple default interface
The stock interface design has a modern feel and is simple for new users to use.
Pro Free and open source
Released under the MIT license.
Pro Full role and permissions system built in
Granular permissions can be set up for specific roles on a per-content basis and permissions will waterfall down to child content.
Pro Multilingual
Over 9 different languages are built in to BookStack which can be set at a per-profile level.
Pro Feature rich and stable
Markdown editing, syntax highlighting, WYSIWYG, keyboard shortcuts, versioning, SSO, LDAP, different roles, performant and fast developer response.
Pro Support for domain authentication
Can be deployed within an active directory environment with its features to connect over LDAP.
Pro Supports SSO using Google Apps
Very convenient when you're a company that uses Google Apps, that makes logging into Bookstack more secure and more convenient.
Pro Note encryption
Pro Free and open source software
Pro Excellent WYSIWYG interface
Pro Attributes that can be assigned to nodes and inherited
Pro Graph of node connectivity
Pro Note versioning
Pro Synchronization with a server
You can set up synchronization but you need a server to do this.
Pro Database storage rather than files
This enables the tool to do a lot of things that would be difficult with plain text file storage.
Pro Archival functionality
Cons
Con Limited customisability
Customisation options are limited with only the main theme color, logo and name being customisable.
Con No support for readable markup languages
The content entered through the WYSIWIG editor is stored as HTML. The HTML can be edited directly, but no other markup language is parsed. Speak ReST, Markdown, etc.
Con Limited to 2 levels of content
Bookstack implements a "Book / Chapter / Page" system which works fine, but lacks flexibility when you need to have more levels of imbrication.
Con Complicated installation
The current installation process involves many steps and may be a lot to take in for people not familiar with setting up Laravel applications.
Con Interface can be confusing
There is a fair amount of flexibility to the interface but it can also become confusing, especially when some parts are not necessarily simple to use. Most of the basic features nevertheless are intuitive.
Con Database storage rather than files
This makes it a little less simple to work with (also has benefits).
Con Not markdown
It will import and export markdown but it does not store content as markdown. This isn't necessarily a problem if you don't need it.
Con Synchronization requires use of Trilium's sync server
This can be problematic to set up unless you have a web server that will support the requirements of this.
