Typedoc secondary entrypoints rendered on the docs hub

[petertonysmith94]

Summary

As part of the #2919 we added multiple entrypoints for typedocs. There are correctly not rendered as a navigation item within Vitepress, however, on the docs hub, these are being displayed as navigation items.

We should remove these items from being displayed as navigation items on the docs hub.

[danielbate]

This should've been resolved by #2937. When was docs hub last updated?

[petertonysmith94]

I can see that it's not in the apps/docs/.typedoc/api-links.json. Potentially the docs-hub uses the directory contents for constructing these navigation items (so it's a docs-hub issue).

I'd favour isolating the API docs and referencing it, like what was discussed in sync.

[maschad]

I'd favour isolating the API docs and referencing it, like what was discussed in sync.

I agree as well, I think that would be the ideal solution rather than maintaining these API docs via a hacky postbuild script it seems like misappropriated engineering resources in my opinion.

[petertonysmith94]

Added the following.

Would we want to close this or move the issue to the docs-hub?

[danielbate]

My preference would be to close this and just do #3058. I imagine the docs hub nav setup is probably as fragile as the typedoc postbuild script. Probably worth just doing the above.

[petertonysmith94]

Closed in favour of:

• Consider moving ApiDocs outside of the documentation. #3058.