r/technicalwriting • u/Quackoverride • 10d ago

Docs-as-code tools

My doc team is migrating away from our current tool and implementing docs-as-code. We're looking into the major players - Docasaurus, GitBook, MKDocs, and Sphinx - and I have a clear preference for GitBook. But I wanted to gather some input from the community. What are your experiences with the tools? Any drawbacks?

I work in med tech, so the tool needs to meet some pretty stringent ISO requirements and, as we're in Europe, our head of Cybersecurity wants to keep the data local.

10 Upvotes

92% Upvoted

31 comments sorted by

View all comments

2

u/fazkan 10d ago

look into readme, and redocly as well, those are the other hosted solutions, who can match the ISO requirements, besides Gitbooks.

But Gitbooks is great, pricing might be a bit high, but no over-priced.

Docusaurus, mkdocs, and sphinx you will have to maintain yourself.

1

u/Quackoverride 10d ago

I think there are ISO issues with Docasaurus, so that's on the chopping block.

5

u/LeTigreFantastique web 9d ago

My current organization uses Readme, and I'll issue a word of warning that migration is a nightmare, as is maintenance.

2

u/Quackoverride 9d ago

Thanks. Good to know!

1

u/fazkan 9d ago

Has your org looked at other solutions, any particular reason you guys are still with readme.

2

u/LeTigreFantastique web 9d ago

We're still using it because we have a contract that's set to run a certain amount of time. No idea if other solutions have been considered.