elastic / elastic/docs-content

[API docs]: Clarify Serverless "Beta" label meanings (add supportability description), and more clearly label "Technical Preview with clear supportability statements

Open
#200 3 comments 2 reactions 1 assignee Claimed by @lcawl View on GitHub
blocked cross-team cumulative_docs Team:Projects
Dominant language
No language data
Stars
47
Forks
261
Avg merge
3d 12h
Merged PRs (30d)
116

Description

### Description

Within the Serverless documentation:
- some pages clearly say `preview` at the top (which need to hover to see supportability statements), ie https://www.elastic.co/guide/en/serverless/current/security-add-exceptions.html
![Image](https://github.com/user-attachments/assets/b832a61f-0c15-4451-8d4a-9495c90ffeba)

- some have the statement written out (ie https://www.elastic.co/docs/api/doc/serverless)
![Image](https://github.com/user-attachments/assets/8e4730c9-a257-4c73-b8fd-c7a2183b88e5)

- some have `Beta` (with no hover or description) (ie https://www.elastic.co/docs/api/doc/serverless/operation/operation-findendpointlistitems)
![Image](https://github.com/user-attachments/assets/c7500ad5-54ec-4e37-93e6-6b9af7ca87ec)

It would be very helpful to add clear, consistent and formatted supportability statements for the supportability of Serverless APIs and Serverless products. Currently, the layout creates confusion about what can be supported for Serverless products and `Beta` does not appear to be explained in the Serverless documentation.

### Resources

Platform - serverless team

### Which documentation set does this change impact?

Elastic Cloud (Hosted and Serverless) only

### Feature differences

This is specific to all Serverless documentation

### What release is this request related to?

N/A

### Collaboration model

The product team

### Point of contact.

**Main contact:** @ppf2

**Stakeholders:**

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.