diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 89dd6f40cdb..376c6a5495e 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -61,34 +61,6 @@ jobs:
 
       - run: bundle exec rake check_ca
 
-  link_validation_check_scos_dev:
-    name: Links validation (check_scos_dev)
-    needs: jekyll_build
-    runs-on: ubuntu-latest
-
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Set up Ruby
-        uses: ruby/setup-ruby@v1
-        with:
-          ruby-version: 3.2.2
-          bundler-cache: true
-
-      - name: Cache HTMLProofer
-        id: cache-htmlproofer
-        uses: actions/cache@v2
-        with:
-          path: tmp/.htmlproofer
-          key: ${{ runner.os }}-check_scos_dev-htmlproofer
-
-      - uses: actions/download-artifact@v2
-
-      - name: Unpack artifacts
-        run: tar -xf build-result/result.tar.gz
-
-      - run: bundle exec rake check_scos_dev
-
   link_validation_check_scos_user:
     name: Links validation (check_scos_user)
     needs: jekyll_build
diff --git a/Rakefile b/Rakefile
index 002d8adca6f..e22911f419c 100644
--- a/Rakefile
+++ b/Rakefile
@@ -92,29 +92,6 @@ task :check_ca do
   HTMLProofer.check_directory("./_site", options).run
 end
 
-
-task :check_scos_dev do
-  options = commonOptions.dup
-  options[:ignore_files] = [
-    /docs\/ca\/.+/,
-    /docs\/fes\/.+/,
-    /docs\/acp\/.+/,
-    /docs\/dg\/.+/,
-    /docs\/scos\/user\/.+/,
-    /docs\/pbc\/.+/,
-    /docs\/scos\/\w+\/[\w-]+\/201811\.0\/.+/,
-    /docs\/scos\/\w+\/[\w-]+\/201903\.0\/.+/,
-    /docs\/scos\/\w+\/[\w-]+\/201907\.0\/.+/,
-    /docs\/scos\/\w+\/[\w-]+\/202001\.0\/.+/,
-    /docs\/scos\/\w+\/[\w-]+\/202005\.0\/.+/,
-    /docs\/scos\/\w+\/[\w-]+\/202009\.0\/.+/,
-    /docs\/scos\/\w+\/[\w-]+\/202108\.0\/.+/,
-    /docs\/scos\/\w+\/[\w-]+\/202204\.0\/.+/,
-    /docs\/scos\/\w+\/[\w-]+\/202400\.0\/.+/
-  ]
-  HTMLProofer.check_directory("./_site", options).run
-end
-
 task :check_scos_user do
   options = commonOptions.dup
   options[:ignore_files] = [
diff --git a/_config.yml b/_config.yml
index bb3c2cbd8d6..95d122e59b2 100644
--- a/_config.yml
+++ b/_config.yml
@@ -86,12 +86,6 @@ defaults:
       path: "docs/scos"
     values:
       product: "scos"
-  -
-    scope:
-      path: "docs/scos/dev"
-    values:
-      sidebar: "scos_dev_sidebar"
-      role: "dev"
   -
     scope:
       path: "docs/scos/user"
@@ -145,15 +139,6 @@ versions:
 
 # versioned categories - these must match corresponding directories
 versioned_categories:
-  scos:
-    dev:
-      - feature-integration-guides
-      - data-import
-      - data-export
-      - glue-api-guides
-      - the-docker-sdk
-      - system-requirements
-      - front-end-development
   dg:
     dev:
       - data-import
@@ -199,7 +184,6 @@ versioned_categories:
 sidebars:
   - ca_dev_sidebar
   - ca_devscu_sidebar
-  - scos_dev_sidebar
   - scos_user_sidebar
   - pbc_all_sidebar
   - dg_dev_sidebar
diff --git a/_data/sidebars/dg_dev_sidebar.yml b/_data/sidebars/dg_dev_sidebar.yml
index 003d2a291fd..a3c3006c5c3 100644
--- a/_data/sidebars/dg_dev_sidebar.yml
+++ b/_data/sidebars/dg_dev_sidebar.yml
@@ -4,7 +4,7 @@ entries:
 - product: Development
   nested:
   - title: Developer getting started guide
-    url: /docs/scos/dev/developer-getting-started-guide.html
+    url: /docs/dg/dev/development-getting-started-guide.html
   - title: Set up locally
     url: /docs/dg/dev/set-up-spryker-locally/set-up-spryker-locally.html
     nested:
@@ -1259,6 +1259,103 @@ entries:
     - title: Coding best practices
       url: /docs/dg/dev/best-practices/coding-best-practices.html
 
+  - title: Troubleshooting
+    url: /docs/dg/dev/troubleshooting/troubleshooting.html
+    nested:
+    - title: Troubleshooting general technical issues
+      url: /docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-general-technical-issues.html
+      nested:
+      - title: Troubleshooting RabbitMQ
+        url: /docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/troubleshooting-rabbitmq.html
+        nested:
+        - title: Messages are moved to error queues
+          url: /docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-moved-to-error-queues.html
+        - title: Messages are stuck in the Unacked state
+          url: /docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-stuck-in-the-unacked-state.html
+        - title: Messages are stuck without error notifications
+          url: /docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-stuck-without-error-notifications.html
+      - title: RabbitMQ - Zed.CRITICAL - PhpAmqpLib\Exception\AMQPChannelClosedException
+        url: /docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.html
+      - title: Fail whale on the frontend
+        url: /docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-frontend.html
+      - title: A command fails with a `Killed` message
+        url: /docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/a-command-fails-with-a-killed-message.html
+      - title: 'API request fails with the exception: Session has not been set'
+        url: /docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/api-request-fails-with-the-exception-session-has-not-been-set.html
+      - title: Composer version 2 compatibility issues
+        url: /docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/composer-version-2-compatibility-issues.html
+      - title: Unable to resolve hosts for Mail, Jenkins, and RabbitMQ
+        url: /docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq.html
+      - title: PHPStan memory issues
+        url: /docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/phpstan-memory-issues.html
+      - title: ProcessTimedOutException after queue-task-start
+        url: /docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/processtimedoutexception-after-queue-task-start.html
+      - title: RuntimeException - Failed to execute regex - PREG_JIT_STACKLIMIT_ERROR
+        url: /docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error.html
+      - title: ERROR - remove spryker_logs - volume is in use
+        url: /docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/error-remove-spryker-logs-volume-is-in-use.html
+      - title: Class Silex/ControllerProviderInterface not found
+        url: /docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/class-silex-controllerproviderinterface-not-found.html
+      - title: Error response from daemon - OCI runtime create failed - .... \\\"no such file or directory\\\"\""- unknown
+        url: /docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown.html
+
+      - title: Router generates absolute URL with localhost
+        url: /docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/router-generates-absolute-url-with-localhost.html
+      - title: No data on the Storefront
+        url: /docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/no-data-on-the-storefront.html
+      - title: The spy_oms_transition_log table takes up too much space
+        url: /docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/the-spy-oms-transition-log-table-takes-up-too-much-space.html
+    - title: Troubleshooting performance issues
+      url: /docs/dg/dev/troubleshooting/troubleshooting-performance-issues/troubleshooting-performance-issues.html
+      nested:
+      - title: External calls take a lot of time
+        url: /docs/dg/dev/troubleshooting/troubleshooting-performance-issues/external-calls-take-a-lot-of-time.html
+      - title: External calls—several calls to Zed
+        url: /docs/dg/dev/troubleshooting/troubleshooting-performance-issues/external-calls-several-calls-to-zed.html
+      - title: N+1 problem
+        url: /docs/dg/dev/troubleshooting/troubleshooting-performance-issues/n+1-problem.html
+      - title: Not optimized Composer on the production environment
+        url: /docs/dg/dev/troubleshooting/troubleshooting-performance-issues/not-optimised-composer-on-the-production-environment.html
+      - title: Redis session lock
+        url: /docs/dg/dev/troubleshooting/troubleshooting-performance-issues/redis-session-lock.html
+      - title: Slow Publish and Synchronization
+        url: /docs/dg/dev/troubleshooting/troubleshooting-performance-issues/slow-publish-and-synchronization.html
+      - title: Technology restrictions
+        url: /docs/dg/dev/troubleshooting/troubleshooting-performance-issues/technology-restrictions.html
+    - title: Troubleshooting Spryker in Docker issues
+      url: /docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-docker-issues.html
+      nested:
+      - title: Troubleshooting debugging in Docker
+        nested:
+        - title: PHP `xdebug` extension is not active when accessing the website via
+            a browser or curl
+          url: /docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-when-accessing-the-website-via-a-browser-or-curl.html
+        - title: nc command tells that the port is opened
+          url: /docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-tells-that-the-port-is-opened.html
+        - title: Xdebug does not work
+          url: /docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/xdebug-does-not-work.html
+        - title: nc command does not give any output
+          url: /docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-does-not-give-any-output.html
+        - title: PHP `xdebug` extension is not active in CLI
+          url: /docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-in-cli.html
+      - title: Troubleshooting running applications in Docker
+        nested:
+        - title: An application is not reachable via http
+          url: /docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/an-application-is-not-reachable-via-http.html
+        - title: Mutagen synchronization issue
+          url: /docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-synchronization-issue.html
+        - title: 413 Request Entity Too Large
+          url: /docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/413-request-entity-too-large.html
+        - title: MacOS and Windows - file synchronization issues in Development mode
+          url: /docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/macos-and-windows-file-synchronization-issues-in-development-mode.html
+        - title: Nginx welcome page
+          url: /docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/nginx-welcome-page.html
+        - title: Mutagen error
+          url: /docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-error.html
+        - title: Port is already occupied on host
+          url: /docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/port-is-already-occupied-on-host.html
+
+
 
   - title: Glue API
     url: /docs/dg/dev/glue-api/glue-api.html
@@ -1376,7 +1473,6 @@ entries:
           url: /docs/dg/dev/glue-api/glue-api-tutorials/validate-rest-request-format.html
 
 
-
   - title: Zed API
     url: /docs/dg/dev/zed-api/zed-api.html
     nested:
@@ -1431,3 +1527,10 @@ entries:
         url: /docs/dg/dev/miscellaneous-guides/using-database-transaction.html
       - title: "Transfer big databases between environments"
         url: /docs/dg/dev/miscellaneous-guides/transfer-big-databases-between-environments.html
+
+  - title: Code contribution guide
+    url: /docs/dg/dev/code-contribution-guide.html
+  - title: Code generator
+    url: /docs/dg/dev/code-generator.html
+  - title: Example modules
+    url: /docs/dg/dev/example-modules.html
diff --git a/_data/sidebars/scos_dev_sidebar.yml b/_data/sidebars/scos_dev_sidebar.yml
deleted file mode 100644
index 48ee03dbb6b..00000000000
--- a/_data/sidebars/scos_dev_sidebar.yml
+++ /dev/null
@@ -1,1073 +0,0 @@
-title: SCOS Developer Guides
-entries:
-- product: SCOS
-  nested:
-  - title: Developer getting started guide
-    url: /docs/scos/dev/developer-getting-started-guide.html
-  - title: Feature walkthroughs
-    url: /docs/scos/dev/feature-walkthroughs/feature-walkthroughs.html
-    include_versions:
-    - "202204.0"
-    nested:
-    - title: Agent Assist
-      url: /docs/scos/dev/feature-walkthroughs/agent-assist-feature-walkthrough.html
-      include_versions:
-      - "202204.0"
-    - title: Alternative Products
-      url: /docs/scos/dev/feature-walkthroughs/alternative-products-feature-walkthrough.html
-      include_versions:
-      - "202204.0"
-    - title: Customer Access
-      url: /docs/scos/dev/feature-walkthroughs/customer-access-feature-walkthrough.html
-      include_versions:
-      - "202204.0"
-    - title: Customer Account Management
-      url: /docs/scos/dev/feature-walkthroughs/customer-account-management-feature-walkthrough/customer-account-management-feature-walkthrough.html
-      include_versions:
-      - "202204.0"
-      nested:
-      - title: "Customer module overview: reference information"
-        url: /docs/scos/dev/feature-walkthroughs/customer-account-management-feature-walkthrough/customer-module-overview-reference-information.html
-
-
-    - title: Merchant
-      url: /docs/scos/dev/feature-walkthroughs/merchant-feature-walkthrough.html
-      include_versions:
-      - "202204.0"
-    - title: Merchant B2B Contracts
-      url: /docs/scos/dev/feature-walkthroughs/merchant-b2b-contracts-feature-walkthrough.html
-      include_versions:
-      - "202204.0"
-    - title: Merchant Product Restrictions
-      url: /docs/scos/dev/feature-walkthroughs/merchant-product-restrictions-feature-walkthrough/merchant-product-restrictions-feature-walkthrough.html
-      include_versions:
-      - "202204.0"
-      nested:
-      - title: Restricted products behavior
-        url: /docs/scos/dev/feature-walkthroughs/merchant-product-restrictions-feature-walkthrough/restricted-products-behavior.html
-        include_versions:
-        - "202204.0"
-
-
-    - title: Order Management
-      url: /docs/scos/dev/feature-walkthroughs/order-management-feature-walkthrough/order-management-feature-wakthrough.html
-      include_versions:
-      - "202204.0"
-      nested:
-      - title: "Sales module: reference information"
-        url: /docs/scos/dev/feature-walkthroughs/order-management-feature-walkthrough/sales-module-reference-information.html
-      - title: "Custom order reference: module relations"
-        url: /docs/scos/dev/feature-walkthroughs/order-management-feature-walkthrough/custom-order-reference-module-relations.html
-        include_versions:
-        - "202204.0"
-    - title: Product Relations
-      url: /docs/scos/dev/feature-walkthroughs/product-relations-feature-walkthrough/product-relations-feature-walkthrough.html
-      include_versions:
-      - "202204.0"
-      nested:
-      - title: "Product Relations: module relations"
-        url: /docs/scos/dev/feature-walkthroughs/product-relations-feature-walkthrough/product-relations-module-relations.html
-        include_versions:
-        - "202204.0"
-
-    - title: Reclamations
-      url: /docs/scos/dev/feature-walkthroughs/reclamations-feature-walkthrough.html
-      include_versions:
-      - "202204.0"
-
-    - title: Refunds
-      url: /docs/scos/dev/feature-walkthroughs/refunds-feature-walkthrough.html
-      include_versions:
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-    - title: Reorder
-      url: /docs/scos/dev/feature-walkthroughs/reorder-feature-walkthrough.html
-      include_versions:
-      - "202108.0"
-      - "202204.0"
-
-    - title: Search
-      url: /docs/scos/dev/feature-walkthroughs/search-feature-walkthrough.html
-      include_versions:
-      - "202108.0"
-      - "202204.0"
-
-
-    - title: Spryker Core Back Office
-      url: /docs/scos/dev/feature-walkthroughs/spryker-core-back-office-feature-walkthrough/spryker-core-back-office-feature-walkthrough.html
-      include_versions:
-      - "202204.0"
-      - "202108.0"
-    - title: Spryker Core
-      url: /docs/scos/dev/feature-walkthroughs/spryker-core-feature-walkthrough/spryker-core-feature-walkthrough.html
-      include_versions:
-      - "201811.0"
-      - "201903.0"
-      - "201907.0"
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-      nested:
-      - title: How translations are managed
-        url: /docs/scos/dev/feature-walkthroughs/spryker-core-feature-walkthrough/how-translations-are-managed.html
-        include_versions:
-        - "201811.0"
-        - "201903.0"
-        - "201907.0"
-        - "202001.0"
-        - "202005.0"
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-      - title: URL redirects overview
-        url: /docs/scos/dev/feature-walkthroughs/spryker-core-feature-walkthrough/url-redirects-overview.html
-        include_versions:
-        - "201811.0"
-        - "201903.0"
-        - "201907.0"
-        - "202001.0"
-        - "202005.0"
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-
-  - title: Feature integration guides
-    url: /docs/scos/dev/feature-integration-guides/feature-integration-guides.html
-    include_versions:
-    - "202009.0"
-    - "201907.0"
-    - "202108.0"
-    - "202204.0"
-    nested:
-    - title: Glue API
-      nested:
-      - title: Glue API installation and configuration
-        url: /docs/scos/dev/feature-integration-guides/glue-api/glue-api-installation-and-configuration.html
-        include_versions:
-        - "202009.0"
-        - "201907.0"
-        - "202108.0"
-        - "202204.0"
-      - title: Glue API - Agent Assist
-        url: /docs/scos/dev/feature-integration-guides/glue-api/glue-api-agent-assist-feature-integration.html
-        include_versions:
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-      - title: Glue API - Cart
-        url: /docs/scos/dev/feature-integration-guides/glue-api/glue-api-cart-feature-integration.html
-        include_versions:
-        - "201907.0"
-        - "202001.0"
-        - "202005.0"
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-      - title: Glue API - Company Account
-        url: /docs/scos/dev/feature-integration-guides/glue-api/glue-api-company-account-feature-integration.html
-        include_versions:
-        - "201907.0"
-        - "202001.0"
-        - "202005.0"
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-
-      - title: Glue API - Development Tools
-        url: /docs/scos/dev/feature-integration-guides/glue-api/glue-api-development-tools-feature-integration.html
-        include_versions:
-        - "201811.0"
-        - "201903.0"
-        - "201907.0"
-        - "202001.0"
-        - "202005.0"
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-        include_versions:
-        - "202108.0"
-        - "202204.0"
-      - title: Glue API - Glue application
-        url: /docs/scos/dev/feature-integration-guides/glue-api/glue-api-glue-application-feature-integration.html
-        include_versions:
-        - "201811.0"
-        - "201903.0"
-        - "201907.0"
-        - "202001.0"
-        - "202005.0"
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-      - title: Glue API - Order Management
-        url: /docs/scos/dev/feature-integration-guides/glue-api/glue-api-order-management-feature-integration.html
-        include_versions:
-        - "202005.0"
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-      - title: Glue API - Payments
-        url: /docs/scos/dev/feature-integration-guides/glue-api/glue-api-payments-feature-integration.html
-        include_versions:
-        - "201903.0"
-        - "201907.0"
-        - "202001.0"
-        - "202005.0"
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-      - title: Glue API - Product Relations
-        url: /docs/scos/dev/feature-integration-guides/glue-api/glue-api-product-relations-feature-integration.html
-        include_versions:
-        - "202001.0"
-        - "202005.0"
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-      - title: Glue API - REST Schema Validation
-        url: /docs/scos/dev/feature-integration-guides/glue-api/glue-api-rest-schema-validation-feature-integration.html
-        include_versions:
-        - "202108.0"
-        - "202204.0"
-      - title: Glue API - Spryker Core
-        url: /docs/scos/dev/feature-integration-guides/glue-api/glue-api-spryker-core-feature-integration.html
-        include_versions:
-        - "202001.0"
-        - "202005.0"
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-      - title: Glue API - Wishlist
-        url: /docs/scos/dev/feature-integration-guides/glue-api/glue-api-wishlist-feature-integration.html
-        include_versions:
-        - "201811.0"
-        - "201903.0"
-        - "201907.0"
-        - "202001.0"
-        - "202005.0"
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-      - title: Install the Data Exchange API
-        url: /docs/scos/dev/feature-integration-guides/glue-api/data-exchange-api/install-the-data-exchange-api.html
-        include_versions:
-        - "202307.0"
-        - "202311.0"
-      - title: Data Exchange API + Inventory Management feature integration
-        url: /docs/scos/dev/feature-integration-guides/glue-api/dynamic-data-api/install-the-data-exchange-api-inventory-management-feature.md
-        include_versions:
-        - "202307.0"
-        - "202311.0"
-    - title: Company Account
-      url: /docs/scos/dev/feature-integration-guides/company-account-feature-integration.html
-      include_versions:
-      - "201903.0"
-      - "201907.0"
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-    - title: Company Account + Order Management
-      url: /docs/scos/dev/feature-integration-guides/company-account-order-management-feature-integration.html
-      include_versions:
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-    - title: Customer Access
-      url: /docs/scos/dev/feature-integration-guides/customer-access-feature-integration.html
-      include_versions:
-      - "201903.0"
-      - "201907.0"
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-    - title: Customer Account Management
-      url: /docs/scos/dev/feature-integration-guides/customer-account-management-feature-integration.html
-      include_versions:
-      - "201907.0"
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-    - title: Customer Account Management + Agent Assist
-      url: /docs/scos/dev/feature-integration-guides/customer-account-management-agent-assist-feature-integration.html
-      include_versions:
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-    - title: Customer Account Management + Order Management
-      url: /docs/scos/dev/feature-integration-guides/customer-account-management-order-management-feature-integration.html
-      include_versions:
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-    - title: Discontinued Products + Product Labels
-      url: /docs/scos/dev/feature-integration-guides/discontinued-products-product-labels-feature-integration.html
-      include_versions:
-      - "202009.0"
-      - "202108.0"
-    - title: Mailing and Notifications
-      url: /docs/scos/dev/feature-integration-guides/mailing-and-notifications-feature-integration.html
-      include_versions:
-      - "202204.0"
-    - title: Merchant
-      url: /docs/scos/dev/feature-integration-guides/merchant-feature-integration.html
-      include_versions:
-      - "202108.0"
-      - "202204.0"
-    - title: Merchant B2B Contracts
-      url: /docs/scos/dev/feature-integration-guides/merchant-b2b-contracts-feature-integration.html
-      include_versions:
-      - "201903.0"
-      - "201907.0"
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-    - title: Merchant Product Restrictions
-      url: /docs/scos/dev/feature-integration-guides/merchant-product-restrictions-feature-integration.html
-      include_versions:
-      - "202108.0"
-      - "202204.0"
-    - title: Merchants and Merchant Relations
-      url: /docs/scos/dev/feature-integration-guides/merchants-and-merchant-relations-feature-integration.html
-      include_versions:
-      - "202108.0"
-      - "202204.0"
-    - title: Multiple Abstract Products as Promotional Products & Discounts
-      url: /docs/scos/dev/feature-integration-guides/multiple-abstract-products-as-promotional-products-and-discounts-feature-integration.html
-      include_versions:
-      - "202204.0"
-    - title: Multi-store Products
-      url: /docs/scos/dev/feature-integration-guides/multi-store-products-feature-integration.html
-      include_versions:
-      - "202204.0"
-    - title: Order Management
-      url: /docs/scos/dev/feature-integration-guides/order-management-feature-integration.html
-      include_versions:
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-    - title: Payments
-      url: /docs/scos/dev/feature-integration-guides/payments-feature-integration.html
-      include_versions:
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-    - title: Permissions
-      url: /docs/scos/dev/feature-integration-guides/permissions-feature-integration.html
-      include_versions:
-      - "202108.0"
-      - "202204.0"
-    - title: Product Relations
-      url: /docs/scos/dev/feature-integration-guides/product-relations-feature-integration.html
-      include_versions:
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-    - title: Queue Data Import
-      url: /docs/scos/dev/feature-integration-guides/queue-data-import-feature-integration.html
-      include_versions:
-      - "201903.0"
-      - "201907.0"
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-    - title: Reclamations
-      url: /docs/scos/dev/feature-integration-guides/reclamations-feature-integration.html
-      include_versions:
-      - "201903.0"
-      - "201907.0"
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-
-    - title: Search Widget for Concrete Products
-      url: /docs/scos/dev/feature-integration-guides/search-widget-for-concrete-products-feature-integration.html
-      include_versions:
-      - "201903.0"
-      - "201907.0"
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-
-
-    - title: Splittable Order Items
-      url: /docs/scos/dev/feature-integration-guides/splittable-order-items-feature-integration.html
-      include_versions:
-      - "201811.0"
-      - "201903.0"
-      - "201907.0"
-      - "202204.0"
-    - title: Spryker Core
-      url: /docs/scos/dev/feature-integration-guides/spryker-core-feature-integration.html
-      include_versions:
-      - "201903.0"
-      - "201907.0"
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-    - title: Spryker Core Back Office
-      url: /docs/scos/dev/feature-integration-guides/spryker-core-back-office-feature-integration.html
-      include_versions:
-      - "201903.0"
-      - "201907.0"
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-    - title: Uuid Generation Console
-      url: /docs/scos/dev/feature-integration-guides/uuid-generation-console-feature-integration.html
-      include_versions:
-      - "202204.0"
-    - title: Zed API
-      url: /docs/scos/dev/feature-integration-guides/zed-api-feature-integration.html
-      include_versions:
-      - "202204.0"
-
-  - title: Code generator
-    url: /docs/scos/dev/sdk/code-generator.html
-    include_versions:
-    - "201811.0"
-
-  - title: Technology partner guides
-    url: /docs/scos/dev/technology-partner-guides/technology-partner-guides.html
-    include_versions:
-    - "202204.0"
-    nested:
-    - title: Marketing and conversion
-      url: /docs/scos/dev/technology-partner-guides/marketing-and-conversion/marketing-and-conversion.html
-      nested:
-      - title: Analytics
-        nested:
-        - title: Installing and integrating Minubo
-          url: /docs/scos/dev/technology-partner-guides/marketing-and-conversion/analytics/installing-and-integrating-minubo.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-          - "202212.0"
-          - "202307.0"
-          - "202311.0"
-      - title: Customer communication
-        nested:
-        - title: Episerver guides
-          url: /docs/scos/dev/technology-partner-guides/marketing-and-conversion/customer-communication/episerver/episerver.html
-          include_versions:
-          - "202212.0"
-          - "202307.0"
-          - "202311.0"
-          nested:
-          - title: Integrating Episerver
-            url: /docs/scos/dev/technology-partner-guides/marketing-and-conversion/customer-communication/episerver/integrating-episerver.html
-          - title: Installing and configuring Episerver
-            url: /docs/scos/dev/technology-partner-guides/marketing-and-conversion/customer-communication/episerver/installing-and-configuring-episerver.html
-          - title: API
-            url: /docs/scos/dev/technology-partner-guides/marketing-and-conversion/customer-communication/episerver/episerver-api.html
-          - title: Order reference commands
-            url: /docs/scos/dev/technology-partner-guides/marketing-and-conversion/customer-communication/episerver/episerver-order-reference-commands.html
-        - title: Inxmail guides
-          include_versions:
-          - "202009.0"
-          - "202108.0"
-          - "202204.0"
-          nested:
-          - title: Installing and configuring Inxmail
-            url: /docs/scos/dev/technology-partner-guides/marketing-and-conversion/customer-communication/inxmail/installing-and-configuring-inxmail.html
-          - title: Integrating Inxmail
-            url: /docs/scos/dev/technology-partner-guides/marketing-and-conversion/customer-communication/inxmail/integrating-inxmail.html
-          - title: Inxmail API requests
-            url: /docs/scos/dev/technology-partner-guides/marketing-and-conversion/customer-communication/inxmail/inxmail-api-requests.html
-          - title: Inxmail order referenced commands
-            url: /docs/scos/dev/technology-partner-guides/marketing-and-conversion/customer-communication/inxmail/inxmail-order-referenced-commands.html
-      - title: Personalization and cross-selling
-        include_versions:
-        - "202108.0"
-        - "202204.0"
-        nested:
-        - title: Econda
-          url: /docs/scos/dev/technology-partner-guides/marketing-and-conversion/personalization-and-cross-selling/econda/econda.html
-          include_versions:
-          - "202212.0"
-          - "202307.0"
-          - "202311.0"
-          nested:
-          - title: Installing Econda
-            url: /docs/scos/dev/technology-partner-guides/marketing-and-conversion/personalization-and-cross-selling/econda/installing-econda.html
-          - title: Integrating Econda
-            url: /docs/scos/dev/technology-partner-guides/marketing-and-conversion/personalization-and-cross-selling/econda/integrating-econda.html
-          - title: Integrating Econda cross-selling
-            url: /docs/scos/dev/technology-partner-guides/marketing-and-conversion/personalization-and-cross-selling/econda/integrating-econda-cross-selling.html
-          - title: Adding the Econda tracking code
-            url: /docs/scos/dev/technology-partner-guides/marketing-and-conversion/personalization-and-cross-selling/econda/adding-the-econda-tracking-code.html
-          - title: Exporting Econda data
-            url: /docs/scos/dev/technology-partner-guides/marketing-and-conversion/personalization-and-cross-selling/econda/exporting-econda-data.html
-    - title: Operational tools, monitoring, legal, etc.
-      url: /docs/scos/dev/technology-partner-guides/operational-tools-monitoring-legal-etc/operational-tools-monitoring-legal-etc.html
-      nested:
-        - title: New Relic
-          include_versions:
-          - "202204.0"
-          nested:
-            - title: Installing and configuring New Relic
-              url: /docs/scos/dev/technology-partner-guides/operational-tools-monitoring-legal-etc/new-relic/installing-and-configuring-new-relic–with–vagrant.html
-            - title: Configuring logging
-              url: /docs/scos/dev/technology-partner-guides/operational-tools-monitoring-legal-etc/new-relic/configuring-new-relic-logging.html
-        - title: Loggly
-          url: /docs/scos/dev/technology-partner-guides/operational-tools-monitoring-legal-etc/loggly/loggly.html
-          nested:
-            - title: Configuring Loggly
-              url: /docs/scos/dev/technology-partner-guides/operational-tools-monitoring-legal-etc/loggly/configuring-loggly.html
-        - title: Installing and configuring Tideways
-          url: /docs/scos/dev/technology-partner-guides/operational-tools-monitoring-legal-etc/installing-and-configuring-tideways-with-vagrant.html
-          include_versions:
-          - "202204.0"
-    - title: Order Management Erpoms
-      include_versions:
-      - "202204.0"
-      nested:
-    - title: Payment partners
-      nested:
-        - title: Adyen
-          include_versions:
-          - "202204.0"
-          nested:
-            - title: Installing and configuring Adyen
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/adyen/installing-and-configuring-adyen.html
-            - title: Integrating Adyen
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/adyen/integrating-adyen.html
-            - title: Integrating payment methods
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/adyen/integrating-adyen-payment-methods.html
-            - title: Enabling filtering of payment methods
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/adyen/enabling-filtering-of-payment-methods-for-adyen.html
-        - title: Afterpay
-          include_versions:
-          - "202204.0"
-          nested:
-            - title: Installing and configuring Afterpay
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/afterpay/installing-and-configuring-afterpay.html
-            - title: Integrating Afterpay
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/afterpay/integrating-afterpay.html
-        - title: Amazon Pay
-          include_versions:
-          - "202204.0"
-          nested:
-            - title: Configuring Amazon Pay
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/amazon-pay/configuring-amazon-pay.html
-            - title: Obtaining an Amazon Order Reference and information about shipping addresses
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/amazon-pay/obtaining-an-amazon-order-reference-and-information-about-shipping-addresses.html
-            - title: Sandbox Simulations
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/amazon-pay/amazon-pay-sandbox-simulations.html
-            - title: State machine
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/amazon-pay/amazon-pay-state-machine.html
-            - title: Handling orders with Amazon Pay API
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/amazon-pay/handling-orders-with-amazon-pay-api.html
-
-        - title: Arvato
-          include_versions:
-          - "201811.0"
-          - "201903.0"
-          - "201907.0"
-          - "202001.0"
-          - "202005.0"
-          - "202009.0"
-          - "202108.0"
-          - "202204.0"
-          nested:
-            - title: Installing and configuring Arvato
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/arvato/installing-and-configuring-arvato.html
-              include_versions:
-              - "202001.0"
-              - "202005.0"
-              - "202009.0"
-              - "202108.0"
-              - "202204.0"
-            - title: Arvato - Risk Check
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/arvato/arvato-risk-check.html
-              include_versions:
-              - "202001.0"
-              - "202005.0"
-              - "202009.0"
-              - "202108.0"
-              - "202204.0"
-            - title: Arvato - Store Order
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/arvato/arvato-store-order.html
-            - title: v.2.0
-              include_versions:
-              - "201811.0"
-              - "201903.0"
-              - "201907.0"
-              nested:
-              - title: Arvato - Risk Check 2.0
-                url: /docs/scos/dev/technology-partner-guides/payment-partners/arvato/v.2.0/arvato-risk-check-2.0.html
-                include_versions:
-                - "201811.0"
-                - "201903.0"
-                - "201907.0"
-              - title: Installing and configuring Arvato 2.0
-                url: /docs/scos/dev/technology-partner-guides/payment-partners/arvato/v.2.0/installing-and-configuring-arvato-2.0.html
-                include_versions:
-                - "201811.0"
-                - "201903.0"
-                - "201907.0"
-        - title: Billpay
-          include_versions:
-          - "201811.0"
-          - "201903.0"
-          - "201907.0"
-          - "202001.0"
-          - "202005.0"
-          - "202009.0"
-          - "202108.0"
-          - "202204.0"
-          nested:
-            - title: Integrating Billpay
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/billpay/integrating-billpay.html
-            - title: Billpay - Switching invoice payments to a preauthorize mode
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/billpay/billpay-switching-invoice-payments-to-a-preauthorize-mode.html
-        - title: Braintree
-          include_versions:
-          - "201811.0"
-          - "201903.0"
-          - "201907.0"
-          - "202001.0"
-          - "202005.0"
-          - "202009.0"
-          - "202108.0"
-          - "202204.0"
-          nested:
-            - title: Installing and configuring Braintree
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/braintree/installing-and-configuring-braintree.html
-            - title: Integrating Braintree
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/braintree/integrating-braintree.html
-              include_versions:
-              - "202009.0"
-              - "202108.0"
-              - "202204.0"
-            - title: Performing requests
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/braintree/braintree-performing-requests.html
-            - title: Request workflow
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/braintree/braintree-request-workflow.html
-
-        - title: Computop
-          include_versions:
-          - "201811.0"
-          - "201903.0"
-          - "201907.0"
-          - "202001.0"
-          - "202005.0"
-          - "202009.0"
-          - "202108.0"
-          - "202204.0"
-          nested:
-          - title: Installing and configuring Computop
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/computop/installing-and-configuring-computop.html
-          - title: OMS plugins
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/computop/computop-oms-plugins.html
-          - title: API calls
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/computop/computop-api-calls.html
-          - title: Integrating payment methods for Computop
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/computop/integrating-payment-methods-for-computop/integrating-payment-methods-for-computop.html
-            include_versions:
-            - "202212.0"
-            nested:
-            - title: Integrating the Sofort payment method
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-sofort-payment-method-for-computop.html
-            - title: Integrating the PayPal payment method
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-paypal-payment-method-for-computop.html
-            - title: Integrating the Easy Credit payment method
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-easy-credit-payment-method-for-computop.html
-            - title: Integrating the CRIF payment method
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-crif-payment-method-for-computop.html
-            - title: Integrating the iDeal payment method
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-ideal-payment-method-for-computop.html
-            - title: Integrating the PayNow payment method
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-paynow-payment-method-for-computop.html
-            - title: Integrating the Сredit Сard payment method
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-credit-card-payment-method-for-computop.html
-            - title: Integrating the Direct Debit payment method
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-direct-debit-payment-method-for-computop.html
-            - title: Integrating the Paydirekt payment method
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-paydirekt-payment-method-for-computop.html
-          - title: Integrating Computop
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/computop/integrating-computop.html
-            include_versions:
-            - "202009.0"
-            - "202108.0"
-            - "202204.0"
-            - "202212.0"
-        - title: CrefoPay
-          include_versions:
-          - "201811.0"
-          - "201903.0"
-          - "201907.0"
-          - "202001.0"
-          - "202005.0"
-          - "202009.0"
-          - "202108.0"
-          - "202204.0"
-          nested:
-          - title: Installing and configuring CrefoPay
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/crefopay/installing-and-configuring-crefopay.html
-          - title: Integrating CrefoPay
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/crefopay/integrating-crefopay.html
-          - title: Enabling B2B payments
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/crefopay/crefopay-enabling-b2b-payments.html
-          - title: Callbacks
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/crefopay/crefopay-callbacks.html
-          - title: Notifications
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/crefopay/crefopay-notifications.html
-          - title: Capture and refund processes
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/crefopay/crefopay-capture-and-refund-processes.html
-          - title: Payment methods
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/crefopay/crefopay-payment-methods.html
-        - title: Heidelpay
-          include_versions:
-          - "201811.0"
-          - "201903.0"
-          - "201907.0"
-          - "202001.0"
-          - "202005.0"
-          - "202009.0"
-          - "202108.0"
-          - "202204.0"
-          nested:
-          - title: Installing Heidelpay
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/heidelpay/installing-heidelpay.html
-          - title: Integrating Heidelpay
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/heidelpay/integrating-heidelpay.html
-          - title: Configuring Heidelpay
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/heidelpay/configuring-heidelpay.html
-          - title: Integrating payment methods for Heidelpay
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/heidelpay/integrating-payment-methods-for-heidelpay/integrating-payment-methods-for-heidelpay.html
-            include_versions:
-            - "202212.0"
-            - "202307.0"
-            nested:
-            - title: Integrating the Sofort payment method
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/heidelpay/integrating-payment-methods-for-heidelpay/integrating-the-sofort-payment-method-for-heidelpay.html
-            - title: Integrating the Invoice Secured B2C payment method
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/heidelpay/integrating-payment-methods-for-heidelpay/integrating-the-invoice-secured-b2c-payment-method-for-heidelpay.html
-            - title: Integrating the iDeal payment method
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/heidelpay/integrating-payment-methods-for-heidelpay/integrating-the-ideal-payment-method-for-heidelpay.html
-            - title: Integrating the Easy Credit payment method
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/heidelpay/integrating-payment-methods-for-heidelpay/integrating-the-easy-credit-payment-method-for-heidelpay.html
-            - title: Integrating the Direct Debit payment method
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/heidelpay/integrating-payment-methods-for-heidelpay/integrating-the-direct-debit-payment-method-for-heidelpay.html
-            - title: Integrating the Split-payment Marketplace payment method
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/heidelpay/integrating-payment-methods-for-heidelpay/integrating-the-split-payment-marketplace-payment-method-for-heidelpay.html
-            - title: Integrating the Paypal Debit payment method
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/heidelpay/integrating-payment-methods-for-heidelpay/integrating-the-paypal-debit-payment-method-for-heidelpay.html
-            - title: Integrating the Paypal Authorize payment method
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/heidelpay/integrating-payment-methods-for-heidelpay/integrating-the-paypal-authorize-payment-method-for-heidelpay.html
-            - title: Integrating the Credit Card Secure payment method
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/heidelpay/integrating-payment-methods-for-heidelpay/integrating-the-credit-card-secure-payment-method-for-heidelpay.html
-          - title: Workflow for errors
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/heidelpay/heidelpay-workflow-for-errors.html
-          - title: OMS workflow
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/heidelpay/heidelpay-oms-workflow.html
-          - title: Integrating Heidelpay into the Legacy Demoshop
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/heidelpay/integrating-heidelpay-into-the-legacy-demoshop.html
-            include_versions:
-            - "201811.0"
-            - "201903.0"
-            - "201907.0"
-            - "202001.0"
-        - title: Payolution
-          include_versions:
-          - "201811.0"
-          - "201903.0"
-          - "201907.0"
-          - "202001.0"
-          - "202005.0"
-          - "202009.0"
-          - "202108.0"
-          - "202204.0"
-          nested:
-          - title: Installing and configuring Payolution
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/payolution/installing-and-configuring-payolution.html
-          - title: Integrating Payolution
-            include_versions:
-            - "202009.0"
-            - "202108.0"
-            - "202204.0"
-            - "202212.0"
-            - "202307.0"
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/payolution/integrating-payolution.html
-          - title: Integrating the invoice payment method
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/payolution/integrating-the-invoice-payment-method-for-payolution.html
-          - title: Integrating the installment payment method for
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/payolution/integrating-the-installment-payment-method-for-payolution.html
-          - title: Performing requests
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/payolution/payolution-performing-requests.html
-          - title: Payolution request flow
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/payolution/payolution-request-flow.html
-        - title: Ratenkauf by easyCredit
-          include_versions:
-          - "201811.0"
-          - "201903.0"
-          - "201907.0"
-          - "202001.0"
-          - "202005.0"
-          - "202009.0"
-          - "202108.0"
-          - "202204.0"
-          nested:
-          - title: Installing and configuring ratenkauf by easyCredit
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/ratenkauf-by-easycredit/installing-and-configuring-ratenkauf-by-easycredit.html
-          - title: Integrating ratenkauf by easyCredit
-            url: /docs/scos/dev/technology-partner-guides/payment-partners/ratenkauf-by-easycredit/integrating-ratenkauf-by-easycredit.html
-            include_versions:
-            - "202009.0"
-            - "202108.0"
-            - "202204.0"
-            - "202212.0"
-            - "202307.0"
-        - title: RatePay
-          include_versions:
-          - "201811.0"
-          - "201903.0"
-          - "201907.0"
-          - "202001.0"
-          - "202005.0"
-          - "202009.0"
-          - "202108.0"
-          - "202204.0"
-          nested:
-            - title: Facade methods
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/ratepay/ratepay-facade-methods.html
-            - title: Payment workflow
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/ratepay/ratepay-payment-workflow.html
-            - title: Disabling address updates from the backend application
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/ratepay/disabling-address-updates-from-the-backend-application-for-ratepay.html
-            - title: State machine commands and conditions
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/ratepay/ratepay-state-machine-commands-and-conditions.html
-            - title: Core module structure diagram
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/ratepay/ratepay-core-module-structure-diagram.html
-            - title: State machines
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/ratepay/ratepay-state-machines.html
-            - title: Integrating payment methods for RatePay
-              url: /docs/scos/dev/technology-partner-guides/payment-partners/ratepay/integrating-payment-methods-for-ratepay/integrating-payment-methods-for-ratepay.html
-              nested:
-                - title: Integrating the Direct Debit payment method
-                  url: /docs/scos/dev/technology-partner-guides/payment-partners/ratepay/integrating-payment-methods-for-ratepay/integrating-the-direct-debit-payment-method-for-ratepay.html
-                - title: Integrating the Prepayment payment method
-                  url: /docs/scos/dev/technology-partner-guides/payment-partners/ratepay/integrating-payment-methods-for-ratepay/integrating-the-prepayment-payment-method-for-ratepay.html
-                - title: Integrating the Installment payment method
-                  url: /docs/scos/dev/technology-partner-guides/payment-partners/ratepay/integrating-payment-methods-for-ratepay/integrating-the-installment-payment-method-for-ratepay.html
-                - title: Integrating the Invoice payment method
-                  url: /docs/scos/dev/technology-partner-guides/payment-partners/ratepay/integrating-payment-methods-for-ratepay/integrating-the-invoice-payment-method-for-ratepay.html
-    - title: Product information (PIMERP)
-      nested:
-      - title: Akeneo
-        include_versions:
-        - "202009.0"
-        - "202108.0"
-        nested:
-        - title: Installing and configuring Akeneo
-          url: /docs/scos/dev/technology-partner-guides/product-information-pimerp/akeneo/installing-and-configuring-akeneo.html
-        - title: Akeneo — Console commands
-          url: /docs/scos/dev/technology-partner-guides/product-information-pimerp/akeneo/akeneo-console-commands.html
-          include_versions:
-          - "202009.0"
-          - "202108.0"
-    - title: Shipment
-      include_versions:
-      - "202108.0"
-      nested:
-      - title: Seven Senders
-        nested:
-          - title: Installing and configuring Seven Senders
-            url: /docs/scos/dev/technology-partner-guides/shipment/seven-senders/installing-and-configuring-seven-senders.html
-          - title: Integrating Seven Senders
-            url: /docs/scos/dev/technology-partner-guides/shipment/seven-senders/integrating-seven-senders.html
-          - title: API requests
-            url: /docs/scos/dev/technology-partner-guides/shipment/seven-senders/seven-senders-api-requests.html
-          - title: Mappers
-            url: /docs/scos/dev/technology-partner-guides/shipment/seven-senders/seven-senders-mappers.html
-          - title: Persistance layer
-            url: /docs/scos/dev/technology-partner-guides/shipment/seven-senders/seven-senders-persistance-layer.html
-    - title: Taxes
-      include_versions:
-      - "202108.0"
-      nested:
-        - title: Avalara
-          nested:
-            - title: Integrating Avalara
-              url: /docs/scos/dev/technology-partner-guides/taxes/avalara/integrating-avalara.html
-            - title: Integrating Avalara Tax + Product Options
-              url: /docs/scos/dev/technology-partner-guides/taxes/avalara/integrating-avalara-tax-product-options.html
-            - title: Integrating Avalara Tax + Shipment
-              url: /docs/scos/dev/technology-partner-guides/taxes/avalara/integrating-avalara-tax-shipment.html
-
-  - title: Troubleshooting
-    url: /docs/scos/dev/troubleshooting/troubleshooting.html
-    nested:
-    - title: Troubleshooting general technical issues
-      url: /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-general-technical-issues.html
-      nested:
-      - title: Troubleshooting RabbitMQ
-        url: /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/troubleshooting-rabbitmq.html
-        nested:
-        - title: Messages are moved to error queues
-          url: /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-moved-to-error-queues.html
-        - title: Messages are stuck in the Unacked state
-          url: /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-stuck-in-the-unacked-state.html
-        - title: Messages are stuck without error notifications
-          url: /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-stuck-without-error-notifications.html
-      - title: Fail whale on the frontend
-        url: /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-frontend.html
-      - title: A command fails with a `Killed` message
-        url: /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/a-command-fails-with-a-killed-message.html
-      - title: 'API request fails with the exception: Session has not been set'
-        url: /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/api-request-fails-with-the-exception-session-has-not-been-set.html
-      - title: Composer version 2 compatibility issues
-        url: /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/composer-version-2-compatibility-issues.html
-      - title: Unable to resolve hosts for Mail, Jenkins, and RabbitMQ
-        url: /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq.html
-      - title: PHPStan memory issues
-        url: /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/phpstan-memory-issues.html
-      - title: Prices filter and sorting doesn't work on Frontend
-        url: /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/prices-filter-and-sorting-does-t-work-on-frontend.html
-      - title: ProcessTimedOutException after queue-task-start
-        url: /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/processtimedoutexception-after-queue-task-start.html
-      - title: RuntimeException - Failed to execute regex - PREG_JIT_STACKLIMIT_ERROR
-        url: /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error.html
-      - title: ERROR - remove spryker_logs - volume is in use
-        url: /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-remove-spryker-logs-volume-is-in-use.html
-      - title: Class Silex/ControllerProviderInterface not found
-        url: /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/class-silex-controllerproviderinterface-not-found.html
-      - title: Error response from daemon - OCI runtime create failed - .... \\\"no such file or directory\\\"\""- unknown
-        url: /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown.html
-      - title: RabbitMQ - Zed.CRITICAL - PhpAmqpLib\Exception\AMQPChannelClosedException
-          - Channel connection is closed
-        url: /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.html
-      - title: Router generates absolute URL with localhost
-        url: /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/router-generates-absolute-url-with-localhost.html
-      - title: No data on the Storefront
-        url: /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/no-data-on-the-storefront.html
-      - title: The spy_oms_transition_log table takes up too much space
-        url: /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/the-spy-oms-transition-log-table-takes-up-too-much-space.html
-    - title: Troubleshooting performance issues
-      url: /docs/scos/dev/troubleshooting/troubleshooting-performance-issues/troubleshooting-performance-issues.html
-      nested:
-      - title: External calls take a lot of time
-        url: /docs/scos/dev/troubleshooting/troubleshooting-performance-issues/external-calls-take-a-lot-of-time.html
-      - title: External calls—several calls to Zed
-        url: /docs/scos/dev/troubleshooting/troubleshooting-performance-issues/external-calls-several-calls-to-zed.html
-      - title: N+1 problem
-        url: /docs/scos/dev/troubleshooting/troubleshooting-performance-issues/n+1-problem.html
-      - title: Not optimized Composer on the production environment
-        url: /docs/scos/dev/troubleshooting/troubleshooting-performance-issues/not-optimised-composer-on-the-production-environment.html
-      - title: Redis session lock
-        url: /docs/scos/dev/troubleshooting/troubleshooting-performance-issues/redis-session-lock.html
-      - title: Slow Publish and Synchronization
-        url: /docs/scos/dev/troubleshooting/troubleshooting-performance-issues/slow-publish-and-synchronization.html
-      - title: Technology restrictions
-        url: /docs/scos/dev/troubleshooting/troubleshooting-performance-issues/technology-restrictions.html
-    - title: Troubleshooting Spryker in Vagrant issues
-      url: /docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/troubleshooting-spryker-in-vagrant-installation-issues.html
-      nested:
-      - title: Frontend issues
-        nested:
-        - title: NPM error during installation
-          url: /docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/frontend-issues/npm-error-during-installation.html
-      - title: Other Spryker in Vagrant issues
-        nested:
-        - title: VM stuck at 'Configuring and enabling network interfaces'
-          url: /docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/other-spryker-in-vagrant-issues/vm-stuck-at-configuring-and-enabling-network-interfaces.html
-        - title: Failed to decode response - zlib_decode() - data error
-          url: /docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/other-spryker-in-vagrant-issues/failed-to-decode-response-zlib-decode-data-error.html
-        - title: NFS export issues
-          url: /docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/other-spryker-in-vagrant-issues/nfs-export-issues.html
-        - title: Too many open files in Dev VM
-          url: /docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/other-spryker-in-vagrant-issues/too-many-open-files-in-dev-vm.html
-        - title: Dev VM takes a lot of disk space (40+ GB)
-          url: /docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/other-spryker-in-vagrant-issues/dev-vm-takes-a-lot-of-disk-space-40-gb.html
-        - title: Error on box image download
-          url: /docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/other-spryker-in-vagrant-issues/error-on-box-image-download.html
-        - title: .NFS files crash my console commands
-          url: /docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/other-spryker-in-vagrant-issues/nfs-files-crash-my-console-commands.html
-      - title: Windows issues
-        nested:
-        - title: Windows - The host path of the shared folder is missing
-          url: /docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/windows-issues/windows-the-host-path-of-the-shared-folder-is-missing.html
-      - title: MacOS issues
-        nested:
-        - title: Mac OSX - Wrong curl version error
-          url: /docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/macos-issues/mac-osx-wrong-curl-version-error.html
-        - title: Mac OSX - Installation fails or project folder can not be mounted
-            due to SIP
-          url: /docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/macos-issues/mac-osx-installation-fails-or-project-folder-can-not-be-mounted-due-to-sip.html
-        - title: Mac OSX - iterm2 (locale error)
-          url: /docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/macos-issues/mac-osx-iterm2-locale-error.html
-      - title: Databases and services issues
-        nested:
-        - title: Setup MySQL Workbench to avoid port clashing with the host system
-          url: /docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/databases-and-services-issues/setup-mysql-workbench-to-avoid-port-clashing-with-the-host-system.html
-        - title: Exception connecting to Redis
-          url: /docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/databases-and-services-issues/exception-connecting-to-redis.html
-        - title: Peer authentication failed for user postgres
-          url: /docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/databases-and-services-issues/peer-authentication-failed-for-user-postgres.html
-        - title: My Elasticsearch dies
-          url: /docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/databases-and-services-issues/my-elasticsearch-dies.html
-    - title: Troubleshooting Spryker in Docker Issues
-      url: /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-spryker-in-docker-issues.html
-      nested:
-      - title: Troubleshooting debugging in Docker
-        nested:
-        - title: PHP `xdebug` extension is not active when accessing the website via
-            a browser or curl
-          url: /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-when-accessing-the-website-via-a-browser-or-curl.html
-        - title: nc command tells that the port is opened
-          url: /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-tells-that-the-port-is-opened.html
-        - title: Xdebug does not work
-          url: /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/xdebug-does-not-work.html
-        - title: nc command does not give any output
-          url: /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-does-not-give-any-output.html
-        - title: PHP `xdebug` extension is not active in CLI
-          url: /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-in-cli.html
-      - title: Troubleshooting running applications in Docker
-        nested:
-        - title: An application is not reachable via http
-          url: /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/an-application-is-not-reachable-via-http.html
-        - title: Mutagen synchronization issue
-          url: /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-synchronization-issue.html
-        - title: 413 Request Entity Too Large
-          url: /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/413-request-entity-too-large.html
-        - title: MacOS and Windows - file synchronization issues in Development mode
-          url: /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/macos-and-windows-file-synchronization-issues-in-development-mode.html
-        - title: Nginx welcome page
-          url: /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/nginx-welcome-page.html
-        - title: Mutagen error
-          url: /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-error.html
-        - title: Port is already occupied on host
-          url: /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/port-is-already-occupied-on-host.html
-
-  - title: Example modules
-    url: /docs/scos/dev/example-modules.html
-  - title: Code contribution guide
-    url: /docs/scos/dev/code-contribution-guide.html
diff --git a/_drafts/deprecated-devvm/installing-spryker-with-development-virtual-machine/installing-spryker-with-devvm-on-macos-and-linux.md b/_drafts/deprecated-devvm/installing-spryker-with-development-virtual-machine/installing-spryker-with-devvm-on-macos-and-linux.md
index 92b8da72f18..5532de83f05 100644
--- a/_drafts/deprecated-devvm/installing-spryker-with-development-virtual-machine/installing-spryker-with-devvm-on-macos-and-linux.md
+++ b/_drafts/deprecated-devvm/installing-spryker-with-development-virtual-machine/installing-spryker-with-devvm-on-macos-and-linux.md
@@ -162,5 +162,5 @@ Back Office credentials:
 
 ## Next steps
 
-* [Troubleshooting installation issues](/docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/troubleshooting-spryker-in-vagrant-installation-issues.html)
+* [Troubleshooting installation issues](/docs/dg/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/troubleshooting-spryker-in-vagrant-installation-issues.html)
 * [Configure Spryker after installing with DevVM](/docs/dg/dev/set-up-spryker-locally/installing-spryker-with-development-virtual-machine/configuring-spryker-with-devvm/configuring-spryker-after-installing-with-devvm.html)
diff --git a/_drafts/deprecated-devvm/installing-spryker-with-development-virtual-machine/installing-spryker-with-devvm-on-windows.md b/_drafts/deprecated-devvm/installing-spryker-with-development-virtual-machine/installing-spryker-with-devvm-on-windows.md
index 8a014292e35..77350ae3e7b 100644
--- a/_drafts/deprecated-devvm/installing-spryker-with-development-virtual-machine/installing-spryker-with-devvm-on-windows.md
+++ b/_drafts/deprecated-devvm/installing-spryker-with-development-virtual-machine/installing-spryker-with-devvm-on-windows.md
@@ -252,6 +252,6 @@ Back Office credentials:
 
 ## Next steps
 
-* [Troubleshooting installation issues](/docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/troubleshooting-spryker-in-vagrant-installation-issues.html)
+* [Troubleshooting installation issues](/docs/dg/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/troubleshooting-spryker-in-vagrant-installation-issues.html)
 
 * [Configure Spryker after installing with DevVM](/docs/dg/dev/set-up-spryker-locally/installing-spryker-with-development-virtual-machine/configuring-spryker-with-devvm/configuring-spryker-after-installing-with-devvm.html)
diff --git a/_drafts/deprecated-devvm/installing-spryker-without-docker.md b/_drafts/deprecated-devvm/installing-spryker-without-docker.md
index e42f2fa7611..18ce301692b 100644
--- a/_drafts/deprecated-devvm/installing-spryker-without-docker.md
+++ b/_drafts/deprecated-devvm/installing-spryker-without-docker.md
@@ -243,4 +243,4 @@ Credentials to access the administrator interface: user `admin@spryker.com` and
 
 ## Next steps:
 
-* [Troubleshooting installation issues](/docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/troubleshooting-spryker-in-vagrant-installation-issues.html)
+* [Troubleshooting installation issues](/docs/dg/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/troubleshooting-spryker-in-vagrant-installation-issues.html)
diff --git a/_drafts/deprecated-devvm/troubleshooting-spryker-in-vagrant-issues/troubleshooting-spryker-in-vagrant-installation-issues.md b/_drafts/deprecated-devvm/troubleshooting-spryker-in-vagrant-issues/troubleshooting-spryker-in-vagrant-installation-issues.md
index 75821433c7c..f41e6ac36d7 100644
--- a/_drafts/deprecated-devvm/troubleshooting-spryker-in-vagrant-issues/troubleshooting-spryker-in-vagrant-installation-issues.md
+++ b/_drafts/deprecated-devvm/troubleshooting-spryker-in-vagrant-issues/troubleshooting-spryker-in-vagrant-installation-issues.md
@@ -35,34 +35,34 @@ When you [install Spryker with Vagrant](/docs/dg/dev/set-up-spryker-locally/inst
 
 MacOS issues:
 
-  * [Mac OSX: iterm2 (locale error)](/docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/macos-issues/mac-osx-iterm2-locale-error.html)
-  * [Mac OSX: Installation fails or project folder can not be mounted due to SIP](/docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/macos-issues/mac-osx-installation-fails-or-project-folder-can-not-be-mounted-due-to-sip.html)
-  * [Mac OSX: Wrong curl version error](/docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/macos-issues/mac-osx-wrong-curl-version-error.html)
+  * [Mac OSX: iterm2 (locale error)](/docs/dg/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/macos-issues/mac-osx-iterm2-locale-error.html)
+  * [Mac OSX: Installation fails or project folder can not be mounted due to SIP](/docs/dg/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/macos-issues/mac-osx-installation-fails-or-project-folder-can-not-be-mounted-due-to-sip.html)
+  * [Mac OSX: Wrong curl version error](/docs/dg/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/macos-issues/mac-osx-wrong-curl-version-error.html)
 
 Windows issues:
 
-  * [Windows: The host path of the shared folder is missing](/docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/windows-issues/windows-the-host-path-of-the-shared-folder-is-missing.html)
+  * [Windows: The host path of the shared folder is missing](/docs/dg/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/windows-issues/windows-the-host-path-of-the-shared-folder-is-missing.html)
 
 Databases and services issues:
 
-  * [Peer authentication failed for user postgres](/docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/databases-and-services-issues/peer-authentication-failed-for-user-postgres.html)
-  * [Setup MySQL Workbench to avoid port clashing with the host system](/docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/databases-and-services-issues/setup-mysql-workbench-to-avoid-port-clashing-with-the-host-system.html)
-  * [My Elasticsearch dies](/docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/databases-and-services-issues/my-elasticsearch-dies.html)
-  * [Exception connecting to Redis](/docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/databases-and-services-issues/exception-connecting-to-redis.html)
+  * [Peer authentication failed for user postgres](/docs/dg/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/databases-and-services-issues/peer-authentication-failed-for-user-postgres.html)
+  * [Setup MySQL Workbench to avoid port clashing with the host system](/docs/dg/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/databases-and-services-issues/setup-mysql-workbench-to-avoid-port-clashing-with-the-host-system.html)
+  * [My Elasticsearch dies](/docs/dg/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/databases-and-services-issues/my-elasticsearch-dies.html)
+  * [Exception connecting to Redis](/docs/dg/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/databases-and-services-issues/exception-connecting-to-redis.html)
 
 Frontend issues:
 
-  * [NPM error during installation](/docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/frontend-issues/npm-error-during-installation.html)
+  * [NPM error during installation](/docs/dg/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/frontend-issues/npm-error-during-installation.html)
 
 Other Spryker in Vagrant issues:
 
-  * [Too many open files in Dev VM](/docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/other-spryker-in-vagrant-issues/too-many-open-files-in-dev-vm.html)
-  * [VM stuck at *Configuring and enabling network interfaces*](/docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/other-spryker-in-vagrant-issues/vm-stuck-at-configuring-and-enabling-network-interfaces.html)
-  * [Error on box image download](/docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/other-spryker-in-vagrant-issues/error-on-box-image-download.html)
-  * [NFS export issues](/docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/other-spryker-in-vagrant-issues/nfs-export-issues.html)
-  * [.NFS files crash my console commands](/docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/other-spryker-in-vagrant-issues/nfs-files-crash-my-console-commands.html)
-  * [Failed to decode response: zlib_decode(): data error](/docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/other-spryker-in-vagrant-issues/failed-to-decode-response-zlib-decode-data-error.html)
-  * [Dev VM takes a lot of disk space (40+ GB)](/docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/other-spryker-in-vagrant-issues/dev-vm-takes-a-lot-of-disk-space-40-gb.html)
+  * [Too many open files in Dev VM](/docs/dg/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/other-spryker-in-vagrant-issues/too-many-open-files-in-dev-vm.html)
+  * [VM stuck at *Configuring and enabling network interfaces*](/docs/dg/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/other-spryker-in-vagrant-issues/vm-stuck-at-configuring-and-enabling-network-interfaces.html)
+  * [Error on box image download](/docs/dg/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/other-spryker-in-vagrant-issues/error-on-box-image-download.html)
+  * [NFS export issues](/docs/dg/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/other-spryker-in-vagrant-issues/nfs-export-issues.html)
+  * [.NFS files crash my console commands](/docs/dg/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/other-spryker-in-vagrant-issues/nfs-files-crash-my-console-commands.html)
+  * [Failed to decode response: zlib_decode(): data error](/docs/dg/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/other-spryker-in-vagrant-issues/failed-to-decode-response-zlib-decode-data-error.html)
+  * [Dev VM takes a lot of disk space (40+ GB)](/docs/dg/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/other-spryker-in-vagrant-issues/dev-vm-takes-a-lot-of-disk-space-40-gb.html)
 
 If you found a solution to a repetitive issue, please suggest a change to this page using "Edit and Report" button.
 
diff --git a/docs/scos/dev/drafts-dev/cleaning-up-devvm.md b/_drafts/drafts-dev/cleaning-up-devvm.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/cleaning-up-devvm.md
rename to _drafts/drafts-dev/cleaning-up-devvm.md
diff --git a/docs/scos/dev/drafts-dev/contributing-to-documentation.md b/_drafts/drafts-dev/contributing-to-documentation.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/contributing-to-documentation.md
rename to _drafts/drafts-dev/contributing-to-documentation.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201811.0/catalog-schema.md b/_drafts/drafts-dev/database-schema-guide/201811.0/catalog-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201811.0/catalog-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201811.0/catalog-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201811.0/cms-schema.md b/_drafts/drafts-dev/database-schema-guide/201811.0/cms-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201811.0/cms-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201811.0/cms-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201811.0/company-account-schema.md b/_drafts/drafts-dev/database-schema-guide/201811.0/company-account-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201811.0/company-account-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201811.0/company-account-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201811.0/customer-lists-schema.md b/_drafts/drafts-dev/database-schema-guide/201811.0/customer-lists-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201811.0/customer-lists-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201811.0/customer-lists-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201811.0/customer-schema.md b/_drafts/drafts-dev/database-schema-guide/201811.0/customer-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201811.0/customer-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201811.0/customer-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201811.0/database-schema-guide.md b/_drafts/drafts-dev/database-schema-guide/201811.0/database-schema-guide.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201811.0/database-schema-guide.md
rename to _drafts/drafts-dev/database-schema-guide/201811.0/database-schema-guide.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201811.0/discounts-schema.md b/_drafts/drafts-dev/database-schema-guide/201811.0/discounts-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201811.0/discounts-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201811.0/discounts-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201811.0/gift-cards-schema.md b/_drafts/drafts-dev/database-schema-guide/201811.0/gift-cards-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201811.0/gift-cards-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201811.0/gift-cards-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201811.0/marketplace-schema.md b/_drafts/drafts-dev/database-schema-guide/201811.0/marketplace-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201811.0/marketplace-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201811.0/marketplace-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201811.0/navigation-schema.md b/_drafts/drafts-dev/database-schema-guide/201811.0/navigation-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201811.0/navigation-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201811.0/navigation-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201811.0/sales-schema.md b/_drafts/drafts-dev/database-schema-guide/201811.0/sales-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201811.0/sales-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201811.0/sales-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201811.0/shipment-schema.md b/_drafts/drafts-dev/database-schema-guide/201811.0/shipment-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201811.0/shipment-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201811.0/shipment-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201811.0/tax-schema.md b/_drafts/drafts-dev/database-schema-guide/201811.0/tax-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201811.0/tax-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201811.0/tax-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201811.0/url-schema.md b/_drafts/drafts-dev/database-schema-guide/201811.0/url-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201811.0/url-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201811.0/url-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201811.0/zed-administration-schema.md b/_drafts/drafts-dev/database-schema-guide/201811.0/zed-administration-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201811.0/zed-administration-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201811.0/zed-administration-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201903.0/catalog-schema.md b/_drafts/drafts-dev/database-schema-guide/201903.0/catalog-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201903.0/catalog-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201903.0/catalog-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201903.0/cms-schema.md b/_drafts/drafts-dev/database-schema-guide/201903.0/cms-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201903.0/cms-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201903.0/cms-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201903.0/company-account-schema.md b/_drafts/drafts-dev/database-schema-guide/201903.0/company-account-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201903.0/company-account-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201903.0/company-account-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201903.0/customer-lists-schema.md b/_drafts/drafts-dev/database-schema-guide/201903.0/customer-lists-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201903.0/customer-lists-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201903.0/customer-lists-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201903.0/customer-schema.md b/_drafts/drafts-dev/database-schema-guide/201903.0/customer-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201903.0/customer-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201903.0/customer-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201903.0/database-schema-guide.md b/_drafts/drafts-dev/database-schema-guide/201903.0/database-schema-guide.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201903.0/database-schema-guide.md
rename to _drafts/drafts-dev/database-schema-guide/201903.0/database-schema-guide.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201903.0/discounts-schema.md b/_drafts/drafts-dev/database-schema-guide/201903.0/discounts-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201903.0/discounts-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201903.0/discounts-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201903.0/gift-cards-schema.md b/_drafts/drafts-dev/database-schema-guide/201903.0/gift-cards-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201903.0/gift-cards-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201903.0/gift-cards-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201903.0/marketplace-schema.md b/_drafts/drafts-dev/database-schema-guide/201903.0/marketplace-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201903.0/marketplace-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201903.0/marketplace-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201903.0/navigation-schema.md b/_drafts/drafts-dev/database-schema-guide/201903.0/navigation-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201903.0/navigation-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201903.0/navigation-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201903.0/sales-schema.md b/_drafts/drafts-dev/database-schema-guide/201903.0/sales-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201903.0/sales-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201903.0/sales-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201903.0/shipment-schema.md b/_drafts/drafts-dev/database-schema-guide/201903.0/shipment-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201903.0/shipment-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201903.0/shipment-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201903.0/tax-schema.md b/_drafts/drafts-dev/database-schema-guide/201903.0/tax-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201903.0/tax-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201903.0/tax-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201903.0/url-schema.md b/_drafts/drafts-dev/database-schema-guide/201903.0/url-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201903.0/url-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201903.0/url-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201903.0/zed-administration-schema.md b/_drafts/drafts-dev/database-schema-guide/201903.0/zed-administration-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201903.0/zed-administration-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201903.0/zed-administration-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201907.0/catalog-schema.md b/_drafts/drafts-dev/database-schema-guide/201907.0/catalog-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201907.0/catalog-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201907.0/catalog-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201907.0/cms-schema.md b/_drafts/drafts-dev/database-schema-guide/201907.0/cms-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201907.0/cms-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201907.0/cms-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201907.0/company-account-schema.md b/_drafts/drafts-dev/database-schema-guide/201907.0/company-account-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201907.0/company-account-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201907.0/company-account-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201907.0/customer-lists-schema.md b/_drafts/drafts-dev/database-schema-guide/201907.0/customer-lists-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201907.0/customer-lists-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201907.0/customer-lists-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201907.0/customer-schema.md b/_drafts/drafts-dev/database-schema-guide/201907.0/customer-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201907.0/customer-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201907.0/customer-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201907.0/database-schema-guide.md b/_drafts/drafts-dev/database-schema-guide/201907.0/database-schema-guide.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201907.0/database-schema-guide.md
rename to _drafts/drafts-dev/database-schema-guide/201907.0/database-schema-guide.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201907.0/discounts-schema.md b/_drafts/drafts-dev/database-schema-guide/201907.0/discounts-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201907.0/discounts-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201907.0/discounts-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201907.0/gift-cards-schema.md b/_drafts/drafts-dev/database-schema-guide/201907.0/gift-cards-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201907.0/gift-cards-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201907.0/gift-cards-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201907.0/marketplace-schema.md b/_drafts/drafts-dev/database-schema-guide/201907.0/marketplace-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201907.0/marketplace-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201907.0/marketplace-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201907.0/navigation-schema.md b/_drafts/drafts-dev/database-schema-guide/201907.0/navigation-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201907.0/navigation-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201907.0/navigation-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201907.0/sales-schema.md b/_drafts/drafts-dev/database-schema-guide/201907.0/sales-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201907.0/sales-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201907.0/sales-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201907.0/shipment-schema.md b/_drafts/drafts-dev/database-schema-guide/201907.0/shipment-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201907.0/shipment-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201907.0/shipment-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201907.0/tax-schema.md b/_drafts/drafts-dev/database-schema-guide/201907.0/tax-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201907.0/tax-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201907.0/tax-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201907.0/url-schema.md b/_drafts/drafts-dev/database-schema-guide/201907.0/url-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201907.0/url-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201907.0/url-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/201907.0/zed-administration-schema.md b/_drafts/drafts-dev/database-schema-guide/201907.0/zed-administration-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/201907.0/zed-administration-schema.md
rename to _drafts/drafts-dev/database-schema-guide/201907.0/zed-administration-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202001.0/catalog-schema.md b/_drafts/drafts-dev/database-schema-guide/202001.0/catalog-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202001.0/catalog-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202001.0/catalog-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202001.0/cms-schema.md b/_drafts/drafts-dev/database-schema-guide/202001.0/cms-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202001.0/cms-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202001.0/cms-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202001.0/company-account-schema.md b/_drafts/drafts-dev/database-schema-guide/202001.0/company-account-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202001.0/company-account-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202001.0/company-account-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202001.0/customer-lists-schema.md b/_drafts/drafts-dev/database-schema-guide/202001.0/customer-lists-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202001.0/customer-lists-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202001.0/customer-lists-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202001.0/customer-schema.md b/_drafts/drafts-dev/database-schema-guide/202001.0/customer-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202001.0/customer-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202001.0/customer-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202001.0/database-schema-guide.md b/_drafts/drafts-dev/database-schema-guide/202001.0/database-schema-guide.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202001.0/database-schema-guide.md
rename to _drafts/drafts-dev/database-schema-guide/202001.0/database-schema-guide.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202001.0/discounts-schema.md b/_drafts/drafts-dev/database-schema-guide/202001.0/discounts-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202001.0/discounts-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202001.0/discounts-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202001.0/gift-cards-schema.md b/_drafts/drafts-dev/database-schema-guide/202001.0/gift-cards-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202001.0/gift-cards-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202001.0/gift-cards-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202001.0/marketplace-schema.md b/_drafts/drafts-dev/database-schema-guide/202001.0/marketplace-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202001.0/marketplace-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202001.0/marketplace-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202001.0/navigation-schema.md b/_drafts/drafts-dev/database-schema-guide/202001.0/navigation-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202001.0/navigation-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202001.0/navigation-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202001.0/sales-schema.md b/_drafts/drafts-dev/database-schema-guide/202001.0/sales-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202001.0/sales-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202001.0/sales-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202001.0/shipment-schema.md b/_drafts/drafts-dev/database-schema-guide/202001.0/shipment-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202001.0/shipment-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202001.0/shipment-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202001.0/tax-schema.md b/_drafts/drafts-dev/database-schema-guide/202001.0/tax-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202001.0/tax-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202001.0/tax-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202001.0/url-schema.md b/_drafts/drafts-dev/database-schema-guide/202001.0/url-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202001.0/url-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202001.0/url-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202001.0/zed-administration-schema.md b/_drafts/drafts-dev/database-schema-guide/202001.0/zed-administration-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202001.0/zed-administration-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202001.0/zed-administration-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202005.0/catalog-schema.md b/_drafts/drafts-dev/database-schema-guide/202005.0/catalog-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202005.0/catalog-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202005.0/catalog-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202005.0/cms-schema.md b/_drafts/drafts-dev/database-schema-guide/202005.0/cms-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202005.0/cms-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202005.0/cms-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202005.0/company-account-schema.md b/_drafts/drafts-dev/database-schema-guide/202005.0/company-account-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202005.0/company-account-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202005.0/company-account-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202005.0/customer-lists-schema.md b/_drafts/drafts-dev/database-schema-guide/202005.0/customer-lists-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202005.0/customer-lists-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202005.0/customer-lists-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202005.0/customer-schema.md b/_drafts/drafts-dev/database-schema-guide/202005.0/customer-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202005.0/customer-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202005.0/customer-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202005.0/database-schema-guide.md b/_drafts/drafts-dev/database-schema-guide/202005.0/database-schema-guide.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202005.0/database-schema-guide.md
rename to _drafts/drafts-dev/database-schema-guide/202005.0/database-schema-guide.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202005.0/discounts-schema.md b/_drafts/drafts-dev/database-schema-guide/202005.0/discounts-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202005.0/discounts-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202005.0/discounts-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202005.0/gift-cards-schema.md b/_drafts/drafts-dev/database-schema-guide/202005.0/gift-cards-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202005.0/gift-cards-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202005.0/gift-cards-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202005.0/marketplace-schema.md b/_drafts/drafts-dev/database-schema-guide/202005.0/marketplace-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202005.0/marketplace-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202005.0/marketplace-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202005.0/navigation-schema.md b/_drafts/drafts-dev/database-schema-guide/202005.0/navigation-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202005.0/navigation-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202005.0/navigation-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202005.0/sales-schema.md b/_drafts/drafts-dev/database-schema-guide/202005.0/sales-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202005.0/sales-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202005.0/sales-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202005.0/shipment-schema.md b/_drafts/drafts-dev/database-schema-guide/202005.0/shipment-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202005.0/shipment-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202005.0/shipment-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202005.0/tax-schema.md b/_drafts/drafts-dev/database-schema-guide/202005.0/tax-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202005.0/tax-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202005.0/tax-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202005.0/url-schema.md b/_drafts/drafts-dev/database-schema-guide/202005.0/url-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202005.0/url-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202005.0/url-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202005.0/zed-administration-schema.md b/_drafts/drafts-dev/database-schema-guide/202005.0/zed-administration-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202005.0/zed-administration-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202005.0/zed-administration-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202009.0/catalog-schema.md b/_drafts/drafts-dev/database-schema-guide/202009.0/catalog-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202009.0/catalog-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202009.0/catalog-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202009.0/cms-schema.md b/_drafts/drafts-dev/database-schema-guide/202009.0/cms-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202009.0/cms-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202009.0/cms-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202009.0/company-account-schema.md b/_drafts/drafts-dev/database-schema-guide/202009.0/company-account-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202009.0/company-account-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202009.0/company-account-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202009.0/customer-lists-schema.md b/_drafts/drafts-dev/database-schema-guide/202009.0/customer-lists-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202009.0/customer-lists-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202009.0/customer-lists-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202009.0/customer-schema.md b/_drafts/drafts-dev/database-schema-guide/202009.0/customer-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202009.0/customer-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202009.0/customer-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202009.0/database-schema-guide.md b/_drafts/drafts-dev/database-schema-guide/202009.0/database-schema-guide.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202009.0/database-schema-guide.md
rename to _drafts/drafts-dev/database-schema-guide/202009.0/database-schema-guide.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202009.0/discounts-schema.md b/_drafts/drafts-dev/database-schema-guide/202009.0/discounts-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202009.0/discounts-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202009.0/discounts-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202009.0/gift-cards-schema.md b/_drafts/drafts-dev/database-schema-guide/202009.0/gift-cards-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202009.0/gift-cards-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202009.0/gift-cards-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202009.0/marketplace-schema.md b/_drafts/drafts-dev/database-schema-guide/202009.0/marketplace-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202009.0/marketplace-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202009.0/marketplace-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202009.0/navigation-schema.md b/_drafts/drafts-dev/database-schema-guide/202009.0/navigation-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202009.0/navigation-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202009.0/navigation-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202009.0/sales-schema.md b/_drafts/drafts-dev/database-schema-guide/202009.0/sales-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202009.0/sales-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202009.0/sales-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202009.0/shipment-schema.md b/_drafts/drafts-dev/database-schema-guide/202009.0/shipment-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202009.0/shipment-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202009.0/shipment-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202009.0/tax-schema.md b/_drafts/drafts-dev/database-schema-guide/202009.0/tax-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202009.0/tax-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202009.0/tax-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202009.0/url-schema.md b/_drafts/drafts-dev/database-schema-guide/202009.0/url-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202009.0/url-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202009.0/url-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202009.0/zed-administration-schema.md b/_drafts/drafts-dev/database-schema-guide/202009.0/zed-administration-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202009.0/zed-administration-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202009.0/zed-administration-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202108.0/catalog-schema.md b/_drafts/drafts-dev/database-schema-guide/202108.0/catalog-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202108.0/catalog-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202108.0/catalog-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202108.0/cms-schema.md b/_drafts/drafts-dev/database-schema-guide/202108.0/cms-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202108.0/cms-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202108.0/cms-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202108.0/company-account-schema.md b/_drafts/drafts-dev/database-schema-guide/202108.0/company-account-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202108.0/company-account-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202108.0/company-account-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202108.0/customer-lists-schema.md b/_drafts/drafts-dev/database-schema-guide/202108.0/customer-lists-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202108.0/customer-lists-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202108.0/customer-lists-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202108.0/customer-schema.md b/_drafts/drafts-dev/database-schema-guide/202108.0/customer-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202108.0/customer-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202108.0/customer-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202108.0/database-schema-guide.md b/_drafts/drafts-dev/database-schema-guide/202108.0/database-schema-guide.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202108.0/database-schema-guide.md
rename to _drafts/drafts-dev/database-schema-guide/202108.0/database-schema-guide.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202108.0/discounts-schema.md b/_drafts/drafts-dev/database-schema-guide/202108.0/discounts-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202108.0/discounts-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202108.0/discounts-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202108.0/gift-cards-schema.md b/_drafts/drafts-dev/database-schema-guide/202108.0/gift-cards-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202108.0/gift-cards-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202108.0/gift-cards-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202108.0/marketplace-schema.md b/_drafts/drafts-dev/database-schema-guide/202108.0/marketplace-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202108.0/marketplace-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202108.0/marketplace-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202108.0/navigation-schema.md b/_drafts/drafts-dev/database-schema-guide/202108.0/navigation-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202108.0/navigation-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202108.0/navigation-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202108.0/sales-schema.md b/_drafts/drafts-dev/database-schema-guide/202108.0/sales-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202108.0/sales-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202108.0/sales-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202108.0/shipment-schema.md b/_drafts/drafts-dev/database-schema-guide/202108.0/shipment-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202108.0/shipment-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202108.0/shipment-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202108.0/tax-schema.md b/_drafts/drafts-dev/database-schema-guide/202108.0/tax-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202108.0/tax-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202108.0/tax-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202108.0/url-schema.md b/_drafts/drafts-dev/database-schema-guide/202108.0/url-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202108.0/url-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202108.0/url-schema.md
diff --git a/docs/scos/dev/drafts-dev/database-schema-guide/202108.0/zed-administration-schema.md b/_drafts/drafts-dev/database-schema-guide/202108.0/zed-administration-schema.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/database-schema-guide/202108.0/zed-administration-schema.md
rename to _drafts/drafts-dev/database-schema-guide/202108.0/zed-administration-schema.md
diff --git a/docs/scos/dev/drafts-dev/deapi_download_spec_button.png b/_drafts/drafts-dev/deapi_download_spec_button.png
similarity index 100%
rename from docs/scos/dev/drafts-dev/deapi_download_spec_button.png
rename to _drafts/drafts-dev/deapi_download_spec_button.png
diff --git a/docs/scos/dev/drafts-dev/deapi_generation_in_progress.png b/_drafts/drafts-dev/deapi_generation_in_progress.png
similarity index 100%
rename from docs/scos/dev/drafts-dev/deapi_generation_in_progress.png
rename to _drafts/drafts-dev/deapi_generation_in_progress.png
diff --git a/docs/scos/dev/drafts-dev/multistore-infrastructure-options.md b/_drafts/drafts-dev/multistore-infrastructure-options.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/multistore-infrastructure-options.md
rename to _drafts/drafts-dev/multistore-infrastructure-options.md
diff --git a/docs/scos/dev/drafts-dev/paas+/dev/change-default-branch.md/set-default-branch.png b/_drafts/drafts-dev/paas+/dev/change-default-branch.md/set-default-branch.png
similarity index 100%
rename from docs/scos/dev/drafts-dev/paas+/dev/change-default-branch.md/set-default-branch.png
rename to _drafts/drafts-dev/paas+/dev/change-default-branch.md/set-default-branch.png
diff --git a/docs/scos/dev/drafts-dev/roadmap.md b/_drafts/drafts-dev/roadmap.md
similarity index 100%
rename from docs/scos/dev/drafts-dev/roadmap.md
rename to _drafts/drafts-dev/roadmap.md
diff --git a/_includes/topnav.html b/_includes/topnav.html
index d69f9301c39..c746a33b781 100644
--- a/_includes/topnav.html
+++ b/_includes/topnav.html
@@ -37,8 +37,6 @@
                                                 Managing cloud applications
                                                 {% elsif page.product == 'ca' and page.role == 'devscu' %}
                                                 Upgrading cloud applications
-                                                {% elsif page.product == 'scos' and page.role == 'dev' %}
-                                                SCOS developer guide
                                                 {% elsif page.product == 'scos' and page.role == 'user' %}
                                                 SCOS users guide
                                                 {% else %}
@@ -49,7 +47,7 @@
                                         </a>
                                         <ul class="main-nav__drop main-nav__drop--mob-static dropdown-menu" aria-labelledby="navbarDropdownMenuLink">
                                           <li>
-                                              <a href="/docs/dg/dev/developer-getting-started-guide.html" class="main-nav__drop-link">
+                                              <a href="/docs/dg/dev/development-getting-started-guide.html" class="main-nav__drop-link">
                                               Development
                                               </a>
                                           </li>
@@ -58,32 +56,11 @@
                                               Packaged Business Capabilities [BETA]
                                               </a>
                                           </li>
-                                            <li class="dropdown">
-                                                <a href="/" class="main-nav__drop-link dropdown-toggle" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">
-                                                    Spryker Commerce OS
-                                                    <i class="main-nav__drop-link-arrow icon-arrow-right"></i>
-                                                </a>
-                                                <ul class="main-nav__drop dropdown-menu">
-                                                    <li>
-                                                        <a href="/docs/scos/dev/developer-getting-started-guide.html" class="main-nav__drop-link">
-                                                            <span class="main-nav__drop-link-title">
-                                                                <i class="icon-developer"></i>
-                                                                Developer
-                                                            </span>
-                                                            <span class="main-nav__drop-link-subtitle">SCOS developer guide</span>
-                                                        </a>
-                                                    </li>
-                                                    <li>
-                                                        <a href="/docs/scos/user/intro-to-spryker/intro-to-spryker.html" class="main-nav__drop-link">
-                                                            <span class="main-nav__drop-link-title">
-                                                                <i class="icon-business"></i>
-                                                                Business User
-                                                            </span>
-                                                            <span class="main-nav__drop-link-subtitle">SCOS users guide</span>
-                                                        </a>
-                                                    </li>
-                                                </ul>
-                                            </li>
+                                          <li>
+                                              <a href="/docs/scos/user/intro-to-spryker/intro-to-spryker.html" class="main-nav__drop-link">
+                                              SCOS user guide
+                                              </a>
+                                          </li>
                                             <li class="dropdown">
                                                 <a href="/" class="main-nav__drop-link dropdown-toggle" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">
                                                     Cloud administration
diff --git a/_layouts/home.html b/_layouts/home.html
index 6c528fc624d..114c578ab15 100644
--- a/_layouts/home.html
+++ b/_layouts/home.html
@@ -29,9 +29,8 @@ <h2 class="card__heading-title">Developer guides</h2>
                     <div class="card__footer">
                         <ul class="card__links">
                             <li><a href="/docs/scos/dev/set-up-spryker-locally/quickstart-guides-install-spryker/quickstart-guides-install-spryker.html">Quick installation guides</a></li>
-                            <li><a href="/docs/dg/dev/developer-getting-started-guide.html">Development guides</a></li>
+                            <li><a href="/docs/dg/dev/development-getting-started-guide.html">Development guides</a></li>
                             <li><a href="/docs/pbc/all/pbc.html">PBC guides</a></li>
-                            <li><a href="/docs/scos/dev/developer-getting-started-guide.html">SCOS developer guides</a></li>
                         </ul>
                     </div>
                 </div>
diff --git a/_scripts/redirects_generator/redirect_from_generator.sh b/_scripts/redirects_generator/redirect_from_generator.sh
index 0c382ab8c82..2392b58b1e1 100644
--- a/_scripts/redirects_generator/redirect_from_generator.sh
+++ b/_scripts/redirects_generator/redirect_from_generator.sh
@@ -21,7 +21,7 @@ process_markdown_files() {
 }
 
 # Specify the folder to add `redirect_from` to
-folder_path="docs/sdk"
+folder_path="docs/scos/dev/troubleshooting"
 
 # Check if the folder exists
 if [ ! -d "$folder_path" ]; then
diff --git a/_scripts/redirects_generator/redirects_generator.sh b/_scripts/redirects_generator/redirects_generator.sh
index 1d6a53a0d0a..41fb905ad48 100644
--- a/_scripts/redirects_generator/redirects_generator.sh
+++ b/_scripts/redirects_generator/redirects_generator.sh
@@ -37,7 +37,7 @@ process_files() {
 }
 
 # Specify the folder containing the files to add paths to
-folder_path="docs/sdk"
+folder_path="docs/scos/dev/troubleshooting"
 
 # Check if the folder exists
 if [ ! -d "$folder_path" ]; then
diff --git a/docs/ca/dev/performance-testing-in-staging-enivronments.md b/docs/ca/dev/performance-testing-in-staging-enivronments.md
index e7840990451..cb62597822b 100644
--- a/docs/ca/dev/performance-testing-in-staging-enivronments.md
+++ b/docs/ca/dev/performance-testing-in-staging-enivronments.md
@@ -39,7 +39,7 @@ Gatling is capable of creating an immense amount of traffic from a single node,
 
 The purpose of this guide is to show you how to integrate Spryker's load testing tool into your environment. While the instructions here will focus on setting this up with using one of Spryker’s many available demo shops, it can also be implemented into an on-going project.
 
-For instructions on setting up a developer environment using one of the available Spryker shops, you can visit our [getting started guide](/docs/scos/dev/developer-getting-started-guide.html) which shows you how to set up the Spryker Commerce OS.
+For instructions on setting up a developer environment using one of the available Spryker shops, you can visit our [getting started guide](/docs/dg/dev/development-getting-started-guide.html) which shows you how to set up the Spryker Commerce OS.
 
 Some of the following options are available to choose from:
 - [B2B Demo Shop](/docs/scos/user/intro-to-spryker//b2b-suite.html): A boilerplate for B2B commerce projects.
diff --git a/docs/dg/dev/architecture/module-api/semantic-versioning-major-vs.-minor-vs.-patch-release.md b/docs/dg/dev/architecture/module-api/semantic-versioning-major-vs.-minor-vs.-patch-release.md
index 4a80cf8f77b..ebbd9c3f34f 100644
--- a/docs/dg/dev/architecture/module-api/semantic-versioning-major-vs.-minor-vs.-patch-release.md
+++ b/docs/dg/dev/architecture/module-api/semantic-versioning-major-vs.-minor-vs.-patch-release.md
@@ -56,6 +56,6 @@ Usually, you need to run `composer update` to get Spryker Core updates, because
 
 Some minor updates require specific development effort for the project, which is caused by the deprecation of some old approaches or 3rd party modules. We recommend reading the [release notes](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes.html) published after the project's start.
 
-For solutions to general technical issues you might have, see [Troubleshooting general technical issues](/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-general-technical-issues.html).
+For solutions to general technical issues you might have, see [Troubleshooting general technical issues](/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-general-technical-issues.html).
 
 {% endinfo_block %}
diff --git a/docs/dg/dev/developer-getting-started-guide.md b/docs/dg/dev/development-getting-started-guide.md
similarity index 98%
rename from docs/dg/dev/developer-getting-started-guide.md
rename to docs/dg/dev/development-getting-started-guide.md
index 60aeb442bad..dbaa2ec473d 100644
--- a/docs/dg/dev/developer-getting-started-guide.md
+++ b/docs/dg/dev/development-getting-started-guide.md
@@ -1,5 +1,5 @@
 ---
-title: Developer getting started guide
+title: Development getting started guide
 description: This is a step-by-step checklist that you can follow through all the stages of working with Spryker.
 last_updated: July 11, 2022
 template: concept-topic-template
@@ -8,6 +8,7 @@ originalArticleId: 79b50d48-6f09-45b0-9e4a-f372e274d462
 redirect_from:
   - /docs/scos/dev/module-migration-guides/about-migration-guides.html
   - /docs/pbc/all/punchout/202307.0/punchout-catalogs-overview.html
+  - /docs/scos/dev/developer-getting-started-guide.html
 ---
 
 This document helps you get started with the Spryker Cloud Commerce OS. It has been structured as a step-by-step checklist to help get you through all of the stages involved in working with Spryker. If you have any questions after following these instructions, you can connect with the Spryker community at [CommerceQuest](https://commercequest.space/).
diff --git a/docs/scos/dev/example-modules.md b/docs/dg/dev/example-modules.md
similarity index 98%
rename from docs/scos/dev/example-modules.md
rename to docs/dg/dev/example-modules.md
index 70f9a34653c..29cda6bc4d0 100644
--- a/docs/scos/dev/example-modules.md
+++ b/docs/dg/dev/example-modules.md
@@ -3,6 +3,8 @@ title: Example modules
 description: Spryker example modules are designed for specific use cases and their functionality is aligned with unique business requirements.
 last_updated: Jan 11, 2024
 template: concept-topic-template
+redirect_from:
+- /docs/scos/dev/example-modules.html
 ---
 
 The Spryker *core modules* provide generic, reusable functionality that benefits a wide range of use cases. These modules offer a foundation for customization and serve as versatile building blocks.
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-does-not-give-any-output.md b/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-does-not-give-any-output.md
new file mode 100644
index 00000000000..bc5785b31ae
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-does-not-give-any-output.md
@@ -0,0 +1,21 @@
+---
+title: nc command does not give any output
+description: If the nc command does not give any output, contact us
+last_updated: Jun 16, 2021
+template: troubleshooting-guide-template
+originalLink: https://documentation.spryker.com/2021080/docs/nc-command-does-not-give-any-output
+originalArticleId: 65a16193-926a-4aab-a5df-2570e880168c
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-does-not-give-any-output.html
+related:
+  - title: nc command tells that the port is opened
+    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-tells-that-the-port-is-opened.html
+---
+
+## Description
+
+`nc` command does not give any output.
+
+## Solution
+
+[contact us](https://spryker.com/en/support/) if you have any questions.
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-tells-that-the-port-is-opened.md b/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-tells-that-the-port-is-opened.md
new file mode 100644
index 00000000000..6173012c602
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-tells-that-the-port-is-opened.md
@@ -0,0 +1,27 @@
+---
+title: nc command tells that the port is opened
+description: Learn how to fix the issue when nc command tells that the port is opened
+last_updated: Jun 16, 2021
+template: troubleshooting-guide-template
+originalLink: https://documentation.spryker.com/2021080/docs/nc-command-tells-that-the-port-is-opened
+originalArticleId: 4a169ffc-dd56-4026-b17f-44981617e0fe
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-tells-that-the-port-is-opened.html
+related:
+  - title: nc command does not give any output
+    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-does-not-give-any-output.html
+---
+
+## Description
+
+`nc` command tells that the port is opened.
+
+## Solution
+
+1. Check what process occupies the port 9000 by running the command on the host:
+
+```bash
+sudo lsof -nPi:9000 | grep LISTEN
+```
+
+2. If it's not your IDE, free up the port to be used by the IDE.
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-in-cli.md b/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-in-cli.md
similarity index 58%
rename from docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-in-cli.md
rename to docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-in-cli.md
index 007530df99a..337b46df932 100644
--- a/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-in-cli.md
+++ b/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-in-cli.md
@@ -6,17 +6,8 @@ template: troubleshooting-guide-template
 originalLink: https://documentation.spryker.com/2021080/docs/php-xdebug-extension-is-not-active-in-cli
 originalArticleId: 5fe9a7c8-6e68-4024-952b-ae353d41bce0
 redirect_from:
-  - /2021080/docs/php-xdebug-extension-is-not-active-in-cli
-  - /2021080/docs/en/php-xdebug-extension-is-not-active-in-cli
-  - /docs/php-xdebug-extension-is-not-active-in-cli
-  - /docs/en/php-xdebug-extension-is-not-active-in-cli
-  - /v6/docs/php-xdebug-extension-is-not-active-in-cli
-  - /v6/docs/en/php-xdebug-extension-is-not-active-in-cli
+- /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-in-cli.html
 related:
-  - title: nc command does not give any output
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-does-not-give-any-output.html
-  - title: nc command tells that the port is opened
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-tells-that-the-port-is-opened.html
   - title: PHP `xdebug` extension is not active when accessing the website via a browser or curl
     link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-when-accessing-the-website-via-a-browser-or-curl.html
   - title: Xdebug does not work
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-when-accessing-the-website-via-a-browser-or-curl.md b/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-when-accessing-the-website-via-a-browser-or-curl.md
similarity index 57%
rename from docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-when-accessing-the-website-via-a-browser-or-curl.md
rename to docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-when-accessing-the-website-via-a-browser-or-curl.md
index 1b5d940d11a..8a094352e96 100644
--- a/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-when-accessing-the-website-via-a-browser-or-curl.md
+++ b/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-when-accessing-the-website-via-a-browser-or-curl.md
@@ -6,17 +6,8 @@ template: troubleshooting-guide-template
 originalLink: https://documentation.spryker.com/2021080/docs/php-xdebug-extension-is-not-active-when-accessing-the-website-via-a-browser-or-curl
 originalArticleId: eb4a91fe-ab09-4e6f-a591-f942dea005f5
 redirect_from:
-  - /2021080/docs/php-xdebug-extension-is-not-active-when-accessing-the-website-via-a-browser-or-curl
-  - /2021080/docs/en/php-xdebug-extension-is-not-active-when-accessing-the-website-via-a-browser-or-curl
-  - /docs/php-xdebug-extension-is-not-active-when-accessing-the-website-via-a-browser-or-curl
-  - /docs/en/php-xdebug-extension-is-not-active-when-accessing-the-website-via-a-browser-or-curl
-  - /v6/docs/php-xdebug-extension-is-not-active-when-accessing-the-website-via-a-browser-or-curl
-  - /v6/docs/en/php-xdebug-extension-is-not-active-when-accessing-the-website-via-a-browser-or-curl
+- /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-when-accessing-the-website-via-a-browser-or-curl.html
 related:
-  - title: nc command does not give any output
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-does-not-give-any-output.html
-  - title: nc command tells that the port is opened
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-tells-that-the-port-is-opened.html
   - title: PHP `xdebug` extension is not active in CLI
     link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-in-cli.html
   - title: Xdebug does not work
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/xdebug-does-not-work.md b/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/xdebug-does-not-work.md
new file mode 100644
index 00000000000..7610ff95d0c
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/xdebug-does-not-work.md
@@ -0,0 +1,33 @@
+---
+title: Xdebug does not work
+description: Learn how to fix the issue with a non-working Xdebug
+last_updated: Jun 16, 2021
+template: troubleshooting-guide-template
+originalLink: https://documentation.spryker.com/2021080/docs/xdebug-does-not-work
+originalArticleId: 8169faa4-1c53-4812-bbba-6e34c72cb77c
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/xdebug-does-not-work.html
+---
+
+## Description
+
+Xdebug does not work.
+
+## Solution
+
+1. Ensure that Xdebug is enabled in `deploy.*.yml`:
+
+```yaml
+docker:
+...
+    debug:
+      xdebug:
+        enabled: true
+```
+
+2. Ensure that IDE is listening to the port 9000.
+3. Check if the host is accessible from the container:
+
+```bash
+docker/sdk cli -x bash -c 'nc -zv ${SPRYKER_XDEBUG_HOST_IP} 9000'
+```
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-docker-issues.md b/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-docker-issues.md
new file mode 100644
index 00000000000..17614dc294e
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-docker-issues.md
@@ -0,0 +1,42 @@
+---
+title: Troubleshooting Docker issues
+description: Troubleshoot issues you might encounter when you have your Spryker-based project in Docker.
+last_updated: Jun 16, 2021
+template: troubleshooting-guide-template
+originalLink: https://documentation.spryker.com/2021080/docs/troubleshooting-spryker-in-docker-issues
+originalArticleId: 86164c2a-2a65-4c15-a36e-3f37d4e8c001
+redirect_from:
+  - /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-docker-issues.html
+  - /docs/spryker-in-docker-troubleshooting
+  - /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-spryker-in-docker-issues.html
+---
+
+This section includes guidance for problems related to issues you might encounter with your Spryker-based project in the Docker environment.  
+
+## Topics
+
+Troubleshooting running applications in Docker:
+
+* [Port is already occupied on host](/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/port-is-already-occupied-on-host.html)
+* [413 Request Entity Too Large](/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/413-request-entity-too-large.html)
+* [Nginx welcome page](/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/nginx-welcome-page.html)
+* [An application is not reachable via http](/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/an-application-is-not-reachable-via-http.html)
+* [Mutagen error](/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-error.html)
+* [Mutagen synchronization issue](/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-synchronization-issue.html)
+* [MacOS and Windows: file synchronization issues in Development mode](/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/macos-and-windows-file-synchronization-issues-in-development-mode.html)
+
+Troubleshooting debugging in Docker:
+
+* [Xdebug does not work](/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/xdebug-does-not-work.html)
+* [`nc` command does not give any output](/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-does-not-give-any-output.html)
+* [`nc` command tells that the port is opened](/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-tells-that-the-port-is-opened.html)
+* [PHP `xdebug` extension is not active in CLI](/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-in-cli.html)
+* [PHP `xdebug` extension is not active when accessing the website via a browser or curl](/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-when-accessing-the-website-via-a-browser-or-curl.html)
+
+{% info_block infoBox %}
+
+If you encounter a Spryker in Docker issue that is not addressed on this page, try searching by an error output or keywords, or visit the [Spryker Support Portal](https://spryker.force.com/support/s/) for technical support.
+
+If you found a solution to a repetitive issue, please suggest a change to this page by clicking the **Edit or Report** button.
+
+{% endinfo_block %}
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/413-request-entity-too-large.md b/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/413-request-entity-too-large.md
new file mode 100644
index 00000000000..8526bf0b99b
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/413-request-entity-too-large.md
@@ -0,0 +1,30 @@
+---
+title: 413 Request Entity Too Large
+description: Learn how to fix the issue 413 Request Entity Too Large
+last_updated: Jun 16, 2021
+template: troubleshooting-guide-template
+originalLink: https://documentation.spryker.com/2021080/docs/413-request-entity-too-large
+originalArticleId: 5cfeaaf5-441d-4e75-92c8-215c2db21af5
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/413-request-entity-too-large.html
+
+---
+
+## Description
+
+You get the `413 Request Entity Too Large` error.
+
+## Solution
+
+1. Increase the maximum request body size for the related application. See [Deploy file reference](/docs/dg/dev/sdks/the-docker-sdk/deploy-file/deploy-file-reference.html) to learn how to do that.
+2. Fetch the update:
+
+```bash
+docker/sdk bootstrap
+```
+
+3. Re-build applications:
+
+```bash
+docker/sdk up
+```
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/an-application-is-not-reachable-via-http.md b/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/an-application-is-not-reachable-via-http.md
new file mode 100644
index 00000000000..bc4e0c790e8
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/an-application-is-not-reachable-via-http.md
@@ -0,0 +1,24 @@
+---
+title: An application is not reachable via http
+description: Learn how to fix the issue when an application is not reachable via http
+last_updated: Jun 16, 2021
+template: troubleshooting-guide-template
+originalLink: https://documentation.spryker.com/2021080/docs/an-application-is-not-reachable-via-http
+originalArticleId: 2a96637b-d930-436b-908a-62f9ddbd8298
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/an-application-is-not-reachable-via-http.html
+---
+
+## Description
+
+An application like Yves, BackOffice(Zed), GlueStorefront(Glue), GlueBackend or MerchantPortal is not reachable after installation.
+
+## Solution
+
+In `deploy.*.yml`, ensure that SSL encryption is disabled:
+
+```yaml
+docker:
+    ssl:
+        enabled: false
+```
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/macos-and-windows-file-synchronization-issues-in-development-mode.md b/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/macos-and-windows-file-synchronization-issues-in-development-mode.md
new file mode 100644
index 00000000000..ad25562e313
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/macos-and-windows-file-synchronization-issues-in-development-mode.md
@@ -0,0 +1,26 @@
+---
+title: MacOS and Windows - file synchronization issues in Development mode
+description: Learn how to deal with file synchronization issues in Development mode on MacOS and Windows.
+last_updated: Jun 16, 2021
+template: troubleshooting-guide-template
+originalLink: https://documentation.spryker.com/2021080/docs/macos-and-windows-file-synchronization-issues-in-development-mode
+originalArticleId: 1c53083e-003e-4fda-b23e-3d926adcd08b
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/macos-and-windows-file-synchronization-issues-in-development-mode.html
+---
+
+A project has file synchronization issues in Development mode.
+
+## Solution
+
+1. Follow sync logs:
+
+```bash
+docker/sdk sync logs
+```
+
+2. Hard reset:
+
+```bash
+docker/sdk trouble && rm -rf vendor && rm -rf src/Generated && docker/sdk sync && docker/sdk up
+```
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-error.md b/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-error.md
new file mode 100644
index 00000000000..ea25c56b358
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-error.md
@@ -0,0 +1,23 @@
+---
+title: Mutagen error
+description: Learn how to fix the Mutagen error
+last_updated: Jun 16, 2021
+template: troubleshooting-guide-template
+originalLink: https://documentation.spryker.com/2021080/docs/mutagen-error
+originalArticleId: b1896a64-b124-48a9-9fc5-33c950a620ad
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-error.html
+---
+
+## Description
+
+You get the error:
+
+```bash
+unable to reconcile Mutagen sessions: unable to create synchronization session (spryker-dev-codebase): unable to connect to beta: unable to connect to endpoint: unable to dial agent endpoint: unable to create agent command: unable to probe container: container probing failed under POSIX hypothesis (signal: killed) and Windows hypothesis (signal: killed)
+```
+
+## Solution
+
+1. Restart your OS.
+2. If the error persists: Check [Mutagen documentation](https://mutagen.io/documentation/introduction).
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-synchronization-issue.md b/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-synchronization-issue.md
new file mode 100644
index 00000000000..5c46dc52725
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-synchronization-issue.md
@@ -0,0 +1,26 @@
+---
+title: Mutagen synchronization issue
+description: Learn how to fix the Mutagen synchronization issue
+last_updated: Jun 16, 2021
+template: troubleshooting-guide-template
+originalLink: https://documentation.spryker.com/2021080/docs/mutagen-synchronization-issue
+originalArticleId: c02d26b0-4cfd-4274-8253-c6ff27aa3b3d
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-synchronization-issue.html
+---
+
+## Description
+
+There is a synchronization issue.
+
+## Solution
+
+* Restart your OS.
+* Run the commands:
+
+```
+docker/sdk trouble
+mutagen sync list
+mutagen sync terminate <all sessions in the list>
+docker/sdk up
+```
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/nginx-welcome-page.md b/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/nginx-welcome-page.md
new file mode 100644
index 00000000000..5a21d37e5ab
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/nginx-welcome-page.md
@@ -0,0 +1,25 @@
+---
+title: Nginx welcome page
+description: Learn how to fix the issue when you get Nginx welcome page upon opening an application in browser
+last_updated: Jun 16, 2021
+template: troubleshooting-guide-template
+originalLink: https://documentation.spryker.com/2021080/docs/nginx-welcome-page
+originalArticleId: 27e0d295-8262-41c9-affb-f2339556ef1c
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/nginx-welcome-page.html
+
+---
+
+You get the Nginx welcome page by opening an application in the browser.
+
+1. Update the `nginx:alpine` image:
+
+```bash
+docker pull nginx:alpine
+```
+
+2. Re-build applications:
+
+```bash
+docker/sdk up
+```
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/port-is-already-occupied-on-host.md b/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/port-is-already-occupied-on-host.md
new file mode 100644
index 00000000000..d6d0158eef6
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/port-is-already-occupied-on-host.md
@@ -0,0 +1,29 @@
+---
+title: Port is already occupied on host
+description: Learn how to fix the issue when port is already occupied on host
+last_updated: Jun 16, 2021
+template: troubleshooting-guide-template
+originalLink: https://documentation.spryker.com/2021080/docs/port-is-already-occupied-on-host
+originalArticleId: cf038694-8d04-43cf-adc7-005de29058e2
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/port-is-already-occupied-on-host.html
+---
+
+## Description
+
+Running the `docker/sdk up` console command returns an error similar to the following:
+
+```bash
+ERROR: for nginx_frontend Cannot start service nginx_frontend: driver failed programming external connectivity on endpoint spryker_nginx_frontend_1 (e4fdb360f6c9a3243c0a88fa74f8d377325f65b8cd2340b2dacb51377519c1cf): Error starting userland proxy: Bind for 0.0.0.0:80: unexpected error (Failure EADDRINUSE)
+```
+
+## Solution
+
+1. Check what process occupies the port:
+
+```bash
+sudo lsof -nPi:80 | grep LISTEN
+```
+
+2. Stop the process or make it use a different port.
+3. Run `docker/sdk up` again.
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/a-command-fails-with-a-killed-message.md b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/a-command-fails-with-a-killed-message.md
new file mode 100644
index 00000000000..f9698b83e5e
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/a-command-fails-with-a-killed-message.md
@@ -0,0 +1,43 @@
+---
+title: A command fails with a `Killed` message
+description: Learn how to resolve the issue with a command returning a `killed` message.
+last_updated: Jun 16, 2021
+template: troubleshooting-guide-template
+originalLink: https://documentation.spryker.com/2021080/docs/a-command-fails-with-a-killed-message
+originalArticleId: 09c3dd70-4e87-4604-b5d3-844e49e4c853
+redirect_from:
+  - /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/a-command-fails-with-a-killed-message.html
+---
+
+Running a CLI command with a long execution time returns a `Killed` message.
+
+## Solution
+
+* In PHP settings, increase `max_execution_time`. In Docker based projects, you can do it via a Deploy file as follows:
+
+```yaml
+image:
+  tag: ...
+  php:
+    ini:
+      'max_execution_time': 300
+```
+
+* Increase `PropelConfig` class timeout:
+
+**/b2c/vendor/spryker/propel/src/Spryker/Zed/Propel/PropelConfig.php**
+
+```php
+
+class PropelConfig extends AbstractBundleConfig
+{
+    public const DB_ENGINE_MYSQL = 'mysql';
+    public const DB_ENGINE_PGSQL = 'pgsql';
+
+    protected const PROCESS_TIMEOUT = {process_timeout_value};
+
+    ...
+}
+```
+
+Replace `{process_timeout_value}` with a suitable value. We recommend setting the value that is just enough to run the command. Setting an unreasonably big value may cause performance issue.
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/api-request-fails-with-the-exception-session-has-not-been-set.md b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/api-request-fails-with-the-exception-session-has-not-been-set.md
similarity index 82%
rename from docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/api-request-fails-with-the-exception-session-has-not-been-set.md
rename to docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/api-request-fails-with-the-exception-session-has-not-been-set.md
index 907afba639c..d5d49e1dce0 100644
--- a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/api-request-fails-with-the-exception-session-has-not-been-set.md
+++ b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/api-request-fails-with-the-exception-session-has-not-been-set.md
@@ -3,6 +3,9 @@ title: 'API request fails with the exception: Session has not been set'
 description: Learn how to resolve the issue with an exception that session has not been set.
 last_updated: Jan 24, 2023
 template: troubleshooting-guide-template
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/api-request-fails-with-the-exception-session-has-not-been-set.html
+
 ---
 
 Executing an API command leads to the exception `Session has not been set`.
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/class-silex-controllerproviderinterface-not-found.md b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/class-silex-controllerproviderinterface-not-found.md
new file mode 100644
index 00000000000..5cb6cccf856
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/class-silex-controllerproviderinterface-not-found.md
@@ -0,0 +1,23 @@
+---
+title: Class Silex/ControllerProviderInterface not found
+description: Learn how to fix the issue when class Silex/ControllerProviderInterface is not found
+last_updated: Jun 16, 2021
+template: troubleshooting-guide-template
+originalLink: https://documentation.spryker.com/2021080/docs/class-silexcontrollerproviderinterface-not-found
+originalArticleId: 1ed7e7c7-6975-4cdc-855c-3f5e8006a555
+redirect_from:
+  - /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/class-silex-controllerproviderinterface-not-found.html
+  - /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-front-end.html
+---
+
+## Description
+
+When a project still uses Silex, but modules were updated to the newest versions, where Silex is moved to the require-dev dependency, class `Silex/ControllerProviderInterface` is not found.
+
+## Cause
+
+The current version (1.0.4) of this module uses `SprykerShop\Yves\CheckoutPage\Plugin\Provider\CheckoutPageControllerPlugin`which is no longer functional in the latest Spryker Core.
+
+## Solution
+
+Until a new version of this module is provided, users can work around this issue by overriding `EasycreditController` and using `CheckoutPageRouteProviderPlugin` instead of `CheckoutPageControllerPlugin`. Also, see [Silex replacement](/docs/dg/dev/upgrade-and-migrate/silex-replacement/silex-replacement.html).
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/composer-version-2-compatibility-issues.md b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/composer-version-2-compatibility-issues.md
new file mode 100644
index 00000000000..a4b729c32c6
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/composer-version-2-compatibility-issues.md
@@ -0,0 +1,39 @@
+---
+title: Composer version 2 compatibility issues
+description: Learn how to solve Composer version 2 compatibility issues.
+last_updated: Jun 16, 2021
+template: troubleshooting-guide-template
+originalLink: https://documentation.spryker.com/2021080/docs/composer-version-2-compatibility-issues
+originalArticleId: b110284a-a19f-4c7b-a8fd-769b3dff6ed2
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/composer-version-2-compatibility-issues.html
+---
+
+After running `composer update spryker/{module_name}`, you get an error similar to the following:
+
+```bash
+Problem 1
+- ocramius/package-versions is locked to version 1.4.2 and an update of this package was not requested.
+- ocramius/package-versions 1.4.2 requires composer-plugin-api ^1.0.0 -> found composer-plugin-api[2.0.0] but it does not match the constraint.
+Problem 2
+- sllh/composer-versions-check is locked to version v2.0.3 and an update of this package was not requested.
+- sllh/composer-versions-check v2.0.3 requires composer-plugin-api ^1.0 -> found composer-plugin-api[2.0.0] but it does not match the constraint.
+Problem 3
+- ocramius/package-versions 1.4.2 requires composer-plugin-api ^1.0.0 -> found composer-plugin-api[2.0.0] but it does not match the constraint.
+- jean85/pretty-package-versions 1.2 requires ocramius/package-versions ^1.2.0 -> satisfiable by ocramius/package-versions[1.4.2].
+- jean85/pretty-package-versions is locked to version 1.2 and an update of this package was not requested.
+ocramius/package-versions only provides support for Composer 2 in 1.8+, which requires PHP 7.4.
+If you can not upgrade PHP you can require composer/package-versions-deprecated to resolve this with PHP 7.0+.
+```
+
+## Solution
+
+Run the following commands:
+
+```bash
+composer self-update --2
+composer remove sllh/composer-versions-check --ignore-platform-reqs
+composer require spryker-sdk/phpstan-spryker:^0.3 -W --ignore-platform-reqs
+
+git commit && git push
+```
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/error-remove-spryker-logs-volume-is-in-use.md b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/error-remove-spryker-logs-volume-is-in-use.md
new file mode 100644
index 00000000000..41cc2e7c50a
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/error-remove-spryker-logs-volume-is-in-use.md
@@ -0,0 +1,23 @@
+---
+title: ERROR- remove spryker_logs- volume is in use
+description: The solution to the `ERROR- remove spryker_logs- volume is in use` error.
+last_updated: Jun 16, 2021
+template: troubleshooting-guide-template
+originalLink: https://documentation.spryker.com/2021080/docs/error-remove-spryker-logs-volume-is-in-use
+originalArticleId: 2c841376-da36-4778-8964-306d0088f3d6
+redirect_from:
+  - /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-remove-spryker-logs-volume-is-in-use.html
+  - /v6/docs/en/error-remove-spryker-logs-volume-is-in-use
+---
+
+You get the error `ERROR: remove spryker_logs: volume is in use - [{container_hash}]`
+
+## Solution
+
+1. Run the command:
+
+```
+docker rm -f {container_hash}
+```
+
+2. Repeat the failed command.
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown.md b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown.md
new file mode 100644
index 00000000000..4b5c2cef535
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown.md
@@ -0,0 +1,16 @@
+---
+title: Error response from daemon- OCI runtime create failed- .... \\\"no such file or directory\\\"\""- unknown
+description: The solution to the `Error response from daemon- OCI runtime create failed- .... no such file or directory - unknown.` error
+last_updated: Jun 16, 2021
+template: troubleshooting-guide-template
+originalLink: https://documentation.spryker.com/2021080/docs/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown
+originalArticleId: e06c6e8d-1edd-4227-8c9c-a18395175f74
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown.html
+---
+
+You get the error `Error response from daemon: OCI runtime create failed: .... \\\"no such file or directory\\\"\"": unknown.`.
+
+## Solution
+
+Repeat the failed command.
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-frontend.md b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-frontend.md
new file mode 100644
index 00000000000..148da5582a8
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-frontend.md
@@ -0,0 +1,24 @@
+---
+title: Fail whale on the frontend
+description: The solution for the fail whale on the front end.
+last_updated: Jun 16, 2021
+template: troubleshooting-guide-template
+originalLink: https://documentation.spryker.com/2021080/docs/fail-whale-on-the-front-end
+originalArticleId: bf2d7e12-feee-4369-a291-72d4fc5ed562
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-frontend.html
+---
+
+A fail whale is displayed on the front end.
+
+## Solution
+
+1. Run the command:
+
+```bash
+docker/sdk logs
+```
+
+2. Add several returns to mark the line you started from.
+3. Open the page with the error.
+4. Check the logs.
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/no-data-on-the-storefront.md b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/no-data-on-the-storefront.md
new file mode 100644
index 00000000000..1029a1f9f3a
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/no-data-on-the-storefront.md
@@ -0,0 +1,19 @@
+---
+title: No data on the Storefront
+description: The solution to the data being absent on the Storefront.
+last_updated: Jun 16, 2021
+template: troubleshooting-guide-template
+originalLink: https://documentation.spryker.com/2021080/docs/no-data-on-the-storefront
+originalArticleId: 5edf4ea6-b0e3-4284-90f3-a5ad06a30f58
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/no-data-on-the-storefront.html
+---
+
+There is no data on the Storefront.
+
+## Solution
+
+Use the following services to check the status of queues and jobs:
+
+* `https://queue.mysprykershop.com`
+* `https://scheduler.mysprykershop.com`
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/phpstan-memory-issues.md b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/phpstan-memory-issues.md
new file mode 100644
index 00000000000..ae022e9d5ae
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/phpstan-memory-issues.md
@@ -0,0 +1,17 @@
+---
+title: PHPStan memory issues
+last_updated: Jun 16, 2021
+template: troubleshooting-guide-template
+originalLink: https://documentation.spryker.com/2021080/docs/phpstan-memory-issues
+originalArticleId: c234b12e-5260-4f86-97b4-44c7ef5c8dbf
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/phpstan-memory-issues.html
+---
+
+## Cause
+
+PHPStan needs to parse all files and due to Spryker's magic with resolving classes, e.g., `$this->getFacade()`, PHPStan needs to look up this class on its own when the `@method` annotation is missing.
+
+## Solution
+
+Run PHPStan in debug mode `--debug` on the module where it needs too much memory. In the debug mode, PHPStan will display the file name currently being analyzed. If PHPStan gets stuck at a specific file, look into this file and check if all `@method` annotations are present.
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/prices-filter-and-sorting-does-t-work-on-frontend.md b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/prices-filter-and-sorting-does-t-work-on-frontend.md
similarity index 100%
rename from docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/prices-filter-and-sorting-does-t-work-on-frontend.md
rename to docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/prices-filter-and-sorting-does-t-work-on-frontend.md
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/processtimedoutexception-after-queue-task-start.md b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/processtimedoutexception-after-queue-task-start.md
new file mode 100644
index 00000000000..fcf25f46c05
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/processtimedoutexception-after-queue-task-start.md
@@ -0,0 +1,34 @@
+---
+title: ProcessTimedOutException after queue-task-start
+description: Learn how to fix the exception after running queue-task-start
+last_updated: Jun 16, 2021
+template: troubleshooting-guide-template
+originalLink: https://documentation.spryker.com/2021080/docs/processtimedoutexception-after-queuetaskstart
+originalArticleId: e480ba5c-9f2c-49ff-b238-1e907b2c61ce
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/processtimedoutexception-after-queue-task-start.html
+---
+
+## Description
+After running `queue:task:start`, the following exception is thrown:
+
+```bash
+Symphony\Component\Process\Exception\ProcesstimedOutException - Exception: The process "/app/vendor/bin/console queue:task:start event" exeeded the timeout of 60 seconds in /app/vendor/symfony/process/Process.php (1335)
+```
+
+## Cause
+
+The problem occurs when the task runs for longer than the max execution time specified in the PHP settings.
+
+## Solution
+
+In the PHP settings, increase `max_execution_time`.
+If you use Docker, you can increase the max execution time in the *deploy.yml* file, for example:
+
+```yaml
+image:
+  tag: ...
+  php:
+    ini:
+      'max_execution_time': 300
+```
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/router-generates-absolute-url-with-localhost.md b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/router-generates-absolute-url-with-localhost.md
new file mode 100644
index 00000000000..b7f88cf938d
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/router-generates-absolute-url-with-localhost.md
@@ -0,0 +1,60 @@
+---
+title: Router generates absolute URL with localhost
+description: Learn how to fix the issue when router generates URLs with an absolute path instead of a relative one
+last_updated: Jun 16, 2021
+template: troubleshooting-guide-template
+originalLink: https://documentation.spryker.com/2021080/docs/router-generates-absolute-url-with-localhost
+originalArticleId: d9195e61-e421-4623-88bf-343a48b2d707
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/router-generates-absolute-url-with-localhost.html
+---
+
+Router generates URLs with an absolute path instead of a relative one.
+
+## Cause
+
+Prior to version 1.9.0 of the [Router](https://github.com/spryker/router) module, Spryker did not set the `RequestContext` properly in `ChainRouter`. This led to an issue that URLs were generated with an absolute path instead of a relative one. This silently happens inside Symfony's router when the host retrieved from `RequestContext` doesn't match the one that the resolved route has.
+
+## Solution
+
+Do the following:
+
+1. Update the [Router](https://github.com/spryker/router) module to at least version 1.9.0.
+2. Set `RequestContext` as follows: Extend `\Spryker\Yves\Router\Router\ChainRouter` in your project, add a new `addRequestContext()` method to it and call that method in the constructor of that class.
+
+```php
+/**
+ * @param \Symfony\Component\Routing\RequestContext|null $requestContext
+ *
+ * @return void
+ */
+protected function addRequestContext(?RequestContext $requestContext = null): void
+{
+    $request = Request::createFromGlobals();
+
+    if (!$requestContext) {
+        $requestContext = new RequestContext();
+    }
+    $requestContext->fromRequest($request);
+
+    $this->setContext($requestContext);
+}
+
+```
+
+3. Update the constructor:
+
+```php
+/**
+ * @param \Spryker\Yves\RouterExtension\Dependency\Plugin\RouterPluginInterface[] $routerPlugins
+ * @param \Psr\Log\LoggerInterface|null $logger
+ * @param \Symfony\Component\Routing\RequestContext|null $requestContext
+ */
+public function __construct(array $routerPlugins, ?LoggerInterface $logger = null, ?RequestContext $requestContext = null)
+{
+    parent::__construct($logger);
+
+    $this->addRequestContext($requestContext);
+    $this->addRouterPlugins($routerPlugins);
+}
+```
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error.md b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error.md
new file mode 100644
index 00000000000..ad09ca73f4d
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error.md
@@ -0,0 +1,35 @@
+---
+title: RuntimeException- Failed to execute regex- PREG_JIT_STACKLIMIT_ERROR
+description: This troubleshooting guide will help you to fix the error `RuntimeException- Failed to execute regex- PREG_JIT_STACKLIMIT_ERROR`.
+last_updated: Jun 16, 2021
+template: troubleshooting-guide-template
+originalLink: https://documentation.spryker.com/2021080/docs/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error
+originalArticleId: 53d95154-60db-40db-b4b8-6e0c4ae9233b
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error.html
+---
+
+## Description
+```bash
+[RuntimeException]                                  
+Failed to execute regex: PREG_JIT_STACKLIMIT_ERROR
+```
+
+This error is received when using composer (`composer require`) to add additional modules.
+
+## Cause
+The error is thrown if the [backtracking/recursion limit](https://www.php.net/manual/en/pcre.configuration.php) is not high enough.
+
+## Solution
+Either increase the limits to your requirements or switch off PCRE's just-in-time compilation in your php.ini:
+```bash
+pcre.jit=0
+```
+You can also switch off PCRE just in time compilation using your `deploy.yml`.
+```bash
+image:
+  tag: ...
+  php:
+    ini:
+      'pcre.jit': 0
+```
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/the-spy-oms-transition-log-table-takes-up-too-much-space.md b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/the-spy-oms-transition-log-table-takes-up-too-much-space.md
new file mode 100644
index 00000000000..9f6af344636
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/the-spy-oms-transition-log-table-takes-up-too-much-space.md
@@ -0,0 +1,33 @@
+---
+title: The spy_oms_transition_log table takes up too much space
+description: Configure transition logs to be removed automatically.
+last_updated: Jun 16, 2021
+template: troubleshooting-guide-template
+originalLink: https://documentation.spryker.com/2021080/docs/the-spy-oms-transition-log-table-takes-up-too-much-space
+originalArticleId: 5c025e16-bfc2-4dcf-ba35-137044daa486
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/the-spy-oms-transition-log-table-takes-up-too-much-space.html
+---
+
+The `spy_oms_transition_log` table stores the history of order management system transitions. The logs are kept for debugging reasons. If you don't need them or you have backed them up, you can remove them.
+
+{% info_block errorBox "Manipulating tables" %}
+
+Table manipulations can affect a shop greatly. It is not safe to do so, and we recommend double-checking all the details before you proceed. The instructions below can help you solve a storage space issue. Make sure to follow them exactly.
+
+{% endinfo_block %}
+
+## Cause
+
+By default, nothing limits the table size or deletes old records.
+
+## Solution
+
+Schedule the following SQL query to delete all the logs older than 90 days. You can adjust the time interval per your requirements.
+
+```sql
+DELETE FROM
+	spy_oms_transition_log
+WHERE
+	created_at < CURRENT_DATE - interval '90' day;
+```
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-general-technical-issues.md b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-general-technical-issues.md
new file mode 100644
index 00000000000..60b17d447b5
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-general-technical-issues.md
@@ -0,0 +1,39 @@
+---
+title: Troubleshooting general technical issues
+description: Troubleshoot general technical issues you might encounter when running your Spryker-based project
+last_updated: Jun 16, 2021
+template: troubleshooting-guide-template
+originalLink: https://documentation.spryker.com/2021080/docs/troubleshooting-general-technical-issues
+originalArticleId: b625da8e-d503-4450-90d2-ff1297d3a809
+redirect_from:
+  - /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-general-technical-issues.html
+  - /docs/general-troubleshooting
+---
+
+This section helps you troubleshoot general technical issues you might encounter when running your Spryker-based project.
+
+## Topics
+
+* [A command fails with a `Killed` message](/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/a-command-fails-with-a-killed-message.html)
+* [Class Silex/ControllerProviderInterface not found](/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/class-silex-controllerproviderinterface-not-found.html)
+* [Unable to resolve hosts for Mail, Jenkins, and RabbitMQ](/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq.html)
+* [RabbitMQ: Zed.CRITICAL: PhpAmqpLib\Exception\AMQPChannelClosedException - Channel connection is closed](/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.html)
+* [ProcessTimedOutException after queue:task:start](/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/processtimedoutexception-after-queue-task-start.html)
+* [RuntimeException: Failed to execute regex: PREG_JIT_STACKLIMIT_ERROR](/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error.html)
+* [The spy_oms_transition_log table takes up too much space](/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/the-spy-oms-transition-log-table-takes-up-too-much-space.html)
+* [ERROR: remove spryker_logs: volume is in use](/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/error-remove-spryker-logs-volume-is-in-use.html)
+* [Fail whale on the front end](/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-frontend.html)
+* [No data on the Storefront](/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/no-data-on-the-storefront.html)
+* [Error response from daemon: OCI runtime create failed: .... \\\"no such file or directory\\\"\"": unknown](/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown.html)
+* [Composer version 2 compatibility issues](/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/composer-version-2-compatibility-issues.html)
+* [Router generates absolute URL with localhost](/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/router-generates-absolute-url-with-localhost.html)
+* [PHPStan memory issues](/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/phpstan-memory-issues.html)
+
+
+{% info_block infoBox %}
+
+If you encounter a general technical issue that is not addressed on this page, try searching by an error output or keywords, or visit the [Spryker Support Portal](https://spryker.force.com/support/s/) for technical support.
+
+If you found a solution to a repetitive issue, please suggest a change to this page by clicking the **Edit or Report** button.
+
+{% endinfo_block %}
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-moved-to-error-queues.md b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-moved-to-error-queues.md
similarity index 94%
rename from docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-moved-to-error-queues.md
rename to docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-moved-to-error-queues.md
index 4e0477ea02b..cc896b6b5dc 100644
--- a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-moved-to-error-queues.md
+++ b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-moved-to-error-queues.md
@@ -3,6 +3,9 @@ title: Messages are moved to error queues
 description: This troubleshooting guide describes how to approach diagnosing why messages are moved to error queues in RabbitMQ
 last_updated: Oct 31, 2022
 template: troubleshooting-guide-template
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-moved-to-error-queues.html
+
 related:
   - title: Messages are stuck in the Unacked state
     link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-stuck-in-the-unacked-state.html
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-stuck-in-the-unacked-state.md b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-stuck-in-the-unacked-state.md
similarity index 93%
rename from docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-stuck-in-the-unacked-state.md
rename to docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-stuck-in-the-unacked-state.md
index b4fc2959d1c..8cdb5027c8d 100644
--- a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-stuck-in-the-unacked-state.md
+++ b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-stuck-in-the-unacked-state.md
@@ -3,6 +3,9 @@ title: Messages are stuck in the Unacked state
 description: This troubleshooting guide suggests solution strategies for messages that get stuck in the unacked status
 last_updated: Oct 31, 2022
 template: troubleshooting-guide-template
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-stuck-in-the-unacked-state.html
+
 related:
   - title: Messages are moved to error queues
     link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-moved-to-error-queues.html
@@ -27,12 +30,12 @@ $config[EventConstants::EVENT_CHUNK]
 ```
 
 Try to reduce it drastically—for example, reduce to 100 and redeploy.
-Then, you can move back the stuck messages from `Unacked` to the `ready` state so that the consumers can try to consume them again by force closing the connections as the following example shows. 
+Then, you can move back the stuck messages from `Unacked` to the `ready` state so that the consumers can try to consume them again by force closing the connections as the following example shows.
 
 ![Force Close RabbitMQ Connections](https://spryker.s3.eu-central-1.amazonaws.com/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/rabbitmq_troubleshooting_force_close_connection.gif)
 
 Once the queue worker process runs, the messages are attempted to be consumed again.
 
-If the messages are still not consumable, try to reproduce this behavior locally by dumping your database and publishing the messages in your local development environment as explained in [HowTo: Do better deployments](https://docs.spryker.com/docs/scos/dev/tutorials-and-howtos/howtos/howto-do-better-deployments.html#ingest-staging-or-production-data). 
+If the messages are still not consumable, try to reproduce this behavior locally by dumping your database and publishing the messages in your local development environment as explained in [HowTo: Do better deployments](https://docs.spryker.com/docs/scos/dev/tutorials-and-howtos/howtos/howto-do-better-deployments.html#ingest-staging-or-production-data).
 
 If the messages are consumed in your local environment without a problem, get in touch with our [support](https://docs.spryker.com/docs/scos/user/intro-to-spryker/support/how-to-contact-spryker-support.html) and include the information that you have tested the consumption locally.
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-stuck-without-error-notifications.md b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-stuck-without-error-notifications.md
similarity index 94%
rename from docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-stuck-without-error-notifications.md
rename to docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-stuck-without-error-notifications.md
index b6b6b2411a4..6951ed9da4d 100644
--- a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-stuck-without-error-notifications.md
+++ b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-stuck-without-error-notifications.md
@@ -3,6 +3,9 @@ title: Messages are stuck without error notifications
 description: This troubleshooting guide describes how to deal with messages that get stuck in queues without visible error notifications
 last_updated: Oct 31, 2022
 template: troubleshooting-guide-template
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-stuck-without-error-notifications.html
+
 related:
   - title: Messages are moved to error queues
     link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-moved-to-error-queues.html
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.md b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.md
new file mode 100644
index 00000000000..c4ef503c5a5
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.md
@@ -0,0 +1,34 @@
+---
+title: RabbitMQ- Zed.CRITICAL- PhpAmqpLib\Exception\AMQPChannelClosedException - Channel connection is closed
+description: Learn how to fix the issue when events are not consumed or are consumed slowly.
+last_updated: May 3, 2023
+template: troubleshooting-guide-template
+originalLink: https://documentation.spryker.com/2021080/docs/rabbitmq-zedcritical-phpamqplibexceptionamqpchannelclosedexception-channel-connection-is-closed
+originalArticleId: 39daf8b8-9e73-4c76-a6ee-372d3e5bbca6
+redirect_from:
+  - /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.html
+---
+
+## Description
+
+Events are not consumed or are consumed much slower than normal. In RabbitMQ exception.log, the following exception can be found (often also with Broken Pipe reference):
+
+```php
+Zed.CRITICAL: PhpAmqpLib\Exception\AMQPChannelClosedException - Channel connection is closed.
+```
+
+## Cause
+
+There are several potential reasons for this error. The most common cause is that during P&S chunks take too much time to be processed and RabbitMQ is closing its TCP connection as it anticipates either a timeout or no further connection to happen.
+
+## Solution
+
+It is best to profile the job where you are experiencing this error to understand what exactly makes processing the chunks expensive. Temporary mitigation of the issue might be possible as explained below:
+
+**Adjusting CHUNK_SIZE**
+
+Using smaller chunk sizes might help to alleviate the issue because it reduces the time until a chunk is fully processed. If you are running a standard publishing setup, you can adjust the following value in `config_default.php`.
+
+```php
+$config[EventConstants::EVENT_CHUNK] = 200;
+```
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/troubleshooting-rabbitmq.md b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/troubleshooting-rabbitmq.md
new file mode 100644
index 00000000000..380f18fec7b
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/troubleshooting-rabbitmq.md
@@ -0,0 +1,16 @@
+---
+title: Troubleshooting RabbitMQ
+description: Troubleshoot RabbitMQ issues
+template: concept-topic-template
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/troubleshooting-rabbitmq.html
+
+last_updated: May 2, 2023
+---
+
+This section helps you troubleshoot issues related to RabbitMQ.
+
+## Topics
+- [Messages are moved to error queues](/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-moved-to-error-queues.html)
+- [Messages are stuck in the Unacked state](/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-stuck-in-the-unacked-state.html)
+- [Messages are stuck without error notifications](/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-stuck-without-error-notifications.html)
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq.md b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq.md
new file mode 100644
index 00000000000..3f2f5a8af47
--- /dev/null
+++ b/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq.md
@@ -0,0 +1,22 @@
+---
+title: Unable to resolve hosts for Mail, Jenkins, and RabbitMQ
+description: Learn how to fix the issue with unresolved hosts for Mail, Jenkins, and RabbitMQ on Windows
+last_updated: Jun 16, 2021
+template: troubleshooting-guide-template
+originalLink: https://documentation.spryker.com/2021080/docs/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq
+originalArticleId: bbddc907-8edc-4e0f-b880-b67381364801
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq.html
+---
+
+## Description
+
+The issue occurs when setting up Docker and WSL 2 and adding routes to `etc/hosts` in one line on Windows. Host file has row 127.0.0.1.
+
+## Cause
+
+The cause of the issue might be in the maximum length limitaion of a line that you can have in your hosts file in Windows.
+
+## Solution
+
+In the hosts file, start a new line with `127.0.0.1`, and then add routes for services for which the hosts are not resolved.
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-performance-issues/external-calls-several-calls-to-zed.md b/docs/dg/dev/troubleshooting/troubleshooting-performance-issues/external-calls-several-calls-to-zed.md
similarity index 85%
rename from docs/scos/dev/troubleshooting/troubleshooting-performance-issues/external-calls-several-calls-to-zed.md
rename to docs/dg/dev/troubleshooting/troubleshooting-performance-issues/external-calls-several-calls-to-zed.md
index 16e995952a1..f54a8a42e7b 100644
--- a/docs/scos/dev/troubleshooting/troubleshooting-performance-issues/external-calls-several-calls-to-zed.md
+++ b/docs/dg/dev/troubleshooting/troubleshooting-performance-issues/external-calls-several-calls-to-zed.md
@@ -2,6 +2,9 @@
 title: External calls—several calls to Zed
 description: Troubleshoot the performance issue with several external calls to Zed
 template: troubleshooting-guide-template
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-performance-issues/external-calls-several-calls-to-zed.html
+
 last_updated: Mar 1, 2023
 ---
 
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-performance-issues/external-calls-take-a-lot-of-time.md b/docs/dg/dev/troubleshooting/troubleshooting-performance-issues/external-calls-take-a-lot-of-time.md
similarity index 79%
rename from docs/scos/dev/troubleshooting/troubleshooting-performance-issues/external-calls-take-a-lot-of-time.md
rename to docs/dg/dev/troubleshooting/troubleshooting-performance-issues/external-calls-take-a-lot-of-time.md
index 69293317f0f..4e3b61bae9f 100644
--- a/docs/scos/dev/troubleshooting/troubleshooting-performance-issues/external-calls-take-a-lot-of-time.md
+++ b/docs/dg/dev/troubleshooting/troubleshooting-performance-issues/external-calls-take-a-lot-of-time.md
@@ -2,6 +2,9 @@
 title: External calls take a lot of time
 description: Troubleshoot the performance issue with external calls taking much time
 template: troubleshooting-guide-template
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-performance-issues/external-calls-take-a-lot-of-time.html
+
 last_updated: Feb 27, 2023
 ---
 
@@ -21,8 +24,8 @@ Blackfire:
 
 ## Solution
 
-1. Make sure there is no [N+1 problem](/docs/scos/dev/troubleshooting/troubleshooting-performance-issues/n+1-problem.html).
+1. Make sure there is no [N+1 problem](/docs/dg/dev/troubleshooting/troubleshooting-performance-issues/n+1-problem.html).
 2. Check if this issue really causes a performance problem. For example, sometimes, during the checkout, customers have to wait until some call to a 3rd party system is done.
 3. Check if this call can be done before or after this action in the background. Is it acceptable for business?
 If yes—move it.
-If no—confirm the behavior with the business stakeholders or contact the 3rd party system to optimize the request. 
+If no—confirm the behavior with the business stakeholders or contact the 3rd party system to optimize the request.
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-performance-issues/n+1-problem.md b/docs/dg/dev/troubleshooting/troubleshooting-performance-issues/n+1-problem.md
similarity index 96%
rename from docs/scos/dev/troubleshooting/troubleshooting-performance-issues/n+1-problem.md
rename to docs/dg/dev/troubleshooting/troubleshooting-performance-issues/n+1-problem.md
index d2a9673df97..535de174f2a 100644
--- a/docs/scos/dev/troubleshooting/troubleshooting-performance-issues/n+1-problem.md
+++ b/docs/dg/dev/troubleshooting/troubleshooting-performance-issues/n+1-problem.md
@@ -2,6 +2,9 @@
 title: N+1 problem
 description: N+1 problem
 template: troubleshooting-guide-template
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-performance-issues/n+1-problem.html
+
 last_updated: Mar 7, 2023
 keywords: n1; n one
 ---
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-performance-issues/not-optimised-composer-on-the-production-environment.md b/docs/dg/dev/troubleshooting/troubleshooting-performance-issues/not-optimised-composer-on-the-production-environment.md
similarity index 93%
rename from docs/scos/dev/troubleshooting/troubleshooting-performance-issues/not-optimised-composer-on-the-production-environment.md
rename to docs/dg/dev/troubleshooting/troubleshooting-performance-issues/not-optimised-composer-on-the-production-environment.md
index 152391177b1..36faf18bf51 100644
--- a/docs/scos/dev/troubleshooting/troubleshooting-performance-issues/not-optimised-composer-on-the-production-environment.md
+++ b/docs/dg/dev/troubleshooting/troubleshooting-performance-issues/not-optimised-composer-on-the-production-environment.md
@@ -2,6 +2,9 @@
 title: Not optimized Composer on the production environment
 description: Fix the issue when all pages are slow on the production environment
 template: troubleshooting-guide-template
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-performance-issues/not-optimised-composer-on-the-production-environment.html
+
 last_updated: Mar 1, 2023
 ---
 
@@ -9,7 +12,7 @@ All pages are slow on the production environment.
 
 ## Cause
 
-The possible cause can be an unoptimized Composer for the production environment. 
+The possible cause can be an unoptimized Composer for the production environment.
 
 Here is an example of a profile from [Blackfire](/docs/dg/dev/integrate-and-configure/configure-services.html#blackfire):
 
@@ -23,13 +26,13 @@ Optimize the Composer autoloader. Follow the [general performance guidelines](/d
 
 For example, you can run the `dump-autoload` command with `-o ` or `--optimize`.
 
-After running the command defined in the guidelines, the profile can look like this: 
+After running the command defined in the guidelines, the profile can look like this:
 
 ![profile-after-command](https://spryker.s3.eu-central-1.amazonaws.com/docs/scos/dev/troubleshooting/troubleshooting-performance-issues/not-optimised-composer-on-the-production-environment/profile-after-command.png)
 
 As you can see, the two most time-consuming points are gone.
 
-The comparison view looks like this: 
+The comparison view looks like this:
 
 ![comparison-view](https://spryker.s3.eu-central-1.amazonaws.com/docs/scos/dev/troubleshooting/troubleshooting-performance-issues/not-optimised-composer-on-the-production-environment/comparison-view.png)
 
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-performance-issues/redis-session-lock.md b/docs/dg/dev/troubleshooting/troubleshooting-performance-issues/redis-session-lock.md
similarity index 87%
rename from docs/scos/dev/troubleshooting/troubleshooting-performance-issues/redis-session-lock.md
rename to docs/dg/dev/troubleshooting/troubleshooting-performance-issues/redis-session-lock.md
index fa9e2a19b52..d9dbe78ab32 100644
--- a/docs/scos/dev/troubleshooting/troubleshooting-performance-issues/redis-session-lock.md
+++ b/docs/dg/dev/troubleshooting/troubleshooting-performance-issues/redis-session-lock.md
@@ -2,6 +2,9 @@
 title: Redis session lock
 description: Redis Session Lock
 template: troubleshooting-guide-template
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-performance-issues/redis-session-lock.html
+
 last_updated: Feb 23, 2023
 ---
 
@@ -17,4 +20,4 @@ An example of a pessimistic Redis session Lock in the New Relic report:
 
 ## Solution
 
-Follow the approaches from the [architecture performance guidelines](/docs/dg/dev/guidelines/performance-guidelines/architecture-performance-guidelines.html#optimistic-vs-pessimistic-locking).
\ No newline at end of file
+Follow the approaches from the [architecture performance guidelines](/docs/dg/dev/guidelines/performance-guidelines/architecture-performance-guidelines.html#optimistic-vs-pessimistic-locking).
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-performance-issues/slow-publish-and-synchronization.md b/docs/dg/dev/troubleshooting/troubleshooting-performance-issues/slow-publish-and-synchronization.md
similarity index 88%
rename from docs/scos/dev/troubleshooting/troubleshooting-performance-issues/slow-publish-and-synchronization.md
rename to docs/dg/dev/troubleshooting/troubleshooting-performance-issues/slow-publish-and-synchronization.md
index b8ea8a97e2b..47d8f11f457 100644
--- a/docs/scos/dev/troubleshooting/troubleshooting-performance-issues/slow-publish-and-synchronization.md
+++ b/docs/dg/dev/troubleshooting/troubleshooting-performance-issues/slow-publish-and-synchronization.md
@@ -5,6 +5,8 @@ template: troubleshooting-guide-template
 last_updated: Feb 23, 2023
 redirect_from:
     - /docs/scos/dev/troubleshooting/troubleshooting-performance-issues/slow-p-and-s.html
+    - /docs/scos/dev/troubleshooting/troubleshooting-performance-issues/slow-publish-and-synchronization.html
+
 related:
     - title: Troubleshooting RabbitMQ
       link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/troubleshooting-rabbitmq.html
@@ -30,4 +32,4 @@ The Publish action, in this case, can look like this:
 
 ![publish-action](https://spryker.s3.eu-central-1.amazonaws.com/docs/scos/dev/troubleshooting/troubleshooting-performance-issues/slow-p-and-s/publish-action.png)
 
-2. Check and disable messages that are not used on the project.
\ No newline at end of file
+2. Check and disable messages that are not used on the project.
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-performance-issues/technology-restrictions.md b/docs/dg/dev/troubleshooting/troubleshooting-performance-issues/technology-restrictions.md
similarity index 89%
rename from docs/scos/dev/troubleshooting/troubleshooting-performance-issues/technology-restrictions.md
rename to docs/dg/dev/troubleshooting/troubleshooting-performance-issues/technology-restrictions.md
index e4b4dd3c830..efc5ee95956 100644
--- a/docs/scos/dev/troubleshooting/troubleshooting-performance-issues/technology-restrictions.md
+++ b/docs/dg/dev/troubleshooting/troubleshooting-performance-issues/technology-restrictions.md
@@ -2,6 +2,9 @@
 title: Technology restrictions
 description: Fix the issue with slow actions, parts of the website, or the entire webiste related to technology restrictions.
 template: troubleshooting-guide-template
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-performance-issues/technology-restrictions.html
+
 last_updated: Mar 1, 2023
 ---
 
@@ -15,13 +18,13 @@ A possible cause is technology restriction.
 
 Before using some technology, you need to understand all its advantages and disadvantages.
 
-A good example is Redis. It is fast, but if used incorrectly, it can lead to performance degradation. If we search against `*` or `Wildkey` in Redis with a large DB, we get the following results: 
+A good example is Redis. It is fast, but if used incorrectly, it can lead to performance degradation. If we search against `*` or `Wildkey` in Redis with a large DB, we get the following results:
 
-NewRelic—DB: 
+NewRelic—DB:
 
 ![new-relic-db](https://spryker.s3.eu-central-1.amazonaws.com/docs/scos/dev/troubleshooting/troubleshooting-performance-issues/technology-restrictions/new-relic-db.png)
 
-NewRelic—Breakdown: 
+NewRelic—Breakdown:
 
 ![new-relic-breakdown](https://spryker.s3.eu-central-1.amazonaws.com/docs/scos/dev/troubleshooting/troubleshooting-performance-issues/technology-restrictions/new-relic-breakdown.png)
 
@@ -32,5 +35,3 @@ In the code, this would look similar to this line:
 ```php
 $this->storageClient->getKeys(self::RESOURCE . ':*');
 ```
-
-
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-performance-issues/troubleshooting-performance-issues.md b/docs/dg/dev/troubleshooting/troubleshooting-performance-issues/troubleshooting-performance-issues.md
similarity index 98%
rename from docs/scos/dev/troubleshooting/troubleshooting-performance-issues/troubleshooting-performance-issues.md
rename to docs/dg/dev/troubleshooting/troubleshooting-performance-issues/troubleshooting-performance-issues.md
index f3ff2f84100..ac35f40126f 100644
--- a/docs/scos/dev/troubleshooting/troubleshooting-performance-issues/troubleshooting-performance-issues.md
+++ b/docs/dg/dev/troubleshooting/troubleshooting-performance-issues/troubleshooting-performance-issues.md
@@ -2,6 +2,9 @@
 title: Troubleshooting performance issues
 description: Learn how you can troubleshoot the most common performance issues
 template: concept-topic-template
+redirect_from:
+- /docs/scos/dev/troubleshooting/troubleshooting-performance-issues/troubleshooting-performance-issues.html
+
 last_updated: Feb 22, 2023
 related:
   - title: Performance guidelines
diff --git a/docs/scos/dev/troubleshooting/troubleshooting.md b/docs/dg/dev/troubleshooting/troubleshooting.md
similarity index 91%
rename from docs/scos/dev/troubleshooting/troubleshooting.md
rename to docs/dg/dev/troubleshooting/troubleshooting.md
index 250a10b28a4..bcf63dc8f30 100644
--- a/docs/scos/dev/troubleshooting/troubleshooting.md
+++ b/docs/dg/dev/troubleshooting/troubleshooting.md
@@ -23,12 +23,14 @@ redirect_from:
     - /docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/databases-and-services-issues/exception-connecting-to-redis.html
     - /docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/databases-and-services-issues/peer-authentication-failed-for-user-postgres.html
     - /docs/scos/dev/troubleshooting/troubleshooting-spryker-in-vagrant-issues/databases-and-services-issues/my-elasticsearch-dies.html
+    - /docs/scos/dev/troubleshooting/troubleshooting.html
+
 ---
 
 This section gives answers to common troubleshooting questions and includes the following topics:
 
-* [Troubleshooting general technical issues](/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-general-technical-issues.html)
-* [Troubleshooting Docker issues](/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-docker-issues.html)
+* [Troubleshooting general technical issues](/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-general-technical-issues.html)
+* [Troubleshooting Docker issues](/docs/dg/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-docker-issues.html)
 
 If you can not find answer to your questions and require technical support, you can create a Support ticket via our [Support portal](https://spryker.force.com/support/s/). If your case is not an emergency, check the following articles to understand how the Spryker support works and how the support requests are processed:
 
diff --git a/docs/dg/dev/updating-spryker/analyzing-and-upgrading-projects-with-spryker-jarvis.md b/docs/dg/dev/updating-spryker/analyzing-and-upgrading-projects-with-spryker-jarvis.md
index c65f044e20c..7e64ae53f14 100644
--- a/docs/dg/dev/updating-spryker/analyzing-and-upgrading-projects-with-spryker-jarvis.md
+++ b/docs/dg/dev/updating-spryker/analyzing-and-upgrading-projects-with-spryker-jarvis.md
@@ -33,7 +33,7 @@ This document shows how to install and use the Spryker Jarvis tool for the analy
 
 ## Prerequisites
 
-* [Install Spryker project locally](/docs/scos/dev/developer-getting-started-guide.html#install-spryker)
+* [Install Spryker project locally](/docs/dg/dev/development-getting-started-guide.html#install-spryker)
 * [Install Node.js](https://nodejs.org/en/download)
 
 ## Install Spryker Jarvis
diff --git a/docs/scos/dev/developer-getting-started-guide.md b/docs/scos/dev/developer-getting-started-guide.md
deleted file mode 100644
index 55a5c9e503c..00000000000
--- a/docs/scos/dev/developer-getting-started-guide.md
+++ /dev/null
@@ -1,215 +0,0 @@
----
-title: Developer getting started guide
-description: This is a step-by-step checklist that you can follow through all the stages of working with Spryker.
-last_updated: July 11, 2022
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/dev-getting-started
-originalArticleId: 79b50d48-6f09-45b0-9e4a-f372e274d462
-redirect_from:
-  - /docs/scos/dev/module-migration-guides/about-migration-guides.html
-  - /docs/pbc/all/punchout/202307.0/punchout-catalogs-overview.html
----
-
-This document guides you into getting started with the Spryker Cloud Commerce OS. It has been structured as a step-by-step checklist to help get you through all of the stages involved in working with Spryker. After following these instructions, if you still have any questions, you can access the Spryker community at [CommerceQuest](https://commercequest.space/).
-
-## 1. Install Spryker
-
-For the starting point of any project, it is good to start from one of the Spryker Demo Shops that are available. They act as a typical Spryker installation and help to establish different types of the Spryker Commerce OS. A Demo Shop includes different sets of components that have been selected for a different type of business or project. Each of these options is fully functional and can be used for both demonstrative purposes as well as working as a boilerplate for your new project. Though each shop comes with its own pre-selected components, Spryker also offers hundreds of additional modules which can be chosen later.
-
-You can choose from the following options:
-
-* [B2B Demo Shop](/docs/scos/user/intro-to-spryker//b2b-suite.html): A boilerplate for B2B commerce projects.
-* [B2C Demo Shop](/docs/scos/user/intro-to-spryker/b2c-suite.html): A starting point for B2C implementations.
-
-Both Demo Shops can also be expanded with separate features and modules.
-
-To install Spryker, see [Set up Spryker locally](/docs/dg/dev/set-up-spryker-locally/set-up-spryker-locally.html). Spryker can be run on MacOS, Linux, and Windows with WSL1 or WSL2.
-
-### The deploy file
-
-When working with a local environment, you should use the [deploy.dev.yml](/docs/dg/dev/sdks/the-docker-sdk/deploy-file/deploy-file.html) file.
-
-In the default deploy file, change the following attributes:
-
-* Namespace: We recommend specifying the name for your project, as this helps to avoid issues when you have two or more projects with the same names
-* Regions
-* Stores
-* Domains for the local environment
-* Domains for the services (RabbitMQ, Jenkins): Optional, but this can help to keep all project links together
-
-### Vagrant clean-up
-
-In the past, Vagrant had been used to run Spryker locally. Now that Spryker runs on Docker, you can remove the following Vagrant configuration files:
-
-* `config/install/development.yml`
-* `config_default-development_*.php`
-
-### Adjust the `readme.md` file
-
-Once your project has been installed, you need to adjust the `readme.md` file as follows:
-
-* Update the project installation description.
-* Update the repository link.
-* Remove any unused information, such as Vagrant installation instructions if a DevVM was not used.
-* Consider moving the production information further done in the file so that new developers can more readily understand how to use the project.
-
-## 2. Manage modules
-
-Once the installation of your new project has been completed, you may start to manage the modules you want to use. A module within Spryker is a single-function unit that has well-defined dependencies and can be updated independently.
-
-{% info_block infoBox %}
-
-To better define your strategy when implementing Spryker updates, learn about our [module and feature release process](/docs/scos/user/intro-to-spryker/spryker-release-process.html).
-
-{% endinfo_block %}
-
-When installing and managing module dependencies, we use [Composer](/docs/dg/dev/set-up-spryker-locally/manage-dependencies-with-composer.html). Depending on what you want to do, you can run one of the following Composer commands:
-
-* To install the dependencies you listed in the `composer.json` file of the project: `composer install`.
-* To update all the modules for your project: `composer update "spryker/*"`.
-
-{% info_block infoBox %}
-
-We recommend running this command weekly to ensure you have the latest fixes. We also recommend [subscribing to our release notes newsletter](https://now.spryker.com/release-notes) to stay up to date with the improvements.
-
-{% endinfo_block %}
-
-* To update a particular module: `composer update "spryker/module-name"`.
-
-{% info_block infoBox %}
-
-You can easily keep track of new module versions using the [composer-versions-check](https://github.com/Soullivaneuh/composer-versions-check) addon for your local Composer tool.
-
-{% endinfo_block %}
-
-* To add a new module to your project: `composer require "spryker/module-name"`.
-
-To learn about the module versioning approach in Spryker, see [Semantic Versioning: Major vs. Minor vs. Patch Release](/docs/dg/dev/architecture/module-api/semantic-versioning-major-vs.-minor-vs.-patch-release.html).
-
-## 3. Configure the environment
-
-To configure and customize your project, you can do the following:
-
-1. Define how to manage the settings in the configuration files with [Configuration management](/docs/dg/dev/backend-development/data-manipulation/configuration-management.html).
-2. Configure your environment:
-    <!-- * [Database](/docs/dg/dev/set-up-spryker-locally/installing-spryker-with-development-virtual-machine/configuring-spryker-with-devvm/configuring-database-servers.html) -->
-    * [Redis](/docs/dg/dev/set-up-spryker-locally/redis-configuration.html)
-    <!---*   [ElasticSearch](/docs/pbc/all/search/{{site.version}}/tutorials-and-howtos/configure-elasticsearch.html)-->
-    * [Queue](/docs/dg/dev/backend-development/data-manipulation/queue/queue.html)
-3. [Configure stores](/docs/dg/dev/internationalization-and-multi-store/set-up-multiple-stores.html#configure-stores) depending on your need for one or multiple stores in your online shop.
-4. [Schedule tasks](/docs/dg/dev/backend-development/cronjobs/cronjobs.html) (Cron jobs).
-<!---4. Move to the maintenance mode-->
-
-### Store clean-up
-
-This step depends on the store setup you came up with during your configuring. For example, if you choose to start with just one store, you should clean up the remaining stores in the following files:
-
-* `config/install/*`
-* `data/import/*`
-* `deploy.dev.yml`
-* `config_default.php`
-* `src/SprykerConfig/CodeBucketConfig.php`
-
-### Modules clean-up
-
-* Analyze modules that you have in the desired Demoshop.
-* Analyze modules that you need to have.
-* Remove unnecessary modules (to do that, you can use the migration guide backward).
-
-### Data import clean-up
-
-Located in the `data/import` folder, you may find additional files related to these other stores. As with cleaning up stores, you must define the stores you intend to use and remove unused files of the rest.
-
-{% info_block infoBox "Info" %}
-
-Keep in mind that you must also change the default config in `DataImportConfig::getDefaultYamlConfigPath()`.
-
-{% endinfo_block %}
-
-For those stores that you wish to allow, don’t forget to edit `CodeBucketConfig::getCodeBuckets()`.
-
-## 4. Configure CI
-
-Continuous Integration (CI) is a development practice where each part of the code can be verified by an automated build and automated tests. This allows for good code quality and that each new feature does not break the existing functionality. The following documents will help you to enable CI in different repositories:
-* [Deployment pipelines](/docs/ca/dev/configure-deployment-pipelines/configure-azure-pipelines.html)
-* [Customizing deployment pipelines](/docs/ca/dev/configure-deployment-pipelines/configure-bitbucket-pipelines.html)
-* [GitHub Actions](/docs/ca/dev/configure-deployment-pipelines/configure-github-actions.html)
-* [Configuring GitLab pipelines](/docs/ca/dev/configure-deployment-pipelines/configure-gitlab-pipelines.html)
-* [Azure Pipelines](/docs/ca/dev/configure-deployment-pipelines/configure-azure-pipelines.html)
-* [Configuring Bitbucket Pipelines ](/docs/ca/dev/configure-deployment-pipelines/configure-bitbucket-pipelines.html)
-
-## 5. Configure checkers
-
-To keep your code clean, we recommend using code checkers. To keep your code clean, we recommend using the code checkers.
-
-### Code Sniffer
-
-Before running any code sniffer, we recommend that you update it to its latest version. There are often changes that introduce new checks which help to increase the quality of code. When updating, be sure to keep in mind that you will also need to make changes to the `composer.json` file.
-
-```bash
-composer update spryker/code-sniffer slevomat/coding-standard --with-dependencies
-```
-
-At the project level, you may choose to use your own rules or to exclude rules enabled in Spryker by default.
-
-* To activate a new rule, check out the full list of rules at [Slevomat Coding Standard](https://github.com/slevomat/coding-standard).
-* To disable a rule, you can use configuration. The following example excludes a rule that makes annotation for constructor and method required:
-
-```yaml
-<rule ref="vendor/spryker/code-sniffer/Spryker/ruleset.xml">
-        <exclude name="Spryker.Commenting.DocBlock"/>
-</rule>
-```
-### PHPStan
-
-When using PHPStan, we recommend version 1.2.* or later. These versions help you avoid memory and other issues.
-
-This can be toggled at the project level by enabling rule level 6:
-
-```yaml
-vendor/bin/phpstan analyze -l 6 -c phpstan.neon src/
-```
-
-## 6. Configure PhpStorm
-
-If you wish to speed up your work, we recommend configuring PhpStorm.
-
-### Plugins
-
-Make sure to configure the following plugins:
-
-### Speed up indexation
-At the beginning of the project, you need to reset your project quite often. PhpStorm indexing is annoying and takes too much of the resources. To avoid this, you can disable cache indexing.
-
-To disable cache indexing, in the PhpStorm, right-click the folder and select **Mark Directory As&nbsp;<span aria-label="and then">></span> Excluded**.
-
-It is safe to disable cache indexing for the following files:
-
-* `data/cache `
-* `data/tmp`
-* `public/(Yves/Zed/Marketlace)/assets`
-
-## 7. Configure debugging
-
-Before you start developing, you should set up and get to know your debugging environment. To learn how to configure debugging, see one of the following:
-
-* [Configuring debugging in Docker](/docs/dg/dev/set-up-spryker-locally/configure-after-installing/configure-debugging/configure-debugging.html)
-
-{% info_block infoBox %}
-
-When in a production environment, Zed must be configured to use a VPN, basic access authentication, or an IP allowlist.
-
-{% endinfo_block %}
-
-## 8. Familiarize yourself with the Spryker architecture
-
-As a developer, the Spryker structure is the first thing you need to know to extend the core functionality. To familiarize yourself with the Spryker architecture, different parts of the Client, Shared, Zed, and Yves folders, and their different layers, see the following documents:
-
-* [Conceptual overview](/docs/dg/dev/architecture/conceptual-overview.html): to learn about application layers and code structure.
-* [Modules and layers](/docs/dg/dev/architecture/modules-and-application-layers.html): to learn about layers and how various functionality is encapsulated in modules.
-* [Programming concepts](/docs/dg/dev/architecture/programming-concepts.html): to learn about the Spryker building blocks contained in the application layers.
-* [Technology stack](/docs/dg/dev/architecture/technology-stack.html): to learn about the technologies we use.
-
-<!---* Introduction to navigating the folder structure, main concepts and namespacing.
-* The project directory
-* The OS directories-->
diff --git a/docs/scos/dev/feature-integration-guides/202212.0/feature-integration-guides.md b/docs/scos/dev/feature-integration-guides/202212.0/feature-integration-guides.md
deleted file mode 100644
index 46a13a436e8..00000000000
--- a/docs/scos/dev/feature-integration-guides/202212.0/feature-integration-guides.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Feature integration guides
-last_updated: Jun 16, 2021
-template: feature-integration-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/about-integration
-originalArticleId: 3c8973bd-80d2-451c-bd19-abfdd7eef96a
-redirect_from:
-  - /2021080/docs/about-integration
-  - /2021080/docs/en/about-integration
-  - /docs/about-integration
-  - /docs/en/about-integration
-  - /2021080/docs/about-migration-integration
-  - /2021080/docs/en/about-migration-integration
-  - /docs/about-migration-integration
-  - /docs/en/about-migration-integration
-  - /v6/docs/about-migration-integration
-  - /v6/docs/en/about-migration-integration
-  - /v5/docs/about-migration-integration
-  - /v5/docs/en/about-migration-integration
-  - /v4/docs/about-migration-integration
-  - /v4/docs/en/about-migration-integration
-  - /v3/docs/about-migration-integration
-  - /v3/docs/en/about-migration-integration
-  - /v2/docs/about-migration-integration
-  - /v2/docs/en/about-migration-integration
-  - /v1/docs/about-migration-integration
-  - /v1/docs/en/about-migration-integration
-  - /docs/scos/dev/migration-and-integration/about-migration-and-integration-guides.html
-  - /docs/scos/dev/feature-integration-guides/202200.0/feature-integration-guides.html
-  - /docs/scos/dev/glue-api-guides/202212.0/
----
-
-The integration guides provide step-by-step instructions on how to enable individual Spryker features for your project.
-
-Please keep in mind, that since Spryker Commerce OS is a highly modular system, you have total freedom in choosing what features to add to your project. When making a decision to install new features, we recommend not to bloat your project by installing everything, but opt for the features that are really justified in terms of your business needs.
-
-If you have spotted an issue with either of the guides, please feel free to [create an issue](https://github.com/spryker/spryker-docs/issues) or pull request by using the Edit on GitHub option.
-
-Not found an integration guide you are looking for? Let us know about it by [creating an issue on Github](https://github.com/spryker/spryker-docs/issues) or dropping an email to [documentation@spryker.com](mailto:documentation@spryker.com).
diff --git a/docs/scos/dev/feature-integration-guides/202212.0/glue-api/glue-api-installation-and-configuration.md b/docs/scos/dev/feature-integration-guides/202212.0/glue-api/glue-api-installation-and-configuration.md
deleted file mode 100644
index 66842e495e9..00000000000
--- a/docs/scos/dev/feature-integration-guides/202212.0/glue-api/glue-api-installation-and-configuration.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: Glue API installation and configuration
-description: This article describes the process of installing and enabling the GLUE API infrastructure and explains the details of integrating the REST API resources.
-last_updated: Jun 16, 2021
-template: feature-integration-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/glue-api-installation-and-configuration
-originalArticleId: e3903160-d613-4e86-81c5-ac4f3aa3308a
-redirect_from:
-  - /2021080/docs/glue-api-installation-and-configuration
-  - /2021080/docs/en/glue-api-installation-and-configuration
-  - /docs/glue-api-installation-and-configuration
-  - /docs/en/glue-api-installation-and-configuration
-  - /docs/scos/dev/feature-integration-guides/202200.0/glue-api/glue-api-installation-and-configuration.html
----
-
-{% include pbc/all/install-features/202212.0/install-glue-api/install-glue-api.md %} <!-- To edit, see /_includes/pbc/all/install-features/202212.0/install-glue-api/install-glue-api.md -->
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-does-not-give-any-output.md b/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-does-not-give-any-output.md
deleted file mode 100644
index 495ca509325..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-does-not-give-any-output.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: nc command does not give any output
-description: If the nc command does not give any output, contact us
-last_updated: Jun 16, 2021
-template: troubleshooting-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/nc-command-does-not-give-any-output
-originalArticleId: 65a16193-926a-4aab-a5df-2570e880168c
-redirect_from:
-  - /2021080/docs/nc-command-does-not-give-any-output
-  - /2021080/docs/en/nc-command-does-not-give-any-output
-  - /docs/nc-command-does-not-give-any-output
-  - /docs/en/nc-command-does-not-give-any-output
-  - /v6/docs/nc-command-does-not-give-any-output
-  - /v6/docs/en/nc-command-does-not-give-any-output
-related:
-  - title: nc command tells that the port is opened
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-tells-that-the-port-is-opened.html
-  - title: PHP `xdebug` extension is not active in CLI
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-in-cli.html
-  - title: PHP `xdebug` extension is not active when accessing the website via a browser or curl
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-when-accessing-the-website-via-a-browser-or-curl.html
-  - title: Xdebug does not work
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/xdebug-does-not-work.html
----
-
-## Description
-
-`nc` command does not give any output.
-
-## Solution
-
-[contact us](https://spryker.com/en/support/) if you have any questions.
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-tells-that-the-port-is-opened.md b/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-tells-that-the-port-is-opened.md
deleted file mode 100644
index 05877007f91..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-tells-that-the-port-is-opened.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title: nc command tells that the port is opened
-description: Learn how to fix the issue when nc command tells that the port is opened
-last_updated: Jun 16, 2021
-template: troubleshooting-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/nc-command-tells-that-the-port-is-opened
-originalArticleId: 4a169ffc-dd56-4026-b17f-44981617e0fe
-redirect_from:
-  - /2021080/docs/nc-command-tells-that-the-port-is-opened
-  - /2021080/docs/en/nc-command-tells-that-the-port-is-opened
-  - /docs/nc-command-tells-that-the-port-is-opened
-  - /docs/en/nc-command-tells-that-the-port-is-opened
-  - /v6/docs/nc-command-tells-that-the-port-is-opened
-  - /v6/docs/en/nc-command-tells-that-the-port-is-opened
-related:
-  - title: nc command does not give any output
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-does-not-give-any-output.html
-  - title: PHP `xdebug` extension is not active in CLI
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-in-cli.html
-  - title: PHP `xdebug` extension is not active when accessing the website via a browser or curl
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-when-accessing-the-website-via-a-browser-or-curl.html
-  - title: Xdebug does not work
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/xdebug-does-not-work.html
----
-
-## Description
-
-`nc` command tells that the port is opened.
-
-## Solution
-
-1. Check what process occupies the port 9000 by running the command on the host:
-   
-```bash
-sudo lsof -nPi:9000 | grep LISTEN
-```
-
-2. If it's not your IDE, free up the port to be used by the IDE.
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/xdebug-does-not-work.md b/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/xdebug-does-not-work.md
deleted file mode 100644
index 5577da98ddc..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/xdebug-does-not-work.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Xdebug does not work
-description: Learn how to fix the issue with a non-working Xdebug
-last_updated: Jun 16, 2021
-template: troubleshooting-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/xdebug-does-not-work
-originalArticleId: 8169faa4-1c53-4812-bbba-6e34c72cb77c
-redirect_from:
-  - /2021080/docs/xdebug-does-not-work
-  - /2021080/docs/en/xdebug-does-not-work
-  - /docs/xdebug-does-not-work
-  - /docs/en/xdebug-does-not-work
-  - /v6/docs/xdebug-does-not-work
-  - /v6/docs/en/xdebug-does-not-work
-related:
-  - title: nc command does not give any output
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-does-not-give-any-output.html
-  - title: nc command tells that the port is opened
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-tells-that-the-port-is-opened.html
-  - title: PHP `xdebug` extension is not active in CLI
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-in-cli.html
-  - title: PHP `xdebug` extension is not active when accessing the website via a browser or curl
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-when-accessing-the-website-via-a-browser-or-curl.html
----
-
-## Description
-
-Xdebug does not work.
-
-## Solution
-
-1. Ensure that Xdebug is enabled in `deploy.*.yml`:
-
-```yaml
-docker:
-...
-    debug:
-      xdebug:
-        enabled: true
-```
-
-2. Ensure that IDE is listening to the port 9000.
-3. Check if the host is accessible from the container:
-
-```bash
-docker/sdk cli -x bash -c 'nc -zv ${SPRYKER_XDEBUG_HOST_IP} 9000'
-```
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-docker-issues.md b/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-docker-issues.md
deleted file mode 100644
index f5a78565dbe..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-docker-issues.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: Troubleshooting Docker issues
-description: Troubleshoot issues you might encounter when you have your Spryker-based project in Docker.
-last_updated: Jun 16, 2021
-template: troubleshooting-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/troubleshooting-spryker-in-docker-issues
-originalArticleId: 86164c2a-2a65-4c15-a36e-3f37d4e8c001
-redirect_from:
-  - /2021080/docs/troubleshooting-spryker-in-docker-issues
-  - /2021080/docs/en/troubleshooting-spryker-in-docker-issues
-  - /docs/troubleshooting-spryker-in-docker-issues
-  - /docs/en/troubleshooting-spryker-in-docker-issues
-  - /v6/docs/troubleshooting-spryker-in-docker-issues
-  - /v6/docs/en/troubleshooting-spryker-in-docker-issues
-  - /v5/docs/spryker-in-docker-troubleshooting
-  - /v5/docs/en/spryker-in-docker-troubleshooting
-  - /v4/docs/spryker-in-docker-troubleshooting
-  - /v4/docs/en/spryker-in-docker-troubleshooting
-  - /v3/docs/spryker-in-docker-troubleshooting
-  - /v3/docs/en/spryker-in-docker-troubleshooting
-  - /docs/spryker-in-docker-troubleshooting
-  - /docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-spryker-in-docker-issues.html
----
-
-This section includes guidance for problems related to issues you might encounter with your Spryker-based project in the Docker environment.  
-
-## Topics
-
-Troubleshooting running applications in Docker:
-
-* [Port is already occupied on host](/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/port-is-already-occupied-on-host.html)
-* [413 Request Entity Too Large](/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/413-request-entity-too-large.html)
-* [Nginx welcome page](/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/nginx-welcome-page.html)
-* [An application is not reachable via http](/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/an-application-is-not-reachable-via-http.html)
-* [Mutagen error](/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-error.html)
-* [Mutagen synchronization issue](/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-synchronization-issue.html)
-* [MacOS and Windows: file synchronization issues in Development mode](/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/macos-and-windows-file-synchronization-issues-in-development-mode.html)
-
-Troubleshooting debugging in Docker:
-
-* [Xdebug does not work](/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/xdebug-does-not-work.html)
-* [`nc` command does not give any output](/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-does-not-give-any-output.html)
-* [`nc` command tells that the port is opened](/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/nc-command-tells-that-the-port-is-opened.html)
-* [PHP `xdebug` extension is not active in CLI](/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-in-cli.html)
-* [PHP `xdebug` extension is not active when accessing the website via a browser or curl](/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-debugging-in-docker/php-xdebug-extension-is-not-active-when-accessing-the-website-via-a-browser-or-curl.html)
-
-{% info_block infoBox %}
-
-If you encounter a Spryker in Docker issue that is not addressed on this page, try searching by an error output or keywords, or visit the [Spryker Support Portal](https://spryker.force.com/support/s/) for technical support.
-
-If you found a solution to a repetitive issue, please suggest a change to this page by clicking the **Edit or Report** button.
-
-{% endinfo_block %}
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/413-request-entity-too-large.md b/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/413-request-entity-too-large.md
deleted file mode 100644
index 6b3efca5e4b..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/413-request-entity-too-large.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: 413 Request Entity Too Large
-description: Learn how to fix the issue 413 Request Entity Too Large
-last_updated: Jun 16, 2021
-template: troubleshooting-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/413-request-entity-too-large
-originalArticleId: 5cfeaaf5-441d-4e75-92c8-215c2db21af5
-redirect_from:
-  - /2021080/docs/413-request-entity-too-large
-  - /2021080/docs/en/413-request-entity-too-large
-  - /docs/413-request-entity-too-large
-  - /docs/en/413-request-entity-too-large
-  - /v6/docs/413-request-entity-too-large
-  - /v6/docs/en/413-request-entity-too-large
-related:
-  - title: An application is not reachable via http
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/an-application-is-not-reachable-via-http.html
-  - title: MacOS and Windows - file synchronization issues in Development mode
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/macos-and-windows-file-synchronization-issues-in-development-mode.html
-  - title: Mutagen error
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-error.html
-  - title: Mutagen synchronization issue
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-synchronization-issue.html
-  - title: Nginx welcome page
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/nginx-welcome-page.html
-  - title: Port is already occupied on host
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/port-is-already-occupied-on-host.html
-
----
-
-## Description
-
-You get the `413 Request Entity Too Large` error.
-
-## Solution
-
-1. Increase the maximum request body size for the related application. See [Deploy file reference](/docs/dg/dev/sdks/the-docker-sdk/deploy-file/deploy-file-reference.html) to learn how to do that.
-2. Fetch the update:
-
-```bash
-docker/sdk bootstrap
-```
-
-3. Re-build applications:
-
-```bash
-docker/sdk up
-```
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/an-application-is-not-reachable-via-http.md b/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/an-application-is-not-reachable-via-http.md
deleted file mode 100644
index 1f6476259f5..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/an-application-is-not-reachable-via-http.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: An application is not reachable via http
-description: Learn how to fix the issue when an application is not reachable via http
-last_updated: Jun 16, 2021
-template: troubleshooting-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/an-application-is-not-reachable-via-http
-originalArticleId: 2a96637b-d930-436b-908a-62f9ddbd8298
-redirect_from:
-  - /2021080/docs/an-application-is-not-reachable-via-http
-  - /2021080/docs/en/an-application-is-not-reachable-via-http
-  - /docs/an-application-is-not-reachable-via-http
-  - /docs/en/an-application-is-not-reachable-via-http
-  - /v6/docs/an-application-is-not-reachable-via-http
-  - /v6/docs/en/an-application-is-not-reachable-via-http
-related:
-  - title: 413 Request Entity Too Large
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/413-request-entity-too-large.html
-  - title: MacOS and Windows - file synchronization issues in Development mode
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/macos-and-windows-file-synchronization-issues-in-development-mode.html
-  - title: Mutagen error
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-error.html
-  - title: Mutagen synchronization issue
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-synchronization-issue.html
-  - title: Nginx welcome page
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/nginx-welcome-page.html
-  - title: Port is already occupied on host
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/port-is-already-occupied-on-host.html
----
-
-## Description
-
-An application like Yves, BackOffice(Zed), GlueStorefront(Glue), GlueBackend or MerchantPortal is not reachable after installation.
-
-## Solution
-
-In `deploy.*.yml`, ensure that SSL encryption is disabled:
-
-```yaml
-docker:
-    ssl:
-        enabled: false
-```
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/macos-and-windows-file-synchronization-issues-in-development-mode.md b/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/macos-and-windows-file-synchronization-issues-in-development-mode.md
deleted file mode 100644
index 11203360ccc..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/macos-and-windows-file-synchronization-issues-in-development-mode.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: MacOS and Windows - file synchronization issues in Development mode
-description: Learn how to deal with file synchronization issues in Development mode on MacOS and Windows.
-last_updated: Jun 16, 2021
-template: troubleshooting-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/macos-and-windows-file-synchronization-issues-in-development-mode
-originalArticleId: 1c53083e-003e-4fda-b23e-3d926adcd08b
-redirect_from:
-  - /2021080/docs/macos-and-windows-file-synchronization-issues-in-development-mode
-  - /2021080/docs/en/macos-and-windows-file-synchronization-issues-in-development-mode
-  - /docs/macos-and-windows-file-synchronization-issues-in-development-mode
-  - /docs/en/macos-and-windows-file-synchronization-issues-in-development-mode
-  - /v6/docs/macos-and-windows-file-synchronization-issues-in-development-mode
-  - /v6/docs/en/macos-and-windows-file-synchronization-issues-in-development-mode
-related:
-  - title: 413 Request Entity Too Large
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/413-request-entity-too-large.html
-  - title: An application is not reachable via http
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/an-application-is-not-reachable-via-http.html
-  - title: Mutagen error
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-error.html
-  - title: Mutagen synchronization issue
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-synchronization-issue.html
-  - title: Nginx welcome page
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/nginx-welcome-page.html
-  - title: Port is already occupied on host
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/port-is-already-occupied-on-host.html
----
-
-A project has file synchronization issues in Development mode.
-
-## Solution
-
-1. Follow sync logs:
-
-```bash
-docker/sdk sync logs
-```
-
-2. Hard reset:
-
-```bash
-docker/sdk trouble && rm -rf vendor && rm -rf src/Generated && docker/sdk sync && docker/sdk up
-```
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-error.md b/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-error.md
deleted file mode 100644
index c4e55b1437b..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-error.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: Mutagen error
-description: Learn how to fix the Mutagen error
-last_updated: Jun 16, 2021
-template: troubleshooting-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/mutagen-error
-originalArticleId: b1896a64-b124-48a9-9fc5-33c950a620ad
-redirect_from:
-  - /2021080/docs/mutagen-error
-  - /2021080/docs/en/mutagen-error
-  - /docs/mutagen-error
-  - /docs/en/mutagen-error
-  - /v6/docs/mutagen-error
-  - /v6/docs/en/mutagen-error
-related:
-  - title: 413 Request Entity Too Large
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/413-request-entity-too-large.html
-  - title: An application is not reachable via http
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/an-application-is-not-reachable-via-http.html
-  - title: MacOS and Windows - file synchronization issues in Development mode
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/macos-and-windows-file-synchronization-issues-in-development-mode.html
-  - title: Mutagen synchronization issue
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-synchronization-issue.html
-  - title: Nginx welcome page
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/nginx-welcome-page.html
-  - title: Port is already occupied on host
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/port-is-already-occupied-on-host.html
----
-
-## Description
-
-You get the error:
-
-```bash
-unable to reconcile Mutagen sessions: unable to create synchronization session (spryker-dev-codebase): unable to connect to beta: unable to connect to endpoint: unable to dial agent endpoint: unable to create agent command: unable to probe container: container probing failed under POSIX hypothesis (signal: killed) and Windows hypothesis (signal: killed)
-```
-
-## Solution
-
-1. Restart your OS.
-2. If the error persists: Check [Mutagen documentation](https://mutagen.io/documentation/introduction).
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-synchronization-issue.md b/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-synchronization-issue.md
deleted file mode 100644
index d9e96c9b580..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-synchronization-issue.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Mutagen synchronization issue
-description: Learn how to fix the Mutagen synchronization issue
-last_updated: Jun 16, 2021
-template: troubleshooting-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/mutagen-synchronization-issue
-originalArticleId: c02d26b0-4cfd-4274-8253-c6ff27aa3b3d
-redirect_from:
-  - /2021080/docs/mutagen-synchronization-issue
-  - /2021080/docs/en/mutagen-synchronization-issue
-  - /docs/mutagen-synchronization-issue
-  - /docs/en/mutagen-synchronization-issue
-  - /v6/docs/mutagen-synchronization-issue
-  - /v6/docs/en/mutagen-synchronization-issue
-related:
-  - title: 413 Request Entity Too Large
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/413-request-entity-too-large.html
-  - title: An application is not reachable via http
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/an-application-is-not-reachable-via-http.html
-  - title: MacOS and Windows - file synchronization issues in Development mode
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/macos-and-windows-file-synchronization-issues-in-development-mode.html
-  - title: Mutagen error
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-error.html
-  - title: Nginx welcome page
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/nginx-welcome-page.html
-  - title: Port is already occupied on host
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/port-is-already-occupied-on-host.html
----
-
-## Description
-
-There is a synchronization issue.
-
-## Solution
-
-* Restart your OS.
-* Run the commands:
-
-```
-docker/sdk trouble
-mutagen sync list
-mutagen sync terminate <all sessions in the list>
-docker/sdk up
-```
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/nginx-welcome-page.md b/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/nginx-welcome-page.md
deleted file mode 100644
index 1a9d817332f..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/nginx-welcome-page.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Nginx welcome page
-description: Learn how to fix the issue when you get Nginx welcome page upon opening an application in browser
-last_updated: Jun 16, 2021
-template: troubleshooting-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/nginx-welcome-page
-originalArticleId: 27e0d295-8262-41c9-affb-f2339556ef1c
-redirect_from:
-  - /2021080/docs/nginx-welcome-page
-  - /2021080/docs/en/nginx-welcome-page
-  - /docs/nginx-welcome-page
-  - /docs/en/nginx-welcome-page
-  - /v6/docs/nginx-welcome-page
-  - /v6/docs/en/nginx-welcome-page
-related:
-  - title: 413 Request Entity Too Large
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/413-request-entity-too-large.html
-  - title: An application is not reachable via http
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/an-application-is-not-reachable-via-http.html
-  - title: MacOS and Windows - file synchronization issues in Development mode
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/macos-and-windows-file-synchronization-issues-in-development-mode.html
-  - title: Mutagen error
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-error.html
-  - title: Mutagen synchronization issue
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-synchronization-issue.html
-  - title: Port is already occupied on host
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/port-is-already-occupied-on-host.html
----
-
-You get the Nginx welcome page by opening an application in the browser.
-
-1. Update the `nginx:alpine` image:
-
-```bash
-docker pull nginx:alpine
-```
-
-2. Re-build applications:
-
-```bash
-docker/sdk up
-```
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/port-is-already-occupied-on-host.md b/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/port-is-already-occupied-on-host.md
deleted file mode 100644
index 896e5bfe1c2..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/port-is-already-occupied-on-host.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Port is already occupied on host
-description: Learn how to fix the issue when port is already occupied on host
-last_updated: Jun 16, 2021
-template: troubleshooting-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/port-is-already-occupied-on-host
-originalArticleId: cf038694-8d04-43cf-adc7-005de29058e2
-redirect_from:
-  - /2021080/docs/port-is-already-occupied-on-host
-  - /2021080/docs/en/port-is-already-occupied-on-host
-  - /docs/port-is-already-occupied-on-host
-  - /docs/en/port-is-already-occupied-on-host
-  - /v6/docs/port-is-already-occupied-on-host
-  - /v6/docs/en/port-is-already-occupied-on-host
-related:
-  - title: 413 Request Entity Too Large
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/413-request-entity-too-large.html
-  - title: An application is not reachable via http
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/an-application-is-not-reachable-via-http.html
-  - title: MacOS and Windows - file synchronization issues in Development mode
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/macos-and-windows-file-synchronization-issues-in-development-mode.html
-  - title: Mutagen error
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-error.html
-  - title: Mutagen synchronization issue
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/mutagen-synchronization-issue.html
-  - title: Nginx welcome page
-    link: docs/scos/dev/troubleshooting/troubleshooting-docker-issues/troubleshooting-running-applications-in-docker/nginx-welcome-page.html
----
-
-## Description
-
-Running the `docker/sdk up` console command returns an error similar to the following:
-
-```bash
-ERROR: for nginx_frontend Cannot start service nginx_frontend: driver failed programming external connectivity on endpoint spryker_nginx_frontend_1 (e4fdb360f6c9a3243c0a88fa74f8d377325f65b8cd2340b2dacb51377519c1cf): Error starting userland proxy: Bind for 0.0.0.0:80: unexpected error (Failure EADDRINUSE)
-```
-
-## Solution
-
-1. Check what process occupies the port:
-
-```bash
-sudo lsof -nPi:80 | grep LISTEN
-```
-
-2. Stop the process or make it use a different port.
-3. Run `docker/sdk up` again.
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/a-command-fails-with-a-killed-message.md b/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/a-command-fails-with-a-killed-message.md
deleted file mode 100644
index fc4eb6e29ba..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/a-command-fails-with-a-killed-message.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: A command fails with a `Killed` message
-description: Learn how to resolve the issue with a command returning a `killed` message.
-last_updated: Jun 16, 2021
-template: troubleshooting-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/a-command-fails-with-a-killed-message
-originalArticleId: 09c3dd70-4e87-4604-b5d3-844e49e4c853
-redirect_from:
-  - /2021080/docs/a-command-fails-with-a-killed-message
-  - /2021080/docs/en/a-command-fails-with-a-killed-message
-  - /docs/a-command-fails-with-a-killed-message
-  - /docs/en/a-command-fails-with-a-killed-message
-  - /v6/docs/a-command-fails-with-a-killed-message
-  - /v6/docs/en/a-command-fails-with-a-killed-message
-related:
-  - title: Class Silex/ControllerProviderInterface not found
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/class-silex-controllerproviderinterface-not-found.html
-  - title: Composer version 2 compatibility issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/composer-version-2-compatibility-issues.html
-  - title: ERROR - remove spryker_logs - volume is in use
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-remove-spryker-logs-volume-is-in-use.html
-  - title: Error response from daemon - OCI runtime create failed - .... \\\"no such file or directory\\\"\""- unknown
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown.html
-  - title: Fail whale on the frontend
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-front-end.html
-  - title: No data on the Storefront
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/no-data-on-the-storefront.html
-  - title: PHPStan memory issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/phpstan-memory-issues.html
-  - title: ProcessTimedOutException after queue-task-start
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/processtimedoutexception-after-queue-task-start.html
-  - title: RabbitMQ - Zed.CRITICAL - PhpAmqpLib\Exception\AMQPChannelClosedException - Channel connection is closed
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.html
-  - title: Router generates absolute URL with localhost
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/router-generates-absolute-url-with-localhost.html
-  - title: RuntimeException - Failed to execute regex - PREG_JIT_STACKLIMIT_ERROR
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error.html
-  - title: The spy_oms_transition_log table takes up too much space
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/the-spy-oms-transition-log-table-takes-up-too-much-space.html
-  - title: Unable to resolve hosts for Mail, Jenkins, and RabbitMQ
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq.html
----
-
-Running a CLI command with a long execution time returns a `Killed` message.
-
-## Solution
-
-* In PHP settings, increase `max_execution_time`. In Docker based projects, you can do it via a Deploy file as follows:
-
-```yaml
-image:
-  tag: ...
-  php:
-    ini:
-      'max_execution_time': 300
-```
-
-* Increase `PropelConfig` class timeout:
-
-**/b2c/vendor/spryker/propel/src/Spryker/Zed/Propel/PropelConfig.php**
-
-```php
-
-class PropelConfig extends AbstractBundleConfig
-{
-    public const DB_ENGINE_MYSQL = 'mysql';
-    public const DB_ENGINE_PGSQL = 'pgsql';
-
-    protected const PROCESS_TIMEOUT = {process_timeout_value};
-
-    ...
-}
-```
-
-Replace `{process_timeout_value}` with a suitable value. We recommend setting the value that is just enough to run the command. Setting an unreasonably big value may cause performance issue.
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/class-silex-controllerproviderinterface-not-found.md b/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/class-silex-controllerproviderinterface-not-found.md
deleted file mode 100644
index f5d96ee9610..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/class-silex-controllerproviderinterface-not-found.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Class Silex/ControllerProviderInterface not found
-description: Learn how to fix the issue when class Silex/ControllerProviderInterface is not found
-last_updated: Jun 16, 2021
-template: troubleshooting-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/class-silexcontrollerproviderinterface-not-found
-originalArticleId: 1ed7e7c7-6975-4cdc-855c-3f5e8006a555
-redirect_from:
-  - /2021080/docs/class-silexcontrollerproviderinterface-not-found
-  - /2021080/docs/en/class-silexcontrollerproviderinterface-not-found
-  - /docs/class-silexcontrollerproviderinterface-not-found
-  - /docs/en/class-silexcontrollerproviderinterface-not-found
-  - /v6/docs/class-silexcontrollerproviderinterface-not-found
-  - /v6/docs/en/class-silexcontrollerproviderinterface-not-found
-  - /docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-front-end.html
-related:
-  - title: A command fails with a `Killed` message
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/a-command-fails-with-a-killed-message.html
-  - title: Composer version 2 compatibility issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/composer-version-2-compatibility-issues.html
-  - title: ERROR - remove spryker_logs - volume is in use
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-remove-spryker-logs-volume-is-in-use.html
-  - title: Error response from daemon- OCI runtime create failed- .... \\\"no such file or directory\\\"\""- unknown
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown.html
-  - title: Fail whale on the frontend
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-front-end.html
-  - title: No data on the Storefront
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/no-data-on-the-storefront.html
-  - title: PHPStan memory issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/phpstan-memory-issues.html
-  - title: ProcessTimedOutException after queue-task-start
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/processtimedoutexception-after-queue-task-start.html
-  - title: RabbitMQ - Zed.CRITICAL - PhpAmqpLib\Exception\AMQPChannelClosedException - Channel connection is closed
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.html
-  - title: Router generates absolute URL with localhost
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/router-generates-absolute-url-with-localhost.html
-  - title: RuntimeException - Failed to execute regex - PREG_JIT_STACKLIMIT_ERROR
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error.html
-  - title: The spy_oms_transition_log table takes up too much space
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/the-spy-oms-transition-log-table-takes-up-too-much-space.html
-  - title: Unable to resolve hosts for Mail, Jenkins, and RabbitMQ
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq.html
----
-
-## Description
-
-When a project still uses Silex, but modules were updated to the newest versions, where Silex is moved to the require-dev dependency, class `Silex/ControllerProviderInterface` is not found.
-
-## Cause
-
-The current version (1.0.4) of this module uses `SprykerShop\Yves\CheckoutPage\Plugin\Provider\CheckoutPageControllerPlugin`which is no longer functional in the latest Spryker Core.
-
-## Solution
-
-Until a new version of this module is provided, users can work around this issue by overriding `EasycreditController` and using `CheckoutPageRouteProviderPlugin` instead of `CheckoutPageControllerPlugin`. Also, see [Silex replacement](/docs/dg/dev/upgrade-and-migrate/silex-replacement/silex-replacement.html).
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/composer-version-2-compatibility-issues.md b/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/composer-version-2-compatibility-issues.md
deleted file mode 100644
index 6b847c2cf72..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/composer-version-2-compatibility-issues.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: Composer version 2 compatibility issues
-description: Learn how to solve Composer version 2 compatibility issues.
-last_updated: Jun 16, 2021
-template: troubleshooting-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/composer-version-2-compatibility-issues
-originalArticleId: b110284a-a19f-4c7b-a8fd-769b3dff6ed2
-redirect_from:
-  - /2021080/docs/composer-version-2-compatibility-issues
-  - /2021080/docs/en/composer-version-2-compatibility-issues
-  - /docs/composer-version-2-compatibility-issues
-  - /docs/en/composer-version-2-compatibility-issues
-  - /v6/docs/composer-version-2-compatibility-issues
-  - /v6/docs/en/composer-version-2-compatibility-issues
-related:
-  - title: A command fails with a `Killed` message
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/a-command-fails-with-a-killed-message.html
-  - title: Class Silex/ControllerProviderInterface not found
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/class-silex-controllerproviderinterface-not-found.html
-  - title: ERROR - remove spryker_logs - volume is in use
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-remove-spryker-logs-volume-is-in-use.html
-  - title: Error response from daemon - OCI runtime create failed - .... \\\"no such file or directory\\\"\""- unknown
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown.html
-  - title: Fail whale on the frontend
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-front-end.html
-  - title: No data on the Storefront
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/no-data-on-the-storefront.html
-  - title: PHPStan memory issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/phpstan-memory-issues.html
-  - title: ProcessTimedOutException after queue-task-start
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/processtimedoutexception-after-queue-task-start.html
-  - title: RabbitMQ - Zed.CRITICAL - PhpAmqpLib\Exception\AMQPChannelClosedException - Channel connection is closed
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.html
-  - title: Router generates absolute URL with localhost
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/router-generates-absolute-url-with-localhost.html
-  - title: RuntimeException - Failed to execute regex - PREG_JIT_STACKLIMIT_ERROR
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error.html
-  - title: The spy_oms_transition_log table takes up too much space
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/the-spy-oms-transition-log-table-takes-up-too-much-space.html
-  - title: Unable to resolve hosts for Mail, Jenkins, and RabbitMQ
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq.html
----
-
-After running `composer update spryker/{module_name}`, you get an error similar to the following:
-
-```bash
-Problem 1
-- ocramius/package-versions is locked to version 1.4.2 and an update of this package was not requested.
-- ocramius/package-versions 1.4.2 requires composer-plugin-api ^1.0.0 -> found composer-plugin-api[2.0.0] but it does not match the constraint.
-Problem 2
-- sllh/composer-versions-check is locked to version v2.0.3 and an update of this package was not requested.
-- sllh/composer-versions-check v2.0.3 requires composer-plugin-api ^1.0 -> found composer-plugin-api[2.0.0] but it does not match the constraint.
-Problem 3
-- ocramius/package-versions 1.4.2 requires composer-plugin-api ^1.0.0 -> found composer-plugin-api[2.0.0] but it does not match the constraint.
-- jean85/pretty-package-versions 1.2 requires ocramius/package-versions ^1.2.0 -> satisfiable by ocramius/package-versions[1.4.2].
-- jean85/pretty-package-versions is locked to version 1.2 and an update of this package was not requested.
-ocramius/package-versions only provides support for Composer 2 in 1.8+, which requires PHP 7.4.
-If you can not upgrade PHP you can require composer/package-versions-deprecated to resolve this with PHP 7.0+.
-```
-
-## Solution
-
-Run the following commands:
-
-```bash
-composer self-update --2
-composer remove sllh/composer-versions-check --ignore-platform-reqs
-composer require spryker-sdk/phpstan-spryker:^0.3 -W --ignore-platform-reqs
-
-git commit && git push
-```
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-remove-spryker-logs-volume-is-in-use.md b/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-remove-spryker-logs-volume-is-in-use.md
deleted file mode 100644
index f2bea5ddd7c..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-remove-spryker-logs-volume-is-in-use.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: ERROR- remove spryker_logs- volume is in use
-description: The solution to the `ERROR- remove spryker_logs- volume is in use` error.
-last_updated: Jun 16, 2021
-template: troubleshooting-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/error-remove-spryker-logs-volume-is-in-use
-originalArticleId: 2c841376-da36-4778-8964-306d0088f3d6
-redirect_from:
-  - /2021080/docs/error-remove-spryker-logs-volume-is-in-use
-  - /2021080/docs/en/error-remove-spryker-logs-volume-is-in-use
-  - /docs/error-remove-spryker-logs-volume-is-in-use
-  - /docs/en/error-remove-spryker-logs-volume-is-in-use
-  - /v6/docs/error-remove-spryker-logs-volume-is-in-use
-  - /v6/docs/en/error-remove-spryker-logs-volume-is-in-use
-related:
-  - title: A command fails with a `Killed` message
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/a-command-fails-with-a-killed-message.html
-  - title: Class Silex/ControllerProviderInterface not found
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/class-silex-controllerproviderinterface-not-found.html
-  - title: Composer version 2 compatibility issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/composer-version-2-compatibility-issues.html
-  - title: Error response from daemon - OCI runtime create failed - .... \\\"no such file or directory\\\"\""- unknown
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown.html
-  - title: Fail whale on the frontend
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-front-end.html
-  - title: No data on the Storefront
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/no-data-on-the-storefront.html
-  - title: PHPStan memory issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/phpstan-memory-issues.html
-  - title: ProcessTimedOutException after queue-task-start
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/processtimedoutexception-after-queue-task-start.html
-  - title: RabbitMQ- Zed.CRITICAL - PhpAmqpLib\Exception\AMQPChannelClosedException - Channel connection is closed
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.html
-  - title: Router generates absolute URL with localhost
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/router-generates-absolute-url-with-localhost.html
-  - title: RuntimeException - Failed to execute regex - PREG_JIT_STACKLIMIT_ERROR
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error.html
-  - title: The spy_oms_transition_log table takes up too much space
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/the-spy-oms-transition-log-table-takes-up-too-much-space.html
-  - title: Unable to resolve hosts for Mail, Jenkins, and RabbitMQ
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq.html
----
-
-You get the error `ERROR: remove spryker_logs: volume is in use - [{container_hash}]`
-
-## Solution
-
-1. Run the command:
-
-```
-docker rm -f {container_hash}
-```
-
-2. Repeat the failed command.
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown.md b/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown.md
deleted file mode 100644
index 6e3ed7411c1..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: Error response from daemon- OCI runtime create failed- .... \\\"no such file or directory\\\"\""- unknown
-description: The solution to the `Error response from daemon- OCI runtime create failed- .... no such file or directory - unknown.` error
-last_updated: Jun 16, 2021
-template: troubleshooting-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown
-originalArticleId: e06c6e8d-1edd-4227-8c9c-a18395175f74
-redirect_from:
-  - /2021080/docs/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown
-  - /2021080/docs/en/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown
-  - /docs/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown
-  - /docs/en/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown
-  - /v6/docs/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown
-  - /v6/docs/en/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown
-related:
-  - title: A command fails with a `Killed` message
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/a-command-fails-with-a-killed-message.html
-  - title: Class Silex/ControllerProviderInterface not found
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/class-silex-controllerproviderinterface-not-found.html
-  - title: Composer version 2 compatibility issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/composer-version-2-compatibility-issues.html
-  - title: ERROR - remove spryker_logs - volume is in use
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-remove-spryker-logs-volume-is-in-use.html
-  - title: Fail whale on the frontend
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-front-end.html
-  - title: No data on the Storefront
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/no-data-on-the-storefront.html
-  - title: PHPStan memory issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/phpstan-memory-issues.html
-  - title: ProcessTimedOutException after queue-task-start
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/processtimedoutexception-after-queue-task-start.html
-  - title: RabbitMQ- Zed.CRITICAL- PhpAmqpLib\Exception\AMQPChannelClosedException - Channel connection is closed
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.html
-  - title: Router generates absolute URL with localhost
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/router-generates-absolute-url-with-localhost.html
-  - title: RuntimeException - Failed to execute regex - PREG_JIT_STACKLIMIT_ERROR
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error.html
-  - title: The spy_oms_transition_log table takes up too much space
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/the-spy-oms-transition-log-table-takes-up-too-much-space.html
-  - title: Unable to resolve hosts for Mail, Jenkins, and RabbitMQ
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq.html
----
-
-You get the error `Error response from daemon: OCI runtime create failed: .... \\\"no such file or directory\\\"\"": unknown.`.
-
-## Solution
-
-Repeat the failed command.
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-frontend.md b/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-frontend.md
deleted file mode 100644
index 6861ae4cfb8..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-frontend.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: Fail whale on the frontend
-description: The solution for the fail whale on the front end.
-last_updated: Jun 16, 2021
-template: troubleshooting-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/fail-whale-on-the-front-end
-originalArticleId: bf2d7e12-feee-4369-a291-72d4fc5ed562
-redirect_from:
-  - /2021080/docs/fail-whale-on-the-front-end
-  - /2021080/docs/en/fail-whale-on-the-front-end
-  - /docs/fail-whale-on-the-front-end
-  - /docs/en/fail-whale-on-the-front-end
-  - /v6/docs/fail-whale-on-the-front-end
-  - /v6/docs/en/fail-whale-on-the-front-end
-related:
-  - title: A command fails with a `Killed` message
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/a-command-fails-with-a-killed-message.html
-  - title: Class Silex/ControllerProviderInterface not found
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/class-silex-controllerproviderinterface-not-found.html
-  - title: Composer version 2 compatibility issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/composer-version-2-compatibility-issues.html
-  - title: ERROR- remove spryker_logs- volume is in use
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-remove-spryker-logs-volume-is-in-use.html
-  - title: Error response from daemon - OCI runtime create failed - .... \\\"no such file or directory\\\"\""- unknown
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown.html
-  - title: No data on the Storefront
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/no-data-on-the-storefront.html
-  - title: PHPStan memory issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/phpstan-memory-issues.html
-  - title: ProcessTimedOutException after queue-task-start
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/processtimedoutexception-after-queue-task-start.html
-  - title: RabbitMQ - Zed.CRITICAL- PhpAmqpLib\Exception\AMQPChannelClosedException - Channel connection is closed
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.html
-  - title: Router generates absolute URL with localhost
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/router-generates-absolute-url-with-localhost.html
-  - title: RuntimeException - Failed to execute regex - PREG_JIT_STACKLIMIT_ERROR
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error.html
-  - title: The spy_oms_transition_log table takes up too much space
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/the-spy-oms-transition-log-table-takes-up-too-much-space.html
-  - title: Unable to resolve hosts for Mail, Jenkins, and RabbitMQ
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq.html
----
-
-A fail whale is displayed on the front end.
-
-## Solution
-
-1. Run the command:
-
-```bash
-docker/sdk logs
-```
-
-2. Add several returns to mark the line you started from.
-3. Open the page with the error.
-4. Check the logs.
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/no-data-on-the-storefront.md b/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/no-data-on-the-storefront.md
deleted file mode 100644
index 623ba4ff65f..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/no-data-on-the-storefront.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: No data on the Storefront
-description: The solution to the data being absent on the Storefront.
-last_updated: Jun 16, 2021
-template: troubleshooting-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/no-data-on-the-storefront
-originalArticleId: 5edf4ea6-b0e3-4284-90f3-a5ad06a30f58
-redirect_from:
-  - /2021080/docs/no-data-on-the-storefront
-  - /2021080/docs/en/no-data-on-the-storefront
-  - /docs/no-data-on-the-storefront
-  - /docs/en/no-data-on-the-storefront
-  - /v6/docs/no-data-on-the-storefront
-  - /v6/docs/en/no-data-on-the-storefront
-related:
-  - title: A command fails with a `Killed` message
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/a-command-fails-with-a-killed-message.html
-  - title: Class Silex/ControllerProviderInterface not found
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/class-silex-controllerproviderinterface-not-found.html
-  - title: Composer version 2 compatibility issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/composer-version-2-compatibility-issues.html
-  - title: ERROR - remove spryker_logs - volume is in use
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-remove-spryker-logs-volume-is-in-use.html
-  - title: Error response from daemon - OCI runtime create failed - .... \\\"no such file or directory\\\"\""- unknown
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown.html
-  - title: Fail whale on the frontend
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-front-end.html
-  - title: PHPStan memory issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/phpstan-memory-issues.html
-  - title: ProcessTimedOutException after queue-task-start
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/processtimedoutexception-after-queue-task-start.html
-  - title: RabbitMQ - Zed.CRITICAL- PhpAmqpLib\Exception\AMQPChannelClosedException - Channel connection is closed
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.html
-  - title: Router generates absolute URL with localhost
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/router-generates-absolute-url-with-localhost.html
-  - title: RuntimeException - Failed to execute regex - PREG_JIT_STACKLIMIT_ERROR
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error.html
-  - title: The spy_oms_transition_log table takes up too much space
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/the-spy-oms-transition-log-table-takes-up-too-much-space.html
-  - title: Unable to resolve hosts for Mail, Jenkins, and RabbitMQ
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq.html
----
-
-There is no data on the Storefront.
-
-## Solution
-
-Use the following services to check the status of queues and jobs:
-
-* `https://queue.mysprykershop.com`
-* `https://scheduler.mysprykershop.com`
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/phpstan-memory-issues.md b/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/phpstan-memory-issues.md
deleted file mode 100644
index e2f00086d1a..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/phpstan-memory-issues.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: PHPStan memory issues
-last_updated: Jun 16, 2021
-template: troubleshooting-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/phpstan-memory-issues
-originalArticleId: c234b12e-5260-4f86-97b4-44c7ef5c8dbf
-redirect_from:
-  - /2021080/docs/phpstan-memory-issues
-  - /2021080/docs/en/phpstan-memory-issues
-  - /docs/phpstan-memory-issues
-  - /docs/en/phpstan-memory-issues
-  - /v6/docs/phpstan-memory-issues
-  - /v6/docs/en/phpstan-memory-issues
-related:
-  - title: A command fails with a `Killed` message
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/a-command-fails-with-a-killed-message.html
-  - title: Class Silex/ControllerProviderInterface not found
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/class-silex-controllerproviderinterface-not-found.html
-  - title: Composer version 2 compatibility issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/composer-version-2-compatibility-issues.html
-  - title: ERROR - remove spryker_logs - volume is in use
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-remove-spryker-logs-volume-is-in-use.html
-  - title: Error response from daemon - OCI runtime create failed - .... \\\"no such file or directory\\\"\""- unknown
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown.html
-  - title: Fail whale on the frontend
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-front-end.html
-  - title: No data on the Storefront
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/no-data-on-the-storefront.html
-  - title: ProcessTimedOutException after queue-task-start
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/processtimedoutexception-after-queue-task-start.html
-  - title: RabbitMQ - Zed.CRITICAL- PhpAmqpLib\Exception\AMQPChannelClosedException - Channel connection is closed
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.html
-  - title: Router generates absolute URL with localhost
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/router-generates-absolute-url-with-localhost.html
-  - title: RuntimeException - Failed to execute regex - PREG_JIT_STACKLIMIT_ERROR
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error.html
-  - title: The spy_oms_transition_log table takes up too much space
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/the-spy-oms-transition-log-table-takes-up-too-much-space.html
-  - title: Unable to resolve hosts for Mail, Jenkins, and RabbitMQ
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq.html
----
-
-## Cause
-
-PHPStan needs to parse all files and due to Spryker's magic with resolving classes, e.g., `$this->getFacade()`, PHPStan needs to look up this class on its own when the `@method` annotation is missing.
-
-## Solution
-
-Run PHPStan in debug mode `--debug` on the module where it needs too much memory. In the debug mode, PHPStan will display the file name currently being analyzed. If PHPStan gets stuck at a specific file, look into this file and check if all `@method` annotations are present.
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/processtimedoutexception-after-queue-task-start.md b/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/processtimedoutexception-after-queue-task-start.md
deleted file mode 100644
index 21b6787834b..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/processtimedoutexception-after-queue-task-start.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: ProcessTimedOutException after queue-task-start
-description: Learn how to fix the exception after running queue-task-start
-last_updated: Jun 16, 2021
-template: troubleshooting-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/processtimedoutexception-after-queuetaskstart
-originalArticleId: e480ba5c-9f2c-49ff-b238-1e907b2c61ce
-redirect_from:
-  - /2021080/docs/processtimedoutexception-after-queuetaskstart
-  - /2021080/docs/en/processtimedoutexception-after-queuetaskstart
-  - /docs/processtimedoutexception-after-queuetaskstart
-  - /docs/en/processtimedoutexception-after-queuetaskstart
-  - /v6/docs/processtimedoutexception-after-queuetaskstart
-  - /v6/docs/en/processtimedoutexception-after-queuetaskstart
-related:
-  - title: A command fails with a `Killed` message
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/a-command-fails-with-a-killed-message.html
-  - title: Class Silex/ControllerProviderInterface not found
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/class-silex-controllerproviderinterface-not-found.html
-  - title: Composer version 2 compatibility issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/composer-version-2-compatibility-issues.html
-  - title: ERROR - remove spryker_logs - volume is in use
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-remove-spryker-logs-volume-is-in-use.html
-  - title: Error response from daemon - OCI runtime create failed - .... \\\"no such file or directory\\\"\""- unknown
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown.html
-  - title: Fail whale on the frontend
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-front-end.html
-  - title: No data on the Storefront
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/no-data-on-the-storefront.html
-  - title: PHPStan memory issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/phpstan-memory-issues.html
-  - title: RabbitMQ - Zed.CRITICAL- PhpAmqpLib\Exception\AMQPChannelClosedException - Channel connection is closed
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.html
-  - title: Router generates absolute URL with localhost
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/router-generates-absolute-url-with-localhost.html
-  - title: RuntimeException - Failed to execute regex - PREG_JIT_STACKLIMIT_ERROR
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error.html
-  - title: The spy_oms_transition_log table takes up too much space
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/the-spy-oms-transition-log-table-takes-up-too-much-space.html
-  - title: Unable to resolve hosts for Mail, Jenkins, and RabbitMQ
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq.html
----
-
-## Description
-After running `queue:task:start`, the following exception is thrown:
-
-```bash
-Symphony\Component\Process\Exception\ProcesstimedOutException - Exception: The process "/app/vendor/bin/console queue:task:start event" exeeded the timeout of 60 seconds in /app/vendor/symfony/process/Process.php (1335)
-```
-
-## Cause
-
-The problem occurs when the task runs for longer than the max execution time specified in the PHP settings.
-
-## Solution
-
-In the PHP settings, increase `max_execution_time`.
-If you use Docker, you can increase the max execution time in the *deploy.yml* file, for example:
-
-```yaml
-image:
-  tag: ...
-  php:
-    ini:
-      'max_execution_time': 300
-```
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.md b/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.md
deleted file mode 100644
index 1f590d4d429..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: RabbitMQ- Zed.CRITICAL- PhpAmqpLib\Exception\AMQPChannelClosedException - Channel connection is closed
-description: Learn how to fix the issue when events are not consumed or are consumed slowly.
-last_updated: May 3, 2023
-template: troubleshooting-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/rabbitmq-zedcritical-phpamqplibexceptionamqpchannelclosedexception-channel-connection-is-closed
-originalArticleId: 39daf8b8-9e73-4c76-a6ee-372d3e5bbca6
-redirect_from:
-  - /2021080/docs/rabbitmq-zedcritical-phpamqplibexceptionamqpchannelclosedexception-channel-connection-is-closed
-  - /2021080/docs/en/rabbitmq-zedcritical-phpamqplibexceptionamqpchannelclosedexception-channel-connection-is-closed
-  - /docs/rabbitmq-zedcritical-phpamqplibexceptionamqpchannelclosedexception-channel-connection-is-closed
-  - /docs/en/rabbitmq-zedcritical-phpamqplibexceptionamqpchannelclosedexception-channel-connection-is-closed
-  - /v6/docs/rabbitmq-zedcritical-phpamqplibexceptionamqpchannelclosedexception-channel-connection-is-closed
-  - /v6/docs/en/rabbitmq-zedcritical-phpamqplibexceptionamqpchannelclosedexception-channel-connection-is-closed
-related:
-  - title: A command fails with a `Killed` message
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/a-command-fails-with-a-killed-message.html
-  - title: Class Silex/ControllerProviderInterface not found
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/class-silex-controllerproviderinterface-not-found.html
-  - title: Composer version 2 compatibility issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/composer-version-2-compatibility-issues.html
-  - title: ERROR - remove spryker_logs - volume is in use
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-remove-spryker-logs-volume-is-in-use.html
-  - title: Error response from daemon - OCI runtime create failed - .... \\\"no such file or directory\\\"\""- unknown
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown.html
-  - title: Fail whale on the frontend
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-front-end.html
-  - title: No data on the Storefront
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/no-data-on-the-storefront.html
-  - title: PHPStan memory issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/phpstan-memory-issues.html
-  - title: ProcessTimedOutException after queue-task-start
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/processtimedoutexception-after-queue-task-start.html
-  - title: Router generates absolute URL with localhost
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/router-generates-absolute-url-with-localhost.html
-  - title: RuntimeException - Failed to execute regex - PREG_JIT_STACKLIMIT_ERROR
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error.html
-  - title: The spy_oms_transition_log table takes up too much space
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/the-spy-oms-transition-log-table-takes-up-too-much-space.html
-  - title: Unable to resolve hosts for Mail, Jenkins, and RabbitMQ
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq.html
----
-
-## Description
-
-Events are not consumed or are consumed much slower than normal. In RabbitMQ exception.log, the following exception can be found (often also with Broken Pipe reference):
-
-```php
-Zed.CRITICAL: PhpAmqpLib\Exception\AMQPChannelClosedException - Channel connection is closed.
-```
-
-## Cause
-
-There are several potential reasons for this error. The most common cause is that during P&S chunks take too much time to be processed and RabbitMQ is closing its TCP connection as it anticipates either a timeout or no further connection to happen.
-
-## Solution
-
-It is best to profile the job where you are experiencing this error to understand what exactly makes processing the chunks expensive. Temporary mitigation of the issue might be possible as explained below:
-
-**Adjusting CHUNK_SIZE**
-
-Using smaller chunk sizes might help to alleviate the issue because it reduces the time until a chunk is fully processed. If you are running a standard publishing setup, you can adjust the following value in `config_default.php`. 
-
-```php
-$config[EventConstants::EVENT_CHUNK] = 200;
-```
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/router-generates-absolute-url-with-localhost.md b/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/router-generates-absolute-url-with-localhost.md
deleted file mode 100644
index f0650cf9c83..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/router-generates-absolute-url-with-localhost.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: Router generates absolute URL with localhost
-description: Learn how to fix the issue when router generates URLs with an absolute path instead of a relative one
-last_updated: Jun 16, 2021
-template: troubleshooting-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/router-generates-absolute-url-with-localhost
-originalArticleId: d9195e61-e421-4623-88bf-343a48b2d707
-redirect_from:
-  - /2021080/docs/router-generates-absolute-url-with-localhost
-  - /2021080/docs/en/router-generates-absolute-url-with-localhost
-  - /docs/router-generates-absolute-url-with-localhost
-  - /docs/en/router-generates-absolute-url-with-localhost
-  - /v6/docs/router-generates-absolute-url-with-localhost
-  - /v6/docs/en/router-generates-absolute-url-with-localhost
-related:
-  - title: A command fails with a `Killed` message
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/a-command-fails-with-a-killed-message.html
-  - title: Class Silex/ControllerProviderInterface not found
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/class-silex-controllerproviderinterface-not-found.html
-  - title: Composer version 2 compatibility issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/composer-version-2-compatibility-issues.html
-  - title: ERROR - remove spryker_logs - volume is in use
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-remove-spryker-logs-volume-is-in-use.html
-  - title: Error response from daemon - OCI runtime create failed - .... \\\"no such file or directory\\\"\""- unknown
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown.html
-  - title: Fail whale on the frontend
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-front-end.html
-  - title: No data on the Storefront
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/no-data-on-the-storefront.html
-  - title: PHPStan memory issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/phpstan-memory-issues.html
-  - title: ProcessTimedOutException after queue-task-start
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/processtimedoutexception-after-queue-task-start.html
-  - title: RabbitMQ - Zed.CRITICAL- PhpAmqpLib\Exception\AMQPChannelClosedException - Channel connection is closed
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.html
-  - title: RuntimeException - Failed to execute regex - PREG_JIT_STACKLIMIT_ERROR
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error.html
-  - title: The spy_oms_transition_log table takes up too much space
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/the-spy-oms-transition-log-table-takes-up-too-much-space.html
-  - title: Unable to resolve hosts for Mail, Jenkins, and RabbitMQ
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq.html
----
-
-Router generates URLs with an absolute path instead of a relative one.
-
-## Cause
-
-Prior to version 1.9.0 of the [Router](https://github.com/spryker/router) module, Spryker did not set the `RequestContext` properly in `ChainRouter`. This led to an issue that URLs were generated with an absolute path instead of a relative one. This silently happens inside Symfony's router when the host retrieved from `RequestContext` doesn't match the one that the resolved route has.
-
-## Solution
-
-Do the following:
-
-1. Update the [Router](https://github.com/spryker/router) module to at least version 1.9.0.
-2. Set `RequestContext` as follows: Extend `\Spryker\Yves\Router\Router\ChainRouter` in your project, add a new `addRequestContext()` method to it and call that method in the constructor of that class.
-
-```php
-/**
- * @param \Symfony\Component\Routing\RequestContext|null $requestContext
- *
- * @return void
- */
-protected function addRequestContext(?RequestContext $requestContext = null): void
-{
-    $request = Request::createFromGlobals();
-
-    if (!$requestContext) {
-        $requestContext = new RequestContext();
-    }
-    $requestContext->fromRequest($request);
-
-    $this->setContext($requestContext);
-}
-
-```
-
-3. Update the constructor:
-
-```php
-/**
- * @param \Spryker\Yves\RouterExtension\Dependency\Plugin\RouterPluginInterface[] $routerPlugins
- * @param \Psr\Log\LoggerInterface|null $logger
- * @param \Symfony\Component\Routing\RequestContext|null $requestContext
- */
-public function __construct(array $routerPlugins, ?LoggerInterface $logger = null, ?RequestContext $requestContext = null)
-{
-    parent::__construct($logger);
-
-    $this->addRequestContext($requestContext);
-    $this->addRouterPlugins($routerPlugins);
-}
-```
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error.md b/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error.md
deleted file mode 100644
index e4b63024ec3..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: RuntimeException- Failed to execute regex- PREG_JIT_STACKLIMIT_ERROR
-description: This troubleshooting guide will help you to fix the error `RuntimeException- Failed to execute regex- PREG_JIT_STACKLIMIT_ERROR`.
-last_updated: Jun 16, 2021
-template: troubleshooting-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error
-originalArticleId: 53d95154-60db-40db-b4b8-6e0c4ae9233b
-redirect_from:
-  - /2021080/docs/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error
-  - /2021080/docs/en/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error
-  - /docs/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error
-  - /docs/en/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error
-  - /v6/docs/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error
-  - /v6/docs/en/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error
-related:
-  - title: A command fails with a `Killed` message
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/a-command-fails-with-a-killed-message.html
-  - title: Class Silex/ControllerProviderInterface not found
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/class-silex-controllerproviderinterface-not-found.html
-  - title: Composer version 2 compatibility issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/composer-version-2-compatibility-issues.html
-  - title: ERROR - remove spryker_logs - volume is in use
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-remove-spryker-logs-volume-is-in-use.html
-  - title: Error response from daemon - OCI runtime create failed - .... \\\"no such file or directory\\\"\""- unknown
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown.html
-  - title: Fail whale on the frontend
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-front-end.html
-  - title: No data on the Storefront
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/no-data-on-the-storefront.html
-  - title: PHPStan memory issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/phpstan-memory-issues.html
-  - title: ProcessTimedOutException after queue-task-start
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/processtimedoutexception-after-queue-task-start.html
-  - title: RabbitMQ - Zed.CRITICAL- PhpAmqpLib\Exception\AMQPChannelClosedException - Channel connection is closed
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.html
-  - title: Router generates absolute URL with localhost
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/router-generates-absolute-url-with-localhost.html
-  - title: The spy_oms_transition_log table takes up too much space
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/the-spy-oms-transition-log-table-takes-up-too-much-space.html
-  - title: Unable to resolve hosts for Mail, Jenkins, and RabbitMQ
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq.html
----
-
-## Description
-```bash
-[RuntimeException]                                  
-Failed to execute regex: PREG_JIT_STACKLIMIT_ERROR
-```
-
-This error is received when using composer (`composer require`) to add additional modules.
-
-## Cause
-The error is thrown if the [backtracking/recursion limit](https://www.php.net/manual/en/pcre.configuration.php) is not high enough.
-
-## Solution
-Either increase the limits to your requirements or switch off PCRE's just-in-time compilation in your php.ini:
-```bash
-pcre.jit=0
-```
-You can also switch off PCRE just in time compilation using your `deploy.yml`.
-```bash
-image:
-  tag: ...
-  php:
-    ini:
-      'pcre.jit': 0
-```
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/the-spy-oms-transition-log-table-takes-up-too-much-space.md b/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/the-spy-oms-transition-log-table-takes-up-too-much-space.md
deleted file mode 100644
index 419379e8fdf..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/the-spy-oms-transition-log-table-takes-up-too-much-space.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: The spy_oms_transition_log table takes up too much space
-description: Configure transition logs to be removed automatically.
-last_updated: Jun 16, 2021
-template: troubleshooting-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/the-spy-oms-transition-log-table-takes-up-too-much-space
-originalArticleId: 5c025e16-bfc2-4dcf-ba35-137044daa486
-redirect_from:
-  - /2021080/docs/the-spy-oms-transition-log-table-takes-up-too-much-space
-  - /2021080/docs/en/the-spy-oms-transition-log-table-takes-up-too-much-space
-  - /docs/the-spy-oms-transition-log-table-takes-up-too-much-space
-  - /docs/en/the-spy-oms-transition-log-table-takes-up-too-much-space
-  - /v6/docs/the-spy-oms-transition-log-table-takes-up-too-much-space
-  - /v6/docs/en/the-spy-oms-transition-log-table-takes-up-too-much-space
-related:
-  - title: A command fails with a `Killed` message
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/a-command-fails-with-a-killed-message.html
-  - title: Class Silex/ControllerProviderInterface not found
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/class-silex-controllerproviderinterface-not-found.html
-  - title: Composer version 2 compatibility issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/composer-version-2-compatibility-issues.html
-  - title: ERROR - remove spryker_logs - volume is in use
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-remove-spryker-logs-volume-is-in-use.html
-  - title: Error response from daemon - OCI runtime create failed - .... \\\"no such file or directory\\\"\""- unknown
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown.html
-  - title: Fail whale on the frontend
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-front-end.html
-  - title: No data on the Storefront
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/no-data-on-the-storefront.html
-  - title: PHPStan memory issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/phpstan-memory-issues.html
-  - title: ProcessTimedOutException after queue-task-start
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/processtimedoutexception-after-queue-task-start.html
-  - title: RabbitMQ - Zed.CRITICAL - PhpAmqpLib\Exception\AMQPChannelClosedException - Channel connection is closed
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.html
-  - title: Router generates absolute URL with localhost
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/router-generates-absolute-url-with-localhost.html
-  - title: RuntimeException - Failed to execute regex - PREG_JIT_STACKLIMIT_ERROR
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error.html
-  - title: Unable to resolve hosts for Mail, Jenkins, and RabbitMQ
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq.html
----
-
-The `spy_oms_transition_log` table stores the history of order management system transitions. The logs are kept for debugging reasons. If you don't need them or you have backed them up, you can remove them.
-
-{% info_block errorBox "Manipulating tables" %}
-
-Table manipulations can affect a shop greatly. It is not safe to do so, and we recommend double-checking all the details before you proceed. The instructions below can help you solve a storage space issue. Make sure to follow them exactly.
-
-{% endinfo_block %}
-
-## Cause
-
-By default, nothing limits the table size or deletes old records.
-
-## Solution
-
-Schedule the following SQL query to delete all the logs older than 90 days. You can adjust the time interval per your requirements.
-
-```sql
-DELETE FROM
-	spy_oms_transition_log
-WHERE
-	created_at < CURRENT_DATE - interval '90' day;
-```
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-general-technical-issues.md b/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-general-technical-issues.md
deleted file mode 100644
index 98657393a0e..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-general-technical-issues.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-title: Troubleshooting general technical issues
-description: Troubleshoot general technical issues you might encounter when running your Spryker-based project
-last_updated: Jun 16, 2021
-template: troubleshooting-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/troubleshooting-general-technical-issues
-originalArticleId: b625da8e-d503-4450-90d2-ff1297d3a809
-redirect_from:
-  - /2021080/docs/troubleshooting-general-technical-issues
-  - /2021080/docs/en/troubleshooting-general-technical-issues
-  - /docs/troubleshooting-general-technical-issues
-  - /docs/en/troubleshooting-general-technical-issues
-  - /v6/docs/troubleshooting-general-technical-issues
-  - /v6/docs/en/troubleshooting-general-technical-issues
-  - /docs/general-troubleshooting
-related:
-  - title: A command fails with a `Killed` message
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/a-command-fails-with-a-killed-message.html
-  - title: Class Silex/ControllerProviderInterface not found
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/class-silex-controllerproviderinterface-not-found.html
-  - title: Composer version 2 compatibility issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/composer-version-2-compatibility-issues.html
-  - title: ERROR - remove spryker_logs - volume is in use
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-remove-spryker-logs-volume-is-in-use.html
-  - title: Error response from daemon - OCI runtime create failed - .... \\\"no such file or directory\\\"\""- unknown
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown.html
-  - title: Fail whale on the frontend
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-front-end.html
-  - title: No data on the Storefront
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/no-data-on-the-storefront.html
-  - title: PHPStan memory issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/phpstan-memory-issues.html
-  - title: ProcessTimedOutException after queue-task-start
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/processtimedoutexception-after-queue-task-start.html
-  - title: RabbitMQ - Zed.CRITICAL - PhpAmqpLib\Exception\AMQPChannelClosedException - Channel connection is closed
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.html
-  - title: Router generates absolute URL with localhost
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/router-generates-absolute-url-with-localhost.html
-  - title: RuntimeException - Failed to execute regex - PREG_JIT_STACKLIMIT_ERROR
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error.html
-  - title: The spy_oms_transition_log table takes up too much space
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/the-spy-oms-transition-log-table-takes-up-too-much-space.html
-  - title: Unable to resolve hosts for Mail, Jenkins, and RabbitMQ
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq.html
----
-
-This section helps you troubleshoot general technical issues you might encounter when running your Spryker-based project.
-
-## Topics
-
-* [A command fails with a `Killed` message](/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/a-command-fails-with-a-killed-message.html)
-* [Class Silex/ControllerProviderInterface not found](/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/class-silex-controllerproviderinterface-not-found.html)
-* [Unable to resolve hosts for Mail, Jenkins, and RabbitMQ](/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq.html)
-* [RabbitMQ: Zed.CRITICAL: PhpAmqpLib\Exception\AMQPChannelClosedException - Channel connection is closed](/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.html)
-* [ProcessTimedOutException after queue:task:start](/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/processtimedoutexception-after-queue-task-start.html)
-* [RuntimeException: Failed to execute regex: PREG_JIT_STACKLIMIT_ERROR](/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error.html)
-* [The spy_oms_transition_log table takes up too much space](/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/the-spy-oms-transition-log-table-takes-up-too-much-space.html)
-* [ERROR: remove spryker_logs: volume is in use](/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-remove-spryker-logs-volume-is-in-use.html)
-* [Fail whale on the front end](/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-frontend.html)
-* [No data on the Storefront](/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/no-data-on-the-storefront.html)
-* [Error response from daemon: OCI runtime create failed: .... \\\"no such file or directory\\\"\"": unknown](/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown.html)
-* [Composer version 2 compatibility issues](/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/composer-version-2-compatibility-issues.html)
-* [Router generates absolute URL with localhost](/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/router-generates-absolute-url-with-localhost.html)
-* [PHPStan memory issues](/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/phpstan-memory-issues.html)
-
-
-{% info_block infoBox %}
-
-If you encounter a general technical issue that is not addressed on this page, try searching by an error output or keywords, or visit the [Spryker Support Portal](https://spryker.force.com/support/s/) for technical support.
-
-If you found a solution to a repetitive issue, please suggest a change to this page by clicking the **Edit or Report** button.
-
-{% endinfo_block %}
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/troubleshooting-rabbitmq.md b/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/troubleshooting-rabbitmq.md
deleted file mode 100644
index c2be801ef5a..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/troubleshooting-rabbitmq.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: Troubleshooting RabbitMQ
-description: Troubleshoot RabbitMQ issues
-template: concept-topic-template
-last_updated: May 2, 2023
----
-
-This section helps you troubleshoot issues related to RabbitMQ.
-
-## Topics
-- [Messages are moved to error queues](/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-moved-to-error-queues.html)
-- [Messages are stuck in the Unacked state](/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-stuck-in-the-unacked-state.html)
-- [Messages are stuck without error notifications](/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/messages-are-stuck-without-error-notifications.html)
diff --git a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq.md b/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq.md
deleted file mode 100644
index 15e4f0b19cb..00000000000
--- a/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: Unable to resolve hosts for Mail, Jenkins, and RabbitMQ
-description: Learn how to fix the issue with unresolved hosts for Mail, Jenkins, and RabbitMQ on Windows
-last_updated: Jun 16, 2021
-template: troubleshooting-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq
-originalArticleId: bbddc907-8edc-4e0f-b880-b67381364801
-redirect_from:
-  - /2021080/docs/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq
-  - /2021080/docs/en/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq
-  - /docs/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq
-  - /docs/en/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq
-  - /v6/docs/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq
-  - /v6/docs/en/unable-to-resolve-hosts-for-mail-jenkins-and-rabbitmq
-related:
-  - title: A command fails with a `Killed` message
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/a-command-fails-with-a-killed-message.html
-  - title: Class Silex/ControllerProviderInterface not found
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/class-silex-controllerproviderinterface-not-found.html
-  - title: Composer version 2 compatibility issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/composer-version-2-compatibility-issues.html
-  - title: ERROR - remove spryker_logs - volume is in use
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-remove-spryker-logs-volume-is-in-use.html
-  - title: Error response from daemon - OCI runtime create failed - .... \\\"no such file or directory\\\"\""- unknown
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/error-response-from-daemon-oci-runtime-create-failed-no-such-file-or-directory-unknown.html
-  - title: Fail whale on the frontend
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/fail-whale-on-the-front-end.html
-  - title: No data on the Storefront
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/no-data-on-the-storefront.html
-  - title: PHPStan memory issues
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/phpstan-memory-issues.html
-  - title: ProcessTimedOutException after queue-task-start
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/processtimedoutexception-after-queue-task-start.html
-  - title: RabbitMQ - Zed.CRITICAL - PhpAmqpLib\Exception\AMQPChannelClosedException - Channel connection is closed
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.html
-  - title: Router generates absolute URL with localhost
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/router-generates-absolute-url-with-localhost.html
-  - title: RuntimeException - Failed to execute regex - PREG_JIT_STACKLIMIT_ERROR
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/runtimeexception-failed-to-execute-regex-preg-jit-stacklimit-error.html
-  - title: The spy_oms_transition_log table takes up too much space
-    link: docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/the-spy-oms-transition-log-table-takes-up-too-much-space.html
----
-
-## Description
-
-The issue occurs when setting up Docker and WSL 2 and adding routes to `etc/hosts` in one line on Windows. Host file has row 127.0.0.1.
-
-## Cause
-
-The cause of the issue might be in the maximum length limitaion of a line that you can have in your hosts file in Windows.
-
-## Solution
-
-In the hosts file, start a new line with `127.0.0.1`, and then add routes for services for which the hosts are not resolved.
diff --git a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/general-rules-and-guidance-for-adding-new-documents.md b/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/general-rules-and-guidance-for-adding-new-documents.md
index 5123d9e02ea..0844cc4cda1 100644
--- a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/general-rules-and-guidance-for-adding-new-documents.md
+++ b/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/general-rules-and-guidance-for-adding-new-documents.md
@@ -63,7 +63,7 @@ To keep our docs consistent, we have templates for all types of documents. The t
 | [data-export-template](https://github.com/spryker/spryker-docs/blob/master/_templates/data-export-template.md) | Use this template for creating documents on [data export](/docs/pbc/all/order-management-system/{{site.version}}/base-shop/import-and-export-data/orders-data-export/export-file-details-orders.csv.html). |
 | [data-import-template](https://github.com/spryker/spryker-docs/blob/master/_templates/data-import-template.md) | Use this template for creating documents on [data import](/docs/pbc/all/merchant-management/{{site.version}}/marketplace/import-and-export-data/import-file-details-merchant-category.csv.html). |
 | [module-migration-guide-template](https://github.com/spryker/spryker-docs/blob/master/_templates/module-migration-guide-template.md) | Use this template for creating [module migration guides](/docs/pbc/all/merchant-management/{{site.version}}/base-shop/install-and-upgrade/upgrade-the-merchantgui-module.html#upgrading-from-version-1-to-version-2). |
-| [troubleshooting-guide-template](https://github.com/spryker/spryker-docs/blob/master/_templates/troubleshooting-guide-template.md) | Use this template for creating [troubleshooting pages](/docs/scos/dev/troubleshooting/troubleshooting-general-technical-issues/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.html). |
+| [troubleshooting-guide-template](https://github.com/spryker/spryker-docs/blob/master/_templates/troubleshooting-guide-template.md) | Use this template for creating [troubleshooting pages](/docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-rabbitmq/rabbitmq-zed.critical-phpamqplib-exception-amqpchannelclosedexception-channel-connection-is-closed.html). |
 | [howto-guide-template](https://github.com/spryker/spryker-docs/blob/master/_templates/howto-guide-template.md) | Use this template for creating [howto guides](/docs/pbc/all/cart-and-checkout/{{site.version}}/base-shop/tutorials-and-howtos/add-additional-countries-to-checkout.html). |
 | [best-practices-file-template](https://github.com/spryker/spryker-docs/blob/master/_templates/best-practices-file-template.md) | Use this template for creating [best practices](/docs/scos/user/back-office-user-guides/{{site.version}}/catalog/products/creating-service-offerings-best-practices.html) docs. |
 
diff --git a/docs/scos/user/intro-to-spryker/intro-to-spryker.md b/docs/scos/user/intro-to-spryker/intro-to-spryker.md
index 78602b17077..582bed396a3 100644
--- a/docs/scos/user/intro-to-spryker/intro-to-spryker.md
+++ b/docs/scos/user/intro-to-spryker/intro-to-spryker.md
@@ -106,4 +106,4 @@ This documentation site contains lots of information on Spryker Commerce OS. Sel
 * [Setup](/docs/dg/dev/set-up-spryker-locally/set-up-spryker-locally.html): installation of Spryker.
 * [Packaged Business Capabilities](/docs/pbc/all/pbc.html): catalogue of functionality and related guides.
 * [Glue REST API](/docs/dg/dev/glue-api/{{site.version}}/old-glue-infrastructure/glue-rest-api.html): Spryker Glue REST API overview, reference, and features.
-* [Developer Guides](/docs/scos/dev/developer-getting-started-guide.html): technical information and guides for developers.
+* [Developer Guides](/docs/dg/dev/development-getting-started-guide.html): technical information and guides for developers.
diff --git a/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/release-notes-202212.0.md b/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/release-notes-202212.0.md
index 3df70da5eee..670d9d90877 100644
--- a/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/release-notes-202212.0.md
+++ b/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/release-notes-202212.0.md
@@ -10,7 +10,7 @@ redirect_from:
 
 The Spryker Commerce OS is an end-to-end solution for digital commerce. This document contains a business-level description of new features and enhancements.
 
-For information about installing the Spryker Commerce OS, see [Getting started guide](/docs/scos/dev/developer-getting-started-guide.html).
+For information about installing the Spryker Commerce OS, see [Getting started guide](/docs/dg/dev/development-getting-started-guide.html).
 
 ## Spryker Commerce OS
 
diff --git a/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202307.0/release-notes-202307.0.md b/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202307.0/release-notes-202307.0.md
index b7dd934b97b..76415f7e7b1 100644
--- a/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202307.0/release-notes-202307.0.md
+++ b/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202307.0/release-notes-202307.0.md
@@ -7,7 +7,7 @@ template: concept-topic-template
 
 The Spryker Commerce OS is an end-to-end solution for digital commerce. This document contains a business-level description of new features and enhancements.
 
-For information about installing the Spryker Commerce OS, see [Getting started guide](/docs/scos/dev/developer-getting-started-guide.html).
+For information about installing the Spryker Commerce OS, see [Getting started guide](/docs/dg/dev/development-getting-started-guide.html).
 
 ## Spryker Commerce OS
 
diff --git a/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202311.0/release-notes-202311.0.md b/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202311.0/release-notes-202311.0.md
index d717f4ed9f7..a2519293017 100644
--- a/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202311.0/release-notes-202311.0.md
+++ b/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202311.0/release-notes-202311.0.md
@@ -9,7 +9,7 @@ redirect_from:
 
 The Spryker Commerce OS is an end-to-end solution for digital commerce. This document contains a business-level description of new features and enhancements.
 
-For information about installing the Spryker Commerce OS, see [Getting started guide](/docs/scos/dev/developer-getting-started-guide.html).
+For information about installing the Spryker Commerce OS, see [Getting started guide](/docs/dg/dev/development-getting-started-guide.html).
 
 ## <span class="inline-img">![core-commerce](https://spryker.s3.eu-central-1.amazonaws.com/docs/scos/user/intro-to-spryker/releases/release-notes/icon_Spryker+Commerce+OS_128.png)</span> Fulfillment App <span class="inline-img">![feature](https://spryker.s3.eu-central-1.amazonaws.com/docs/scos/user/intro-to-spryker/releases/release-notes/feature.png)</span>