DEV Community

Supraja Tangella
Supraja Tangella

Posted on

๐— ๐—ฎ๐˜€๐˜๐—ฒ๐—ฟ ๐—ฌ๐—ผ๐˜‚๐—ฟ ๐—ฃ๐—ฟ๐—ผ๐—ท๐—ฒ๐—ฐ๐˜ ๐——๐—ผ๐—ฐ๐˜€ ๐˜„๐—ถ๐˜๐—ต ๐—”๐˜‡๐˜‚๐—ฟ๐—ฒ ๐——๐—ฒ๐˜ƒ๐—ข๐—ฝ๐˜€ ๐—ช๐—ถ๐—ธ๐—ถ

I replaced our $600/month Confluence with a free Azure DevOps feature. Here's what happened.

I spent 3 months migrating our docs from Confluence to Azure DevOps Wiki.

Our team paid $600 every month for Confluence, but it was hard to manage, and people didnโ€™t update the docs.

Things went wrong when a big API change broke production because the docs were hidden in Confluence and not updated.

Azure DevOps Wiki lives right in your project. It's a Git repo that your devs already know how to use.

90% faster doc updates, zero permission issues, and our docs are now part of our CI/CD pipeline. Plus, we saved $7,200/year.

It feels too simple. Your devs will ask, "Wait, that's it?" Yes. That's it.

Have you tried keeping documents inside your development tools instead of using separate platforms? What worked (or didn't) for your team?

Top comments (0)