I'm going to ask a general question... Can someone help me understand the pros/cons of routing API documentation through the gateway? I ask because I ran into a discussion concerning APIs build on the .NET platform where a level of "help" content is generated automatically through the build process. In this case, gateway routes would resolve to an endpoint on the backend that serves up "help" content.
My initial reaction was that serving up "content" was not something that API gateway "should" do, but at the end of the day its just another content type so technically it "can" do it. Any feelings on this?