Rename topics

README.md

@@ -122,7 +122,7 @@ We know that learning a new tool can be hard and time-consuming. We have a growi
 
 📚 [Visit the documentation](https://docs.getunleash.io/) for more in-depth descriptions, how-to guides, and more.
 
-📖 Learn more about the principles of building and scaling [feature flag](https://docs.getunleash.io/topics/feature-flags/feature-flag-best-practices) solutions.
+📖 Learn more about the principles of building and scaling [feature flag](https://docs.getunleash.io/guides/feature-flag-best-practices) solutions.
 
 <br/>
 

website/docs/feature-flag-tutorials/golang/implementing-feature-flags-golang.md

@@ -34,7 +34,7 @@ Most importantly, you must:
 
 ![A gradual rollout form can allow you to customize your flag strategy.](/img/go-example-rollout.png)
 
-For a complete list of architectural guidelines, including caching strategies, see our [best practices for building and scaling feature flag systems](/topics/feature-flags/feature-flag-best-practices).
+For a complete list of architectural guidelines, including caching strategies, see our [best practices for building and scaling feature flag systems](/guides/feature-flag-best-practices).
 
 ## Install a local feature flag provider
 

website/docs/feature-flag-tutorials/ios/implementing-feature-flags-ios.md

@@ -39,13 +39,13 @@ a. Limit PII (personally identifiable information) leakage from the end-user dev
 
 b. Avoid leakage of configuration information from the central feature flag control service to end-user devices.
 
-Solving both means you need to avoid evaluating feature flags on the user's machine due to security risks like exposing API keys and flag data. Instead, send application context (e.g. username, location, etc) to your feature flag evaluation service to evaluate the results. These results (and only these results) should be stored in the client-side application memory. By keeping the evaluated results for a specific context in memory, you avoid network roundtrips every time your application needs to check the status of a feature flag. This method prevents unauthorized access and data breaches by [keeping configurations and PII secure](/topics/feature-flags/feature-flag-best-practices#6-protect-pii-by-evaluating-flags-server-side).
+Solving both means you need to avoid evaluating feature flags on the user's machine due to security risks like exposing API keys and flag data. Instead, send application context (e.g. username, location, etc) to your feature flag evaluation service to evaluate the results. These results (and only these results) should be stored in the client-side application memory. By keeping the evaluated results for a specific context in memory, you avoid network roundtrips every time your application needs to check the status of a feature flag. This method prevents unauthorized access and data breaches by [keeping configurations and PII secure](/guides/feature-flag-best-practices#6-protect-pii-by-evaluating-flags-server-side).
 
 ![Keep configurations and PII secure image](/img/react-tutorial-pii-diagram.png)
 
 Unleash, the open-source feature flag system used in this tutorial, evaluates feature flags in this way, so by following the rest of these steps, you will be protecting your user’s data and your company’s reputation.
 
-For a complete list of architectural guidelines, see our [best practices for building and scaling feature flag systems](/topics/feature-flags/feature-flag-best-practices).
+For a complete list of architectural guidelines, see our [best practices for building and scaling feature flag systems](/guides/feature-flag-best-practices).
 
 ## 2. Install a local feature flag provider
 

website/docs/feature-flag-tutorials/java/implementing-feature-flags.mdx

@@ -52,7 +52,7 @@ As your application scales, performance and resiliency become more critical and
 
 Additionally, you can cache your feature flag configuration to help reduce network round trips and dependency on external services. You can rely on the cache if your Feature Flag Control Service is not available, which will mitigate potential failure in your application.
 
-For a complete list of architectural guidelines, see our [best practices for building and scaling feature flag systems](https://docs.getunleash.io/topics/feature-flags/feature-flag-best-practices).
+For a complete list of architectural guidelines, see our [best practices for building and scaling feature flag systems](https://docs.getunleash.io//guides/feature-flag-best-practices).
 
 ## 2. Install a local feature flag provider
 

website/docs/feature-flag-tutorials/java/spring-boot-implementing-feature-flags.mdx

@@ -55,7 +55,7 @@ As your application scales, performance and resiliency become more critical and
 
 Additionally, you can cache your feature flag configuration to help reduce network round trips and dependency on external services. You can rely on the cache if your Feature Flag Control Service is unavailable, mitigating potential application failure.
 
-For a complete list of architectural guidelines, see our [best practices for building and scaling feature flag systems](/topics/feature-flags/feature-flag-best-practices).
+For a complete list of architectural guidelines, see our [best practices for building and scaling feature flag systems](/guides/feature-flag-best-practices).
 
 ## 2. Install a local feature flag provider
 

website/docs/feature-flag-tutorials/python/implementing-feature-flags.mdx

@@ -58,7 +58,7 @@ As your application scales, performance and resiliency become more critical and
 
 Additionally, our SDKs cache your feature flag configuration to help reduce network round trips and dependency on external services. You can rely on the cache if your Feature Flag Control Service is not available, which will mitigate potential failure in your application.
 
-For a complete list of architectural guidelines, see our [best practices for building and scaling feature flag systems](https://docs.getunleash.io/topics/feature-flags/feature-flag-best-practices).
+For a complete list of architectural guidelines, see our [best practices for building and scaling feature flag systems](https://docs.getunleash.io//guides/feature-flag-best-practices).
 
 ## 2. Install a local feature flag provider
 

website/docs/feature-flag-tutorials/rails/implementing-feature-flags-rails.md

@@ -41,7 +41,7 @@ Most importantly, you must:
 -   Limit feature flag payloads for scalability, security, and efficiency
 -   Use graceful degradation where possible to improve the resiliency of your architecture
 
-For a complete list of architectural guidelines, including caching strategies, see our [best practices for building and scaling feature flag systems](/topics/feature-flags/feature-flag-best-practices).
+For a complete list of architectural guidelines, including caching strategies, see our [best practices for building and scaling feature flag systems](/guides/feature-flag-best-practices).
 
 ## 2. Install a local feature flag provider
 

website/docs/feature-flag-tutorials/react/implementing-feature-flags.mdx

@@ -51,13 +51,13 @@ a. Limit PII (personally identifiable information) leakage from the end-user dev
 
 b. Avoid leakage of configuration information from the central feature flag control service to end-user devices.
 
-Solving both means you need to avoid evaluating feature flags on the user's machine due to security risks like exposing API keys and flag data. Instead, send application context (e.g. username, location, etc) to your feature flag evaluation service to evaluate the results. These results (and only these results) should be stored in the client-side application memory. By keeping the evaluated results for a specific context in memory, you avoid network roundtrips every time your application needs to check the status of a feature flag. This method prevents unauthorized access and data breaches by [keeping configurations and PII secure](/topics/feature-flags/feature-flag-best-practices#6-protect-pii-by-evaluating-flags-server-side).
+Solving both means you need to avoid evaluating feature flags on the user's machine due to security risks like exposing API keys and flag data. Instead, send application context (e.g. username, location, etc) to your feature flag evaluation service to evaluate the results. These results (and only these results) should be stored in the client-side application memory. By keeping the evaluated results for a specific context in memory, you avoid network roundtrips every time your application needs to check the status of a feature flag. This method prevents unauthorized access and data breaches by [keeping configurations and PII secure](/guides/feature-flag-best-practices#6-protect-pii-by-evaluating-flags-server-side).
 
 ![Keep configurations and PII secure image](/img/react-tutorial-pii-diagram.png)
 
 Unleash, the open-source feature flag system used in this tutorial, evaluates feature flags in this way, so by following the rest of these steps, you will be protecting your user’s data and your company’s reputation.
 
-For a complete list of architectural guidelines, see our [best practices for building and scaling feature flag systems](/topics/feature-flags/feature-flag-best-practices).
+For a complete list of architectural guidelines, see our [best practices for building and scaling feature flag systems](/guides/feature-flag-best-practices).
 
 ## 2. Install a local feature flag provider
 

website/docs/feature-flag-tutorials/ruby/implementing-feature-flags-ruby.mdx

@@ -46,7 +46,7 @@ Most importantly, you must:
 -   Limit feature flag payloads for scalability, security, and efficiency
 -   Use graceful degradation where possible to improve the resiliency of your architecture.
 
-For a complete list of architectural guidelines, including caching strategies, see our [best practices for building and scaling feature flag systems](https://docs.getunleash.io/topics/feature-flags/feature-flag-best-practices).
+For a complete list of architectural guidelines, including caching strategies, see our [best practices for building and scaling feature flag systems](/guides/feature-flag-best-practices).
 
 ## 2. Install a local feature flag provider
 

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](/get-started/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](/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).
 

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](/get-started/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](/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.
 
@@ -140,7 +140,7 @@ After you have implemented a gradual rollout strategy, we recommend managing the
 -   Reviewing audit logs of each change to your flag configurations over time by project collaborators within your organization, which is exportable for reporting
 -   Reviewing and approving change requests to your flags and strategy configurations
 
-Read our documentation on how to effectively manage [feature flags at scale](/topics/feature-flags/best-practices-using-feature-flags-at-scale) while reducing security risks. Let’s walk through these recommended Unleash features in the subsequent sections.
+Read our documentation on how to effectively manage [feature flags at scale](/guides/best-practices-using-feature-flags-at-scale) while reducing security risks. Let’s walk through these recommended Unleash features in the subsequent sections.
 
 ### Reviewing application metrics
 

website/docs/feature-flag-tutorials/use-cases/security-compliance.md

@@ -100,7 +100,7 @@ One of the key responsibilities of the Admin role is assigning users as project
 
 For security best practices, we recommend following the principle of least privilege by assigning users the Viewer role or a custom root role with minimal permissions. From there, specific project-level permissions can be granted as needed.
 
-Unleash can handle all of the complexities that come with access controls and we make that process simple for you. Set up roles and permissions so you’re not only in complete control of how your feature flag system is administered, you’re adhering to compliance standards. For more recommendations on setting up permissions for users, read our guide on [using feature flags at scale](/topics/feature-flags/best-practices-using-feature-flags-at-scale).
+Unleash can handle all of the complexities that come with access controls and we make that process simple for you. Set up roles and permissions so you’re not only in complete control of how your feature flag system is administered, you’re adhering to compliance standards. For more recommendations on setting up permissions for users, read our guide on [using feature flags at scale](guides/best-practices-using-feature-flags-at-scale).
 
 Next, we’ll explore how to extend access controls in Unleash for network security.
 
@@ -156,7 +156,7 @@ Let’s say a project owner wants to update a rollout strategy so that a new fea
 
 You could also schedule changes by using the [date and time operators](/reference/activation-strategies#date-and-time-operators) in [strategy constraints](/reference/activation-strategies#constraints). However, when you have change requests configured in the project, we recommend using the schedule feature in change requests, as it is a faster and simpler approach.
 
-For more recommendations, read our section on [change management workflow](/topics/feature-flags/best-practices-using-feature-flags-at-scale#implement-flag-approval-workflows-early) from _Using Feature Flags at Scale_.
+For more recommendations, read our section on [change management workflow](/guides/best-practices-using-feature-flags-at-scale#implement-flag-approval-workflows-early) from _Using Feature Flags at Scale_.
 
 Now that we covered change requests as a practical tool for both feature management oversight and good security posture, let’s explore Unleash event logs as an audit logging system for your organization.
 
@@ -185,7 +185,7 @@ Next, we’ll explore data protection measures built into Unleash and how to enh
 
 ## Protect PII for data privacy
 
-Let’s explore Unleash's architectural layers that address data privacy. Our guide on [11 principles for building and scaling feature flag systems](/topics/feature-flags/feature-flag-best-practices), covers best practices for feature flag system implementations, such as protecting personally identifiable information (PII) by implementing the principle of least privilege.
+Let’s explore Unleash's architectural layers that address data privacy. Our guide on [11 principles for building and scaling feature flag systems](/guides/feature-flag-best-practices), covers best practices for feature flag system implementations, such as protecting personally identifiable information (PII) by implementing the principle of least privilege.
 
 Protecting data is critical within any software tool. It’s a security best practice that is ideally implemented across your tech stack where user data is handled. Unleash is architecturally designed to protect organizations and their end users by keeping data private and limiting the scope of data that is evaluated and stored. Think about the types of sensitive data that could be exposed if you use a feature flag system that isn’t designed to protect data. When feature flags are evaluated, here are examples of what could be at risk:
 

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](/get-started/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](/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).
 
@@ -252,7 +252,7 @@ To keep the trunk in a deployable state, keep the flag off in your production en
 To test your incomplete feature, enable the flag in the development environment in the Unleash Admin UI. In some cases, you may also find it valuable to enable the flag in a testing/QA environment. Unleash environment-specific flag configurations make it easy to manage these different states across your [environments](/reference/environments). You can quickly toggle flags on or off for specific environments, ensuring the trunk remains deployable in production while enabling active development and testing in other contexts. Use the default production environment toggle in Unleash to enable your flag when you’re ready to make your feature available.
 
 :::note
-Depending on the size and scope of a feature you’re developing, you may need more than one flag. Generally, we recommend creating as few flags as possible per feature, as making too many flags associated with one feature can become more complex to manage over time with trunk-based development. Our documentation on [best practices for feature flags at scale](/topics/feature-flags/best-practices-using-feature-flags-at-scale) provides more concrete details on large-scale feature flag management.
+Depending on the size and scope of a feature you’re developing, you may need more than one flag. Generally, we recommend creating as few flags as possible per feature, as making too many flags associated with one feature can become more complex to manage over time with trunk-based development. Our documentation on [best practices for feature flags at scale](/guides/best-practices-using-feature-flags-at-scale) provides more concrete details on large-scale feature flag management.
 :::
 
 ### Automate flag lifecycle management

website/docs/get-started/what-is-a-feature-flag.mdx

@@ -146,7 +146,7 @@ Contrary to the short-lived nature of most feature flags, kill switches are inhe
 
 Operational flags manage a system’s technical aspects that do not directly influence user-visible features but are crucial for the application’s underlying stability and performance. For example, during a library version upgrade, operational flags can toggle between the old and new implementations to ensure the update does not adversely affect the system. By enabling real-time switching between different operational states or configurations, these flags allow for thorough validation of changes in a live environment without disrupting the user experience.
 
-Operational flags should be short-lived, existing only long enough to confirm that a change, such as a library update, is stable and does not introduce regressions. Once the new state is validated, the flag should be promptly retired to avoid accumulating technical debt. Avoid using operational flags as a solution for long-term configuration management; see our [Best practices for building and scaling feature flags](./topics/feature-flags/feature-flag-best-practices) guide to learn more.
+Operational flags should be short-lived, existing only long enough to confirm that a change, such as a library update, is stable and does not introduce regressions. Once the new state is validated, the flag should be promptly retired to avoid accumulating technical debt. Avoid using operational flags as a solution for long-term configuration management; see our [Best practices for building and scaling feature flags](guides/feature-flag-best-practices) guide to learn more.
 
 
 ### Permission flags
@@ -211,6 +211,6 @@ Unleash is on a mission to make developers’ lives easier. Individual developer
 
 If you want to learn more about how to implement feature flags at scale, check out the following resources:
 - [Feature Flag Tutorials](/feature-flag-tutorials/use-cases/gradual-rollout)
-- [Best practices for using feature flags at scale](./topics/feature-flags/best-practices-using-feature-flags-at-scale)
-- [Best practices for building and scaling feature flags](./topics/feature-flags/feature-flag-best-practices)
+- [Best practices for using feature flags at scale](/guides/best-practices-using-feature-flags-at-scale)
+- [Best practices for building and scaling feature flags](/guides.feature-flags/feature-flag-best-practices)
 - [Try Unleash for Free](https://www.getunleash.io/pricing)

website/docs/guides-overview.mdx

@@ -16,8 +16,8 @@ If you're new to Unleash, start with our [Quickstart](/quickstart) guide to set
 These best practices guides show you how to design a secure, scalable feature flag system, operate it at enterprise scale, and migrate safely from a homegrown setup to Unleash. 
 
 Learn more:
-- [Building and scaling feature flag systems](/topics/feature-flags/feature-flag-best-practices)
-- [Using feature flags at scale](/topics/feature-flags/best-practices-using-feature-flags-at-scale)
+- [Building and scaling feature flag systems](/guides/feature-flag-best-practices)
+- [Using feature flags at scale](/guides/best-practices-using-feature-flags-at-scale)
 - [Migrating from homegrown feature management solutions](/topics/feature-flag-migration/feature-flag-migration-best-practices)
 
 ---

website/docs/guides/best-practices-using-feature-flags-at-scale.mdx

@@ -160,7 +160,7 @@ A good rule of thumb is that if the data is static (you don't expect it to chang
 
 ### Reusing feature flag names
 
-Feature flag names need to be [globally unique](https://docs.getunleash.io/topics/feature-flags/unique-names). In an ideal world, all flag references would be removed from the codebase as soon as a flag is archived—but in reality, that rarely happens. Using unique names helps protect new features from accidentally linking to old, unused flags that could unintentionally re-enable outdated behavior.
+Feature flag names need to be [globally unique](/guides/feature-flag-best-practices#4-ensure-unique-flag-names). In an ideal world, all flag references would be removed from the codebase as soon as a flag is archived—but in reality, that rarely happens. Using unique names helps protect new features from accidentally linking to old, unused flags that could unintentionally re-enable outdated behavior.
 
 To avoid this risk, enforce a [naming pattern](/reference/feature-toggles#set-a-naming-pattern) at flag creation.
 

website/docs/guides/feature-flag-best-practices.mdx

@@ -2,7 +2,7 @@
 title: "11 principles for building and scaling feature flag systems"
 description: Build a scalable, secure feature flag system with 11 key principles. Improve DevOps metrics, ensure reliability, and enhance developer experience."
 toc_max_heading_level: 2
-pagination_next: topics/feature-flags/best-practices-using-feature-flags-at-scale
+pagination_next: guides/best-practices-using-feature-flags-at-scale
 ---
 
 import VideoContent from '@site/src/components/VideoContent.jsx';
@@ -54,7 +54,7 @@ Let's break down these components.
 
 The most common use case for feature flags is to manage the [rollout](https://www.getunleash.io/feature-flag-use-cases-progressive-or-gradual-rollouts) of new functionality. Once a rollout is complete, you should remove the feature flag from your code and archive it. Remove any old code paths that the new functionality replaces.
 
-Avoid using feature flags for static application configuration. Application configuration should be consistent, long-lived, and loaded during application startup. In contrast, [feature flags should be short-lived, dynamic, and updated at runtime](./best-practices-using-feature-flags-at-scale). They prioritize availability over consistency and can be modified frequently.
+Avoid using feature flags for static application configuration. Application configuration should be consistent, long-lived, and loaded during application startup. In contrast, [feature flags should be short-lived, dynamic, and updated at runtime](/best-practices-using-feature-flags-at-scale). They prioritize availability over consistency and can be modified frequently.
 
 <table>
   <thead>
@@ -93,7 +93,7 @@ Avoid using feature flags for static application configuration. Application conf
 </table>
 
 ### Strategies for large organizations implementing feature flags
-To succeed with feature flags in a large organization, [follow these strategies](https://docs.getunleash.io/topics/feature-flags/best-practices-using-feature-flags-at-scale):
+To succeed with feature flags in a large organization, [follow these strategies](/guides/best-practices-using-feature-flags-at-scale):
 
 - **Set flag expiration dates**: Assign expiration dates to feature flags to track which flags are no longer needed. A good feature flag management tool will alert you to expired flags, making it easier to maintain your codebase.
 - **Treat feature flags like technical debt**: Incorporate tasks to remove outdated feature flags into your sprint or project planning, just as you would with [technical debt](../../reference/technical-debt). Feature flags add complexity to your code by introducing multiple code paths that need context and maintenance. If you don't clean up feature flags in a timely manner, you risk losing the context as time passes or personnel changes, making them harder to manage or remove.
@@ -118,7 +118,7 @@ You can implement the following strategies to achieve a resilient architecture:
 
 ## 4. Ensure unique flag names
 
-Ensure that all flags within the same _Feature Flag Control Service_ have unique names across your entire system. [Unique naming](https://docs.getunleash.io/topics/feature-flags/best-practices-using-feature-flags-at-scale#13-never-reuse-feature-flag-names) prevents the reuse of old flag names, reducing the risk of accidentally re-enabling outdated features with the same name.
+Ensure that all flags within the same _Feature Flag Control Service_ have unique names across your entire system. [Unique naming](/guides/best-practices-using-feature-flags-at-scale#13-never-reuse-feature-flag-names) prevents the reuse of old flag names, reducing the risk of accidentally re-enabling outdated features with the same name.
 
 ![Creating a feature flag with a unique name referencing the project and related jira ticket.](/img/feature-flag-unique-name.png)
 
@@ -223,7 +223,7 @@ Keeping the feature flag payload small results in:
 - **Improved system reliability**: Delivering smaller, more manageable payloads minimizes the risk of network timeouts and failures.
 - **Ease of monitoring and debugging**: Smaller payloads are easier to monitor and debug, making issue resolution faster.
 
-For more insights into reducing payload size, visit our [Best practices for using feature flags at scale](/topics/feature-flags/best-practices-using-feature-flags-at-scale#using-large-targeting-lists) guide.
+For more insights into reducing payload size, visit our [Best practices for using feature flags at scale](/guides/best-practices-using-feature-flags-at-scale#using-large-targeting-lists) guide.
 
 ## 10. Prioritize consistent user experience
 

website/docs/quickstart.mdx

@@ -128,5 +128,5 @@ For examples that show how to connect to Unleash in other programming languages,
 You have successfully connected Unleash to your application. To continue exploring, see the following resources:
 
 - **Core concepts**: Learn about the [Unleash architecture](/get-started/unleash-overview), available [hosting options](/understanding-unleash/hosting-options), and other [reference documentation](/reference/projects).
-- **Developer guides**: Explore feature flag [best practices](/topics/feature-flags/feature-flag-best-practices) and [language-specific tutorials](/feature-flag-tutorials/react).
+- **Developer guides**: Explore feature flag [best practices](/guides/feature-flag-best-practices) and [language-specific tutorials](/feature-flag-tutorials/react).
 - **Join the community**: Have questions or feedback? Join the [Unleash community on Slack](https://slack.unleash.run) to connect with other developers and the Unleash team.

website/docs/reference/terraform.mdx

@@ -18,7 +18,7 @@ import SearchPriority from '@site/src/components/SearchPriority';
 
 The [Unleash Terraform provider](https://github.com/Unleash/terraform-provider-unleash) enables you to manage and configure Unleash programmatically, leveraging infrastructure as code (IaC) for automated and scalable configuration.
 
-This provider is designed to help you with the **initial setup and configuration** of an instance. The provider does not support managing feature flags through Terraform. Since most [feature flags are short-lived](/topics/feature-flags/feature-flag-best-practices#2-make-flags-short-lived), we recommend managing them through the Unleash Admin UI.
+This provider is designed to help you with the **initial setup and configuration** of an instance. The provider does not support managing feature flags through Terraform. Since most [feature flags are short-lived](/guides/feature-flag-best-practices#2-make-flags-short-lived), we recommend managing them through the Unleash Admin UI.
 
 For a detailed video tutorial, check out [Managing Unleash through Terraform](https://www.youtube.com/watch?v=B4OIBC1u1ns).
 For more examples of specific resources and data sources, visit the [Terraform registry](https://registry.terraform.io/providers/Unleash/unleash/latest/docs/data-sources/permission).

website/docs/understanding-unleash/data-collection.md

@@ -3,7 +3,7 @@ title: Data and privacy
 pagination_next: using-unleash/compliance/compliance-overview
 ---
 
-At Unleash, we prioritize the privacy and security of our customers' data. Our [architecture](/understanding-unleash/the-anatomy-of-unleash) ensures privacy by evaluating feature flags locally within the [client SDKs](/reference/sdks) or [Unleash Edge](/reference/unleash-edge), meaning no user data is shared with the Unleash instance.
+At Unleash, we prioritize the privacy and security of our customers' data. Our [architecture](/reference/core-concepts) ensures privacy by evaluating feature flags locally within the [client SDKs](/reference/sdks) or [Unleash Edge](/reference/unleash-edge), meaning no user data is shared with the Unleash instance.
 
 :::info
 

website/sidebars.ts

@@ -42,13 +42,13 @@ const sidebars: SidebarsConfig = {
             type: 'category',
             link: {
                 type: 'doc',
-                id: 'get-started/quickstart',
+                id: 'quickstart',
             },
             items: [
                 {
                     type: 'doc',
                     label: 'Quickstart',
-                    id: 'get-started/quickstart',
+                    id: 'quickstart',
                 },
                 {
                     type: 'doc',
@@ -199,23 +199,23 @@ const sidebars: SidebarsConfig = {
                     type: 'category',
                     link: {
                         type: 'doc',
-                        id: 'topics/feature-flags/feature-flag-best-practices',
+                        id: 'guides/feature-flag-best-practices',
                     },
                     items: [
                         {
                             type: 'doc',
                             label: 'Building and scaling feature flag systems',
-                            id: 'topics/feature-flags/feature-flag-best-practices',
+                            id: 'guides/feature-flag-best-practices',
                         },
                         {
                             type: 'doc',
                             label: 'Using feature flags at scale',
-                            id: 'topics/feature-flags/best-practices-using-feature-flags-at-scale',
+                            id: 'guides/best-practices-using-feature-flags-at-scale',
                         },
                         {
                             type: 'doc',
                             label: 'Migrating from homegrown feature management solutions',
-                            id: 'topics/feature-flag-migration/feature-flag-migration-best-practices',
+                            id: 'guides/feature-flag-migration-best-practices',
                         },
                     ],
                 },

website/src/components/Homepage/HomepageCards.tsx

@@ -11,7 +11,7 @@ const cardsData = [
         title: 'Quickstart',
         description: 'Get up and running with Unleash in less than 5 minutes.',
         icon: <QuickstartIcon />,
-        href: '/get-started/quickstart',
+        href: '/quickstart',
     },
     {
         title: 'Tutorials and Guides',

website/vercel.json

@@ -23,7 +23,7 @@
           "value": "www.featureflagbook.com"
         }
       ],
-      "destination": "https://docs.getunleash.io/topics/feature-flags/feature-flag-best-practices",
+      "destination": "https://docs.getunleash.io/guides/feature-flag-best-practices",
       "permanent": false
     },
     {
@@ -523,22 +523,22 @@
     },
     {
       "source": "/user_guide/quickstart",
-      "destination": "/get-started/quickstart",
+      "destination": "/quickstart",
       "permanent": true
     },
     {
       "source": "/docs/getting_started",
-      "destination": "/get-started/quickstart",
+      "destination": "/quickstart",
       "permanent": true
     },
     {
       "source": "/tutorials/quickstart",
-      "destination": "/get-started/quickstart",
+      "destination": "/quickstart",
       "permanent": true
     },
     {
       "source": "/tutorials/getting-started",
-      "destination": "/get-started/quickstart",
+      "destination": "/quickstart",
       "permanent": true
     },
     {
@@ -943,7 +943,7 @@
     },
     {
       "source": "/topics",
-      "destination": "/topics/what-is-a-feature-flag",
+      "destination": "/get-started/what-is-a-feature-flag",
       "permanent": true
     },
     {
@@ -1085,11 +1085,6 @@
       "source": "/deploy/environment-import-export",
       "destination": "/how-to/how-to-environment-import-export",
       "permanent": true
-    },
-        {
-      "source": "/quickstart",
-      "destination": "/get-started/quickstart",
-      "permanent": true
     },
     {
       "source": "/what-is-a-feature-flag",