dholbach

"GUI" should point to fluxcd.io/ecosystem

https://www.algolia.com/doc/guides/managing-results/must-do/custom-ranking/ and https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/ might be helpful, but I haven't found out how just yet. Help would be appreciated.

@h20220025 Super - thanks a lot. Let us know when you need help.

It'd be great to list the following in separate sections (instead of a wall of text) and incorporate info from https://fluxcd.io/community/ and pages linked from there: - meeting information: how...

@hiddeco found https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/infinite-scroll/js/ as a probably better suggestion.

`docsearch` is what we are using in https://github.com/fluxcd/website/blob/main/layouts/partials/hooks/body-end.html Unfortunately it's not supported there yet: https://github.com/algolia/docsearch/issues/883 So Hidde's example in the earlier comment could be helpful. If anyone could help with...

Regarding pagination: [docusaurus](https://github.com/facebook/docusaurus/) seems to do this better than docsy, but I couldn't find how it's configured there. Check out the https://docs.gitops.weave.works/ search as an example.

My thinking was to have it just at the top of the doc itself. And yes - find a way to convey that "overview of changes" also includes breaking changes...

Not sure how much of an issue this still is?

Thanks for offering help @UnfixedSun - we are looking forward to anything you can do to fix this issue.