[Serverless]: Fragmented experience of how we present limitations and differences in Serverless Docs

[ppf2]

Serverless Docs

Welcome to Elastic Serverless

Description

This originates from a meeting I had with Yaru on ES3 docs.

In short, users have to look at Limitations and Differences pages across project types to figure out the differences in the availability of features between Hosted/self-managed vs. Serverless.

Suggestions:

1. Combine all the Limitations and Differences pages across project types into a higher level page with a breakdown of features that will "never be available on Serverless" vs, "available on Serverless in a different form (by design)" vs. "we know it's a limitation and it will come in the future".
2. In this table, we can tag the features based on where it is applicable to 1 or more project types so we don't need to duplicate the same content across pages of project types

Resources and additional context

This is now mapped to the work item here: https://github.com/elastic/platform-docs-team/issues/537

[georgewallace]

@leemthompo I am pretty sure this can be closed now, but double checking with you.

[leemthompo]

We have consolidated information on the Elasticsearch side, but we need to discuss higher-level consolidation with the other teams, or at least make sure they point to the ES serverless differences page (if they're not already)

[ppf2]

Related #224.

Once we standardize and consolidate on how we present limitations information, we can add a reference link to the roadmap page as well.

[leemthompo]

Closing as all of this content is being moved as part of docs migration

FYI this information will be in the WIP Deploy and manage section