Viewing profile — NiklasBegley

You're correct - Doctave Studio is for making local development easier. It packages the whole "authoring environment", so it's all you need to start writing. It's technically not W…

Oops. Good catch.

I think this is a really good point in the post: > If you don’t review, check, and merge docs the same way your org reviews, checks, and merges code, you’re not doing docs-as-code …

I also want to give a shout out to the Rustler folks for creating a great library! We use Rustler quite extensively at Doctave, and have written about our experiences with Rustler …

For us at Doctave ( https://www.doctave.com ), migrating customers from existing solutions manually ourselves has proved very effective. The product is a technical documentation pl…

Agreed on a lot of this, but I'd be cautious about saying that any kind of documentation is "simple". Especially when it comes to technical products - be they internal or external.…

Congrats on the launch! I'm curious how you manage syncing the changes from the WYSIWYG editor back to the repo? If you have two editors, one editing raw Markdown, and another one …

Creator here. The Doctave CLI is more like MkDocs or Docusaurus in that it supports a docs-as-code workflow. It takes your Markdown files and generates a pretty documentation site …

Author here. This is a good point. In this case we found it does slow down clean builds somewhat since we're pulling down + compiling Rust dependencies now as well as Elixir. While…

Author here. I actually was not aware of cmark.ex - thanks for pointing it out. In this case the code reuse was more important than pure native speed. We already had a Rust library…