Readme > Redocly migration
Personal/efficiency reasons for moving from Readme to Redocly
Section titled “Personal/efficiency reasons for moving from Readme to Redocly”When I started at Navro, their documentation was hosted on Readme. Readme is a SaaS API documentation platform, which has a cutesy owl mascot that made you question your sanity when the platform didn’t work or support the things you need it to. It seems like Readme have now gotten rid of the mascot and leant into generic AI-generated styling, although it lives on through screenshots and materials in their documentation they haven’t had time to update.
At the time I started the migration, at the start of 2025, Readme still strongly encouraged you to use their web-based editor.
As a sole technical writer with a lot of time constraints, this wasn’t feasible. There were a few things that were frustrating about their editor When you added content in their proprietary markdown format, there would be a slight delay as it was rendered, and it would also strip content when it converted a table to their proprietary format.
Business reasons for moving from Readme to Redocly
Section titled “Business reasons for moving from Readme to Redocly”There were a few reasons for moving Navro’s documentation from Readme to Redocly.
Role-based access control and conditional content
Section titled “Role-based access control and conditional content”Navro’s product provides different functionality and requires that information be provided in different formats based on a client’s contract.