NiklasBegley

6 ms·

1.
by NiklasBegley 2y ago
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 WYSIWYG, but you do get a side-by-si
2.
by NiklasBegley 2y ago
Oops. Good catch.
3.
by NiklasBegley 2y ago
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 — you’re doing docs-as-bore. While some WYSIWYG cloud-bas
4.
by NiklasBegley 3y ago
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 before [0] (though our architecture has advanced quite a bit
5.
by NiklasBegley 3y ago
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 platform, and most customers are coming from an exis
6.
by NiklasBegley 3y ago
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. Technical writers train specifically to comm
7.
by NiklasBegley 3y ago
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 comes along with the WYSIWYG editor and makes a change
8.
RBoy: A Gameboy Emulator in Rust(github.com)
146 points by NiklasBegley 5y ago|57 comments
9.
Rustler: Safe Rust bridge for creating Erlang NIF functions(github.com)
4 points by NiklasBegley 5y ago|0 comments
10.
by NiklasBegley 5y ago
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 from them. It's more batteries-included and opinionated
11.
Doctave CLI 0.2.0: A Benchmarking Story(blog.doctave.com)
4 points by NiklasBegley 5y ago|2 comments
12.
Google, Twitter, and Spotify built a culture of documentation(blog.doctave.com)
3 points by NiklasBegley 5y ago|1 comments
13.
Consider Using Docs-as-Code(blog.doctave.com)
9 points by NiklasBegley 5y ago|7 comments
14.
by NiklasBegley 5y ago
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 actually editing Elixir code I haven't experience
15.
by NiklasBegley 5y ago
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 that used pulldown-cmark [1] with some custom tweaks that w
16.
Using Rust with Elixir for code reuse and performance(blog.doctave.com)
121 points by NiklasBegley 5y ago|19 comments