Following on from https://github.com/transportapi/api-console/issues/7 I personally have a preference, and I believe search engines also have a preference, for a more old-school web site composed of several pages loaded from different URLs, versus the newfangled javascript-heavy everything-on-one-page-with-broken-scrolling approach followed by the API console.
Probably the only fix to this issue would be to use something different :-( But there are some other RAML-powered documentation tools which run server-side generating a page per resource. Could be worth looking into.
Following on from https://github.com/transportapi/api-console/issues/7 I personally have a preference, and I believe search engines also have a preference, for a more old-school web site composed of several pages loaded from different URLs, versus the newfangled javascript-heavy everything-on-one-page-with-broken-scrolling approach followed by the API console.
Probably the only fix to this issue would be to use something different :-( But there are some other RAML-powered documentation tools which run server-side generating a page per resource. Could be worth looking into.