Skip to content

Assembler doesn't respect navigation.yml order #1045

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
bmorelli25 opened this issue Apr 7, 2025 · 2 comments · Fixed by #1095
Closed

Assembler doesn't respect navigation.yml order #1045

bmorelli25 opened this issue Apr 7, 2025 · 2 comments · Fixed by #1095
Labels

Comments

@bmorelli25
Copy link
Member

bmorelli25 commented Apr 7, 2025

Summary

The assembler doesn't respect the order of navigation.yml.

An example of this is the glossary. The glossary is defined in navigation.yml at the end of the reference section. However, in staging, you'll see the glossary in the middle of the page.

What I expect to happen

I expect the navigation/toc to be displayed in the same order that toc.yml files are included in the navigation.yml file.

Related bug

Due to the above bug, on some pages, the links to previous and next pages aren't the pages I'd expect, i.e., they don't match the navigation/TOC. For example:

Go to https://staging-website.elastic.co/docs/release-notes/apm/agents/android. According to the nav, the previous page is the Elastic APM Deprecations and the next page is the Elastic APM Android Agent Known Issues.


Image

However, The previous and next links are:


Image

The troubleshooting page is the APM Android Agent Troubleshooting page. However, that page is in the Reference content set (a completely different navigation tree).

@bmorelli25 bmorelli25 added the bug label Apr 7, 2025
@bmorelli25 bmorelli25 changed the title Previous and Next pages are out of order Assembler doesn't respect navigation.yml order Apr 9, 2025
@Mpdreamz
Copy link
Member

Closed by #1068

@Mpdreamz Mpdreamz linked a pull request Apr 11, 2025 that will close this issue
@Mpdreamz
Copy link
Member

And #1095 addresses the related issue for which this ticket was left open as indicated here elastic/docs-content#1058 (comment) 😸

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants