Ask HN: What are you using for non-tech, team documentation?

[aosaigh]

We have a small team (5). I'm the developer and the others are mostly non-technical.

I've been writing technical documentation with MKDocs which is great as a developer comfortable with Git and Markdown, but I now want to create a separate documentation set for client-facing, help/guide material that the other team members can contribute to.

Currently we just manage a Google Drive of docs and PDFs and it's disorganised and hard to manage.

What are other small teams using here? I'm looking for something that has some sort of editing interface, ideally can still track versioning of content, and is themeable to some extent. It could be self-hosted or a regular hosted SAAS.

What are some options?

[dataminded]

Markdown and Git should be very accessible to a non-technical audience and I've had good success with both.

Here's my favorite SAAS offering in the space - https://www.gitbook.com/

[PaulHoule → dataminded]

More to the point, there isn't anything better.

All of those tools that look like Microsoft Word (have the B, I, U buttons) have something wrong with their underlying conceptual model. (You can tell from the way the selection behaves as if it was possessed by the devil.)

That conceptual mismatch is annoying for a single-user editor but it makes a multiple-user editor a complete mess.

[aosaigh → dataminded]

Thanks. I'm actually checking Gitbook out as we speak. I actually don't mind the team using Git and Markdown, as long as it's easy. In Gitbook's case it seems like it is, the editing is easy.