-
Notifications
You must be signed in to change notification settings - Fork 189
Create Elasticsearch disambiguation snippet we can reuse #4271
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
base: main
Are you sure you want to change the base?
Conversation
leemthompo
commented
Dec 10, 2025
- https://github.com/elastic/docs-content-internal/issues/313
- Follow up to Define and disambiguate Elasticsearch in glossary #4031
Vale Linting ResultsSummary: 1 suggestion found 💡 Suggestions (1)
|
shainaraskas
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
couple of small comments
before we push this, maybe it makes sense to workshop how it will be used by trying it out somewhere. it might impact the way that we shape the snippet
|
|
||
| The term "{{es}}" has several additional meanings depending on the context in which it is used: | ||
| - {{es}} is the name of a [**project** type](/deploy-manage/deploy/elastic-cloud/create-serverless-project.md) on {{serverless-full}}, tailored for general-purpose search use cases. | ||
| - {{es}} is also the name of a **solution** in other Elastic deployment types. Each [space](/deploy-manage/manage-spaces.md) has its own navigation or **solution view**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think framing the navigation in terms of spaces is a little confusing.
wonder if, to support this, we should extract the solution view definitions from the stack procedure here. I don't think it's critical to indicate that these can be overridden at this stage - we are just trying to indicate that when we say "Elasticsearch" we might be talking about the es solution view
| - {{es}} is also the name of a **solution** in other Elastic deployment types. Each [space](/deploy-manage/manage-spaces.md) has its own navigation or **solution view**. | |
| - {{es}} is also the name of a [**solution**](no good link) in other Elastic deployment types. Each solution has its own [solution view](no good link), which controls the navigation and menus that users see in {{kib}}. |
| @@ -0,0 +1,6 @@ | |||
| {{es}} is the [open source](https://github.com/elastic/elasticsearch) search and analytics engine, data store, and vector database which powers the Elastic platform and is fundamental to every Elastic [deployment type](/deploy-manage/deploy.md). | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we link to the stack overview elasticsearch section here so people can wayfind to the reference / info about doing these various tasks?
this or another way
| {{es}} is the [open source](https://github.com/elastic/elasticsearch) search and analytics engine, data store, and vector database which powers the Elastic platform and is fundamental to every Elastic [deployment type](/deploy-manage/deploy.md). | |
| [{{es}}](/get-started/the-stack.md#stack-components-elasticsearch) is the [open source](https://github.com/elastic/elasticsearch) search and analytics engine, data store, and vector database which powers the Elastic platform and is fundamental to every Elastic [deployment type](/deploy-manage/deploy.md). |