Recommended Blog - indoition
Doc-To-Help MVP
LavaCon Speaker

« People and tool reasons for migrating docs | Main | Migrating from a CCMS »


Feed You can follow this conversation by subscribing to the comment feed for this post.


Thanks for sharing your decision. I'm glad you found a tool that meets your needs :)

I'm curious to understand how Confluence's licensing costs were a barrier for your team?

Mary Connor

The barrier was lack of budget for ANY new solution. Our migrating to Doc-to-Help didn't cost us any _new_ money, in that we had budget for maintenance on our prior tool, and that was enough (thankfully). Perhaps I could have argued my way to new money if the wiki solved integrating API docs and those isolated HTML content files, but I couldn't see a happy path to that.


Thanks Mary – makes total sense :)

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Your comment could not be posted. Error type:
Your comment has been posted. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.


Post a comment

Your Information

(Name is required. Email address will not be displayed with the comment.)