ReadMe

“Everyone brought their pros and cons to the conversation and we really dug into what made each solution efficient or less efficient. The learning curve was a factor — we were already using and enjoying ReadMe, and we wanted to launch this project quickly. We decided to stick with ReadMe not just because of that, but also because you offer more than the baseline documentation and introduce new products and services at a faster rate than the competition. For example, the developer community features and discussion posts were another deciding factor.”

“We hear frequently from our customers that our docs are amazing, in large part due to Journeys, made possible thanks to ReadMe’s custom HTML/CSS widgets. It has reduced our support ticket load by 35% and decreased our onboarding times from hours to minutes.”

“The "Suggest Edits" feature is our favorite. We used to get a ton of support tickets with corrections to our documentation. Using Suggested Edits, our customers can now instantly create a pull request for us with their proposed changes. The user experience on both sides is far more streamlined.”

“The API Explorer is fantastic for our users as it allows them to try out our APIs right from their browser. For API window shoppers, it’s a great experience.”

“We wanted Doppler’s docs to feel like an extension of our product, with deep thought put into the user experience and design. This meant keeping things simple, guiding the user when possible, and being on-brand.”

“Before ReadMe, we had 2 separate documentation hubs in our product that were built in-house. They were a nightmare to maintain, keep in sync, and style. Thankfully, those days are behind us!”

“ReadMe allows you to create beautiful API docs without the need to be a developer. If you are a developer, it’s even better.”

“I had made an initial template for the docs to match what the marketing team was doing and I was told, ‘You cannot remove anything. Don’t rewrite anything. Just reorganize it.’ It’s a tedious task that involves going through everything. They were written by four people over time and you could tell by looking at them.”

“Our designer made the designs in Figma. I saw those designs and I was like, ‘I don’t think this is possible.’ I said, ‘This is nuts. But go in, ask for it, even though you probably won’t get it.’ And then they did all of it. They did crazy JavaScript. They did all of it.”

“The first time I saw customization in ReadMe was at a previous company where we had a frontend engineer who could hack anything. It was very impressive, and I knew then that a lot of customization was possible. Because of my engineering background, I’ve hacked a fair amount of customizations in ReadMe too. But with Atelio, we basically had two months to go from designs to live docs. And so I basically said to your team, ‘I know a lot of this is customizable. I know you all know it’s all customizable. I know you all know where all the skeletons are. And I don’t. So how do we make this work?’”

“We were able to get [Atelio’s developer hub] to look like it was part of a page made by a whole different company, which was really amazing. The fact that ReadMe did what they did is like witchcraft.”

“The docs are one of the most viewed parts of the site to this day. I think that speaks to who we’re serving,”

““Our sales folks are very grateful — this makes us much more competitive when we’re showing off our docs. And we know our support team loves that we can respond quickly to any kinds of problems that people find in the docs, and update them accordingly.””

““We do all of the work in Git and then we import or upload the Swagger files to ReadMe, and it publishes beautifully. We get all the nice interactivity, and all of the examples end up in the right place.””

““We’re very developer-focused at Akamai, and the ReadMe platform was one way of demonstrating to our developer customers that we care. Being able to publish API docs from Swagger to our developer hub really connects us to our engineering teams and makes what could be a really dry process very engaging for the user,” shared Beth.”

“The skeptics on my team became fans almost immediately after they started using it. Everyone breathed a sigh of relief, because if we had to fix a typo, we could just fix it ourselves. We didn’t have to wait for a long internal process to happen before the changes were live.”

“I spun up a site fairly quickly and thought, ‘this is awesome,’ and reached out to your sales team the same day.”

“We have code samples everywhere so users can ask, "How do I create a company compliantly?" And we can say, "Here are the steps. Here’s the exact code that does it.”

“We decided to stick with ReadMe not just because of that, but also because you offer more than the baseline documentation and introduce new products and services at a faster rate than the competition.”

“The fact that ReadMe did what they did is like witchcraft.”

“Switching from our previous vendor to ReadMe has been night and day difference from a customer satisfaction standpoint, it's a lot easier to navigate the documentation and find what you need.”

“Our goal was a best-in-class developer experience, and ReadMe was the clear winner. Out-of-the-box features with real customer impact, collaborative editing across product teams, and bi-directional sync from the UI meant no other solution checked all the boxes the way ReadMe did.”

“When you’re an API-first platform, I don’t think you can overstate the importance of documentation. It’s the way forward for support issues, for engineering to keep improving the API, and for customer-facing teams to sell and implement effectively. It’s worth the time to get it right.”

“One of the things that’s paid dividends for us is writing guides for how to make updates with ReadMe. When people feel empowered to make changes to the documentation without needing me or the team, they’re more likely to take the time to do it.”

“One of the things that has been really impactful is the interactivity that ReadMe provides. We’ve made our docs fully interactive, so developers can make API calls without actually having to write code: like a “no-code” editor for our API.”