Thank you so much! Great question. Kalmia actually borrows elements from all three, but in different ways:
* On the GUI side, it leans heavily towards TinaCMS. We even considered using TinaCMS directly (Tinasaurus (https://github.com/tinacms/tinasaurus)) but ultimately built our own for better integration with our backend.
* For the backend (MDX -> HTML) generation, it's very similar to Docusaurus. We use a tool called RsPress, which is part of the RsBuild/RsPack tool suite. It's relatively new, but because it's written in Rust, it's much faster than Docusaurus. (Fun fact, if you look at the commit history you will see that we initially used Docusaurus but then migrated away from it!)
* Wiki.js is extremely extensive, but it’s dropping support for SQLite, which was a big factor for us. Also, its frontend for documentation doesn’t feel as fast as RsPress (you can try ours out on kalmia.difuse.io it's hosted on single core azure server). The biggest reason we didn’t go with Wiki.js was the versioning system—it felt clunky (or non existent for entire docs?). In Kalmia, versioning the entire documentation is just a one-click process.
So, in short, Kalmia combines a TinaCMS-like editing experience with Docusaurus-like static site generation, but with speed advantages from the latest Rust based tooling for SSG.
Comments
Thank you so much! Great question. Kalmia actually borrows elements from all three, but in different ways:
* On the GUI side, it leans heavily towards TinaCMS. We even considered using TinaCMS directly (Tinasaurus (https://github.com/tinacms/tinasaurus)) but ultimately built our own for better integration with our backend.
* For the backend (MDX -> HTML) generation, it's very similar to Docusaurus. We use a tool called RsPress, which is part of the RsBuild/RsPack tool suite. It's relatively new, but because it's written in Rust, it's much faster than Docusaurus. (Fun fact, if you look at the commit history you will see that we initially used Docusaurus but then migrated away from it!)
* Wiki.js is extremely extensive, but it’s dropping support for SQLite, which was a big factor for us. Also, its frontend for documentation doesn’t feel as fast as RsPress (you can try ours out on kalmia.difuse.io it's hosted on single core azure server). The biggest reason we didn’t go with Wiki.js was the versioning system—it felt clunky (or non existent for entire docs?). In Kalmia, versioning the entire documentation is just a one-click process.
So, in short, Kalmia combines a TinaCMS-like editing experience with Docusaurus-like static site generation, but with speed advantages from the latest Rust based tooling for SSG.