I think it is less critical for new content changes than for new releases.
Because the index is there but just stale.
However for new releases, the experience is different. People can't really
search anything for the new release.
I think the fix should be simple and straightforward in the release
A logical conundrum! You can’t get it index until its published and you can’t
control when the updated site is indexed. Is there anyway to trigger their
index? If so, do it to minimize the trouble.
Infra just announced a new .asf.yaml service. I can see how we could add Apache
Solr indexing to
Thanks for init this discuss. It seems not only relate with release? Will
we meet this issue while do other website content change?
Is there a way to add this waiting process into the website build script?
If so, after a success build, we know Algolia indexes already success.
Best Regards.
Jia
Hi all,
I am starting a discussion to gather ideas on how to improve the website
publish process in our release procedure. Searchbox doesn't work
immediately after we publish the documentation for new release. It happened
both 2.4.0 and 2.4.1 release.
- The documentation is indexed using Algolia
