-
Notifications
You must be signed in to change notification settings - Fork 163
Edit Elasticsearch getting started landing page #2248
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
Conversation
🔍 Preview links for changed docs |
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.
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.?
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.
Looks great! Just left a few optional comments.
Co-authored-by: Janeen Mikell Roberts <[email protected]>
Co-authored-by: Janeen Mikell Roberts <[email protected]>
Co-authored-by: Janeen Mikell Roberts <[email protected]>
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.
Looks great, thank you! I left one suggestion about mentioning that ES is also a vector database.
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.
Thank you very much, LGTM!
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:
Looking at how users actually approach Elasticsearch, it might be simpler to somehow bucket the user's flow here into two approaches:
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 |
I like that label for the last step so I've made that change in 86114c1
Agreed. For now I've just added more "skip to x" at the end of each step to try to open those escape hatches.
Good point, done in 86114c1 Thanks for the feedback! |
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.
🚢
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.