[ES] Emphasizes the datastore capabilities of ES on landing page #2892
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
szabosteve
added
documentation
🔍 Preview links for changed docs |
szabosteve
changed the title
…into szabosteve/dci-281
lcawl
reviewed
Sep 17, 2025
…into szabosteve/dci-281
jimczi
reviewed
Sep 18, 2025
| # The Elasticsearch solution | ||
|
|
||
| {{es}} enables you to build powerful search experiences for websites, applications, and enterprise data using Elastic's unified platform. | ||
| The {{es}} solution and serverless project type position {{es}} as a comprehensive platform: a scalable data store, a powerful search engine, and a vector database in one. At its core, {{es}} is a distributed datastore that can ingest, index, and manage various types of data in near real-time, making them both searchable and analyzable. With specialized user interfaces and tools, it provides the flexibility to create, deploy, and run a wide range of applications, from search to analytics to AI-driven solutions. |
There was a problem hiding this comment.
Small nit: I wonder if the wording here should be about a scalable datastore that powers a search engine, a vector database and analytics in one?
leemthompo
reviewed
Sep 18, 2025
| --- | ||
|
|
||
| # Elasticsearch | ||
| # The Elasticsearch solution |
There was a problem hiding this comment.
Not strong opinion, but I'd lean towards this being: The Elasticsearch solution and search use case
and for the navigation_title, something like:
- Elasticsearch & Search
- Elasticsearch for search
benironside
approved these changes
Sep 18, 2025
| * **Search relevance tools**: Purpose-built UIs for managing synonyms, query rules, and other relevance-enhancing features | ||
| * **AI toolkit**: RAG Playground and inference endpoints management for building AI-enhanced applications | ||
| * **Complete {{es}} REST API**: Full access to {{es}}'s comprehensive APIs for indexing, searching, and managing data | ||
| * **Deployment flexibility**: Run in Elastic Cloud, Elastic Serverless, or self-managed environments with consistent interfaces |
There was a problem hiding this comment.
Maybe a good place to use attributes {{ecloud}} and {{serverless-full}}?
|
|
||
| ### Datastore and vector database | ||
|
|
||
| You can index many types of data, keep them stored efficiently, searchable, and analyzable. If all you need is a reliable and scalable datastore, you can use {{es}} that way without adding anything else. All of {{es}}’s advanced capabilities start with its role as a [data store](/manage-data/data-store.md). Examples include, but are not limited to: |
There was a problem hiding this comment.
Suggested change
| You can index many types of data, keep them stored efficiently, searchable, and analyzable. If all you need is a reliable and scalable datastore, you can use {{es}} that way without adding anything else. All of {{es}}’s advanced capabilities start with its role as a [data store](/manage-data/data-store.md). Examples include, but are not limited to: | |
| You can index many types of data to store it efficiently for search and analysis. If all you need is a reliable and scalable datastore, you can use {{es}}'s basic functionality without advanced configuration. All of {{es}}’s advanced capabilities start with its role as a [data store](/manage-data/data-store.md). Supported data types include, but are not limited to: |
As written, it sounded to me like the "Examples" will be advanced capabilities, not types of data.
Not sure my suggestions for the second sentence are accurate.
Co-authored-by: Benjamin Ironside Goldstein <[email protected]>
Co-authored-by: Benjamin Ironside Goldstein <[email protected]>
Co-authored-by: Benjamin Ironside Goldstein <[email protected]>
Co-authored-by: Benjamin Ironside Goldstein <[email protected]>
Co-authored-by: Benjamin Ironside Goldstein <[email protected]>
Co-authored-by: Benjamin Ironside Goldstein <[email protected]>
szabosteve
commented
Sep 25, 2025
Update (25 Sep)The terms (and less likely the content focus) might change after the offsite (22–26 Sep). That’s why I haven’t edited the page further. The PR can be amended based on @serenachou’s feedback about the direction defined at the offsite:
CC @lcawl |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PAGE PREVIEW
Overview
Related to https://github.com/elastic/docs-content-internal/issues/281
This PR repositions the message of the
/searchlanding page. It emphasizes that the datastore and vector database capabilities are core use cases of the ES solution. Search is presented as one of several possible use cases of ES, rather than the defining use case.TO DO
/solutions/search.md#elasticsearch-serverlessto point to H1