Skip to content

Conversation

@leemthompo
Copy link
Contributor

@github-actions
Copy link
Contributor

Vale Linting Results

Summary: 1 suggestion found

💡 Suggestions (1)
File Line Rule Message
solutions/_snippets/elasticsearch-disambiguation.md 6 Elastic.WordChoice Consider using 'efficiently' instead of 'simply', unless the term is in the UI.

Copy link
Collaborator

@shainaraskas shainaraskas left a 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**.
Copy link
Collaborator

Choose a reason for hiding this comment

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

do we have a definition for what a solution is that we can link to? I looked here and it looks like we don't tell people what solutions are 😿 maybe your new overview in this page will

Copy link
Collaborator

@shainaraskas shainaraskas Dec 17, 2025

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

Suggested change
- {{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).
Copy link
Collaborator

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

Suggested change
{{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).

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.

3 participants