10/23/18 Decide On and Implement a Documentation Tool
This is the first blog entry for the documentation for the Monorepo Boilerplate project that is currently in development. My first decision in creating the project is to start by outlining different documentation tools and deciding on which to move forward with.
The Options
After some initial research, it seems like there are quite a few good documentation tools out there that could meet our needs. The table below outlines the different tools and their benefits and considerations for our use case.
Tool Name | Benefits | Considerations |
---|---|---|
Gitbook ⭐ |
|
|
docsify ⭐⭐ |
|
|
docz ⭐⭐ |
|
|
docusaurus ⭐⭐⭐ |
|
|
Gatsby ⭐⭐⭐⭐ | I did not officially consider Gatsby. It would be a great candidate if we needed that level of configurability and customization, but it seemed like overkill. | -- |
The Verdict - Docusaurus
When I finally got into the weeds with the different tools they started to show their true colors. I wanted to like docz
the most but it ended up having issues that I felt like warranted caution in proceding with use. (See the considerations for docz
above). My second choice was docusaurus
largely for the powerful support community of Facebook
and it turned out not to disapoint. It's easy to set up and use and allows for great customization, but isolates it when it's unecessary.