Skip to content

Update semantic_text doc per feedback#137970

Merged
kderusso merged 1 commit intoelastic:mainfrom
kderusso:kderusso/michail-feedback
Nov 12, 2025
Merged

Update semantic_text doc per feedback#137970
kderusso merged 1 commit intoelastic:mainfrom
kderusso:kderusso/michail-feedback

Conversation

@kderusso
Copy link
Member

Update to #137963 based on feedback

@kderusso kderusso added >docs General docs changes auto-backport Automatically create backport pull requests when merged :SearchOrg/Relevance Label for the Search (solution/org) Relevance team v9.3.0 branch:9.2 branch:9.1 labels Nov 12, 2025
@kderusso kderusso requested a review from mromaios November 12, 2025 15:05
@elasticsearchmachine elasticsearchmachine added Team:Docs Meta label for docs team v9.2.2 Team:Search - Relevance The Search organization Search Relevance team v9.1.8 labels Nov 12, 2025
@elasticsearchmachine
Copy link
Collaborator

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

@elasticsearchmachine
Copy link
Collaborator

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

@github-actions
Copy link
Contributor

🔍 Preview links for changed docs

@github-actions
Copy link
Contributor

ℹ️ 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?

Copy link
Contributor

@mromaios mromaios left a comment

Choose a reason for hiding this comment

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

LGTM!

@kderusso kderusso enabled auto-merge (squash) November 12, 2025 15:11
@kderusso kderusso merged commit c3c9d2f into elastic:main Nov 12, 2025
11 checks passed
kderusso added a commit to kderusso/elasticsearch that referenced this pull request Nov 12, 2025
@elasticsearchmachine
Copy link
Collaborator

💚 Backport successful

Status Branch Result
9.2
9.1

kderusso added a commit to kderusso/elasticsearch that referenced this pull request Nov 12, 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.8 v9.2.2 v9.3.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants