I like it. Clean looking theme. You won't hear me complaining if someone makes it easy for people to make good documentation.
Static site builders are just annoying enough to use that it's a barrier to keeping documentation updated. You have to have a GitHub repo, write in markdown, and commit changes which means that nontechnical people can't really help keep documentation up-to-date.
I didn't see it in the demo, but how does it handle code snippets? That's the biggest pain-point I have with keeping documentation in WordPress.
Helpie is a WordPress plugin, so it can use WordPress' Text Editor or even work with the many amazing Visual Page Builders for WordPress. Putting that together with Helpie's Insights, Search, User Access Control and other features, you have a better overall solution with so many integration possibilities.
* The Timber plugin provides an API for clean separation of concerns (lib classes for posts/pages as a model layer, Twig templates for views) and lots of elegant helper functionality to boot. It also includes an undersores-like starter theme that you can copy to take start taking advantage of the plugin's API immediately. Learning Timber is an investment for sure, but it is the single most valuable investment I've ever made in any WordPress-related tech. [0]
* Pantheon is a PaaS for WP and Drupal. [1]
* Lando (beta) [2] and its predecessor Kalabox [3] are container-based dev environments with tight integration with Pantheon.
But I spent a good chunk of the last two weeks messing around with kalabox and lando.... I do a whole lot of WP work, and I find that running the amp stack directly on macOS is a lot easier then containerizing things on several levels. I don't have to work with earlier versions of PHP or test against mySQL or Maria directly, so that's probably a pain point I will find eventually, though.
Static site builders are just annoying enough to use that it's a barrier to keeping documentation updated. You have to have a GitHub repo, write in markdown, and commit changes which means that nontechnical people can't really help keep documentation up-to-date.
I didn't see it in the demo, but how does it handle code snippets? That's the biggest pain-point I have with keeping documentation in WordPress.