> How does this compare to other well-established SSGs (Sphinx, Hugo, Jekyll, etc.)? Looks like this has a GUI, for one, which is potentially a big selling poi

> How does this compare to other well-established SSGs (Sphinx, Hugo, Jekyll, etc.)? Looks like this has a GUI, for one, which is potentially a big selling point for the not-so-technical crowd. I know there are headless CMS tools out there that you can hook up to almost any SSG, but even getting that set up is way too big of a stumbling block for the kind of tech writer who doesn't want to tinker or use the CLI or any of that. At that point you'd probably just opt to use Zendesk or whatever (boo). > What does this tool offer that would make it worthwhile to switch? Even with the GUI stuff, I'm also wondering whether there's anything here enticing enough to switch. If your docs are already entrenched in some other ancient tool, it can be hard to get the resources/support to switch even if you want to switch, which many writers may not. OTOH anyone who wants to do docs-as-code probably already is, and the kinds of environments where docs-as-code thrives are the kinds of environments where it's not unreasonable to ask your writers to learn Git.