From 528f31f886a4be06f7b8c1d2ef0dc071e01a2145 Mon Sep 17 00:00:00 2001 From: melindafekete Date: Mon, 24 Nov 2025 14:12:50 +0100 Subject: [PATCH] update get started --- .../implementing-feature-flags-django.md | 2 +- .../implementing-feature-flags-dotnet.md | 2 +- .../implementing-feature-flags-golang.md | 2 +- .../java/implementing-feature-flags.mdx | 2 +- ...spring-boot-implementing-feature-flags.mdx | 2 +- .../python/implementing-feature-flags.mdx | 2 +- .../rails/implementing-feature-flags-rails.md | 2 +- .../ruby/implementing-feature-flags-ruby.mdx | 2 +- .../rust/implementing-feature-flags-rust.md | 2 +- .../use-cases/a-b-testing.md | 2 +- .../use-cases/gradual-rollout.md | 2 +- .../use-cases/organize-feature-flags.mdx | 2 +- .../use-cases/security-compliance.md | 2 +- .../use-cases/trunk-based-development.md | 2 +- .../docs/{ => get-started}/api-overview.mdx | 0 .../{ => get-started}/guides-overview.mdx | 2 +- website/docs/{ => get-started}/quickstart.mdx | 0 website/docs/get-started/unleash-overview.mdx | 6 ++-- .../docs/guides/unleash-edge-quickstart.md | 4 +-- .../reference/api/legacy/unleash/index.md | 2 +- website/docs/reference/whats-new-v4.md | 2 +- website/docs/support/oss-comparison.mdx | 2 +- website/docs/support/troubleshooting.mdx | 2 +- website/docusaurus.config.ts | 2 +- website/sidebars.ts | 8 ++--- website/vercel.json | 35 +++++++++++++------ 26 files changed, 54 insertions(+), 39 deletions(-) rename website/docs/{ => get-started}/api-overview.mdx (100%) rename website/docs/{ => get-started}/guides-overview.mdx (95%) rename website/docs/{ => get-started}/quickstart.mdx (100%) diff --git a/website/docs/feature-flag-tutorials/django/implementing-feature-flags-django.md b/website/docs/feature-flag-tutorials/django/implementing-feature-flags-django.md index 74670719df..cd10650a08 100644 --- a/website/docs/feature-flag-tutorials/django/implementing-feature-flags-django.md +++ b/website/docs/feature-flag-tutorials/django/implementing-feature-flags-django.md @@ -18,7 +18,7 @@ For this tutorial, you'll need the following: ![architecture diagram for our implementation](../rails/diagram.png) -The Unleash Server is a **Feature Flag Control Service**, which manages your feature flags and lets you retrieve flag data. Unleash has a UI for creating and managing projects and feature flags. For backend applications or automated scripts, Unleash exposes an [API](/api-overview) defined by an OpenAPI specification, allowing you to perform these actions programmatically. +The Unleash Server is a **Feature Flag Control Service**, which manages your feature flags and lets you retrieve flag data. Unleash has a UI for creating and managing projects and feature flags. For backend applications or automated scripts, Unleash exposes an [API](/get-started/api-overview) defined by an OpenAPI specification, allowing you to perform these actions programmatically. ## 1. Install a local feature flag provider diff --git a/website/docs/feature-flag-tutorials/dotnet/implementing-feature-flags-dotnet.md b/website/docs/feature-flag-tutorials/dotnet/implementing-feature-flags-dotnet.md index 4980d29a4c..4e14c25d94 100644 --- a/website/docs/feature-flag-tutorials/dotnet/implementing-feature-flags-dotnet.md +++ b/website/docs/feature-flag-tutorials/dotnet/implementing-feature-flags-dotnet.md @@ -24,7 +24,7 @@ For this tutorial, you’ll need the following: ![architecture diagram for our implementation](./diagram.png) -The Unleash Server is a **Feature Flag Control Service**, which manages your feature flags and lets you retrieve flag data. Unleash has a UI for creating and managing projects and feature flags. There are also [API commands available](/api-overview) to perform the same actions straight from your CLI or app. +The Unleash Server is a **Feature Flag Control Service**, which manages your feature flags and lets you retrieve flag data. Unleash has a UI for creating and managing projects and feature flags. There are also [API commands available](/get-started/api-overview) to perform the same actions straight from your CLI or app. ## 1. Install a local feature flag provider diff --git a/website/docs/feature-flag-tutorials/golang/implementing-feature-flags-golang.md b/website/docs/feature-flag-tutorials/golang/implementing-feature-flags-golang.md index b6116bfc44..8ad3e532ce 100644 --- a/website/docs/feature-flag-tutorials/golang/implementing-feature-flags-golang.md +++ b/website/docs/feature-flag-tutorials/golang/implementing-feature-flags-golang.md @@ -21,7 +21,7 @@ For this tutorial, you'll need the following: ![architecture diagram for our implementation](./diagram.png) -The Unleash Server is a **Feature Flag Control Service**, which manages your feature flags and lets you retrieve flag data. Unleash has a UI for creating and managing projects and feature flags. You can perform the same actions straight from your CLI or server-side app using the [Unleash API](/api-overview). +The Unleash Server is a **Feature Flag Control Service**, which manages your feature flags and lets you retrieve flag data. Unleash has a UI for creating and managing projects and feature flags. You can perform the same actions straight from your CLI or server-side app using the [Unleash API](/get-started/api-overview). ## Best practices for back-end apps with Unleash diff --git a/website/docs/feature-flag-tutorials/java/implementing-feature-flags.mdx b/website/docs/feature-flag-tutorials/java/implementing-feature-flags.mdx index 354d12bdf8..4f11ef7f75 100644 --- a/website/docs/feature-flag-tutorials/java/implementing-feature-flags.mdx +++ b/website/docs/feature-flag-tutorials/java/implementing-feature-flags.mdx @@ -37,7 +37,7 @@ In this tutorial, you will need the following: This architecture diagram breaks down how the Java app works with Unleash to control feature flags. We connect the Unleash service to your Java app using the Java SDK. -The Unleash Server acts as a Feature Flag Control Service, managing and storing your feature flags. It enables the retrieval of flag data and, particularly when not utilizing a user interface, supports the sending of data to and from the service. The Unleash Server has a UI for creating and managing projects and feature flags. There are also [API commands available](/api-overview) to perform the same actions straight from your CLI or server-side app. +The Unleash Server acts as a Feature Flag Control Service, managing and storing your feature flags. It enables the retrieval of flag data and, particularly when not utilizing a user interface, supports the sending of data to and from the service. The Unleash Server has a UI for creating and managing projects and feature flags. There are also [API commands available](/get-started/api-overview) to perform the same actions straight from your CLI or server-side app. ## 1. Feature Flag best practices for backend apps diff --git a/website/docs/feature-flag-tutorials/java/spring-boot-implementing-feature-flags.mdx b/website/docs/feature-flag-tutorials/java/spring-boot-implementing-feature-flags.mdx index da5ad49cf1..ab87ec9bab 100644 --- a/website/docs/feature-flag-tutorials/java/spring-boot-implementing-feature-flags.mdx +++ b/website/docs/feature-flag-tutorials/java/spring-boot-implementing-feature-flags.mdx @@ -38,7 +38,7 @@ In this tutorial, you will need the following: This architecture diagram breaks down how the Java Spring Boot app works with Unleash to use feature flags. -The Unleash Server is a Feature Flag Control Service for managing and storing your feature flags. It enables the retrieval of flag data and, particularly when not utilizing a user interface, supports sending data to and from the service. The Unleash Server has a UI for creating and managing projects and feature flags. API commands are also [available](/api-overview) to perform the same actions from your CLI or server-side app. +The Unleash Server is a Feature Flag Control Service for managing and storing your feature flags. It enables the retrieval of flag data and, particularly when not utilizing a user interface, supports sending data to and from the service. The Unleash Server has a UI for creating and managing projects and feature flags. API commands are also [available](/get-started/api-overview) to perform the same actions from your CLI or server-side app. The Spring Boot SDK is an extension of the Java SDK, configured for Spring Boot-specific architecture and conventions. diff --git a/website/docs/feature-flag-tutorials/python/implementing-feature-flags.mdx b/website/docs/feature-flag-tutorials/python/implementing-feature-flags.mdx index 6f74b837a2..be8a6e55d6 100644 --- a/website/docs/feature-flag-tutorials/python/implementing-feature-flags.mdx +++ b/website/docs/feature-flag-tutorials/python/implementing-feature-flags.mdx @@ -43,7 +43,7 @@ In this tutorial, you will need the following: This architecture diagram breaks down how the Python app works with Unleash to control feature flags. We connect the Unleash service to your Python app using the Python SDK. -The Unleash Server is a **Feature Flag Control Service**, which is a service that manages your feature flags and is used to retrieve flag data from (and send data to, especially when not using a UI). The Unleash server has a UI for creating and managing projects and feature flags. There are also [API commands available](/api-overview) to perform the same actions straight from your CLI or server-side app. +The Unleash Server is a **Feature Flag Control Service**, which is a service that manages your feature flags and is used to retrieve flag data from (and send data to, especially when not using a UI). The Unleash server has a UI for creating and managing projects and feature flags. There are also [API commands available](/get-started/api-overview) to perform the same actions straight from your CLI or server-side app. ## 1. Unleash best practice for backend apps diff --git a/website/docs/feature-flag-tutorials/rails/implementing-feature-flags-rails.md b/website/docs/feature-flag-tutorials/rails/implementing-feature-flags-rails.md index 3ea3791590..0383f8e9ba 100644 --- a/website/docs/feature-flag-tutorials/rails/implementing-feature-flags-rails.md +++ b/website/docs/feature-flag-tutorials/rails/implementing-feature-flags-rails.md @@ -30,7 +30,7 @@ For this tutorial, you’ll need the following: ![architecture diagram for our implementation](./diagram.png) -The Unleash Server is a **Feature Flag Control Service**, which manages your feature flags and lets you retrieve flag data. Unleash has a UI for creating and managing projects and feature flags. There are also [API commands available](/api-overview) to perform the same actions straight from your CLI or server-side app. +The Unleash Server is a **Feature Flag Control Service**, which manages your feature flags and lets you retrieve flag data. Unleash has a UI for creating and managing projects and feature flags. There are also [API commands available](/get-started/api-overview) to perform the same actions straight from your CLI or server-side app. ## 1. Best practices for back-end apps with Unleash diff --git a/website/docs/feature-flag-tutorials/ruby/implementing-feature-flags-ruby.mdx b/website/docs/feature-flag-tutorials/ruby/implementing-feature-flags-ruby.mdx index cdfa27765a..766e7a4daa 100644 --- a/website/docs/feature-flag-tutorials/ruby/implementing-feature-flags-ruby.mdx +++ b/website/docs/feature-flag-tutorials/ruby/implementing-feature-flags-ruby.mdx @@ -35,7 +35,7 @@ For this tutorial, you’ll need the following: ![architecture diagram for our implementation](./diagram.png) -The Unleash Server is a **Feature Flag Control Service**, which manages your feature flags and lets you retrieve flag data. Unleash has a UI for creating and managing projects and feature flags. There are also [API commands available](/api-overview) to perform the same actions straight from your CLI or server-side app. +The Unleash Server is a **Feature Flag Control Service**, which manages your feature flags and lets you retrieve flag data. Unleash has a UI for creating and managing projects and feature flags. There are also [API commands available](/get-started/api-overview) to perform the same actions straight from your CLI or server-side app. ## 1. Best practices for back-end apps with Unleash diff --git a/website/docs/feature-flag-tutorials/rust/implementing-feature-flags-rust.md b/website/docs/feature-flag-tutorials/rust/implementing-feature-flags-rust.md index 5195c7f1d4..170714a540 100644 --- a/website/docs/feature-flag-tutorials/rust/implementing-feature-flags-rust.md +++ b/website/docs/feature-flag-tutorials/rust/implementing-feature-flags-rust.md @@ -26,7 +26,7 @@ For this tutorial, you’ll need the following: ![architecture diagram for our implementation](./diagram.png) -The Unleash Server is a **Feature Flag Control Service**, which manages your feature flags and lets you retrieve flag data. Unleash has a UI for creating and managing projects and feature flags. There are also [API commands available](/api-overview) to perform the same actions straight from your CLI or app. +The Unleash Server is a **Feature Flag Control Service**, which manages your feature flags and lets you retrieve flag data. Unleash has a UI for creating and managing projects and feature flags. There are also [API commands available](/get-started/api-overview) to perform the same actions straight from your CLI or app. ## 1. Install a local feature flag provider diff --git a/website/docs/feature-flag-tutorials/use-cases/a-b-testing.md b/website/docs/feature-flag-tutorials/use-cases/a-b-testing.md index c1b900f54b..d00c292167 100644 --- a/website/docs/feature-flag-tutorials/use-cases/a-b-testing.md +++ b/website/docs/feature-flag-tutorials/use-cases/a-b-testing.md @@ -12,7 +12,7 @@ Feature flags are a great way to run A/B or multivariate tests with minimal code ## How to perform A/B testing with feature flags -To follow along with this tutorial, you need access to an Unleash instance to create and manage feature flags. Head over to our [Quick Start documentation](/quickstart) for options, including running locally or using an [Unleash SaaS instance](https://www.getunleash.io/pricing?). +To follow along with this tutorial, you need access to an Unleash instance to create and manage feature flags. Head over to our [Quick Start documentation](/get-started/quickstart) for options, including running locally or using an [Unleash SaaS instance](https://www.getunleash.io/pricing?). With Unleash set up, you can use your application to talk to Unleash through one of our [SDKs](/reference/sdks). diff --git a/website/docs/feature-flag-tutorials/use-cases/gradual-rollout.md b/website/docs/feature-flag-tutorials/use-cases/gradual-rollout.md index 9b3b9e0910..394f29d4dc 100644 --- a/website/docs/feature-flag-tutorials/use-cases/gradual-rollout.md +++ b/website/docs/feature-flag-tutorials/use-cases/gradual-rollout.md @@ -20,7 +20,7 @@ The key benefits of gradual rollouts are that you can experiment rapidly on a co ## How to perform a gradual rollout with Unleash -To follow along with this tutorial, you will need an Unleash instance. If you’d prefer to self-host Unleash, read our [Quickstart guide](/quickstart). Alternatively, if you’d like your project to be hosted by Unleash, go to [getunleash.io](https://www.getunleash.io/pricing). +To follow along with this tutorial, you will need an Unleash instance. If you’d prefer to self-host Unleash, read our [Quickstart guide](/get-started/quickstart). Alternatively, if you’d like your project to be hosted by Unleash, go to [getunleash.io](https://www.getunleash.io/pricing). With Unleash set up, you can use your application to talk to Unleash through one of our SDKs. diff --git a/website/docs/feature-flag-tutorials/use-cases/organize-feature-flags.mdx b/website/docs/feature-flag-tutorials/use-cases/organize-feature-flags.mdx index 0c7195ed03..c0dc04b1a8 100644 --- a/website/docs/feature-flag-tutorials/use-cases/organize-feature-flags.mdx +++ b/website/docs/feature-flag-tutorials/use-cases/organize-feature-flags.mdx @@ -135,7 +135,7 @@ A common challenge is managing a single feature that spans multiple services (fo - **Use separate, coordinated flags**: If the services are owned by different teams and have different release cadences, it's better to create separate flags in their respective projects. This prevents one team from impacting another's release. The rollout can then be coordinated across teams using release templates. ## Evolve your structure -Remember that your initial project and environment structure is not set in stone. Unleash is flexible. You can add new environments, create new projects, and even move flags between them later. For larger migrations, you can use the [Import/Export](/reference/import-export) functionality or the [Admin API](/api-overview). +Remember that your initial project and environment structure is not set in stone. Unleash is flexible. You can add new environments, create new projects, and even move flags between them later. For larger migrations, you can use the [Import/Export](/reference/import-export) functionality or the [Admin API](/get-started/api-overview). The system is designed to evolve with your organization, so don't be afraid to start with a simple setup and refactor as your needs change. diff --git a/website/docs/feature-flag-tutorials/use-cases/security-compliance.md b/website/docs/feature-flag-tutorials/use-cases/security-compliance.md index e0823f4d7d..abd57db221 100644 --- a/website/docs/feature-flag-tutorials/use-cases/security-compliance.md +++ b/website/docs/feature-flag-tutorials/use-cases/security-compliance.md @@ -177,7 +177,7 @@ For more advanced implementations, integrate Unleash event logs directly into br ### Leverage access logs for broader auditing -Let’s think back to the importance of user management that we covered earlier. Developers and other stakeholders go through onboarding to use the platform. Authentication protocols and user provisioning ensure these processes are secure, unified, and automated. During this process, access logs keep track of what users and systems accessed Unleash and what actions they performed, including [Unleash API interactions](/api-overview) from your services and applications. You can export these logs to S3 buckets for long-term data storage. This is valuable if you need to preserve data for complying with legal or regulatory compliance, storing critical backups for disaster recovery, and archiving. +Let’s think back to the importance of user management that we covered earlier. Developers and other stakeholders go through onboarding to use the platform. Authentication protocols and user provisioning ensure these processes are secure, unified, and automated. During this process, access logs keep track of what users and systems accessed Unleash and what actions they performed, including [Unleash API interactions](/get-started/api-overview) from your services and applications. You can export these logs to S3 buckets for long-term data storage. This is valuable if you need to preserve data for complying with legal or regulatory compliance, storing critical backups for disaster recovery, and archiving. Auditing your feature flag system is made simple for traceability and reportability with Unleash’s event logs and access logs. We recommend leveraging these features as data sources for third-party services that make your data a valuable asset for security reviews, meeting compliance standards, and overall risk mitigation. diff --git a/website/docs/feature-flag-tutorials/use-cases/trunk-based-development.md b/website/docs/feature-flag-tutorials/use-cases/trunk-based-development.md index 046ad52615..cb7f5ec3f5 100644 --- a/website/docs/feature-flag-tutorials/use-cases/trunk-based-development.md +++ b/website/docs/feature-flag-tutorials/use-cases/trunk-based-development.md @@ -13,7 +13,7 @@ Unleash provides a powerful mechanism for safely managing and controlling these ## How to implement trunk-based development with feature flags -To follow along with this tutorial, you need access to an Unleash instance to create and manage feature flags. Head over to our [Quick Start documentation](/quickstart) for options, including running locally or using an [Unleash SaaS instance](https://www.getunleash.io/pricing?). +To follow along with this tutorial, you need access to an Unleash instance to create and manage feature flags. Head over to our [Quick Start documentation](/get-started/quickstart) for options, including running locally or using an [Unleash SaaS instance](https://www.getunleash.io/pricing?). With Unleash set up, you can use your application to talk to Unleash through one of our [SDKs](/reference/sdks). diff --git a/website/docs/api-overview.mdx b/website/docs/get-started/api-overview.mdx similarity index 100% rename from website/docs/api-overview.mdx rename to website/docs/get-started/api-overview.mdx diff --git a/website/docs/guides-overview.mdx b/website/docs/get-started/guides-overview.mdx similarity index 95% rename from website/docs/guides-overview.mdx rename to website/docs/get-started/guides-overview.mdx index af0bc7f3c4..6a8fcedbcd 100644 --- a/website/docs/guides-overview.mdx +++ b/website/docs/get-started/guides-overview.mdx @@ -6,7 +6,7 @@ displayed_sidebar: documentation This overview helps you explore our hands-on tutorials and best-practice guides. Each section groups resources around a specific theme, helping you build, ship, and scale features with confidence. -If you're new to Unleash, start with our [Quickstart](/quickstart) guide to set up your environment, then choose a track below based on what you're building. +If you're new to Unleash, start with our [Quickstart](/get-started/quickstart) guide to set up your environment, then choose a track below based on what you're building. --- ## Feature management best practices diff --git a/website/docs/quickstart.mdx b/website/docs/get-started/quickstart.mdx similarity index 100% rename from website/docs/quickstart.mdx rename to website/docs/get-started/quickstart.mdx diff --git a/website/docs/get-started/unleash-overview.mdx b/website/docs/get-started/unleash-overview.mdx index d161c618a6..726b58461f 100644 --- a/website/docs/get-started/unleash-overview.mdx +++ b/website/docs/get-started/unleash-overview.mdx @@ -72,13 +72,13 @@ Beyond scalability, Unleash Edge also offers privacy and security benefits for f #### Client API -The [Client API](/api-overview) is the API used by backend SDKs to fetch feature flag configurations and send SDK usage metrics to Unleash. +The [Client API](/get-started/api-overview) is the API used by backend SDKs to fetch feature flag configurations and send SDK usage metrics to Unleash. #### Frontend API -The [Frontend API](/api-overview) is the API used by frontend SDKs to retrieve all enabled feature flags for a given [Unleash Context](/reference/unleash-context) and send SDK usage metrics to Unleash. +The [Frontend API](/get-started/api-overview) is the API used by frontend SDKs to retrieve all enabled feature flags for a given [Unleash Context](/reference/unleash-context) and send SDK usage metrics to Unleash. #### Admin API -The [Admin API](/api-overview) is an API layer for managing all aspects of your Unleash instance, including creating, updating, and deleting resources, such as feature flags, activation strategies, and environments. This API is used by the [Unleash Admin UI](#the-unleash-admin-ui) and other tools and [integrations](/reference/integrations). +The [Admin API](/get-started/api-overview) is an API layer for managing all aspects of your Unleash instance, including creating, updating, and deleting resources, such as feature flags, activation strategies, and environments. This API is used by the [Unleash Admin UI](#the-unleash-admin-ui) and other tools and [integrations](/reference/integrations). | API | Used by | Available endpoints | |---------------|---------|---| diff --git a/website/docs/guides/unleash-edge-quickstart.md b/website/docs/guides/unleash-edge-quickstart.md index 0da5ae32ef..778be96835 100644 --- a/website/docs/guides/unleash-edge-quickstart.md +++ b/website/docs/guides/unleash-edge-quickstart.md @@ -11,7 +11,7 @@ This document helps you get started with [Unleash Edge](https://docs.getunleash. ## Why Unleash Edge Unleash Edge is a lightweight layer between your SDKs and your Unleash instance. -It exposes the same HTTP interface as the main [Unleash API](/api-overview) but is built for higher throughput and lower latency. +It exposes the same HTTP interface as the main [Unleash API](/get-started/api-overview) but is built for higher throughput and lower latency. @@ -39,7 +39,7 @@ It exposes the same HTTP interface as the main [Unleash API](/api-overview) but Here's what you need before getting started: -1. An [Unleash instance](https://docs.getunleash.io/quickstart) running locally or remotely (version `4.15` or later) +1. An [Unleash instance](https://docs.getunleash.io/get-started/quickstart) running locally or remotely (version `4.15` or later) 2. A valid [API token](https://docs.getunleash.io/reference/api-tokens-and-client-keys) for your Unleash instance 3. [Docker](https://www.docker.com/get-started/) installed and running 4. Your preferred Unleash SDK in a [sample app](https://github.com/Unleash/unleash-sdk-examples) diff --git a/website/docs/reference/api/legacy/unleash/index.md b/website/docs/reference/api/legacy/unleash/index.md index 733fa38cdf..afdf614023 100644 --- a/website/docs/reference/api/legacy/unleash/index.md +++ b/website/docs/reference/api/legacy/unleash/index.md @@ -9,7 +9,7 @@ import SearchPriority from '@site/src/components/SearchPriority'; :::caution -These APIs have been deprecared. Wse the [Unleash OpenAPI docs](/api-overview) reference instead. +These APIs have been deprecared. Wse the [Unleash OpenAPI docs](/get-started/api-overview) reference instead. ::: diff --git a/website/docs/reference/whats-new-v4.md b/website/docs/reference/whats-new-v4.md index ba904f3efb..2ba50fb538 100644 --- a/website/docs/reference/whats-new-v4.md +++ b/website/docs/reference/whats-new-v4.md @@ -44,7 +44,7 @@ In version 4 we improved the User Management and made it available for Unleash O In version 4 we improved the API Access and made it available for Unleash Open-Source and Unleash Enterprise. Starting from Unleash v4 we require all SDKs to use an access token in order to connect to Unleash. -[Read more](/api-overview) +[Read more](/get-started/api-overview) ### Custom stickiness {#custom-stickiness} diff --git a/website/docs/support/oss-comparison.mdx b/website/docs/support/oss-comparison.mdx index 0c124a1787..05b2261810 100644 --- a/website/docs/support/oss-comparison.mdx +++ b/website/docs/support/oss-comparison.mdx @@ -21,7 +21,7 @@ This page highlights the key differences between Unleash OSS and Unleash Enterpr | [Projects](/reference/projects) | 1 | Unlimited | | [Environments](/reference/environments) | 2 | Unlimited | | [Private or protected projects](/reference/project-collaboration-mode) | ❌ | ✅ | -| [SDKs](/reference/sdks) and [APIs](/api-overview) | ✅ | ✅ | +| [SDKs](/reference/sdks) and [APIs](/get-started/api-overview) | ✅ | ✅ | | [Activation strategies](/reference/activation-strategies) and [stickiness](/reference/stickiness) | ✅ | ✅ | | [Playground](/reference/playground) | ✅ | ✅ | | [Release templates](/reference/release-templates) | ❌ | ✅ | diff --git a/website/docs/support/troubleshooting.mdx b/website/docs/support/troubleshooting.mdx index dc9d05dcd9..6bb3a2154c 100644 --- a/website/docs/support/troubleshooting.mdx +++ b/website/docs/support/troubleshooting.mdx @@ -110,7 +110,7 @@ Cross-Origin Resource Sharing (CORS) issues can prevent your client-side applica - Define the allowed origins (e.g., `https://your-app.com`). - **For troubleshooting:** You can temporarily set the allowed origin to `*` (a single asterisk) to allow all origins. This helps confirm if CORS is the root cause. - **Important Security Note:** Using `*` in production is generally discouraged. Always restrict origins to only those that require access. -- These settings can also be managed via the [Unleash API](/api-overview). +- These settings can also be managed via the [Unleash API](/get-started/api-overview). ### Configuring CORS for Unleash Edge diff --git a/website/docusaurus.config.ts b/website/docusaurus.config.ts index e40f1ffcfa..9c6849d4fc 100644 --- a/website/docusaurus.config.ts +++ b/website/docusaurus.config.ts @@ -359,7 +359,7 @@ class="header-github-link" items: [ { label: 'Quickstart', - to: '/quickstart', + to: '/get-started/quickstart', }, { label: 'Unleash architecture', diff --git a/website/sidebars.ts b/website/sidebars.ts index e719401626..badff1ec8b 100644 --- a/website/sidebars.ts +++ b/website/sidebars.ts @@ -42,13 +42,13 @@ const sidebars: SidebarsConfig = { type: 'category', link: { type: 'doc', - id: 'quickstart', + id: 'get-started/quickstart', }, items: [ { type: 'doc', label: 'Quickstart', - id: 'quickstart', + id: 'get-started/quickstart', }, { type: 'doc', @@ -201,7 +201,7 @@ const sidebars: SidebarsConfig = { type: 'category', link: { type: 'doc', - id: 'guides-overview', + id: 'get-started/guides-overview', }, items: [ { @@ -552,7 +552,7 @@ const sidebars: SidebarsConfig = { type: 'category', link: { type: 'doc', - id: 'api-overview', + id: 'get-started/api-overview', }, items: [ docsSidebar, diff --git a/website/vercel.json b/website/vercel.json index 957d18190f..4189a2cd84 100644 --- a/website/vercel.json +++ b/website/vercel.json @@ -113,12 +113,12 @@ }, { "source": "/reference/api/unleash", - "destination": "/api-overview", + "destination": "/get-started/api-overview", "permanent": true }, { "source": "/api/open_api", - "destination": "/api-overview", + "destination": "/get-started/api-overview", "permanent": true }, { @@ -548,22 +548,22 @@ }, { "source": "/user_guide/quickstart", - "destination": "/quickstart", + "destination": "/get-started/quickstart", "permanent": true }, { "source": "/docs/getting_started", - "destination": "/quickstart", + "destination": "/get-started/quickstart", "permanent": true }, { "source": "/tutorials/quickstart", - "destination": "/quickstart", + "destination": "/get-started/quickstart", "permanent": true }, { "source": "/tutorials/getting-started", - "destination": "/quickstart", + "destination": "/get-started/quickstart", "permanent": true }, { @@ -773,12 +773,12 @@ }, { "source": "/how-to/how-to-enable-openapi", - "destination": "/api-overview", + "destination": "/get-started/api-overview", "permanent": true }, { "source": "/how-to/api", - "destination": "/api-overview", + "destination": "/get-started/api-overview", "permanent": true }, { @@ -813,7 +813,7 @@ }, { "source": "/using-unleash", - "destination": "/api-overview", + "destination": "/get-started/api-overview", "permanent": true }, { @@ -1018,7 +1018,7 @@ }, { "source": "/topics", - "destination": "/guides-overview", + "destination": "/get-started/guides-overview", "permanent": true }, { @@ -1071,6 +1071,21 @@ "destination": "/support/oss-comparison", "permanent": true }, + { + "source": "/api-overview", + "destination": "/get-started/api-overview", + "permanent": true + }, + { + "source": "/guides-overview", + "destination": "/get-started/guides-overview", + "permanent": true + }, + { + "source": "/quickstart", + "destination": "/get-started/quickstart", + "permanent": true + }, { "source": "/how-to/sso", "destination": "/single-sign-on/how-to-add-sso-open-id-connect",