Skip to content

Conversation

@Mikep86
Copy link
Contributor

@Mikep86 Mikep86 commented Nov 4, 2025

No description provided.

@Mikep86 Mikep86 added >docs General docs changes auto-backport Automatically create backport pull requests when merged :SearchOrg/Relevance Label for the Search (solution/org) Relevance team branch:9.2 branch:9.1 labels Nov 4, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Nov 4, 2025

@github-actions
Copy link
Contributor

github-actions bot commented Nov 4, 2025

ℹ️ Important: Docs version tagging

👋 Thanks for updating the docs! Just a friendly reminder that our docs are now cumulative. This means all 9.x versions are documented on the same page and published off of the main branch, instead of creating separate pages for each minor version.

We use applies_to tags to mark version-specific features and changes.

Expand for a quick overview

When to use applies_to tags:

✅ At the page level to indicate which products/deployments the content applies to (mandatory)
✅ When features change state (e.g. preview, ga) in a specific version
✅ When availability differs across deployments and environments

What NOT to do:

❌ Don't remove or replace information that applies to an older version
❌ Don't add new information that applies to a specific version without an applies_to tag
❌ Don't forget that applies_to tags can be used at the page, section, and inline level

🤔 Need help?

@Mikep86 Mikep86 requested a review from a team November 4, 2025 18:39
@Mikep86 Mikep86 marked this pull request as ready for review November 4, 2025 18:39
@elasticsearchmachine elasticsearchmachine added Team:Docs Meta label for docs team Team:Search - Relevance The Search organization Search Relevance team labels Nov 4, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/search-relevance (Team:Search - Relevance)

@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/core-docs (Team:Docs)

Copy link
Contributor

@leemthompo leemthompo left a comment

Choose a reason for hiding this comment

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

LGTM!

@leemthompo
Copy link
Contributor

In theory, it's implicit that everything is available on serverless, if the frontmatter already indicates that the page applies to serverless (and everything is GA by default on serverless, unless specified too)

But folks are working on making these more intuitive and this doesn't hurt in the meantime

@Mikep86
Copy link
Contributor Author

Mikep86 commented Nov 4, 2025

Thanks for the clarification @leemthompo! Do you think we need this PR then?

@leemthompo
Copy link
Contributor

technically no, I guess as long as the page level applicability is set

Copy link
Member

@kderusso kderusso left a comment

Choose a reason for hiding this comment

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

:shipit:

@Mikep86
Copy link
Contributor Author

Mikep86 commented Nov 5, 2025

Closing without merging because the relevant pages wholly apply to serverless, and thus each subsection implicitly applies to serverless as well.

@Mikep86 Mikep86 closed this Nov 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-backport Automatically create backport pull requests when merged >docs General docs changes :SearchOrg/Relevance Label for the Search (solution/org) Relevance team Team:Docs Meta label for docs team Team:Search - Relevance The Search organization Search Relevance team v9.1.7 v9.2.1 v9.3.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants