kalmia

For purely static sites, there are other great options out there, but Kalmia focuses on more interactive, collaborative documentation.

Another feature Kalmia supports is private documentation, where users need to log in to access certain docs (there's a simple toggle to enable authentication).

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).

Looking forward to trying out Kalmia on some project soon.

One major difference between Outline and Kalmia is the license.

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.

While we don't personally use it, we'll be adding it so people can host their docs on static file platforms without needing Kalmia as the backend.

While it does limit deployment to platforms like GitHub Pages, Kalmia is designed for teams that need more than just static documentation—think of it as a middle ground between static site generators and fully dynamic CMS solutions.

However I don't understand how this goes together with "Cross-Platform Compatibility: Run Kalmia virtually anywhere thanks to its Go-based architecture." I couldn't find a roadmap for the project but I would suggest to implement some sort of SSO.

With Kalmia, non-technical users can contribute to documentation without needing to know Git or Markdown, making content editing much easier.

We’re currently developing a feature that allows you to push directly to Git from Kalmia.

Kalmia actually borrows elements from all three, but in different ways: * On the GUI side, it leans heavily towards TinaCMS.