Restructure the search section

[kolchfa-aws]

Restructure the search section

Checklist

• By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
  For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[github-actions]

Thank you for submitting your PR. The PR states are In progress (or Draft) -> Tech review -> Doc review -> Editorial review -> Merged.

Before you submit your PR for doc review, make sure the content is technically accurate. If you need help finding a tech reviewer, tag a maintainer.

When you're ready for doc review, tag the assignee of this PR. The doc reviewer may push edits to the PR directly or leave comments and editorial suggestions for you to address (let us know in a comment if you have a preference). The doc reviewer will arrange for an editorial review.

[kolchfa-aws]

@epugh As discussed, here's the PR to restructure the search section. Could you review this PR?

[epugh]

A couple of comments, and I don't know if they are relavant to this PR or not, but wanted to provde.

When I go to the Search page, the very top section is fine. The second seciton is about Query Langugages. Four of the Five query langagues have nothing to do with Search, they are specific for Dashboards. So it's a bit confusing why they are there. They should be in the Dashboards space of the docs maybe?

[epugh]

I lvoe this process steps you added:

I'll think more about it, it might be worthy of a graphic at some point. When we add in tools like ART (agentic relevance tuning) they may show up in this.

[kolchfa-aws]

When I go to the Search page, the very top section is fine. The second seciton is about Query Langugages. Four of the Five query langagues have nothing to do with Search, they are specific for Dashboards. So it's a bit confusing why they are there. They should be in the Dashboards space of the docs maybe?

@epugh I focused the table on backend languages and added a link to the Dashboards query language list (already present in /dashboards/index). Many people are confused about the query language options, so I think it's a good idea to cross-reference these.

[epugh]

When I go to the Search page, the very top section is fine. The second seciton is about Query Langugages. Four of the Five query langagues have nothing to do with Search, they are specific for Dashboards. So it's a bit confusing why they are there. They should be in the Dashboards space of the docs maybe?

@epugh I focused the table on backend languages and added a link to the Dashboards query language list (already present in /dashboards/index). Many people are confused about the query language options, so I think it's a good idea to cross-reference these.

Yeah, looking at it, it's better. It's just taking up a lot of real estate!

Maybe I would like it if it said "retrieve your data":

Since with PPL and SQL you are not searching, at least not in the more traditional sense. You are retrieving data, and we have multiple languages to support it.

[epugh]

In this document: https://docs.google.com/presentation/d/1EspLVQa9d2qZB55rBouSGSPtqzdsQt_waaiG3aKfxzE/edit?slide=id.g6fdd1a86d3_0_0#slide=id.g6fdd1a86d3_0_0 I have a graphic of the relevancy optimization....

And a slightly out of date (now) diagram that is specific to OpenSearch... WOuld you want to modify the section Search Quality Workflow to poentially include this diagram with the appropriate updates?

[epugh]

LGTM! I left one comment and one idea, but the rest of the restructure looks good. I angst over if the vector tutorials should at all link to Search Quality, but we don't yet have an awesome thing to point to that would make a strong case, and you do have the link form the reranking one.