Ld migration seo fix (#542)

* from-ld -> from-launchdarkly

* png compress

Author: kp-cat

website/docs/advanced/migration-from-ld-translation.mdx renamed to website/docs/advanced/migration-from-launchdarkly-translation.mdx

@@ -1,5 +1,5 @@
 ---
-id: migration-from-ld-translation
+id: migration-from-launchdarkly-translation
 title: Details of LaunchDarkly to ConfigCat Translation
 description: Details of the LaunchDarkly to ConfigCat translation performed by the "Import from LaunchDarkly" tool.
 ---
@@ -8,7 +8,7 @@ import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import CodeBlock from '@theme/CodeBlock';
 
-This document discusses the details of how [ConfigCat's "Import from LaunchDarkly" tool](../migration-from-ld#migrate-launchdarkly-feature-flags-and-segments-to-configcat) translates LaunchDarkly projects to ConfigCat products (i.e., how, in practice, the import tool converts the project
+This document discusses the details of how [ConfigCat's "Import from LaunchDarkly" tool](../migration-from-launchdarkly#migrate-launchdarkly-feature-flags-and-segments-to-configcat) translates LaunchDarkly projects to ConfigCat products (i.e., how, in practice, the import tool converts the project
 data fetched fromLaunchDarkly's REST API to ConfigCat's Export/Import JSON format).
 
 You need this information if you want to understand
@@ -26,7 +26,7 @@ The table below shows how LaunchDarkly entities are mapped to ConfigCat entities
 | environment         | [environment](../../main-concepts#environment) | |
 | segment             | [segment](../../targeting/targeting-rule/segment-condition#what-is-a-segment-condition-what-is-a-segment) | LaunchDarkly segments are specific to an environment, but ConfigCat segments are specific to a product, so mapped segment names are prefixed with the environment name to avoid ambiguity. |
 | feature flag        | [feature flag / setting](../../targeting/targeting-overview#feature-flag--setting) | LaunchDarkly feature flags are directly contained by a project, but ConfigCat feature flags are organized into [configs](../../main-concepts#config), so a config named "Main Config" is created to contain them. |
-| targeting toggle    | -                              | No direct translation is possible. More on this [here](../migration-from-ld#targeting-toggle-translation-mode). |
+| targeting toggle    | -                              | No direct translation is possible. More on this [here](../migration-from-launchdarkly#targeting-toggle-translation-mode). |
 | prerequisites       | -                              | Each prerequisite is translated to a [Targeting Rule](../../targeting/targeting-overview#targeting-rule) containing a [Flag Condition](../../targeting/targeting-rule/flag-condition). |
 | individual targets  | -                              | Each target group is translated to a [Targeting Rule](../../targeting/targeting-overview#targeting-rule) containing an IS ONE OF [User Condition](../../targeting/targeting-rule/user-condition). |
 | custom rule         | [Targeting Rule](../../targeting/targeting-overview#targeting-rule) | Multiple clauses (i.e. [AND conditions](../../targeting/targeting-rule/targeting-rule-overview/#and-and-or-relationships) in ConfigCat's terminology) are not supported for segments, only for feature flags at the moment. |

website/docs/advanced/migration-from-ld.mdx renamed to website/docs/advanced/migration-from-launchdarkly.mdx

@@ -1,5 +1,5 @@
 ---
-id: migration-from-ld
+id: migration-from-launchdarkly
 title: Migration from LaunchDarkly
 description: A guide to migration from LaunchDarkly to ConfigCat.
 ---
@@ -60,11 +60,11 @@ behavior as closely as possible.
 To launch the import tool, open the dropdown menu in the top left corner of the [ConfigCat Dashboard](https://app.configcat.com/organization),
 navigate to the Organization Overview page, then click the card labeled "Import from LaunchDarkly".
 
-<img alt="Launching the import tool" src="/docs/assets/migration-from-ld/launch-import-tool_192dpi.png" width="1366" height="768" decoding="async" loading="lazy" />
+<img alt="Launching the import tool" src="/docs/assets/migration-from-launchdarkly/launch-import-tool_192dpi.png" width="1366" height="768" decoding="async" loading="lazy" />
 
 This will take you to a page with a wizard-like UI:
 
-<img alt="The import tool" src="/docs/assets/migration-from-ld/import-tool_192dpi.png" width="1366" height="768" decoding="async" loading="lazy" />
+<img alt="The import tool" src="/docs/assets/migration-from-launchdarkly/import-tool_192dpi.png" width="1366" height="768" decoding="async" loading="lazy" />
 
 Follow the instructions and go through the steps to perform the import.
 
@@ -134,7 +134,7 @@ operation by importing the selected LaunchDarkly projects one by one. Importing
 #### Translation phase
 
 First, the import tool translates the LaunchDarkly project to a ConfigCat product. For more details on how this is done,
-please refer to [this document](../migration-from-ld-translation).
+please refer to [this document](../migration-from-launchdarkly-translation).
 
 It's important to note that the import tool performs translation on a best effort basis. It aims to do translation in
 such a way that you get a feature flag evaluation behavior as close to the original as possible. However, since there
@@ -144,7 +144,7 @@ Such problematic cases are called *translation issues*. The import tool detects
 translation, and includes them in the report generated at the end of the import operation so you can review them, and
 make the necessary adjustments where necessary.
 
-You can find the list of possible translation issues [here](../migration-from-ld-translation#translation-issues).
+You can find the list of possible translation issues [here](../migration-from-launchdarkly-translation#translation-issues).
 
 #### Import phase
 
@@ -285,7 +285,7 @@ Let's see now step by step how to convert this code to ConfigCat:
    To be able to convert a context data structure to a User Object one, you will need to do the following:
    * Read [the section on User Objects](../../sdk-reference/node#user-object) in the reference of the SDK for your
      platform.
-   * Read [this section](../migration-from-ld-translation#mapping-between-launchdarkly-contexts-and-configcat-user-objects)
+   * Read [this section](../migration-from-launchdarkly-translation#mapping-between-launchdarkly-contexts-and-configcat-user-objects)
      to learn how context paths are mapped to User Object attribute names.
 
    For an example of such conversion, see the adjusted code at the end of this section.
@@ -308,7 +308,7 @@ Let's see now step by step how to convert this code to ConfigCat:
    * The order of parameters is different. In ConfigCat, the User Object comes last.
    * The ConfigCat feature flag key may be different from the LaunchDarkly one. E.g. if the key starts with a non-letter
      character, or contains a dot, it will be changed by the import tool because such keys are not valid in ConfigCat.
-     To see which keys have been changed, look for <a href="/docs/advanced/migration-from-ld-translation#translation-issue-T002">T002</a>
+     To see which keys have been changed, look for <a href="/docs/advanced/migration-from-launchdarkly-translation#translation-issue-T002">T002</a>
      translation issues in the report.
    * ConfigCat SDKs don't support [automatic camel casing](https://launchdarkly.com/docs/sdk/client-side/react/react-web#flag-keys-in-the-react-web-sdk)
      of feature flag keys.
@@ -387,7 +387,7 @@ Otherwise, to switch to ConfigCat, you need to do the following:
 1. Convert [LaunchDarkly-specific evaluation context objects](https://github.com/launchdarkly/openfeature-node-server?tab=readme-ov-file#openfeature-specific-considerations)
    to have a data structure compatible with ConfigCat.
 
-   This is done in a very similar way to what's described in the previous section. Read [this section](../migration-from-ld-translation#mapping-between-launchdarkly-contexts-and-configcat-user-objects)
+   This is done in a very similar way to what's described in the previous section. Read [this section](../migration-from-launchdarkly-translation#mapping-between-launchdarkly-contexts-and-configcat-user-objects)
    to learn how context paths are mapped to User Object attribute names.
 
    For example, something like
@@ -486,7 +486,7 @@ LaunchDarkly organization.
 To set up permission groups for a product, open the [ConfigCat Dashboard](https://app.configcat.com/organization),
 select the product on the sidebar, and choose "Permission Groups" in the top menu.
 
-<img alt="Launching the import tool" src="/docs/assets/migration-from-ld/permission-groups_192dpi.png" width="1366" height="768" decoding="async" loading="lazy" />
+<img alt="Launching the import tool" src="/docs/assets/migration-from-launchdarkly/permission-groups_192dpi.png" width="1366" height="768" decoding="async" loading="lazy" />
 
 ### Invite users to ConfigCat and assign them to permission groups
 
@@ -507,4 +507,4 @@ one of the products (it doesn't matter which one), then, after they've signed up
 organization, and assign them to the other products too, using the "Change roles" feature of the "Members & Roles"
 table.
 
-<img alt="Launching the import tool" src="/docs/assets/migration-from-ld/member-and-roles_192dpi.png" width="1366" height="768" decoding="async" loading="lazy" />
+<img alt="Launching the import tool" src="/docs/assets/migration-from-launchdarkly/member-and-roles_192dpi.png" width="1366" height="768" decoding="async" loading="lazy" />

website/docs/news.mdx

@@ -27,14 +27,14 @@ You can find the import tool on the [Organization Overview](https://app.configca
 ConfigCat Dashboard:
 
 <p>
-  <img alt="Launching the import tool" src="/docs/assets/migration-from-ld/launch-import-tool_192dpi.png" width="1366" height="768" decoding="async" loading="lazy" />
+  <img alt="Launching the import tool" src="/docs/assets/migration-from-launchdarkly/launch-import-tool_192dpi.png" width="1366" height="768" decoding="async" loading="lazy" />
 </p>
 
 :::info
 You'll need to be an Organization Admin to access it.
 :::
 
-If you decide to make the full switch, we've prepared a [migration guide](../advanced/migration-from-ld) to walk you
+If you decide to make the full switch, we've prepared a [migration guide](../advanced/migration-from-launchdarkly) to walk you
 through the whole process.
 
 So why not make the jump? You'll land on your paws anyway. :cat:

website/docusaurus.config.ts

@@ -54,6 +54,14 @@ const config: Config = {
             from: '/advanced/segments',
             to: '/targeting/targeting-rule/segment-condition',
           },
+          {
+            from: '/advanced/migration-from-ld',
+            to: '/advanced/migration-from-launchdarkly',
+          },
+          {
+            from: '/advanced/migration-from-ld-translation',
+            to: '/advanced/migration-from-launchdarkly-translation',
+          },
           {
             from: '/V2/targeting/targeting-overview',
             to: '/targeting/targeting-overview',

website/sidebars.ts

@@ -165,11 +165,11 @@ const sidebars: SidebarsConfig = {
         {
           label: 'Migration from LaunchDarkly',
           type: 'category',
-          link: { type: 'doc', id: 'advanced/migration-from-ld' },
+          link: { type: 'doc', id: 'advanced/migration-from-launchdarkly' },
           items: [
             {
               type: 'doc',
-              id: 'advanced/migration-from-ld-translation',
+              id: 'advanced/migration-from-launchdarkly-translation',
               label: 'Details of LaunchDarkly to ConfigCat Translation',
             },
           ],

website/src/pages/index.js

@@ -53,7 +53,7 @@ const features = [
         title: 'ConfigCat Proxy',
       },
       {
-        url: 'advanced/migration-from-ld',
+        url: 'advanced/migration-from-launchdarkly',
         title: 'Migration from LaunchDarkly',
       },
       // { url: 'advanced/config-v2-migration-guide', title: 'Config V2 Migration Guide' },