âšī¸ These changes focus on the ES3 docs, I don't know if we'll have time to consolidate and collaborate with other docs teams on moving this stuff up to a higher level before GA.
âšī¸ This is very drafty, if you'd prefer to work in the shadow Google Doc then comment there
Better structural organization - Moving the serverless differences section earlier in the documentation hierarchy for visibility
More detailed explanations of:
Infrastructure management changes
Specific API and settings availability
Clear categorization of features into replaced, planned, and permanently unavailable
Added clarity around error handling - The inclusion of specific error message examples helps developers understand and handle unavailable API responses.
Request a new doc build by commenting
* Rebuild this PR: `run docs-build`
* Rebuild this PR and all Elastic docs: `run docs-build rebuild`
`run docs-build` is much faster than `run docs-build rebuild`. A `rebuild` should only be needed in rare situations. If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status [here](https://buildkite.com/elastic/docs-build).
Addresses https://github.com/elastic/platform-docs-team/issues/537 + https://github.com/elastic/docs-content/issues/78#event-15284101032
đī¸ URL preview
âšī¸ These changes focus on the ES3 docs, I don't know if we'll have time to consolidate and collaborate with other docs teams on moving this stuff up to a higher level before GA.
âšī¸ This is very drafty, if you'd prefer to work in the shadow Google Doc then comment there
Summary
Consolidate Elasticsearch tech preview limitations + serverless differences,clarify API/setting availabilities
đ¨ TODO