Spec editor renders openAPI tags, but portal does not
When editing an openAPI spec inside Apigee, it honors openAPI Tags , but on the resulting Portal, it does not.
For example, here is the editor with tags on left and rendered version on right:
and here is how the portal renders it:
How do I get the tags to be honored on the rendering of the actual portal?
After a bit more drilling, it looks like the "old" version v1 of the Integrated Portal does render stuff by tagged categories, as shown on this page: https://docs.apigee.com/api-platform/publish/portal/original-theme/publish-apis-v1
So, is it possible that the "New and improved" version of the Integrated Portal no longer includes the ability to group endpoints into subcategories (ie in the case where there might be 100s of endpoints or more)??
Today SmartDocs on the portal does not use tags to organize the API reference documentation. However, this is the next area of improvement we're planning, so good to hear of your interest!
I have access to another Apigee portal which does in fact render with the spec editor style of categorization.. I just don't know how that is done. One would think it is via tags since that is how the spec editor renders tags, but apparently not. If not via tags, then how? Seems extremely broken for the spec editor to render like that but not the portal.
Can you share a link? A long time ago, before we released SmartDocs for integrated portals, there was a short term solution that leveraged Swagger UI, which did consider tags. This is no longer an option for developer portals, though there may be legacy examples?
unfortunately it would not be appropriate for me to post it, but further research revealed it as drupal based. Note however that as mentioned above, this page shows the swagger-ui styled rendering as part of the v1 portal food carts API example: https://docs.apigee.com/api-platform/publish/portal/original-theme/publish-apis-v1
