Skip to content

Conversation

lcawl
Copy link
Contributor

@lcawl lcawl commented Jul 24, 2025

This PR edits https://www.elastic.co/docs/solutions/search/get-started to match the layout in https://www.elastic.co/docs/solutions/observability/get-started and https://www.elastic.co/docs/solutions/security/get-started. It more closely aligns with the latter in length and scope at this point.

@github-actions
Copy link

github-actions bot commented Jul 24, 2025

🔍 Preview links for changed docs

@lcawl lcawl marked this pull request as ready for review August 28, 2025 01:46
@lcawl lcawl requested a review from a team as a code owner August 28, 2025 01:46
@lcawl lcawl requested review from jmikell821 and theletterf August 28, 2025 01:47
Copy link
Contributor

@theletterf theletterf left a comment

Choose a reason for hiding this comment

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

Love it, this is much cleaner. :)

As a suggestion, you could perhaps add a Related resources section at the end with links to other relevant docs, quickstarts, training resources, etc.?

Copy link
Contributor

@jmikell821 jmikell821 left a comment

Choose a reason for hiding this comment

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

Looks great! Just left a few optional comments.

Copy link
Contributor

@szabosteve szabosteve left a comment

Choose a reason for hiding this comment

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

Looks great, thank you! I left one suggestion about mentioning that ES is also a vector database.

Copy link
Contributor

@szabosteve szabosteve left a comment

Choose a reason for hiding this comment

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

Thank you very much, LGTM!

@leemthompo
Copy link
Contributor

leemthompo commented Sep 3, 2025

This is definitely nicer than the existing stub but I'm not sure about the structure here, particularly Steps 2 and 4.

I'd be more inclined to something like:

  1. Choose your deployment type
  2. Ingest data
  3. Build your search queries - Combine actionable elements from steps 2 & 4

Looking at how users actually approach Elasticsearch, it might be simpler to somehow bucket the user's flow here into two approaches:

  1. "I have my own data and want to query it"
  2. "I just wanna try some tutorials/quickstarts using sample data".

This would acknowledge the real-world paths users take and provide clearer options based on their actual intentions.

I'd also lean towards not duplicating links already present in the stepper in the "Related resources" section, to prevent link fatigue.

These are only suggestions, and given that use case guidance etc. is thin on the ground in solutions/search, I think there's a limit to how useful we can actually make this page right now :)

@lcawl
Copy link
Contributor Author

lcawl commented Sep 4, 2025

I'd be more inclined to something like:

  1. Choose your deployment type
  2. Ingest data
  3. Build your search queries - Combine actionable elements from steps 2 & 4

I like that label for the last step so I've made that change in 86114c1
I've kept the "figure out your search goals", however, since it seems like the semantic and vector search in particular affect your subsequent choices.

Looking at how users actually approach Elasticsearch, it might be simpler to somehow bucket the user's flow here into two approaches:

  1. "I have my own data and want to query it"
  2. "I just wanna try some tutorials/quickstarts using sample data".

Agreed. For now I've just added more "skip to x" at the end of each step to try to open those escape hatches.

I'd also lean towards not duplicating links already present in the stepper in the "Related resources" section, to prevent link fatigue.

Good point, done in 86114c1

Thanks for the feedback!

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.

🚢

@lcawl lcawl enabled auto-merge (squash) September 5, 2025 14:11
@lcawl lcawl merged commit 1330d9d into elastic:main Sep 5, 2025
6 of 7 checks passed
@lcawl lcawl deleted the es-get-started branch September 5, 2025 14:13
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.

5 participants