Ask HN: How could OpenAPI documentation UIs (Swagger, Redoc, etc.) be improved?
I'm wondering how OpenAPI documentation UIs (like Swagger, Redoc, etc.) could be improved. Even when you make sure your OpenAPI spec is clean (e.g. run Vacuuum linter, provide full descriptions), the documentation sites still often feel rough or lacking polish, especially compared to general developer docs. Now that we have advanced tooling and AI, I suspect there's room to do much better—maybe smarter interactions, more helpful examples, or even AI-assisted code snippets.
But I'm not sure what the "next step" looks like, especially with AI in the mix and new approaches to codegen/documentation coming out. Curious what concrete improvements others would like to see, or if you've solved these pain points in creative ways yourself.