Thanks for filing this.

Copying my comments from Zulip:

1. Currently we only index the quarkiverse docs that are mentioned on quarkus.io, which is not a lot. We'll need to find some other index (+ metadata) if we want to index more than that. We may also need to retrieve the pages differently (currently we do HTTP requests, I don't think that will scale -- cloning the GitHub Pages branch would be better).
2. We'll need a separate UI. Since @ia3andy 's work will lead to the UI being implemented quite differently, it would probably be best to wait for that to be done and use it from the start.
3. I think Quarkiverse docs are multi-page, so we'll need to think how we handle that (i.e. should search results show guides with a link pointing to the beginning of the guide, or pages with a link pointing directly to the relevant page)

And also:

Bonus points if Quarkiverse guides are shown in https://quarkus.io/guides too.

one challenge would be to properly boost up the non-quarkiverse guides in the search results to avoid some quarkiverse docs "taking over" quarkus.io :)

1. Currently we only index the quarkiverse docs that are mentioned on quarkus.io, which is not a lot. We'll need to find some other index (+ metadata) if we want to index more than that. We may also need to retrieve the pages differently (currently we do HTTP requests, I don't think that will scale -- cloning the GitHub Pages branch would be better).

The site at http://quarkus.io/extensions lists each extension's guide, so that might be a natural starting point for the index, since it comes with some built-in metadata. (Well, sort of.)

Other potential entry point if you plan to clone the repositories and want to parse the AsciiDoc: https://github.com/quarkiverse/quarkiverse-docs/blob/main/antora-playbook.yml

Note to implementors, see #157:

Also, for now we still duplicate Quarkiverse guides per Quarkus version, but we could probably get rid of that too if we were to solve #143 by:

• Taking metadata for those guides from a version-independent source (e.g.
  the Quarkiverse docs GitHub repo).
• AND allowing search results on quarkus.io to return Quarkiverse guides
  independently from whether they are referenced in
  quarkus.yaml/quarkiverse.yaml.

Hey all 😃

I've drafted something that would index the Quarkiverse docs. It'll automatically include them in the search results on https://quarkus.io/guides/.

Someone might think I went for the bonus points right away 😄:

Bonus points if Quarkiverse guides are shown in https://quarkus.io/guides too.

Now as for the https://docs.quarkiverse.io/index/explore/index.html ... there's no search at all on this page at the moment. Hence I'm thinking that we can add the search input here at the top:

and then display the results in the main area as:

any other ideas?

Awesome! It would be nice if it had some indicator saying that the area represents the search results (maybe a different background color?)