Support for multiple endpoints in a tab view

[vatsan-0613]

Describe the problem

I am trying to bring a tab like view where in if I click a tab(endpoint), the respective documentation will be shown. I am using iframes which points to the welcome.html folder inside the introduction of each build folder. I am running an express server which loads the main index.html and the i-frame it has that dynamically points to the build folder of the active tab. I also have a build button which runs the generate command to update the documentation. Is there any possible way to achieve this.

Describe the proposed solution

on clicking each tab the respective documentation must be shown.

Importance

I cannot use Magidoc without it

[pelletier197]

If what you aim to do is something like this, then it is already possible. You can put embedded markdown inside the tabs.

[vatsan-0613]

My use case is I have 4 graphql endpoints for which I've generated 4 build folders, I have to bring all the endpoints into one single website, for which my approach is using iframes and linking each iframe with the build folder html. But that doesn't work for me.

[pelletier197]

Oh I see, sorry. I misunderstood what you wanted. In this case you could use the "externalLinks" property from the website configuration and use a different root property for each of these websites. Then you have a default index.html that redirects to the default one, or you can do a landing page.

There's an example of how to do this here.

These websites will show up as external links on the right navbar.

[vatsan-0613]

Thank you for replying, but what I exactly want is a tab like experience wherein, 4 tabs will be present at the top. On clicking the tab the respective docs will be displayed below. I've developed an index.html which has these tabs and an iframe that points to the active route of the selected api doc. Is there any better way to do this.

I want a single page layout instead of switching to multiple pages.

[pelletier197]

I don't think that's possible at the moment. The produced documentation is static, it's not a single page application. If you have something that works well, you should probably stick with it.

Sorry for the late reply, I missed the notification 😬