Skip to content

Adjust versions page wording #1805

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

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Conversation

reakaleek
Copy link
Member

No description provided.

@reakaleek reakaleek requested a review from a team as a code owner June 19, 2025 20:37
Copy link

github-actions bot commented Jun 19, 2025

🔍 Preview links for changed docs:

🔔 The preview site may take up to 3 minutes to finish building. These links will become live once it completes.

versions.md Outdated
@@ -2,81 +2,81 @@
navigation_title: "All versions"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn’t it make sense to change the nav title to “Previous versions” or “Other versions”?

Copy link
Member Author

@reakaleek reakaleek Jun 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense, thank you! But I actually removed the navigation title. This page will not appear in the prod navigation.

e4faaf0

@@ -2,81 +2,81 @@
navigation_title: "All versions"
---

# All versions of Elastic Docs
# Elastic documentation versions
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe "Previous documentation versions” would be more explicit as to what the user would find here. But maybe the nav title is more important in guiding users to this page.

By the way, is hiding this page from the dropdown navigation on purpose?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This page will not be accessible form the navigation.

It will be accessed through the landing page or the new (soon released) version dropdown.

Copy link
Contributor

@vishaangelova vishaangelova Jun 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I saw that the link on the landing page navigated to this page. Then I saw it was highlighted in the navigation, and my expectation was that I'd able to get back to it later. But once I had started browsing the docs in the dropdown, I thought, how the heck am I going to get back to this page? So it makes sense to remove it from the nav 👍 I’m curious about the new version dropdown:)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can actually see it in our edge environment.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh cool, looks awesome! One thing though - maybe the link to this page in the new dropdown should also be “View other versions” instead of “View all versions”.

Screenshot 2025-06-19 at 23 52 23

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup. Makes sense with the suggestions of this PR.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

@KOTungseth KOTungseth Jun 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To match the short description, Previous documentation versions makes sense.

Good catch on the version dropdown!

@reakaleek is View other versions going to be too long?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

image

Copy link
Contributor

@vishaangelova vishaangelova left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@reakaleek
Copy link
Member Author

reakaleek commented Jun 19, 2025

@KOTungseth can you please confirm the suggestions of @vishaangelova.

I will then proceed with the changes. Thank you! 🙏

Copy link
Contributor

@KOTungseth KOTungseth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great. Thank you, @reakaleek!

@reakaleek
Copy link
Member Author

This looks great. Thank you, @reakaleek!

@KOTungseth Should we also change the page title?

#1805 (comment)

# All versions of Elastic Docs

Review the documentation for all versions of Elastic products.
Review the Elastic documentation for previous product releases.
Copy link
Collaborator

@shainaraskas shainaraskas Jun 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

previous is a little ambiguous, because eventually the v3 docs will contain multiples, including versions released in the "past".

Suggested change
Review the Elastic documentation for previous product releases.
In April 2025, we released our new documentation site. This site includes documentation for our latest product versions, including {{stack}} 9.0+ and {{serverless-full}}.
To review the product versions covered on elastic.co/docs, refer to [Find docs for your product version](/get-started/versioning-availability.md#find-docs-for-your-product-version).
To access our previous documentation system, which contains the documentation for older releases including {{stack}} 8.x, use the following links.

having written this comment, I'm wondering if this info should be integrated into the other page instead? wdyt @KOTungseth

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

Successfully merging this pull request may close these issues.

4 participants