External build of API docs and Lunr.js integration

[thesteve0]

Greetings helpful folks:
I am building my API docs (python and typescript) outside of mkdocs. I am using pydoctor for python and typedoc for typescript to generate the API html files. I then symlink each of those directories into my "docs" directory before I call mkdocs build (or serve).

After mkdocs serve, I can navigate to both sets of API docs from the nav bar and links in my general documentation. But if I search for any of the API docs on the main site there are no results pointing to the API doc.

Couple of questions

1. Is symlinking in the build API docs the right way to approach integrating API doc into my overall doc build? If not - do tell of the better solution

2. If it is the right way to do it, then how do I get API docs to show up in the main page search results?

Pydoctor is generating a Lunr index as well. Back when I worked in Lucene, there was a way to merge indices. Is there something similar in Lunr?

Any help great appreciated - cheers!

[thesteve0]

Ahhhhh given this issue and the blog post about search, I am pretty sure the answer is - not much I can do about it now. I will wait for the release of the new search and go with that.
Thanks

#6307

[squidfunk]

Yes, the new search will allow to more easily integrate with resources outside of the Markdown realm :-) Search will be part of the foundational work we're currently focusing on.