Add feature states, clarify state of existing features (#196)

Author: tothmano

apl/tabular-operators/join-operator.mdx

@@ -12,7 +12,7 @@ This operator is useful when you want to:
 - Enrich existing data with supplementary details.
 
 <Note>
-    The `join` operator is currently in preview. To try it out, [contact Axiom](https://axiom.co/contact).
+    The `join` operator is currently in private preview. To try it out, [contact Axiom](https://axiom.co/contact).
 
     The preview of the `join` operator works with an upper limit of 5,000 events on the left side of the join and 50,000 on the right side of the join.
 </Note>

getting-started-guide/feature-states.mdx

@@ -0,0 +1,29 @@
+---
+title: "Feature states in Axiom"
+description: "This section explains the feature states in Axiom."
+sidebarTitle: Feature states
+tags:
+    ['axiom documentation', 'documentation', 'axiom', 'feature states']
+---
+
+Each feature of Axiom is in one of the following states:
+
+- **In development:** Axiom is actively building this feature. It’s not available yet but it’s progressing towards Preview.
+- **Private preview:** An early-access feature available to selected customers which helps Axiom validate the feature with trusted partners.
+- **Public preview:** The feature is available for everyone to try but may have some rough edges. Axiom is gathering feedback before making it GA.
+- **Generally available (GA):** The feature is fully released, production-ready, and supported. Feel free to use it in your workflows.
+- **Planned end of life:** The feature is scheduled to be retired. It’s still working but you should start migrating to alternative solutions.
+- **End of life:** The feature is no longer available or supported. Axiom has sunset it in favor of newer solutions.
+
+<Warning>
+Private and public preview features are experimental, are not guaranteed to work as expected, and may return unexpected query results. Please consider the risk you run when you use preview features against production workloads.
+</Warning>
+
+Current private preview features:
+
+- [Flow](/process-data/introduction)
+- [Join operator](/apl/tabular-operators/join-operator)
+- [Send data from Datadog to Axiom](/send-data/datadog)
+
+Current public preview features:
+- [Cursor-based pagination](/restapi/pagination)

mint.json

@@ -80,6 +80,7 @@
           "pages": [
             "getting-started-guide/event-data",
             "getting-started-guide/observability",
+            "getting-started-guide/feature-states",
             "getting-started-guide/glossary"
           ]
         },
@@ -445,6 +446,7 @@
             "apl/tabular-operators/distinct-operator",
             "apl/tabular-operators/extend-operator",
             "apl/tabular-operators/extend-valid-operator",
+            "apl/tabular-operators/join-operator",
             "apl/tabular-operators/limit-operator",
             "apl/tabular-operators/order-operator",
             "apl/tabular-operators/parse-operator",

process-data/destinations/manage-destinations.mdx

@@ -4,7 +4,7 @@ description: 'This page explains how to manage Flow destinations.'
 ---
 
 <Note>
-    Flow is currently in preview. To try it out, [sign up for a free account](https://app.axiom.co/flows).
+    Flow is currently in private preview. To try it out, [sign up for a free account](https://app.axiom.co/flows).
 </Note>
 
 To transform and route data from an Axiom dataset to a destination, you need to set up a destination. This is where data is routed. Once you set up a destination, it can be used in any flow configuration.

process-data/flows.mdx

@@ -6,7 +6,7 @@ description: 'This page explains how to set up a flow to filter, shape, and rout
 import Prerequisites from "/snippets/minimal-prerequisites.mdx"
 
 <Note>
-    Flow is currently in preview. To try it out, [sign up for a free preview](https://app.axiom.co/flows).
+    Flow is currently in private preview. To try it out, [sign up for a free preview](https://app.axiom.co/flows).
 </Note>
 
 A flow is a way to filter, shape, and route data from an Axiom dataset to a destination that you choose. This page explains how to set up a flow.

process-data/introduction.mdx

@@ -7,7 +7,7 @@ sidebarTitle: Introduction
 Flow provides onward event processing, including filtering, shaping, and routing. Flow works after persisting data in Axiom’s highly efficient queryable store, and uses [APL](/apl/introduction) to define processing.
 
 <Note>
-    Flow is currently in preview. To try it out, [sign up for a free account](https://app.axiom.co/flows).
+    Flow is currently in private preview. To try it out, [sign up for a free account](https://app.axiom.co/flows).
 </Note>
 
 ## Elements of a flow
@@ -25,7 +25,7 @@ There are three types of flows:
 - **Continuous flows** are continuously running operations that process your incoming data and route the outputs to a destination in real-time.
 
 <Note>
-    Flow is currently in preview, with support for one-time and continuous flows.
+    Flow is currently in private preview, with support for one-time and continuous flows.
 </Note>
 
 To get started with Flow, see [Configure Flow](/process-data/flows).

restapi/pagination.mdx

@@ -17,9 +17,9 @@ You can use pagination for the following endpoints:
 You can use one of the following pagination mechanisms:
 
 - [Pagination based on timestamp](#timestamp-based-pagination) (stable)
-- [Pagination based on cursor](#cursor-based-pagination) (preview)
+- [Pagination based on cursor](#cursor-based-pagination) (public preview)
 
-Axiom recommends timestamp-based pagination. Cursor-based pagination is in preview and may result in data loss.
+Axiom recommends timestamp-based pagination. Cursor-based pagination is in public preview and may return unexpected query results.
 
 ## Timestamp-based pagination
 
@@ -129,7 +129,7 @@ curl -X 'POST' 'https://api.axiom.co/v1/datasets/{dataset_id}/query' \
 
 ## Cursor-based pagination
 
-Cursor-based pagination is in preview and may result in data loss. Axiom recommends timestamp-based pagination.
+Cursor-based pagination is in public preview and may return unexpected query results. Axiom recommends timestamp-based pagination.
 
 The parameters and mechanisms differ between the current and legacy endpoints.