Update introduction to solutions

[lcawl]

Relates to #2795

Per #3005 (comment), this PR:

• updates the Use cases page to briefly describe the differences between the solutions, then point to the solution landing pages and get started guides for more details (moved the same summary out of the fundamentals landing page too)
• integrates "Core concepts" and "Use cases" details into the Observability and Security solution landing pages
• makes rather minimal changes to the Elasticsearch solution landing page, since there are significant changes already proposed in [ES] Emphasizes the datastore capabilities of ES on landing page #2892 (which is the source for some of the introductory text I've added to that page here--thanks @szabosteve ).

[github-actions]

🔍 Preview links for changed docs

• get-started/index.md
• get-started/introduction.md
• solutions/index.md
• solutions/observability.md
• solutions/observability/get-started/opentelemetry/use-cases/kubernetes/prerequisites-compatibility.md
• solutions/search.md
• solutions/search/get-started.md
• solutions/search/ingest-for-search.md
• solutions/security.md

[benironside]

Great work. This is a really nice overview, very succinct and a good level of detail. Left some comments for your consideration. I hope they are helpful.

[leemthompo]

I have no issues with the wording or anything here, looks good! But I'm concerned about scattering info, based on two main reactions to reading this:

First, I'm not sure why we aren't adding this content to the solutions landing page which is comparably quite sparse, despite being the section landing page? My instinct would be to make the section under fundamentals just a brief page that basically links out to /solutions (i.e. swap the content of get-started/introduction.md and solutions/index.md).

With this addition, the solutions and use cases now have five landing page surfaces that all overlap quite strongly:

• This new section under fundamentals
• The solutions/use cases landing page
  • The Elasticsearch solution landing page
  • The Observability solution landing page
  • The Security solution landing page

---

My next question is about the asymmetry of treatment of the 3 solutions/use cases: Observability and Security have detailed dropdowns with big hyperlinked lists. The fact that we've put these in dropdowns gives me the impression that this is too much info for this surface, which reinforces my concerns about scattering info from my first point.

Given ES has the broadest set of use cases and features, it's not super clear to me why it's given comparatively briefer treatment here, with no dropdowns, for example.

I don't consider any of this a giant problem, just my impression of the changes and perhaps there are follow-up plans I'm not aware of. I might be overthinking this :)

[lcawl]

Based on all the great feedback, in particular #3005 (comment), I've made the following changes to this PR:

• Updated the "Solutions and use cases" page to only briefly describe the differences between the solutions, then point to the solution landing pages and get started guides for more details (moved the same summary out of the fundamentals landing page too)
• Made rather minimal changes to the Elasticsearch solution landing page, since there are significant changes already proposed in [ES] Emphasizes the datastore capabilities of ES on landing page #2892 (which is the source for some of the introductory text I've added to that page here--thanks @szabosteve ).
• Made more significant additions to the Observability and Security solution landing pages to integrate the "Core concepts" and "Use cases" details there.

[florent-leborgne]

Nice to have this content in solution introductions 👍
2 thoughts that I think are pretty important to consider:

• The fundamentals section and especially the introduction page is a lot less useful without the "orientation based on your use case" content. Why not having it in both places using snippets? It's useful enough in both places to consider - on one you land once you already guessed which solution you need or is closest to your case, on the other one, you don't know how Elastic bundles their features nor where to look to start doing what you have in mind.
• Are we sure we should use dropdowns on these pages, they hide quite valuable and strategic content by default. Doing so is contrary to things we keep hearing from leadership about Elastic in general: so many people don't know that Elastic does this or that. It should rather be highlighted than hidden by default.

[leemthompo]

Few minor suggestions upon re-reading the latest updates. I agree with @florent-leborgne's point about the drop-downs, and I'm in two minds about his suggestion about the reusable snippet. Maybe it would make sense to re-orient fundamentals towards "use cases" and then have /solutions focus more on the actual solutions (but then that puts ES content in a weird spot because it's a lot more use case than solution) 😬 — so perhaps reusing content is fine here.

[lcawl]

• The fundamentals section and especially the introduction page is a lot less useful without the "orientation based on your use case" content. Why not having it in both places using snippets? ...

I'm in two minds about his suggestion about the reusable snippet... so perhaps reusing content is fine here.

I like the idea of re-using content in those locations. However, I think we're not in a great place to do it yet (and so I've temporarily commented out the content re-use that was added in 673212e).

My opinion is that since the outstanding #2892 is revising the Elasticsearch use cases and we've had previous comments in this PR and its predecessor about the (1) out-dated nature of the ES use cases in https://www.elastic.co/docs/get-started/introduction#elasticsearch and (2) the poor experience of having a mismatch of detail between ES and other solution sections, that we ought to wait and do the re-use once we've got the content in the ES landing page into a better shape. If folks disagree, let me know but I think this should be one of the ongoing baby-steps to improvement in this section. Until ES is clearer, my next step was to circle back to cleaning the Elastic Stack page.

[theletterf]

All: This has been open for too long and more than thoroughly reviewed. Let's please merge it and plan for subsequent improvements.

[leemthompo]

Made rather minimal changes to the Elasticsearch solution landing page, since there are significant changes already proposed in #2892

I wouldn't merge this PR until we have decided how to proceed on the Elasticsearch solution landing page. That's the bigger rock. I'm sure Istvan wouldn't mind if the onboarding team picked up that ball and ran with it this week.

[lcawl]

I wouldn't merge this PR until we have decided how to proceed on the Elasticsearch solution landing page. That's the bigger rock. I'm sure Istvan wouldn't mind if the onboarding team picked up that ball and ran with it this week.

I'm going to go ahead and merge this PR rather than continuting to block on the Elasticsearch landing page re-work, though I agree that's where the most important outstanding action items lie. Will follow up hereafter on the to-dos in #2892