Add new Elastic intro section #2795
Conversation
|
@lcawl @jmikell821 We need to decide what to do with Edit: Removed and added a redirect. |
…cs-content into add-elastic-new-intro-section
There was a problem hiding this comment.
overall, I think these changes are too shallow when it comes to the platform overview, and too deep when it comes to docs about docs. have these changes been planned with consideration for people's pain points when first getting started with our platform?
I think we need to spend more time explaining what our components are (in quite a bit of detail), how they fit together, and the "landscape" of elastic. also, explaining the implications of the various choices users need to make when getting started. I worry that some of the cuts that were made when repositioning this will give us fewer ledges to cling onto when trying to provide core definitions of our offerings (especially when it comes to "what is elasticsearch? what is kibana? what is fleet?").
I advise tripling down on depth of information overall.
Quick commit to save changes, then circling back.
|
FYI There were three pages that still had outstanding comments but were held up by parallel efforts or initiatives. I've therefore split those pages' updates into separate PRs for follow-up: |
An addendum to #2795. Updates the links to point to the Get Started landing pages instead of the solution landing pages.
Relates to #2795 This PR updates the introductory [Versioning and availability](https://www.elastic.co/docs/get-started/versioning-availability) page. It is a work in progress until we address the following feedback: - #2795 (comment): "I don't know if this [Examples of where availability can vary] section is very clear. I think it could use some more details or introductory content. Somewhere on this page, we should try to explain a few things, how these multiple, differently versioned, products work together and how this can impact availability: - Elastic Cloud, ECE, and ECK are orchestrators used to create and manage serverless projects (Elastic Cloud only) and deployments of the Elastic Stack - The versions of the Elastic Stack that you can deploy depend on the version of these orchestrators. For example, Elastic Stack 9.0 is not available to deploy on ECE 3.1. - Because some products are released on different schedules and have different architecture or network constraints, it is possible that a feature isn't available for some deployment types, or becomes available at a different time for each deployment type." - #2795 (comment) "we also do some of this explanation on the following surfaces and you can mine them for language / make sure they align: - https://www.elastic.co/docs/deploy-manage/deploy#about-orchestration - https://www.elastic.co/docs/deploy-manage/deploy#versioning-and-compatibility - https://www.elastic.co/docs/deploy-manage/upgrade/plan-upgrade" - #2795 (comment) "> Because some products are released on different schedules... would be careful with this because a lot of functionality is controlled by the stack version. might indicate that these are usually at the admin layer rather than the storage/querying layer of elastic. examples would be helpful (e.g. not all auth types are available for all deployment types [e.g. [ldap](https://www.elastic.co/docs/deploy-manage/users-roles/cluster-or-deployment-auth/ldap)] - that's kind of a layer "above" / "around" the es engine)" --------- Co-authored-by: Janeen Roberts <[email protected]> Co-authored-by: Janeen Mikell Roberts <[email protected]> Co-authored-by: Fabrizio Ferri-Benedetti <[email protected]>
9 participants
This rebuilds the Get Started section into the Elastic fundamentals section to improve Onboarding experience.
Pending: