docs: updates to Unleash Frontend API docs and Unleash architecture overview

src/lib/openapi/util/openapi-tags.ts

@@ -68,7 +68,7 @@ const OPENAPI_TAGS = [
     {
         name: 'Frontend API',
         description:
-            'API for connecting client-side (frontend) applications to Unleash.',
+            'The [Frontend API](https://docs.getunleash.io/reference/front-end-api) is used for connecting client-side (frontend) applications to Unleash.',
     },
     {
         name: 'Import/Export',

website/docs/reference/activation-strategies.md

@@ -63,7 +63,7 @@ These parts turn the constraint into an expression that evaluates to true or fal
 
 #### Constraint operators
 
-Constraint operators help you define the conditional statements that get evaluated as part of the constraint. [Basic operators](#basic-operators) are available in all versions and SDKs. All other operators require Unleash version 4.9+ and [SDK compatibility](/reference/sdks#server-side-sdk-compatibility-table).
+Constraint operators help you define the conditional statements that get evaluated as part of the constraint. [Basic operators](#basic-operators) are available in all versions and SDKs. All other operators require Unleash version 4.9+ and [SDK compatibility](/reference/sdks#feature-compatibility-in-server-side-sdks).
 
 All constraints can be negated. For example: 
 
@@ -72,14 +72,15 @@ All constraints can be negated. For example:
 | `STR_ENDS_WITH`  | "@user.com" | "[email protected]" | true |
 | NOT `STR_ENDS_WITH`  | "@user.com" | "[email protected]" | false |
 
-##### Basic operators
+#### Basic operators
 
 | Operator      | Description
 |-----------|--------------------------------------------------------------------------------|
 | `IN`  | The context field is equal to any of the provided values; case sensitive. |
 | `NOT_IN`  | The context field is not equal to any of the values provided; case sensitive. |
 
-#### Numeric operators
+#### Advanced operators
+##### Numeric operators
 
 Numeric operators compare the numeric value of context fields with the provided value. Numeric operators only accept single values.
 

website/docs/reference/api-tokens-and-client-keys.mdx

@@ -171,4 +171,4 @@ To designate a string as a proxy client key, add it to the `clientKeys` list whe
 
 :::
 
-Proxy client keys cannot be used to connect to the Unleash API; use [API tokens](#api-tokens) instead.
+Proxy client keys cannot be used to connect to the Unleash API; use API tokens instead.

website/docs/reference/feature-toggles.mdx

@@ -128,7 +128,7 @@ If an archived feature is revived, it starts a new lifecycle with a new [Define]
 
 **Plan**: [Pro](/availability#plans) and [Enterprise](https://www.getunleash.io/pricing)
 
-**Unleash version**: `5.7+` | **Unleash Edge version**: `13.1+` | **Unleash Proxy version**: `0.18+`. Requires [SDK compatibility](../reference/sdks#server-side-sdk-compatibility-table) for variants.
+**Unleash version**: `5.7+` | **Unleash Edge version**: `13.1+` | **Unleash Proxy version**: `0.18+`. Requires [SDK compatibility](../reference/sdks#feature-compatibility-in-server-side-sdks) for variants.
 :::
 
 Feature flag dependencies define a relationship between feature flags. Each feature flag can have one parent, but multiple child flags can share the same parent.

website/docs/reference/front-end-api.md

@@ -8,41 +8,30 @@ title: Frontend API
 
 :::
 
-The Unleash Frontend API offers a simplified workflow for connecting client-side applications to Unleash. It provides the exact same API as [Unleash Edge](https://docs.getunleash.io/reference/unleash-edge) and [Unleash Proxy - deprecated](../generated/unleash-proxy.md). The Frontend API is a quick and easy way to add Unleash to single-page applications and mobile apps.
+## Overview
 
-Compared to using Unleash Edge, using the Frontend API has both benefits and drawbacks. The benefits are:
+The Unleash [Frontend API](/reference/api/unleash/frontend-api) simplifies connecting client-side applications to Unleash. [Unleash Edge](https://docs.getunleash.io/reference/unleash-edge) also implements this API allowing you to scale from development environments, low-traffic applications, or internal dashboards to a production-ready scalable solution.
 
-- **You don't need to configure and run Unleash Edge.** The Frontend API is part of Unleash itself and not an external process. All clients will work exactly the same as they would with Unleash Edge.
+The Frontend API has a straightforward setup, and since it is built directly into Unleash, you don't need to manage it. However, unlike Unleash Edge, it cannot be scaled horizontally and isn’t designed for high request volumes.
 
-On the other hand, using the Frontend API has the following drawbacks compared to using Unleash Edge:
+Since the Frontend API shares the same API as Unleash Edge, you can start development with the Frontend API and transition to Unleash Edge when needed.
 
-- **It can't handle a large number of requests per second.** Because the Frontend API is part of Unleash, you can't scale it horizontally the way you can scale Unleash Edge.
-- **It sends client details to your Unleash instance.** Unleash only stores these details in its short-term runtime cache, but this can be a privacy issue for some use cases.
+## Configure the Frontend API
 
-These points make the Unleash Frontend API best suited for development purposes and applications that don’t receive a lot of traffic, such as internal dashboards. However, because the API is identical to the Unleash Edge API, you can go from one to the other at any time. As such, you can start out by using the Frontend API and switch to Unleash Edge when you need it.
+### Configure cross-origin resource sharing (CORS)
 
-## Using the Unleash Frontend API
+For web and hybrid mobile apps, allow traffic from your application's domains.
 
-When using the Frontend API in an SDK, there's three things you need to configure.
+For Unleash, you can update CORS settings in the Unleash Admin UI in **Admin > CORS origins**. For Unleash Edge, follow our [command-line for CORS settings](https://github.com/Unleash/unleash-edge/blob/243cfbdf2ef5f78a7312db6cc688cc74b7d5f318/CLI.md).
 
-### Cross-origin resource sharing (CORS) configuration {#cors}
+### Configure the API URL
 
-You need to allow traffic from your application domains to use the Unleash Frontend API with web and hybrid mobile applications. You can update the Frontend API CORS settings from the Unleash UI under _admin \> CORS_ or by using the API.
+Point your application to the correct API endpoint: `<your-unleash-instance>/api/frontend`.
 
-### API URL
+### Generate an API token
 
-The client needs to point to the correct API endpoint. The Frontend API is available at `<your-unleash-instance>/api/frontend`.
+Your application needs a [frontend token](../reference/api-tokens-and-client-keys.mdx#frontend-tokens) to interact with the Frontend API.
 
-<!-- Point to the API docs when they're published -->
+### Configure the refresh interval for tokens
 
-### API token
-
-The client needs a frontend [token](../reference/api-tokens-and-client-keys.mdx#frontend-tokens) to interact with the Frontend API.
-
-### Refresh interval for tokens
-
-Internally, Unleash creates a new Unleash client for each token it receives. Each client is configured with the project and environment specified in the token.
-
-Each client updates its feature flag configuration at a specified refresh interval plus a random offset between 0 and 10 seconds. By default, the refresh interval is set to 10 seconds. The random offset is used to stagger incoming requests to avoid a large number of clients all querying the database simultaneously. A new, random offset is used for every update.
-
-The refresh interval is specified in milliseconds and can be set by using the `FRONTEND_API_REFRESH_INTERVAL_MS` environment variable or by using the `frontendApi.refreshIntervalInMs` configuration option in code.
+Feature flag updates occur at a default refresh interval of 10 seconds plus a random offset (0-10 seconds) to prevent simultaneous database queries. You can customize the refresh interval using the `FRONTEND_API_REFRESH_INTERVAL_MS` environment variable or the `frontendApi.refreshIntervalInMs` configuration option in the SDK.

website/docs/reference/impression-data.md

@@ -5,7 +5,7 @@ pagination_next: reference/events
 
 :::note Availability
 
-**Version**: `4.7+`. Requires [SDK compatibility](../reference/sdks#server-side-sdk-compatibility-table).
+**Version**: `4.7+`. Requires [SDK compatibility](../reference/sdks#feature-compatibility-in-server-side-sdks).
 
 :::
 

website/docs/reference/rbac.md

@@ -92,7 +92,7 @@ You can assign the following root permissions:
 |---------------------|------------------------------------|
 | Change instance banners | Change instance [banners](./banners). |
 | Change maintenance mode state | Change [maintenance mode](./maintenance-mode) state. |
-| Update CORS settings | Update [CORS settings](./front-end-api#cors). |
+| Update CORS settings | Update [CORS settings](./front-end-api#configure-cross-origin-resource-sharing-cors). |
 | Read instance logs and login history | Read instance logs and [login history](./login-history.md). |
 
 #### Integration permissions