Hi @omonk, thanks for reporting this issue. Definitely seems like some cleanup is in order here, at least the component names are not intuitive.

If I'm understanding correctly, you want the "authorization" component to render both inside the ApiItem and ApiExplorer components? I think we used to render it under ApiItem, before our last major redesign.

• I don't think infoId and infoPath are the same values but I'll double check. It matters because the infoPath is what's used to generate the links to the correct security scheme tab under the generated info doc.
• It looks like we may have forgotten to clean up the createAuthorization under createApiPageMD but I'll double check.

Either way, it should be possible to achieve what you're asking for, i.e. with a custom markdownGenerators function. I'll look through to see what if anything we can clean up.

If I'm understanding correctly, you want the "authorization" component to render both inside the ApiItem and ApiExplorer components?

Yep exactly, it looks as though this was the case previously as the main API template has this template condition as I mentioned.

I don't think there needs to be a custom markdown generator, just passing the infoPath to the API item that i passed around to the markdown generators is enough.

Lots of as any make things quite tricky to parse 😬