Move query languages section under Elasticsearch reference in navigation

[Copilot]

The query languages section was a top-level sibling of the Elasticsearch reference in the nav, but belongs nested as a child of it alongside other Elasticsearch-specific reference content, positioned just after the REST APIs section.

Changes

• config/navigation.yml: Moved elasticsearch://reference/query-languages from a standalone entry under reference to the first child of elasticsearch://reference/elasticsearch, placing it just after the built-in toc items (which include REST APIs)

# Before: top-level sibling under reference
- toc: elasticsearch://reference/query-languages
  path_prefix: reference/query-languages

# After: first child of elasticsearch reference (just under REST APIs)
- toc: elasticsearch://reference/elasticsearch
  path_prefix: reference/elasticsearch
  children:
    - toc: elasticsearch://reference/query-languages   # ← moved here, first child
      path_prefix: reference/query-languages
    - toc: elasticsearch://reference/text-analysis
    ...

Note: REST APIs is defined within the elasticsearch://reference/elasticsearch toc itself rather than as an explicit child in navigation.yml, so positioning query-languages as the first child places it directly after the built-in toc items (Configuration through Command-line tools, including REST APIs). Page URLs are unchanged — path_prefix: reference/query-languages is preserved — so no redirects are needed.

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[leemthompo]

@copilot do we need to update https://github.com/elastic/elasticsearch/blob/main/docs/reference/toc.yml too?

[Copilot]

@copilot do we need to update https://github.com/elastic/elasticsearch/blob/main/docs/reference/toc.yml too?

No, we don't need to update the elasticsearch repo's toc.yml. The toc.yml files in individual repos (like elasticsearch) define the internal content structure of their sections. The config/navigation.yml in docs-builder is the assembly configuration that controls how those sections are nested in the global navigation. Moving elasticsearch://reference/query-languages to be a child of elasticsearch://reference/elasticsearch is purely a docs-builder assembly change.

[leemthompo]

@copilot won't the new URLs change for these pages, meaning we'll need redirects?

[Copilot]

@copilot won't the new URLs change for these pages, meaning we'll need redirects?

No redirects needed. The path_prefix for the query-languages section remains reference/query-languages in both the old and new positions — only the navigation hierarchy changes (where it appears in the sidebar), not the actual page URLs.

[leemthompo]

@georgewallace any preference for where we this to sit in the elasticsearch TOC?

[Mpdreamz]

Let's leave this move until after all the releases go out today, to give us some space :)

[leemthompo]

@copilot let's move that section to sit just under REST API

[Copilot]

@copilot let's move that section to sit just under REST API

Done in b3a91d7. Moved query-languages to be the first item in the elasticsearch reference children list — since REST APIs is defined within the elasticsearch://reference/elasticsearch toc itself (not a separate child entry in navigation.yml), this positions query-languages to appear just after the built-in toc items (Configuration through Command-line tools, which includes REST APIs).

[leemthompo]

@leemthompo just realized that there are assembly previews now and so he wasted time doing this locally yesterday 🫥

👏 for that in any case, so NICE 🪄

@elastic/docs-engineering feel free to merge this whenever it makes sense for y'all