You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it conceivable to build the search index independently of the build step? E.g. only based on the markdown files in the docs folder?
We have the issue, that we are using client-side authentication in our Docusaurus build and thus, had to use a work around (as described here: #210 (comment) ) to solve this.
It would be great if you could choose between using the build folder or let's say the original docs folder to create the search index.
The text was updated successfully, but these errors were encountered:
Currently no, under the hood, we parse the generated html files to build the search index (just like a server side search engine). We can't build the index by parsing markdown files because they may contain information that is not available until runtime, such as React components in mdx.
Currently no, under the hood, we parse the generated html files to build the search index (just like a server side search engine). We can't build the index by parsing markdown files because they may contain information that is not available until runtime, such as React components in mdx.
That makes total sense. Thanks for the explanation.
Is it conceivable to build the search index independently of the build step? E.g. only based on the markdown files in the docs folder?
We have the issue, that we are using client-side authentication in our Docusaurus build and thus, had to use a work around (as described here: #210 (comment) ) to solve this.
It would be great if you could choose between using the build folder or let's say the original docs folder to create the search index.
The text was updated successfully, but these errors were encountered: