-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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
Move breaking changes to (or near) Upgrading Elasticsearch section #34251
Comments
Pinging @elastic/es-docs |
This was an intentional change in #33588 related to elastic/docs#382 |
I've verified that there's a link to the breaking changes in the "important" section of each of the following upgrade pages: If you have suggestions for other places to link from, though, let me know! |
Thanks @lcawl . While we are linking to breaking changes from https://www.elastic.co/guide/en/elasticsearch/reference/master/setup-upgrade.html and https://www.elastic.co/guide/en/elasticsearch/reference/master/release-highlights.html, as soon as the user starts clicking through the pages linked from these landing pages, they will no longer see the breaking changes link unless they go back to the main page (or scroll all the way down just to find the Breaking Changes section again). It can be helpful to have the breaking changes section link be prominently displayed alongside "Upgrading ..." sections (below it), or as a subsection of "Upgrading ..." so that it is right there towards the top of the right navigation as a reminder regardless of what subpages they may end up on. |
[docs issue triage] Related to ES reorg and general docs navigation. Leaving open for discussion. |
We have some pending redesign and reorganization projects that will make this issue moot. Closing for now. We can re-open later if needed. |
Somehow breaking changes section is ending up towards the very bottom of the table of contents for the Elasticsearch documentation.
Breaking changes is such an important section for upgrades. Let's move this back up towards the "Upgrade Elasticsearch" section, either as a section parallel to "Upgrade Elasticsearch", or as a subsection within "Upgrade Elasticsearch".
The text was updated successfully, but these errors were encountered: