(no title)
gkoberger | 1 month ago
I run a documentation product, ReadMe. There's a lot of reasons to roll your own, but I'd recommend you also look into a third-party tool like us. One of the biggest reasons to use a product is that the building v1 is easy, but keeping it up to date over time is a lot tougher... you're stuck remembering how to deploy, figuring out a workflow, dealing with multiple versions, etc.
You also just don't get a ton of really great features for your developers... fast typeahead search, AI tools (which your developers increasingly really want), navigation, accessibility and more. ReadMe also lets your developers play around with you API locally and get copy-and-paste code snippets.
(If you're deciding between your own and ReadMe, email me! greg@readme.io; would love to talk)
pluralmonad|1 month ago
cmoski|1 month ago
gkoberger|1 month ago
If it's not for you, that's okay! But an increasing number of documentation teams are cross-functional (marketing, sales, engineering, product), and not everyone is comfortable editing content directly in Git and dealing with a release.
Docs are the heart and soul of most devtools, so I think it makes sense a lot of companies want a good product.