YotiBecause of their documentation.
Yoti, a multi-award winning London-based company providing digital ID applications, revamped their documentation in DeveloperHub, transforming it from a developer bottleneck into a competitive advantage.
After switching to DeveloperHub, clients were calling us and telling us that they chose us over competitors due to documentation.
When Yoti first started with developer integrations four years ago, they did what most startups do: use open-source general software to document their products. While the result was indeed a documentation site, the process of writing documentation remained a code-driven, developer-dependent process.
Being a technology company, Yoti does have developers on the team; however their time is most useful building the product rather than the documentation site. As Yoti's Head of Integrations put it, this process was “frustrating”.
“It was just so frustrating because it was just a really quick change or even a capital letter, but we had to do some coding, and then get somebody to check the code, commit it and deploy it. It took so much time. The team then grew and it just was not scalable anymore.”
Kiran Bali“We had a new product coming up, and we couldn't do it quickly on the platform we built. We knew that we needed to find a different solution.”
Kiran BaliTo remove the dependency on developers and bring documentation back under the control of the product team, Yoti looked into DeveloperHub alongside competitors, and set up one of their products' documentation on DeveloperHub for a test.
“We were looking for a collaborative solution that is super easy to use. With DeveloperHub, our product team is able to do changes right away and publish it without thinking about technical challenges, so we can focus on what matters.”
Kiran BaliTwo months later, Yoti's documentation process was transformed by DeveloperHub, so they moved the entire documentation of five other products.
“It has been really easy to move all our documentation. We also extended it to the release notes and we were able to build an entire integrations ecosystem with DeveloperHub. As we are growing fast, we are always updating the products so we continuously need to change the structure and the formatting, and I feel like I can do that because I could just clone the version and make the changes without breaking the existing one.”
Kiran BaliCustom CSS, linked documentation per product and cloned versions, so a structural change never breaks the docs already in front of integrators.
We have APIs and SDKs which we monetise through and they need to be explained. My dream is to have them self-serviced, but in order to make them self-serviced, we need to empower our client with the ability to easily integrate. For them to easily integrate, we need to provide great documentation and this is where DeveloperHub comes in.
“I absolutely love what Yoti made with their documentation at DeveloperHub. They have one of the best branded developer portals we have seen, as well as documentation that is so clearly structured. They leveraged the ability to inject Custom CSS to design a beautiful experience, and used multiple linked documentation for each one of their products, which made it a wonderful journey for their integrators.”
27,000+ documentation sections written and a 4.8★ average on G2.
“Our experience using DeveloperHub for public docs vs. our solution is like the difference between night and day.”
“We saved half the time we were putting into documentation before. I can tell you that if I took DeveloperHub away from the team, then there will be some loud loud protests at the office.”
Join thousands of companies delivering exceptional developer experiences with DeveloperHub. Fourteen days free, no card required.
