From ffca5f0191169915c8349c55c580cfe1ed7340e2 Mon Sep 17 00:00:00 2001
From: Andrii Tserkovnyi <andrii.tserkovnyi@spryker.com>
Date: Fri, 1 Mar 2024 15:05:22 +0200
Subject: [PATCH 01/26] move docs

---
 .github/workflows/ci.yml                      |  10 +-
 Rakefile                                      |  19 +-
 _config.yml                                   |  19 +-
 ...user_sidebar.yml => about_all_sidebar.yml} |   8 +-
 _includes/topnav.html                         |  18 +-
 _layouts/home.html                            |   2 +-
 .../redirect_from_generator.sh                |   2 +-
 .../redirects_generator.sh                    |   4 +-
 .../about-spryker-documentation.md            |   0
 ...dd-global-sections-to-the-documentation.md | 215 +-------
 ...-and-edit-diagrams-in-the-documentation.md |   3 +
 .../contribute-to-the-documentation.md        |   6 +-
 .../edit-the-documentation-locally.md         |   2 +
 ...it-the-documentation-via-pull-requests.md} |   4 +-
 .../report-documentation-issues.md            |   2 +
 .../review-pull-requests.md                   |   5 +-
 .../install-recommended-vs-code-extensions.md |  11 +-
 .../run-the-documentation-locally.md}         |  35 +-
 .../examples.md                               |   3 +
 ...ules-and-guidance-for-adding-documents.md} |   4 +-
 .../markdown-syntax.md                        |  24 +-
 .../spelling.md                               |   3 +
 .../spryker-documentation-style-guide.md      |   3 +
 .../word-list.md                              |   3 +
 .../all}/b2b-suite.md                         |   1 +
 .../all}/b2c-suite.md                         |   1 +
 .../all}/docs-updates.md                      |   1 +
 .../intro-to-spryker => about/all}/faq.md     |   1 +
 .../all}/intro-to-spryker.md                  |   1 +
 .../all}/master-suite.md                      |   1 +
 .../all}/mvp-project-structuring.md           |   1 +
 .../release-notes-202211.0.md                 |   1 +
 .../patch-releases-202212.0.md                |   1 +
 .../release-notes-202212.0.md                 |   1 +
 .../security-release-notes-202212.0.md        |   2 +
 .../security-release-notes-202302.0.md        |   4 +-
 .../security-release-notes-202304.0.md        |   2 +
 .../release-notes-202307.0.md                 |   2 +
 .../security-release-notes-202307.0.md        |   2 +
 .../release-notes-202311.0.md                 |   1 +
 .../releases/release-notes/release-notes.md   |   1 +
 .../security-release-notes-202306.0.md        |   1 +
 .../security-release-notes-202309.0.md        |   4 +-
 .../security-release-notes-202312.0.md        |   2 +
 .../all}/releases/releases.md                 |   1 +
 .../all}/spryker-academy.md                   |   4 +-
 .../back-office-for-marketplace-operator.md   |   1 +
 .../marketplace-b2b-suite.md                  |   1 +
 .../marketplace-b2c-suite.md                  |   1 +
 .../marketplace-concept.md                    |   1 +
 .../marketplace-personas.md                   |   1 +
 .../marketplace-storefront.md                 |   1 +
 .../merchant-onboarding.md                    |   1 +
 .../spryker-marketplace/merchant-portal.md    |   1 +
 .../spryker-marketplace.md                    |   1 +
 .../all}/spryker-release-process.md           |   3 +-
 .../all}/support/case-escalation.md           |   3 +-
 .../all}/support/escalations.md               |   1 +
 .../all}/support/getting-support.md           |   1 +
 .../support/guidelines-for-new-gdpr-rules.md  |   1 +
 .../all}/support/handling-security-issues.md  |   1 +
 .../all}/support/how-spryker-support-works.md |   1 +
 .../support/how-to-contact-spryker-support.md |   1 +
 ...-to-get-the-most-out-of-spryker-support.md |   1 +
 ...e-secrets-with-the-spryker-support-team.md |   1 +
 .../support/how-to-use-the-support-portal.md  |   1 +
 .../special-prepare-for-a-busy-season.md      |   1 +
 .../all}/support/understand-slas.md           |   1 +
 ...erstanding-project-and-core-level-fixes.md |   2 +-
 .../support/understanding-ticket-status.md    |   1 +
 .../all}/supported-browsers.md                |   2 +
 .../all}/whats-new/ie11-end-of-life.md        |   2 +
 ...inimum-version-for-all-spryker-projects.md |   2 +
 .../2019.11-security-audit-by-sektioneins.md  |   3 +-
 ...ion-test-by-port-zero-executive-summary.md |   2 +-
 .../all}/whats-new/security-updates.md        |   1 +
 .../whats-new/supported-versions-of-php.md    |   1 +
 .../upcoming-major-module-releases.md         |   1 +
 .../all}/whats-new/whats-new.md               |   1 +
 .../202204.0/customer-service/dixa.md         |  44 --
 .../202204.0/customer-service/iadvize.md      |  47 --
 .../customer-service/live-chat-service.md     |  60 ---
 .../202204.0/customer-service/optimise-it.md  |  43 --
 .../finance-and-accounting/collectai.md       |  45 --
 .../finance-and-accounting/nitrobox.md        |  34 --
 .../202204.0/hosting-providers/claranet.md    |  44 --
 .../202204.0/hosting-providers/continum.md    |  44 --
 .../202204.0/hosting-providers/heroku.md      |  28 -
 .../202204.0/hosting-providers/metaways.md    |  41 --
 .../202204.0/hosting-providers/root-360.md    |  42 --
 .../ab-testing-and-performance/ab-tasty.md    |  45 --
 .../ab-testing-and-performance/baqend.md      |  27 -
 .../analytics/channelpilot-analytics.md       |  42 --
 .../analytics/fact-finder.md                  |  68 ---
 .../analytics/haensel-ams.md                  |  32 --
 .../analytics/mindlab.md                      |  45 --
 .../analytics/minubo.md                       |  46 --
 .../customer-communication/dotdigital.md      |  50 --
 .../customer-communication/episerver.md       |  54 --
 .../customer-communication/inxmail.md         |  56 --
 .../customer-retention-and-loyalty/namogoo.md |  43 --
 .../trustpilot.md                             |  43 --
 .../customer-retention-and-loyalty/zenloop.md |  43 --
 .../8select.md                                |  32 --
 .../contentserv.md                            |  24 -
 .../econda.md                                 |  52 --
 .../nosto.md                                  |  49 --
 .../personalization-and-cross-selling/trbo.md |  45 --
 .../channelpilot-marketplace.md               |  43 --
 .../common-solutions.md                       |  28 -
 .../data-virtuality.md                        |  46 --
 .../loggly.md                                 |  39 --
 .../mindcurv.md                               |  28 -
 .../new-relic.md                              |  32 --
 .../plusserver.md                             |  45 --
 .../proclane.md                               |  47 --
 .../shopmacher.md                             |  25 -
 .../tideways.md                               |  47 --
 .../usercentrics.md                           |  44 --
 .../vshn.md                                   |  47 --
 .../order-management-erpoms/nekom-cc-gmbh.md  |  37 --
 .../order-management-erpoms/tradebyte.md      |  42 --
 .../202204.0/payment-partners/adyen.md        |  45 --
 .../202204.0/payment-partners/afterpay.md     |  58 --
 .../202204.0/payment-partners/amazon-pay.md   |  53 --
 .../202204.0/payment-partners/arvato.md       |  40 --
 .../202204.0/payment-partners/billie.md       |  48 --
 .../202204.0/payment-partners/billpay.md      |  64 ---
 .../202204.0/payment-partners/braintree.md    |  69 ---
 .../payment-partners/bs-payone/bs-payone.md   | 436 ---------------
 ...tion-and-preauthorization-capture-flows.md |  63 ---
 .../payone-facade.md                          |  58 --
 ...ration-into-the-legacy-demoshop-project.md | 373 -------------
 .../payone-credit-card-payment.md             |  86 ---
 .../payone-direct-debit-payment.md            |  86 ---
 .../payone-invoice-payment.md                 |  51 --
 .../payone-online-transfer-payment.md         |  83 ---
 .../payone-paypal-express-checkout-payment.md | 136 -----
 .../payone-paypal-payment.md                  |  61 ---
 .../payone-prepayment.md                      |  54 --
 .../payone-security-invoice-payment.md        |  48 --
 ...-machine-commands-conditions-and-events.md |  53 --
 .../payone-cash-on-delivery.md                |  96 ----
 ...ayone-integration-into-the-scos-project.md | 499 ------------------
 .../payone-paypal-express-checkout-payment.md | 136 -----
 .../payone-risk-check-and-address-check.md    | 320 -----------
 .../202204.0/payment-partners/computop.md     |  81 ---
 .../202204.0/payment-partners/crefopay.md     |  36 --
 .../202204.0/payment-partners/heidelpay.md    |  46 --
 .../202204.0/payment-partners/klarna.md       |  79 ---
 .../202204.0/payment-partners/payolution.md   |  53 --
 .../202204.0/payment-partners/powerpay.md     |  51 --
 .../ratenkauf-by-easycredit.md                |  43 --
 .../202204.0/payment-partners/ratepay.md      |  79 ---
 .../202204.0/technology-partners.md           | 122 -----
 155 files changed, 182 insertions(+), 5727 deletions(-)
 rename _data/sidebars/{scos_user_sidebar.yml => about_all_sidebar.yml} (99%)
 create mode 100644 docs/about/all/about-the-documentation/about-spryker-documentation.md
 rename docs/{scos/user/intro-to-spryker/contribute-to-the-documentation => about/all/about-the-documentation}/add-global-sections-to-the-documentation.md (64%)
 rename docs/{scos/user/intro-to-spryker => about/all/about-the-documentation}/contribute-to-the-documentation/add-and-edit-diagrams-in-the-documentation.md (95%)
 rename docs/{scos/user/intro-to-spryker => about/all/about-the-documentation}/contribute-to-the-documentation/contribute-to-the-documentation.md (91%)
 rename docs/{scos/user/intro-to-spryker => about/all/about-the-documentation}/contribute-to-the-documentation/edit-the-documentation-locally.md (97%)
 rename docs/{scos/user/intro-to-spryker/contribute-to-the-documentation/edit-documentation-via-pull-requests.md => about/all/about-the-documentation/contribute-to-the-documentation/edit-the-documentation-via-pull-requests.md} (97%)
 rename docs/{scos/user/intro-to-spryker => about/all/about-the-documentation}/contribute-to-the-documentation/report-documentation-issues.md (94%)
 rename docs/{scos/user/intro-to-spryker => about/all/about-the-documentation}/contribute-to-the-documentation/review-pull-requests.md (97%)
 rename docs/{scos/user/intro-to-spryker/contribute-to-the-documentation => about/all/about-the-documentation}/install-recommended-vs-code-extensions.md (94%)
 rename docs/{scos/user/intro-to-spryker/contribute-to-the-documentation/build-the-documentation-site.md => about/all/about-the-documentation/run-the-documentation-locally.md} (95%)
 rename docs/{scos/user/intro-to-spryker/contribute-to-the-documentation => about/all/about-the-documentation}/spryker-documentation-style-guide/examples.md (90%)
 rename docs/{scos/user/intro-to-spryker/contribute-to-the-documentation/general-rules-and-guidance-for-adding-new-documents.md => about/all/about-the-documentation/spryker-documentation-style-guide/general-rules-and-guidance-for-adding-documents.md} (99%)
 rename docs/{scos/user/intro-to-spryker/contribute-to-the-documentation => about/all/about-the-documentation/spryker-documentation-style-guide}/markdown-syntax.md (98%)
 rename docs/{scos/user/intro-to-spryker/contribute-to-the-documentation => about/all/about-the-documentation}/spryker-documentation-style-guide/spelling.md (67%)
 rename docs/{scos/user/intro-to-spryker/contribute-to-the-documentation => about/all/about-the-documentation}/spryker-documentation-style-guide/spryker-documentation-style-guide.md (86%)
 rename docs/{scos/user/intro-to-spryker/contribute-to-the-documentation => about/all/about-the-documentation}/spryker-documentation-style-guide/word-list.md (88%)
 rename docs/{scos/user/intro-to-spryker => about/all}/b2b-suite.md (99%)
 rename docs/{scos/user/intro-to-spryker => about/all}/b2c-suite.md (99%)
 rename docs/{scos/user/intro-to-spryker => about/all}/docs-updates.md (99%)
 rename docs/{scos/user/intro-to-spryker => about/all}/faq.md (99%)
 rename docs/{scos/user/intro-to-spryker => about/all}/intro-to-spryker.md (99%)
 rename docs/{scos/user/intro-to-spryker => about/all}/master-suite.md (96%)
 rename docs/{scos/user/intro-to-spryker => about/all}/mvp-project-structuring.md (99%)
 rename docs/{scos/user/intro-to-spryker => about/all}/releases/release-notes/release-notes-202211.0/release-notes-202211.0.md (90%)
 rename docs/{scos/user/intro-to-spryker => about/all}/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.md (82%)
 rename docs/{scos/user/intro-to-spryker => about/all}/releases/release-notes/release-notes-202212.0/release-notes-202212.0.md (98%)
 rename docs/{scos/user/intro-to-spryker => about/all}/releases/release-notes/release-notes-202212.0/security-release-notes-202212.0.md (99%)
 rename docs/{scos/user/intro-to-spryker => about/all}/releases/release-notes/release-notes-202302.0/security-release-notes-202302.0.md (98%)
 rename docs/{scos/user/intro-to-spryker => about/all}/releases/release-notes/release-notes-202304.0/security-release-notes-202304.0.md (99%)
 rename docs/{scos/user/intro-to-spryker => about/all}/releases/release-notes/release-notes-202307.0/release-notes-202307.0.md (99%)
 rename docs/{scos/user/intro-to-spryker => about/all}/releases/release-notes/release-notes-202307.0/security-release-notes-202307.0.md (93%)
 rename docs/{scos/user/intro-to-spryker => about/all}/releases/release-notes/release-notes-202311.0/release-notes-202311.0.md (99%)
 rename docs/{scos/user/intro-to-spryker => about/all}/releases/release-notes/release-notes.md (94%)
 rename docs/{scos/user/intro-to-spryker => about/all}/releases/release-notes/security-release-notes-202306.0.md (99%)
 rename docs/{scos/user/intro-to-spryker => about/all}/releases/release-notes/security-release-notes-202309.0.md (97%)
 rename docs/{scos/user/intro-to-spryker => about/all}/releases/release-notes/security-release-notes-202312.0.md (99%)
 rename docs/{scos/user/intro-to-spryker => about/all}/releases/releases.md (98%)
 rename docs/{scos/user/intro-to-spryker => about/all}/spryker-academy.md (99%)
 rename docs/{scos/user/intro-to-spryker => about/all}/spryker-marketplace/back-office-for-marketplace-operator.md (98%)
 rename docs/{scos/user/intro-to-spryker => about/all}/spryker-marketplace/marketplace-b2b-suite.md (95%)
 rename docs/{scos/user/intro-to-spryker => about/all}/spryker-marketplace/marketplace-b2c-suite.md (97%)
 rename docs/{scos/user/intro-to-spryker => about/all}/spryker-marketplace/marketplace-concept.md (97%)
 rename docs/{scos/user/intro-to-spryker => about/all}/spryker-marketplace/marketplace-personas.md (96%)
 rename docs/{scos/user/intro-to-spryker => about/all}/spryker-marketplace/marketplace-storefront.md (99%)
 rename docs/{scos/user/intro-to-spryker => about/all}/spryker-marketplace/merchant-onboarding.md (99%)
 rename docs/{scos/user/intro-to-spryker => about/all}/spryker-marketplace/merchant-portal.md (97%)
 rename docs/{scos/user/intro-to-spryker => about/all}/spryker-marketplace/spryker-marketplace.md (96%)
 rename docs/{scos/user/intro-to-spryker => about/all}/spryker-release-process.md (97%)
 rename docs/{scos/user/intro-to-spryker => about/all}/support/case-escalation.md (98%)
 rename docs/{scos/user/intro-to-spryker => about/all}/support/escalations.md (98%)
 rename docs/{scos/user/intro-to-spryker => about/all}/support/getting-support.md (96%)
 rename docs/{scos/user/intro-to-spryker => about/all}/support/guidelines-for-new-gdpr-rules.md (98%)
 rename docs/{scos/user/intro-to-spryker => about/all}/support/handling-security-issues.md (97%)
 rename docs/{scos/user/intro-to-spryker => about/all}/support/how-spryker-support-works.md (98%)
 rename docs/{scos/user/intro-to-spryker => about/all}/support/how-to-contact-spryker-support.md (95%)
 rename docs/{scos/user/intro-to-spryker => about/all}/support/how-to-get-the-most-out-of-spryker-support.md (98%)
 rename docs/{scos/user/intro-to-spryker => about/all}/support/how-to-share-secrets-with-the-spryker-support-team.md (96%)
 rename docs/{scos/user/intro-to-spryker => about/all}/support/how-to-use-the-support-portal.md (98%)
 rename docs/{scos/user/intro-to-spryker => about/all}/support/special-prepare-for-a-busy-season.md (98%)
 rename docs/{scos/user/intro-to-spryker => about/all}/support/understand-slas.md (99%)
 rename docs/{scos/user/intro-to-spryker => about/all}/support/understanding-project-and-core-level-fixes.md (95%)
 rename docs/{scos/user/intro-to-spryker => about/all}/support/understanding-ticket-status.md (98%)
 rename docs/{scos/user/intro-to-spryker => about/all}/supported-browsers.md (97%)
 rename docs/{scos/user/intro-to-spryker => about/all}/whats-new/ie11-end-of-life.md (96%)
 rename docs/{scos/user/intro-to-spryker => about/all}/whats-new/php8-as-a-minimum-version-for-all-spryker-projects.md (95%)
 rename docs/{scos/user/intro-to-spryker => about/all}/whats-new/security-audit-reports/2019.11-security-audit-by-sektioneins.md (96%)
 rename docs/{scos/user/intro-to-spryker => about/all}/whats-new/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.md (95%)
 rename docs/{scos/user/intro-to-spryker => about/all}/whats-new/security-updates.md (94%)
 rename docs/{scos/user/intro-to-spryker => about/all}/whats-new/supported-versions-of-php.md (99%)
 rename docs/{scos/user/intro-to-spryker => about/all}/whats-new/upcoming-major-module-releases.md (94%)
 rename docs/{scos/user/intro-to-spryker => about/all}/whats-new/whats-new.md (99%)
 delete mode 100644 docs/scos/user/technology-partners/202204.0/customer-service/dixa.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/customer-service/iadvize.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/customer-service/live-chat-service.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/customer-service/optimise-it.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/finance-and-accounting/collectai.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/finance-and-accounting/nitrobox.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/hosting-providers/claranet.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/hosting-providers/continum.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/hosting-providers/heroku.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/hosting-providers/metaways.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/hosting-providers/root-360.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/marketing-and-conversion/ab-testing-and-performance/ab-tasty.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/marketing-and-conversion/ab-testing-and-performance/baqend.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/marketing-and-conversion/analytics/channelpilot-analytics.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/marketing-and-conversion/analytics/fact-finder.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/marketing-and-conversion/analytics/haensel-ams.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/marketing-and-conversion/analytics/mindlab.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/marketing-and-conversion/analytics/minubo.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/marketing-and-conversion/customer-communication/dotdigital.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/marketing-and-conversion/customer-communication/episerver.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/marketing-and-conversion/customer-communication/inxmail.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/marketing-and-conversion/customer-retention-and-loyalty/namogoo.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/marketing-and-conversion/customer-retention-and-loyalty/trustpilot.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/marketing-and-conversion/customer-retention-and-loyalty/zenloop.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/marketing-and-conversion/personalization-and-cross-selling/8select.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/marketing-and-conversion/personalization-and-cross-selling/contentserv.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/marketing-and-conversion/personalization-and-cross-selling/econda.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/marketing-and-conversion/personalization-and-cross-selling/nosto.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/marketing-and-conversion/personalization-and-cross-selling/trbo.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/marketplace-integrations/channelpilot-marketplace.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/common-solutions.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/data-virtuality.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/loggly.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/mindcurv.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/new-relic.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/plusserver.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/proclane.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/shopmacher.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/tideways.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/usercentrics.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/vshn.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/order-management-erpoms/nekom-cc-gmbh.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/order-management-erpoms/tradebyte.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/adyen.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/afterpay.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/amazon-pay.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/arvato.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/billie.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/billpay.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/braintree.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/bs-payone.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-authorization-and-preauthorization-capture-flows.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-facade.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-integration-into-the-legacy-demoshop-project.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-credit-card-payment.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-direct-debit-payment.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-invoice-payment.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-online-transfer-payment.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-paypal-express-checkout-payment.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-paypal-payment.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-prepayment.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-security-invoice-payment.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-state-machine-commands-conditions-and-events.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/scos-integration/payone-cash-on-delivery.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/scos-integration/payone-integration-into-the-scos-project.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/scos-integration/payone-paypal-express-checkout-payment.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/scos-integration/payone-risk-check-and-address-check.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/computop.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/crefopay.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/heidelpay.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/klarna.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/payolution.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/powerpay.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/ratenkauf-by-easycredit.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/payment-partners/ratepay.md
 delete mode 100644 docs/scos/user/technology-partners/202204.0/technology-partners.md

diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index f56a9e793c4..65a284edd3c 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -89,8 +89,8 @@ jobs:
 
       - run: bundle exec rake check_scos_dev
 
-  link_validation_check_scos_user:
-    name: Links validation (check_scos_user)
+  link_validation_check_about_all:
+    name: Links validation (check_about_all)
     needs: jekyll_build
     runs-on: ubuntu-latest
 
@@ -108,14 +108,14 @@ jobs:
         uses: actions/cache@v2
         with:
           path: tmp/.htmlproofer
-          key: ${{ runner.os }}-check_scos_user-htmlproofer
+          key: ${{ runner.os }}-check_about_all-htmlproofer
 
       - uses: actions/download-artifact@v2
 
       - name: Unpack artifacts
         run: tar -xf build-result/result.tar.gz
 
-      - run: bundle exec rake check_scos_user
+      - run: bundle exec rake check_about_all
 
   link_validation_check_pbc:
     name: Links validation (check_pbc)
@@ -215,7 +215,7 @@ jobs:
           bundler-cache: true
 
       - run: bundle exec jekyll validate
-      
+
   deploy:
     runs-on: ubuntu-latest
     needs: jekyll_build
diff --git a/Rakefile b/Rakefile
index 523d64b823c..7ecd28bc7bd 100644
--- a/Rakefile
+++ b/Rakefile
@@ -86,6 +86,7 @@ task :check_ca do
     /docs\/scos\/.+/,
     /docs\/fes\/.+/,
     /docs\/pbc\/.+/,
+    /docs\/about\/.+/,
     /docs\/dg\/.+/,
     /docs\/acp\/.+/,
     /docs\/sdk\/.+/
@@ -102,7 +103,7 @@ task :check_scos_dev do
     /docs\/acp\/.+/,
     /docs\/sdk\/.+/,
     /docs\/dg\/.+/,
-    /docs\/scos\/user\/.+/,
+    /docs\/about\/.+/,
     /docs\/pbc\/.+/,
     /docs\/scos\/\w+\/[\w-]+\/201811\.0\/.+/,
     /docs\/scos\/\w+\/[\w-]+\/201903\.0\/.+/,
@@ -117,7 +118,7 @@ task :check_scos_dev do
   HTMLProofer.check_directory("./_site", options).run
 end
 
-task :check_scos_user do
+task :check_about_all do
   options = commonOptions.dup
   options[:ignore_files] = [
     /docs\/ca\/.+/,
@@ -126,16 +127,7 @@ task :check_scos_user do
     /docs\/fes\/.+/,
     /docs\/pbc\/.+/,
     /docs\/dg\/.+/,
-    /docs\/sdk\/.+/,
-    /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\/.+/
+    /docs\/sdk\/.+/
   ]
   HTMLProofer.check_directory("./_site", options).run
 end
@@ -144,6 +136,7 @@ task :check_pbc do
   options = commonOptions.dup
   options[:ignore_files] = [
     /docs\/scos\/.+/,
+    /docs\/about\/.+/,
     /docs\/sdk\/.+/,
     /docs\/ca\/.+/,
     /docs\/fes\/.+/,
@@ -165,6 +158,7 @@ task :check_sdk do
     /docs\/scos\/.+/,
     /docs\/ca\/.+/,
     /docs\/acp\/.+/,
+    /docs\/about\/.+/,
     /docs\/fes\/.+/,
     /docs\/pbc\/.+/,
     /docs\/dg\/.+/,
@@ -180,6 +174,7 @@ task :check_dg do
     /docs\/scos\/.+/,
     /docs\/ca\/.+/,
     /docs\/acp\/.+/,
+    /docs\/about\/.+/,    
     /docs\/fes\/.+/,
     /docs\/pbc\/.+/,
     /docs\/sdk\/.+/
diff --git a/_config.yml b/_config.yml
index 13682f8b147..4c7da7e17c2 100644
--- a/_config.yml
+++ b/_config.yml
@@ -92,12 +92,6 @@ defaults:
     values:
       sidebar: "scos_dev_sidebar"
       role: "dev"
-  -
-    scope:
-      path: "docs/scos/user"
-    values:
-      sidebar: "scos_user_sidebar"
-      role: "user"
   -
      scope:
        path: "docs/sdk"
@@ -148,6 +142,17 @@ defaults:
     values:
       sidebar: "pbc_all_sidebar"
       role: "all"
+  -
+     scope:
+       path: "docs/about"
+     values:
+       product: "about"
+  -
+    scope:
+      path: "docs/about/all"
+    values:
+      sidebar: "about_all_sidebar"
+      role: "all"
 
 versions:
   '202212.0': '202212.0'
@@ -210,9 +215,9 @@ sidebars:
   - ca_dev_sidebar
   - ca_devscu_sidebar
   - scos_dev_sidebar
-  - scos_user_sidebar
   - sdk_dev_sidebar
   - pbc_all_sidebar
+  - about_all_sidebar
   - dg_dev_sidebar
 
 description: "Spryker documentation center."
diff --git a/_data/sidebars/scos_user_sidebar.yml b/_data/sidebars/about_all_sidebar.yml
similarity index 99%
rename from _data/sidebars/scos_user_sidebar.yml
rename to _data/sidebars/about_all_sidebar.yml
index 4306ae18d02..603539a00eb 100644
--- a/_data/sidebars/scos_user_sidebar.yml
+++ b/_data/sidebars/about_all_sidebar.yml
@@ -1,8 +1,8 @@
----
-title: SCOS User Guides
+title: About Spryker
 entries:
-- product: SCOS
-  nested:
+  - product: About Spryker
+    nested:
+      - title:
   - title: Intro to Spryker
     url: /docs/scos/user/intro-to-spryker/intro-to-spryker.html
     nested:
diff --git a/_includes/topnav.html b/_includes/topnav.html
index 0841103056c..d13b08b8a0c 100644
--- a/_includes/topnav.html
+++ b/_includes/topnav.html
@@ -40,8 +40,8 @@
                                                 {% elsif page.product == 'scos' and page.role == 'dev' %}
                                                 SCOS developer guide
                                                 {% elsif page.product == 'scos' and page.role == 'user' %}
-                                                SCOS users guide
-                                                {% elsif page.product == 'sdk' and page.role == 'dev' %}
+                                                About Spryker
+                                                {% elsif page.product == 'about' and page.role == 'all' %}
                                                 Spryker SDK
                                                 {% else %}
                                                 Select a guide
@@ -59,6 +59,11 @@
                                               <a href="/docs/pbc/all/pbc.html" class="main-nav__drop-link">
                                               Packaged Business Capabilities [BETA]
                                               </a>
+                                          </li>
+                                          <li>
+                                              <a href="/docs/about/all/intro-to-spryker.html" class="main-nav__drop-link">
+                                              About Spryker
+                                              </a>
                                           </li>
                                             <li class="dropdown">
                                                 <a href="/" class="main-nav__drop-link dropdown-toggle" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">
@@ -75,15 +80,6 @@
                                                             <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 class="dropdown">
diff --git a/_layouts/home.html b/_layouts/home.html
index 64a97ff242f..773ce03c5c2 100644
--- a/_layouts/home.html
+++ b/_layouts/home.html
@@ -47,7 +47,7 @@ <h2 class="card__heading-title">Business User guides</h2>
                     </div>
                     <div class="card__footer">
                         <ul class="card__links">
-                            <li><a href="/docs/scos/user/intro-to-spryker/intro-to-spryker.html">SCOS user guides</a></li>
+                            <li><a href="/docs/about/all/intro-to-spryker.html">About Spryker</a></li>
                         </ul>
                     </div>
                 </div>
diff --git a/_scripts/redirects_generator/redirect_from_generator.sh b/_scripts/redirects_generator/redirect_from_generator.sh
index e9a7a0c8d15..e1ec0435972 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/scos/dev/the-docker-sdk"
+folder_path="docs/scos/user"
 
 # 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 00916cc6564..265cd8f47e0 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/scos/dev/the-docker-sdk"
+folder_path="docs/scos/user"
 
 # Check if the folder exists
 if [ ! -d "$folder_path" ]; then
@@ -46,7 +46,7 @@ if [ ! -d "$folder_path" ]; then
 fi
 
 # Specify the root directory to make paths relative to. Must end with `spryker-docs`
-root_directory="/Users/andrii.tserkovnyi/Documents/GitHub/spryker-docs"
+root_directory="/Users/oscarwilde/Documents/GitHub/spryker-docs"
 
 # Call the function to process files and subfolders
 process_files "$folder_path" "$root_directory"
diff --git a/docs/about/all/about-the-documentation/about-spryker-documentation.md b/docs/about/all/about-the-documentation/about-spryker-documentation.md
new file mode 100644
index 00000000000..e69de29bb2d
diff --git a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/add-global-sections-to-the-documentation.md b/docs/about/all/about-the-documentation/add-global-sections-to-the-documentation.md
similarity index 64%
rename from docs/scos/user/intro-to-spryker/contribute-to-the-documentation/add-global-sections-to-the-documentation.md
rename to docs/about/all/about-the-documentation/add-global-sections-to-the-documentation.md
index cfdf1bd19d4..a00775aa2a9 100644
--- a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/add-global-sections-to-the-documentation.md
+++ b/docs/about/all/about-the-documentation/add-global-sections-to-the-documentation.md
@@ -7,6 +7,8 @@ redirect_from:
   - /docs/scos/user/intro-to-spryker/contributing-to-documentation/adding-a-new-product-to-the-documentation-site.html
   - /docs/scos/user/intro-to-spryker/contributing-to-documentation/adding-product-sections-to-the-documentation.html
   - /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/add-product-sections-to-the-documentation.html
+  - /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
+
 related:
   - title: Build the documentation site
     link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/build-the-documentation-site.html
@@ -289,215 +291,4 @@ task :check_mp_dev do
 ...  
 ```
 
-## 6. Configure Algolia
-
-To configure Algolia in the repository and the Algolia app, take the following steps.
-
-### Configure Algolia in the repository
-
-1. In `algolia_config/`, create YML configuration files per role: `algolia_config/_acp_dev.yml` and `algolia_config/_acp_user.yml`.
-
-2. In both files, exclude generic pages and the pages of all the existing projects from indexing.
-
-{% info_block warningBox "Excluding the files you are adding" %}
-
-If you are adding configuration for two roles, you also need to exclude them from indexing each other. In the following examples, this is indicated by the following entries:
-* `docs/acp/dev/**/*.md`
-* `docs/acp/user/**/*.md`
-
-{% endinfo_block %}
-
-
-**algolia_config/_acp_user.yml**
-```yaml
-algolia:
-  index_name: 'acp_user'
-  files_to_exclude:
-    - index.md
-    - 404.md
-    - search.md
-    - docs/marketplace/user/**/*.md
-    - docs/marketplace/dev/**/*.md
-    - docs/scos/user/**/*.md
-    - docs/scos/dev/**/*.md
-    - docs/paas-plus/dev/**/*.md
-    - docs/fes/dev/**/*.md
-    - docs/cloud/dev/**/*.md
-    - docs/pbc/all/**/*.md
-    - docs/sdk/dev/**/*.md
-    - docs/acp/dev/**/*.md
-```
-
-**algolia_config/_acp_dev.yml**
-```yaml
-algolia:
-  index_name: 'acp_dev'
-  files_to_exclude:
-    - index.md
-    - 404.md
-    - search.md
-    - docs/marketplace/user/**/*.md
-    - docs/marketplace/dev/**/*.md
-    - docs/scos/user/**/*.md
-    - docs/scos/dev/**/*.md
-    - docs/paas-plus/dev/**/*.md
-    - docs/fes/dev/**/*.md
-    - docs/cloud/dev/**/*.md
-    - docs/pbc/all/**/*.md
-    - docs/sdk/dev/**/*.md
-    - docs/acp/user/**/*.md
-```
-
-
-3. In the Algolia configuration file of each existing section, exclude the project for both roles from indexing:
-
-**algolia_config/_scos_dev.yml**
-
-```yaml
-algolia:
-  index_name: 'scos_dev'
-  files_to_exclude:
-    - index.md
-    - 404.md
-    - search.md
-    - docs/marketplace/user/**/*.md
-    - docs/marketplace/dev/**/*.md
-    - docs/cloud/dev/**/*.md
-    - docs/scos/user/**/*.md
-    - docs/paas-plus/dev/**/*.md
-    - docs/acp/dev/**/*.md
-    - docs/acp/user/**/*.md   
-```
-
-4. In `.github/workflows/ci.yml`, add the Algolia configuration files you've created:
-
-```yaml
-jobs:
-  ...
-  algolia_search:
-    ...
-    steps:
-      ...
-      - run: bundle exec jekyll algolia --config=_config.yml,algolia_config/_acp_dev.yml
-        env: # Or as an environment variable
-          ALGOLIA_API_KEY: ${{ secrets.ALGOLIA_API_KEY }}
-      - run: bundle exec jekyll algolia --config=_config.yml,algolia_config/_acp_user.yml
-        env: # Or as an environment variable
-          ALGOLIA_API_KEY: ${{ secrets.ALGOLIA_API_KEY }}          
-```
-
-<a name="add-product-names-for-the-search"></a>
-
-5. In `_config.yml`, in the `algolia: indices:` section, add indexes per role:
-
-```yaml
-algolia:
-  ...
-  indices:
-    ...
-    - name: 'acp_user'
-      title: 'ACP User'
-    - name: 'acp_dev'
-      title: 'ACP Developer'
-```
-
-### Configure Algolia in the Algolia app
-
-To configure the search in the Algolia app, take the following steps.
-
-#### Create an index
-
-1. In the Algloia web interface, go to [Indices](https://www.algolia.com/apps/IBBSSFT6M1/indices).
-2. Select **Create Index**.
-3. In the **Create index** window, enter the **Index name**.
-4. Click **Create**.
-  This shows a success message and opens the page of the created index.
-
-#### Add searchable attributes
-
-1. Click the **Configuration** tab.
-2. Click **+  Add a Searchable Attribute**.
-3. Enter `title` and press `Enter`.
-4. Repeat steps 2-3 until you add the following attributes in the provided order and make them either ordered or unordered for search:
-
-| ATTRIBUTE | VALUE |
-| - | - |
-| title | ordered |
-| headings | ordered |
-| content | unordered |
-| collection,categories,tags | unordered |
-| url | ordered |
-
-#### Add ranking attributes
-
-1. Go to **RELEVANCE ESSENTIALS > Ranking and Sorting**.
-2. Click **+  Add custom ranking attribute**.
-3. Enter `date` and press `Enter`.
-4. Repeat steps 2-3 until you add the following attributes in the provided order and make them either ascending or descending:
-
-| ATTRIBUTE | VALUE |
-| - | - |
-| date | descending |
-| custom_ranking.heading | descending |
-| custom_ranking.position | ascending |
-
-#### Configure languages
-
-1. Go to **RELEVANCE OPTIMIZATIONS > Language**.
-2. In the **Index Languages** section, click **+ Select one or more languages**.
-3. Enter `English` and press `Enter`.
-4. In the **Query Languages** section, click **+ Select one or more languages**.
-5. Enter `English` and press `Enter`.
-6. Toggle **Ignore plural**.
-7. Enter `English` and press `Enter`.
-
-#### Add facet attributes
-
-1. Go to **FILTERING AND FACETING > Facets**.
-2. Click **+  Add an Attribute**.
-3. Enter `categories` and press `Enter`.
-4. Repeat steps 2-3 until you add the following attributes in the provided order and make them either searchable or not searchable:
-
-| ATTRIBUTE | VALUE |
-| - | - |
-| categories | searchable |
-| collection | searchable |
-| tags | searchable |
-| title | searchable |
-| type | not searchable |
-
-#### Configure highlighting
-
-1. Go to **PAGINATION AND DISPLAY > Highlighting**.
-2. In the **Attributes to highlight** section, click **+  Add an Attribute**.
-3. Enter `categories` and press `Enter`.
-4. Repeat steps 2-3 until you add the following attributes in the provided order:
-    * categories
-    * collection
-    * content
-    * headings
-    * html
-    * tags
-    * title
-    * type
-5. In the **Highlight prefix tag** section, replace the default value with `<em class="ais-Highlight">`.
-
-#### Add snippeting attributes
-
-1. Go to **PAGINATION AND DISPLAY > Snippeting**.
-2. Click **+  Add an Attribute**.
-3. Enter `content` and press `Enter`.
-
-#### Add unretrievable attributes
-
-1. Go to **SEARCH BEHAVIOR > Retrieved attributes**.
-2. In the **Unretrievable attributes** section, click **+  Add an Attribute**.
-3. Enter `custom_ranking` and press `Enter`.
-#### Configure duplicating and grouping
-
-1. Go to **SEARCH BEHAVIOR > Deduplication and Grouping**.
-2. For **Distinct**, select **true**.
-3. In the **Attribute for Distinct** section, enter `url` and press `Enter`.
-4. Click **Review and Save Settings**.
-5. Review the settings and click **Save Settings**.
-This shows a success message. After you merge the PR and it's deployed to master, you will be able to search across the new section.
+After you merge the PR and it's deployed to master, you will be able to search across the new section.
diff --git a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/add-and-edit-diagrams-in-the-documentation.md b/docs/about/all/about-the-documentation/contribute-to-the-documentation/add-and-edit-diagrams-in-the-documentation.md
similarity index 95%
rename from docs/scos/user/intro-to-spryker/contribute-to-the-documentation/add-and-edit-diagrams-in-the-documentation.md
rename to docs/about/all/about-the-documentation/contribute-to-the-documentation/add-and-edit-diagrams-in-the-documentation.md
index f824afc467e..f6d0123b26c 100644
--- a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/add-and-edit-diagrams-in-the-documentation.md
+++ b/docs/about/all/about-the-documentation/contribute-to-the-documentation/add-and-edit-diagrams-in-the-documentation.md
@@ -3,6 +3,9 @@ title: Add and edit diagrams in the documentation
 description: Learn how to add and edit diagrams.net diagrams in Spryker documentation.
 last_updated: Dec 22, 2022
 template: howto-guide-template
+redirect_from:
+- /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/add-and-edit-diagrams-in-the-documentation.html
+
 related:
   - title: Build the documentation site
     link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/build-the-documentation-site.html
diff --git a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/contribute-to-the-documentation.md b/docs/about/all/about-the-documentation/contribute-to-the-documentation/contribute-to-the-documentation.md
similarity index 91%
rename from docs/scos/user/intro-to-spryker/contribute-to-the-documentation/contribute-to-the-documentation.md
rename to docs/about/all/about-the-documentation/contribute-to-the-documentation/contribute-to-the-documentation.md
index 20ea9709dda..5015701cf2c 100644
--- a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/contribute-to-the-documentation.md
+++ b/docs/about/all/about-the-documentation/contribute-to-the-documentation/contribute-to-the-documentation.md
@@ -1,10 +1,12 @@
 ---
-title: Contribute to documentation
+title: Contribute to the documentation
 description: Learn how you can contribute to the Spryker docs.
 last_updated: Jul 18, 2022
 template: howto-guide-template
 redirect_from:
   - /docs/scos/user/intro-to-spryker/contributing-to-documentation/contributing-to-documentation.html
+  - /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/contribute-to-the-documentation.html
+
 related:
   - title: Build the documentation site
     link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/build-the-documentation-site.html
@@ -28,4 +30,4 @@ We at Spryker aim to constantly improve the content we provide our customers and
 * [Editing documentation by creating pull requests on GitHub](/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/edit-documentation-via-pull-requests.html).
 * [Reviewing pull requests](/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/review-pull-requests.html).
 
-Therefore, to contribute to the Spryker documentation, you must have a GitHub account. For information about how to create it, see [Signing up for a new GitHub account](https://docs.github.com/en/get-started/signing-up-for-github/signing-up-for-a-new-github-account) in the official GitHub documentation.
\ No newline at end of file
+Therefore, to contribute to the Spryker documentation, you must have a GitHub account. For information about how to create it, see [Signing up for a new GitHub account](https://docs.github.com/en/get-started/signing-up-for-github/signing-up-for-a-new-github-account) in the official GitHub documentation.
diff --git a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/edit-the-documentation-locally.md b/docs/about/all/about-the-documentation/contribute-to-the-documentation/edit-the-documentation-locally.md
similarity index 97%
rename from docs/scos/user/intro-to-spryker/contribute-to-the-documentation/edit-the-documentation-locally.md
rename to docs/about/all/about-the-documentation/contribute-to-the-documentation/edit-the-documentation-locally.md
index b7927c9bb7a..34bc02f5912 100644
--- a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/edit-the-documentation-locally.md
+++ b/docs/about/all/about-the-documentation/contribute-to-the-documentation/edit-the-documentation-locally.md
@@ -1,8 +1,10 @@
+  - /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/edit-the-documentation-locally.html
 ---
 title: Edit the documentation locally
 description: Learn how edit the documentation on your machine.
 last_updated: Jan 23, 2023
 template: howto-guide-template
+redirect_from:
 ---
 
 
diff --git a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/edit-documentation-via-pull-requests.md b/docs/about/all/about-the-documentation/contribute-to-the-documentation/edit-the-documentation-via-pull-requests.md
similarity index 97%
rename from docs/scos/user/intro-to-spryker/contribute-to-the-documentation/edit-documentation-via-pull-requests.md
rename to docs/about/all/about-the-documentation/contribute-to-the-documentation/edit-the-documentation-via-pull-requests.md
index 35b661d137b..0711320b03e 100644
--- a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/edit-documentation-via-pull-requests.md
+++ b/docs/about/all/about-the-documentation/contribute-to-the-documentation/edit-the-documentation-via-pull-requests.md
@@ -1,5 +1,5 @@
 ---
-title: Edit documentation via pull requests
+title: Edit the documentation using only a web browser
 description: Learn how you can propose changes to the Spryker docs
 last_updated: Jul 18, 2022
 template: howto-guide-template
@@ -7,6 +7,8 @@ redirect_from:
   - /docs/scos/user/intro-to-spryker/contributing-to-documentation/contributing-to-spryker-documentation.html
   - /docs/scos/user/intro-to-spryker/contributing-to-documentation/contributing-to-documentation.html
   - /docs/scos/user/intro-to-spryker/contributing-to-documentation/editing-documentation-via-pull-requests.html
+  - /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
+
 related:
   - title: Build the documentation site
     link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/build-the-documentation-site.html
diff --git a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/report-documentation-issues.md b/docs/about/all/about-the-documentation/contribute-to-the-documentation/report-documentation-issues.md
similarity index 94%
rename from docs/scos/user/intro-to-spryker/contribute-to-the-documentation/report-documentation-issues.md
rename to docs/about/all/about-the-documentation/contribute-to-the-documentation/report-documentation-issues.md
index 7bfdbb003fd..92c80e68386 100644
--- a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/report-documentation-issues.md
+++ b/docs/about/all/about-the-documentation/contribute-to-the-documentation/report-documentation-issues.md
@@ -5,6 +5,8 @@ last_updated: Jul 18, 2022
 template: howto-guide-template
 redirect_from:
   - /docs/scos/user/intro-to-spryker/contributing-to-documentation/reporting-documentation-issues.html
+  - /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/report-documentation-issues.html
+
 related:
   - title: Build the documentation site
     link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/build-the-documentation-site.html
diff --git a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/review-pull-requests.md b/docs/about/all/about-the-documentation/contribute-to-the-documentation/review-pull-requests.md
similarity index 97%
rename from docs/scos/user/intro-to-spryker/contribute-to-the-documentation/review-pull-requests.md
rename to docs/about/all/about-the-documentation/contribute-to-the-documentation/review-pull-requests.md
index 87525531145..7aeafe54e2d 100644
--- a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/review-pull-requests.md
+++ b/docs/about/all/about-the-documentation/contribute-to-the-documentation/review-pull-requests.md
@@ -5,6 +5,8 @@ last_updated: Jul 18, 2022
 template: howto-guide-template
 redirect_from:
   - /docs/scos/user/intro-to-spryker/contributing-to-documentation/reviewing-pull-requests.html
+  - /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/review-pull-requests.html
+
 related:
   - title: Build the documentation site
     link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/build-the-documentation-site.html
@@ -60,7 +62,6 @@ Before you submit your review, your line comments are pending and only visible t
 ![Viewed files](https://spryker.s3.eu-central-1.amazonaws.com/docs/scos/user/intro-to-spryker/contributing-to-documentation/viewed.png)
 
 5. Once you are done reviewing all the files, click **Review changes** in the top right corner and select either *Comment*, *Approve* or *Request changes*.
-   
+
 6. Click **Submit review**:
 ![Submit review](https://spryker.s3.eu-central-1.amazonaws.com/docs/scos/user/intro-to-spryker/contributing-to-documentation/submit-review.png)   
-   
diff --git a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/install-recommended-vs-code-extensions.md b/docs/about/all/about-the-documentation/install-recommended-vs-code-extensions.md
similarity index 94%
rename from docs/scos/user/intro-to-spryker/contribute-to-the-documentation/install-recommended-vs-code-extensions.md
rename to docs/about/all/about-the-documentation/install-recommended-vs-code-extensions.md
index 5e663493e05..dc7049a8392 100644
--- a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/install-recommended-vs-code-extensions.md
+++ b/docs/about/all/about-the-documentation/install-recommended-vs-code-extensions.md
@@ -3,6 +3,9 @@ title: Install recommended VS Code extensions
 description: Install recommended VS Code extensions to improve speed and quality quality of your contributions.
 last_updated: Feb 28, 2023
 template: howto-guide-template
+redirect_from:
+- /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/install-recommended-vs-code-extensions.html
+
 related:
   - title: Build the documentation site
     link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/build-the-documentation-site.html
@@ -33,10 +36,10 @@ Some extensions, like Vale, need additional configuration. For Vale installation
 
 ## Vale overview
 
-Vale works by analyzing the text of a file and comparing it to a set of customizable rules, which are located in the `vale/styles` folder. 
+Vale works by analyzing the text of a file and comparing it to a set of customizable rules, which are located in the `vale/styles` folder.
 Vale uses the rules to check for issues such as spelling, grammar, and stylistic errors.
 
-The `vale/styles/Vocab/Base` folder holds the `accept.txt` and `reject.txt` files. 
+The `vale/styles/Vocab/Base` folder holds the `accept.txt` and `reject.txt` files.
 These files contain custom words and phrases that must always be accepted or rejected, respectively, during the Vale review process.
 
 When Vale identifies an issue, it highlights the relevant text and displays an inline message that describes the issue and suggests a solution. These messages can include links to external resources or documentation for more information.
@@ -55,7 +58,7 @@ To use Vale in VS Code, you need to install it on your computer. For installatio
 2. On the **User** tab, for **Vale > Vale CLI: Config**, enter `${workspaceFolder}/.vale.ini`.
 3. For **Vale › Vale CLI: Min Alert Level**, select **inherited**.
 4. For **Vale › Vale CLI: Path**, enter `vale`.
-5. Click the **Workspace** tab and repeat steps 2-4. 
+5. Click the **Workspace** tab and repeat steps 2-4.
 6. To apply the settings, relaunch VS Code.
 
- Now you can use Vale to lint and style-check Markdown files in the project.
\ No newline at end of file
+ Now you can use Vale to lint and style-check Markdown files in the project.
diff --git a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/build-the-documentation-site.md b/docs/about/all/about-the-documentation/run-the-documentation-locally.md
similarity index 95%
rename from docs/scos/user/intro-to-spryker/contribute-to-the-documentation/build-the-documentation-site.md
rename to docs/about/all/about-the-documentation/run-the-documentation-locally.md
index c385dbf4742..9469b4fd58d 100644
--- a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/build-the-documentation-site.md
+++ b/docs/about/all/about-the-documentation/run-the-documentation-locally.md
@@ -1,10 +1,12 @@
 ---
-title: Build the documentation site
+title: Run the documentation locally
 description: Find out how you can build the Spryker documentation site
 last_updated: Jul 18, 2022
 template: howto-guide-template
 redirect_from:
   - /docs/scos/user/intro-to-spryker/contributing-to-documentation/building-the-documentation-site.html
+  - /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/build-the-documentation-site.html
+
 related:
   - title: Add product sections to the documentation
     link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
@@ -27,7 +29,7 @@ We use [Jekyll](https://jekyllrb.com/) to build the Spryker documentation site.
 3. Run the documentation site locally
 
 
-## Install Jekyll 
+## Install Jekyll
 
 Depending on your operating system, follow the Jekyll installation guides below.
 
@@ -41,22 +43,22 @@ The installation process is different depending whether you are using a Mac with
 
 {% info_block warningBox "MacOS on M1 processor – Open Terminal using Rosetta" %}
 
-On a MacBook with the M1 processor, make sure your Terminal is opened with Rosetta 2, by following the instructions here. Rosetta is a translation layer that enables non-native Intel x86 apps, including Homebrew, to run on Apple Silicon Macs. 
+On a MacBook with the M1 processor, make sure your Terminal is opened with Rosetta 2, by following the instructions here. Rosetta is a translation layer that enables non-native Intel x86 apps, including Homebrew, to run on Apple Silicon Macs.
 To open your terminal using Rosetta, follow these steps:
 1.	Open a _Finder_ window.
 2.	In _Applications_, locate _Terminal_.
-3.	Right click on **Terminal** and select **Get Info**. 
-4.	Make sure _Open using Rosetta_ is checked. 
-  
+3.	Right click on **Terminal** and select **Get Info**.
+4.	Make sure _Open using Rosetta_ is checked.
+
 {% endinfo_block %}
 
 On either an M1 or an Intel Mac, follow the steps below to install Jekyll. M1-specific instructions appear as notes wherever necessary.  
 
 #### 1. Install Homebrew
 
-Homebrew is a package manager for macOS because by default Mac doesn’t have a package manager. You use Homebrew to install Ruby in the next step. Additionally, when you install Homebrew, Xcode command line tools and GCC are also installed automatically. 
+Homebrew is a package manager for macOS because by default Mac doesn’t have a package manager. You use Homebrew to install Ruby in the next step. Additionally, when you install Homebrew, Xcode command line tools and GCC are also installed automatically.
 
-To install Homebrew, follow these steps: 
+To install Homebrew, follow these steps:
 ```bash
 /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
 ```
@@ -92,7 +94,7 @@ To save the updated .zprofile file, click **control o**. Then, to exit the .zpro
 
 ```bash
 brew install make
-``` 
+```
 
 #### 3. Install Ruby
 Check your current Ruby version:
@@ -106,8 +108,8 @@ You should not use the Ruby version that came pre-installed with your Mac. Apple
 
 {% endinfo_block %}
 
-If you have not yet installed a recent Ruby version, install Ruby: 
- 
+If you have not yet installed a recent Ruby version, install Ruby:
+
 ```bash
 brew install ruby
 ```
@@ -125,7 +127,7 @@ Add the brew Ruby and gems path to your shell configuration:
         ```bash
         echo 'export PATH="/usr/local/opt/ruby/bin:/usr/local/lib/ruby/gems/3.0.0/bin:$PATH"' >> ~/.bash_profile
         ```
-        
+
 #### 3. Install Jekyll and Bundler
 1. Install Jekyll and Bundler gems:
 ```bash
@@ -144,8 +146,8 @@ ruby -v
     ```bash
     echo 'export PATH="$HOME/.gem/ruby/X.X.0/bin:$PATH"' >> ~/.bash_profile
     ```
-    
-### Install Jekyll on Windows, Ubuntu, or other Linux systems 
+
+### Install Jekyll on Windows, Ubuntu, or other Linux systems
 
 #### Prerequisites
 
@@ -155,7 +157,7 @@ To use Jekyll on Windows, Ubuntu, or other Linux systems, you also need to insta
 * [RubyGems](https://rubygems.org/pages/download), the latest version. To check your RubyGems version, run `gem -v`.
 * [GCC](https://gcc.gnu.org/install/) and [Make](https://www.gnu.org/software/make/). To check your GCC version, run `gcc -v,g++ -v`, for Make version run `make -v`.
 
-  
+
 #### Install Jekyll on Windows
 
 To install Jekyll on Windows, follow the [official Jekyll on Windows documentation](https://jekyllrb.com/docs/installation/windows/).
@@ -214,7 +216,7 @@ arch -arch x86_64 bundle exec jekyll serve
 ```
 
 {% endinfo_block %}
- 
+
 ## Tips and tricks
 
 * To regenerate only those pages that were added or updated since the last build, build the site with the following command:
@@ -225,4 +227,3 @@ bundle exec jekyll serve --incremental
 ```bash
 bundle exec jekyll serve --incremental --livereload
 ```
-
diff --git a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/spryker-documentation-style-guide/examples.md b/docs/about/all/about-the-documentation/spryker-documentation-style-guide/examples.md
similarity index 90%
rename from docs/scos/user/intro-to-spryker/contribute-to-the-documentation/spryker-documentation-style-guide/examples.md
rename to docs/about/all/about-the-documentation/spryker-documentation-style-guide/examples.md
index 9dfbf2734f7..16439a1565c 100644
--- a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/spryker-documentation-style-guide/examples.md
+++ b/docs/about/all/about-the-documentation/spryker-documentation-style-guide/examples.md
@@ -3,6 +3,9 @@ title: Examples
 description: Guidance for introducing examples in Spryker documentation
 last_updated: Mar 23, 2023
 template: concept-topic-template
+redirect_from:
+- /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/spryker-documentation-style-guide/examples.html
+
 ---
 
 In general, follow [Google's guidance for examples](https://developers.google.com/style/format-examples?hl=en).
diff --git a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/general-rules-and-guidance-for-adding-new-documents.md b/docs/about/all/about-the-documentation/spryker-documentation-style-guide/general-rules-and-guidance-for-adding-documents.md
similarity index 99%
rename from docs/scos/user/intro-to-spryker/contribute-to-the-documentation/general-rules-and-guidance-for-adding-new-documents.md
rename to docs/about/all/about-the-documentation/spryker-documentation-style-guide/general-rules-and-guidance-for-adding-documents.md
index 5123d9e02ea..6b8dbd8124b 100644
--- a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/general-rules-and-guidance-for-adding-new-documents.md
+++ b/docs/about/all/about-the-documentation/spryker-documentation-style-guide/general-rules-and-guidance-for-adding-documents.md
@@ -1,11 +1,13 @@
 ---
-title: General rules and guidance for adding new documents
+title: General rules and guidance for adding documents
 description: Learn how to style and format your docs.
 last_updated: Jul 18, 2022
 template: concept-topic-template
 redirect_from:
   - /docs/scos/user/intro-to-spryker/contributing-to-documentation/style-formatting-general-rules.html
   - /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/style-formatting-general-rules.html
+  - /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/general-rules-and-guidance-for-adding-new-documents.html
+
 related:
   - title: Build the documentation site
     link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/build-the-documentation-site.html
diff --git a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/markdown-syntax.md b/docs/about/all/about-the-documentation/spryker-documentation-style-guide/markdown-syntax.md
similarity index 98%
rename from docs/scos/user/intro-to-spryker/contribute-to-the-documentation/markdown-syntax.md
rename to docs/about/all/about-the-documentation/spryker-documentation-style-guide/markdown-syntax.md
index f45263671d0..db620ee2a8a 100644
--- a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/markdown-syntax.md
+++ b/docs/about/all/about-the-documentation/spryker-documentation-style-guide/markdown-syntax.md
@@ -5,6 +5,8 @@ last_updated: 18 Jul, 2022
 template: howto-guide-template
 redirect_from:
   - /docs/scos/user/intro-to-spryker/contributing-to-documentation/markdown-syntax.html
+  - /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/markdown-syntax.html
+
 related:
   - title: Build the documentation site
     link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/build-the-documentation-site.html
@@ -82,9 +84,9 @@ Example:
 
 {% info_block warningBox "Warning" %}
 
-Make sure to fulfill the requirements: 
+Make sure to fulfill the requirements:
 
-- `{drop-down toggle button}` in `<summary>{drop-down toggle button}</summary>` should not undergo any kind of formatting. For example, `<summary>`code.php`</summary>` or `<summary><var>code.php</var></summary>`. Otherwise, the code snippet will be corrupted. 
+- `{drop-down toggle button}` in `<summary>{drop-down toggle button}</summary>` should not undergo any kind of formatting. For example, `<summary>`code.php`</summary>` or `<summary><var>code.php</var></summary>`. Otherwise, the code snippet will be corrupted.
 - Put a blank row between `<summary>{drop-down toggle button}</summary>` and _```{programming language}_. This will ensure that the code snippet is displayed correctly on the documentation website.
 
 {% endinfo_block %}
@@ -252,7 +254,7 @@ When a table column contains only code snippets, do the following:
 
 1. Remove the column with the code snippet from the table entirely.
 2. Below the table, paste all the code snippets in the following format:
-   
+
 ```md
 <details><summary>{removed column header name}:{entity name}</summary>
 
@@ -336,7 +338,7 @@ Published table:
 ```
 </details>
 
-### Mixed content 
+### Mixed content
 
 If you have a table column with cells containing both code snippets and supported content, do the following:
 
@@ -354,7 +356,7 @@ Published table:
 
 | FUNCTION NAME | DESCRIPTION | METHOD SIGNATURE | USAGE EXAMPLE |
 | --- | --- | --- | --- |
-| `model` | Resolves a model path and returns a string in the following format: `{% raw %}@ShopUi/models/{modelName}.twig{% endraw %}`. | `{% raw %}function model($modelName: string){% endraw %}`: string `{% raw %}$modelName{% endraw %}` - model name (required). | `{% raw %}{% extends model('component') %}{% endraw %}` | 
+| `model` | Resolves a model path and returns a string in the following format: `{% raw %}@ShopUi/models/{modelName}.twig{% endraw %}`. | `{% raw %}function model($modelName: string){% endraw %}`: string `{% raw %}$modelName{% endraw %}` - model name (required). | `{% raw %}{% extends model('component') %}{% endraw %}` |
 | `define` | This function is used for: creating a default object that can be changed from an incoming context and defining tags used to pass properties and contract for a specific component. | | See **Usage Example: define** below. |
 | `qa` | Returns a string in the following format: `{% raw %}data-qa="qa values here"{% endraw %}` | `{% raw %}function qa($qaValues: string[] = []): string{% endraw %}` | `{% raw %}{{ qa('submit-button') }}{% endraw %}` |
 
@@ -373,7 +375,7 @@ Published table:
 
 ## Anchors
 
-You don’t have to create anchors for headings. Each heading has its default anchor that corresponds to its text. However, still check [step 2](#step-2) of this section to learn about important aspects of linking to anchors. 
+You don’t have to create anchors for headings. Each heading has its default anchor that corresponds to its text. However, still check [step 2](#step-2) of this section to learn about important aspects of linking to anchors.
 
 Follow these steps to create an anchor and link to it:
 
@@ -404,7 +406,7 @@ To integrate GLUE API in your project, you need to:
 * [Install GLUE](#install-glue)
 * [Enable GLUE](#enable-glue)
 
-1. Install GLUE  <a name="install-glue"></a> 
+1. Install GLUE  <a name="install-glue"></a>
 2. Enable GLUE <a name="enable-glue"></a>
 ```
 
@@ -424,8 +426,8 @@ You can also set video’s width and height. For example:
 
 `{% raw %}{% wistia eiw5ev4gv2 960 720 %}{% endraw %}`
 
-where 
-960 - is the video’s width 
+where
+960 - is the video’s width
 720 - is the video’s height
 
 ## Adding other videos
@@ -444,11 +446,11 @@ To add a link to a video in the .mp4 format that originates not from Wistia, add
 To embed PDF files, use the following code:
 
 ```html
-<embed src="http://example.com/the.pdf" width="500" height="375" 
+<embed src="http://example.com/the.pdf" width="500" height="375"
  type="application/pdf">
 ```
 
-where `http://example.com/the.pdf` is the link to your .pdf file. 
+where `http://example.com/the.pdf` is the link to your .pdf file.
 
 
 ## Glossary
diff --git a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/spryker-documentation-style-guide/spelling.md b/docs/about/all/about-the-documentation/spryker-documentation-style-guide/spelling.md
similarity index 67%
rename from docs/scos/user/intro-to-spryker/contribute-to-the-documentation/spryker-documentation-style-guide/spelling.md
rename to docs/about/all/about-the-documentation/spryker-documentation-style-guide/spelling.md
index 8ca52dea7a1..960aac603d9 100644
--- a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/spryker-documentation-style-guide/spelling.md
+++ b/docs/about/all/about-the-documentation/spryker-documentation-style-guide/spelling.md
@@ -3,6 +3,9 @@ title: Spelling
 description: Guidance for spelling in Spryker documentation
 last_updated: Mar 23, 2023
 template: concept-topic-template
+redirect_from:
+- /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/spryker-documentation-style-guide/spelling.html
+
 ---
 
 In general, use American spelling and follow [Google's guidance for spelling](https://developers.google.com/style/spelling).
diff --git a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/spryker-documentation-style-guide/spryker-documentation-style-guide.md b/docs/about/all/about-the-documentation/spryker-documentation-style-guide/spryker-documentation-style-guide.md
similarity index 86%
rename from docs/scos/user/intro-to-spryker/contribute-to-the-documentation/spryker-documentation-style-guide/spryker-documentation-style-guide.md
rename to docs/about/all/about-the-documentation/spryker-documentation-style-guide/spryker-documentation-style-guide.md
index 538505da4be..b3b26950e75 100644
--- a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/spryker-documentation-style-guide/spryker-documentation-style-guide.md
+++ b/docs/about/all/about-the-documentation/spryker-documentation-style-guide/spryker-documentation-style-guide.md
@@ -3,6 +3,9 @@ title: Spryker documentation style guide
 description:
 last_updated: Mar 23, 2023
 template: concept-topic-template
+redirect_from:
+- /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/spryker-documentation-style-guide/spryker-documentation-style-guide.html
+
 ---
 
 When writing and reviewing documentation at Spryker, we are mostly relying on external style guides.
diff --git a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/spryker-documentation-style-guide/word-list.md b/docs/about/all/about-the-documentation/spryker-documentation-style-guide/word-list.md
similarity index 88%
rename from docs/scos/user/intro-to-spryker/contribute-to-the-documentation/spryker-documentation-style-guide/word-list.md
rename to docs/about/all/about-the-documentation/spryker-documentation-style-guide/word-list.md
index 24f07da8250..4667d87da08 100644
--- a/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/spryker-documentation-style-guide/word-list.md
+++ b/docs/about/all/about-the-documentation/spryker-documentation-style-guide/word-list.md
@@ -3,6 +3,9 @@ title: Word list
 description: A list of words specific to Spryker Cloud Commerce OS
 last_updated: Jun 23, 2023
 template: concept-topic-template
+redirect_from:
+- /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/spryker-documentation-style-guide/word-list.html
+
 ---
 
 
diff --git a/docs/scos/user/intro-to-spryker/b2b-suite.md b/docs/about/all/b2b-suite.md
similarity index 99%
rename from docs/scos/user/intro-to-spryker/b2b-suite.md
rename to docs/about/all/b2b-suite.md
index 9c1ccbc5f46..0e705d78264 100644
--- a/docs/scos/user/intro-to-spryker/b2b-suite.md
+++ b/docs/about/all/b2b-suite.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/b2b-suite.html
 ---
 title: B2B Suite
 description: The Spryker B2B Suite is a showcase that demonstrates ready-to-use B2B-specific Spryker features in a live implementation.
diff --git a/docs/scos/user/intro-to-spryker/b2c-suite.md b/docs/about/all/b2c-suite.md
similarity index 99%
rename from docs/scos/user/intro-to-spryker/b2c-suite.md
rename to docs/about/all/b2c-suite.md
index 53d4e460b05..1e0c91792c8 100644
--- a/docs/scos/user/intro-to-spryker/b2c-suite.md
+++ b/docs/about/all/b2c-suite.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/b2c-suite.html
 ---
 title: B2C Suite
 description: The Spryker B2C Suite is a showcase that demonstrates ready-to-use B2C-specific Spryker features in a live implementation.
diff --git a/docs/scos/user/intro-to-spryker/docs-updates.md b/docs/about/all/docs-updates.md
similarity index 99%
rename from docs/scos/user/intro-to-spryker/docs-updates.md
rename to docs/about/all/docs-updates.md
index ff1f8f96052..162814ded64 100644
--- a/docs/scos/user/intro-to-spryker/docs-updates.md
+++ b/docs/about/all/docs-updates.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/docs-updates.html
 ---
 title: Docs updates
 description: Spryker docs release notes
diff --git a/docs/scos/user/intro-to-spryker/faq.md b/docs/about/all/faq.md
similarity index 99%
rename from docs/scos/user/intro-to-spryker/faq.md
rename to docs/about/all/faq.md
index 2910a100890..2add95b27c3 100644
--- a/docs/scos/user/intro-to-spryker/faq.md
+++ b/docs/about/all/faq.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/faq.html
 ---
 title: FAQ
 description: Use the article to get answers to the most popular questions about Spryker.
diff --git a/docs/scos/user/intro-to-spryker/intro-to-spryker.md b/docs/about/all/intro-to-spryker.md
similarity index 99%
rename from docs/scos/user/intro-to-spryker/intro-to-spryker.md
rename to docs/about/all/intro-to-spryker.md
index 066d8fb1dfd..3fb8a78cdc0 100644
--- a/docs/scos/user/intro-to-spryker/intro-to-spryker.md
+++ b/docs/about/all/intro-to-spryker.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/intro-to-spryker.html
 ---
 title: Intro to Spryker
 description: The Spryker Commerce OS or SCOS is a completely modular, API-first, headless commerce technology for transactional business models in a B2B or B2C context.
diff --git a/docs/scos/user/intro-to-spryker/master-suite.md b/docs/about/all/master-suite.md
similarity index 96%
rename from docs/scos/user/intro-to-spryker/master-suite.md
rename to docs/about/all/master-suite.md
index 2d1396b8825..f94d9a56e69 100644
--- a/docs/scos/user/intro-to-spryker/master-suite.md
+++ b/docs/about/all/master-suite.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/master-suite.html
 ---
 title: Master Suite
 last_updated: Jun 16, 2021
diff --git a/docs/scos/user/intro-to-spryker/mvp-project-structuring.md b/docs/about/all/mvp-project-structuring.md
similarity index 99%
rename from docs/scos/user/intro-to-spryker/mvp-project-structuring.md
rename to docs/about/all/mvp-project-structuring.md
index ef9fcf430ca..e67d50ffeca 100644
--- a/docs/scos/user/intro-to-spryker/mvp-project-structuring.md
+++ b/docs/about/all/mvp-project-structuring.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/mvp-project-structuring.html
 ---
 title: MVP project structuring
 description: This article helps with the project planning stage.
diff --git a/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202211.0/release-notes-202211.0.md b/docs/about/all/releases/release-notes/release-notes-202211.0/release-notes-202211.0.md
similarity index 90%
rename from docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202211.0/release-notes-202211.0.md
rename to docs/about/all/releases/release-notes/release-notes-202211.0/release-notes-202211.0.md
index 1f44722e130..1e08a91c41c 100644
--- a/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202211.0/release-notes-202211.0.md
+++ b/docs/about/all/releases/release-notes/release-notes-202211.0/release-notes-202211.0.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202211.0/release-notes-202211.0.html
 ---
 title: Release notes 202211.0
 last_updated: November 22, 2022
diff --git a/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.md b/docs/about/all/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.md
similarity index 82%
rename from docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.md
rename to docs/about/all/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.md
index f7349cec868..16376d4ee2f 100644
--- a/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.md
+++ b/docs/about/all/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.html
 ---
 title: Patch releases 202212.0
 description: Patch releases for the Spryker release 202212.0
diff --git a/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/release-notes-202212.0.md b/docs/about/all/releases/release-notes/release-notes-202212.0/release-notes-202212.0.md
similarity index 98%
rename from docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/release-notes-202212.0.md
rename to docs/about/all/releases/release-notes/release-notes-202212.0/release-notes-202212.0.md
index 3df70da5eee..db859b25b2e 100644
--- a/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/release-notes-202212.0.md
+++ b/docs/about/all/releases/release-notes/release-notes-202212.0/release-notes-202212.0.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/release-notes-202212.0.html
 ---
 title: Release notes 202212.0
 description: Release notes for the Spryker SCOS release 202212.0
diff --git a/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/security-release-notes-202212.0.md b/docs/about/all/releases/release-notes/release-notes-202212.0/security-release-notes-202212.0.md
similarity index 99%
rename from docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/security-release-notes-202212.0.md
rename to docs/about/all/releases/release-notes/release-notes-202212.0/security-release-notes-202212.0.md
index ac404a9d08a..335c41bcd7a 100644
--- a/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/security-release-notes-202212.0.md
+++ b/docs/about/all/releases/release-notes/release-notes-202212.0/security-release-notes-202212.0.md
@@ -1,8 +1,10 @@
+  - /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/security-release-notes-202212.0.html
 ---
 title: Security release notes 202212.0
 description: Security release notes for the Spryker Product release 202212.0
 last_updated: Dec 21, 2022
 template: concept-topic-template
+redirect_from:
 ---
 
 The following information pertains to security-related issues that have been recently resolved. All issues are listed by description and affected modules.
diff --git a/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202302.0/security-release-notes-202302.0.md b/docs/about/all/releases/release-notes/release-notes-202302.0/security-release-notes-202302.0.md
similarity index 98%
rename from docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202302.0/security-release-notes-202302.0.md
rename to docs/about/all/releases/release-notes/release-notes-202302.0/security-release-notes-202302.0.md
index 683913dbd3b..377d8af9684 100644
--- a/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202302.0/security-release-notes-202302.0.md
+++ b/docs/about/all/releases/release-notes/release-notes-202302.0/security-release-notes-202302.0.md
@@ -1,8 +1,10 @@
+  - /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202302.0/security-release-notes-202302.0.html
 ---
 title: Security release notes 202302.0
 description: Security release notes for the Spryker Product release 202302.0
 last_updated: Mar 21, 2023
 template: concept-topic-template
+redirect_from:
 ---
 
 This document describes the security-related issues we have recently resolved. All issues are listed by description and affected modules.
@@ -184,4 +186,4 @@ Update the `spryker/sales` version and verify the version:
 ```bash
 composer require spryker/sales:"~11.36.2"
 composer show spryker/sales # Verify the version
-```
\ No newline at end of file
+```
diff --git a/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202304.0/security-release-notes-202304.0.md b/docs/about/all/releases/release-notes/release-notes-202304.0/security-release-notes-202304.0.md
similarity index 99%
rename from docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202304.0/security-release-notes-202304.0.md
rename to docs/about/all/releases/release-notes/release-notes-202304.0/security-release-notes-202304.0.md
index 86b49e636ef..f4f57e41678 100644
--- a/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202304.0/security-release-notes-202304.0.md
+++ b/docs/about/all/releases/release-notes/release-notes-202304.0/security-release-notes-202304.0.md
@@ -1,8 +1,10 @@
+  - /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202304.0/security-release-notes-202304.0.html
 ---
 title: Security release notes 202304.0
 description: Security release notes for the Spryker Product release 202304.0
 last_updated: Apr 21, 2023
 template: concept-topic-template
+redirect_from:
 ---
 
 The following information pertains to security-related issues that have been recently resolved. All issues are listed by description and affected modules.
diff --git a/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202307.0/release-notes-202307.0.md b/docs/about/all/releases/release-notes/release-notes-202307.0/release-notes-202307.0.md
similarity index 99%
rename from docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202307.0/release-notes-202307.0.md
rename to docs/about/all/releases/release-notes/release-notes-202307.0/release-notes-202307.0.md
index 2c8fb2c140b..07dd0c1ab97 100644
--- a/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202307.0/release-notes-202307.0.md
+++ b/docs/about/all/releases/release-notes/release-notes-202307.0/release-notes-202307.0.md
@@ -1,8 +1,10 @@
+  - /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202307.0/release-notes-202307.0.html
 ---
 title: Release notes 202307.0
 description: Release notes for the Spryker SCOS release 202307.0
 last_updated: Jul 31, 2023
 template: concept-topic-template
+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.
diff --git a/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202307.0/security-release-notes-202307.0.md b/docs/about/all/releases/release-notes/release-notes-202307.0/security-release-notes-202307.0.md
similarity index 93%
rename from docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202307.0/security-release-notes-202307.0.md
rename to docs/about/all/releases/release-notes/release-notes-202307.0/security-release-notes-202307.0.md
index b7eabd0d283..6c4dd213fbd 100644
--- a/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202307.0/security-release-notes-202307.0.md
+++ b/docs/about/all/releases/release-notes/release-notes-202307.0/security-release-notes-202307.0.md
@@ -1,8 +1,10 @@
+  - /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202307.0/security-release-notes-202307.0.html
 ---
 title: Security release notes 202307.0
 description: Security release notes for the Spryker Summer 2023 Cross-Product Release
 last_updated: Jul 26, 2023
 template: concept-topic-template
+redirect_from:
 ---
 
 The following information pertains to security-related issues that have been recently resolved. All issues are listed by description and affected modules.
diff --git a/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202311.0/release-notes-202311.0.md b/docs/about/all/releases/release-notes/release-notes-202311.0/release-notes-202311.0.md
similarity index 99%
rename from docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202311.0/release-notes-202311.0.md
rename to docs/about/all/releases/release-notes/release-notes-202311.0/release-notes-202311.0.md
index d717f4ed9f7..99478ad0be6 100644
--- a/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202311.0/release-notes-202311.0.md
+++ b/docs/about/all/releases/release-notes/release-notes-202311.0/release-notes-202311.0.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202311.0/release-notes-202311.0.html
 ---
 title: Release notes 202311.0
 description: Release notes for the Spryker SCOS release 202311.0
diff --git a/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes.md b/docs/about/all/releases/release-notes/release-notes.md
similarity index 94%
rename from docs/scos/user/intro-to-spryker/releases/release-notes/release-notes.md
rename to docs/about/all/releases/release-notes/release-notes.md
index 97409e4360e..26fab71b26b 100644
--- a/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes.md
+++ b/docs/about/all/releases/release-notes/release-notes.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes.html
 ---
 title: Release Notes
 description: The article describes the release flow of features and enhancements.
diff --git a/docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202306.0.md b/docs/about/all/releases/release-notes/security-release-notes-202306.0.md
similarity index 99%
rename from docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202306.0.md
rename to docs/about/all/releases/release-notes/security-release-notes-202306.0.md
index d102e62a8bc..c3a518f0c1f 100644
--- a/docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202306.0.md
+++ b/docs/about/all/releases/release-notes/security-release-notes-202306.0.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202306.0.html
 ---
 title: Security release notes 202306.0
 description: Security release notes for the Spryker Product release 202306.0
diff --git a/docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202309.0.md b/docs/about/all/releases/release-notes/security-release-notes-202309.0.md
similarity index 97%
rename from docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202309.0.md
rename to docs/about/all/releases/release-notes/security-release-notes-202309.0.md
index c8298dd2306..2a7d251fd6f 100644
--- a/docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202309.0.md
+++ b/docs/about/all/releases/release-notes/security-release-notes-202309.0.md
@@ -1,8 +1,10 @@
+  - /docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202309.0.html
 ---
 title: Security release notes 202309.0
 description: Security release notes for 202309.0
 last_updated: Oct 4, 2023
 template: concept-topic-template
+redirect_from:
 ---
 
 The following information pertains to security-related issues that have been recently resolved. All issues are listed by description and affected modules.
@@ -190,4 +192,4 @@ class SecurityBlockerPageConfig extends SprykerSecurityBlockerPageConfig
      */
     protected const USE_EMAIL_CONTEXT_FOR_LOGIN_SECURITY_BLOCKER = false;
 }
-```
\ No newline at end of file
+```
diff --git a/docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202312.0.md b/docs/about/all/releases/release-notes/security-release-notes-202312.0.md
similarity index 99%
rename from docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202312.0.md
rename to docs/about/all/releases/release-notes/security-release-notes-202312.0.md
index 1659901068a..9bf2c1f9ba1 100644
--- a/docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202312.0.md
+++ b/docs/about/all/releases/release-notes/security-release-notes-202312.0.md
@@ -1,8 +1,10 @@
+  - /docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202312.0.html
 ---
 title: Security release notes 202312.0
 description: Security release notes for 202312.0
 last_updated: Dec 18, 2023
 template: concept-topic-template
+redirect_from:
 ---
 
 The following information pertains to security-related issues that have been recently resolved. All issues are listed by description and affected modules.
diff --git a/docs/scos/user/intro-to-spryker/releases/releases.md b/docs/about/all/releases/releases.md
similarity index 98%
rename from docs/scos/user/intro-to-spryker/releases/releases.md
rename to docs/about/all/releases/releases.md
index 609267a8788..21bbb9be7bc 100644
--- a/docs/scos/user/intro-to-spryker/releases/releases.md
+++ b/docs/about/all/releases/releases.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/releases/releases.html
 ---
 title: Releases
 description: This section contains the notes for each release made by Spryker.
diff --git a/docs/scos/user/intro-to-spryker/spryker-academy.md b/docs/about/all/spryker-academy.md
similarity index 99%
rename from docs/scos/user/intro-to-spryker/spryker-academy.md
rename to docs/about/all/spryker-academy.md
index 3ca1ed3dcef..09c9f054e6e 100644
--- a/docs/scos/user/intro-to-spryker/spryker-academy.md
+++ b/docs/about/all/spryker-academy.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/spryker-academy.html
 ---
 title: Spryker Academy
 description: Spryker Academy is a dedicated resource for learning Spryker Commerce OS through a variety of self-paced and instructor-led courses.
@@ -174,6 +175,3 @@ redirect_from:
 We believe that good technology doesn’t stop with the code. You also need examples and information to help you convert your vision into reality.
 
 [Spryker Academy](https://academy.spryker.com/learn) is a dedicated resource for learning our Spryker Commerce OS through a variety of self-paced and instructor-led courses.
-
-
-
diff --git a/docs/scos/user/intro-to-spryker/spryker-marketplace/back-office-for-marketplace-operator.md b/docs/about/all/spryker-marketplace/back-office-for-marketplace-operator.md
similarity index 98%
rename from docs/scos/user/intro-to-spryker/spryker-marketplace/back-office-for-marketplace-operator.md
rename to docs/about/all/spryker-marketplace/back-office-for-marketplace-operator.md
index 929f63c578f..317f5ff99a7 100644
--- a/docs/scos/user/intro-to-spryker/spryker-marketplace/back-office-for-marketplace-operator.md
+++ b/docs/about/all/spryker-marketplace/back-office-for-marketplace-operator.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/spryker-marketplace/back-office-for-marketplace-operator.html
 ---
 title: Back Office for Marketplace Operator
 description: This document describes how a marketplace operator works in the Back Office.
diff --git a/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2b-suite.md b/docs/about/all/spryker-marketplace/marketplace-b2b-suite.md
similarity index 95%
rename from docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2b-suite.md
rename to docs/about/all/spryker-marketplace/marketplace-b2b-suite.md
index 6ae68969017..9506c692ec8 100644
--- a/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2b-suite.md
+++ b/docs/about/all/spryker-marketplace/marketplace-b2b-suite.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2b-suite.html
 ---
 title: Marketplace B2B Suite
 description: The Spryker Marketplace B2B Demo Shop is a showcase that demonstrates ready-to-use Marketplace B2B-specific Spryker features in a live implementation.
diff --git a/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2c-suite.md b/docs/about/all/spryker-marketplace/marketplace-b2c-suite.md
similarity index 97%
rename from docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2c-suite.md
rename to docs/about/all/spryker-marketplace/marketplace-b2c-suite.md
index ff50dc0293a..c41f28a4a6f 100644
--- a/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2c-suite.md
+++ b/docs/about/all/spryker-marketplace/marketplace-b2c-suite.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2c-suite.html
 ---
 title: Marketplace B2C Suite
 description: The Spryker Marketplace B2C Demo Shop is a showcase that demonstrates ready-to-use Marketplace B2C-specific Spryker features in a live implementation.
diff --git a/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-concept.md b/docs/about/all/spryker-marketplace/marketplace-concept.md
similarity index 97%
rename from docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-concept.md
rename to docs/about/all/spryker-marketplace/marketplace-concept.md
index 40f85bcbf32..6b5e3f4aa39 100644
--- a/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-concept.md
+++ b/docs/about/all/spryker-marketplace/marketplace-concept.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-concept.html
 ---
 title: Marketplace concept
 description: This document describes what a Marketplace is in the Spryker Commerce OS.
diff --git a/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-personas.md b/docs/about/all/spryker-marketplace/marketplace-personas.md
similarity index 96%
rename from docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-personas.md
rename to docs/about/all/spryker-marketplace/marketplace-personas.md
index f19fb3fe32d..011acff8957 100644
--- a/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-personas.md
+++ b/docs/about/all/spryker-marketplace/marketplace-personas.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-personas.html
 ---
 title: Marketplace personas
 description: This document describes key users that cooperate in the Marketplace environment.
diff --git a/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-storefront.md b/docs/about/all/spryker-marketplace/marketplace-storefront.md
similarity index 99%
rename from docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-storefront.md
rename to docs/about/all/spryker-marketplace/marketplace-storefront.md
index a92d16187eb..fbd072412a4 100644
--- a/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-storefront.md
+++ b/docs/about/all/spryker-marketplace/marketplace-storefront.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-storefront.html
 ---
 title: Marketplace Storefront
 description: This document describes the peculiarities of the Marketplace Storefront application.
diff --git a/docs/scos/user/intro-to-spryker/spryker-marketplace/merchant-onboarding.md b/docs/about/all/spryker-marketplace/merchant-onboarding.md
similarity index 99%
rename from docs/scos/user/intro-to-spryker/spryker-marketplace/merchant-onboarding.md
rename to docs/about/all/spryker-marketplace/merchant-onboarding.md
index 9cd884c175d..d2ee872c92a 100644
--- a/docs/scos/user/intro-to-spryker/spryker-marketplace/merchant-onboarding.md
+++ b/docs/about/all/spryker-marketplace/merchant-onboarding.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/spryker-marketplace/merchant-onboarding.html
 ---
 title:  Merchant onboarding
 description: This document describes the onboarding process for merchants and gives step-by-step instructions for marketplace operators.
diff --git a/docs/scos/user/intro-to-spryker/spryker-marketplace/merchant-portal.md b/docs/about/all/spryker-marketplace/merchant-portal.md
similarity index 97%
rename from docs/scos/user/intro-to-spryker/spryker-marketplace/merchant-portal.md
rename to docs/about/all/spryker-marketplace/merchant-portal.md
index 18dd7604f33..11540cdd0f5 100644
--- a/docs/scos/user/intro-to-spryker/spryker-marketplace/merchant-portal.md
+++ b/docs/about/all/spryker-marketplace/merchant-portal.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/spryker-marketplace/merchant-portal.html
 ---
 title: Merchant Portal
 description: This document describes the peculiarities of the Merchant Portal application.
diff --git a/docs/scos/user/intro-to-spryker/spryker-marketplace/spryker-marketplace.md b/docs/about/all/spryker-marketplace/spryker-marketplace.md
similarity index 96%
rename from docs/scos/user/intro-to-spryker/spryker-marketplace/spryker-marketplace.md
rename to docs/about/all/spryker-marketplace/spryker-marketplace.md
index 5f1f535be29..48769e15a04 100644
--- a/docs/scos/user/intro-to-spryker/spryker-marketplace/spryker-marketplace.md
+++ b/docs/about/all/spryker-marketplace/spryker-marketplace.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/spryker-marketplace/spryker-marketplace.html
 ---
 title: Spryker Marketplace
 description: This document is an overview of Spryker Marketplace
diff --git a/docs/scos/user/intro-to-spryker/spryker-release-process.md b/docs/about/all/spryker-release-process.md
similarity index 97%
rename from docs/scos/user/intro-to-spryker/spryker-release-process.md
rename to docs/about/all/spryker-release-process.md
index f4d4be37f46..22d122a5e48 100644
--- a/docs/scos/user/intro-to-spryker/spryker-release-process.md
+++ b/docs/about/all/spryker-release-process.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/spryker-release-process.html
 ---
 title: Spryker release process
 last_updated: Jun 16, 2021
@@ -37,4 +38,4 @@ Also, Code Releases are not incorporated into the Demo Shops and can contain bet
 ## Product releases
 A product release is done every several months. The product release has its own version and is accompanied by [release notes](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes.html).  The product release code is stored in our [B2B Demo Shop repository](https://github.com/spryker-shop/b2b-demo-shop) and [B2C Demo Shop repository](https://github.com/spryker-shop/b2c-demo-shop) and includes a specific feature set that we believe is best suitable for each vertical.
 
-A product release does not include beta modules. All of its features are integrated and tested in the Demo Shops, as well as fully documented.
\ No newline at end of file
+A product release does not include beta modules. All of its features are integrated and tested in the Demo Shops, as well as fully documented.
diff --git a/docs/scos/user/intro-to-spryker/support/case-escalation.md b/docs/about/all/support/case-escalation.md
similarity index 98%
rename from docs/scos/user/intro-to-spryker/support/case-escalation.md
rename to docs/about/all/support/case-escalation.md
index 4964e775a3f..eacae2ed70e 100644
--- a/docs/scos/user/intro-to-spryker/support/case-escalation.md
+++ b/docs/about/all/support/case-escalation.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/support/case-escalation.html
 ---
 title: Case escalation
 last_updated: Sep 6, 2021
@@ -88,4 +89,4 @@ If you feel that your issue is not receiving the attention it deserves, or if yo
 There is also a link in the signature of every mail sent by our support representatives that you can use to ask for an increase in priority.
 Both options lead to a form where we ask you to explain why the priority of your case should be increased in relation to the other cases we currently work on. Make sure to provide relevant reasons for why we should increase the priority of your request.
 
-{% endinfo_block %}
\ No newline at end of file
+{% endinfo_block %}
diff --git a/docs/scos/user/intro-to-spryker/support/escalations.md b/docs/about/all/support/escalations.md
similarity index 98%
rename from docs/scos/user/intro-to-spryker/support/escalations.md
rename to docs/about/all/support/escalations.md
index 49c8ef781ec..3ba3f6c7262 100644
--- a/docs/scos/user/intro-to-spryker/support/escalations.md
+++ b/docs/about/all/support/escalations.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/support/escalations.html
 ---
 title: Escalations
 last_updated: Oct 25, 2021
diff --git a/docs/scos/user/intro-to-spryker/support/getting-support.md b/docs/about/all/support/getting-support.md
similarity index 96%
rename from docs/scos/user/intro-to-spryker/support/getting-support.md
rename to docs/about/all/support/getting-support.md
index 5abd907c816..999a5482d16 100644
--- a/docs/scos/user/intro-to-spryker/support/getting-support.md
+++ b/docs/about/all/support/getting-support.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/support/getting-support.html
 ---
 title: Getting support
 last_updated: Jun 16, 2021
diff --git a/docs/scos/user/intro-to-spryker/support/guidelines-for-new-gdpr-rules.md b/docs/about/all/support/guidelines-for-new-gdpr-rules.md
similarity index 98%
rename from docs/scos/user/intro-to-spryker/support/guidelines-for-new-gdpr-rules.md
rename to docs/about/all/support/guidelines-for-new-gdpr-rules.md
index 84260ab6c34..51008d2d544 100644
--- a/docs/scos/user/intro-to-spryker/support/guidelines-for-new-gdpr-rules.md
+++ b/docs/about/all/support/guidelines-for-new-gdpr-rules.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/support/guidelines-for-new-gdpr-rules.html
 ---
 title: Guidelines for new GDPR rules
 description: GDPR contains rules relating to the protection and control of personal data.
diff --git a/docs/scos/user/intro-to-spryker/support/handling-security-issues.md b/docs/about/all/support/handling-security-issues.md
similarity index 97%
rename from docs/scos/user/intro-to-spryker/support/handling-security-issues.md
rename to docs/about/all/support/handling-security-issues.md
index f0c4c3a0dbf..d0700ce6f99 100644
--- a/docs/scos/user/intro-to-spryker/support/handling-security-issues.md
+++ b/docs/about/all/support/handling-security-issues.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/support/handling-security-issues.html
 ---
 title: Handling security issues
 description: Use this article to learn how to report a security issue and to understand how we handle these reports.
diff --git a/docs/scos/user/intro-to-spryker/support/how-spryker-support-works.md b/docs/about/all/support/how-spryker-support-works.md
similarity index 98%
rename from docs/scos/user/intro-to-spryker/support/how-spryker-support-works.md
rename to docs/about/all/support/how-spryker-support-works.md
index 2d1ae0c36d7..a070e7bc313 100644
--- a/docs/scos/user/intro-to-spryker/support/how-spryker-support-works.md
+++ b/docs/about/all/support/how-spryker-support-works.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html
 ---
 title: How Spryker Support works
 last_updated: Jun 16, 2021
diff --git a/docs/scos/user/intro-to-spryker/support/how-to-contact-spryker-support.md b/docs/about/all/support/how-to-contact-spryker-support.md
similarity index 95%
rename from docs/scos/user/intro-to-spryker/support/how-to-contact-spryker-support.md
rename to docs/about/all/support/how-to-contact-spryker-support.md
index e3e0086016d..56ec3817688 100644
--- a/docs/scos/user/intro-to-spryker/support/how-to-contact-spryker-support.md
+++ b/docs/about/all/support/how-to-contact-spryker-support.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/support/how-to-contact-spryker-support.html
 ---
 title: How to contact Spryker Support
 last_updated: Jun 16, 2021
diff --git a/docs/scos/user/intro-to-spryker/support/how-to-get-the-most-out-of-spryker-support.md b/docs/about/all/support/how-to-get-the-most-out-of-spryker-support.md
similarity index 98%
rename from docs/scos/user/intro-to-spryker/support/how-to-get-the-most-out-of-spryker-support.md
rename to docs/about/all/support/how-to-get-the-most-out-of-spryker-support.md
index 4eb1d590d54..54e7ae9762f 100644
--- a/docs/scos/user/intro-to-spryker/support/how-to-get-the-most-out-of-spryker-support.md
+++ b/docs/about/all/support/how-to-get-the-most-out-of-spryker-support.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/support/how-to-get-the-most-out-of-spryker-support.html
 ---
 title: How to get the most out of Spryker Support
 last_updated: Jun 16, 2021
diff --git a/docs/scos/user/intro-to-spryker/support/how-to-share-secrets-with-the-spryker-support-team.md b/docs/about/all/support/how-to-share-secrets-with-the-spryker-support-team.md
similarity index 96%
rename from docs/scos/user/intro-to-spryker/support/how-to-share-secrets-with-the-spryker-support-team.md
rename to docs/about/all/support/how-to-share-secrets-with-the-spryker-support-team.md
index 651dd890997..2b550daf85f 100644
--- a/docs/scos/user/intro-to-spryker/support/how-to-share-secrets-with-the-spryker-support-team.md
+++ b/docs/about/all/support/how-to-share-secrets-with-the-spryker-support-team.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/support/how-to-share-secrets-with-the-spryker-support-team.html
 ---
 title: How to share secrets with the Spryker Support Team
 description: Learn how to share secrets with the Spryker Support Team
diff --git a/docs/scos/user/intro-to-spryker/support/how-to-use-the-support-portal.md b/docs/about/all/support/how-to-use-the-support-portal.md
similarity index 98%
rename from docs/scos/user/intro-to-spryker/support/how-to-use-the-support-portal.md
rename to docs/about/all/support/how-to-use-the-support-portal.md
index 146e01ac257..2febc7030c1 100644
--- a/docs/scos/user/intro-to-spryker/support/how-to-use-the-support-portal.md
+++ b/docs/about/all/support/how-to-use-the-support-portal.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/support/how-to-use-the-support-portal.html
 ---
 title: How to use the Support Portal
 last_updated: Sep 28, 2021
diff --git a/docs/scos/user/intro-to-spryker/support/special-prepare-for-a-busy-season.md b/docs/about/all/support/special-prepare-for-a-busy-season.md
similarity index 98%
rename from docs/scos/user/intro-to-spryker/support/special-prepare-for-a-busy-season.md
rename to docs/about/all/support/special-prepare-for-a-busy-season.md
index a251da39ce3..9f37b3f596b 100644
--- a/docs/scos/user/intro-to-spryker/support/special-prepare-for-a-busy-season.md
+++ b/docs/about/all/support/special-prepare-for-a-busy-season.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/support/special-prepare-for-a-busy-season.html
 ---
 title: Special- Prepare for a busy season
 last_updated: Jun 16, 2021
diff --git a/docs/scos/user/intro-to-spryker/support/understand-slas.md b/docs/about/all/support/understand-slas.md
similarity index 99%
rename from docs/scos/user/intro-to-spryker/support/understand-slas.md
rename to docs/about/all/support/understand-slas.md
index 74f38fe1d94..085f83b9db9 100644
--- a/docs/scos/user/intro-to-spryker/support/understand-slas.md
+++ b/docs/about/all/support/understand-slas.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/support/understand-slas.html
 ---
 title: Understand SLAs
 last_updated: Sep 6, 2021
diff --git a/docs/scos/user/intro-to-spryker/support/understanding-project-and-core-level-fixes.md b/docs/about/all/support/understanding-project-and-core-level-fixes.md
similarity index 95%
rename from docs/scos/user/intro-to-spryker/support/understanding-project-and-core-level-fixes.md
rename to docs/about/all/support/understanding-project-and-core-level-fixes.md
index af5e2c70550..6aa2934b937 100644
--- a/docs/scos/user/intro-to-spryker/support/understanding-project-and-core-level-fixes.md
+++ b/docs/about/all/support/understanding-project-and-core-level-fixes.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/support/understanding-project-and-core-level-fixes.html
 ---
 title: Understanding Project and Core Level Fixes
 last_updated: Jun 16, 2021
@@ -27,4 +28,3 @@ While often taking a considerable amount of time, depending on the urgency of a
 ## Summary
 
 Wherever the circumstances allow, we try to provide a core-level fix. If the problem is sufficiently urgent, there might be an option to develop a project-level fix for certain problems; however, this should always be viewed as a temporary solution.
-
diff --git a/docs/scos/user/intro-to-spryker/support/understanding-ticket-status.md b/docs/about/all/support/understanding-ticket-status.md
similarity index 98%
rename from docs/scos/user/intro-to-spryker/support/understanding-ticket-status.md
rename to docs/about/all/support/understanding-ticket-status.md
index 96b0d5faa3a..71ab9b012a8 100644
--- a/docs/scos/user/intro-to-spryker/support/understanding-ticket-status.md
+++ b/docs/about/all/support/understanding-ticket-status.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/support/understanding-ticket-status.html
 ---
 title: Understanding ticket status
 last_updated: Oct 8, 2021
diff --git a/docs/scos/user/intro-to-spryker/supported-browsers.md b/docs/about/all/supported-browsers.md
similarity index 97%
rename from docs/scos/user/intro-to-spryker/supported-browsers.md
rename to docs/about/all/supported-browsers.md
index c9b83caf852..97f02258f22 100644
--- a/docs/scos/user/intro-to-spryker/supported-browsers.md
+++ b/docs/about/all/supported-browsers.md
@@ -9,6 +9,8 @@ redirect_from:
   - /docs/marketplace/dev/setup/202307.0/marketplace-supported-browsers.html
   - /docs/marketplace/dev/setup/202212.0/marketplace-supported-browsers.html
   - /docs/marketplace/dev/setup/202204.0/marketplace-supported-browsers.html
+  - /docs/scos/user/intro-to-spryker/supported-browsers.html
+  
 ---
 
 
diff --git a/docs/scos/user/intro-to-spryker/whats-new/ie11-end-of-life.md b/docs/about/all/whats-new/ie11-end-of-life.md
similarity index 96%
rename from docs/scos/user/intro-to-spryker/whats-new/ie11-end-of-life.md
rename to docs/about/all/whats-new/ie11-end-of-life.md
index 59afea839ec..09944bdcc32 100644
--- a/docs/scos/user/intro-to-spryker/whats-new/ie11-end-of-life.md
+++ b/docs/about/all/whats-new/ie11-end-of-life.md
@@ -1,8 +1,10 @@
+  - /docs/scos/user/intro-to-spryker/whats-new/ie11-end-of-life.html
 ---
 title: IE11 end of life
 description: Microsoft announced that the Internet Explorer 11 desktop application would be retired on June 15, 2022, for specific versions of Windows 10. Legacy Internet Explorer-based websites and applications will continue to work with Microsoft Edge’s built-in Internet Explorer mode.
 last_updated: June 8, 2022
 template: concept-topic-template
+redirect_from:
 ---
 
 Microsoft announced that the Internet Explorer 11 (IE11) desktop application would be retired on June 15, 2022, for specific versions of Windows 10. Legacy Internet Explorer-based websites and applications will continue to work with Microsoft Edge’s built-in Internet Explorer mode.
diff --git a/docs/scos/user/intro-to-spryker/whats-new/php8-as-a-minimum-version-for-all-spryker-projects.md b/docs/about/all/whats-new/php8-as-a-minimum-version-for-all-spryker-projects.md
similarity index 95%
rename from docs/scos/user/intro-to-spryker/whats-new/php8-as-a-minimum-version-for-all-spryker-projects.md
rename to docs/about/all/whats-new/php8-as-a-minimum-version-for-all-spryker-projects.md
index 0750c622595..18e39332136 100644
--- a/docs/scos/user/intro-to-spryker/whats-new/php8-as-a-minimum-version-for-all-spryker-projects.md
+++ b/docs/about/all/whats-new/php8-as-a-minimum-version-for-all-spryker-projects.md
@@ -1,8 +1,10 @@
+  - /docs/scos/user/intro-to-spryker/whats-new/php8-as-a-minimum-version-for-all-spryker-projects.html
 ---
 title: PHP 8.1 as the minimum version for all Spryker projects
 description: End of November 2022, Spryker will release a new version of its Demo Shops requiring PHP 8.1 as the minimum version.
 last_updated: November 22, 2022
 template: concept-topic-template
+redirect_from:
 ---
 
 
diff --git a/docs/scos/user/intro-to-spryker/whats-new/security-audit-reports/2019.11-security-audit-by-sektioneins.md b/docs/about/all/whats-new/security-audit-reports/2019.11-security-audit-by-sektioneins.md
similarity index 96%
rename from docs/scos/user/intro-to-spryker/whats-new/security-audit-reports/2019.11-security-audit-by-sektioneins.md
rename to docs/about/all/whats-new/security-audit-reports/2019.11-security-audit-by-sektioneins.md
index 58a31528607..ee7ccf5063f 100644
--- a/docs/scos/user/intro-to-spryker/whats-new/security-audit-reports/2019.11-security-audit-by-sektioneins.md
+++ b/docs/about/all/whats-new/security-audit-reports/2019.11-security-audit-by-sektioneins.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/whats-new/security-audit-reports/2019.11-security-audit-by-sektioneins.html
 ---
 title: 2019.11 — Security audit by SektionEins
 description: This page contains the report of the audit performed on Spryker Commerce OS.
@@ -51,4 +52,4 @@ The safe use of functions and the lack of critical vulnerabilities such as SQL i
 
 For each of the security vulnerabilities, a detailed risk analysis has been performed that is documented throughout the report. For more information, please reach out for a more extended version of this report to [Spryker Systems](mailto:academy@spryker.com).
 
-For a list of secure coding recommendations, see [Secure Coding Practices](/docs/dg/dev/guidelines/coding-guidelines/secure-coding-practices.html).
\ No newline at end of file
+For a list of secure coding recommendations, see [Secure Coding Practices](/docs/dg/dev/guidelines/coding-guidelines/secure-coding-practices.html).
diff --git a/docs/scos/user/intro-to-spryker/whats-new/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.md b/docs/about/all/whats-new/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.md
similarity index 95%
rename from docs/scos/user/intro-to-spryker/whats-new/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.md
rename to docs/about/all/whats-new/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.md
index 01759687900..144eaca3626 100644
--- a/docs/scos/user/intro-to-spryker/whats-new/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.md
+++ b/docs/about/all/whats-new/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/whats-new/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.html
 ---
 title: 2020.11 — Penetration test by Port Zero (executive summary)
 description: Results of penetration tests of the Spryker Commerce B2C and Spryker Commerce B2B.
@@ -25,4 +26,3 @@ During the penetration test, a few medium- and high-rated vulnerabilities such a
 In summary, the security of the shop systems is ensured by effective protection measures and can be enhanced at some points.
 
 For each of the security vulnerabilities, a detailed risk analysis has been performed that is documented throughout the report. For more information, please reach out for a more extended version of this report to Spryker Systems.
-
diff --git a/docs/scos/user/intro-to-spryker/whats-new/security-updates.md b/docs/about/all/whats-new/security-updates.md
similarity index 94%
rename from docs/scos/user/intro-to-spryker/whats-new/security-updates.md
rename to docs/about/all/whats-new/security-updates.md
index 4b53b28e8eb..3d1dadcdb79 100644
--- a/docs/scos/user/intro-to-spryker/whats-new/security-updates.md
+++ b/docs/about/all/whats-new/security-updates.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/whats-new/security-updates.html
 ---
 title: Security updates
 description: Learn about the security updates that happened to the Spryker Commerce OS.
diff --git a/docs/scos/user/intro-to-spryker/whats-new/supported-versions-of-php.md b/docs/about/all/whats-new/supported-versions-of-php.md
similarity index 99%
rename from docs/scos/user/intro-to-spryker/whats-new/supported-versions-of-php.md
rename to docs/about/all/whats-new/supported-versions-of-php.md
index 98c004ef805..b05a79c0b4b 100644
--- a/docs/scos/user/intro-to-spryker/whats-new/supported-versions-of-php.md
+++ b/docs/about/all/whats-new/supported-versions-of-php.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/whats-new/supported-versions-of-php.html
 ---
 title: Supported versions of PHP
 description: This document provides information about the PHP versions Spryker supports.
diff --git a/docs/scos/user/intro-to-spryker/whats-new/upcoming-major-module-releases.md b/docs/about/all/whats-new/upcoming-major-module-releases.md
similarity index 94%
rename from docs/scos/user/intro-to-spryker/whats-new/upcoming-major-module-releases.md
rename to docs/about/all/whats-new/upcoming-major-module-releases.md
index ca615fa072b..9a351606f02 100644
--- a/docs/scos/user/intro-to-spryker/whats-new/upcoming-major-module-releases.md
+++ b/docs/about/all/whats-new/upcoming-major-module-releases.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/whats-new/upcoming-major-module-releases.html
 ---
 title: Upcoming major module releases
 description: Learn what modules and when will have the next major versions release
diff --git a/docs/scos/user/intro-to-spryker/whats-new/whats-new.md b/docs/about/all/whats-new/whats-new.md
similarity index 99%
rename from docs/scos/user/intro-to-spryker/whats-new/whats-new.md
rename to docs/about/all/whats-new/whats-new.md
index e1dd8b34ffc..6f1348170de 100644
--- a/docs/scos/user/intro-to-spryker/whats-new/whats-new.md
+++ b/docs/about/all/whats-new/whats-new.md
@@ -1,3 +1,4 @@
+  - /docs/scos/user/intro-to-spryker/whats-new/whats-new.html
 ---
 title: What's new
 description: This article contains information about what’s new and changed in the Spryker Commerce OS.
diff --git a/docs/scos/user/technology-partners/202204.0/customer-service/dixa.md b/docs/scos/user/technology-partners/202204.0/customer-service/dixa.md
deleted file mode 100644
index e84b7ead8d0..00000000000
--- a/docs/scos/user/technology-partners/202204.0/customer-service/dixa.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Dixa
-description: Unify customer engagement across email, chat, messaging and phone in one platform for a better customer and agent experience by integrating Dixa into the Spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/dixa
-originalArticleId: dc886da2-70f3-4c30-9ca7-8a35f3c3de8e
-redirect_from:
-  - /2021080/docs/dixa
-  - /2021080/docs/en/dixa
-  - /docs/dixa
-  - /docs/en/dixa
-  - /docs/scos/user/technology-partners/202200.0/customer-service/dixa.html
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-[ABOUT DIXA](https://dixa.com/)
-
-Meet Conversational Customer Engagement- Helping brands build stronger bonds with their customers and eliminate bad customer service. Dixa is the Conversational Customer Engagement platform of choice for hundreds of the world’s leading brands. Our software unifies customer engagement across email, chat, messaging and phone in one platform for a
-better customer and agent experience.
-Dixa is a truly international company with 14+ nationalities working together in the heart of Copenhagen and with offices in London, Berlin and Kiev. With customers in 20+ countries, Dixa has experienced incredible growth since it’s global launch in 2018, quickly becoming one of Scandinavia’s fastest growing SaaS companies.
-
-YOUR ADVANTAGES:
-
-* Personalized conversations with insights across all channels - so you can lift customer experience dramatically.
-* Intelligent routing and automation of conversations based on context &amp; data - so you can increase agent efficiency significantly.
-* Channel-neutral conversational CE platform with unified data - so you can emposer data-driven decision making on CX.
-* “One Window Wonder” and effortless onboarding of agents - secure fast risk-free shift towards true omni-channel.
-* Agent availability and presence in real-time across all channels and conversations - so you can enable agent/channel blending and boosting agent productivity.
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/customer-service/iadvize.md b/docs/scos/user/technology-partners/202204.0/customer-service/iadvize.md
deleted file mode 100644
index 52acc4eedc4..00000000000
--- a/docs/scos/user/technology-partners/202204.0/customer-service/iadvize.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: iAdvize
-description: Connect customers in need of advice with experts who are available 24/7 via real-time messaging by integrating iAdvize into the Spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/iadvize
-originalArticleId: 9284434a-b0d9-4bde-95b2-3080da8f0f66
-redirect_from:
-  - /2021080/docs/iadvize
-  - /2021080/docs/en/iadvize
-  - /docs/iadvize
-  - /docs/en/iadvize
-  - /docs/scos/user/technology-partners/202200.0/customer-service/iadvize.html
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-<!---[About IADVIZE](https://spryker.com/industry-partner/iadvize/)-->
-
-About IADVIZE
-
-Make Customer Experience authentic
-
-iAdvize is a conversational marketing platform that allows more than 1,500 brands worldwide to make their customer experience authentic. iAdvize connects customers or prospects in need of advice with experts who are available 24/7 via real-time messaging.
-
-YOUR ADVANTAGES:
-
-* Conversational Platform
-* Engage your customers proactively thanks to smart targeting
-* Omni-Channel: Website Chat, Call, Video & Messaging
-* Optimize your conversion rate and customer live time value
-* connectors to your favorite CRM
-* supported by our customer success team
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/customer-service/live-chat-service.md b/docs/scos/user/technology-partners/202204.0/customer-service/live-chat-service.md
deleted file mode 100644
index f2dcddb9757..00000000000
--- a/docs/scos/user/technology-partners/202204.0/customer-service/live-chat-service.md
+++ /dev/null
@@ -1,60 +0,0 @@
----
-title: Live Chat Service
-description: Ensure that live chat helps their customers with new leads and
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/live-chat-service
-originalArticleId: c8b0f94f-7551-4dfc-9b6e-f7d45d6f55bc
-redirect_from:
-  - /2021080/docs/live-chat-service
-  - /2021080/docs/en/live-chat-service
-  - /docs/live-chat-service
-  - /docs/en/live-chat-service
-  - /docs/scos/user/technology-partners/202200.0/customer-service/live-chat-service.html
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-[ABOUT LIVECHAT SERVICE](https://conversation24.de/)
-
-We are the plus for your company
-
-LiveChat Service is an online service provider in the field of live chat. Through trained chat
-operators, LiveChat Service ensures that they help their customers with new leads and
-improved service through the website every day. The chat gives visitors the opportunity to
-ask questions, leave comments and convert. This removes the barrier for chatters to leave
-their data behind. It works faster, friendlier and easier.
-
-YOUR ADVANTAGES:
-
-* Outsourcing chat to LiveChat Service.
-  - More sales: increasing conversion by answering questions of website visitors
-real time.
-  - More service: live chat is an approachable contact channel that you can use
-from 07:00 - 23:00 during the week and from 09:00 - 23:00 during weekends.
-  - More leads: on average we generate up to 20-25% of the chats into leads.
-  - Less phone calls: by answering questions on the website, we’re reducing
-incoming calls.
-
-* LiveChat Software (Knowler).
-  - For companies that wish to chat with their own employees we offer reliable
-and innovative chat software.
-  - Available in 6 languages, including support.
-  - The software allows chat operators to chat efficiently and effective.
-
-* Hybrid chat
-  - We offer hybrid chat, because we can provide clients with both chat services and chat software. This allows companies to chat by themselves but forward chats to our service when they are too busy and/or we chat for them outside office hours.
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/customer-service/optimise-it.md b/docs/scos/user/technology-partners/202204.0/customer-service/optimise-it.md
deleted file mode 100644
index 257fab26797..00000000000
--- a/docs/scos/user/technology-partners/202204.0/customer-service/optimise-it.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: optimise-it
-description: Integrate a custom-tailored chat solution - Optimise it, which can include integrations of messengers (WhatsApp, Facebook, Apple Business Chat), chatbots, video-chat, co-browsing, screen sharing into Spryker  Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/optimise-it
-originalArticleId: 06bc548f-802c-42e2-926c-be4fdec1e622
-redirect_from:
-  - /2021080/docs/optimise-it
-  - /2021080/docs/en/optimise-it
-  - /docs/optimise-it
-  - /docs/en/optimise-it
-  - /docs/scos/user/technology-partners/202200.0/customer-service/optimise-it.html
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-[ABOUT OPTIMIZE IT](https://www.optimise-it.de/de/)
-
-We ❤ Conversations!
-
-As one of the leading chat service providers in Europe, optimise-it focuses primarily on a custom tailored chat solution, which can include integrations of messengers (WhatsApp, Facebook, Apple Business Chat), chatbots, video-chat, co-browsing, screen sharing, and more. With their inhouse chat lab, they provide experienced and performance driven chat agents for their full service customers. optimise-it’s customers include leading companies like BASF, Migros, Eurowings, Deutsche Bahn and 1&1.
-
-YOUR ADVANTAGES:
-
-* Innovative and technically flexible chat solution, custom tailored to the needs and use cases of the customer
-* Integration of messengers (WhatsApp, Facebook, Apple Business Chat), chatbots etc.
-* Popular and modern expansions like video chat, conversational ad, co-browsing, screen sharing and more
-* optimise-it Chat Lab: Experienced and performance driven chat experts for full service projects
-* 100% Privacy and GDPR compliant. All dedicated servers are hosted exceptionally in german data centres
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/finance-and-accounting/collectai.md b/docs/scos/user/technology-partners/202204.0/finance-and-accounting/collectai.md
deleted file mode 100644
index e23426c775a..00000000000
--- a/docs/scos/user/technology-partners/202204.0/finance-and-accounting/collectai.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: CollectAI
-description: Integrate Collect AI into Spryker Commerce OS  to have digitized, AI-based payments and collection services to manage account receivables.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/collect-ai
-originalArticleId: a2a855d2-1680-44e9-9e69-b11a59936f78
-redirect_from:
-  - /2021080/docs/collect-ai
-  - /2021080/docs/en/collect-ai
-  - /docs/collect-ai
-  - /docs/en/collect-ai
-  - /docs/scos/user/technology-partners/202200.0/finance-and-accounting/collectai.html
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-[ABOUT COLLECTAI](https://www.collect.ai/)
-
-Digital accounts receivable management based on AI collection services
-
-collectAI is a software platform providing digitised, AI-based payments and collection services to manage accounts receivables. Covering the end-to-end process from e-invoicing and payment reminder to debt collection it flexibly optimises the goals of collection rates, costs and customer retention. In addition, the company offers payment links as well as business process outsourcing services. It uses digital communication channels and payment solutions for a frictionless checkout process. With its proprietary technology, collectAI fundamentally improves the customer experience, putting the needs and behaviour of the end consumer to the centre of the service. collectAI, founded in 2016, is part of Germany’s largest e-commerce retailer, the Otto Group.
-
-YOUR ADVANTAGES:
-
-* Self-Learning AI for continuously better results
-* Numerous Communication Channels for an individual customer approach
-* Large Selection of Payment Solutions increases the conversion rate
-* Landing Page in your Branding for an individual brand experience - even when paying
-* Customer Orientation (UX / UI) leads to optimal services and satisfied customers
-* Flexible Integration across Platforms for easy implementation in your System
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/finance-and-accounting/nitrobox.md b/docs/scos/user/technology-partners/202204.0/finance-and-accounting/nitrobox.md
deleted file mode 100644
index 64833162239..00000000000
--- a/docs/scos/user/technology-partners/202204.0/finance-and-accounting/nitrobox.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: Nitrobox
-description: Integrate Nitrobox to model, automate and API control customer financial processes.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/nitrobox
-originalArticleId: 6f0a9ca1-dfe5-4331-94dd-c89fe217ad63
-redirect_from:
-  - /2021080/docs/nitrobox
-  - /2021080/docs/en/nitrobox
-  - /docs/nitrobox
-  - /docs/en/nitrobox
-  - /docs/scos/user/technology-partners/202200.0/finance-and-accounting/nitrobox.html
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-[ABOUT NITROBOX](https://www.nitrobox.com/de/)
-
-Nitrobox is a service and solution provider for intelligent order-to-cash processes. Our mission is to be an enabler of new mobility solutions by providing the most flexible Order-to-Cash product on the market. Our central cloud platform enables enterprises to model, automate and API control their financial processes, so they are able to build, charge and scale digital business models such as connected car products, in-car purchase, car sharing or new mobility solutions.The central platform allows a lean approach to charge new and exisiting business models. Start fast, adapt, optimize and scale sky high. Also our ecosystem of integrated partners allows a heads-up start for new financial processes.
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/hosting-providers/claranet.md b/docs/scos/user/technology-partners/202204.0/hosting-providers/claranet.md
deleted file mode 100644
index ff3b74a4c8c..00000000000
--- a/docs/scos/user/technology-partners/202204.0/hosting-providers/claranet.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Claranet
-description: Integrate Claranet hosting solution to host Spryker-based project.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/claranet
-originalArticleId: fb70e246-97a8-4a15-80db-46e66b4eab36
-redirect_from:
-  - /2021080/docs/claranet
-  - /2021080/docs/en/claranet
-  - /docs/claranet
-  - /docs/en/claranet
-  - /docs/scos/user/technology-partners/202200.0/hosting-providers/claranet.html
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-[ABOUT CLARANET](https://www.claranet.de/)
-
- Claranet is your innovative partner for hosting your Spryker Shop. E-commerce businesses face the challenge of constantly delivering new features while guaranteeing a safe and performant operation.As one of Europe's leading managed IT services providers we bring your demands for availability, performance and security into line with the competitive factor agility. We are thus relying on container technologies and a high performance e-commerce stack, enabling you to provide your consumers a high end shopping experience with continuous appearance of new features and high standards of quality.
-
- YOUR ADVANTAGES:
-
-* Rely on our expertise in hosting Spryker on a container-based environment – Spryker Demoshop is powered by Claranet.
-* Fast and easy deployment of new features by leveraging container technologies and further DevOps practices.
-* Highest performance and customer satisfaction with a proven e-commerce stack.
-* The right cloud meeting your requirements–we are certified partner of Google, AWS und Microsoft Azure.
-* Highest availability covered by business SLAs.
-* Guaranteed security for your data ensured by ISO-certification.
-* Expertise in migrating and operating complex applications.
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/hosting-providers/continum.md b/docs/scos/user/technology-partners/202204.0/hosting-providers/continum.md
deleted file mode 100644
index d09ede41871..00000000000
--- a/docs/scos/user/technology-partners/202204.0/hosting-providers/continum.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Continum
-description: Integrate Continum hosting solution to host Spryker-based project.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/continum
-originalArticleId: efc5b68e-b18f-41f6-90fb-8c30c2ac4a9a
-redirect_from:
-  - /2021080/docs/continum
-  - /2021080/docs/en/continum
-  - /docs/continum
-  - /docs/en/continum
-  - docs/scos/user/technology-partners/202200.0/hosting-providers/continum.html
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-[ABOUT CONTINUM](https://www.continum.net/de/)
-
-The Continum AG is a specialist for high-quality enterprise and application hosting according to the highest security requirements. In state-of-the-art data centers in Germany the company provides managed services according to the highest German privacy policy. Continum is certified to ISO/IEC 27001 and to PCI-DSS (Payment Card Industry Data Security Standard). Business partners have permanent confidence in the outstanding and reliable competence and performance.
-
- YOUR ADVANTAGES:
-
-* Specialist for high-quality enterprise and application hosting
-* More than 20 years of experience in the hosting of complex solutions
-* Digitizing partner for medium-sized businesses with B2B and B2C expertise
-* Flexible private, public and hybrid cloud concepts
-* Guaranteed SLAs and 24/7 support with personal contact person
-* ISO/IEC 27001 and PCI DSS (Payment Card Industry Data Security Standard)
-* Several data centers in Freiburg i.Br., Karlsruhe and Frankfurt/Main
-* Your partner for managed e-commerce hosting and internationalization
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/hosting-providers/heroku.md b/docs/scos/user/technology-partners/202204.0/hosting-providers/heroku.md
deleted file mode 100644
index 2bffd9899a2..00000000000
--- a/docs/scos/user/technology-partners/202204.0/hosting-providers/heroku.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Heroku
-template: concept-topic-template
-last_updated: May 16, 2022
-redirect_from:
-  - /docs/scos/user/technology-partners/202200.0/hosting-providers/heroku.html
----
-
-## Partner Information
-
-[ABOUT HEROKU](https://www.heroku.com/)
-
-Heroku is a container-based cloud Platform as a Service (PaaS). Developers use Heroku to deploy, manage, and scale modern apps. Our platform is elegant, flexible, and easy to use, offering developers the simplest path to getting their apps to market.
-
-Heroku is fully managed, giving developers the freedom to focus on their core product without the distraction of maintaining servers, hardware, or infrastructure. The Heroku experience provides services, tools, workflows, and polyglot support—all designed to enhance developer productivity.
-
-## Related Developer guides
-
-* [Integrating Heroku](/docs/scos/dev/technology-partner-guides/{{page.version}}/hosting-providers/integrating-heroku.html)
-
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
diff --git a/docs/scos/user/technology-partners/202204.0/hosting-providers/metaways.md b/docs/scos/user/technology-partners/202204.0/hosting-providers/metaways.md
deleted file mode 100644
index 1787dd7b9fc..00000000000
--- a/docs/scos/user/technology-partners/202204.0/hosting-providers/metaways.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: Metaways
-description: Integrate Metaways hosting solution to host Spryker-based project.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/metaways
-originalArticleId: 672f7e79-ad0d-4eeb-8c61-64ea6e700d5d
-redirect_from:
-  - /2021080/docs/metaways
-  - /2021080/docs/en/metaways
-  - /docs/metaways
-  - /docs/en/metaways
-  - /docs/scos/user/technology-partners/202200.0/hosting-providers/metaways.html
----
-
-## Partner Information
-
-[ABOUT METAWAYS](https://www.metaways.de/hosting/spryker/?L=1)
-
-Metaways Infosystems stands for multidimensional managed services in hosting of business-critical web applications and e-commerce platforms. At Metaways, sophisticated and innovative e-commerce projects meet experienced system and software architects. Comprehensive technology knowledge and high method competence for scalable application operation, zero downtime deployments as well as automated system and software testing make Metaways a strong hosting partner for agencies and operators.
-
- YOUR ADVANTAGES:
-
-* Platform and application specialists from system and software engineering
-* More than 15 years of experience in hosting enterprise e-commerce projects
-* High identification with technologies, methods and processes in continuous delivery
-* Dynamically scalable Spryker OS Commerce setups with optional content delivery in the cloud (AWS and Akamai)
-* Services for system and software testing (CI, unit testing, automated testing and load and performance testing)
-* Two ISO27001 certified data centers at the Hamburg site
-* Regular contact persons for platform operation and service management
-* Guaranteed SLA at application level
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/hosting-providers/root-360.md b/docs/scos/user/technology-partners/202204.0/hosting-providers/root-360.md
deleted file mode 100644
index 75b735f5a77..00000000000
--- a/docs/scos/user/technology-partners/202204.0/hosting-providers/root-360.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Root 360
-description: Integrate Root 360 hosting solution to host Spryker -based project
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/root360
-originalArticleId: 837b21cc-5bf3-4c7d-8da7-57945a6af0bf
-redirect_from:
-  - /2021080/docs/root360
-  - /2021080/docs/en/root360
-  - /docs/root360
-  - /docs/en/root360
-  - /docs/scos/user/technology-partners/202200.0/hosting-providers/root-360.html
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-[ABOUT ROOT360](https://www.root360.de/)
-
- Root360 designs, implements and operates flexible „Managed Cloud Hosting" solutions based on Amazon Web Services (AWS). These solutions range from automatically scalable online shops to complex global portals. Managed Cloud Hosting from root360 combines professional cloud management with Amazon Web Services (AWS) cloud infrastructure.
-
-YOUR ADVANTAGES:
-
-* 24/7 Premium Management: monitoring, maintaining and supporting of cloud environments based on Amazon Web Services
-* E-Commerce expertise: since our beginnings we have been specialized in E-Commerce hosting
-* Flexibility: our solutions for cloud hosting are as flexible and individual as the business model of your company requires
-* Compliance: hosting in a German data center, fully compliant with German data protection laws (BSI / C5)
-* Speed and Performance: agile approach for short "time-to-market" as well as high performance for fast page load times
-* Cost-effectiveness: pay-as-you-go and cost-optimized billing as well as low management costs
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/ab-testing-and-performance/ab-tasty.md b/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/ab-testing-and-performance/ab-tasty.md
deleted file mode 100644
index eea36a51ca3..00000000000
--- a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/ab-testing-and-performance/ab-tasty.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: AB Tasty
-description: Integrate AB Tasty into Spryker Commerce OS - a complete tool for website and conversion rate optimization, personalization, user engagement, and A/B and MVT testing.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/ab-tasty
-originalArticleId: eaac5623-d807-4057-ae96-50765c872696
-redirect_from:
-  - /2021080/docs/ab-tasty
-  - /2021080/docs/en/ab-tasty
-  - /docs/ab-tasty
-  - /docs/en/ab-tasty
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-[ABOUT ABTASTY](https://www.abtasty.com/)
-
-All-in-one and Expandable Conversion Optimization Platform
-
-AB Tasty is a complete tool for website and conversion rate optimization, personalization, user engagement, and A/B and MVT testing. We serve as your digital lab, equipped with everything you need to create experiments that will help you to better understand your users and customer journeys so that you can create the clearest and most engaging user experience possible, ensuring your website performs well and yields the maximum results.
-
-YOUR ADVANTAGES:
-
-* All-in-one solution: strong tool and many years of experience
-* Support and consulting by experienced conversion experts
-* Efficient and easy-to-use visual editor
-* Strong targeting and segmentation model
-* Extensive and intuitive reporting
-* Extensive and intuitive reporting
-* Company with a reliable infrastructure
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/ab-testing-and-performance/baqend.md b/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/ab-testing-and-performance/baqend.md
deleted file mode 100644
index 660563d3605..00000000000
--- a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/ab-testing-and-performance/baqend.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: Baqend
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/baqend
-originalArticleId: dc885480-133d-423b-b566-e11bfcfe0c39
-redirect_from:
-  - /2021080/docs/baqend
-  - /2021080/docs/en/baqend
-  - /docs/baqend
-  - /docs/en/baqend
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
-
diff --git a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/analytics/channelpilot-analytics.md b/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/analytics/channelpilot-analytics.md
deleted file mode 100644
index 6bea181d164..00000000000
--- a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/analytics/channelpilot-analytics.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: ChannelPilot Analytics
-description: Integrate ChannelPilot Analytics - an innovative, cloud-based marketing solution for online merchants to increase their website traffic and reach.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/channelpilot-analytics
-originalArticleId: 56a3d03b-a02f-468c-ba91-31e422fd458a
-redirect_from:
-  - /2021080/docs/channelpilot-analytics
-  - /2021080/docs/en/channelpilot-analytics
-  - /docs/channelpilot-analytics
-  - /docs/en/channelpilot-analytics
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-[ABOUT CHANNELPILOT](https://channelpilot.com)
-
-ChannelPilot is an innovative, cloud-based marketing solution for online merchants to increase their website traffic and reach. Companies are able to present their products on over 2,000 sales channels across more than 40 countries, for example Google, Yahoo, Bing, affiliate networks, marketplaces such as Amazon and eBay, in addition to social media. The tool goes beyond listing by providing merchants with the means to analyse, optimise and control performance, channels and products based on actionable KPIs. Additional modules include market price analysis and dynamic pricing.
-
-YOUR ADVANTAGES:
-
-* Easy-to-use tool
-* Automated product listing
-* Targeted modulation of activities
-* Full control over activities
-* Reliable forecasts
-* Single interface for each channel
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/analytics/fact-finder.md b/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/analytics/fact-finder.md
deleted file mode 100644
index b71521d44ce..00000000000
--- a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/analytics/fact-finder.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: FACT-Finder
-description: Integrate FACT-Finder for on-site search, navigation, merchandising, personalization and product recommendations in Spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/factfinder
-originalArticleId: e0ad7780-edb5-4c15-bdc0-c4e6f30d7938
-redirect_from:
-  - /2021080/docs/factfinder
-  - /2021080/docs/en/factfinder
-  - /docs/factfinder
-  - /docs/en/factfinder
-related:
-  - title: Installing and configuring FACT-Finder
-    link: docs/scos/dev/technology-partner-guides/page.version/marketing-and-conversion/analytics/fact-finder/installing-and-configuring-fact-finder.html
-  - title: Integrating FACT-Finder
-    link: docs/scos/dev/technology-partner-guides/page.version/marketing-and-conversion/analytics/fact-finder/integrating-fact-finder.html
-  - title: Installing and configuring FACT-Finder NG API
-    link: docs/scos/dev/technology-partner-guides/page.version/marketing-and-conversion/analytics/fact-finder/installing-and-configuring-the-fact-finder-ng-api.html
-  - title: Using FACT-Finder search
-    link: docs/scos/dev/technology-partner-guides/page.version/marketing-and-conversion/analytics/fact-finder/using-fact-finder-search.html
-  - title: Using FACT-Finder tracking
-    link: docs/scos/dev/technology-partner-guides/page.version/marketing-and-conversion/analytics/fact-finder/using-fact-finder-tracking.html
-  - title: Exporting product data for FACT-Finder
-    link: docs/scos/dev/technology-partner-guides/page.version/marketing-and-conversion/analytics/fact-finder/exporting-product-data-for-fact-finder.html
-  - title: Using FACT-Finder recommendation engine
-    link: docs/scos/dev/technology-partner-guides/page.version/marketing-and-conversion/analytics/fact-finder/using-fact-finder-recommendation-engine.html
-  - title: Using FACT-Finder search suggestions
-    link: docs/scos/dev/technology-partner-guides/page.version/marketing-and-conversion/analytics/fact-finder/using-fact-finder-search-suggestions.html
-  - title: Using FACT-Finder campaigns
-    link: docs/scos/dev/technology-partner-guides/page.version/marketing-and-conversion/analytics/fact-finder/using-fact-finder-campaigns.html
----
-
-## Partner Information
-
-[ABOUT FACT-FINDER](http://www.fact-finder.de/)
-
-FACT-Finder is a software for online shops. We provide on-site search, navigation, merchandising, personalisation and product recommendations – with a measurable impact: A/B tests have proven that merchants experience a conversion uplift of 10-33 %. More than 1600 online shops use FACT-Finder, among them are brands like Media Markt, Distrelec, MyTheresa, Misterspex and Bergfreunde.
-
-## FACT-Finder User Management
-
-FACT-Finder has its own User Management (permissions management) functions that allow you to set the authorizations for various modules at a fine, granular level. In this way, for example, individual users can only manage specific channels or check and maintain the associated configurations.
-This system of permissions is based on roles that provide access to the specific modules. These roles can be allocated to the user directly or indirectly via groups. Groups allow complex roles to be allocated in bulk, without having to assign them individually to each user.
-
-## Related Developer guides
-
-* [Integrating FACT-Finder](/docs/scos/dev/technology-partner-guides/{{page.version}}/marketing-and-conversion/analytics/fact-finder/integrating-fact-finder.html)
-* [Installing and configuring FACT-Finder](/docs/scos/dev/technology-partner-guides/{{page.version}}/marketing-and-conversion/analytics/fact-finder/installing-and-configuring-fact-finder.html)
-* [Installing and configuring FACT-Finder NG API](/docs/scos/dev/technology-partner-guides/{{page.version}}/marketing-and-conversion/analytics/fact-finder/installing-and-configuring-the-fact-finder-ng-api.html)
-* [Installing and configuring FACT-Finder web components](/docs/scos/dev/technology-partner-guides/{{page.version}}/marketing-and-conversion/analytics/fact-finder/installing-and-configuring-fact-finder-web-components.html)
-* [Using FACT-Finder campaigns](/docs/scos/dev/technology-partner-guides/{{page.version}}/marketing-and-conversion/analytics/fact-finder/using-fact-finder-campaigns.html)
-* [Using FACT-Finder recommendation engine](/docs/scos/dev/technology-partner-guides/{{page.version}}/marketing-and-conversion/analytics/fact-finder/using-fact-finder-recommendation-engine.html)
-* [Using FACT-Finder search](/docs/scos/dev/technology-partner-guides/{{page.version}}/marketing-and-conversion/analytics/fact-finder/using-fact-finder-search.html)
-* [Using FACT-Finder search suggestions](/docs/scos/dev/technology-partner-guides/{{page.version}}/marketing-and-conversion/analytics/fact-finder/using-fact-finder-search-suggestions.html)
-* [Using FACT-Finder tracking](/docs/scos/dev/technology-partner-guides/{{page.version}}/marketing-and-conversion/analytics/fact-finder/using-fact-finder-tracking.html)
-* [Exporting product data for FACT-Finder](/docs/scos/dev/technology-partner-guides/{{page.version}}/marketing-and-conversion/analytics/fact-finder/exporting-product-data-for-fact-finder.html)
-
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/analytics/haensel-ams.md b/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/analytics/haensel-ams.md
deleted file mode 100644
index b6ed2176797..00000000000
--- a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/analytics/haensel-ams.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: Haensel AMS
-description: Integrate Haensel AMS into Spryker project - a leading technology and data analytics service  that offers you innovative and outstanding machine learning and big data solutions.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/haensel-ams
-originalArticleId: f282ab4f-da56-4ee3-b09c-b91dd1b32a23
-redirect_from:
-  - /2021080/docs/haensel-ams
-  - /2021080/docs/en/haensel-ams
-  - /docs/haensel-ams
-  - /docs/en/haensel-ams
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-[ABOUT HANSEL AMS](https://haensel-ams.com/)
-
-Haensel AMS – Advanced Mathematical Solutions – is a leading technology and data analytics boutique that offers you innovative and outstanding machine learning and big data solutions. We work for our international corporate clients at locations in Germany (Berlin) and the USA (New York). We provide and offer our clients customized solutions, data sovereignty lies with you, we do not collect data, we always bring the optimal Data Analytics solution to you. Our expertise focuses primarily on multi-channel attribution, customer journey analytics and pricing for a wide range of industries, including retail/e-commerce, travel/tourism, finance and logistics.
-Our only internal KPI for success is that our solutions are fully used by YOU !
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/analytics/mindlab.md b/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/analytics/mindlab.md
deleted file mode 100644
index 63f76a8e35a..00000000000
--- a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/analytics/mindlab.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Mindlab
-description: Integrate Mindlab - a leading implementation of challenging analytics projects for websites, apps and intranet systems.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/mindlab
-originalArticleId: 9ed22cbb-d549-4160-86ee-b1ef6932a5ab
-redirect_from:
-  - /2021080/docs/mindlab
-  - /2021080/docs/en/mindlab
-  - /docs/mindlab
-  - /docs/en/mindlab
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-As a web analysis pioneer with 18 years of experience, Mindlab Solutions is one of the leading specialists in the implementation of challenging analytics projects for websites, apps and intranet systems. Germany's leading companies count on Mindlab when it comes to increasing the scope of digital applications, raising customer satisfaction and conversion rates, and evaluating the efficiency of digitally transformed processes.
-
-{% info_block infoBox "Info" %}
-
-This integration is built and supported by our technology partner Mindlab Solutions.
-
-{% endinfo_block %}
-
-## Mindlab Documentation
-
-Spryker customers can easily connect to Mindlab and access comprehensive Mindlab e-commerce reporting. On request, this can be individually adapted to customer-specific questions. The Mindlab analytics solution grows long term with customer requirements and supports individual business models.
-
-For successful e-commerce strategies in today's world, meaningful data analysis is often the only way to continually improve the platform. For this, they need a suitable analytics solution, that will harmonize with the technology and tailor to specific business models.
-
-## Mindlab Download and Support
-
-For downloads, support and additional information send a message to: **[info@mindlab.de](mailto:info@mindlab.de)**.
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/analytics/minubo.md b/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/analytics/minubo.md
deleted file mode 100644
index 445928151ca..00000000000
--- a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/analytics/minubo.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Minubo
-description: Integrate Minubo -  infrastructure and processes provider for a fast-growing omnichannel business.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/minubo
-originalArticleId: a59d9ef6-1912-4b3b-bed6-c6c2ad659a71
-redirect_from:
-  - /2021080/docs/minubo
-  - /2021080/docs/en/minubo
-  - /docs/minubo
-  - /docs/en/minubo
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-[ABOUT MINUBO](https://www.minubo.com/)
-
-Minubo is the Commerce Intelligence Company for omni-channel brands and retailers – solving the top 3 challenges that commerce companies face in becoming data-driven in an omni-channel environment: strategy, people and technology. Fed by a full omni-channel data base, minubo's Analytics & Insights App enables both strategic and operational roles to make better, data-driven decisions – every day. Alongside that, minubo's professional services team helps building the needed infrastructure and processes for a fast-growing omni-channel business. Our customer portfolio includes among others LUSH North America, Scotch & Soda und Intersport.
-
-YOUR ADVANTAGES:
-
-* Out-of-the-box integration of all relevant data sources into one omni-channel data warehouse.
-* Low cost of ownership: The solution is hosted in the cloud and the high level of standardization enables the immediate implementation of a data-driven working environment.
-* Easy-to-use analytics tools for every user group – dashboarding, customer segmentation, Web Pivot for ad-hoc analyses, best practice reports, proactive insights und action recommendation among others.
-* Standardized commerce data model based on industry best practices enables a data-driven working environment from day one.
-* The minubo data feeds and already developed integrations to third-party systems enables flexible use of the data.
-* Implementation and enablement is conducted by our in-house advisory and support team.
-
-## Related Developer guides
-
-* [Installing and configuring Minubo](/docs/scos/dev/technology-partner-guides/{{page.version}}/marketing-and-conversion/analytics/installing-and-integrating-minubo.html)
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/customer-communication/dotdigital.md b/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/customer-communication/dotdigital.md
deleted file mode 100644
index fddbe3fe447..00000000000
--- a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/customer-communication/dotdigital.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Dotdigital
-description: Connect customer data, surface powerful insights, and automate intelligent messages across email, SMS, social, and more by integrating Dotdigital into Spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/dotdigital
-originalArticleId: 809fe6a6-5656-415a-bd26-0646c6ee72e4
-redirect_from:
-  - /2021080/docs/dotdigital
-  - /2021080/docs/en/dotdigital
-  - /docs/dotdigital
-  - /docs/en/dotdigital
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-<!---[ABOUT DOTDIGITAL](https://spryker.com/industry-partner/dotdigital/)-->
-ABOUT DOTDIGITAL
-
-Acquire smarter. Convert faster. Deliver big.
-
-Dotdigital is a leader in customer engagement technology. Dotdigital’s Engagement Cloud is the platform of choice for businesses seeking to engage customers across all touchpoints. The platform’s features empower 4,000+ brands across 150 countries to acquire, convert, and retain customers. Users can connect customer data, surface powerful insights, and automate intelligent messages across email, SMS, social, and more. dotdigital is a global company with over 350 employees, serving companies of all sizes and in all verticals for over 20 years.
-
-YOUR ADVANTAGES:
-
-* Maximize customer engagement with omnichannel marketing.
-* Communicate across a variety of channels – Email, SMS, social, push notifications, web and more.
-* Design stylish campaigns effortlessly with our drag-and-drop tool.
-* Connect and store contact, product and order data in one place to better leverage it across your marketing touchpoints.
-* Use insights to craft dynamic content blocks and ensure relevancy.
-* Segment builder gives you the flexibility to create powerful audience segments based on preferences or any other shared attributes.
-* Boost sales and drive interest with AI-powered product recommendations.
-* Extend brand reach with push messages and re-targeting ads.
-* Leverage our automation builder to create multichannel lifecycle programs.
-* Track preferences, engagements, ROI, and more.
-* Benefit from dedicated support and onboarding teams.
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/customer-communication/episerver.md b/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/customer-communication/episerver.md
deleted file mode 100644
index 89937eb162b..00000000000
--- a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/customer-communication/episerver.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: Episerver
-description: Create a standout experience for customers that unifies digital content, commerce, and marketing in one platform, including omnichannel solutions for smart personalization and intelligent campaigns by integrating Episerver into Spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/episerver
-originalArticleId: cbbe8552-c38a-478d-bcda-cd6b393e895b
-redirect_from:
-  - /2021080/docs/episerver
-  - /2021080/docs/en/episerver
-  - /docs/episerver
-  - /docs/en/episerver
-related:
-  - title: Episerver - Integration into a project
-    link: docs/pbc/all/miscellaneous/page.version/third-party-integrations/marketing-and-conversion/customer-communication/episerver/integrate-episerver.html
-  - title: Episerver - Installation and Configuration
-    link: docs/scos/user/technology-partners/page.version/marketing-and-conversion/customer-communication/episerver/installing-and-configuring-episerver.html
-  - title: Episerver - API Requests
-    link: docs/scos/user/technology-partners/page.version/marketing-and-conversion/customer-communication/episerver/technical-details-and-howtos/episerver-api-requests.html
-  - title: Episerver - Order referenced commands
-    link: docs/scos/user/technology-partners/page.version/marketing-and-conversion/customer-communication/episerver/technical-details-and-howtos/episerver-order-referenced-commands.html
----
-
-## Partner Information
-
-[ABOUT EPISERVER](https://www.episerver.com/)
-
-Episerver empowers digital leaders to easily create standout experiences for customers – everywhere they engage, and always with measurable business results. The Episerver Digital Experience Cloud™ unifies digital content, commerce and marketing in one platform, including omnichannel solutions for smart personalization and intelligent campaigns. Founded in 1994, Episerver has offices in the US, UK, Sweden, Australia, Germany, Denmark, Finland, Norway, the Netherlands, Spain, South Africa, Singapore, Vietnam and the UAE.
-Episerver Intelligent Campaigns is a suite of intelligent marketing automation products. It helps already more than 1.300 companies to quickly create, automate and personalize campaigns across all channels. This includes web, mobile, email, text, social and the Internet of Things. The solution uses artificial intelligence and customer data to send and personalize content based on real-time behavior. Intelligent Campaign automatically tracks and analyzes every customer visit, click, email and purchase, to provide valuable insights about customers and segments. By reaching out to customers at exactly the right time, with exactly the right content, you can quickly increase leads, conversions and revenue.
-
-YOUR ADVANTAGES:
-
-* Omnichannel campaigns: Episerver Campaign helps you easily create, automate and personalize campaigns across all channels.
-* Powered by AI: Personalize every experience based on artificial intelligence, customer data and real-time behavior.
-* Increased engagement: Deliver seamless experiences, get smarter segmentation, and increase engagement and conversions.
-
-## Related Developer guides
-
-* [Episerver API](/docs/pbc/all/miscellaneous/{{page.version}}/third-party-integrations/marketing-and-conversion/customer-communication/episerver/episerver-api.html)
-* [Episerver order reference commands](/docs/pbc/all/miscellaneous/{{page.version}}/third-party-integrations/marketing-and-conversion/customer-communication/episerver/episerver-order-reference-commands.html)
-* [Installing and configuring Episerver](/docs/pbc/all/miscellaneous/{{page.version}}/third-party-integrations/marketing-and-conversion/customer-communication/episerver/install-and-configure-episerver.html)
-* [Integrating Episerver](/docs/pbc/all/miscellaneous/{{page.version}}/third-party-integrations/marketing-and-conversion/customer-communication/episerver/integrate-episerver.html)
-
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/customer-communication/inxmail.md b/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/customer-communication/inxmail.md
deleted file mode 100644
index bee2d468651..00000000000
--- a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/customer-communication/inxmail.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: Inxmail
-description: Support customers and partners with fantastic email marketing service and grow their potential in a targeted way by integrating Inxmail into spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/inxmail
-originalArticleId: 8ec1729f-d277-42ae-b8e2-36e15ff2a937
-redirect_from:
-  - /2021080/docs/inxmail
-  - /2021080/docs/en/inxmail
-  - /docs/inxmail
-  - /docs/en/inxmail
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-![image](https://spryker.s3.eu-central-1.amazonaws.com/docs/Technology+Partners/Marketing+%26+Conversion/inxmail_logo.png)
-
-[ABOUT INXMAIL](https://www.inxmail.com)
-
-With nearly 20 years of experience, we are a pioneer in software development for email marketing. We support our customers and partners with fantastic service and grow their potential in a targeted way. In doing so, we draw upon a broad range of technology and services.Our solutions are influenced by our strong relationships with customers. We flexibly adapt our solutions to meet specific customer needs. Expertise that pays off: We have been implementing successful email marketing and multichannel campaigns for over 2,000 customers in more than 20 countries since 1999.
-
-YOUR ADVANTAGES:
-
-* Broad portfolio of technology, service and know-how - from the standard solution to individual solution packages
-* E-mail delivery solutions for highly personalized newsletters, transaction mails, and automated e-mail campaigns
-* Delivery security via whitelisted mail server even with high mail volumes
-* Powerful interfaces for seamless integration into existing system landscapes
-* Software made and hosted in Germany
-* DSGVO-compliant e-mail marketing
-* Co-founder and member of the Certified Senders Alliance (CSA)
-* Award Winning: Competent, Fast and Reliable Customer Service and Support
-* Personal advice and contact person
-
-
-## Related Developer guides
-
-* [Inxmail API requests](/docs/scos/dev/technology-partner-guides/{{page.version}}/marketing-and-conversion/customer-communication/inxmail/inxmail-api-requests.html)
-* [Inxmail order reference commands](/docs/scos/dev/technology-partner-guides/{{page.version}}/marketing-and-conversion/customer-communication/inxmail/inxmail-order-referenced-commands.html)
-* [Installing and configuring Inxmail](/docs/scos/dev/technology-partner-guides/{{page.version}}/marketing-and-conversion/customer-communication/inxmail/installing-and-configuring-inxmail.html)
-* [Integrating Inxmail](/docs/scos/dev/technology-partner-guides/{{page.version}}/marketing-and-conversion/customer-communication/inxmail/integrating-inxmail.html)
-
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/customer-retention-and-loyalty/namogoo.md b/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/customer-retention-and-loyalty/namogoo.md
deleted file mode 100644
index 1da625c5c5a..00000000000
--- a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/customer-retention-and-loyalty/namogoo.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Namogoo
-description: Identify and block unauthorized ads injected into consumer web sessions that divert customers to competitor offerings by integrating  Namogoo into Spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/namogoo
-originalArticleId: 69018fe0-c91f-48d1-be86-6fa06334ea76
-redirect_from:
-  - /2021080/docs/namogoo
-  - /2021080/docs/en/namogoo
-  - /docs/namogoo
-  - /docs/en/namogoo
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-[ABOUT NAMOGOO](https://www.namogoo.com/)
-
-Preventing Online Journey Hijacking and Boosting eCommerce KPIs
-
-Namogoo is pioneering the market of customer hijacking prevention. Namogoo’s disruptive technology identifies and blocks unauthorized ads injected into consumer web sessions that divert customers to competitor offerings, hurting conversion rates and damaging brand equity. By eliminating these invasive promotions, companies who use Namogoo preserve a distraction-free online customer experience and consistently increase conversions by 2-5%.
-
-YOUR ADVANTAGES:
-
-* Immediate Conversion Uplift of 2-5%
-* Improve cart abandonment and customer retention KPIs
-* Protect brand equity and customer experience
-* Easy deployment, integrated reporting, zero maintenance
-* Cloud-based platform uses AI and machine learning
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/customer-retention-and-loyalty/trustpilot.md b/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/customer-retention-and-loyalty/trustpilot.md
deleted file mode 100644
index 441d077053f..00000000000
--- a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/customer-retention-and-loyalty/trustpilot.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Trustpilot
-description: Integrate Trustpilot that gives people a place to share and discover reviews of businesses, and we give every company the tools to turn consumer feedback into business results
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/trustpilot
-originalArticleId: d26d9e19-afe5-4838-91bc-c3fe1894443e
-redirect_from:
-  - /2021080/docs/trustpilot
-  - /2021080/docs/en/trustpilot
-  - /docs/trustpilot
-  - /docs/en/trustpilot
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-[ABOUT TRUSTPILOT](https://de.business.trustpilot.com/)
-
-The world’s most powerful review platform
-
-Trustpilot is a leading independent review platform – free and open to all. With more than 550 million reviews of over 260,000 domains, Trustpilot gives people a place to share and discover reviews of businesses, and we give every company the tools to turn consumer feedback into business results. Our mission is to bring people and businesses closer together to create ever improving experiences for everyone. Trustpilot reviews are seen more than 2.5 billion times each month by consumers worldwide. With offices in Copenhagen, London, New York, Denver, Berlin, Melbourne and Vilnius, Trustpilot’s 700 employees represent more than 40 different nationalities. For more information, visit https://www.trustpilot.com/
-
-YOUR ADVANTAGES:
-
-* Trustpilot creates the trust that makes potential customers paying customers
-* Trustpilot generates traffic, increases click-through rates, lowers bounce rates and increases conversion rates
-* Trustpilot increases domain presence in organic search results (Google, Bing, Yahoo)
-* Trustpilot can help improve Google Adwords performance (CTR and CVR)
-* Trustpilot provides improved customer understanding and insights
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/customer-retention-and-loyalty/zenloop.md b/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/customer-retention-and-loyalty/zenloop.md
deleted file mode 100644
index 09ec16b819b..00000000000
--- a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/customer-retention-and-loyalty/zenloop.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Zenloop
-description: Collect customer feedback automatically via multiple channels by integrating  Zenlopp into Spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/zenloop
-originalArticleId: 53542a74-7858-44d0-939b-0d9c76aa4011
-redirect_from:
-  - /2021080/docs/zenloop
-  - /2021080/docs/en/zenloop
-  - /docs/zenloop
-  - /docs/en/zenloop
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-[ABOUT ZENLOOP](https://www.zenloop.com)
-
-Automate customer retention
-
-At zenloop, the focus is on the customer – the SaaS platform for customer retention and winback based on the Net Promoter System® (NPS). Companies such as AboutYou, Deichmann and ShopApotheke use zenloop to ask the right questions at the right time and collect customer feedback automatically via multiple channels. The platform uses artificial intelligence to process this feedback and subsequently identifies reasons for customer churn as well as internal weak spots. As a result, zenloop creates an individual communication strategy for every (un)satisfied customers and paves the way to optimized CX, strong customer loyalty and increased CLV.
-
-YOUR ADVANTAGES:
-
-* collect actionable feedback at high response rates up to 25-30%
-* excite and engage your organization with feedback livestreams
-* identify immediate insights and trends with Smart Labels (text analytics)
-* delight promoters and critics with personalized replies to reduce churn
-* empower improvements - route feedback alerts to colleagues
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/personalization-and-cross-selling/8select.md b/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/personalization-and-cross-selling/8select.md
deleted file mode 100644
index b62e9a96252..00000000000
--- a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/personalization-and-cross-selling/8select.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: 8Select
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/8select
-originalArticleId: fba4cfc6-ef7f-477b-8788-3b9ffa1a52c0
-redirect_from:
-  - /2021080/docs/8select
-  - /2021080/docs/en/8select
-  - /docs/8select
-  - /docs/en/8select
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-[ABOUT 8SELECT](https://www.8select.com/en/)
-
-8select offers online retailers and their teams a technical platform to manage their experts, product knowledge, product data and customer interaction and provide interactive content along the customer journey. We deliver our solution as SaaS with easy API access. Managing Human Experience with 8.HX is scalable, simple and efficient - trusted by leading online retailers like HSE24, myToys, Peek&Cloppenburg, VAUDE and Ulla Popken Fashion Group.
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/personalization-and-cross-selling/contentserv.md b/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/personalization-and-cross-selling/contentserv.md
deleted file mode 100644
index 075ca1c32d3..00000000000
--- a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/personalization-and-cross-selling/contentserv.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: Contentserv
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/contentserv-1
-originalArticleId: 6c3cc495-d781-4bc1-bfda-31b00febf221
-redirect_from:
-  - /2021080/docs/contentserv-1
-  - /2021080/docs/en/contentserv-1
-  - /docs/contentserv-1
-  - /docs/en/contentserv-1
----
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
-
diff --git a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/personalization-and-cross-selling/econda.md b/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/personalization-and-cross-selling/econda.md
deleted file mode 100644
index 8805775f1d8..00000000000
--- a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/personalization-and-cross-selling/econda.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: Econda
-description: Store the data, enrich it and provide instant reports by integrating Econda into Spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/econda
-originalArticleId: 55ba509a-6fe7-480d-914f-1bbcf9e84d2f
-redirect_from:
-  - /2021080/docs/econda
-  - /2021080/docs/en/econda
-  - /docs/econda
-  - /docs/en/econda
-  - /docs/scos/user/technology-partners/202108.0/marketing-and-conversion/personalization-and-cross-selling/econda/econda.html
----
-
-## Partner information
-
-[ABOUT ECONDA](https://www.econda.de/)
-
-High performance in E-commerce is our daily bread - yours too? Econda collects billions of E-commerce data from thousands of online shops for more than 1000 customers throughout the world, on a daily basis. We store the data, enrich it and provide instant reports – we compile the user profile and product recommendations and return this to the online shops in real time. Of course all in line with data protection. We manage the flood of data for our customers using the latest methods and cutting edge technology, helping them to capitalize on their E-commerce data.
-
-YOUR ADVANTAGES:
-
-* Spryker Industry Partner – interface to Spryker
-* Data ownership with customers, TÜV certified data protection, according to the EU data protection regulations (in force as of 05/2018) and eprivacy regulation
-* Web and app data acquisitions, Tag Management
-* Cross-channel and cross-device tracking, analyses and personalization
-* Data imports and exports from third party systems with automated matching
-* All in real time: analyses, recommendations and personalization
-* Item-2-item recommendations, thanks to the most innovative data mining and machine learning process (up to 25% of turnover share with good recommendations)
-* Personalization and individualization with the very latest KI methods (up to 40% increase in turnover share, an increase of up to 800% in mailing success.)
-
-## Related Developer guides
-
-* [Installing Econda](/docs/scos/dev/technology-partner-guides/{{page.version}}/marketing-and-conversion/personalization-and-cross-selling/econda/installing-econda.html)
-* [Integrating Econda](/docs/scos/dev/technology-partner-guides/{{page.version}}/marketing-and-conversion/personalization-and-cross-selling/econda/integrating-econda.html)
-* [Integrating Econda cross-selling](/docs/scos/dev/technology-partner-guides/{{page.version}}/marketing-and-conversion/personalization-and-cross-selling/econda/integrating-econda-cross-selling.html)
-* [Adding the Econda tracking code](/docs/scos/dev/technology-partner-guides/{{page.version}}/marketing-and-conversion/personalization-and-cross-selling/econda/adding-the-econda-tracking-code.html)
-* [Exporting Econda data](/docs/scos/dev/technology-partner-guides/{{page.version}}/marketing-and-conversion/personalization-and-cross-selling/econda/exporting-econda-data.html)
-
-
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/personalization-and-cross-selling/nosto.md b/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/personalization-and-cross-selling/nosto.md
deleted file mode 100644
index 69bce23d4c3..00000000000
--- a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/personalization-and-cross-selling/nosto.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Nosto
-description: Empower retailers to build, launch and optimize 1-1 omnichannel marketing campaigns and digital experiences without the need for dedicated IT resources or a lengthy implementation process by integrating Nosto into the Spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/nosto
-originalArticleId: e7d00914-ce24-46dc-a139-0ec2e038ccf9
-redirect_from:
-  - /2021080/docs/nosto
-  - /2021080/docs/en/nosto
-  - /docs/nosto
-  - /docs/en/nosto
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-[ABOUT NOSTO](https://www.nosto.com/)
-
-Powerful Personalization. Made Easy.
-
-Nosto enables retailers to deliver personalized digital shopping experiences at every touch point, across every device. An AI-Powered Personalization Platform designed for ease of use, Nosto empowers retailers to build, launch and optimize 1:1 omnichannel marketing campaigns and digital experiences without the need for dedicated IT resources or a lengthy
-implementation process. Over 2,500 brands in over 100 countries use Nosto to grow their business and delight their customers. Nosto supports its clients from its offices in Helsinki, Berlin, Stockholm, London, New York, Los Angeles and Paris.
-
-YOUR ADVANTAGES:
-
-* No complicated back-end integration or product feed needed for technical setup and deployment
-* Products are automatically indexed (faster go-to-market)
-* Beautifully-designed and intuitive UI
-* Ecommerce professionals can easily access and use different marketing technologies
-* Proprietary machine learning algorithms trained solely on ecommerce data, analyze both online and offline transactional and behavioral data
-* Highly scalable infrastructure capable of dealing with 3Mil concurrent sessions in real time
-* Integrates seamlessly with leading ecommerce technology providers and platforms
-* Segments can be created individually and via Nosto and directly exported to the Facebook, ESP, Google accounts
-* Product recommendations can be used in pop-ups, emails and Facebook ads
-* Extensive technical onboarding, strong support, in-house frontend design team
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/personalization-and-cross-selling/trbo.md b/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/personalization-and-cross-selling/trbo.md
deleted file mode 100644
index 44cd4f9210e..00000000000
--- a/docs/scos/user/technology-partners/202204.0/marketing-and-conversion/personalization-and-cross-selling/trbo.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: trbo
-description: Enable online shops and websites to address visitors individually - onsite, in real-time and fully automated by integrating trbo into the Spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/trbo
-originalArticleId: 066f52aa-3367-4b57-8158-e23df04eb494
-redirect_from:
-  - /2021080/docs/trbo
-  - /2021080/docs/en/trbo
-  - /docs/trbo
-  - /docs/en/trbo
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-[ABOUT TRBO](https://www.trbo.com/en/)
-
-Onsite. Realtime. Smart.trbo GmbH is a Munich-based technology company founded in 2013. With its cloud-based communication tool, the company enables online shops and websites to address visitors individually - onsite, in real-time and fully automated. A self-learning algorithm analyzes user behavior based on more than 50 visitor characteristics. This data then allows a targeted delivery of various layers in the design of the online presence, which demonstrably optimize the shopping experience of website visitors. For website operators this means: increased user engagement, lower bounce rates, better conversion rates, fuller shopping baskets and thus more turnover. trbo's customers include airline holidays, Buffalo, Galeria Kaufhof, L'Oréal, Limango, Lodenfrey, Medion, mydays, Rose Bikes and Thomas Cook AG. trbo GmbH is run by Felix Schirl.
-
-YOUR ADVANTAGES:
-
-* Personalized and targeted user approach - via mobile, tablet and desktop
-* Analysis of more than 50 visitor characteristics in real-time
-* Self-optimizing and data-supported algorithm
-* Individualized layer content in the design of the web shop and tailored to its goals
-* Statistically valid A/B testing and multivariant testing directly in the trbo system
-* Intuitive tool & managed service enable fast implementation
-* Success cases: airberlin holidays (now airline holidays)
-* Newsletter subscription increased by 152 percent
-* ROSE Bikes - Bounce Rate reduced by 9.5 percent
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/marketplace-integrations/channelpilot-marketplace.md b/docs/scos/user/technology-partners/202204.0/marketplace-integrations/channelpilot-marketplace.md
deleted file mode 100644
index 58c58d6ae0a..00000000000
--- a/docs/scos/user/technology-partners/202204.0/marketplace-integrations/channelpilot-marketplace.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: ChannelPilot Marketplace
-description: Provide merchants with the means to analyze, optimize and control performance, channels, and products based on actionable KPIs by integrating Channelpilot into the Spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/channelpilot
-originalArticleId: 74542238-4686-4f7c-ab7e-6c38acc89e7d
-redirect_from:
-  - /2021080/docs/channelpilot
-  - /2021080/docs/en/channelpilot
-  - /docs/channelpilot
-  - /docs/en/channelpilot
-  - /docs/scos/user/technology-partners/202200.0/marketplace-integrations/channelpilot-marketplace.html
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-[ABOUT CHANNELPILOT](https://channelpilot.com)
-
-ChannelPilot is an innovative, cloud-based marketing solution for online merchants to increase their website traffic and reach. Companies are able to present their products on over 2,000 sales channels across more than 40 countries, for example Google, Yahoo, Bing, affiliate networks, marketplaces such as Amazon and eBay, in addition to social media. The tool goes beyond listing by providing merchants with the means to analyse, optimise and control performance, channels and products based on actionable KPIs. Additional modules include market price analysis and dynamic pricing.
-
-YOUR ADVANTAGES:
-
-* Easy-to-use tool
-* Automated product listing
-* Targeted modulation of activities
-* Full control over activities
-* Reliable forecasts
-* Single interface for each channel
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/common-solutions.md b/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/common-solutions.md
deleted file mode 100644
index 2ee7baa67f3..00000000000
--- a/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/common-solutions.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: common solutions
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/common-solutions
-originalArticleId: d69094dd-b80d-466a-813c-d26c3f4f9efe
-redirect_from:
-  - /2021080/docs/common-solutions
-  - /2021080/docs/en/common-solutions
-  - /docs/common-solutions
-  - /docs/en/common-solutions
-  - /docs/scos/user/technology-partners/202200.0/operational-tools-monitoring-legal-etc/common-solutions.html
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
-
diff --git a/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/data-virtuality.md b/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/data-virtuality.md
deleted file mode 100644
index 40d097162c3..00000000000
--- a/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/data-virtuality.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Data Virtuality
-description: Benefit from reducing data integration effort by 80% and gaining faster business insights by integrating Data Virtuality into the Spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/datavirtuality
-originalArticleId: 5de4a6c0-796c-4aa3-baa4-cfae81cc3810
-redirect_from:
-  - /2021080/docs/datavirtuality
-  - /2021080/docs/en/datavirtuality
-  - /docs/datavirtuality
-  - /docs/en/datavirtuality
-  - /docs/scos/user/technology-partners/202200.0/operational-tools-monitoring-legal-etc/data-virtuality.html
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-[ABOUT DATA VIRTUALITY](https://datavirtuality.com/)
-
-Data Virtuality successfully became the fastest growing big data start-up in Germany with offices in Leipzig, Frankfurt am Main and San Francisco.The Data Virtuality Platform enables detailed insights from real time and historical data with any BI tool. By combining data virtualization with an automated ETL engine, customers benefit from reducing their data integration effort by 80% and gaining faster business insights. Make your decisions based on facts. Become data driven while using and accessing all your data from multiple data sources! And everything just by using SQL.
-
-YOUR ADVANTAGES:
-
-* Saves resources by 80%.
-* One programming language – SQL.
-* +150 pre-built connectors for data sources and BI tools.
-* Set up time for solutions in just one day.
-* High performance marketing automation.
-* Grows and changes anytime with customer requirements.
-* Endless compatibility with any data infrastructure.
-* One platform for BI starters, startups to enterprises.
-* Availability of real-time and persisted data.
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/loggly.md b/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/loggly.md
deleted file mode 100644
index 851e4b4c230..00000000000
--- a/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/loggly.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Loggly
-description: Read log messages from a queue and send the messages via https by integrating Loggly into the Spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/loggly-queue
-originalArticleId: 27b2bc47-2cf9-466c-b944-5a9768b601b3
-redirect_from:
-  - /2021080/docs/loggly-queue
-  - /2021080/docs/en/loggly-queue
-  - /docs/loggly-queue
-  - /docs/en/loggly-queue
-  - /docs/scos/user/technology-partners/202200.0/operational-tools-monitoring-legal-etc/loggly.html
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-The [Loggly](https://github.com/spryker-eco/loggly) module provides a plugin to read log messages from a queue and send the messages via https to [Loggly](https://www.loggly.com/).
-
-
-## Related Developer guides
-
-
-* [Loggly](/docs/pbc/all/miscellaneous/{{page.version}}/third-party-integrations/operational-tools-monitoring-legal/loggly/loggly.html)
-* [Configuring Loggly](/docs/pbc/all/miscellaneous/{{page.version}}/third-party-integrations/operational-tools-monitoring-legal/loggly/configure-loggly.html)
-
-
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/mindcurv.md b/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/mindcurv.md
deleted file mode 100644
index 6d9ba031a26..00000000000
--- a/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/mindcurv.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Mindcurv
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/mindcurv
-originalArticleId: c7323c96-85a4-401e-a877-f37278243953
-redirect_from:
-  - /2021080/docs/mindcurv
-  - /2021080/docs/en/mindcurv
-  - /docs/mindcurv
-  - /docs/en/mindcurv
-  - /docs/scos/user/technology-partners/202200.0/operational-tools-monitoring-legal-etc/mindcurv.html
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
-
diff --git a/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/new-relic.md b/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/new-relic.md
deleted file mode 100644
index 52e9ad478dd..00000000000
--- a/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/new-relic.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: New Relic
-description: Monitor the performance and health of your application by integrating New Relic into the Spryker Commerce OS.
-last_updated: Sep 27, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/new-relic
-originalArticleId: 6932e215-8b44-4cb4-b43e-12704e967a45
-redirect_from:
-  - /2021080/docs/new-relic
-  - /2021080/docs/en/new-relic
-  - /docs/new-relic
-  - /docs/en/new-relic
-  - docs/scos/user/technology-partners/202200.0/operational-tools-monitoring-legal-etc/new-relic.html
----
-
-Spryker enables integration with New Relic for performance monitoring. New Relic contains a set of powerful features that help you monitor the performance and health of your application.
-
-## Related Developer guides
-
-* [Installing and configuring New Relic with Vagrant](/docs/scos/dev/technology-partner-guides/{{page.version}}/operational-tools-monitoring-legal-etc/new-relic/installing-and-configuring-new-relic–with–vagrant.html)
-* [Configuring New Relic request logging](/docs/scos/dev/technology-partner-guides/{{page.version}}/operational-tools-monitoring-legal-etc/new-relic/configuring-new-relic-logging.html)
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/plusserver.md b/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/plusserver.md
deleted file mode 100644
index 53850d56195..00000000000
--- a/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/plusserver.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: PlusServer
-description: Monitor the performance of your Spryker Commerce OS by integrating PlusServer into your online shop.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/plusserver
-originalArticleId: 56e02408-2d1c-4b3f-86b5-f3807b325724
-redirect_from:
-  - /2021080/docs/plusserver
-  - /2021080/docs/en/plusserver
-  - /docs/plusserver
-  - /docs/en/plusserver
-  - /docs/scos/user/technology-partners/202200.0/operational-tools-monitoring-legal-etc/plusserver.html
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-[ABOUT PLUSSERVER](https://www.plusserver.com/)
-PlusServer GmbH is the leading managed cloud provider in Germany, Austria and Switzerland. As a cloud optimizer, they offer flexible, reliable and efficient hybrid cloud solutions for medium-sized and large companies from a single source. Thanks to many years of cooperation with leading companies from trade, industry and other sectors, PlusServer GmbH have a deep understanding of the respective trends and challenges. They advise our customers in the choice of architecture and orchestrate all relevant infrastructures to an optimal hybrid cloud environment. They are technology-independent and technically flexible and include dedicated infrastructures, public and private cloud solutions as well as offers from Hyperscalers.
-
-YOUR ADVANTAGES: 
-* Highest performance through optimized solutions
-* Proactive monitoring and 24/7 support
-* Flexible scalability, e.g. for peak loads
-* Experts certified by shop software manufacturers
-* 99.998% average availability in 2017
-* German data protection and secure credit card payment
-* Integrated solutions for IoT and Industry 4.0
-* Comprehensive advice on digitalization
-* Hybrid infrastructures from "on premises" to the cloud
-* Scalable solutions for big data scenarios
-* Partner network of IoT specialists
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/proclane.md b/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/proclane.md
deleted file mode 100644
index d8f93cfcd40..00000000000
--- a/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/proclane.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Proclane
-description: Connect SAP and other ERP systems with your shop application by integrating Proclane into the Spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/proclane
-originalArticleId: c61f1780-f44c-4641-a68f-c0d0fb29ad47
-redirect_from:
-  - /2021080/docs/proclane
-  - /2021080/docs/en/proclane
-  - /docs/proclane
-  - /docs/en/proclane
-  - docs/scos/user/technology-partners/202200.0/operational-tools-monitoring-legal-etc/proclane.html
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-[ABOUT PROCLANE](https://proclane.com/)
-
-PROCLANE Integration is a leading German integration house and specializes in connecting.
-SAP and other ERP systems to eCommerce solutions, such as those required for real-time processes in B2B shops. The integration platform &quot;PROCLANE IntegrationMan&quot; already provides around 80% of all processes for the SAP connection of online shops as standard.
-Integration projects can therefore be implemented very efficiently. In addition to connecting ERP systems to online shops, IntegrationMan can also be used to flexibly integrate PIM, CRM or payment systems.
-
-YOUR ADVANTAGES:
-* Standardized solution for many requirements in ERP / Spryker integration
-* Optimization of all internal data and processes for eCommerce
-* Fully automated transactions
-* Automatic and secure data transmission
-* Easy entry, flexibly expandable
-* Marketplace and logistics connection possible
-* Live monitoring and error handling
-* Increased efficiency and cost savings
-* SAP-certified solution
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/shopmacher.md b/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/shopmacher.md
deleted file mode 100644
index 06a107cadb3..00000000000
--- a/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/shopmacher.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: Shopmacher
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/shopmacher
-originalArticleId: 9ae60ecc-8181-45c1-8797-e5b101e1e61b
-redirect_from:
-  - /2021080/docs/shopmacher
-  - /2021080/docs/en/shopmacher
-  - /docs/shopmacher
-  - /docs/en/shopmacher
-  - /docs/scos/user/technology-partners/202200.0/operational-tools-monitoring-legal-etc/shopmacher.html
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/tideways.md b/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/tideways.md
deleted file mode 100644
index 024fe653fd4..00000000000
--- a/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/tideways.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Tideways
-description: Track and analyze errors and background processed by integrating Tideways intot he Spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/tideways
-originalArticleId: e42c9f43-b61c-4427-ad2a-3389aae909b6
-redirect_from:
-  - /2021080/docs/tideways
-  - /2021080/docs/en/tideways
-  - /docs/tideways
-  - /docs/en/tideways
-  - /docs/scos/user/technology-partners/202200.0/operational-tools-monitoring-legal-etc/tideways.html
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-[ABOUT TIDEWAYS](https://tideways.com/)
-
-Monitoring, Profiling and Exception Tracking. Tideways is an Application-Performance-Monitoring (APM) solution with built-in profiler and automated error tracking. All services are tailor-made for E-commerce systems like Spryker. Your customers are looking for a fast and painless online shopping experiences. Tideways helps you to create that experience through detailed insights about your shop's performance from fronted, checkout and backend to background processes. In addition to a weekly report and overview over your performance, you have the possibility to analyse single database queries or functions in detail.
-
-YOUR ADVANTAGES:
-* Smooth integration into Spryker software with automatic analysis (no further installation or code changes required).
-* Weekly reporting to detect tendencies within your performance.
-* Codeontinuous monitoring with intelligent data segmentation (shops, languages, backend or frontend...).
-* Automated regularly profiling with detailed performance data of outlier requests.
-* Multiple options to prioritize profiling data based on your own criteria.
-* Automated recognition of errors with precise and detailed leads to causes and bugfixing tips.
-
-## Related Developer guides
-
-* [Installing and configuring Tideways](/docs/scos/dev/technology-partner-guides/{{page.version}}/operational-tools-monitoring-legal-etc/installing-and-configuring-tideways-with-vagrant.html)
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/usercentrics.md b/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/usercentrics.md
deleted file mode 100644
index 632fc1eb2a1..00000000000
--- a/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/usercentrics.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Usercentrics
-description: Enable your business to collect, manage and optimize user consents across all digital such as websites or apps by integrating Usercentrics into the Spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/usercentrics
-originalArticleId: c5befac4-d875-4e4e-b20e-59089c27ea38
-redirect_from:
-  - /2021080/docs/usercentrics
-  - /2021080/docs/en/usercentrics
-  - /docs/usercentrics
-  - /docs/en/usercentrics
-  - /docs/scos/user/technology-partners/202200.0/operational-tools-monitoring-legal-etc/usercentrics.html
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-[ABOUT USERCENTRICS](https://usercentrics.com/)
-
-From Consent To Conversion
-
-Headquartered in the heart of Munich, Usercentrics’ vision is to create a new infrastructure for user consent across data architectures - making privacy practical. As a leader in the area of Consent Management Platforms (CMPs), the SaaS solution enables businesses to collect, manage and optimize user consents across all digital channels such as websites or apps. Thus, compliance with current and future international privacy regulations such as GDPR, ePrivacy and CCPA can be ensured. Since its founding in late 2017, the company has grown  dramatically and now counts hundreds of leading organizations as customers. Usercentrics is backed by premier venture capital investors including ALSTIN, Reimann Investors and Cavalry Ventures.
-
-YOUR ADVANTAGES:
-* Bring your legal requirements in harmony with your marketing strategy (A/B Testing...)
-* 100% Customization (design)
-* Legal flexibility
-* Optimize your opt-in rates
-* German-speaking support from Munich / headquaters in Munich
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/vshn.md b/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/vshn.md
deleted file mode 100644
index 1474c5986d3..00000000000
--- a/docs/scos/user/technology-partners/202204.0/operational-tools-monitoring-legal-etc/vshn.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: VSHN
-description: Run your applications agile and 24/7 on any infrastructure by integrating VSHN into the Spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/vshn
-originalArticleId: 69bd6ace-b4a2-4fe2-9102-b12669b3d4b9
-redirect_from:
-  - /2021080/docs/vshn
-  - /2021080/docs/en/vshn
-  - /docs/vshn
-  - /docs/en/vshn
-  - /docs/scos/user/technology-partners/202200.0/operational-tools-monitoring-legal-etc/vshn.html
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-[ABOUT VSHN](https://vshn.ch/)
-
-The DevOps Company
-
-VSHN AG is Switzerland’s leading DevOps, Docker, Kubernetes, Openshift and 24/7 cloud operations partner. VSHN helps software developers to run their applications agile and 24/7 on any infrastructure while relieving the burden on IT operations.
-
-Since 2014 we support 300 customers & partners operating over 900 servers in 20 different clouds and on-premises with more than 62000 combined monitored services. We are ISO 27001 certified and work in accordance with the strict FINMA guidelines to ensure the security and confidentiality of customer data at all times. We also created APPUiO.ch, the Swiss container platform based on Red Hat OpenShift, where we provide managed services on a Platform-as-a-Service (PaaS) on any infrastructure: public, dedicated, private and on-premises.
-
-YOUR ADVANTAGES:
-* Your partner for DevOps, Docker, Kubernetes, Openshift and 24/7 cloud operations partner & application operation.
-* Our automation accelerates development, deployment and operations processes.
-* Shorter time to market due to proven technologies like Git and Docker.
-* APPUiO.ch - the Swiss container platform based on Red Hat OpenShift as Managed Service.
-* Our processes are ISO 27001 certified and we operate according to the Swiss banking standards.
-* Our team of experts is available to you. 24/7 in case of emergency.
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/order-management-erpoms/nekom-cc-gmbh.md b/docs/scos/user/technology-partners/202204.0/order-management-erpoms/nekom-cc-gmbh.md
deleted file mode 100644
index 0c4e6aa889b..00000000000
--- a/docs/scos/user/technology-partners/202204.0/order-management-erpoms/nekom-cc-gmbh.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: NEKOM CC GmbH
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/nekom
-originalArticleId: 1a67e15e-3fde-4fa7-ac70-362acb1132c9
-redirect_from:
-  - /2021080/docs/nekom
-  - /2021080/docs/en/nekom
-  - /docs/nekom
-  - /docs/en/nekom
----
-
-## Partner Information
-
-[ABOUT NEKOM](https://www.nekom.com/)
-
-Scaleable Omnichannel for high-growth brands
-
-NEKOM is an Austrian platform provider for eCommerce services and multichannel processes. The system is completely modularly programmed and can therefore quickly react to your requirements and those of the market. NEKOM also provides the modules as Micro Services. These Microservices are easy and fast to integrate and extend the existing feature set of online shops without large implementation projects and costs. NEKOM’s goal is to provide retailers the best tools to be successful on- and offline.
-
-YOUR ADVANATAGES:
-* Short Time2Market - in 4 weeks to the first orders
-* All commerce processes combined in one cloud based system - from oders over returns to customer care
-* Highest security standards by quarterly PCI certification
-* Open REST and GRPC API for fast integration of third-party systems
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/order-management-erpoms/tradebyte.md b/docs/scos/user/technology-partners/202204.0/order-management-erpoms/tradebyte.md
deleted file mode 100644
index 107abddb6ce..00000000000
--- a/docs/scos/user/technology-partners/202204.0/order-management-erpoms/tradebyte.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Tradebyte
-description: Offer SaaS solutions for the electronic exchange of data amongst manufacturers, brands, retailers, and marketplaces by integrating Tradebyte into the Spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/tradebyte
-originalArticleId: 46d787fb-900d-43ab-b73d-bd2fd49a3479
-redirect_from:
-  - /2021080/docs/tradebyte
-  - /2021080/docs/en/tradebyte
-  - /docs/tradebyte
-  - /docs/en/tradebyte
-  - /docs/scos/user/technology-partners/202200.0/order-management-erpoms/tradebyte.html
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Partner Information
-
-[ABOUT TRADEBYTE](https://www.tradebyte.com/)
-
-Cycle of e-commerce
-
-Tradebyte operates a modern ecosystem for digital commerce and offers SaaS solutions (TB.One, TB.PIM and TB.Market) for the electronic exchange of data amongst manufacturers, brands, retailers and marketplaces. More than 650 vendors, such as Guess, Hallhuber and Christ, and more than 90 retailers and marketplaces, such as Amazon, Otto and Zalando, in 17 countries are connected through the Tradebyte ecosystem. Since May 2016, Tradebyte has been a subsidiary of Zalando SE.
-
-YOUR ADVANATAGES:
-* The Tradebyte ecosystem provides answers to the challenges of the digital transformation in commerce and enables the seamless interconnection of manufacturers, traders and retailers in the digital supply chain.
-* Consistent and standardised exchange formats and transmission paths – supported end-to- end by Tradebyte – enable a fully-automatic and always synchronous data flow.
-* Highly-scalable SaaS solutions building on the modern ecosystem, provide the necessary functions out-of-the-box.
-* The Tradebyte ecosystem overcomes barriers and saves resources with a short time-to-market.
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/adyen.md b/docs/scos/user/technology-partners/202204.0/payment-partners/adyen.md
deleted file mode 100644
index 021f043a9c2..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/adyen.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Adyen
-description: Integrate Adyen into the Spryker Commerce OS to accept e-commerce, mobile, and point-of-sale payments.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/adyen
-originalArticleId: 0d0cbb43-1cdd-47b8-86a1-a963cef8a788
-redirect_from:
-  - /2021080/docs/adyen
-  - /2021080/docs/en/adyen
-  - /docs/adyen
-  - /dFocs/en/adyen
-  - /docs/scos/user/technology-partners/202108.0/payment-partners/adyen/adyen-provided-payment-methods.html
-related:
-  - title: Installing and configuring Adyen
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/adyen/installing-and-configuring-adyen.html
-  - title: Integrating Adyen
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/adyen/integrating-adyen.html
-  - title: Integrating Adyen payment methods
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/adyen/integrating-adyen-payment-methods.html
-  - title: Enabling filtering of payment methods for Ayden
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/adyen/enabling-filtering-of-payment-methods-for-adyen.html
----
-
-## Partner Information
-
-ABOUT ADYEN
-
-Adyen is a global payment company that allows businesses to accept e-commerce, mobile, and point-of-sale payments. Adyen has more than 3,500 customers and is listed on the stock exchange Euronext. Adyen offers merchants online services for accepting electronic payments by payment methods including credit cards, bank based payments such as debit cards, bank transfer, and real-time bank transfers based on online banking. Adyen's online payment platform connects to payment methods across the world. Payment methods include international credit cards, local cash-based methods, such as Boleto in Brazil, and Internet banking methods, such as iDEAL in the Netherlands. The technology platform acts as a payment gateway, payment service provider and offers risk management and local acquiring. At the present time, Adyen only accepts European companies that generate over 50% of their revenue from the European continent.
-
-## Related Developer guides
-
-* [Installing and configuring Adyen](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/adyen/installing-and-configuring-adyen.html)
-* [Integrating Adyen](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/adyen/integrating-adyen.html)
-* [Integrating Adyen payment methods](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/adyen/integrating-adyen-payment-methods.html)
-* [Enabling filtering of payment methods for Ayden](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/adyen/enabling-filtering-of-payment-methods-for-adyen.html)
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/afterpay.md b/docs/scos/user/technology-partners/202204.0/payment-partners/afterpay.md
deleted file mode 100644
index 4696c0a3c96..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/afterpay.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: AfterPay
-description: AfterPay that can be integrated into the Spryker-based project, provides invoice solutions as an unitary brand in nine European countries.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/afterpay
-originalArticleId: 3ed914a1-aa6a-472e-b213-f5e60058cbb1
-redirect_from:
-  - /2021080/docs/afterpay
-  - /2021080/docs/en/afterpay
-  - /docs/afterpay
-  - /docs/en/afterpay
-related:
-  - title: Afterpay - Installation and Configuration
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/afterpay/installing-and-configuring-afterpay.html
----
-
-## Partner Information
-
-[ABOUT AFTERPAY](https://www.afterpay.de/)
-
-Available since 2017, AfterPay provides invoice solutions as an unitary brand in nine European countries. By integrating into the Spryker Commerce OS AfterPay can now be consumed by all Spryker clients as a cross-border Pay-after-delivery solution. AfterPay depicts local consumer and market requirements as well as simplifies international expansion.AfterPay gives you back control of your customer relationship and takes it to the next level. It provides your customers with all the payment flexibility they want while you stay in charge of and extend the branded checkout experience. And it sharpens your competitive edge by sharing their purchasing data with you, so you know who your best customers are and how to retarget them.
-
-YOUR ADVANTAGES:
-
-**Make your brand stand out**
-Extend the branded customer journey beyond checkout. AfterPay keeps your brand in the spotlight and strengthens your customer relationships.
-* Unique hero images in every invoice strengthen your brand and campaign messaging
-* Add product images that remind your customers of the great deal they got and the joy it gives them
-* The entire payment process becomes a way of extending your brand, both in the MyAfterPay portal and emails
-
-**Keep the joy of shopping alive**
-Happy customers buy more. AfterPay hands them control of their payments, giving them an overview of their purchases and the security to spend more.
-* Customers have a complete overview of their entire purchase history at their fingertips, with all the information they need
-* Knowing what you have bought and from whom makes paying easier and reduces the need to call customer service
-* The ability to control when and how to pay lets customers balance payments with their finances
-
-**Use your payment data to drive sales**
-Unlike other pay-after-delivery providers we keep you informed of your customers' payment behaviour, providing you with insights and intelligence that fit your digital ecosystem.
-* AfterPay is integrated with Google Analytics, allowing you to use your insights into payment behaviour in your digital marketing and sales analysis
-* Segment and retarget your best customers based on their payment behaviour
-* Easy access to refund data lets you segment customers after net sales together with their payment behaviour
-
-## Related Developer guides
-
-* [Installing and configuring Afterpay](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/afterpay/installing-and-configuring-afterpay.html)
-* [Integrating Afterpay](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/afterpay/integrating-afterpay.html)
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/amazon-pay.md b/docs/scos/user/technology-partners/202204.0/payment-partners/amazon-pay.md
deleted file mode 100644
index bd97fdd5bc8..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/amazon-pay.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: Amazon Pay
-description: Amazon Pay is a solution that allows buyers to make purchases from Spryker-based shops via their Amazon accounts.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/amazon-pay
-originalArticleId: 0636967e-995e-4f57-b980-eac1b4bcda3e
-redirect_from:
-  - /2021080/docs/amazon-pay
-  - /2021080/docs/en/amazon-pay
-  - /docs/amazon-pay
-  - /docs/en/amazon-pay
-related:
-  - title: Obtaining an Amazon Order Reference and information about shipping addresses
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/amazon-pay/obtaining-an-amazon-order-reference-and-information-about-shipping-addresses.html
-  - title: Amazon Pay - Rendering a “Pay with Amazon” Button on the Cart Page
-  - title: Configuring Amazon Pay
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/amazon-pay/configuring-amazon-pay.html
-  - title: Handling orders with Amazon Pay API
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/amazon-pay/handling-orders-with-amazon-pay-api.html
-  - title: Amazon Pay - Sandbox Simulations
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/amazon-pay/amazon-pay-sandbox-simulations.html
----
-
-## Partner Information
-
-[ABOUT AMAZONPAY](https://pay.amazon.com/de)
-
-Amazon pay is a solution which allows buyers to make purchases via their Amazon accounts. Basically it consists of client side tools (widget, javascripts etc) and Amazon API with SDKs written for different programming languages (PHP, Python, Ruby, Java, C#).
-
-Client side tools are used for displaying GUI elements on some common pages of an internet shop and it includes a "Pay with Amazon" button on the cart page and widgets for selecting checkout options such as delivery address and payment method.
-
-On the server side, there are API functions for after a buyer decides to use Amazon Pay. Once you the "Seller" decides to integrate the shop with Amazon Pay, all necessary credentials will be provided to you create an Amazon account.
-
-Subsequent all integration functionality is provided by Amazon Pay.
-
-## Related Developer guides
-
-* [Configuring Amazon Pay](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/amazon-pay/configuring-amazon-pay.html)
-* [Amazon Pay - Sandbox Simulations](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/amazon-pay/amazon-pay-sandbox-simulations.html)
-* [Amazon Pay - State Machine](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/amazon-pay/amazon-pay-state-machine.html)
-* [Handling orders with Amazon Pay API](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/amazon-pay/handling-orders-with-amazon-pay-api.html)
-* [Obtaining an Amazon Order Reference and information about shipping addresses](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/amazon-pay/obtaining-an-amazon-order-reference-and-information-about-shipping-addresses.html)
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/arvato.md b/docs/scos/user/technology-partners/202204.0/payment-partners/arvato.md
deleted file mode 100644
index e8bd2d4d328..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/arvato.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: Arvato
-description: Evaluate the profitability of your customer relationships through early identification of credit and fraud risks by integrating the Arvato module into the Spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/arvato
-originalArticleId: baf8a048-9b5c-4c45-aaab-c3093f42bc36
-redirect_from:
-  - /2021080/docs/arvato
-  - /2021080/docs/en/arvato
-  - /docs/arvato
-  - /docs/en/arvato
-related:
-  - title: Arvato - Store Order 2.0
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/arvato/arvato-store-order.html
----
-
-## Partner Information
-
-[ABOUT ARVATO](https://finance.arvato.com//de.html)
-
- Arvato Financial Solutions (AFS) represents the professional outsourcing of financial services and integrated commercial management. In the business unit Risk Management AFS supports all risk- and profit-oriented decisions along the customer lifecycle. This e-commerce industry solution allows an evaluation of the profitability of your customer relationships through an early identification of credit and fraud risks. With an active payment method selection you can offer your customer only appropriate payment methods according to their risk profile – online and in real time.
-
- ## Related Developer guides
-
- * [Installing and configuring Arvato](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/arvato/installing-and-configuring-arvato.html)
- * [Arvato - Risk Check](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/arvato/arvato-risk-check.html)
- * [Arvato - Store Order](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/arvato/arvato-store-order.html)  
-
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/billie.md b/docs/scos/user/technology-partners/202204.0/payment-partners/billie.md
deleted file mode 100644
index 12a1b10a265..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/billie.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: Billie
-description: Provide various payment options from Billie.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/billie
-originalArticleId: 5274b1b6-4f70-425b-99a9-d8a266193110
-redirect_from:
-  - /2021080/docs/billie
-  - /2021080/docs/en/billie
-  - /docs/billie
-  - /docs/en/billie
----
-
-## Partner Information
-
-[ABOUT BILLIE](https://www.billie.io/)
-
-B2B-PayAfterDelivery for the 21st century
-
-Billie is Germany’s innovative online-only provider of flexible working capital solutions. Whether it is our award-wining, 100% digital factoring platform or our B2B-PayAfterDelivery solution for online stores:
-
-Aspiring start-ups, established SMEs and world-leading hidden champions all trust in Billie when it comes to fast, reliable and simple liquidity provision.
-
-Focus fully on your core business — Billie takes care of your debtor management, provides a white-label dunning & collection process and includes full protection against payment defaults.
-
-Offer your business customers their preferred payment option, fully integrated into your online store’s checkout process: easily integrate our B2B-PayAfterDelivery module and experience dramatically improved conversion rates by allowing your customers to pay by invoice. Experience reliable payouts to your bank account on the next business day.
-
-YOUR ADVANTAGES:
-* Fully automated PayAfterDelivery module for your B2B-eCommerce store
-* Credit checks and decisions in real time
-* Improved conversion rates during checkout by providing the most preferred B2B-payment method
-* Payouts to your bank account on the next working day
-* 100% protection against payment defaults for all processed invoices
-* Full service coverage of dunning & collection process in your design and wording
-* Holistic management of your debtors
-* Reduced accounting overhead by automated and secure processing of all incoming cash flows
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/billpay.md b/docs/scos/user/technology-partners/202204.0/payment-partners/billpay.md
deleted file mode 100644
index cbb8e6016de..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/billpay.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: Billpay
-description: Billpay is the provider for the preferred, local payment methods Invoice, Direct Debit and Installments.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/billpay
-originalArticleId: 1aba685d-52bb-4060-bed0-62178fa04d71
-redirect_from:
-  - /2021080/docs/billpay
-  - /2021080/docs/en/billpay
-  - /docs/billpay
-  - /docs/en/billpay
----
-
-## Partner Information
-
-[ABOUT BILLPAY](https://www.billpay.de/de/)
-
-BillPay is the DACH market leader for the preferred, local payment methods Invoice, Direct Debit and Installments, making real-time financing decisions with 100% liability shift, so merchants carry zero risk.As only a bank account is required, these payment methods ensure full customer reach. In addition, BillPay's solution is multi-channel so orders can be placed online, through mobile web apps, at the POS or over-the-phone.
-
-
-## Related Developer guides
-
-* [Billpay - Switching invoice payments to a preauthorize mode](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/billpay/billpay-switching-invoice-payments-to-a-preauthorize-mode.html)
-* [Integrating Billpay](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/billpay/integrating-billpay.html)
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
-
-<!---
-
-## DRAFT NOTE: THIS INFO IS HIDDEN TILL WE HAVE FINAL APPROVAL FROM BILLPAY AND THE DEVELOPMENT IS COMPLETED.
-
-## Prerequisites
-
-To use Billpay, you will need to create a Billpay account or use your existing credentials.
-
-If you do not have a Billpay account, you can create one on the Billpay website: [https://www.billpay.de/en//](https://www.billpay.de/en//)
-
-You will also need your Merchant ID, Portal ID and security key - all provided by Billpay.
-
-Additional important information can be found in the Billpay documentation - [https://www.billpay.de/en/shopintegration/techdocs/](https://www.billpay.de/en/shopintegration/techdocs/).
-
-To integrate Billpay make sure you familiar with concept of [Extending Spryker](/docs/dg/dev/backend-development/extend-spryker/spryker-os-module-customisation/extend-the-spryker-core-functionality.html).
-
-## Installation
-
-**Composer dependency**:
-
-To install the module, use composer, [https://getcomposer.org/](https://getcomposer.org/):
-```bashcomposer require spryker-eco/billpay```
-
-**Billpay visuals**:
-
-If you want to use Billpay visuals on your website, please download them directly from Billpay [https://www.billpay.de/en/shopintegration/downloads/](https://www.billpay.de/en/shopintegration/downloads/).
---->
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/braintree.md b/docs/scos/user/technology-partners/202204.0/payment-partners/braintree.md
deleted file mode 100644
index f6738777884..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/braintree.md
+++ /dev/null
@@ -1,69 +0,0 @@
----
-title: Braintree
-description: Braintree provides credit card and PayPal payment methods for Spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/braintree
-originalArticleId: 940c4c06-b484-4eba-b262-14c9c8ba1a58
-redirect_from:
-  - /2021080/docs/braintree
-  - /2021080/docs/en/braintree
-  - /docs/braintree
-  - /docs/en/braintree
-related:
-  - title: Installing and configuring Braintree
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/braintree/installing-and-configuring-braintree.html
-  - title: Integrating Braintree
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/braintree/integrating-braintree.html
-  - title: Braintree - Performing Requests
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/braintree/braintree-performing-requests.html
-  - title: Braintree - Request workflow
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/braintree/braintree-request-workflow.html
----
-
-[ABOUT BRAINTREE](https://www.braintreepayments.com/)
-
-Braintree, a division of PayPal, is a company based in Chicago that specializes in mobile and web payment systems for ecommerce companies. Braintree emphasizes its easy integrations, multiple payment method options (including PayPal and Venmo), simple pricing, security, and support. Braintree provides its customers with a merchant account and a payment gateway, along with various features including recurring billing, credit card storage, support for mobile and international payments, and PCI compliance solutions.
-
-Braintree provides two methods of payment:
-
-* Credit Card
-* PayPal
-
-In order to integrate Braintree payments, a Braintree merchant account should be created and configuration data then could be obtained from Braintree.
-
-There are two types of accounts for the integration:
-
-1. test accounts
-2. live accounts
-
-Both accounts share the same configuration with different values. Braintree uses the idea of having merchants for handling different requests. Each merchant is defined by a merchant ID which will be given by Braintree.
-
-We use state machines for handling and managing orders and payments. To integrate Braintree payments, a state machine for Braintree should be created.
-
-A basic and fully functional state machine is already built (`BraintreePayPal01` and `BraintreeCreditCard01`). You can use the same state machine or build a new one. In case a new state machine has to be built, it is preferred to contact Braintree and confirm the new state machine design and functionality.
-
-The state machine commands and conditions trigger Braintree facade calls in order to perform the needed requests to Braintree. For simplicity, the Braintree facade uses the same calls for both credit card and PayPal payments and automatically distinguishes between the payment methods from the payment entity.
-
-### PCI Compliance
-
-Because of PCI compliance reasons, credit card data is communicated to the third party through JS and AJAX calls (sensitive information stays browser side).
-
-## Related Developer guides
-
-* [Installing and configuring Braintree](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/braintree/installing-and-configuring-braintree.html)
-* [Integrating Braintree](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/braintree/integrating-braintree.html)
-* [Braintree - Request workflow](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/braintree/braintree-request-workflow.html)
-* [Braintree - Performing requests](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/braintree/braintree-performing-requests.html)
-
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/bs-payone.md b/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/bs-payone.md
deleted file mode 100644
index ce072e1551b..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/bs-payone.md
+++ /dev/null
@@ -1,436 +0,0 @@
----
-title: BS Payone
-description: Provide full-service payment service and payment transaction services by integrating BS Payone into your Spryker-based shop.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/payone-v1-1
-originalArticleId: ffd53037-46a0-410e-941c-eb9cd4c3ff22
-redirect_from:
-  - /2021080/docs/payone-v1-1
-  - /2021080/docs/en/payone-v1-1
-  - /docs/payone-v1-1
-  - /docs/en/payone-v1-1
-related:
-  - title: PayOne - Integration into the SCOS Project
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/scos-integration/payone-integration-into-the-scos-project.html
-  - title: PayOne - Risk Check and Address Check
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/scos-integration/payone-risk-check-and-address-check.html
-  - title: PayOne - Prepayment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-prepayment.html
-  - title: PayOne - Authorization and Preauthorization Capture Flows
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-authorization-and-preauthorization-capture-flows.html
-  - title: PayOne - Invoice Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-invoice-payment.html
-  - title: PayOne - Cash on Delivery
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/scos-integration/payone-cash-on-delivery.html
-  - title: PayOne - Credit Card Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-credit-card-payment.html
-  - title: PayOne - Security Invoice Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-security-invoice-payment.html
----
-
-## Partner Information
-
-[ABOUT BS PAYONE](https://www.payone.com/DE-en)
-
-BS PAYONE GmbH is headquartered in Frankfurt am Main and is one of the leading omnichannel-payment providers in Europe. In addition to providing customer support to numerous Savings Banks (Sparkasse) the full-service payment service provider also provides cashless payment transaction services to more than 255,000 customers from stationary trade to the automated and holistic processing of e-commerce and mobile payments.
-
-YOUR ADVANTAGES:
-* **One solution, one partner, one contract**
-<br>Simple & efficient. Technical processing and financial services from a single source.
-* **International payment processing**
-<br>Access to international and local payment methods.
-* **Automatic debtor management**
-<br>Effective accounting support through transaction allocation and reconciliation.
-* **Credit entries independent of payment type**
-<br>Fast returns management. With automated refunds.
-* **Short time to market thanks to plug'n pay**
-<br>1-click checkout and seamless integration. For an increasing conversion rate.
-
-We integrate with a wide range of payment methods that can be configured according to your needs and convenience. Payment method flows are configured using state machines.
-
-Payone provides the following methods of payment:
-* [Credit Card](/docs/scos/user/technology-partners/{{page.version}}/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-credit-card-payment.html)
-* [Direct Debit](/docs/scos/user/technology-partners/{{page.version}}/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-direct-debit-payment.html)
-* [Online Transfer](/docs/scos/user/technology-partners/{{page.version}}/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-online-transfer-payment.html)
-* [Paypal](/docs/scos/user/technology-partners/{{page.version}}/payment-partners/bs-payone/scos-integration/payone-integration-into-the-scos-project.html)
-* [Prepayment](/docs/scos/user/technology-partners/{{page.version}}/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-prepayment.html)
-* [Invoice](/docs/scos/user/technology-partners/{{page.version}}/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-invoice-payment.html)
-* [Security Invoice](/docs/scos/user/technology-partners/{{page.version}}/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-security-invoice-payment.html)
-* [Paypal Express Checkout](/docs/scos/user/technology-partners/{{page.version}}/payment-partners/bs-payone/scos-integration/payone-integration-into-the-scos-project.html)
-
-We use state machines for handling and managing orders and payments. To integrate Payone payments, a state machine for Payone should be created.
-
-A basic and fully functional state machine for each payment method is already built:
-* `PayoneCreditCard.xml`
-* `PayoneDirectDebit.xml`
-* `PayoneEWallet.xml`
-* `PayoneInvoice.xml`
-* `PayoneSecurityInvoice.xml`
-* `PayoneOnlineTransfer.xml`
-* `PayonePrePayment.xml`
-* `PayonePaypalExpressCheckout.xml`
-
-You can use the same state machines or build new ones. The state machine commands and conditions trigger Payone facade calls in order to perform the needed requests to Payone API.
-
-## Integration to Your Project
-
-You can copy over configs to your config from the Payone module's `config.dist.php` file.
-
-The configuration to integrate payments using Payone is:
-* `PAYONE_CREDENTIALS_KEY`: payment portal key (required).
-* `PAYONE_CREDENTIALS_MID`: merchant id (required).
-* `PAYONE_CREDENTIALS_AID`: sub-account id (required).
-* `PAYONE_CREDENTIALS_PORTAL_ID`: payment portal id (required).
-* `PAYONE_MODE`: the mode of the transaction, either test or live (required).
-* `PAYONE_BUSINESS_RELATION`: the business relation of the transaction, b2b or b2c (required).
-* `PAYONE_PAYMENT_GATEWAY_URL`: server-API-URL.
-* `PAYONE_REDIRECT_SUCCESS_URL`: return URL for successful result on redirect.
-* `PAYONE_REDIRECT_ERROR_URL`: return URL for error on redirect.
-* `PAYONE_REDIRECT_BACK_URL`: return URL that will be engaged when user cancels action on redirect.
-* `PAYONE_EMPTY_SEQUENCE_NUMBER`: sequence number that will be used in API requests when ommitted (0 by default).
-* `PAYONE_CREDENTIALS_ENCODING`: encoding of data sent in requests to Payone API ('UTF-8' for the
-* `HOST_YVES`: yves host in order to generate urls inside payone module.
-* `PAYONE_STANDARD_CHECKOUT_ENTRY_POINT_URL`: entry point url to standart checkout in project(or middleware url in project, depending on your implementation).
-* `PAYONE_EXPRESS_CHECKOUT_BACK_URL`: if user presses back button(if so exists) on payone side, this urs is used to redirect user back to shop.
-* `PAYONE_EXPRESS_CHECKOUT_FAILURE_URL`: if something goes wrong when the user is on payone side, redirect here is done.
-
-## Integration with Checkout module (CheckoutDependencyProvider):
-
-Project (demoshop) level `\Pyz\Yves\Checkout\CheckoutDependencyProvider` method `provideDependencies` container has to be extended with the `static::PAYMENT_SUB_FORMS` and `static::PAYMENT_METHOD_HANDLER` keys which have to contain information about PSP payment methods SubForms and SubForms Handlers accordingly.
-
-Add the keys to `\Pyz\Yves\Checkout\CheckoutDependencyProvider::provideDependencies`:
-
-```php
-<?php
-$container[static::PAYMENT_METHOD_HANDLER] = function () {
- $paymentMethodHandler = new StepHandlerPluginCollection();
-
- $paymentMethodHandler->add(new PayoneHandlerPlugin(), PaymentTransfer::PAYONE_INVOICE);
- $paymentMethodHandler->add(new PayoneHandlerPlugin(), PaymentTransfer::PAYONE_SECURITY_INVOICE);
- $paymentMethodHandler->add(new PayoneHandlerPlugin(), PaymentTransfer::PAYONE_CREDIT_CARD);
- $paymentMethodHandler->add(new PayoneHandlerPlugin(), PaymentTransfer::PAYONE_DIRECT_DEBIT);
- $paymentMethodHandler->add(new PayoneHandlerPlugin(), PaymentTransfer::PAYONE_E_WALLET);
- $paymentMethodHandler->add(new PayoneHandlerPlugin(), PaymentTransfer::PAYONE_ONLINE_TRANSFER);
- $paymentMethodHandler->add(new PayoneHandlerPlugin(), PaymentTransfer::PAYONE_PRE_PAYMENT);
- $paymentMethodHandler->add(new PayoneHandlerPlugin(), PaymentTransfer::PAYONE_PAYPAL_EXPRESS_CHECKOUT);
-
- return $paymentMethodHandler;
- };
-
- $container[static::PAYMENT_SUB_FORMS] = function () {
- $paymentSubFormPlugin = new SubFormPluginCollection();
-
- $paymentSubFormPlugin->add(new PayoneInvoiceSubFormPlugin());
- $paymentSubFormPlugin->add(new PayoneSecurityInvoiceSubFormPlugin());
- $paymentSubFormPlugin->add(new PayoneCreditCardSubFormPlugin());
- $paymentSubFormPlugin->add(new PayoneDirectDebitSubFormPlugin());
- $paymentSubFormPlugin->add(new PayoneEWalletSubFormPlugin());
- $paymentSubFormPlugin->add(new PayoneEpsOnlineTransferSubFormPlugin());
- $paymentSubFormPlugin->add(new PayonePrePaymentSubFormPlugin());
-
- return $paymentSubFormPlugin;
- };
-```
-
-The project (Demo Shop) level `\Pyz\Zed\Checkout\CheckoutDependencyProvider` method `provideBusinessLayerDependencies` container has to be extended with the checkout plugins of Payone. This can be done by adding plugins to the related plugins stacks in these methods in `\Pyz\Zed\Checkout\CheckoutDependencyProvider`:
-* `getCheckoutPreConditions`
-* `getCheckoutOrderSavers`
-* `getCheckoutPostHooks`
-
-Add the plugins to `\Pyz\Zed\Checkout\CheckoutDependencyProvider`:
-
-```php
-<?php
-
-namespace Pyz\Zed\Checkout;
-//...
-use SprykerEco\Zed\Payone\Communication\Plugin\Checkout\PayoneCheckoutDoSaveOrderPlugin;
-use SprykerEco\Zed\Payone\Communication\Plugin\Checkout\PayoneCheckoutPostSavePlugin;
-use SprykerEco\Zed\Payone\Communication\Plugin\Checkout\PayoneCheckoutPreConditionPlugin;
-class CheckoutDependencyProvider extends SprykerCheckoutDependencyProvider
-{
-    /**
-     * @param \Spryker\Zed\Kernel\Container $container
-     *
-     * @return \Spryker\Zed\CheckoutExtension\Dependency\Plugin\CheckoutPreConditionPluginInterface[]
-     */
-    protected function getCheckoutPreConditions(Container $container)
-    {
-        return [
-            //...
-            new PayoneCheckoutPreConditionPlugin(),
-            //...
-        ];
-    }
-    /**
-     * @param \Spryker\Zed\Kernel\Container $container
-     *
-     * @return \Spryker\Zed\Checkout\Dependency\Plugin\CheckoutSaveOrderInterface[]|\Spryker\Zed\CheckoutExtension\Dependency\Plugin\CheckoutDoSaveOrderInterface[]
-     */
-    protected function getCheckoutOrderSavers(Container $container)
-    {
-        return [
-            //...
-            new PayoneCheckoutDoSaveOrderPlugin(),
-            //...
-        ];
-    }
-    /**
-     * @param \Spryker\Zed\Kernel\Container $container
-     *
-     * @return \Spryker\Zed\CheckoutExtension\Dependency\Plugin\CheckoutPostSaveInterface[]
-     */
-    protected function getCheckoutPostHooks(Container $container)
-    {
-        return [
-            //...
-            new PayoneCheckoutPostSavePlugin(),
-            //...
-        ];
-    }
-    //...
-}
-```
-
-## Integration with OMS module (OmsDependencyProvider)
-
-Project (demoshop) level `\Pyz\Zed\Oms\OmsDependencyProvider` method `provideBusinessLayerDependencies` container has to be extended with the `static::CONDITION_PLUGINS` and `static::COMMAND_PLUGINS` keys which have to contain information about PSP OMS State Machine conditions and commands plugins.
-
-Add the keys to `\Pyz\Zed\Oms\OmsDependencyProvider`:
-
-```php<?php
-$container->extend(static::CONDITION_PLUGINS, function (ConditionCollectionInterface $conditionCollection) {
- $conditionCollection->add(new PreAuthorizationIsApprovedConditionPlugin(), 'Payone/PreAuthorizationIsApproved');
- $conditionCollection->add(new AuthorizationIsApprovedConditionPlugin(), 'Payone/AuthorizationIsApproved');
- $conditionCollection->add(new CaptureIsApprovedConditionPlugin(), 'Payone/CaptureIsApproved');
- $conditionCollection->add(new RefundIsApprovedConditionPlugin(), 'Payone/RefundIsApproved');
- $conditionCollection->add(new RefundIsPossibleConditionPlugin(), 'Payone/RefundIsPossible');
- $conditionCollection->add(new PreAuthorizationIsErrorConditionPlugin(), 'Payone/PreAuthorizationIsError');
- $conditionCollection->add(new AuthorizationIsErrorConditionPlugin(), 'Payone/AuthorizationIsError');
- $conditionCollection->add(new PreAuthorizationIsRedirectConditionPlugin(), 'Payone/PreAuthorizationIsRedirect');
- $conditionCollection->add(new AuthorizationIsRedirectConditionPlugin(), 'Payone/AuthorizationIsRedirect');
- $conditionCollection->add(new PaymentIsAppointedConditionPlugin(), 'Payone/PaymentIsAppointed');
- $conditionCollection->add(new PaymentIsCaptureConditionPlugin(), 'Payone/PaymentIsCapture');
- $conditionCollection->add(new PaymentIsPaidConditionPlugin(), 'Payone/PaymentIsPaid');
- $conditionCollection->add(new PaymentIsUnderPaidConditionPlugin(), 'Payone/PaymentIsUnderPaid');
- $conditionCollection->add(new PaymentIsOverpaidConditionPlugin(), 'Payone/PaymentIsOverpaid');
- $conditionCollection->add(new PaymentIsRefundConditionPlugin(), 'Payone/PaymentIsRefund');
-
- return $conditionCollection;
- });
-
- $container->extend(static::COMMAND_PLUGINS, function (CommandCollectionInterface $commandCollection) {
- $commandCollection->add(new PreAuthorizeCommandPlugin(), 'Payone/PreAuthorize');
- $commandCollection->add(new AuthorizeCommandPlugin(), 'Payone/Authorize');
- $commandCollection->add(new CancelCommandPlugin(), 'Payone/Cancel');
- $commandCollection->add(new CaptureCommandPlugin(), 'Payone/Capture');
- $commandCollection->add(new CaptureWithSettlementCommandPlugin(), 'Payone/CaptureWithSettlement');
- $commandCollection->add(new RefundCommandPlugin(), 'Payone/Refund');
-
- return $commandCollection;
- });
-```
-
-In order to use the state machines provided by the Payone module, make sure to add the location path to configuration:
-
-```php
-<?php
-$config[OmsConstants::PROCESS_LOCATION] = [
- OmsConfig::DEFAULT_PROCESS_LOCATION,
- $config[KernelConstants::SPRYKER_ROOT] . '/payone/config/Zed/Oms'
-];
-```
-
-Add Payone controller provider to Yves bootstrap (this is required to provide endpoint URL for transaction status callbacks) in `src/Pyz/Yves/Application/YvesBootstrap.php`.
-```php
-<?php
-use Spryker\Yves\Payone\Plugin\Provider\PayoneControllerProvider;
- ...
- protected function registerControllerProviders()
- {
- ...
- $controllerProviders = [
- ...
- new PayoneControllerProvider($ssl),
- ];
-```
-
-Optionally configure security firewall for `/payone` route to accept `TransactionStatus` requests.
-Excerpt from PAYONE Platform Channel Server API document:
-
-According to the configuration of your payment portal you will receive the data and the status for each payment processed via the URL you have submitted. The data transfer is based on simple HTTP-POST request (key/value pairs). The `TransactionStatus` is sent from the following IP addresses: 185.60.20.0/24 (for example, 185.60.20.1 to 185.60.20.254). Please configure your firewall to allow incoming packets from these IP addresses.
-
-To provide payment details for rendering on frontend, add Payone client to the Checkout and to the Customer module:
-
-in `src/<project_name>/Yves/Checkout/CheckoutDependencyProvider.php`
-
-```php
-<?php
-...
-class CheckoutDependencyProvider extends SprykerCheckoutDependencyProvider
-{
- ...
- const CLIENT_PAYONE = 'CLIENT_PAYONE';
- ...
- protected function provideClients(Container $container)
- {
- ...
- $container[static::CLIENT_PAYONE] = function (Container $container) {
- return $container->getLocator()->payone()->client();
- };
- ...
- return $container;
- }
-```
-
-in `src//Yves/Customer/CustomerDependencyProvider.php`:
-
-```php
-<?php
-...
-class CheckoutDependencyProvider extends SprykerCheckoutDependencyProvider
-{
- ...
- const CLIENT_PAYONE = 'CLIENT_PAYONE';
- ...
- protected function provideClients(Container $container)
- {
- ...
- $container[static::CLIENT_PAYONE] = function (Container $container) {
- return $container->getLocator()->payone()->client();
- };
- ...
- return $container;
- }
- ```
-
-To add payment details on success step of checkout:
-
-Add quote and payment details to template variables in `src/<project_name>/Yves/Checkout/Process/Steps/SuccessStep.php`:
-
- ```php
- <?php
-...
-use Generated\Shared\Transfer\PayoneGetPaymentDetailTransfer;
-use Spryker\Client\Payone\PayoneClientInterface;
-use Spryker\Yves\Payone\Handler\PayoneHandler;
-...
-class SuccessStep extends AbstractBaseStep
-{
- ...
- /**
- * @var \Spryker\Client\Payone\PayoneClientInterface
- */
- protected $payoneClient;
-
- /**
- * @var \Generated\Shared\Transfer\QuoteTransfer
- */
- protected $quoteTransfer;
- ...
- public function __construct(CustomerClientInterface $customerClient, PayoneClientInterface $payoneClient, $stepRoute, $escapeRoute)
- {
- ...
- $this->payoneClient = $payoneClient;
- }
- ...
- public function execute(Request $request, AbstractTransfer $quoteTransfer)
- {
- $this->customerClient->markCustomerAsDirty();
-
- if (method_exists($quoteTransfer->getPayment(), 'getPayone')) {
- $this->quoteTransfer = $quoteTransfer;
- }
-
- return new QuoteTransfer();
- }
- ...
- /**
- * @param \Spryker\Shared\Kernel\AbstractTransfer $dataTransfer
- *
- * @return array
- */
- public function getTemplateVariables(AbstractTransfer $dataTransfer)
- {
- $getPaymentDetailTransfer = new PayoneGetPaymentDetailTransfer();
- if ($this->quoteTransfer->getPayment()->getPaymentProvider() === PayoneHandler::PAYMENT_PROVIDER) {
- $getPaymentDetailTransfer->setOrderReference($this->quoteTransfer->getOrderReference());
- $getPaymentDetailTransfer = $this->payoneClient->getPaymentDetail($getPaymentDetailTransfer);
- }
- return [
- 'quoteTransfer' => $this->quoteTransfer,
- 'paymentDetail' => $getPaymentDetailTransfer->getPaymentDetail(),
- ];
- }
-```
-
-Inject Payone client into the step factory `src/<project_name>/Yves/Checkout/Process/StepFactory.php`:
-
-```php
-<?php
-...
-protected function createSuccessStep()
-{
- return new SuccessStep(
- $this->getProvidedDependency(CheckoutDependencyProvider::CLIENT_CUSTOMER),
- $this->getProvidedDependency(CheckoutDependencyProvider::CLIENT_PAYONE),
- CheckoutControllerProvider::CHECKOUT_SUCCESS,
- ApplicationControllerProvider::ROUTE_HOME
- );
-}
-```
-
-To add payment details on order details page in customer cabinet:
-
-Add method that will create the Payone client into the CustomerFactory `src/<project_name>/Yves/Customer/CustomerFactory.php`:
-
-```php
-<?php
-...
-class CustomerFactory extends AbstractFactory
-{
- ...
- /**
- * @return \Spryker\Client\Payone\PayoneClientInterface
- */
- public function createPayoneClient()
- {
- return $this->getProvidedDependency(CustomerDependencyProvider::CLIENT_PAYONE);
- }
-```
-
-Add payment details to template variables inside the OrderController in `src/<project_name>/Yves/Customer/Controller/OrderController.php`:
-
-```php
-<?php
-...
-use Generated\Shared\Transfer\PayoneGetPaymentDetailTransfer;
-...
-class OrderController extends AbstractCustomerController
-{
- ...
- protected function getOrderDetailsResponseData($idSalesOrder)
- {
- ...
- $getPaymentDetailTransfer = new PayoneGetPaymentDetailTransfer();
- $getPaymentDetailTransfer->setOrderId($idSalesOrder);
- $getPaymentDetailTransfer = $this->getFactory()
- ->getPayoneClient()->getPaymentDetail($getPaymentDetailTransfer);
-
- return [
- 'order' => $orderTransfer,
- 'paymentDetail' => $getPaymentDetailTransfer->getPaymentDetail(),
- ];
- }
-```
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
-
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-authorization-and-preauthorization-capture-flows.md b/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-authorization-and-preauthorization-capture-flows.md
deleted file mode 100644
index 501f24331bb..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-authorization-and-preauthorization-capture-flows.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: PayOne - Authorization and Preauthorization Capture Flows
-description: Payone module makes it possible for a project to choose which Payone flow it wants to implement- authorize or preauthorize + capture.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/payone-authorization-and-preauthorization-capture-flows
-originalArticleId: f890f6c2-8597-4b66-8df4-6f1de2776447
-redirect_from:
-  - /2021080/docs/payone-authorization-and-preauthorization-capture-flows
-  - /2021080/docs/en/payone-authorization-and-preauthorization-capture-flows
-  - /docs/payone-authorization-and-preauthorization-capture-flows
-  - /docs/en/payone-authorization-and-preauthorization-capture-flows
-related:
-  - title: PayOne - Prepayment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-prepayment.html
-  - title: PayOne - Invoice Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-invoice-payment.html
-  - title: PayOne - Cash on Delivery
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/scos-integration/payone-cash-on-delivery.html
-  - title: PayOne - Credit Card Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-credit-card-payment.html
-  - title: PayOne - Security Invoice Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-security-invoice-payment.html
-  - title: PayOne - Direct Debit Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-direct-debit-payment.html
----
-
-Payone module makes it possible for a project to choose which Payone flow it wants to implement: authorize or preauthorize + capture.
-
-## Authorization Example State Machine:
-
-![Click Me](https://spryker.s3.eu-central-1.amazonaws.com/docs/Technology+Partners/Payment+Partners/BS+Payone/payone-authorization-flow-example.png)
-
-Authorization state machine example xml can be found in `vendor/<payone_module_folder>/src/config/Zed/Oms/PayoneInvoice.xml`
-
-### Commands and Conditions Used in Authorization Flow:
-
- Commands:
-  - `src/SprykerEco/Zed/Payone/Communication/Plugin/Oms/Command/AuthorizeCommandPlugin.php`
-
-Conditions:
-  - `vendor/<payone_module_folder>/src/SprykerEco/Zed/Payone/Communication/Plugin/Oms/Condition/AuthorizationIsApprovedConditionPlugin.php`
-  - `vendor/<payone_module_folder>/src/SprykerEco/Zed/Payone/Communication/Plugin/Oms/Condition/AuthorizationIsErrorConditionPlugin.php`
-  - `vendor/<payone_module_folder>/src/SprykerEco/Zed/Payone/Communication/Plugin/Oms/Condition/AuthorizationIsRedirectConditionPlugin.php`
-
-## Preauthorization-Capture Example State Machine:
-![Click Me](https://spryker.s3.eu-central-1.amazonaws.com/docs/Technology+Partners/Payment+Partners/BS+Payone/payone-preauthorization-capture-flow-example.png)
-
-Preauthorization-capture state machine example XML can be found in `vendor/<payone_module_folder>/config/Zed/Oms/DirectDebit.xml`
-
-### Commands and Conditions Used in Preauthorization-Capture Flow:
-
-Commands:
-  * `vendor/<payone_module_folder>/src/SprykerEco/Zed/Payone/Communication/Plugin/Oms/Command/PreAuthorizeCommandPlugin.php`
-  * `vendor/<payone_module_folder>/src/SprykerEco/Zed/Payone/Communication/Plugin/Oms/Command/CaptureCommandPlugin.php`
-  * `vendor/<payone_module_folder>/src/SprykerEco/Zed/Payone/Communication/Plugin/Oms/Command/PreAuthorizaWithSettlementCommandPlugin.php`
-
-Conditions:
-  * `vendor/<payone_module_folder>/src/SprykerEco/Zed/Payone/Communication/Plugin/Oms/Condition/PreAuthorizationIsApprovedConditionPlugin.php`
-  * `vendor/<payone_module_folder>/src/SprykerEco/Zed/Payone/Communication/Plugin/Oms/Condition/PreAuthorizationIsErrorConditionPlugin.php`
-  * `vendor/<payone_module_folder>/src/SprykerEco/Zed/Payone/Communication/Plugin/Oms/Condition/PreAuthorizationIsRedirectConditionPlugin.php`
-  * `vendor/<payone_module_folder>/src/SprykerEco/Zed/Payone/Communication/Plugin/Oms/Condition/CaptureIsApprovedConditionPlugin.php`
-  * `vendor/<payone_module_folder>/src/SprykerEco/Zed/Payone/Communication/Plugin/Oms/Condition/CaptureIsErrorConditionPlugin.php`
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-facade.md b/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-facade.md
deleted file mode 100644
index 43a63e884cc..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-facade.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: PayOne - Facade
-description: This article includes facade methods provided by PayOne.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/payone-facade
-originalArticleId: 51e2f043-2b63-4984-9b06-06f312882fb3
-redirect_from:
-  - /2021080/docs/payone-facade
-  - /2021080/docs/en/payone-facade
-  - /docs/payone-facade
-  - /docs/en/payone-facade
----
-
-|FACEDE METHOD |PARAMETER | RETURN |DESCRIPTION |
-| --- | --- | --- | --- |
-| `saveOrder` (deprecated) | `QuoteTransfer`, `CheckoutResponseTransfer` | void | Saves the PayOne payment method data according to quote and checkout response transfer data. |
-| `saveOrderPayment` | `QuoteTransfer`, `SaveOrderTransfer` | void | Saves the order payment method data according to quote and order data. |
-| `authorizePayment` | `OrderTransfer` | `AuthorizationResponseContainer` | Performs the payment authorization request to PayOne API. |
-| `preAuthorizePayment` | Order ID | `AuthorizationResponseContainer` | Performs payment the pre-authorization request to PayOne API. |
-| `capturePayment` | `PayOneCaptureTransfer` | `CaptureResponseContainer` | Performs payment capture request to PayOne API. |
-| `debitPayment` | Order ID | `DebitResponseContainer` | Performs the debit payment request to PayOne API. |
-| `refundPayment` | `PayOneRefundTransfer` | `RefundResponseContainer` | Performs the refund payment request to PayOne API. |
-| `creditCardCheck` | `PayOneCreditCardTransfer` | `CreditCardCheckResponseContainer` | Performs the creditcardcheck request to PayOne API (card number validation, expiration date check, etc). |
-| `bankAccountCheck` | `PayOneBankAccountCheckTransfer` | `BankAccountCheckResponseContainer` | Performs the bankaccountcheck request to PayOne API. |
-| `manageMandate` | `PayOneManageMandateTransfer` | `ManageMandateResponseContainer` | Performs the managemandate request to PayOne API (used to create SEPA mandate for Direct Debit payment). |
-| `getFile` | `PayOneGetFileTransfer` | `GetFileResponseContainer` | Performs the getfile request to PayOne API (to download an existing SEPA mandate in PDF format). |
-| `getInvoice` | `PayOneGetInvoiceTransfer` | `GetInvoiceResponseContainer` | Performs the getinvoice request to PayOne API (to download invoice in PDF format). |
-| `processTransactionStatusUpdate` | `PayOneTransactionStatusUpdateTransfer` | `TransactionStatusResponse` | Saves transaction status update received from PayOne. |
-| `isAuthorizationApproved` | `OrderTransfer` | bool | Checks if the authorization request to PayOne API received the "Approved" status in response. |
-| `isAuthorizationRedirect` | `OrderTransfer` | bool | Checks if the authorization request to PayOne API received "Redirect" status in response. |
-| `isAuthorizationError` | `OrderTransfer` | bool | Checks if the authorization request to PayOne API received the "Error" status in response. |
-| `isPreauthorizationApproved` | `OrderTransfer` | bool | Checks if the pre-authorization request to PayOne API received the "Approved" status in response. |
-| `isPreauthorizationRedirect` | `OrderTransfer` | bool | Checks if the pre-authorization request to PayOne API received "Redirect" status in response. |
-| `isPreAuthorizationError` | `OrderTransfer` | bool | Checks if pre-authorization request to PayOne API received the "Error" status in response. |
-| `isCaptureApproved` | `OrderTransfer` | bool | Checks if capture request to PayOne API received the "Approved" status in response. |
-| `isCaptureError` | `OrderTransfer` | bool | Checks if capture request to PayOne API received the "Error" status in response. |
-| `isRefundApproved` | `OrderTransfer` | bool | Checks if refund request to PayOne API received the "Approved" status in response. |
-| `isRefundError` | `OrderTransfer` | bool | Checks if refund request to PayOne API received the "Error" status in response. |
-| `isRefundPossible` | `OrderTransfer` | bool | Checks if payment process for certain order supports refund. |
-| `isPaymentDataRequired` | `OrderTransfer` | bool | Checks if payment process for certain order requires bank account details. |
-| `isPaymentNotificationAvailable` | Order ID, Order Item ID | bool | Checks if there are unprocessed transaction status updates from PayOne for a certain order. |
-| `isPaymentPaid` | Order ID, Order Item ID | bool | Checks if there is an unprocessed transaction status update from PayOne with the "Paid" status and balance is zero or negative for a certain order. |
-| `isPaymentOverpaid` | Order ID, Order Item ID | bool | Checks if there is an unprocessed transaction status update from PayOne with the "Paid" status, and the balance is negative for a certain order. |
-| `isPaymentUnderpaid` | Order ID, Order Item ID | bool | Checks if there is an unprocessed transaction status update from PayOne with the "Underpaid" status for a certain order. |
-| `isPaymentRefund` | Order ID, Order Item ID | bool | Checks if there is an unprocessed transaction status update from PayOne with the "Refund" status for a certain order. |
-| `isPaymentAppointed` | Order ID, Order Item ID | bool | Checks if there is an unprocessed transaction status update from PayOne with the "Appointed" status for a certain order. |
-| `isPaymentOther` | Order ID, Order Item ID | bool | Checks if there is an unprocessed transaction status update from PayOne with the status different from "Paid", "Underpaid" or "Appointed" for a certain order. |
-| `isPaymentCapture` | Order ID, Order Item ID | bool | Checks if there is an unprocessed transaction status update from PayOne with the "Capture" status for a certain order. |
-| `postSaveHook` (deprecated) | `QuoteTransfer`, `CheckoutResponseTransfer` | `CheckoutResponseTransfer` | Handles redirects and errors after an order is placed. |
-| `orderPostSave` | `QuoteTransfer`, `CheckoutResponseTransfer` | `CheckoutResponseTransfer` | Handles redirects and errors after an order has been placed. Depending on the payment method, executes the authorization or pre-authorization API call. Updates `CheckoutResponseTransfer` with errors and redirects URL according to the API response. |
-| `getPaymentLogs` | `ObjectCollection` | array of `PayOnePaymentLogTransfer` | Gets payment logs (both API and transaction status) for specific orders in chronological order. |
-| `getPaymentDetail` | Order ID | `PaymentDetailTransfer` | Gets payment details for a specific order. |
-| `updatePaymentDetail` | `PaymentDetailTransfer`, Order ID | void | Updates payment details for a specific order. |
-| install | `MessengerInterface` | void | Installs module translations to project glossary. |
-| `startPayPalExpressCheckout` | `PayOneStartPayPalExpressCheckoutRequestTransfer` | `PayOnePayPalExpressCheckoutGenericPaymentResponseTransfer` | Sends request to PayOne to start express checkout and get the work order ID which is used for further operations. |
-| `getPayPalExpressCheckoutDetails` | `QuoteTransfer` | `PayOnePayPalExpressCheckoutGenericPaymentResponseTransfer` | Returns customer specific information retrieved from PayPal through PayOne (for example, email and shipping info). |
-| `executeCheckoutPostSaveHook` (deprecated) | `QuoteTransfer` `CheckoutResponseTransfer` | `CheckoutResponseTransfer` | Depending on the payment method, executes the authorization or pre-authorization API call. Updates `CheckoutResponseTransfer` with errors and redirects URL according to the API response. |
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-integration-into-the-legacy-demoshop-project.md b/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-integration-into-the-legacy-demoshop-project.md
deleted file mode 100644
index 94d5ea32382..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-integration-into-the-legacy-demoshop-project.md
+++ /dev/null
@@ -1,373 +0,0 @@
----
-title: PayOne - Integration into the Legacy Demoshop Project
-description: Integrate Payone into the Spryker Legacy Demoshop by following the instructions from this article.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/payone-integration-with-project-example
-originalArticleId: 33e511b2-b8d3-489c-bf70-2581e86105a5
-redirect_from:
-  - /2021080/docs/payone-integration-with-project-example
-  - /2021080/docs/en/payone-integration-with-project-example
-  - /docs/payone-integration-with-project-example
-  - /docs/en/payone-integration-with-project-example
----
-
-{% info_block errorBox %}
-
-There is currently an issue when using gifcards with PayOne. Our team is developing a fix for it.
-
-{% endinfo_block %}
-
-**Objectives:**
-* Place order with PayPal express checkout.
-* Be redirected to summary page of standard checkout.
-* Have shipping a method selector on summary page.
-
-First of all we need to provide a URL to Payone module, which will be used to redirect user when the quote is filled with data obtained from PayPal.
- To achieve this, make the following steps:
-
-1. Add custom controller action to `src/Pyz/Yves/Checkout/Controller/CheckoutController.php`:
-
-```php
-/**
-* @return \Symfony\Component\HttpFoundation\RedirectResponse
-*/
-public function paypalExpressCheckoutEntryPointAction()
-{
-$this->getFactory()
-->createExpressCheckoutHandler()
-->fulfillPostConditionsUntilSummaryStep();
-return $this->redirectResponseInternal(CheckoutControllerProvider::CHECKOUT_SUMMARY);
-}
-```
-
-2. Register a new controller action in controller provider:
-
-```php
-...
-const CHECKOUT_PAYPAL_EXPRESS_CHECKOUT_ENTRY_POINT = 'checkout-paypal-express-checkout-entry-point';
-...
-protected function defineControllers(Application $app)
-{
-...
-$this->createController('/{checkout}/paypal-express-checkout-entry-point', self::CHECKOUT_PAYPAL_EXPRESS_CHECKOUT_ENTRY_POINT, 'Checkout', 'Checkout', 'paypalExpressCheckoutEntryPoint')
-->assert('checkout', $allowedLocalesPattern . 'checkout|checkout')
-->value('checkout', 'checkout')
-->method('GET');
-...
-}
-```
-
-3. Create `ExpressCheckoutHandler` class `src/Pyz/Yves/Checkout/Handler/ExpressCheckoutHandler.php` with corresponding interface:
-
-```php
-namespace Pyz\Yves\Checkout\Handler;
-use Generated\Shared\Transfer\ExpenseTransfer;
-use Spryker\Client\Cart\CartClientInterface;
-use Spryker\Shared\Shipment\ShipmentConstants;
-class ExpressCheckoutHandler implements ExpressCheckoutHandlerInterface
-{
-/**
-* @var \Spryker\Client\Cart\CartClientInterface
-*/
-protected $cartClient;
-/**
-* @param \Spryker\Client\Cart\CartClientInterface $cartClient
-*/
-public function __construct(CartClientInterface $cartClient)
-{
-$this->cartClient = $cartClient;
-}
-/**
-* @return void
-*/
-public function fulfillPostConditionsUntilSummaryStep()
-{
-$quoteTransfer = $this->cartClient->getQuote();
-$quoteTransfer->addExpense(
-(new ExpenseTransfer())->setType(ShipmentConstants::SHIPMENT_EXPENSE_TYPE)
-);
-}
-}
-```
-
-4. Add `ExpressCheckoutHandler` related method in `src/Pyz/Yves/Checkout/CheckoutFactory.php`:
-
-```php
-/**
-* @return \Pyz\Yves\Checkout\Handler\ExpressCheckoutHandler
-*/
-public function createExpressCheckoutHandler()
-{
-return new ExpressCheckoutHandler(
-$this->getCartClient()
-);
-}
-```
-
-5. Extend `ShipmentForm` class to override a property_path option (create `src/Pyz/Yves/Shipment/Form/ShipmentSubForm.php`):
-
-```php
-namespace Pyz\Yves\Shipment\Form;
-class ShipmentSubForm extends ShipmentForm
-{
-/**
-* @const string
-*/
-const SHIPMENT_SELECTION_PROPERTY_PATH = self::SHIPMENT_SELECTION;
-}
-```
-
-6. Adjust summary form by adding a shipment subform in `src/Pyz/Yves/Checkout/Form/Steps/SummaryForm.php`:
-
-```php
-class SummaryForm extends AbstractType
-{
-/**
-* Builds the form.
-*
-* This method is called for each type in the hierarchy starting from the
-* top most type. Type extensions can further modify the form.
-*
-* @see FormTypeExtensionInterface::buildForm()
-*
-* @param \Symfony\Component\Form\FormBuilderInterface $builder The form builder
-* @param array $options The options
-*
-* @return void
-*/
-public function buildForm(FormBuilderInterface $builder, array $options)
-{
-$builder->add(
-'shipmentForm',
-ShipmentSubForm::class,
-array_merge(
-$options,
-[
-'data_class' => ShipmentTransfer::class,
-'property_path' => 'shipment',
-]
-)
-);
-}
-/**
-* @param \Symfony\Component\OptionsResolver\OptionsResolver $resolver
-*
-* @return void
-*/
-public function configureOptions(OptionsResolver $resolver)
-{
-$resolver->setRequired('shipmentMethods');
-$resolver->setDefaults([
-'data_class' => QuoteTransfer::class,
-]);
-}
-/**
-* Returns the name of this type.
-*
-* @return string The name of this type
-*/
-public function getName()
-{
-return 'summaryForm';
-}
-}
-```
-
-7. Create shipment subform template for summary page in `src/Pyz/Yves/Checkout/Theme/default/checkout/partials/shipment.twig`:
-
-```php
-
-<div class="row columns">
-
- {% raw %}{%{% endraw %} set shipmentForm = summaryForm.shipmentForm {% raw %}%}{% endraw %}
-
- <div class="callout">
-  <ul class="no-bullet">
-
-   {% raw %}{%{% endraw %} for name, choices in shipmentForm.idShipmentMethod.vars.choices {% raw %}%}{% endraw %}
-
-   <h4>{% raw %}{{{% endraw %} name {% raw %}}}{% endraw %}</h4>
-
-   {% raw %}{%{% endraw %} for key, choice in choices {% raw %}%}{% endraw %}
-   <li>
-    <label>
-     {% raw %}{{{% endraw %} form_widget(shipmentForm.idShipmentMethod[key], {'attr': {'class': '__toggler'{% raw %}}}{% endraw %}) {% raw %}}}{% endraw %}
-     {% raw %}{{{% endraw %} shipmentForm.idShipmentMethod[key].vars.label | raw {% raw %}}}{% endraw %}
-    </label>
-   </li>
-   {% raw %}{%{% endraw %} endfor {% raw %}%}{% endraw %}
-   {% raw %}{%{% endraw %} endfor {% raw %}%}{% endraw %}
-  </ul>
- </div>
-</div>
-```
-
-8. Update summary twig template in `src/Pyz/Yves/Checkout/Theme/default/checkout/summary.twig`.
-Move `form_start` expression to the top of a content section and `form_end` to the end:
-
-```php
-...
-{% raw %}{%{% endraw %} block content {% raw %}%}{% endraw %}
-{% raw %}{{{% endraw %} form_start(summaryForm, {'attr': {'class': 'row'{% raw %}}}{% endraw %}) {% raw %}}}{% endraw %}
-...
-...
-...
-{% raw %}{{{% endraw %} form_end(summaryForm) {% raw %}}}{% endraw %}
-{% raw %}{%{% endraw %} endblock {% raw %}%}{% endraw %}
-```
-
-9. Remove `{% raw %}{%{% endraw %} include '@checkout/checkout/partials/voucher-form.twig' {% raw %}%}{% endraw %}` include from summary template. Include `checkout/partials/shipment.twig` in your summary template:
-
-```php
-      ...
-{% raw %}{{{% endraw %} 'checkout.step.summary.shipping' | trans {% raw %}}}{% endraw %}
-      {% raw %}{%{% endraw %} include '@checkout/checkout/partials/shipment.twig' {% raw %}%}{% endraw %}
-      ...
-```
-10. Add shipment form data provider and remove voucher form from summary form collection (it is just an example, if you need voucher form, you need to adjust summary page on your own). In `src/Pyz/Yves/Checkout/Form/FormFactory.php`:
-
-```php
-/**
-* @param \Generated\Shared\Transfer\QuoteTransfer
-*
-* @return \Spryker\Yves\StepEngine\Form\FormCollectionHandlerInterface
-*/
-public function createSummaryFormCollection()
-{
-return $this->createFormCollection($this->createSummaryFormTypes(), $this->getShipmentFormDataProviderPlugin());
-}
-
-....
-
-
-/**
-* @return \Symfony\Component\Form\FormTypeInterface[]
-*/
-protected function createSummaryFormTypes()
-{
-return [
-$this->createSummaryForm(),
-//$this->createVoucherFormType(),
-];
-}
-```
-11. Handle shipment form data, when summary form is submitted. Inject two dependencies into `src/Pyz/Yves/Checkout/Process/Steps/SummaryStep.php`:
-
-```php
-/**
-* @var \Spryker\Client\Calculation\CalculationClientInterface
-*/
-protected $calculationClient;
-/**
-* @var \Spryker\Yves\StepEngine\Dependency\Plugin\Handler\StepHandlerPluginCollection
-*/
-protected $shipmentPlugins;
-/**
-* @param \Spryker\Yves\ProductBundle\Grouper\ProductBundleGrouperInterface $productBundleGrouper
-* @param \Spryker\Client\Cart\CartClientInterface $cartClient
-* @param \Spryker\Client\Calculation\CalculationClientInterface $calculationClient
-* @param \Spryker\Client\Calculation\CalculationClientInterface $shipmentPlugins
-* @param string $stepRoute
-* @param string $escapeRoute
-*/
-public function __construct(
-ProductBundleGrouperInterface $productBundleGrouper,
-CartClientInterface $cartClient,
-CalculationClientInterface $calculationClient,
-StepHandlerPluginCollection $shipmentPlugins,
-$stepRoute,
-$escapeRoute
-) {
-parent::__construct($stepRoute, $escapeRoute);
-$this->productBundleGrouper = $productBundleGrouper;
-$this->cartClient = $cartClient;
-$this->calculationClient = $calculationClient;
-$this->shipmentPlugins = $shipmentPlugins;
-}
-```
-
-12. Extend `execute` method:
-
-```php
-/**
-* @param \Symfony\Component\HttpFoundation\Request $request
-* @param \Spryker\Shared\Kernel\Transfer\AbstractTransfer|\Generated\Shared\Transfer\QuoteTransfer $quoteTransfer
-*
-* @return \Generated\Shared\Transfer\QuoteTransfer
-*/
-public function execute(Request $request, AbstractTransfer $quoteTransfer)
-{
-$shipmentHandler = $this->shipmentPlugins->get(CheckoutDependencyProvider::PLUGIN_SHIPMENT_STEP_HANDLER);
-$shipmentHandler->addToDataClass($request, $quoteTransfer);
-$this->calculationClient->recalculate($quoteTransfer);
-$this->markCheckoutConfirmed($request, $quoteTransfer);
-return $quoteTransfer;
-}
-```
-
-13. Add Payone checkout plugins in `Pyz\Zed\Checkout\CheckoutDependencyProvider`:
-
-```php
-<?php
-
-/**
- * This file is part of the Spryker Suite.
- * For full license information, please view the LICENSE file that was distributed with this source code.
- */
-
-namespace Pyz\Zed\Checkout;
-
-//...
-use SprykerEco\Zed\Payone\Communication\Plugin\Checkout\PayoneCheckoutDoSaveOrderPlugin;
-use SprykerEco\Zed\Payone\Communication\Plugin\Checkout\PayoneCheckoutPostSavePlugin;
-use SprykerEco\Zed\Payone\Communication\Plugin\Checkout\PayoneCheckoutPreConditionPlugin;
-
-class CheckoutDependencyProvider extends SprykerCheckoutDependencyProvider
-{
-    /**
-     * @param \Spryker\Zed\Kernel\Container $container
-     *
-     * @return \Spryker\Zed\CheckoutExtension\Dependency\Plugin\CheckoutPreConditionPluginInterface[]
-     */
-    protected function getCheckoutPreConditions(Container $container)
-    {
-        return [
-            //...
-            new PayoneCheckoutPreConditionPlugin(),
-            //...
-        ];
-    }
-
-    /**
-     * @param \Spryker\Zed\Kernel\Container $container
-     *
-     * @return \Spryker\Zed\Checkout\Dependency\Plugin\CheckoutSaveOrderInterface[]|\Spryker\Zed\CheckoutExtension\Dependency\Plugin\CheckoutDoSaveOrderInterface[]
-     */
-    protected function getCheckoutOrderSavers(Container $container)
-    {
-        return [
-            //...
-            new PayoneCheckoutDoSaveOrderPlugin(),
-            //...
-        ];
-    }
-
-    /**
-     * @param \Spryker\Zed\Kernel\Container $container
-     *
-     * @return \Spryker\Zed\CheckoutExtension\Dependency\Plugin\CheckoutPostSaveInterface[]
-     */
-    protected function getCheckoutPostHooks(Container $container)
-    {
-        return [
-            //...
-            new PayoneCheckoutPostSavePlugin(),
-            //...
-        ];
-    }
-    //...
-}
-```
-
-Now, go to checkout and try placing an order with Paypal express checkout.
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-credit-card-payment.md b/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-credit-card-payment.md
deleted file mode 100644
index 2d1db3d2523..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-credit-card-payment.md
+++ /dev/null
@@ -1,86 +0,0 @@
----
-title: PayOne - Credit Card Payment
-description: Integrate Credit Card payment through Payone into the Spryker-based shop.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/payone-credit-card
-originalArticleId: b0238458-4982-4762-99e5-6140eee627aa
-redirect_from:
-  - /2021080/docs/payone-credit-card
-  - /2021080/docs/en/payone-credit-card
-  - /docs/payone-credit-card
-  - /docs/en/payone-credit-card
-related:
-  - title: PayOne - Prepayment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-prepayment.html
-  - title: PayOne - Authorization and Preauthorization Capture Flows
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-authorization-and-preauthorization-capture-flows.html
-  - title: PayOne - Invoice Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-invoice-payment.html
-  - title: PayOne - Cash on Delivery
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/scos-integration/payone-cash-on-delivery.html
-  - title: PayOne - Security Invoice Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-security-invoice-payment.html
-  - title: PayOne - Direct Debit Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-direct-debit-payment.html
----
-
-{% info_block infoBox "PCI Compliance" %}
-
-Because of PCI compliance reasons, credit card data is communicated to the third party through AJAX calls (sensitive information stays at the browser side).
-
-{% endinfo_block %}
-
-## PCI Compliance
-
-The Payment Card Industry Data Security Standard ( PCI DSS ) is a set of rules with the intention to ensure that credit card information is processed, stored and transmitted in a secure environment.
-
-The PCI standard applies to companies or organizations that enable making payments using credit cards.
-
-The PCI compliance standard means that any merchant that offers credit card payments or is storing credit card information in the system is mandatory to pass a PCI certification. Processing and storing credit card data in the database involves a serious risk of financial fraud.
-
-In order to meet the requirements of PCI DSS compliance (Compliance) for card payments, this module provides a Hosted iFrame solution. This solution enables you not only to integrate all relevant fields for card data in your checkout process, but also to be fully compliant  with PCI DSS standards. Using this solution qualifies for providing proof of PCI DSS Compliance via SAQ A (Self Assessment Questionnaire A) questionnaire. Please find more information [here](https://pci.payone.de/content/faq).
-
-## Front-end Integration
-
-Run `antelope build yves` after you include the javascript file for credit card check inside the payment step template (e.g. `src/<project_name>/Yves/Checkout/Theme/<custom_theme_name>/checkout/payment.twig`)
-
-```php
-{% raw %}{%{% endraw %} block content {% raw %}%}{% endraw %}
- <script src="/assets/default/js/spryker-yves-payone-main.js"></script>
-{% raw %}{%{% endraw %} endblock {% raw %}%}{% endraw %}
-```
-To adjust frontend appearance, provide following templates in your theme directory:
-
-* `src/<project_name>/Yves/Payone/Theme/<custom_theme_name>/credit_card.twig`
-
-## State Machine Integration
-
-The Payone module provides a demo state machine for Credit Card payment method which implements Pre-Authorization/Capture flow. It's also possible to implement Authorization flow using corresponding command.
-
-To enable the demo state machine, extend the configuration with the following values:
-
-```php
-<?php
-$config[SalesConstants::PAYMENT_METHOD_STATEMACHINE_MAPPING] = [
- ...
- PayoneConfig::PAYMENT_METHOD_CREDIT_CARD => 'PayoneCreditCard',
-];
-
-$config[OmsConstants::ACTIVE_PROCESSES] = [
- ...
- 'PayoneCreditCard',
-];
-```
-
-## Credit Card Payment Flow:
-
-1. A credit card check request is submitted to Payone ( through an AJAX call) The request sent to Payone is encrypted and it contains a secret key configured in the merchant account. The response contains a pseudo credit card pan: a token used to uniquely identify this transaction on third party side, on further communications. The pseudo credit card pan is stored in the database.
-2. A checkout request is made to Spryker; depending if it's a 3d secure credit card or a regular credit card, Spryker will manage to submit the payment on third party side and update the payment status. On authorizing or capturing requests, Spryker will use the pseudo credit card pan stored in the database as an identification token.
-
-## System Interaction
-
-The diagram shows the interaction between the browser, Zed and Payone. We recommend using the creditcardcheck (1) AJAX call from the browser to Payone directly. If the credit card data is valid, Payone will return a credit card pseudo pan. This number must be used with all subsequent Payone interactions as a reference. Optionally the pseudo pan can be stored with an AJAX request into the session (2). When it comes to checkout (3) a state machine must be started. The state machine can either use an authorize call to obtain the money directly or use a preauthorize call (3.1) that blocks the money. If 3d-secure is enabled a redirect message must be handled. At the given time (when package is ready for shipment e.g.) the preauthorized money can be captured.
-![Click Me](https://spryker.s3.eu-central-1.amazonaws.com/docs/Technology+Partners/Payment+Partners/BS+Payone/payone-system-interaction.png)
-
-Credit card Check is an AJAX request from the browser to Payone directly. Before sending the credit card data, it is encrypted with asymmetric encryption algorithm. If the credit card is valid, a Pseudocreditcardpan is returned. This will be used for all subsequent interactions with Payone. The advantage is that a PCI compliance may not be needed.
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-direct-debit-payment.md b/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-direct-debit-payment.md
deleted file mode 100644
index d55cb0750f4..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-direct-debit-payment.md
+++ /dev/null
@@ -1,86 +0,0 @@
----
-title: PayOne - Direct Debit Payment
-description: Integrate Direct Debit payment through Payone into the Spryker-based shop.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/payone-direct-debit
-originalArticleId: b5ee3770-00da-4907-bf81-36c5e9125ab6
-redirect_from:
-  - /2021080/docs/payone-direct-debit
-  - /2021080/docs/en/payone-direct-debit
-  - /docs/payone-direct-debit
-  - /docs/en/payone-direct-debit
-related:
-  - title: PayOne - Prepayment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-prepayment.html
-  - title: PayOne - Authorization and Preauthorization Capture Flows
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-authorization-and-preauthorization-capture-flows.html
-  - title: PayOne - Invoice Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-invoice-payment.html
-  - title: PayOne - Cash on Delivery
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/scos-integration/payone-cash-on-delivery.html
-  - title: PayOne - Security Invoice Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-security-invoice-payment.html
-  - title: PayOne - Online Transfer Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-online-transfer-payment.html
----
-
-## Front-End Integration
-
-Run the `antelope build yves` after you include the javascript file for credit card check inside the payment step template (e.g. `src/<project_name>/Yves/Checkout/Theme/<custom_theme_name>/checkout/payment.twig`)
-
-```php
-{% raw %}{%{% endraw %} block content {% raw %}%}{% endraw %}
-<script src="/assets/default/js/spryker-yves-payone-main.js"></script>
-{% raw %}{%{% endraw %} endblock {% raw %}%}{% endraw %}```
-
-In order to display SEPA mandate text and references, apply next modifications to project templates:
-
-To display SEPA mandate text on summary page of checkout, add the following reference into `src/<project_name>/Yves/Checkout/Theme/<custom_theme_name>/checkout/summary.twig`
-```php
-{% raw %}{%{% endraw %} include '@payone/checkout/partials/summary-payment-details.twig' {% raw %}%}{% endraw %}
-```
-
-To display a link to the SEPA mandate in PDF format on checkout success page, add the following reference into `src/<project_name>/Yves/Checkout/Theme/<custom_theme_name>/checkout/success.twig`
-
-```php
-{% raw %}{%{% endraw %} include '@payone/checkout/partials/success-payment-details.twig' {% raw %}%}{% endraw %}
-```
-
-To display link to SEPA mandate in PDF format on order details page in customer cabinet, add the following reference into `src/<project_name>/Yves/Customer/Theme/<custom_theme_name>/order/details.twig`
-
-```php
-{% raw %}{%{% endraw %} include '@payone/order/partials/details-payment-data.twig' {% raw %}%}{% endraw %}
-```
-
-To adjust frontend appearance, provide following templates in your theme directory:
-* `src/<project_name>/Yves/Payone/Theme/<custom_theme_name>/direct_debit.twig`
-* `src/<project_name>/Yves/Payone/Theme/<custom_theme_name>/index/get-file.twig`
-* `src/<project_name>/Yves/Payone/Theme/<custom_theme_name>/checkout/partials/summary-payment-details.twig`
-* `src/<project_name>/Yves/Payone/Theme/<custom_theme_name>/checkout/partials/success-payment-details.twig`
-* `src/<project_name>/Yves/Payone/Theme/<custom_theme_name>/order/partials/details-payment-data.twig`
-
-## State Machine Integration
-
-The Payone module provides demo state machine for Direct Debit payment method which implements Pre-Authorization/Capture flow. It's also possible to implement Authorization flow using corresponding command.
-
-To enable the demo state machine, extend the configuration with following values:
-
-```php
-<?php
-$config[SalesConstants::PAYMENT_METHOD_STATEMACHINE_MAPPING] = [
- ...
- PayoneConfig::PAYMENT_METHOD_DIRECT_DEBIT => 'PayoneDirectDebit',
-];
-
-$config[OmsConstants::ACTIVE_PROCESSES] = [
- ...
- 'PayoneDirectDebit',
-];
-```
-
-## Direct Debit Payment Flow:
-
-1. When customer enters the payment details on checkout, a manage mandate request is submitted to Payone, which serves for automatic bank account data translation into IBAN/BIC pair(only for DE), IBAN/BIC validation and for SEPA mandate management (either an existing one will be used or a new one will be created).
-2. If a new mandate was created, the customer is presented with a SEPA mandate text on checkout summary step. User agrees with SEPA mandate terms by placing an order. There's no agreement text displayed if existing SEPA mandate was found and was recognized by Payone.
-3. On order placement, authorize (or preauthorize) command confirms user agreement with SEPA mandate terms. The customer is presented with a link to mandate in PDF format on successful order placement. Same link is available inside the order details page in customer cabinet.
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-invoice-payment.md b/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-invoice-payment.md
deleted file mode 100644
index 622fe20bb79..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-invoice-payment.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: PayOne - Invoice Payment
-description: Integrate invoice payment through Payone into the Spryker-based shop.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/payone-invoice
-originalArticleId: cb82c153-b340-427c-8114-3656c07a2d47
-redirect_from:
-  - /2021080/docs/payone-invoice
-  - /2021080/docs/en/payone-invoice
-  - /docs/payone-invoice
-  - /docs/en/payone-invoice
-related:
-  - title: PayOne - Prepayment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-prepayment.html
-  - title: PayOne - Authorization and Preauthorization Capture Flows
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-authorization-and-preauthorization-capture-flows.html
-  - title: PayOne - Cash on Delivery
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/scos-integration/payone-cash-on-delivery.html
-  - title: PayOne - Direct Debit Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-direct-debit-payment.html
-  - title: PayOne - Security Invoice Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-security-invoice-payment.html
-  - title: PayOne - Online Transfer Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-online-transfer-payment.html
----
-
-## Front-end Integration
-
-To adjust the frontend appearance, provide the following templates in your theme directory:
-`src/<project_name>/Yves/Payone/Theme/<custom_theme_name>/invoice.twig`
-
-## State Machine Integration
-
-Payone module provides a demo state machine for the Invoice payment method which implements Authorization flow.
-
-To enable the demo state machine, extend the configuration with following values:
-
-```php
-<?php
-$config[SalesConstants::PAYMENT_METHOD_STATEMACHINE_MAPPING] = [
- ...
- PayoneConfig::PAYMENT_METHOD_INVOICE => 'PayoneInvoice',
-];
-
-$config[OmsConstants::ACTIVE_PROCESSES] = [
- ...
- 'PayoneInvoice',
-];
-```
-
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-online-transfer-payment.md b/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-online-transfer-payment.md
deleted file mode 100644
index 675f24d4ac9..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-online-transfer-payment.md
+++ /dev/null
@@ -1,83 +0,0 @@
----
-title: PayOne - Online Transfer Payment
-description: Integrate online transfer payment through Payone into the Spryker-based shop.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/payone-online-trans
-originalArticleId: 88c7cb3d-2f41-4a0c-8c16-0d458b0f180d
-redirect_from:
-  - /2021080/docs/payone-online-trans
-  - /2021080/docs/en/payone-online-trans
-  - /docs/payone-online-trans
-  - /docs/en/payone-online-trans
-related:
-  - title: PayOne - Prepayment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-prepayment.html
-  - title: PayOne - Authorization and Preauthorization Capture Flows
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-authorization-and-preauthorization-capture-flows.html
-  - title: PayOne - Invoice Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-invoice-payment.html
-  - title: PayOne - Cash on Delivery
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/scos-integration/payone-cash-on-delivery.html
-  - title: PayOne - Direct Debit Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-direct-debit-payment.html
-  - title: PayOne - Security Invoice Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-security-invoice-payment.html
----
-
-Supported online banking service providers are SofortBanking, Giropay, Electronic Payment Standard (Eps), PostFinance Card, PostFinance E-Finance, iDEAL, Przelewy24, and Bancontact. They are enabled  through the integration with Payone, using the online transfer payment type.
-
-Each payment method is limited to certain set of store countries:
-
-* SofortBanking: DE, AT, CH, NL
-* Giropay: DE
-* Electronic Payment Standard (Eps): AT
-* PostFinance Card, PostFinance E-Finance: CH
-* iDEAL: NL
-* Bancontact: BE
-
-The authorization of the transaction is done through a redirect and the customer has to execute the payment authorization. After the customer confirms the payment, their account is charged directly.
-
-## Front-end Integration
-
-To adjust the frontend appearance, provide the following templates inside your theme directory:
-
-* `src/<project_name>/Yves/Payone/Theme/<custom_theme_name>/eps_online_transfer.twig`
-* `src/<project_name>/Yves/Payone/Theme/<custom_theme_name>/giropay_online_transfer.twig`
-* `src/<project_name>/Yves/Payone/Theme/<custom_theme_name>/ideal_online_transfer.twig`
-* `src/<project_name>/Yves/Payone/Theme/<custom_theme_name>/instant_online_transfer.twig`
-* `src/<project_name>/Yves/Payone/Theme/<custom_theme_name>/postfinance_card_online_transfer.twig`
-* `src/<project_name>/Yves/Payone/Theme/<custom_theme_name>/postfinance_efinance_online_transfer.twig`
-* `src/<project_name>/Yves/Payone/Theme/<custom_theme_name>/przelewy24_online_transfer.twig`
-* `src/<project_name>/Yves/Payone/Theme/<custom_theme_name>/bancontact_online_transfer.twig`
-
-## State Machine Integration
-
-Payone module provides a demo state machine for Online Transfer payment method which implements Authorization flow. Preauthorization/Capture is not possible for Online Transfer payment.
-
-To enable the demo state machine, extend the configuration with following values:
-
-```php
-<?php
-$config[SalesConstants::PAYMENT_METHOD_STATEMACHINE_MAPPING] = [
- ...
- PayoneConfig::PAYMENT_METHOD_EPS_ONLINE_TRANSFER => 'PayoneOnlineTransfer',
- PayoneConfig::PAYMENT_METHOD_INSTANT_ONLINE_TRANSFER => 'PayoneOnlineTransfer',
- PayoneConfig::PAYMENT_METHOD_GIROPAY_ONLINE_TRANSFER => 'PayoneOnlineTransfer',
- PayoneConfig::PAYMENT_METHOD_IDEAL_ONLINE_TRANSFER => 'PayoneOnlineTransfer',
- PayoneConfig::PAYMENT_METHOD_POSTFINANCE_CARD_ONLINE_TRANSFER => 'PayoneOnlineTransfer',
- PayoneConfig::PAYMENT_METHOD_POSTFINANCE_EFINANCE_ONLINE_TRANSFER => 'PayoneOnlineTransfer',
- PayoneConfig::PAYMENT_METHOD_PRZELEWY24_ONLINE_TRANSFER => 'PayoneOnlineTransfer',
- PayoneConfig::PAYMENT_METHOD_BANCONTACT_ONLINE_TRANSFER => 'PayoneOnlineTransfer',
-];
-
-$config[OmsConstants::ACTIVE_PROCESSES] = [
- ...
- 'PayoneOnlineTransfer',
-];
-```
-
-## Online Transfer Payment Flow:
-
-1. Customer selects the payment method and, if necessary, fills in the payment details on checkout.
-2. On order placement, the customer is redirected to the payment providers page. Depending on results, the user is redirected back  to the corresponding page (success page, error page or cancellation page) in the shop after that.
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-paypal-express-checkout-payment.md b/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-paypal-express-checkout-payment.md
deleted file mode 100644
index 0534d649a32..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-paypal-express-checkout-payment.md
+++ /dev/null
@@ -1,136 +0,0 @@
----
-title: PayOne - PayPal Express Checkout Payment
-description: Integrate PayPal Express Checkout Payment through Payone into the Spryker-based shop.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/payone-paypal-express-checkout-payment
-originalArticleId: f21d94b3-391e-4e45-ba35-f5a29cf66e3f
-redirect_from:
-  - /2021080/docs/payone-paypal-express-checkout-payment
-  - /2021080/docs/en/payone-paypal-express-checkout-payment
-  - /docs/payone-paypal-express-checkout-payment
-  - /docs/en/payone-paypal-express-checkout-payment
----
-
-The payment using PayPal requires redirect to PayPal website. When the customer is redirected to PayPal's website, he must authorize himself and he has the option to either cancel or validate the transaction.
-
-A concern regarding payment flows that require redirection on third party website pages is that you loose control over the customer's action (the customer can close the browser before accepting or canceling the transaction). If this is the case, PayPal sends an instant payment notification (IPN) to Payone, then Payone notifies Spryker.
-
-## Front-end Integration
-
-To adjust the frontend appearance, add the following templates in your theme directory:
-
-`src/<project_name>/Yves/Cart/Theme/<custom_theme_name>/cart/parts/cart-summary.twig`
-
-Add the following code below the checkout button or anywhere you want depending on your design:
-
-```php
-{% raw %}{{{% endraw %} render(path('payone-checkout-with-paypal-button')) {% raw %}}}{% endraw %}
-```
-
-You can also implement your own button if you want the button to be loaded without separate call to the controller, or if you want to change the design.
-
-## Paypal Express Checkout Flow Description:
-
-* Once you click on the "Checkout with PayPal" button, the genericpayment request is sent to Payone with `setexpresscheckout` action and success, failure and back URLs.
-* In the response we receive a workorderid which is used for all other operations until the capture request and PayPal redirect URL.
-* We store wordorderid to quote and redirect customer to the URL provided by Payone.
-* On the PayPal page, customer has to log in and approve the intention of paying for the desired goods.
-* After the customer clicks the button, he is redirected to success or failure URL, provided by the shop in the first request to Payone.
-* After redirection to success action, one more genericpayment request to Payone is made with action `getexpresscheckoutdetails`.
-* Payone sends us information about the customer like email and shipment data.
-* User is redirected to the page(summary page as default) of standard checkout.
-* After placing the order, the pre-authorization call is sent to Payone (and through it to PayPal). Workorderid is sent to Payone with this request.
-* Order status becomes "pre-authorized pending" after the response with status OK is received.
-
-## State Machine Integration
-
-Payone module provides a demo state machine for Paypal Express Checkout payment method which implements Preauthorization/Capture flow.
-
-To enable the demo state machine, extend the configuration with the following values:
-
-```php
-<?php
-$config[SalesConstants::PAYMENT_METHOD_STATEMACHINE_MAPPING] = [
- ...
- PayoneConfig::PAYMENT_METHOD_PAYPAL_EXPRESS_CHECKOUT => 'PayonePaypalExpressCheckout',
-];
-
-$config[OmsConstants::ACTIVE_PROCESSES] = [
- ...
- 'PayonePaypalExpressCheckout',
-];
- ```
-
-{% info_block infoBox "Note" %}
-
-You can find all needed configuration parameters in `config.dist.php` file inside Payone module.
-
-{% endinfo_block %}
-
-
-## Configuration Parameters Description:
-
-To understand where to go, if control over express checkout process should be handed over to the project, Payone module needs several urls to be confgured in the global config:
-
-**PayoneConstants::PAYONE_STANDARD_CHECKOUT_ENTRY_POINT_URL** - URL, which is used when express checkout details are loaded to quote.
-Normally, its an URL to summary page or to some middleware URL, where additional logic can be added before going to checkout (e.g. filling some post conditions which are required to get to summary page in Spryker step-engine).
-
-**PayoneConstants::PAYONE_EXPRESS_CHECKOUT_FAILURE_URL** - URL where user is redirected when payone fails for some reason.
-
-**PayoneConstants::PAYONE_EXPRESS_CHECKOUT_BACK_URL** - URL where user is redirected when he/she goes back to Paypal side.
-
-```php
- $config[PayoneConstants::PAYONE][PayoneConstants::PAYONE_STANDARD_CHECKOUT_ENTRY_POINT_URL] = sprintf(
- '%s/checkout/paypal-express-checkout-entry-point',
- $config[ApplicationConstants::BASE_URL_YVES]
-);
- <br>
-$config[PayoneConstants::PAYONE][PayoneConstants::PAYONE_EXPRESS_CHECKOUT_FAILURE_URL] = sprintf(
- '%s/cart',
- $config[ApplicationConstants::BASE_URL_YVES]
-);
- <br>
-$config[PayoneConstants::PAYONE][PayoneConstants::PAYONE_EXPRESS_CHECKOUT_BACK_URL] = sprintf(
- '%s/cart',
- $config[ApplicationConstants::BASE_URL_YVES]
-);
- <br>
-```
-
-## Extra Configuration:
-
-To add possibility to skip standard checkout steps for guest user, customer step should be extended:
-Open **Yves/Checkout/Process/Steps/CustomerStep.php** file in your project and add the following code to **postCondition** and **requireInput** methods:
-
-```php
- public function requireInput(AbstractTransfer $quoteTransfer)
- {
- if ($this->isCustomerLoggedIn() || $quoteTransfer->getIsGuestExpressCheckout()) {
- return false;
- }
-
- return true;
- }
- ``````php
- public function postCondition(AbstractTransfer $quoteTransfer)
- {
- if ($this->isCustomerInQuote($quoteTransfer) === false) {
- return false;
- }
-
- if ($quoteTransfer->getIsGuestExpressCheckout()) {
- return true;
- }
-
- if ($this->isGuestCustomerSelected($quoteTransfer)) {
- if ($this->isCustomerLoggedIn()) {
- // override guest user with logged in user
- return false;
- }
-
- return true;
- }
- ...
- }
- ```
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-paypal-payment.md b/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-paypal-payment.md
deleted file mode 100644
index 3badeb9c345..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-paypal-payment.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: PayOne - Paypal Payment
-description: Integrate Paypal payment through Payone into the Spryker-based shop.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/payone-paypal
-originalArticleId: fa4285e0-f408-4b51-807a-1f1fb1a4cdb4
-redirect_from:
-  - /2021080/docs/payone-paypal
-  - /2021080/docs/en/payone-paypal
-  - /docs/payone-paypal
-  - /docs/en/payone-paypal
-related:
-  - title: PayOne - Prepayment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-prepayment.html
-  - title: PayOne - Authorization and Preauthorization Capture Flows
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-authorization-and-preauthorization-capture-flows.html
-  - title: PayOne - Invoice Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-invoice-payment.html
-  - title: PayOne - Cash on Delivery
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/scos-integration/payone-cash-on-delivery.html
-  - title: PayOne - Direct Debit Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-direct-debit-payment.html
-  - title: PayOne - Security Invoice Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-security-invoice-payment.html
----
-
-The payment using PayPal requires a redirect to PayPal website. When the customer is redirected to PayPal's website, he must authorize himself and he has the option to either cancel or validate the transaction.
-
-A concern regarding payment flows that require redirection on third party website pages is that you loose control over the customers action ( the customer can close the browser before accepting or canceling the transaction). If this is the case, PayPal sends an instant payment notification (IPN) to Payone, then Payone notifies Spryker.
-
-## Front-end Integration
-
-To adjust the frontend appearance, provide the following templates in your theme directory: `src/<project_name>/Yves/Payone/Theme/<custom_theme_name>/e_wallet.twig`
-
-PayPal Payment Integration with Payone:
-
-1. A `preAuthorize` command is submitted which leads to a redirect to PayPal webpage.
-2. Redirect to PayPal webpage.
-3. If browser is closed, a notification is sent to PayPal state machine.
-4. After the customer chooses to accept or to cancel the transaction, a redirect is done back to the shop; the redirect URL indicates the option selected by the user ( accept/cancel transaction).
-5. A `captureCommand` is submitted if the customer has accepted the transaction on PayPals website.
-
-## State Machine Integration
-
-Payone module provides a demo state machine for E-Wallet payment method which implements Preauthorization/Capture flow.
-
-To enable the demo state machine, extend the configuration with following values:
-
-```php
-<?php
-$config[SalesConstants::PAYMENT_METHOD_STATEMACHINE_MAPPING] = [
- ...
- PayoneConfig::PAYMENT_METHOD_E_WALLET => 'PayoneEWallet',
-];
-
-$config[OmsConstants::ACTIVE_PROCESSES] = [
- ...
- 'PayoneEWallet',
-];
-```
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-prepayment.md b/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-prepayment.md
deleted file mode 100644
index ad606250f15..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-prepayment.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: PayOne - Prepayment
-description: Integrate prepayment through Payone into the Spryker-based shop.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/payone-prepayment
-originalArticleId: f5e8ebb9-0fd4-4048-88e2-2d8a45bb4c06
-redirect_from:
-  - /2021080/docs/payone-prepayment
-  - /2021080/docs/en/payone-prepayment
-  - /docs/payone-prepayment
-  - /docs/en/payone-prepayment
-related:
-  - title: PayOne - Authorization and Preauthorization Capture Flows
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-authorization-and-preauthorization-capture-flows.html
-  - title: PayOne - Invoice Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-invoice-payment.html
-  - title: PayOne - Cash on Delivery
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/scos-integration/payone-cash-on-delivery.html
-  - title: PayOne - Direct Debit Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-direct-debit-payment.html
-  - title: PayOne - Security Invoice Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-security-invoice-payment.html
-  - title: PayOne - Online Transfer Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-online-transfer-payment.html
----
-
-Prepayment method is a safe alternative to payments involving credit cards or debit cards (such as online banking transfer). Usually bank transfer would require manual processing to mark transaction as cancelled or completed, but the process is fully automated through the integration with the Payone platform.
-
-The payment status is transmitted to the shop via a notification from the payment provider(Payone).
-
-## Front-end Integration
-
-To adjust the frontend appearance, provide the following templates in your theme directory:
-`src/<project_name>/Yves/Payone/Theme/<custom_theme_name>/prepayment.twig`
-
-## State Machine Integration
-
-Payone module provides a demo state machine for Prepayment payment method which implements Preauthorization/Capture flow.
-
-To enable the demo state machine, extend the configuration with the following values:
-
-```php
-<?php
-$config[SalesConstants::PAYMENT_METHOD_STATEMACHINE_MAPPING] = [
- ...
- PayoneConfig::PAYMENT_METHOD_PRE_PAYMENT => 'PayonePrePayment',
-];
-
-$config[OmsConstants::ACTIVE_PROCESSES] = [
- ...
- 'PayonePrePayment',
-];
-```
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-security-invoice-payment.md b/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-security-invoice-payment.md
deleted file mode 100644
index 492823437a1..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-security-invoice-payment.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: PayOne - Security Invoice Payment
-description: Integrate security invoice payment through Payone into the Spryker-based shop.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/payone-security-invoice
-originalArticleId: f993d3b7-e7be-4d7d-ab49-e907f5af256a
-redirect_from:
-  - /2021080/docs/payone-security-invoice
-  - /2021080/docs/en/payone-security-invoice
-  - /docs/payone-security-invoice
-  - /docs/en/payone-security-invoice
-related:
-  - title: PayOne - Authorization and Preauthorization Capture Flows
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-authorization-and-preauthorization-capture-flows.html
-  - title: PayOne - Invoice Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-invoice-payment.html
-  - title: PayOne - Cash on Delivery
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/scos-integration/payone-cash-on-delivery.html
-  - title: PayOne - Prepayment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-prepayment.html
-  - title: PayOne - Direct Debit Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-direct-debit-payment.html
-  - title: PayOne - Online Transfer Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-online-transfer-payment.html
----
-
-## Front-End Integration
-
-To adjust the frontend appearance, provide the following templates in your theme directory: `src/<project_name>/Yves/Payone/Theme/<custom_theme_name>/security_invoice.twig`
-
-## State Machine Integration
-
-Payone module provides a demo state machine for the Security Invoice payment method which implements Authorization flow.
-To enable the demo state machine, extend the configuration with following values:
-
-```php
-<?php
- $config[SalesConstants::PAYMENT_METHOD_STATEMACHINE_MAPPING] = [
- ...
- PayoneConfig::PAYMENT_METHOD_SECURITY_INVOICE => 'PayoneSecurityInvoice',
- ];
- $config[OmsConstants::ACTIVE_PROCESSES] = [
- ...
- 'PayoneSecurityInvoice',
- ];
- ```
-
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-state-machine-commands-conditions-and-events.md b/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-state-machine-commands-conditions-and-events.md
deleted file mode 100644
index 4e35e231c4a..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/legacy-demoshop-integration/payone-state-machine-commands-conditions-and-events.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: PayOne - State Machine Commands, Conditions and Events
-description: This article includes the state machine commands and conditions provided by Payone.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/payone-state-machine-cmd-cond-evnt
-originalArticleId: 807aa919-3bf4-44c1-8a0b-60305df0434b
-redirect_from:
-  - /2021080/docs/payone-state-machine-cmd-cond-evnt
-  - /2021080/docs/en/payone-state-machine-cmd-cond-evnt
-  - /docs/payone-state-machine-cmd-cond-evnt
-  - /docs/en/payone-state-machine-cmd-cond-evnt
-related:
-  - title: PayOne - Authorization and Preauthorization Capture Flows
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-authorization-and-preauthorization-capture-flows.html
-  - title: PayOne - Invoice Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-invoice-payment.html
-  - title: PayOne - Cash on Delivery
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/scos-integration/payone-cash-on-delivery.html
-  - title: PayOne - Prepayment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-prepayment.html
-  - title: PayOne - Direct Debit Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-direct-debit-payment.html
-  - title: PayOne - Security Invoice Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-security-invoice-payment.html
----
-
-| OPERATION | TYPE | DESCRIPTION |
-| --- | --- | --- |
-| `Payone/PreAuthorize` | command | PreAuthorize allows blocking money without capturing it directly. Possible responses are Approved, Redirect (in case of 3d secure for Credit Card, also for all Online Transfer and EWallet payments) and Error. Payment data is verified and stored. The amount is reserved on the customers account. |
-| `Payone/PreAuthorizationIsApprovedPlugin` | condition | Checks if the preauthorization was successful |
-| `Payone/PreAuthorizationIsErrorPlugin` | condition | Checks if the preauthorization had an error |
-| `Payone/PreAuthorizationIsRedirectPlugin` | condition | Checks if the preauthorization send a redirect |
-| cancel redirect | event | This event is issued if cancel redirect url was engaged. This could be used in project state machine to re-activate voucher codes or perform similiar actions |
-| `Payone/PaymentIsAppointed` | condition | Checks if pre-authorization succeeded |
-| `RedirectResponseAppointed` | event | A RedirectResponse event is triggered if a redirect related response message was sent |
-| `Payone/Capture` | command | Capture allows to capture money that has been blocked with a preauthorize command. The card is now charged using the reserved amount. |
-| `Payone/CaptureWithSettlement` | command | Used for PrePayment method. |
-| `Payone/CaptureIsApprovedPlugin` | condition | Checks if the capture was approved |
-| `Payone/PaymentIsCapture` | condition | Checks if capture succeeded |
-| `Payone/Authorize` | command | Payment data is verified. Account is charged immediately. Possible responses are Approved, Redirect (in case of 3d secure for Credit Card, also for all Online Transfer and EWallet payments) and Error. Authorize allows to capture money immediately. |
-| `Payone/AuthorizationIsApprovedPlugin` | condition | Checks if the authorization was successful |
-| `Payone/AuthorizationIsErrorPlugin` | condition | Checks if the authorization had an error |
-| `Payone/AuthorizationIsRedirectPlugin` | condition | Checks if the authorization send a redirect |
-| Payone/PaymentIsPaid | condition | Checks if payment was paid in full |
-| `Payone/PaymentIsUnderPaid` | condition | Checks if payment was made but with balance that is not settled |
-| `Payone/PaymentIsOverpaid` | condition | Checks if total paid amount exceeds initial one |
-| `PaymentNotificationReceived` | event | A `PaymentNotificationReceived` event is triggered successful processing of incoming payment status update notification |
-| `Payone/Refund` | command | Refund allows to return money (in case of goods returns e.g.) |
-| `Payone/RefundIsApprovedPlugin` | condition | `RefundIsApprovedPlugin` checks if the refund was approved |
-| `Payone/RefundIsPossiblePlugin` | condition | `RefundIsPossiblePlugin` checks if IBAN/BIC is available in payment details |
-| `Payone/PaymentIsRefund` | condition | Checks if refund suceeded |
-| `Payone/Cancel` | command | Cancels pre-authorized amount. Could be called instead of Capture on order cancellation. |
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/scos-integration/payone-cash-on-delivery.md b/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/scos-integration/payone-cash-on-delivery.md
deleted file mode 100644
index e500cef2ee5..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/scos-integration/payone-cash-on-delivery.md
+++ /dev/null
@@ -1,96 +0,0 @@
----
-title: PayOne - Cash on Delivery
-description: Integrate  Cash on Delivery payment through Payone into the Spryker-based shop.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/payone-cash-on-delivery
-originalArticleId: e68a44fe-8cfe-4199-a3d0-537c04107688
-redirect_from:
-  - /2021080/docs/payone-cash-on-delivery
-  - /2021080/docs/en/payone-cash-on-delivery
-  - /docs/payone-cash-on-delivery
-  - /docs/en/payone-cash-on-delivery
-related:
-  - title: PayOne - Authorization and Preauthorization Capture Flows
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-authorization-and-preauthorization-capture-flows.html
-  - title: PayOne - Invoice Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-invoice-payment.html
-  - title: PayOne - Prepayment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-prepayment.html
-  - title: PayOne - Direct Debit Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-direct-debit-payment.html
-  - title: PayOne - Security Invoice Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-security-invoice-payment.html
-  - title: PayOne - Online Transfer Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-online-transfer-payment.html
----
-
-## Frontend Integration: Extending Checkout Page
-
-**src/Pyz/Yves/CheckoutPage/CheckoutPageDependencyProvider.php**
-
- ```php
- <?php
-
-namespace Pyz\Yves\CheckoutPage;
-
-use Generated\Shared\Transfer\PaymentTransfer;
-use Spryker\Yves\Kernel\Container;
-use Spryker\Yves\StepEngine\Dependency\Plugin\Form\SubFormPluginCollection;
-use Spryker\Yves\StepEngine\Dependency\Plugin\Handler\StepHandlerPluginCollection;
-use SprykerEco\Yves\Payone\Plugin\PayoneCashOnDeliverySubFormPlugin;
-use SprykerShop\Yves\CheckoutPage\CheckoutPageDependencyProvider as SprykerShopCheckoutPageDependencyProvider;
-
-class CheckoutPageDependencyProvider extends SprykerShopCheckoutPageDependencyProvider
-{
- const CLIENT_PAYONE = 'CLIENT_PAYONE';
-
- public function provideDependencies($container): Container
- {
- $container = parent::provideDependencies($container);
- $container = $this->provideClients($container);
-
- $container[static::PAYMENT_METHOD_HANDLER] = function () {
- $paymentMethodHandler = new StepHandlerPluginCollection();
- $paymentMethodHandler->add(new PayoneHandlerPlugin(), PaymentTransfer::PAYONE_CASH_ON_DELIVERY);
-
- return $paymentMethodHandler;
- };
-
- $container[static::PAYMENT_SUB_FORMS] = function () {
- $paymentSubFormPlugin = new SubFormPluginCollection();
- $paymentSubFormPlugin->add(new PayoneCashOnDeliverySubFormPlugin());
-
- return $paymentSubFormPlugin;
- };
-
- return $container;
- }
-
- protected function provideClients(Container $container)
- {
- $container[static::CLIENT_PAYONE] = function (Container $container) {
- return $container->getLocator()->payone()->client();
- };
- return $container;
- }
-}
-```
-
-## State Machine Integration: Extending the State Machine
-
-**config/Shared/config_default.php**
-
- ```php
- <?php
-
-$config[OmsConstants::ACTIVE_PROCESSES] = [
- 'PayoneCashOnDelivery',
- ...
-];
-
-$config[SalesConstants::PAYMENT_METHOD_STATEMACHINE_MAPPING] = [
- PayoneConfig::PAYMENT_METHOD_CASH_ON_DELIVERY => 'PayoneCashOnDelivery',
- ...
-];
-```
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/scos-integration/payone-integration-into-the-scos-project.md b/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/scos-integration/payone-integration-into-the-scos-project.md
deleted file mode 100644
index bff9060e1f0..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/scos-integration/payone-integration-into-the-scos-project.md
+++ /dev/null
@@ -1,499 +0,0 @@
----
-title: PayOne - Integration into the SCOS Project
-description: Integrate Payone into the Spryker Commerce OS by following the instructions from this article.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/payone-integration-with-project-scos
-originalArticleId: a86017aa-d5ce-44cf-b568-6cda73261766
-redirect_from:
-  - /2021080/docs/payone-integration-with-project-scos
-  - /2021080/docs/en/payone-integration-with-project-scos
-  - /docs/payone-integration-with-project-scos
-  - /docs/en/payone-integration-with-project-scos
-related:
-  - title: PayOne - Cash on Delivery
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/scos-integration/payone-cash-on-delivery.html
-  - title: PayOne - Authorization and Preauthorization Capture Flows
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-authorization-and-preauthorization-capture-flows.html
-  - title: PayOne - Invoice Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-invoice-payment.html
-  - title: PayOne - Prepayment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-prepayment.html
-  - title: PayOne - Direct Debit Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-direct-debit-payment.html
-  - title: PayOne - Security Invoice Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-security-invoice-payment.html
-  - title: PayOne - Online Transfer Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-online-transfer-payment.html
-  - title: PayOne - Paypal Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-paypal-payment.html
----
-
-{% info_block errorBox %}
-
-There is currently an issue when using giftcards with PayOne. Our team is developing a fix for it.
-
-{% endinfo_block %}
-
-**Objectives:**
-* Place order with PayPal express checkout.
-* Be redirected to summary page of standard checkout.
-* Have a shipping method selector on summary page.
-
-## Frontend Update
-
-To make JavaScript and CSS styles enabled in the Suite, update:
-`<root>/tsconfig.json` in section "include":
-
-```php
-./vendor/spryker-eco/**/*",
-```
-
-Update `<root>/frontend/settings.js`:
-
-add entry to 'paths':
-
-```php
-// eco folders
-eco: {
- // all modules
- modules: './vendor/spryker-eco'
-},
-```
-
-add one more directory to `module.exports.find.componentEntryPoints.dirs`:
-
-```php
-path.join(context, paths.eco.modules)
-```
-
-Run `npm run yves` after applying these changes.
-Due to the pending update to Suite, you also have to apply Checkout template `.../src/Pyz/Yves/CheckoutPage/Theme/default/views/payment/payment.twig` update:
-
-```xml
-{% raw %}{%{% endraw %} extends template('page-layout-checkout', 'CheckoutPage') {% raw %}%}{% endraw %}
-
-{% raw %}{%{% endraw %} define data = {
- backUrl: _view.previousStepUrl,
- forms: {
- payment: _view.paymentForm
- },
- title: 'checkout.step.payment.title' | trans
-} {% raw %}%}{% endraw %}
-
-{% raw %}{%{% endraw %} block content {% raw %}%}{% endraw %}
- {% raw %}{%{% endraw %} embed molecule('form') with {
- class: 'box',
- data: {
- form: data.forms.payment,
- options: {
- attr: {
- id: 'payment-form'
- }
- },
- submit: {
- enable: true,
- text: 'checkout.step.summary' | trans
- },
- cancel: {
- enable: true,
- url: data.backUrl,
- text: 'general.back.button' | trans
- }
- }
- } only {% raw %}%}{% endraw %}
- {% raw %}{%{% endraw %} block fieldset {% raw %}%}{% endraw %}
- {% raw %}{%{% endraw %} for name, choices in data.form.paymentSelection.vars.choices {% raw %}%}{% endraw %}
- {% raw %}{%{% endraw %} set paymentProviderIndex = loop.index0 {% raw %}%}{% endraw %}
- <h5>{% raw %}{{{% endraw %} ('checkout.payment.provider.' ~ name) | trans {% raw %}}}{% endraw %}</h5>
- <ul>
- {% raw %}{%{% endraw %} for key, choice in choices {% raw %}%}{% endraw %}
- <li class="list__item spacing-y clear">
- {% raw %}{%{% endraw %} embed molecule('form') with {
- data: {
- form: data.form[data.form.paymentSelection[key].vars.value],
- enableStart: false,
- enableEnd: false
- },
- embed: {
- index: loop.index ~ '-' ~ paymentProviderIndex,
- toggler: data.form.paymentSelection[key],
- }
- } only {% raw %}%}{% endraw %}
- {% raw %}{%{% endraw %} block fieldset {% raw %}%}{% endraw %}
- {% raw %}{{{% endraw %} form_row(embed.toggler, {
- required: false,
- component: molecule('toggler-radio'),
- attributes: {
- 'target-selector': '.js-payment-method-' ~ embed.index,
- 'class-to-toggle': 'is-hidden'
- }
- }) {% raw %}}}{% endraw %}
- <div class="col col--sm-12 is-hidden js-payment-method-{% raw %}{{{% endraw %}embed.index{% raw %}}}{% endraw %}">
- <div class="col col--sm-12 col--md-6">
- {% raw %}{%{% endraw %} if data.form.vars.template_path is defined {% raw %}%}{% endraw %}
- {% raw %}{%{% endraw %} set paymentPath = data.form.vars.template_path | split('/') {% raw %}%}{% endraw %}
- {% raw %}{%{% endraw %} set nameTemplate = paymentPath[1] | replace('_', '-') {% raw %}%}{% endraw %}
- {% raw %}{%{% endraw %} include view(nameTemplate, paymentPath[0]) ignore missing with {
- form: data.form.parent
- } only {% raw %}%}{% endraw %}
- {% raw %}{%{% endraw %} else {% raw %}%}{% endraw %}
- {% raw %}{{{% endraw %}parent(){% raw %}}}{% endraw %}
- {% raw %}{%{% endraw %} endif {% raw %}%}{% endraw %}
- </div>
- </div>
- {% raw %}{%{% endraw %} endblock {% raw %}%}{% endraw %}
- {% raw %}{%{% endraw %} endembed {% raw %}%}{% endraw %}
- </li>
- {% raw %}{%{% endraw %} endfor {% raw %}%}{% endraw %}
- </ul>
- {% raw %}{%{% endraw %} endfor {% raw %}%}{% endraw %}
- {% raw %}{%{% endraw %} endblock {% raw %}%}{% endraw %}
- {% raw %}{%{% endraw %} endembed {% raw %}%}{% endraw %}
-{% raw %}{%{% endraw %} endblock {% raw %}%}{% endraw %}
-```
-
-Run `console cache:empty` afterwards to make this template used during rendering.
-
-## Backend Update
-
-First of all we need to provide a URL to Payone module, which will be used to redirect user when the quote is filled with data obtained from PayPal.
- To achieve this, make the following steps:
-
-1. Add custom controller action to `src/Pyz/Yves/Checkout/Controller/CheckoutController.php`:
-
-```php
-/**
-* @return \Symfony\Component\HttpFoundation\RedirectResponse
-*/
-public function paypalExpressCheckoutEntryPointAction()
-{
-$this->getFactory()
-->createExpressCheckoutHandler()
-->fulfillPostConditionsUntilSummaryStep();
-return $this->redirectResponseInternal(CheckoutPageControllerProvider::CHECKOUT_SUMMARY);
-}
-```
-2. Register a new controller action in controller provider:
-
-```php
-...
-const CHECKOUT_PAYPAL_EXPRESS_CHECKOUT_ENTRY_POINT = 'checkout-paypal-express-checkout-entry-point';
-...
-protected function defineControllers(Application $app)
-{
-...
-$this->createController('/{checkout}/paypal-express-checkout-entry-point', self::CHECKOUT_PAYPAL_EXPRESS_CHECKOUT_ENTRY_POINT, 'Checkout', 'Checkout', 'paypalExpressCheckoutEntryPoint')
-->assert('checkout', $allowedLocalesPattern . 'checkout|checkout')
-->value('checkout', 'checkout')
-->method('GET');
-...
-}
-```
-3. Create `ExpressCheckoutHandler` class `src/Pyz/Yves/CheckoutPage/Handler/ExpressCheckoutHandler.php` with corresponding interface:
-
-```php
-namespace Pyz\Yves\CheckoutPage\Handler;
-use Generated\Shared\Transfer\ExpenseTransfer;
-use Spryker\Client\Cart\CartClientInterface;
-use Spryker\Shared\Shipment\ShipmentConstants;
-class ExpressCheckoutHandler implements ExpressCheckoutHandlerInterface
-{
-/**
-* @var \Spryker\Client\Cart\CartClientInterface
-*/
-protected $cartClient;
-/**
-* @param \Spryker\Client\Cart\CartClientInterface $cartClient
-*/
-public function __construct(CartClientInterface $cartClient)
-{
-$this->cartClient = $cartClient;
-}
-/**
-* @return void
-*/
-public function fulfillPostConditionsUntilSummaryStep()
-{
-$quoteTransfer = $this->cartClient->getQuote();
-$quoteTransfer->addExpense(
-(new ExpenseTransfer())->setType(ShipmentConstants::SHIPMENT_EXPENSE_TYPE)
-);
-}
-}
-```
-
-4. Add `ExpressCheckoutHandler` related method in `src/Pyz/Yves/CheckoutPage/CheckoutPageFactory.php`:
-
-```php
-/**
-* @return \Pyz\Yves\CheckoutPage\Handler\ExpressCheckoutHandler
-*/
-public function createExpressCheckoutHandler()
-{
-return new ExpressCheckoutHandler(
-$this->getCartClient()
-);
-}
-```
-
-5. Extend `ShipmentForm` class to override a property_path option (create `src/Pyz/Yves/Shipment/Form/ShipmentSubForm.php`):
-
-```php
-namespace Pyz\Yves\Shipment\Form;
-class ShipmentSubForm extends ShipmentForm
-{
-/**
-* @const string
-*/
-const SHIPMENT_SELECTION_PROPERTY_PATH = self::SHIPMENT_SELECTION;
-}
-```
-
-6. Adjust summary form by adding a shipment subform in `src/Pyz/Yves/CheckoutPage/Form/Steps/SummaryForm.php`:
-
-```php
-class SummaryForm extends AbstractType
-{
-/**
-* Builds the form.
-*
-* This method is called for each type in the hierarchy starting from the
-* top most type. Type extensions can further modify the form.
-*
-* @see FormTypeExtensionInterface::buildForm()
-*
-* @param \Symfony\Component\Form\FormBuilderInterface $builder The form builder
-* @param array $options The options
-*
-* @return void
-*/
-public function buildForm(FormBuilderInterface $builder, array $options)
-{
-$builder->add(
-'shipmentForm',
-ShipmentSubForm::class,
-array_merge(
-$options,
-[
-'data_class' => ShipmentTransfer::class,
-'property_path' => 'shipment',
-]
-)
-);
-}
-/**
-* @param \Symfony\Component\OptionsResolver\OptionsResolver $resolver
-*
-* @return void
-*/
-public function configureOptions(OptionsResolver $resolver)
-{
-$resolver->setRequired('shipmentMethods');
-$resolver->setDefaults([
-'data_class' => QuoteTransfer::class,
-]);
-}
-/**
-* Returns the name of this type.
-*
-* @return string The name of this type
-*/
-public function getName()
-{
-return 'summaryForm';
-}
-}
-```
-
-7. Create shipment subform template for summary page in `src/Pyz/Yves/CheckoutPage/Theme/default/checkout/partials/shipment.twig`:
-
-```php
-
-<div class="row columns">
-
- {% raw %}{%{% endraw %} set shipmentForm = summaryForm.shipmentForm {% raw %}%}{% endraw %}
-
- <div class="callout">
-  <ul class="no-bullet">
-
-   {% raw %}{%{% endraw %} for name, choices in shipmentForm.idShipmentMethod.vars.choices {% raw %}%}{% endraw %}
-
-   <h4>{% raw %}{{{% endraw %} name {% raw %}}}{% endraw %}</h4>
-
-   {% raw %}{%{% endraw %} for key, choice in choices {% raw %}%}{% endraw %}
-   <li>
-    <label>
-     {% raw %}{{{% endraw %} form_widget(shipmentForm.idShipmentMethod[key], {'attr': {'class': '__toggler'{% raw %}}}{% endraw %}) {% raw %}}}{% endraw %}
-     {% raw %}{{{% endraw %} shipmentForm.idShipmentMethod[key].vars.label | raw {% raw %}}}{% endraw %}
-    </label>
-   </li>
-   {% raw %}{%{% endraw %} endfor {% raw %}%}{% endraw %}
-   {% raw %}{%{% endraw %} endfor {% raw %}%}{% endraw %}
-  </ul>
- </div>
-</div>
-```
-
-8. Update summary twig template in `src/Pyz/Yves/CheckoutPage/Theme/default/checkout/summary.twig`.
-Move `"form_start"` expression to the top of a content section and `"form_end"` to the end:
-
-```php
-...
-{% raw %}{%{% endraw %} block content {% raw %}%}{% endraw %}
-{% raw %}{{{% endraw %} form_start(summaryForm, {'attr': {'class': 'row'{% raw %}}}{% endraw %}) {% raw %}}}{% endraw %}
-...
-...
-...
-{% raw %}{{{% endraw %} form_end(summaryForm) {% raw %}}}{% endraw %}
-{% raw %}{%{% endraw %} endblock {% raw %}%}{% endraw %}
-```
-
-9. Remove `{% raw %}{%{% endraw %} include '@checkout/checkout/partials/voucher-form.twig' {% raw %}%}{% endraw %}` include from summary template. Include `checkout/partials/shipment.twig` in your summary template:
-
-```php
-      ...
-{% raw %}{{{% endraw %} 'checkout.step.summary.shipping' | trans {% raw %}}}{% endraw %}
-      {% raw %}{%{% endraw %} include '@checkout/checkout/partials/shipment.twig' {% raw %}%}{% endraw %}
-      ...
-```
-10. Add shipment form data provider and remove voucher form from summary form collection(It is just an example, if you need voucher form, you need to adjust summary page on your own). In `src/Pyz/Yves/CheckoutPage/Form/FormFactory.php`:
-
-```php
-/**
-* @param \Generated\Shared\Transfer\QuoteTransfer
-*
-* @return \Spryker\Yves\StepEngine\Form\FormCollectionHandlerInterface
-*/
-public function createSummaryFormCollection()
-{
-return $this->createFormCollection($this->createSummaryFormTypes(), $this->getShipmentFormDataProviderPlugin());
-}
-
-....
-
-
-/**
-* @return \Symfony\Component\Form\FormTypeInterface[]
-*/
-protected function createSummaryFormTypes()
-{
-return [
-$this->createSummaryForm(),
-//$this->createVoucherFormType(),
-];
-}
-```
-
-11. Handle shipment form data, when summary form is submitted. Inject two dependencies into `src/Pyz/Yves/CheckoutPage/Process/Steps/SummaryStep.php`:
-
-```php
-/**
-* @var \Spryker\Client\Calculation\CalculationClientInterface
-*/
-protected $calculationClient;
-/**
-* @var \Spryker\Yves\StepEngine\Dependency\Plugin\Handler\StepHandlerPluginCollection
-*/
-protected $shipmentPlugins;
-/**
-* @param \Spryker\Yves\ProductBundle\Grouper\ProductBundleGrouperInterface $productBundleGrouper
-* @param \Spryker\Client\Cart\CartClientInterface $cartClient
-* @param \Spryker\Client\Calculation\CalculationClientInterface $calculationClient
-* @param \Spryker\Client\Calculation\CalculationClientInterface $shipmentPlugins
-* @param string $stepRoute
-* @param string $escapeRoute
-*/
-public function __construct(
-ProductBundleGrouperInterface $productBundleGrouper,
-CartClientInterface $cartClient,
-CalculationClientInterface $calculationClient,
-StepHandlerPluginCollection $shipmentPlugins,
-$stepRoute,
-$escapeRoute
-) {
-parent::__construct($stepRoute, $escapeRoute);
-$this->productBundleGrouper = $productBundleGrouper;
-$this->cartClient = $cartClient;
-$this->calculationClient = $calculationClient;
-$this->shipmentPlugins = $shipmentPlugins;
-}
-```
-
-12. Extend `execute` method:
-
-```php
-/**
-* @param \Symfony\Component\HttpFoundation\Request $request
-* @param \Spryker\Shared\Kernel\Transfer\AbstractTransfer|\Generated\Shared\Transfer\QuoteTransfer $quoteTransfer
-*
-* @return \Generated\Shared\Transfer\QuoteTransfer
-*/
-public function execute(Request $request, AbstractTransfer $quoteTransfer)
-{
-$shipmentHandler = $this->shipmentPlugins->get(CheckoutPageDependencyProvider::PLUGIN_SHIPMENT_STEP_HANDLER);
-$shipmentHandler->addToDataClass($request, $quoteTransfer);
-$this->calculationClient->recalculate($quoteTransfer);
-$this->markCheckoutConfirmed($request, $quoteTransfer);
-return $quoteTransfer;
-}
-```
-
-13. Add the Payone checkout plugins to `Pyz\Zed\Checkout\CheckoutDependencyProvider`:
-
-```php
-<?php
-
-namespace Pyz\Zed\Checkout;
-//...
-use SprykerEco\Zed\Payone\Communication\Plugin\Checkout\PayoneCheckoutDoSaveOrderPlugin;
-use SprykerEco\Zed\Payone\Communication\Plugin\Checkout\PayoneCheckoutPostSavePlugin;
-use SprykerEco\Zed\Payone\Communication\Plugin\Checkout\PayoneCheckoutPreConditionPlugin;
-class CheckoutDependencyProvider extends SprykerCheckoutDependencyProvider
-{
-    /**
-     * @param \Spryker\Zed\Kernel\Container $container
-     *
-     * @return \Spryker\Zed\CheckoutExtension\Dependency\Plugin\CheckoutPreConditionPluginInterface[]
-     */
-    protected function getCheckoutPreConditions(Container $container)
-    {
-        return [
-            //...
-            new PayoneCheckoutPreConditionPlugin(),
-            //...
-        ];
-    }
-
-    /**
-     * @param \Spryker\Zed\Kernel\Container $container
-     *
-     * @return \Spryker\Zed\Checkout\Dependency\Plugin\CheckoutSaveOrderInterface[]|\Spryker\Zed\CheckoutExtension\Dependency\Plugin\CheckoutDoSaveOrderInterface[]
-     */
-    protected function getCheckoutOrderSavers(Container $container)
-    {
-        return [
-            //...
-            new PayoneCheckoutDoSaveOrderPlugin(),
-            //...
-        ];
-    }
-
-    /**
-     * @param \Spryker\Zed\Kernel\Container $container
-     *
-     * @return \Spryker\Zed\CheckoutExtension\Dependency\Plugin\CheckoutPostSaveInterface[]
-     */
-    protected function getCheckoutPostHooks(Container $container)
-    {
-        return [
-            //...
-            new PayoneCheckoutPostSavePlugin(),
-            //...
-        ];
-    }
-    //...
-}
-```
-
-Now, go to checkout and try placing an order with PayPal express checkout.
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/scos-integration/payone-paypal-express-checkout-payment.md b/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/scos-integration/payone-paypal-express-checkout-payment.md
deleted file mode 100644
index c4bf55a635c..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/scos-integration/payone-paypal-express-checkout-payment.md
+++ /dev/null
@@ -1,136 +0,0 @@
----
-title: PayOne - PayPal Express Checkout payment
-description: Integrate PayPal Express Checkout payment through Payone into the Spryker-based shop.
-last_updated: Jun 29, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/payone-paypal-express-checkout-scos
-originalArticleId: 77d504fd-b731-4eb8-86a0-5435630900f8
-redirect_from:
-  - /2021080/docs/payone-paypal-express-checkout-scos
-  - /2021080/docs/en/payone-paypal-express-checkout-scos
-  - /docs/payone-paypal-express-checkout-scos
-  - /docs/en/payone-paypal-express-checkout-scos
----
-
-The payment using PayPal requires a redirect to the PayPal website. When customers are redirected to PayPal's website, they have to authorize and after that either cancel or validate the transaction.
-
-A concern regarding payment flows that require redirection to third-party website pages is that you lose control over the customer's action (the customer can close the browser before accepting or canceling the transaction). If this is the case, PayPal sends an instant payment notification (IPN) to Payone, then Payone notifies Spryker.
-
-## Front-End integration
-
-To adjust the frontend appearance, add the following templates in your theme directory:
-
-`src/<project_name>/Yves/CartPage/Theme/default/components/molecules/cart-summary/cart-summary.twig`
-Add the following code below the checkout button or anywhere you want, depending on your design:
-
-```bash
-{% raw %}{{{% endraw %} render(path('payone-checkout-with-paypal-button')) {% raw %}}}{% endraw %}
-```
-You can also implement your own button if you want the button to be loaded without a separate call to the controller or if you want to change the design.
-
-## Paypal Express Checkout flow description:
-
-* Once you click the **Checkout with PayPal** button, the genericpayment request is sent to Payone with `setexpresscheckout` action and success, failure and back URLs.
-* In the response we receive a workorderid which is used for all other operations until the capture request and PayPal redirect URL.
-* We store workorerid to quote and redirect customer to the URL provided by Payone.
-* On the *PayPal* page, customer has to log in and approve the intention of paying for the desired goods.
-* After clicking the button, the customer is redirected to the success or failure URL, provided by the shop in the first request to Payone.
-* After redirection to success action, one more generic payment request to Payone is made with action `getexpresscheckoutdetails`.
-* Payone sends us information about the customer, like email and shipment data.
-* The user is redirected to the page(summary page as default) of standard checkout.
-* After placing the order, the pre-authorization call is sent to Payone (and through it to PayPal). Workorderid is sent to Payone with this request.
-* Order status becomes "pre-authorized pending" after the response with status OK is received.
-
-## State machine integration
-
-Payone module provides a demo state machine for the Paypal Express Checkout payment method, which implements Preauthorization/Capture flow.
-
-To enable the demo state machine, extend the configuration with the following values:
-
-```php
-<?php
-$config[SalesConstants::PAYMENT_METHOD_STATEMACHINE_MAPPING] = [
- ...
- PayoneConfig::PAYMENT_METHOD_PAYPAL_EXPRESS_CHECKOUT => 'PayonePaypalExpressCheckout',
-];
-
-$config[OmsConstants::ACTIVE_PROCESSES] = [
- ...
- 'PayonePaypalExpressCheckout',
-];
- ```
-
-{% info_block infoBox "Note" %}
-
-You can find all needed configuration parameters in `config.dist.php` file inside Payone module.
-
-{% endinfo_block %}
-
-## Configuration parameters description:
-
-To understand where to go, if control over express checkout process should be handed over to the project,
-Payone module needs several URLs to be configured in the global config:
-
-`PayoneConstants::PAYONE_STANDARD_CHECKOUT_ENTRY_POINT_URL`—URL, which is used when express checkout details are loaded to quote.
-Normally, it's an URL to a summary page or to some middleware URL, where additional logic can be added before going to checkout (e.g., filling some postconditions required to get to the summary page in Spryker step-engine).
-
-`PayoneConstants::PAYONE_EXPRESS_CHECKOUT_FAILURE_URL`—URL where a user is redirected when payone fails for some reason.
-
-`PayoneConstants::PAYONE_EXPRESS_CHECKOUT_BACK_URL`—URL where users are redirected when they go back to Paypal side.
-
-```php
- $config[PayoneConstants::PAYONE][PayoneConstants::PAYONE_STANDARD_CHECKOUT_ENTRY_POINT_URL] = sprintf(
- '%s/checkout/paypal-express-checkout-entry-point',
- $config[ApplicationConstants::BASE_URL_YVES]
-);
-
-$config[PayoneConstants::PAYONE][PayoneConstants::PAYONE_EXPRESS_CHECKOUT_FAILURE_URL] = sprintf(
- '%s/cart',
- $config[ApplicationConstants::BASE_URL_YVES]
-);
-
-$config[PayoneConstants::PAYONE][PayoneConstants::PAYONE_EXPRESS_CHECKOUT_BACK_URL] = sprintf(
- '%s/cart',
- $config[ApplicationConstants::BASE_URL_YVES]
-);
-
-```
-
-## Extra configuration:
-
-To add a possibility to skip standard checkout steps for a guest customer, the customer step should be extended:
-Open `Yves/CheckoutPage/Process/Steps/CustomerStep.php` file in your project and add the following code to the `postCondition` and `requireInput` methods:
-
-```php
- public function requireInput(AbstractTransfer $quoteTransfer)
- {
- if ($this->isCustomerLoggedIn() || $quoteTransfer->getIsGuestExpressCheckout()) {
- return false;
- }
-
- return true;
- }
- ```
-
- ```php
- public function postCondition(AbstractTransfer $quoteTransfer)
- {
- if ($this->isCustomerInQuote($quoteTransfer) === false) {
- return false;
- }
-
- if ($quoteTransfer->getIsGuestExpressCheckout()) {
- return true;
- }
-
- if ($this->isGuestCustomerSelected($quoteTransfer)) {
- if ($this->isCustomerLoggedIn()) {
- // override guest user with logged in user
- return false;
- }
-
- return true;
- }
- ...
- }
- ```
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/scos-integration/payone-risk-check-and-address-check.md b/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/scos-integration/payone-risk-check-and-address-check.md
deleted file mode 100644
index 8d56f3c4758..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/bs-payone/scos-integration/payone-risk-check-and-address-check.md
+++ /dev/null
@@ -1,320 +0,0 @@
----
-title: PayOne - Risk Check and Address Check
-description: In this article, you will get information on the Payone risk check and address check services.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/payone-risk-check-address-check-scos
-originalArticleId: 38b985f4-811e-4e38-8f43-c7863cb5add2
-redirect_from:
-  - /2021080/docs/payone-risk-check-address-check-scos
-  - /2021080/docs/en/payone-risk-check-address-check-scos
-  - /docs/payone-risk-check-address-check-scos
-  - /docs/en/payone-risk-check-address-check-scos
-related:
-  - title: PayOne - Cash on Delivery
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/scos-integration/payone-cash-on-delivery.html
-  - title: PayOne - Authorization and Preauthorization Capture Flows
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-authorization-and-preauthorization-capture-flows.html
-  - title: PayOne - Invoice Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-invoice-payment.html
-  - title: PayOne - Prepayment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-prepayment.html
-  - title: PayOne - Direct Debit Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-direct-debit-payment.html
-  - title: PayOne - Security Invoice Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-security-invoice-payment.html
-  - title: PayOne - Online Transfer Payment
-    link: docs/scos/user/technology-partners/page.version/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-online-transfer-payment.html
----
-
-On the project level, you should override execute and postCondition methods of `SprykerShop\Yves\CheckoutPage\Process\Steps\AddressStep`.
-
-**src/Pyz/Yves/CheckoutPage/Process/Steps/AddressStep.php**
-
-```php
-<?php
-
-namespace Pyz\Yves\CheckoutPage\Process\Steps;
-
-use Generated\Shared\Transfer\QuoteTransfer;
-use Spryker\Shared\Kernel\Transfer\AbstractTransfer;
-use SprykerEco\Client\Payone\PayoneClientInterface;
-use SprykerShop\Yves\CheckoutPage\Dependency\Client\CheckoutPageToCalculationClientInterface;
-use SprykerShop\Yves\CheckoutPage\Dependency\Client\CheckoutPageToCustomerClientInterface;
-use SprykerShop\Yves\CheckoutPage\Process\Steps\AddressStep as SprykerAddressStep;
-use Symfony\Component\HttpFoundation\Request;
-
-class AddressStep extends SprykerAddressStep
-{
- protected const ADDRESS_CHECK_STATUS_VALID = 'VALID';
-
- /**
- * @var \SprykerEco\Client\Payone\PayoneClientInterface
- */
- protected $payoneClient;
-
- public function __construct(CheckoutPageToCustomerClientInterface $customerClient, CheckoutPageToCalculationClientInterface $calculationClient, string $stepRoute, string $escapeRoute, PayoneClientInterface $payoneClient)
- {
- parent::__construct($customerClient, $calculationClient, $stepRoute, $escapeRoute);
- $this->payoneClient = $payoneClient;
- }
-
- public function execute(Request $request, AbstractTransfer $quoteTransfer)
- {
- ...
- $responseTransfer = $this->payoneClient->sendAddressCheckRequest($quoteTransfer);
- $quoteTransfer->setIsAddressValid($responseTransfer->getStatus() === static::ADDRESS_CHECK_STATUS_VALID);
- ...
- }
-
- /**
- * @param \Generated\Shared\Transfer\QuoteTransfer|\Spryker\Shared\Kernel\Transfer\AbstractTransfer $quoteTransfer
- *
- * @return bool
- */
- public function postCondition(AbstractTransfer $quoteTransfer)
- {
- ...
-
- if (!$quoteTransfer->getIsAddressValid()) {
- return false;
- }
-
- ...
- }
-}
-```
-
-Also, `src/Pyz/Yves/CheckoutPage/Process/StepFactory.php` should be updated on the project level.
-
-**src/Pyz/Yves/CheckoutPage/Process/StepFactory.php**
-
-```php
-<?php
-
-namespace Pyz\Yves\CheckoutPage\Process;
-
-...
-use SprykerShop\Yves\HomePage\Plugin\Provider\HomePageControllerProvider;
-...
-
-class StepFactory extends SprykerStepFactory
-{
- /**
- * @var PayoneClientInterface
- */
- protected $payoneClient;
-
- public function __construct(PayoneClientInterface $payoneClient)
- {
- $this->payoneClient = $payoneClient;
- }
-
- ...
-
- /**
- * @return \Pyz\Yves\CheckoutPage\Process\Steps\AddressStep
- */
- public function createAddressStep()
- {
- return new AddressStep(
- $this->getCustomerClient(),
- $this->getCalculationClient(),
- CheckoutPageControllerProvider::CHECKOUT_ADDRESS,
- HomePageControllerProvider::ROUTE_HOME,
- $this->payoneClient
- );
- }
-
- ...
-}
-```
-
-## Consumer Score Integration
-
-On the project level, you should override the execute method of `SprykerShop\Yves\CheckoutPage\Process\Steps\AddressStep`.
-
-**src/Pyz/Yves/CheckoutPage/Process/Steps/ShipmentStep.php**
-
- ```php
-<?php
-
-namespace Pyz\Yves\CheckoutPage\Process\Steps;
-use Generated\Shared\Transfer\QuoteTransfer;
-use Spryker\Shared\Kernel\Transfer\AbstractTransfer;
-use Spryker\Yves\StepEngine\Dependency\Plugin\Handler\StepHandlerPluginCollection;
-use SprykerEco\Client\Payone\PayoneClientInterface;
-use SprykerShop\Yves\CheckoutPage\Dependency\Client\CheckoutPageToCalculationClientInterface;
-use SprykerShop\Yves\CheckoutPage\Process\Steps\ShipmentStep as SprykerShipmentStep;
-use Symfony\Component\HttpFoundation\Request;
-
-class ShipmentStep extends SprykerShipmentStep
-{
- /**
- * @var PayoneClientInterface
- */
- protected $payoneClient;
-
- public function __construct(
- CheckoutPageToCalculationClientInterface $calculationClient,
- StepHandlerPluginCollection $shipmentPlugins,
- string $stepRoute,
- string $escapeRoute,
- PayoneClientInterface $payoneClient
- ) {
- parent::__construct($calculationClient, $shipmentPlugins, $stepRoute, $escapeRoute);
- $this->payoneClient = $payoneClient;
- }
-
- public function execute(Request $request, AbstractTransfer $quoteTransfer)
- {
- $responseTransfer = $this->payoneClient->sendConsumerScoreRequest($quoteTransfer);
- $quoteTransfer->setConsumerScore($responseTransfer->getScore());
- return parent::execute($request, $quoteTransfer);
- }
-}
-```
-
-`src/Pyz/Yves/CheckoutPage/Process/StepFactory.php` should be updated:
-
-**src/Pyz/Yves/CheckoutPage/Process/Steps/ShipmentStep.php**
-
- ```php
-<?php
-
-namespace Pyz\Yves\CheckoutPage\Process\Steps;
-use Generated\Shared\Transfer\QuoteTransfer;
-use Spryker\Shared\Kernel\Transfer\AbstractTransfer;
-use Spryker\Yves\StepEngine\Dependency\Plugin\Handler\StepHandlerPluginCollection;
-use SprykerEco\Client\Payone\PayoneClientInterface;
-use SprykerShop\Yves\CheckoutPage\Dependency\Client\CheckoutPageToCalculationClientInterface;
-use SprykerShop\Yves\CheckoutPage\Process\Steps\ShipmentStep as SprykerShipmentStep;
-use Symfony\Component\HttpFoundation\Request;
-
-class ShipmentStep extends SprykerShipmentStep
-{
- /**
- * @var PayoneClientInterface
- */
- protected $payoneClient;
-
- public function __construct(
- CheckoutPageToCalculationClientInterface $calculationClient,
- StepHandlerPluginCollection $shipmentPlugins,
- string $stepRoute,
- string $escapeRoute,
- PayoneClientInterface $payoneClient
- ) {
- parent::__construct($calculationClient, $shipmentPlugins, $stepRoute, $escapeRoute);
- $this->payoneClient = $payoneClient;
- }
-
- public function execute(Request $request, AbstractTransfer $quoteTransfer)
- {
- $responseTransfer = $this->payoneClient->sendConsumerScoreRequest($quoteTransfer);
- $quoteTransfer->setConsumerScore($responseTransfer->getScore());
- return parent::execute($request, $quoteTransfer);
- }
-}
-```
-
-`src/Pyz/Yves/CheckoutPage/Process/StepFactory.php` should be updated:
-
-**src/Pyz/Yves/CheckoutPage/Process/StepFactory.php**
-
- ```php
-<?php
-
-namespace Pyz\Yves\CheckoutPage\Process;
-
-...
-use SprykerShop\Yves\HomePage\Plugin\Provider\HomePageControllerProvider;
-...
-
-class StepFactory extends SprykerStepFactory
-{
- /**
- * @var PayoneClientInterface
- */
- protected $payoneClient;
-
- public function __construct(PayoneClientInterface $payoneClient)
- {
- $this->payoneClient = $payoneClient;
- }
-
- ...
-
- public function createShipmentStep()
- {
- return new ShipmentStep(
- $this->getCalculationClient(),
- $this->getProvidedDependency(CheckoutPageDependencyProvider::PLUGIN_SHIPMENT_HANDLER),
- CheckoutPageControllerProvider::CHECKOUT_SHIPMENT,
- HomePageControllerProvider::ROUTE_HOME,
- $this->payoneClient
- );
- }
-
- ...
-}
-```
-
-`src/Pyz/Zed/Payment/PaymentDependencyProvider.php` should be updated:
-
-**src/Pyz/Zed/Payment/PaymentDependencyProvider.php**
-
- ```php
-<?php
-
-...
-use SprykerEco\Zed\Payone\Communication\Plugin\Payment\PayonePaymentMethodFilterPlugin;
-...
-
-class PaymentDependencyProvider extends SprykerPaymentDependencyProvider
-{
- ...
-
- /**
- * @return \Spryker\Zed\Payment\Dependency\Plugin\Payment\PaymentMethodFilterPluginInterface[]
- */
- protected function getPaymentMethodFilterPlugins(): array
- {
- return [
- new PayonePaymentMethodFilterPlugin(),
- ];
- }
- ...
-}
-```
-
-<br>Now Payone is ready for filtering Payment methods. Configuration for each score result should be defined in the config:
-
-**Example of configuration for score results**
-
- ```php
-<?php
-
- ...
-
- PayoneConstants::PAYONE_GREEN_SCORE_AVAILABLE_PAYMENT_METHODS => [
- PayoneConfig::PAYMENT_METHOD_INVOICE,
- PayoneConfig::PAYMENT_METHOD_CREDIT_CARD,
- ],
- PayoneConstants::PAYONE_YELLOW_SCORE_AVAILABLE_PAYMENT_METHODS => [
- PayoneConfig::PAYMENT_METHOD_EPS_ONLINE_TRANSFER
- ],
- PayoneConstants::PAYONE_RED_SCORE_AVAILABLE_PAYMENT_METHODS => [
- PayoneConfig::PAYMENT_METHOD_PRE_PAYMENT
- ],
- PayoneConstants::PAYONE_UNKNOWN_SCORE_AVAILABLE_PAYMENT_METHODS => [
- PayoneConfig::PAYMENT_METHOD_CREDIT_CARD,
- PayoneConfig::PAYMENT_METHOD_EPS_ONLINE_TRANSFER,
- PayoneConfig::PAYMENT_METHOD_PRE_PAYMENT,
- ],
-
- //Also you should define the check types for bot requests
- PayoneConstants::PAYONE_ADDRESS_CHECK_TYPE => 'BA',
- PayoneConstants::PAYONE_CONSUMER_SCORE_TYPE => 'IH',
-...
-```
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/computop.md b/docs/scos/user/technology-partners/202204.0/payment-partners/computop.md
deleted file mode 100644
index 9f9edf5719e..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/computop.md
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: Computop
-description: Enable merchants and white label customers to process global multichannel payments by integrating Computop into the Spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/computop
-originalArticleId: afe86236-29c0-44e5-94ed-8df656c7a9de
-redirect_from:
-  - /2021080/docs/computop
-  - /2021080/docs/en/computop
-  - /docs/computop
-  - /docs/en/computop
-related:
-  - title: Integrating the Sofort payment method for Computop
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-sofort-payment-method-for-computop.html
-  - title: Integrating the PayPal payment method for Computop
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-paypal-payment-method-for-computop.html
-  - title: Computop API calls
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/computop/computop-api-calls.html
-  - title: Integrating the PayNow payment method for Computop
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-paynow-payment-method-for-computop.html
-  - title: Integrating the Direct Debit payment method for Computop
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-direct-debit-payment-method-for-computop.html
-  - title: Integrating the iDeal payment method for Computop
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-ideal-payment-method-for-computop.html
-  - title: Integrating the Сredit Сard payment method for Computop
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-credit-card-payment-method-for-computop.html
-  - title: Integrating the Easy Credit payment method for Computop
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-easy-credit-payment-method-for-computop.html
-  - title: Integrating the Paydirekt payment method for Computop
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-paydirekt-payment-method-for-computop.html
-  - title: Integrating the CRIF payment method for Computop
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-crif-payment-method-for-computop.html
----
-
-## Partner Information
-
-[Computop](https://www.computop.com/de/) is a leading international Payment Service Provider that enables merchants and white label customers to process global multichannel payments. Computop’s state of the art and wholly owned payment platform Computop Paygate offers seamless solutions for mobile, online and in store payment transactions. All transactions processed by Computop Paygate are secure as our platform is PCI certified.
-
-Computop offers a global payment management solution that is connected to over 350 payment methods and acquirer connections worldwide, customizable fraud prevention, tokenization and other value added services like currency conversion and debt management that result in secure transaction processing and higher conversion rates.
-
-Paygate is scalable and favoured by merchants in the travel, gaming, gambling, digital, hospitality, and the retail industry. Prebuilt payment and fraud management integration cartridges or modules are available for leading ERP and shop system solutions including demandware, hybris, intershop, Magento, and IBM Websphere.
-
-Founded in 1997, Computop is a global player for the 21st century. Headquartered in Bamberg, Germany, the company has sales operations in New York, London, and Shanghai. Computop is trusted by the largest global brands worldwide including Samsung, The Otto Group, C&A, Fossil, Metro Cash & Carry, and Swarovski.
-
-The Computop payment partner is shipped with the following payment methods:
-
-* Credit Card
-* Direct Debit
-* EasyCredit
-* iDeal
-* Paydirekt
-* PayNow
-* PayPal
-* SofortÜberweisung
-* PayU CEE Single
-* PayPal Express
-
-### PSD2 compatibility
-
-Computop PSP integration supports PSD2. For CreditCard and PayNow payment methods, customer address and additional information is sent to Computop to prevent fraud actions.
-
-### Notifications
-
-Push notifications speed up order placement process for customers. They allow to place orders regardless of the authorization of cards or money transfer for payment methods such as Sofortüberweisung or IDeal. After a customer places an order, they are redirected to the checkout success page. When authorization or money transfer is complete, Computop notifies the shop via a push notification. Order status is updated according to the push notification and the order moves forward in the state machine.
-
-## Related Developer guides
-
-* [Installing and configuring Computop](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/computop/installing-and-configuring-computop.html)
-* [Integrating Computop](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/computop/integrating-computop.html)
-* [Computop API calls](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/computop/computop-api-calls.html)
-* [Computop - OMS plugins](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/computop/computop-oms-plugins.html)
-* [Integrating the Сredit Сard payment method for Computop](/docs/scos/dev/technology-partner-guides/202108.0/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-credit-card-payment-method-for-computop.html)
-* [Integrating the CRIF payment method for Computop](/docs/scos/dev/technology-partner-guides/202108.0/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-crif-payment-method-for-computop.html)
-* [Integrating the Direct Debit payment method for Computop](/docs/scos/dev/technology-partner-guides/202108.0/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-direct-debit-payment-method-for-computop.html)
-* [Integrating the Easy Credit payment method for Computop](/docs/scos/dev/technology-partner-guides/202108.0/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-easy-credit-payment-method-for-computop.html)
-* [Integrating the iDeal payment method for Computop](/docs/scos/dev/technology-partner-guides/202108.0/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-ideal-payment-method-for-computop.html)
-* [Integrating the Paydirekt payment method for Computop](/docs/scos/dev/technology-partner-guides/202108.0/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-paydirekt-payment-method-for-computop.html)
-* [Integrating the PayNow payment method for Computop](/docs/scos/dev/technology-partner-guides/202108.0/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-paynow-payment-method-for-computop.html)
-* [Integrating the PayPal payment method for Computop  ](/docs/scos/dev/technology-partner-guides/202108.0/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-paypal-payment-method-for-computop.html)
-* [Integrating the Sofort payment method for Computop](/docs/scos/dev/technology-partner-guides/202108.0/payment-partners/computop/integrating-payment-methods-for-computop/integrating-the-sofort-payment-method-for-computop.html)
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/crefopay.md b/docs/scos/user/technology-partners/202204.0/payment-partners/crefopay.md
deleted file mode 100644
index 98a82f91d1a..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/crefopay.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: CrefoPay
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/crefopay
-originalArticleId: 136e996b-06c7-46f2-a417-b66a45c84726
-redirect_from:
-  - /2021080/docs/crefopay
-  - /2021080/docs/en/crefopay
-  - /docs/crefopay
-  - /docs/en/crefopay
----
-
-
-Creditreform has more than 130 years of experience in risk and collections management. The 125,000 Creditreform customers include leading corporations from all industries, as well as small and medium-sized businesses.
-
-Since our founding in 1879, our goal has always been to protect our customers against bad debt, which can destroy liquidity and jeopardize the survival of their companies. This is the precept of all solutions and services offered by Creditreform.
-
-The services available on the unique CrefoPay platform offered by CrefoPayment GmbH & Co. KG combine all steps within the payment process, from risk evaluation to payment processing and monitoring all the way to the collection of overdue receivables. CrefoPay not only offers customers access to an individual solution for making purchases on account (invoice), they can also educate themselves about all relevant figures via an interface and benefit of additional services specifically designed for B2B business.
-
-## Related Developer guides
-
-To integrate CrefoPay into your system the see following articles:
-* [Installing and configuring CrefoPay](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/crefopay/installing-and-configuring-crefopay.html)
-* [Integrating CrefoPay](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/crefopay/integrating-crefopay.html)
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/heidelpay.md b/docs/scos/user/technology-partners/202204.0/payment-partners/heidelpay.md
deleted file mode 100644
index 7014b8d24a9..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/heidelpay.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Heidelpay
-description: Heidelpay is an internationally operating payment institution, authorized and regulated by the Federal Financial Supervisory Authority.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/heidelpay
-originalArticleId: 92607b28-3e51-4b0a-a41f-12bc9852b1cb
-redirect_from:
-  - /2021080/docs/heidelpay
-  - /2021080/docs/en/heidelpay
-  - /docs/heidelpay
-  - /docs/en/heidelpay
----
-
-## Partner Information
-
-[ABOUT HEIDELPAY](https://www.heidelpay.de/)
-
-Heidelpay is an internationally operating payment institution, authorized and regulated by the Federal Financial Supervisory Authority. The Full-Service Payment Provider covers the entire range of services connected to international electronic payment processing. For more than 13 years the company has been successfully realizing projects of online and stationary retailers and currently serves more than 16.000 customers in many different industrial sectors worldwide.
-
-## Related Developer guides
-
-* [Installing Heidelpay](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/heidelpay/installing-heidelpay.html)
-* [Integrating Heidelpay](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/heidelpay/integrating-heidelpay.html)
-* [Configuring Heidelpay](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/heidelpay/configuring-heidelpay.html)
-* [Heidelpay OMS workflow](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/heidelpay/heidelpay-oms-workflow.html)
-* [Heidelpay workflow for errors](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/heidelpay/heidelpay-workflow-for-errors.html)
-* [Integrating the Credit Card Secure payment method for Heidelpay](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/heidelpay/integrating-payment-methods-for-heidelpay/integrating-the-credit-card-secure-payment-method-for-heidelpay.html)
-* [Integrating the Direct Debit payment method for Heidelpay](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/heidelpay/integrating-payment-methods-for-heidelpay/integrating-the-direct-debit-payment-method-for-heidelpay.html)
-* [Integrating the Easy Credit payment method for Heidelpay](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/heidelpay/integrating-payment-methods-for-heidelpay/integrating-the-easy-credit-payment-method-for-heidelpay.html)
-* [Integrating the iDeal payment method for Heidelpay](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/heidelpay/integrating-payment-methods-for-heidelpay/integrating-the-ideal-payment-method-for-heidelpay.html)
-* [Integrating the Invoice Secured B2C payment method for Heidelpay](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/heidelpay/integrating-payment-methods-for-heidelpay/integrating-the-invoice-secured-b2c-payment-method-for-heidelpay.html)
-* [Integrating the Paypal Authorize payment method for Heidelpay](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/heidelpay/integrating-payment-methods-for-heidelpay/integrating-the-paypal-authorize-payment-method-for-heidelpay.html)
-* [Integrating the Paypal Debit payment method for Heidelpay](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/heidelpay/integrating-payment-methods-for-heidelpay/integrating-the-paypal-debit-payment-method-for-heidelpay.html)
-* [Integrating the Sofort payment method for Heidelpay](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/heidelpay/integrating-payment-methods-for-heidelpay/integrating-the-sofort-payment-method-for-heidelpay.html)
-* [Integrating the Split-payment Marketplace payment method for Heidelpay](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/heidelpay/integrating-payment-methods-for-heidelpay/integrating-the-split-payment-marketplace-payment-method-for-heidelpay.html)
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/klarna.md b/docs/scos/user/technology-partners/202204.0/payment-partners/klarna.md
deleted file mode 100644
index 0467474d2b2..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/klarna.md
+++ /dev/null
@@ -1,79 +0,0 @@
----
-title: Klarna
-description: Make paying as simple, safe and above all, smooth as possible by integrating the Klarna payment into the Spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/klarna
-originalArticleId: 19d4dba2-c122-4a37-8170-e8ad49b71821
-redirect_from:
-  - /2021080/docs/klarna
-  - /2021080/docs/en/klarna
-  - /docs/klarna
-  - /docs/en/klarna
-related:
-  - title: Klarna payment workflow
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/klarna/klarna-payment-workflow.html
-  - title: Klarna - Invoice Pay in 14 days
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/klarna/klarna-invoice-pay-in-14-days.html
-  - title: Klarna - Part Payment Flexible
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/klarna/klarna-part-payment-flexible.html
-  - title: Klarna state machine commands and conditions
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/klarna/klarna-state-machine-commands-and-conditions.html
----
-
-## Partner Information
-
-[ABOUT KLARNA](https://www.klarna.com/de/)
-
-Klarna was founded in 2005 in Stockholm, Sweden with the aim of making it easier for people to shop online. In the last 12 years, technology has evolved, excited and transformed the world around us, yet our mission remains as relevant as ever, to make paying as simple, safe and above all, smooth as possible.Klarna is now one of Europe's largest banks and is providing payment solutions for 60 million consumers across 70,000 merchants in 18 countries. Klarna offers direct payments, pay after delivery options and installment plans in a smooth one-click purchase experience that lets consumers pay when and how they prefer to.When the company acquired SOFORT in 2014 the Klarna Group was formed.
-
-YOUR ADVANTAGES:
-* With Invoice:  With Installments increase of conversion rates and high acceptance rates  higher baskets and less cancellations easy and secure customer experience for shoppers  direct Direkter shipping thanks to real time-check offer germany´s most popular payment methods guaranteed payout to merchants .
-* Klarna is even cheaper than an inhouse solution.
-* Merchants never take over the risk and always receive their money.
-* Merchants never take over the risk and always receive their money.
-
-### Klarna Invoice
-
-The option to pay after delivery makes buying quicker and easier for customers. With Klarna's Pay Later, shoppers do not need to fill out lengthy personal details or enter card numbers at the online point of sale. The transaction can be completed with only name, email and address. Consumer then have 14 days to pay the invoice.
-
-### Deferred Payment Purchase
-
-Your customers can spread the cost of their purchases over time, at a low interest rate, giving them flexibility and increased purchasing power, which in turn boosts sales. Our unique 4-step credit application process is quick and easy, requiring minimal information and taking just seconds to complete.
-
-Our technology-driven underwriting system makes decisions in real time, and offers smart risk assessment. It allow us to accept more purchases, so you sell more. And even if a customer defaults, you still get paid: we take all the risk.
-
-<!---
-## DRAFT NOTE: THIS INFO IS HIDDEN TILL WE HAVE FINAL APPROVAL FROM KLARNA AND THE DEVELOPMENT IS COMPLETED.
-
-The Klarna module provides two methods of payment:
-
-1. [Part Payment – Flexible - Klarna](klarna-part-payment-flexible.htm)
-2. [Invoice – Pay in 14 days - Klarna](klarna-invoice-pay-in-14-days.htm)
-
-To Integrate Klarna payments, create and configure a Klarna merchant account.
-
-We use state machines for handling and managing orders and payments. To integrate Klarna payments, a dedicated state machine should be created.
-
-A basic and fully functional state machine is already available (KlarnaPayment01). You can use the same state machine or build a new one. In case a new state machine needs to be built, it is preferred to contact Klarna and confirm the new state machine design and functionality.
-
-The [Klarna State Machine Commands and Conditions](klarna-state-machine.htm) trigger the operations exposed by the KlarnaFacade in order to perform the needed requests to Klarna.
--->
-
-## Related Developer guides
-
-* [Klarna - Invoice Pay in 14 days](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/klarna/klarna-invoice-pay-in-14-days.html)
-* [Klarna - Part Payment Flexible](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/klarna/klarna-part-payment-flexible.html)
-* [Klarna payment workflow](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/klarna/klarna-payment-workflow.html)
-* [Klarna state machine commands and conditions](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/klarna/klarna-state-machine-commands-and-conditions.html)
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/payolution.md b/docs/scos/user/technology-partners/202204.0/payment-partners/payolution.md
deleted file mode 100644
index c100d0abc2d..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/payolution.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: Payolution
-description: Provide invoice, installment, monthly invoice, and direct debit solutions by integrating Payolution into the Spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/payolution
-originalArticleId: 4d4f59ce-7e96-42af-a61d-c23df33d1205
-redirect_from:
-  - /2021080/docs/payolution
-  - /2021080/docs/en/payolution
-  - /docs/payolution
-  - /docs/en/payolution
-related:
-  - title: Installing and configuring Payolution
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/payolution/installing-and-configuring-payolution.html
-  - title: Integrating Payolution
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/payolution/integrating-payolution.html
-  - title: Payolution - Performing Requests
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/payolution/payolution-performing-requests.html
-  - title: Payolution request flow
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/payolution/payolution-request-flow.html
-  - title: Integrating the installment payment method for Payolution
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/payolution/integrating-the-installment-payment-method-for-payolution.html
-  - title: Integrating the invoice paymnet method for Payolution
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/payolution/integrating-the-invoice-payment-method-for-payolution.html
----
-
-## Partner Information
-
-[ABOUT PAYOLUTION](https://www.payolution.com/)
-
-Payolution offers white label solutions for the payment options — invoice, instalment, monthly invoice, and direct debit — available in Austria, Germany, Switzerland, the Netherlands, and the United Kingdom. As a mid-sized merchant or a global brand, you will benefit from Payolution's expertise in a seamless omni-channel integration of these payment options. Payolution offers a 100% payment guarantee — they pay you regardless when or if your customer pays you. Payolution's white label approach focuses on you as a merchant, your brand, your conversion and a fair customer support.
-
-Payolution provides two methods of payment:
-* Invoice
-* Installment
-
-In order to integrate Payolution payments, a Payolution merchant account should be created and configuration data then could be obtained from Payolution. There are two types of accounts for the integration: test and live. Both accounts share the same configuration with different values. Payolution uses the idea of having channels for handling different requests. Each channel is specified by a channel ID which will be given by Payolution.
-
-We use state machines for handling and managing orders and payments. To integrate Payolution payments, a state machine for Payolution should be created. A basic and fully functional state machine is already built (`PayolutionPayment01`). You can use the same state machine or build a new one. In case a new state machine has to be built, it is preferred to contact Payolution and confirm the new state machine design and functionality.
-
-The state machine commands and conditions trigger Payolution facade calls in order to perform the needed requests to Payolution. For simplicity, the Payolution facade uses the same calls for both invoice and installment payments and distinguishes the payment method automatically from the payment entity.
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/powerpay.md b/docs/scos/user/technology-partners/202204.0/payment-partners/powerpay.md
deleted file mode 100644
index 3e65f759e03..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/powerpay.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Powerpay
-description: Deliver results for your merchants by integrating Powerpay into the Spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/powerpay
-originalArticleId: f6d0bdfc-6145-4e9f-b2b6-51509e16713c
-redirect_from:
-  - /2021080/docs/powerpay
-  - /2021080/docs/en/powerpay
-  - /docs/powerpay
-  - /docs/en/powerpay
-related:
-  - title: Technology Partner Integration
-    link: docs/scos/user/technology-partners/page.version/technology-partners.html
----
-
-## Payment Information
-
-[ABOUT POWERPAY](https://getpowerpay.com/)
-
-Omni-channel payment solutions for the 21st century, powerpay21, is a Global FinTech Network that provides payment products and solutions for merchants whether offline or online.
-We gained worldwide payments expertise that delivers results for our merchants. From delivering omni-channel payment solutions to controlling risk and fraud to delivering higher conversion ratios, businesses across the world have trusted us and have benefited from our merchant solutions. powerpay21 is committed to outstanding service, out-of-the box solutions and long-lasting relationships.
-
-**Acquiring through powercash21:**
-<br>Operating as a Payments Institution with a license granted by the Central Bank of Cyprus. (Company No: HE289380; License No: 115.1.2.9/2018) (https://www.centralbank.cy/) Principal member of Visa and MasterCard Certified on the Omnipay platform for card present and card not present.
-
-**Prepaid debit cards via powercard21 – both Visa and MasterCard:**
-<br>Boutique prepaid issuing programs, White labelled programs and a Bespoke Bank Management Suite (BMS) providing financial institutions, customer service and program administrators with a comprehensive online suite of functions and reports.
-
-**Mobile Point of Sale solutions through mPOS21:**
-<br>mPOS21 allows businesses to maximize their sales by accepting credit and debit cards on the go mPOS21 uses a MIURA card reader / PIN pad that connects via Bluetooth to a mobile phone. A customized mPOS21 app is available for Android and iOS, allowing Visa and MasterCard Chip and Pin card present transactions.
-
-YOUR ADVANTAGES:
-* Omni-channel merchant payment solutions: Whether it's payments online, in-person or over the phone
-* Global and localized payment solutions
-* Advanced Risk and Fraud Management
-* Superior reporting tools
-* PCI-DSS Level 1 Certified gateway for data security
-* Commitment to outstanding service
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/ratenkauf-by-easycredit.md b/docs/scos/user/technology-partners/202204.0/payment-partners/ratenkauf-by-easycredit.md
deleted file mode 100644
index 8c442068e88..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/ratenkauf-by-easycredit.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: ratenkauf by easyCredit
-description: Offer a simple and standardized solution for e-commerce and for the point of sale by integrating ratenkauf by easyCredit into the Spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/ratenkauf-by-easycredit
-originalArticleId: 86cf0b54-43b8-4585-adef-0245c01e702a
-redirect_from:
-  - /2021080/docs/ratenkauf-by-easycredit
-  - /2021080/docs/en/ratenkauf-by-easycredit
-  - /docs/ratenkauf-by-easycredit
-  - /docs/en/ratenkauf-by-easycredit
-related:
-  - title: Installing and configuring ratenkauf by easyCredit
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/ratenkauf-by-easycredit/installing-and-configuring-ratenkauf-by-easycredit.html
-  - title: Integrating ratenkauf by easyCredit
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/ratenkauf-by-easycredit/integrating-ratenkauf-by-easycredit.html
----
-
-## Partner Information
-
-[ABOUT RATENKAUF](https://www.easycredit-ratenkauf.de/)
-
-Germany’s easiest installment purchase solution ratenkauf by easyCredit is the first payment option to offer a simple and standardized solution for e-commerce and for the point of sale.
-
-TeamBank, with its easyCredit product family, is the liquidity management specialist in the Volksbanken Raiffeisenbanken cooperative financial network. Its ‘ratenkauf by easyCredit’ product is the first installment purchase solution that combines a simple and uniformly designed installment purchase function both for e-commerce and for a physical point of sale. Customers can make their ratenkauf by easyCredit installment purchase in just three steps. No paperwork, immediate approval, and complete flexibility throughout. Simple. Fair.
-
-YOUR ADVANTAGES:
-* Revenue booster: more revenue due to higher purchase amounts.
-* Profitable: fewer purchase cancellations thanks to the immediate credit check and approval.
-* Safe: no payment defaults as TeamBank assumes the credit risk.
-* Fair: excellent easyCredit processes offer transparency and flexibility for customers.
-
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/payment-partners/ratepay.md b/docs/scos/user/technology-partners/202204.0/payment-partners/ratepay.md
deleted file mode 100644
index 0181f016bb1..00000000000
--- a/docs/scos/user/technology-partners/202204.0/payment-partners/ratepay.md
+++ /dev/null
@@ -1,79 +0,0 @@
----
-title: RatePay
-description: Offer intelligent payment solutions for handling most popular paylater models like invoice and installments on the internet for the DACH region by integrating RatePay into the Spryker-based shop.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/ratepay
-originalArticleId: 76f600d9-1b7f-4a0a-81e6-4c2dc466063c
-redirect_from:
-  - /2021080/docs/ratepay
-  - /2021080/docs/en/ratepay
-  - /docs/ratepay
-  - /docs/en/ratepay
-related:
-  - title: Integrating the Invoice payment method for RatePay
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/ratepay/integrating-payment-methods-for-ratepay//integrating-the-invoice-payment-method-for-ratepay.html
-  - title: RatePay facade methods
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/ratepay/ratepay-facade-methods.html
-  - title: Integrating the Prepayment payment method for RatePay
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/ratepay/integrating-payment-methods-for-ratepay//integrating-the-prepayment-payment-method-for-ratepay.html
-  - title: RatePay - Payment Workflow
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/ratepay/ratepay-payment-workflow.html
-  - title: RatePay - How to Disable Address Updates from the Backend Application
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/ratepay/disabling-address-updates-from-the-backend-application-for-ratepay.html
-  - title: RatePay - Core Module Structure Diagram
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/ratepay/ratepay-core-module-structure-diagram.html
-  - title: Integrating the Installment payment method for RatePay
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/ratepay/integrating-payment-methods-for-ratepay//integrating-the-installment-payment-method-for-ratepay.html
-  - title: Integrating the Direct Debit payment method for RatePay
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/ratepay/integrating-payment-methods-for-ratepay/integrating-the-direct-debit-payment-method-for-ratepay.html
-  - title: RatePay - State Machine Commands and Conditions
-    link: docs/scos/dev/technology-partner-guides/page.version/payment-partners/ratepay/ratepay-state-machine-commands-and-conditions.html
----
-
-## Partner Information
-
-[ABOUT RatePAY](https://www.ratepay.com/)
-
-RatePAY is a German Fintech company that offers intelligent payment solutions with 100% loss protection for the handling of the most popular paylater models like invoice and instalments on the internet for the DACH region. Our easy payment methods are among the most popular payment solutions in Germany. One of the reasons lies in the flexibility of our products, since the customer pays only for the goods he decides to keep. As one of only a few payment service companies, RatePAY has been granted a license under the German Payment Services Oversight Act (ZAG) by the Federal Financial Supervisory Authority (BaFin) and is now able to offer customers an even more comprehensive service. Founded in December 2009, the start-up from Berlin has developed itself into a profitable company with more than 140 employees. In April 2017, RatePAY was acquired by the investors Advent International and Bain Capital.
-
-YOUR ADVANTAGES:
-* Complete solutions for unsecured methods of payment as invoice, instalments, direct debit and prepayment
-* White label solution
-* B2B and B2C customers
-* Risk and customer management, customer service
-* Individual service packages for large online retailers
-* No hidden charges for buyers and traders
-* Continuous development of innovative features
-* Seamless integration
-
-RatePAY is an online service provider that allows merchants to provide their customers secure, customized payment methods. It bears the full risk and takes over the complete processing.
-
-RatePAY provides four methods of payment
-* Invoice
-* Prepayment
-* Direct Debit (ELV)
-* Installment
-
-## Related Developer guides
-
-* [RatePay Core module structure diagram](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/ratepay/ratepay-core-module-structure-diagram.html)
-* [RatePay state machines](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/ratepay/ratepay-state-machines.html)
-* [Integrating the Direct Debit payment method for RatePay](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/ratepay/integrating-payment-methods-for-ratepay/integrating-the-direct-debit-payment-method-for-ratepay.html)
-* [Integrating the Installment payment method for RatePay](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/ratepay/integrating-payment-methods-for-ratepay//integrating-the-installment-payment-method-for-ratepay.html)
-* [Integrating the Invoice payment method for RatePay](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/ratepay/integrating-payment-methods-for-ratepay//integrating-the-invoice-payment-method-for-ratepay.html)
-* [Integrating the Prepayment payment method for RatePay](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/ratepay/integrating-payment-methods-for-ratepay//integrating-the-prepayment-payment-method-for-ratepay.html)
-* [Disabling address updates from the backend application for RatePay](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/ratepay/disabling-address-updates-from-the-backend-application-for-ratepay.html)
-* [RatePay facade methods](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/ratepay/ratepay-facade-methods.html)
-* [RatePay payment workflow](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/ratepay/ratepay-payment-workflow.html)
-* [RatePay state machine commands and conditions](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/ratepay/ratepay-state-machine-commands-and-conditions.html)
----
-
-## Copyright and Disclaimer
-
-See [Disclaimer](https://github.com/spryker/spryker-documentation).
-
----
-For further information on this partner and integration into Spryker, please contact us.
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="163e11fb-e833-4638-86ae-a2ca4b929a41" id="hubspot-1"></div>
diff --git a/docs/scos/user/technology-partners/202204.0/technology-partners.md b/docs/scos/user/technology-partners/202204.0/technology-partners.md
deleted file mode 100644
index c6329075b2d..00000000000
--- a/docs/scos/user/technology-partners/202204.0/technology-partners.md
+++ /dev/null
@@ -1,122 +0,0 @@
----
-title: Technology partners
-description: Technology partner solutions to boost your Spryker project performance.
-last_updated: Sep 7, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/technology-partner-integration
-originalArticleId: d4b53f3f-475e-4e02-aa21-79db417a1325
-redirect_from:
-  - /2021080/docs/technology-partner-integration
-  - /2021080/docs/en/technology-partner-integration
-  - /docs/technology-partner-integration
-  - /docs/en/technology-partner-integration
-  - /2021080/docs/payment-provider-integration-guide
-  - /2021080/docs/en/payment-provider-integration-guide
-  - /docs/payment-provider-integration-guide
-  - /docs/en/payment-provider-integration-guide
-  - /docs/scos/user/technology-partners/202200.0/technology-partners.html
----
-
-In this section you will find information about our Technology Partner Integration solutions.
-
-Visit [Technology Partners](https://spryker.com/technology-partners/) for a complete list of our partners.
-
-##  Hosting Providers
-
-* [Claranet](/docs/scos/user/technology-partners/{{page.version}}/hosting-providers/claranet.html)
-* [Continum](/docs/scos/user/technology-partners/{{page.version}}/hosting-providers/continum.html)
-* [Metaways](/docs/scos/user/technology-partners/{{page.version}}/hosting-providers/metaways.html)
-* [root360](/docs/scos/user/technology-partners/{{page.version}}/hosting-providers/root-360.html)
-
-
-## Content Management
-
-* [Coremedia](/docs/pbc/all/content-management-system/{{page.version}}/base-shop/third-party-integrations/coremedia.html)
-* [E-Spirit](/docs/pbc/all/content-management-system/{{page.version}}/base-shop/third-party-integrations/e-spirit.html)
-* [Magnolia](/docs/pbc/all/content-management-system/{{page.version}}/base-shop/third-party-integrations/magnolia.html)
-* [Styla](/docs/pbc/all/content-management-system/{{page.version}}/base-shop/third-party-integrations/styla.html)
-
-## Customer Service
-
-* [Dixa](/docs/scos/user/technology-partners/{{page.version}}/customer-service/dixa.html)
-* [iAdvize](/docs/scos/user/technology-partners/{{page.version}}/customer-service/iadvize.html)
-* [Optimise it](/docs/scos/user/technology-partners/{{page.version}}/customer-service/optimise-it.html)
-* [Live chat service](/docs/scos/user/technology-partners/{{page.version}}/customer-service/live-chat-service.html)
-
-## Finance & Accounting
-
-* [CollectAI](/docs/scos/user/technology-partners/{{page.version}}/finance-and-accounting/collectai.html)
-* [Nitrobox](/docs/scos/user/technology-partners/{{page.version}}/finance-and-accounting/nitrobox.html)
-
-## A/B Testing & Performance
-
-* [AB Tasty](/docs/scos/user/technology-partners/{{page.version}}/marketing-and-conversion/ab-testing-and-performance/ab-tasty.html)
-<!--* [Baqend](/docs/scos/user/technology-partners/{{page.version}}/marketing-and-conversion/ab-testing-and-performance/baqend.html)-->
-
-## Analytics
-
-* [ChannelPilot Analytics](/docs/scos/user/technology-partners/{{page.version}}/marketing-and-conversion/analytics/channelpilot-analytics.html)
-* [FactFinder](/docs/scos/user/technology-partners/{{page.version}}/marketing-and-conversion/analytics/fact-finder.html)
-* [Haensel AMS](/docs/scos/user/technology-partners/{{page.version}}/marketing-and-conversion/analytics/haensel-ams.html)
-* [Mindlab](/docs/scos/user/technology-partners/{{page.version}}/marketing-and-conversion/analytics/mindlab.html)
-* [Minubo](/docs/scos/user/technology-partners/{{page.version}}/marketing-and-conversion/analytics/minubo.html)
-
-## Customer Communication
-
-* [Dotdigital](/docs/scos/user/technology-partners/{{page.version}}/marketing-and-conversion/customer-communication/dotdigital.html)
-* [Episerver](/docs/scos/user/technology-partners/{{page.version}}/marketing-and-conversion/customer-communication/episerver.html)
-* [Inxmail](/docs/scos/user/technology-partners/{{page.version}}/marketing-and-conversion/customer-communication/inxmail.html)
-
-## Customer Retention & Loyalty
-
-* [Namogoo](/docs/scos/user/technology-partners/{{page.version}}/marketing-and-conversion/customer-retention-and-loyalty/namogoo.html)
-* [Trustpilot](/docs/scos/user/technology-partners/{{page.version}}/marketing-and-conversion/customer-retention-and-loyalty/trustpilot.html)
-* [Zenloop](/docs/scos/user/technology-partners/{{page.version}}/marketing-and-conversion/customer-retention-and-loyalty/zenloop.html)
-
-## Personalization & Cross-Selling
-
-<!--* [8Select](/docs/scos/user/technology-partners/{{page.version}}/marketing-and-conversion/personalization-and-cross-selling/8select.html)-->
-* [Econda](/docs/scos/user/technology-partners/{{page.version}}/marketing-and-conversion/personalization-and-cross-selling/econda.html)
-* [Nosto](/docs/scos/user/technology-partners/{{page.version}}/marketing-and-conversion/personalization-and-cross-selling/nosto.html)
-* [trbo](/docs/scos/user/technology-partners/{{page.version}}/marketing-and-conversion/personalization-and-cross-selling/trbo.html)
-
-## Marketplace Integrations
-
-* [ChannelPilot Marketplace](/docs/scos/user/technology-partners/{{page.version}}/marketplace-integrations/channelpilot-marketplace.html)
-
-## Order Management (ERP/OMS)
-
-* [Tradebyte](/docs/scos/user/technology-partners/{{page.version}}/order-management-erpoms/tradebyte.html)
-
-## Operational Tools
-
-<!--* [Common Solutions](/docs/scos/user/technology-partners/{{page.version}}/operational-tools-monitoring-legal-etc/common-solutions.html)-->
-* [Data Virtuality](/docs/scos/user/technology-partners/{{page.version}}/operational-tools-monitoring-legal-etc/data-virtuality.html)
-* [Loggly](/docs/scos/user/technology-partners/{{page.version}}/operational-tools-monitoring-legal-etc/loggly.html)
-* [New Relic](/docs/scos/user/technology-partners/{{page.version}}/operational-tools-monitoring-legal-etc/new-relic.html)
-* [Proclane](/docs/scos/user/technology-partners/{{page.version}}/operational-tools-monitoring-legal-etc/proclane.html)
-* [PlusServer](/docs/scos/user/technology-partners/{{page.version}}/operational-tools-monitoring-legal-etc/plusserver.html)
-* [Tideways](/docs/scos/user/technology-partners/{{page.version}}/operational-tools-monitoring-legal-etc/tideways.html)
-* [Usercentrics](/docs/scos/user/technology-partners/{{page.version}}/operational-tools-monitoring-legal-etc/usercentrics.html)
-* [VSHN](/docs/scos/user/technology-partners/{{page.version}}/operational-tools-monitoring-legal-etc/vshn.html)
-<!--* [Mindcurv](/docs/scos/user/technology-partners/{{page.version}}/operational-tools-monitoring-legal-etc/mindcurv.html)-->
-<!--* [Shopmacher](/docs/scos/user/technology-partners/{{page.version}}/operational-tools-monitoring-legal-etc/shopmacher.html)-->
-
-## Payment Partners
-
-* [Adyen](/docs/scos/user/technology-partners/{{page.version}}/payment-partners/adyen.html)
-* [Amazon Pay](/docs/scos/user/technology-partners/{{page.version}}/payment-partners/amazon-pay.html)
-* [AfterPay](/docs/scos/user/technology-partners/{{page.version}}/payment-partners/afterpay.html)
-* [Arvato](/docs/scos/user/technology-partners/{{page.version}}/payment-partners/arvato.html)
-* [Billie](/docs/scos/user/technology-partners/{{page.version}}/payment-partners/billie.html)
-* [Billpay](/docs/scos/user/technology-partners/{{page.version}}/payment-partners/billpay.html)
-* [Braintree](/docs/scos/user/technology-partners/{{page.version}}/payment-partners/braintree.html)
-* [BS Payone](/docs/scos/user/technology-partners/{{page.version}}/payment-partners/bs-payone/bs-payone.html)
-* [Computop](/docs/scos/user/technology-partners/{{page.version}}/payment-partners/computop.html)
-* [CrefoPay](/docs/scos/dev/technology-partner-guides/{{page.version}}/payment-partners/crefopay/installing-and-configuring-crefopay.html)
-* [Heidelpay](/docs/scos/user/technology-partners/{{page.version}}/payment-partners/heidelpay.html)
-* [Klarna](/docs/scos/user/technology-partners/{{page.version}}/payment-partners/klarna.html)
-* [Payone](/docs/scos/user/technology-partners/{{page.version}}/payment-partners/payolution.html)
-* [Powerpay](/docs/scos/user/technology-partners/{{page.version}}/payment-partners/powerpay.html)
-* [ratenkauf by easyCredit](/docs/scos/user/technology-partners/{{page.version}}/payment-partners/ratenkauf-by-easycredit.html)
-* [RatePAY](/docs/scos/user/technology-partners/{{page.version}}/payment-partners/ratepay.html)

From 144f4e9d3c65c7dd86fc49f019e2201a31d444fe Mon Sep 17 00:00:00 2001
From: Andrii Tserkovnyi <andrii.tserkovnyi@spryker.com>
Date: Mon, 4 Mar 2024 11:33:28 +0200
Subject: [PATCH 02/26] move docs

---
 _data/sidebars/about_all_sidebar.yml          | 948 ------------------
 _data/sidebars/dg_dev_sidebar.yml             |   9 +
 docs/about/all/faq.md                         |  30 +-
 docs/about/all/mvp-project-structuring.md     |  18 +-
 docs/about/all/spryker-academy.md             | 162 +--
 docs/{about/all => dg/dev}/b2b-suite.md       |  17 +-
 docs/{about/all => dg/dev}/b2c-suite.md       |   0
 docs/{about/all => dg/dev}/master-suite.md    |  22 +-
 .../dev/product-and-code-releases.md}         |  19 +-
 9 files changed, 28 insertions(+), 1197 deletions(-)
 rename docs/{about/all => dg/dev}/b2b-suite.md (94%)
 rename docs/{about/all => dg/dev}/b2c-suite.md (100%)
 rename docs/{about/all => dg/dev}/master-suite.md (65%)
 rename docs/{about/all/spryker-release-process.md => dg/dev/product-and-code-releases.md} (68%)

diff --git a/_data/sidebars/about_all_sidebar.yml b/_data/sidebars/about_all_sidebar.yml
index 603539a00eb..0e2a01cda39 100644
--- a/_data/sidebars/about_all_sidebar.yml
+++ b/_data/sidebars/about_all_sidebar.yml
@@ -93,12 +93,6 @@ entries:
         url: /docs/scos/user/intro-to-spryker/support/understanding-project-and-core-level-fixes.html
     - title: FAQ
       url: /docs/scos/user/intro-to-spryker/faq.html
-    - title: B2C Suite
-      url: /docs/scos/user/intro-to-spryker/b2c-suite.html
-    - title: B2B Suite
-      url: /docs/scos/user/intro-to-spryker/b2b-suite.html
-    - title: Master Suite
-      url: /docs/scos/user/intro-to-spryker/master-suite.html
     - title: Supported browsers
       url: /docs/scos/user/intro-to-spryker/supported-browsers.html
     - title: Spryker Marketplace
@@ -121,8 +115,6 @@ entries:
       - title: Marketplace B2B Suite
         url: /docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2b-suite.html
 
-    - title: Spryker release process
-      url: /docs/scos/user/intro-to-spryker/spryker-release-process.html
     - title: MVP project structuring
       url: /docs/scos/user/intro-to-spryker/mvp-project-structuring.html
     - title: Spryker Academy
@@ -160,946 +152,6 @@ entries:
         url: /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/review-pull-requests.html
       - title: Add product sections to the documentation
         url: /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
-  - title: Features
-    url: /docs/scos/user/features/features.html
-    include_versions:
-    - "201903.0"
-    - "201907.0"
-    - "202001.0"
-    - "202005.0"
-    - "202009.0"
-    - "202108.0"
-    - "202204.0"
-    nested:
-    - title: Company Account
-      url: /docs/scos/user/features/company-account-feature-overview/company-account-feature-overview.html
-      include_versions:
-      - "201907.0"
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-      nested:
-      - title: Company accounts
-        url: /docs/scos/user/features/company-account-feature-overview/company-accounts-overview.html
-      - title: Business units
-        url: /docs/scos/user/features/company-account-feature-overview/business-units-overview.html
-      - title: Company user roles and permissions
-        url: /docs/scos/user/features/company-account-feature-overview/company-user-roles-and-permissions-overview.html
-      - title: Customer login by token
-        url: /docs/scos/user/features/company-account-feature-overview/customer-login-by-token-overview.html
-        include_versions:
-        - "201907.0"
-        - "202001.0"
-        - "202005.0"
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-        - "202212.0"
-        - "202307.0"
-      - title: Business on behalf
-        url: /docs/scos/user/features/company-account-feature-overview/business-on-behalf-overview.html
-        include_versions:
-        - "201903.0"
-        - "201907.0"
-        - "202001.0"
-        - "202005.0"
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-        - "202212.0"
-        - "202307.0"
-
-    - title: Customer Access
-      url: /docs/scos/user/features/customer-access-feature-overview.html
-      include_versions:
-      - "201907.0"
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-    - title: Customer Account Management
-      url: /docs/scos/user/features/customer-account-management-feature-overview/customer-account-management-feature-overview.html
-      include_versions:
-      - "201907.0"
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-      nested:
-      - title: Customer Accounts
-        url: /docs/scos/user/features/customer-account-management-feature-overview/customer-accounts-overview.html
-        include_versions:
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-        - "202212.0"
-        - "202307.0"
-      - title: Customer registration
-        url: /docs/scos/user/features/customer-account-management-feature-overview/customer-registration-overview.html
-        include_versions:
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-        - "202212.0"
-        - "202307.0"
-      - title: Customer login
-        url: /docs/scos/user/features/customer-account-management-feature-overview/customer-login-overview.html
-        include_versions:
-        - "201811.0"
-        - "201903.0"
-        - "201907.0"
-        - "202001.0"
-        - "202005.0"
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-        - "202212.0"
-        - "202307.0"
-      - title: Password management
-        url: /docs/scos/user/features/customer-account-management-feature-overview/password-management-overview.html
-      - title: Customer groups
-        url: /docs/scos/user/features/customer-account-management-feature-overview/customer-groups-overview.html
-    - title: Merchant B2B Contracts
-      url: /docs/scos/user/features/merchant-b2b-contracts-feature-overview.html
-      include_versions:
-      - "201903.0"
-      - "201907.0"
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-    - title: Merchant Product Restrictions
-      url: /docs/scos/user/features/merchant-product-restrictions-feature-overview.html
-      include_versions:
-      - "201903.0"
-      - "201907.0"
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-    - title: Navigation
-      url: /docs/scos/user/features/navigation-feature-overview.html
-      include_versions:
-      - "201907.0"
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-    - title: Order Management
-      url: /docs/scos/user/features/order-management-feature-overview/order-management-feature-overview.html
-      include_versions:
-      - "201811.0"
-      - "201903.0"
-      - "201907.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-      nested:
-      - title: Invoice generation
-        url: /docs/scos/user/features/order-management-feature-overview/invoice-generation-overview.html
-        include_versions:
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-        - "202212.0"
-        - "202307.0"
-      - title: Order cancellation
-        url: /docs/scos/user/features/order-management-feature-overview/order-cancellation-overview.html
-        include_versions:
-        - "202005.0"
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-        - "202212.0"
-        - "202307.0"
-      - title: Splittable order items
-        url: /docs/scos/user/features/order-management-feature-overview/splittable-order-items-overview.html
-      - title: Split delivery
-        url: /docs/scos/user/features/order-management-feature-overview/split-delivery-overview.html
-        include_versions:
-        - "202001.0"
-        - "202005.0"
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-        - "202212.0"
-        - "202307.0"
-      - title: OMS (Order management system) matrix
-        url: /docs/scos/user/features/order-management-feature-overview/oms-order-management-system-matrix.html
-      - title: Custom order reference
-        url: /docs/scos/user/features/order-management-feature-overview/custom-order-reference-overview.html
-        include_versions:
-        - "202005.0"
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-        - "202212.0"
-        - "202307.0"
-
-    - title: Payments
-      url: /docs/scos/user/features/payments-feature-overview.html
-      include_versions:
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-
-    - title: Product Relations
-      url: /docs/scos/user/features/product-relations-feature-overview.html
-      include_versions:
-      - "201903.0"
-      - "201907.0"
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-    - title: Quick Add to Cart
-      url: /docs/scos/user/features/quick-add-to-cart-feature-overview.html
-      include_versions:
-      - "202204.0"
-    - title: Reclamations
-      url: /docs/scos/user/features/reclamations-feature-overview.html
-      include_versions:
-      - "201903.0"
-      - "201907.0"
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-    - title: Refunds
-      url: /docs/scos/user/features/refunds-feature-overview.html
-      include_versions:
-      - "201903.0"
-      - "201907.0"
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-    - title: Reorder
-      url: /docs/scos/user/features/reorder-feature-overview.html
-      include_versions:
-      - "201903.0"
-      - "201907.0"
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-
-    - title: Spryker Core
-      url: /docs/scos/user/features/spryker-core-feature-overview/spryker-core-feature-overview.html
-      include_versions:
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-      nested:
-      - title: Vault for Tokens
-        url: /docs/scos/user/features/spryker-core-feature-overview/vault-for-tokens-overview.html
-        include_versions:
-        - "201907.0"
-        - "202001.0"
-        - "202005.0"
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-    - title: Spryker Core Back Office
-      url: /docs/scos/user/features/spryker-core-back-office-feature-overview/spryker-core-back-office-feature-overview.html
-      include_versions:
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-      nested:
-      - title: Back Office Translations
-        url: /docs/scos/user/features/spryker-core-back-office-feature-overview/back-office-translations-overview.html
-
-
-  - title: Back Office User guides
-    url: /docs/scos/user/back-office-user-guides/about-back-office-user-guides.html
-    include_versions:
-    - "201811.0"
-    - "201903.0"
-    - "201907.0"
-    - "202001.0"
-    - "202005.0"
-    - "202009.0"
-    - "202108.0"
-    - "202204.0"
-    nested:
-    - title: Viewing dashboard
-      url: /docs/scos/user/back-office-user-guides/dashboard/viewing-dashboard.html
-      include_versions:
-      - "202108.0"
-      - "202204.0"
-    - title: Punch Out
-      include_versions:
-      - "201907.0"
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-      nested:
-      - title: Managing punch out connections
-        url: /docs/scos/user/back-office-user-guides/punch-out/managing-punch-out-connections.html
-        include_versions:
-        - "201907.0"
-        - "202001.0"
-        - "202005.0"
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-      - title: Managing transactions log
-        url: /docs/scos/user/back-office-user-guides/punch-out/managing-transactions-log.html
-        include_versions:
-        - "201907.0"
-        - "202001.0"
-        - "202005.0"
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-    - title: Sales
-      include_versions:
-      - "201811.0"
-      - "201903.0"
-      - "201907.0"
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-      nested:
-      - title: Order matrix
-        url: /docs/scos/user/back-office-user-guides/sales/view-the-order-matrix.html
-      - title: Orders
-        nested:
-        - title: Changing the state of order items
-          url: /docs/scos/user/back-office-user-guides/sales/orders/changing-the-state-of-order-items.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-        - title: Creating reclamations
-          url: /docs/scos/user/back-office-user-guides/sales/orders/creating-reclamations.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-        - title: Commenting orders
-          url: /docs/scos/user/back-office-user-guides/sales/orders/commenting-orders.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-        - title: Creating returns
-          url: /docs/scos/user/back-office-user-guides/sales/orders/creating-returns.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-        - title: Editing billing addresses in orders
-          url: /docs/scos/user/back-office-user-guides/sales/orders/editing-billing-addresses-in-orders.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-        - title: Adding and removing custom order references
-          url: /docs/scos/user/back-office-user-guides/sales/orders/adding-and-removing-custom-order-references.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-        - title: Creating shipments
-          url: /docs/scos/user/back-office-user-guides/sales/orders/creating-shipments.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-        - title: Editing shipments
-          url: /docs/scos/user/back-office-user-guides/sales/orders/editing-shipments.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-        - title: Viewing returns of an order
-          url: /docs/scos/user/back-office-user-guides/sales/orders/viewing-returns-of-an-order.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-        - title: Creating shipments
-          url: /docs/scos/user/back-office-user-guides/sales/orders/creating-shipments.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-      - title: Reclamations
-        include_versions:
-        - "201903.0"
-        - "201907.0"
-        - "202001.0"
-        - "202005.0"
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-        nested:
-        - title: Viewing reclamations
-          url: /docs/scos/user/back-office-user-guides/sales/reclamations/viewing-reclamations.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-        - title: Changing the state of order items in reclamations
-          url: /docs/scos/user/back-office-user-guides/sales/reclamations/changing-the-state-of-order-items-in-reclamations.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-      - title: Refunds
-        url: /docs/scos/user/back-office-user-guides/sales/refunds/viewing-refunds.html
-    - title: Customer
-      include_versions:
-      - "201903.0"
-      - "201907.0"
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-      nested:
-      - title: Customers
-        include_versions:
-        - "202108.0"
-        - "202204.0"
-        nested:
-        - title: Create customers
-          url: /docs/scos/user/back-office-user-guides/customer/customers/create-customers.html
-        - title: Edit customers
-          url: /docs/scos/user/back-office-user-guides/customer/customers/edit-customers.html
-        - title: View customers
-          url: /docs/scos/user/back-office-user-guides/customer/customers/view-customers.html
-        - title: Add notes to customers
-          url: /docs/scos/user/back-office-user-guides/customer/customers/add-notes-to-customers.html
-        - title: Add customer addresses
-          url: /docs/scos/user/back-office-user-guides/customer/customers/add-customer-addresses.html
-        - title: Edit customer addresses
-          url: /docs/scos/user/back-office-user-guides/customer/customers/edit-customer-addresses.html
-      - title: Manage customer access
-        url: /docs/scos/user/back-office-user-guides/customer/manage-customer-access.html
-        include_versions:
-        - "202204.0"
-      - title: Manage customer groups
-        url: /docs/scos/user/back-office-user-guides/customer/manage-customer-groups.html
-        include_versions:
-        - "202204.0"
-      - title: Manage companies
-        url: /docs/scos/user/back-office-user-guides/customer/manage-companies.html
-        include_versions:
-        - "202108.0"
-        - "202204.0"
-      - title: Company units
-        include_versions:
-        - "202108.0"
-        - "202204.0"
-        nested:
-          - title: Create company units
-            url: /docs/scos/user/back-office-user-guides/customer/company-units/create-company-units.html
-          - title: Edit company units
-            url: /docs/scos/user/back-office-user-guides/customer/company-units/edit-company-units.html
-      - title: Company unit addresses
-        include_versions:
-        - "202108.0"
-        - "202204.0"
-        nested:
-          - title: Create company unit addresses
-            url: /docs/scos/user/back-office-user-guides/customer/company-unit-addresses/create-company-unit-addresses.html
-          - title: Edit company units addresses
-            url: /docs/scos/user/back-office-user-guides/customer/company-unit-addresses/edit-company-unit-addresses.html
-      - title: Company roles
-        include_versions:
-        - "202108.0"
-        - "202204.0"
-        nested:
-          - title: Create company roles
-            url: /docs/scos/user/back-office-user-guides/customer/company-roles/create-company-roles.html
-          - title: Edit company roles
-            url: /docs/scos/user/back-office-user-guides/customer/company-roles/edit-company-roles.html
-      - title: Company users
-        include_versions:
-        - "202108.0"
-        - "202204.0"
-        nested:
-          - title: Create company users
-            url: /docs/scos/user/back-office-user-guides/customer/company-users/create-company-users.html
-          - title: Edit company users
-            url: /docs/scos/user/back-office-user-guides/customer/company-users/edit-company-users.html
-      - title: Product relations
-        include_versions:
-        - "201811.0"
-        - "201903.0"
-        - "201907.0"
-        - "202001.0"
-        - "202005.0"
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-        nested:
-        - title: "Best practices: Promote products with product relations"
-          url: /docs/scos/user/back-office-user-guides/merchandising/product-relations/best-practices-promote-products-with-product-relations.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-        - title: Create product relations
-          url: /docs/scos/user/back-office-user-guides/merchandising/product-relations/create-product-relations.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-        - title: Edit product relations
-          url: /docs/scos/user/back-office-user-guides/merchandising/product-relations/edit-product-relations.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-        - title: View product relations
-          url: /docs/scos/user/back-office-user-guides/merchandising/product-relations/view-product-relations.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-
-
-      - title: Configurable bundle templates
-        include_versions:
-        - "202001.0"
-        - "202005.0"
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-        nested:
-        - title: Create configurable bundle templates
-          url: /docs/scos/user/back-office-user-guides/merchandising/configurable-bundle-templates/create-configurable-bundle-templates.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-          - "202212.0"
-          - "202307.0"
-        - title: Edit configurable bundle templates
-          url: /docs/scos/user/back-office-user-guides/merchandising/configurable-bundle-templates/edit-configurable-bundle-templates.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-          - "202212.0"
-          - "202307.0"
-        - title: Edit slots in configurable bundle templates
-          url: /docs/scos/user/back-office-user-guides/merchandising/configurable-bundle-templates/edit-slots-in-configurable-bundle-templates.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-          - "202212.0"
-          - "202307.0"
-
-      - title: Search Preferences
-        include_versions:
-        - "202108.0"
-        - "202204.0"
-        nested:
-        - title: "Best practices: Promote products with search preferences"
-          url: /docs/scos/user/back-office-user-guides/merchandising/search-preferences/best-practices-promote-products-with-search-preferences.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-        - title: Define search preferences
-          url: /docs/scos/user/back-office-user-guides/merchandising/search-preferences/define-search-preferences.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-        - title: Edit search preferences
-          url: /docs/scos/user/back-office-user-guides/merchandising/search-preferences/edit-search-preferences.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-      - title: Filter Preferences
-        include_versions:
-        - "202108.0"
-        - "202204.0"
-        nested:
-        - title: Define filter preferences
-          url: /docs/scos/user/back-office-user-guides/merchandising/filter-preferences/define-filter-preferences.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-        - title: Edit filter preferences
-          url: /docs/scos/user/back-office-user-guides/merchandising/filter-preferences/edit-filter-preferences.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-        - title: Reorder filter preferences
-          url: /docs/scos/user/back-office-user-guides/merchandising/filter-preferences/reorder-filter-preferences.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-      - title: Category filters
-        include_versions:
-        - "202108.0"
-        - "202204.0"
-        nested:
-        - title: Assign and deassign filters from categories
-          url: /docs/scos/user/back-office-user-guides/merchandising/category-filters/assign-and-deassign-filters-from-categories.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-        - title: Reorder category filters
-          url: /docs/scos/user/back-office-user-guides/merchandising/category-filters/reorder-category-filters.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-
-    - title: Marketplace
-      include_versions:
-      - "201903.0"
-      - "201907.0"
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-      nested:
-      - title: Merchants
-        include_versions:
-        - "202108.0"
-        - "202204.0"
-        nested:
-        - title: Create merchants
-          url: /docs/scos/user/back-office-user-guides/marketplace/merchants/create-merchants.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-        - title: Edit merchants
-          url: /docs/scos/user/back-office-user-guides/marketplace/merchants/edit-merchants.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-      - title: Merchant relations
-        include_versions:
-        - "202108.0"
-        - "202204.0"
-        nested:
-        - title: Create merchant relations
-          url: /docs/scos/user/back-office-user-guides/marketplace/merchant-relations/create-merchant-relations.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-        - title: Edit merchant relations
-          url: /docs/scos/user/back-office-user-guides/marketplace/merchant-relations/edit-merchant-relations.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
-
-    - title: Administration
-      nested:
-      - title: View stores
-        url: /docs/scos/user/back-office-user-guides/administration/view-stores.html
-        include_versions:
-        - "202204.0"
-      - title: Payment methods
-        include_versions:
-        - "202001.0"
-        - "202005.0"
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-        nested:
-        - title: View payment methods
-          url: /docs/scos/user/back-office-user-guides/administration/payment-methods/view-payment-methods.html
-          include_versions:
-          - "202204.0"
-        - title: Edit payment methods
-          url: /docs/scos/user/back-office-user-guides/administration/payment-methods/edit-payment-methods.html
-          include_versions:
-          - "202204.0"
-        - title: Add translations
-          url: /docs/scos/user/back-office-user-guides/administration/glossary/add-translations.html
-          include_versions:
-          - "202204.0"
-        - title: Edit translations
-          url: /docs/scos/user/back-office-user-guides/administration/glossary/edit-translations.html
-          include_versions:
-          - "202204.0"
-
-      - title: Define merchant order thresholds
-        url: /docs/scos/user/back-office-user-guides/administration/define-merchant-order-thresholds.html
-        include_versions:
-        - "202204.0"
-
-  - title: Technology partners
-    url: /docs/scos/user/technology-partners/technology-partners.html
-    include_versions:
-    - "201811.0"
-    - "201903.0"
-    - "201907.0"
-    - "202001.0"
-    - "202005.0"
-    - "202009.0"
-    - "202108.0"
-    - "202204.0"
-    nested:
-    - title: Order Management (ERPOMS)
-      include_versions:
-      - "201811.0"
-      - "201903.0"
-      - "201907.0"
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-      nested:
-      - title: Tradebyte
-        url: /docs/scos/user/technology-partners/order-management-erpoms/tradebyte.html
-        include_versions:
-        - "202001.0"
-        - "202005.0"
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-      - title: NEKOM CC GmbH
-        url: /docs/scos/user/technology-partners/order-management-erpoms/nekom-cc-gmbh.html
-        include_versions:
-        - "202001.0"
-        - "202005.0"
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-    - title: Marketplace Integrations
-      nested:
-      - title: ChannelPilot Marketplace
-        url: /docs/scos/user/technology-partners/marketplace-integrations/channelpilot-marketplace.html
-    - title: Finance and accounting
-      include_versions:
-      - "202108.0"
-      - "202204.0"
-      nested:
-      - title: Nitrobox
-        url: /docs/scos/user/technology-partners/finance-and-accounting/nitrobox.html
-      - title: CollectAI
-        url: /docs/scos/user/technology-partners/finance-and-accounting/collectai.html
-    - title: Customer Service
-      include_versions:
-      - "202108.0"
-      - "202204.0"
-      nested:
-      - title: Dixa
-        url: /docs/scos/user/technology-partners/customer-service/dixa.html
-      - title: Live Chat Service
-        url: /docs/scos/user/technology-partners/customer-service/live-chat-service.html
-      - title: optimise-it
-        url: /docs/scos/user/technology-partners/customer-service/optimise-it.html
-      - title: iAdvize
-        url: /docs/scos/user/technology-partners/customer-service/iadvize.html
-    - title: Hosting Providers
-      nested:
-      - title: Claranet
-        url: /docs/scos/user/technology-partners/hosting-providers/claranet.html
-      - title: Root 360
-        url: /docs/scos/user/technology-partners/hosting-providers/root-360.html
-      - title: Heroku
-        url: /docs/scos/user/technology-partners/hosting-providers/heroku.html
-      - title: Continum
-        url: /docs/scos/user/technology-partners/hosting-providers/continum.html
-      - title: Metaways
-        url: /docs/scos/user/technology-partners/hosting-providers/metaways.html
-    - title: Marketing and conversion
-      include_versions:
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-      - "202212.0"
-      - "202307.0"
-      nested:
-      - title: Personalization and cross-selling
-        nested:
-        include_versions:
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-        - title: Contentserv
-          url: /docs/scos/user/technology-partners/marketing-and-conversion/personalization-and-cross-selling/contentserv.html
-        - title: Econda
-          url: /docs/scos/user/technology-partners/marketing-and-conversion/personalization-and-cross-selling/econda.html
-        - title: Nosto
-          url: /docs/scos/user/technology-partners/marketing-and-conversion/personalization-and-cross-selling/nosto.html
-        - title: 8Select
-          url: /docs/scos/user/technology-partners/marketing-and-conversion/personalization-and-cross-selling/8select.html
-        - title: trbo
-          url: /docs/scos/user/technology-partners/marketing-and-conversion/personalization-and-cross-selling/trbo.html
-      - title: Customer communication
-        include_versions:
-        - "202009.0"
-        - "202108.0"
-        - "202204.0"
-        - "202212.0"
-        - "202307.0"
-        nested:
-        - title: Episerver
-          url: /docs/scos/user/technology-partners/marketing-and-conversion/customer-communication/episerver.html
-        - title: Dotdigital
-          url: /docs/scos/user/technology-partners/marketing-and-conversion/customer-communication/dotdigital.html
-        - title: Inxmail
-          url: /docs/scos/user/technology-partners/marketing-and-conversion/customer-communication/inxmail.html
-          include_versions:
-          - "202009.0"
-          - "202108.0"
-          - "202204.0"
-      - title: AB testing and performance
-        nested:
-        - title: AB Tasty
-          url: /docs/scos/user/technology-partners/marketing-and-conversion/ab-testing-and-performance/ab-tasty.html
-        - title: Baqend
-          url: /docs/scos/user/technology-partners/marketing-and-conversion/ab-testing-and-performance/baqend.html
-      - title: Customer retention and loyalty
-        nested:
-        - title: Zenloop
-          url: /docs/scos/user/technology-partners/marketing-and-conversion/customer-retention-and-loyalty/zenloop.html
-        - title: Namogoo
-          url: /docs/scos/user/technology-partners/marketing-and-conversion/customer-retention-and-loyalty/namogoo.html
-        - title: Trustpilot
-          url: /docs/scos/user/technology-partners/marketing-and-conversion/customer-retention-and-loyalty/trustpilot.html
-      - title: Analytics
-        nested:
-        - title: FACT-Finder
-          url: /docs/scos/user/technology-partners/marketing-and-conversion/analytics/fact-finder.html
-        - title: Minubo
-          url: /docs/scos/user/technology-partners/marketing-and-conversion/analytics/minubo.html
-        - title: ChannelPilot Analytics
-          url: /docs/scos/user/technology-partners/marketing-and-conversion/analytics/channelpilot-analytics.html
-        - title: Haensel AMS
-          url: /docs/scos/user/technology-partners/marketing-and-conversion/analytics/haensel-ams.html
-        - title: Mindlab
-          url: /docs/scos/user/technology-partners/marketing-and-conversion/analytics/mindlab.html
-    - title: Payment Partners
-      include_versions:
-      - "201811.0"
-      - "201903.0"
-      - "201907.0"
-      - "202001.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-      nested:
-      - title: Afterpay
-        url: /docs/scos/user/technology-partners/payment-partners/afterpay.html
-      - title: Amazon Pay
-        url: /docs/scos/user/technology-partners/payment-partners/amazon-pay.html
-      - title: BS Payone
-        url: /docs/scos/user/technology-partners/payment-partners/bs-payone/bs-payone.html
-        nested:
-        - title: SCOS Integration
-          nested:
-          - title: PayOne - Integration into the SCOS Project
-            url: /docs/scos/user/technology-partners/payment-partners/bs-payone/scos-integration/payone-integration-into-the-scos-project.html
-          - title: PayOne - Risk Check and Address Check
-            url: /docs/scos/user/technology-partners/payment-partners/bs-payone/scos-integration/payone-risk-check-and-address-check.html
-          - title: PayOne - Cash on Delivery
-            url: /docs/scos/user/technology-partners/payment-partners/bs-payone/scos-integration/payone-cash-on-delivery.html
-          - title: PayOne - PayPal Express Checkout Payment
-            url: /docs/scos/user/technology-partners/payment-partners/bs-payone/scos-integration/payone-paypal-express-checkout-payment.html
-        - title: Legacy Demoshop Integration
-          nested:
-          - title: PayOne - State Machine Commands, Conditions and Events
-            url: /docs/scos/user/technology-partners/payment-partners/bs-payone/legacy-demoshop-integration/payone-state-machine-commands-conditions-and-events.html
-          - title: PayOne - Authorization and Preauthorization Capture Flows
-            url: /docs/scos/user/technology-partners/payment-partners/bs-payone/legacy-demoshop-integration/payone-authorization-and-preauthorization-capture-flows.html
-          - title: PayOne - Payment methods
-            include_versions:
-            - "202009.0"
-            - "202108.0"
-            nested:
-            - title: PayOne - Credit Card Payment
-              url: /docs/scos/user/technology-partners/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-credit-card-payment.html
-            - title: PayOne - Direct Debit Payment
-              url: /docs/scos/user/technology-partners/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-direct-debit-payment.html
-            - title: PayOne - Prepayment
-              url: /docs/scos/user/technology-partners/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-prepayment.html
-            - title: PayOne - Invoice Payment
-              url: /docs/scos/user/technology-partners/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-invoice-payment.html
-            - title: PayOne - Online Transfer Payment
-              url: /docs/scos/user/technology-partners/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-online-transfer-payment.html
-            - title: PayOne - Security Invoice Payment
-              url: /docs/scos/user/technology-partners/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-security-invoice-payment.html
-            - title: PayOne - Paypal Payment
-              url: /docs/scos/user/technology-partners/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-paypal-payment.html
-            - title: PayOne - PayPal Express Checkout Payment
-              url: /docs/scos/user/technology-partners/payment-partners/bs-payone/legacy-demoshop-integration/payone-payment-methods/payone-paypal-express-checkout-payment.html
-              include_versions:
-              - "202009.0"
-              - "202108.0"
-          - title: PayOne - PayPal Express Checkout Payment
-            url: /docs/scos/user/technology-partners/payment-partners/bs-payone/legacy-demoshop-integration/payone-paypal-express-checkout-payment.html
-            include_versions:
-            - "201811.0"
-            - "201903.0"
-            - "201907.0"
-            - "202001.0"
-            - "202005.0"
-          - title: PayOne - Facade
-            url: /docs/scos/user/technology-partners/payment-partners/bs-payone/legacy-demoshop-integration/payone-facade.html
-          - title: PayOne - Integration into the Legacy Demoshop Project
-            url: /docs/scos/user/technology-partners/payment-partners/bs-payone/legacy-demoshop-integration/payone-integration-into-the-legacy-demoshop-project.html
-      - title: Billpay
-        url: /docs/scos/user/technology-partners/payment-partners/billpay.html
-      - title: Braintree
-        url: /docs/scos/user/technology-partners/payment-partners/braintree.html
-      - title: Computop
-        url: /docs/scos/user/technology-partners/payment-partners/computop.html
-      - title: CrefoPay
-        url: /docs/scos/user/technology-partners/payment-partners/crefopay.html
-      - title: Heidelpay
-        url: /docs/scos/user/technology-partners/payment-partners/heidelpay.html
-      - title: Klarna
-        url: /docs/scos/user/technology-partners/payment-partners/klarna.html
-      - title: Adyen
-        url: /docs/scos/user/technology-partners/payment-partners/adyen.html
-      - title: RatePay
-        url: /docs/scos/user/technology-partners/payment-partners/ratepay.html
-      - title: Billie
-        url: /docs/scos/user/technology-partners/payment-partners/billie.html
-      - title: Powerpay
-        url: /docs/scos/user/technology-partners/payment-partners/powerpay.html
-      - title: Payolution
-        url: /docs/scos/user/technology-partners/payment-partners/payolution.html
-      - title: ratenkauf by easyCredit
-        url: /docs/scos/user/technology-partners/payment-partners/ratenkauf-by-easycredit.html
-      - title: Arvato
-        url: /docs/scos/user/technology-partners/payment-partners/arvato.html
-    - title: Operational tools, monitoring, legal, etc.
-      include_versions:
-      - "202001.0"
-      - "202005.0"
-      - "202009.0"
-      - "202108.0"
-      - "202204.0"
-      nested:
-      - title: PlusServer
-        url: /docs/scos/user/technology-partners/operational-tools-monitoring-legal-etc/plusserver.html
-      - title: common solutions
-        url: /docs/scos/user/technology-partners/operational-tools-monitoring-legal-etc/common-solutions.html
-      - title: VSHN
-        url: /docs/scos/user/technology-partners/operational-tools-monitoring-legal-etc/vshn.html
-      - title: Tideways
-        url: /docs/scos/user/technology-partners/operational-tools-monitoring-legal-etc/tideways.html
-      - title: Shopmacher
-        url: /docs/scos/user/technology-partners/operational-tools-monitoring-legal-etc/shopmacher.html
-      - title: Loggly
-        url: /docs/scos/user/technology-partners/operational-tools-monitoring-legal-etc/loggly.html
-      - title: Proclane
-        url: /docs/scos/user/technology-partners/operational-tools-monitoring-legal-etc/proclane.html
-      - title: Data Virtuality
-        url: /docs/scos/user/technology-partners/operational-tools-monitoring-legal-etc/data-virtuality.html
-      - title: Usercentrics
-        url: /docs/scos/user/technology-partners/operational-tools-monitoring-legal-etc/usercentrics.html
-      - title: New Relic
-        url: /docs/scos/user/technology-partners/operational-tools-monitoring-legal-etc/new-relic.html
-      - title: Mindcurv
-        url: /docs/scos/user/technology-partners/operational-tools-monitoring-legal-etc/mindcurv.html
-
 
 
 
diff --git a/_data/sidebars/dg_dev_sidebar.yml b/_data/sidebars/dg_dev_sidebar.yml
index 54f89df7d16..47aadb18ad3 100644
--- a/_data/sidebars/dg_dev_sidebar.yml
+++ b/_data/sidebars/dg_dev_sidebar.yml
@@ -5,6 +5,12 @@ entries:
   nested:
   - title: Developer getting started guide
     url: /docs/scos/dev/developer-getting-started-guide.html
+  - title: B2C Suite
+    url: /docs/dg/dev/b2c-suite.html
+  - title: B2B Suite
+    url: /docs/dg/dev/b2b-suite.html
+  - title: Master Suite
+    url: /docs/dg/dev/master-suite.html
   - title: Set up locally
     url: /docs/dg/dev/set-up-spryker-locally/set-up-spryker-locally.html
     nested:
@@ -1165,3 +1171,6 @@ entries:
         url: /docs/dg/dev/updating-spryker/switch-demo-shop-version.html
       - title: Troubleshooting updates
         url: /docs/dg/dev/updating-spryker/troubleshooting-updates.html
+
+  - title: Product and code releases
+    url: /docs/dg/dev/product-and-code-releases.html
diff --git a/docs/about/all/faq.md b/docs/about/all/faq.md
index 2add95b27c3..0317ef69938 100644
--- a/docs/about/all/faq.md
+++ b/docs/about/all/faq.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/faq.html
 ---
 title: FAQ
 description: Use the article to get answers to the most popular questions about Spryker.
@@ -7,22 +6,7 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/faq
 originalArticleId: c0bdf12c-d68d-4dc6-84b3-8087fc55b16c
 redirect_from:
-  - /2021080/docs/faq
-  - /2021080/docs/en/faq
-  - /docs/faq
-  - /docs/en/faq
-  - /v5/docs/faq
-  - /v5/docs/en/faq
-  - /v4/docs/faq
-  - /v4/docs/en/faq
-  - /v3/docs/faq
-  - /v3/docs/en/faq
-  - /v2/docs/faq
-  - /v2/docs/en/faq
-  - /v1/docs/faq
-  - /v1/docs/en/faq
-  - /v6/docs/faq
-  - /v6/docs/en/faq
+- /docs/scos/user/intro-to-spryker/faq.html
 ---
 
 ## Does Spryker have features?
@@ -32,21 +16,21 @@ Yes. Like iOS or macOS, Spryker is an operating system that offers a range of fe
 ## What do you mean when you say "apps"?
 
 By apps, we mean everything that is customer-facing. For example, a B2C or B2B shop system, Alexa voice skill, order status update function, easy repeat-order function, chatbot for customer service, native or web-based mobile customer interface, EDP interfaces, and IoT installations. Apps ensure such types of services as communication between elevators or a message from an industrial saw requesting component replacement or even a booking service.
-    
+
 ## Can third-party items be integrated?
 
 Yes. We refer to third-party integrations as industry partners. They include services for payment, shipment, on-site search, recommendation engines, tracking, social, BI, loyalty, chat, and other services which can be integrated into the OS.
-   
+
 ## Which new trends does your OS support?
 
 As vendors of an operating system, our task is to ensure the quick development of apps. Since ROI timescales shorten increasingly and technology develops in ever quicker succession, it is difficult to look ahead even to 12 months. With this in mind, Spryker provides a starting point from which to develop applications in such areas as voice, chatbots, blockchain, AI, and more.
-   
+
 ## What is Spryker's solution for omnichannel?
-    
+
 In our world, omnichannel is a collection of apps in use—for example, a webshop plus POS plus mobile as one possible combination. Within the operating system, we are trying to offer an increasing number of preinstalled capabilities and demo apps so that every customer can put it to work to reflect their own use case as quickly as possible. To avoid duplicating logic such as search, discount, and payment per individual channel, these items are offered or stored in the operating system. This approach significantly improves cycles of customer-facing apps' building and testing.
-   
+
 ## Is Spryker a shop system?
- 
+
 No. Spryker is an operating system for commerce. In our world, a B2C shop is only one of many apps. Customers who only need one app will probably be able to reach their goals faster with a standard, set-in-stone legacy system.
 
 ## Do I need my own team, or can I work with an agency?
diff --git a/docs/about/all/mvp-project-structuring.md b/docs/about/all/mvp-project-structuring.md
index e67d50ffeca..1e918b6bdc6 100644
--- a/docs/about/all/mvp-project-structuring.md
+++ b/docs/about/all/mvp-project-structuring.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/mvp-project-structuring.html
 ---
 title: MVP project structuring
 description: This article helps with the project planning stage.
@@ -7,22 +6,7 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/mvp-project-structuring
 originalArticleId: 2a0c62a9-d1e4-43e0-8b10-b44f200a1bb0
 redirect_from:
-  - /2021080/docs/mvp-project-structuring
-  - /2021080/docs/en/mvp-project-structuring
-  - /docs/mvp-project-structuring
-  - /docs/en/mvp-project-structuring
-  - /v5/docs/mvp-project-structuring
-  - /v5/docs/en/mvp-project-structuring
-  - /v4/docs/mvp-project-structuring
-  - /v4/docs/en/mvp-project-structuring
-  - /v3/docs/mvp-project-structuring
-  - /v3/docs/en/mvp-project-structuring
-  - /v2/docs/mvp-project-structuring
-  - /v2/docs/en/mvp-project-structuring
-  - /v1/docs/mvp-project-structuring
-  - /v1/docs/en/mvp-project-structuring
-  - /v6/docs/mvp-project-structuring
-  - /v6/docs/en/mvp-project-structuring
+- /docs/scos/user/intro-to-spryker/mvp-project-structuring.html
 ---
 
 The purpose of these guidelines described in this topic is to help with the project planning stage.
diff --git a/docs/about/all/spryker-academy.md b/docs/about/all/spryker-academy.md
index 09c9f054e6e..f7a6528e08e 100644
--- a/docs/about/all/spryker-academy.md
+++ b/docs/about/all/spryker-academy.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/spryker-academy.html
 ---
 title: Spryker Academy
 description: Spryker Academy is a dedicated resource for learning Spryker Commerce OS through a variety of self-paced and instructor-led courses.
@@ -7,166 +6,7 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/spryker-videos
 originalArticleId: e1db0ef0-24d3-4862-b493-c4bf8a4adad7
 redirect_from:
-  - /2021080/docs/spryker-videos
-  - /2021080/docs/en/spryker-videos
-  - /docs/spryker-videos
-  - /docs/en/spryker-videos
-  - /v5/docs/spryker-videos
-  - /v5/docs/en/spryker-videos
-  - /v4/docs/b2b-demo-shop
-  - /v4/docs/en/b2b-demo-shop  
-  - /v4/docs/b2c-demo-shop
-  - /v4/docs/en/b2c-demo-shop
-  - /v4/docs/cms-blocks
-  - /v4/docs/en/cms-blocks
-  - /v4/docs/cms-pages-video
-  - /v4/docs/en/cms-pages-video
-  - /v4/docs/product-groups
-  - /v4/docs/en/product-groups
-  - /v4/docs/product-sets-video
-  - /v4/docs/en/product-sets-video
-  - /v4/docs/how-to-configure-navigation
-  - /v4/docs/en/how-to-configure-navigation
-  - /v4/docs/how-to-setup-agent-assist-b2b
-  - /v4/docs/en/how-to-setup-agent-assist-b2b
-  - /v4/docs/how-to-setup-company-structure-b2b
-  - /v4/docs/en/how-to-setup-company-structure-b2b
-  - /v4/docs/how-to-setup-users-and-roles-b2b
-  - /v4/docs/en/how-to-setup-users-and-roles-b2b
-  - /v4/docs/how-to-setup-merchants-and-merchant-relationships
-  - /v4/docs/en/how-to-setup-merchants-and-merchant-relationships
-  - /v4/docs/how-to-use-shopping-carts-b2b
-  - /v4/docs/en/how-to-use-shopping-carts-b2b
-  - /v4/docs/how-to-use-shopping-lists-b2b
-  - /v4/docs/en/how-to-use-shopping-lists-b2b
-  - /v4/docs/legacy-demoshop
-  - /v4/docs/en/legacy-demoshop
-  - /v4/docs/manage-categories-in-spryker
-  - /v4/docs/en/manage-categories-in-spryker
-  - /v4/docs/product-management-video
-  - /v4/docs/en/product-management-video
-  - /v4/docs/navigation-video
-  - /v4/docs/en/navigation-video
-  - /v4/docs/videos
-  - /v4/docs/en/videos
-  - /v4/docs/wishlists-video
-  - /v4/docs/en/wishlists-video
-  - /v3/docs/b2b-demo-shop
-  - /v3/docs/en/b2b-demo-shop
-  - /v3/docs/b2c-demo-shop
-  - /v3/docs/en/b2c-demo-shop
-  - /v3/docs/cms-blocks
-  - /v3/docs/en/cms-blocks
-  - /v3/docs/cms-pages-video
-  - /v3/docs/en/cms-pages-video
-  - /v3/docs/product-groups
-  - /v3/docs/en/product-groups
-  - /v3/docs/product-sets-video
-  - /v3/docs/en/product-sets-video
-  - /v3/docs/how-to-configure-navigation
-  - /v3/docs/en/how-to-configure-navigation
-  - /v3/docs/how-to-setup-agent-assist-b2b
-  - /v3/docs/en/how-to-setup-agent-assist-b2b
-  - /v3/docs/how-to-setup-company-structure-b2b
-  - /v3/docs/en/how-to-setup-company-structure-b2b
-  - /v3/docs/how-to-setup-users-and-roles-b2b
-  - /v3/docs/en/how-to-setup-users-and-roles-b2b
-  - /v3/docs/how-to-setup-merchants-and-merchant-relationships
-  - /v3/docs/en/how-to-setup-merchants-and-merchant-relationships
-  - /v3/docs/how-to-use-shopping-carts-b2b
-  - /v3/docs/en/how-to-use-shopping-carts-b2b
-  - /v3/docs/how-to-use-shopping-lists-b2b
-  - /v3/docs/en/how-to-use-shopping-lists-b2b
-  - /v3/docs/legacy-demoshop
-  - /v3/docs/en/legacy-demoshop
-  - /v3/docs/manage-categories-in-spryker
-  - /v3/docs/en/manage-categories-in-spryker
-  - /v3/docs/product-management-video
-  - /v3/docs/en/product-management-video
-  - /v3/docs/navigation-video
-  - /v3/docs/en/navigation-video
-  - /v3/docs/videos
-  - /v3/docs/en/videos
-  - /v3/docs/wishlists-video
-  - /v3/docs/en/wishlists-video
-  - /v2/docs/b2b-demo-shop
-  - /v2/docs/en/b2b-demo-shop
-  - /v2/docs/b2c-demo-shop
-  - /v2/docs/en/b2c-demo-shop
-  - /v2/docs/cms-blocks
-  - /v2/docs/en/cms-blocks
-  - /v2/docs/cms-pages-video
-  - /v2/docs/en/cms-pages-video
-  - /v2/docs/product-groups
-  - /v2/docs/en/product-groups
-  - /v2/docs/product-sets-video
-  - /v2/docs/en/product-sets-video
-  - /v2/docs/how-to-configure-navigation
-  - /v2/docs/en/how-to-configure-navigation
-  - /v2/docs/how-to-setup-agent-assist-b2b
-  - /v2/docs/en/how-to-setup-agent-assist-b2b
-  - /v2/docs/how-to-setup-company-structure-b2b
-  - /v2/docs/en/how-to-setup-company-structure-b2b
-  - /v2/docs/how-to-setup-users-and-roles-b2b
-  - /v2/docs/en/how-to-setup-users-and-roles-b2b
-  - /v2/docs/how-to-setup-merchants-and-merchant-relationships
-  - /v2/docs/en/how-to-setup-merchants-and-merchant-relationships
-  - /v2/docs/how-to-use-shopping-carts-b2b
-  - /v2/docs/en/how-to-use-shopping-carts-b2b
-  - /v2/docs/how-to-use-shopping-lists-b2b
-  - /v2/docs/en/how-to-use-shopping-lists-b2b
-  - /v2/docs/legacy-demoshop
-  - /v2/docs/en/legacy-demoshop
-  - /v2/docs/manage-categories-in-spryker
-  - /v2/docs/en/manage-categories-in-spryker
-  - /v2/docs/product-management-video
-  - /v2/docs/en/product-management-video
-  - /v2/docs/navigation-video
-  - /v2/docs/en/navigation-video
-  - /v2/docs/videos
-  - /v2/docs/en/videos
-  - /v2/docs/wishlists-video
-  - /v2/docs/en/wishlists-video
-  - /v1/docs/b2b-demo-shop
-  - /v1/docs/en/b2b-demo-shop
-  - /v1/docs/b2c-demo-shop
-  - /v1/docs/en/b2c-demo-shop
-  - /v1/docs/cms-blocks
-  - /v1/docs/en/cms-blocks
-  - /v1/docs/cms-pages-video
-  - /v1/docs/en/cms-pages-video
-  - /v1/docs/product-groups
-  - /v1/docs/en/product-groups
-  - /v1/docs/product-sets-video
-  - /v1/docs/en/product-sets-video
-  - /v1/docs/how-to-configure-navigation
-  - /v1/docs/en/how-to-configure-navigation
-  - /v1/docs/how-to-setup-agent-assist-b2b
-  - /v1/docs/en/how-to-setup-agent-assist-b2b
-  - /v1/docs/how-to-setup-company-structure-b2b
-  - /v1/docs/en/how-to-setup-company-structure-b2b
-  - /v1/docs/how-to-setup-users-and-roles-b2b
-  - /v1/docs/en/how-to-setup-users-and-roles-b2b
-  - /v1/docs/how-to-setup-merchants-and-merchant-relationships
-  - /v1/docs/en/how-to-setup-merchants-and-merchant-relationships
-  - /v1/docs/how-to-use-shopping-carts-b2b
-  - /v1/docs/en/how-to-use-shopping-carts-b2b
-  - /v1/docs/how-to-use-shopping-lists-b2b
-  - /v1/docs/en/how-to-use-shopping-lists-b2b
-  - /v1/docs/legacy-demoshop
-  - /v1/docs/en/legacy-demoshop
-  - /v1/docs/manage-categories-in-spryker
-  - /v1/docs/en/manage-categories-in-spryker
-  - /v1/docs/product-management-video
-  - /v1/docs/en/product-management-video
-  - /v1/docs/navigation-video
-  - /v1/docs/en/navigation-video
-  - /v1/docs/videos
-  - /v1/docs/en/videos
-  - /v1/docs/wishlists-video
-  - /v1/docs/en/wishlists-video
-  - /v6/docs/spryker-videos
-  - /v6/docs/en/spryker-videos
+  - /docs/scos/user/intro-to-spryker/spryker-academy.html
   - /docs/scos/user/intro-to-spryker/videos-and-webinars/spryker-videos.html
   - /docs/scos/user/intro-to-spryker/202204.0/videos-and-webinars/spryker-videos.html
   - /docs/scos/user/intro-to-spryker/spryker-videos.html
diff --git a/docs/about/all/b2b-suite.md b/docs/dg/dev/b2b-suite.md
similarity index 94%
rename from docs/about/all/b2b-suite.md
rename to docs/dg/dev/b2b-suite.md
index 0e705d78264..1e663976f72 100644
--- a/docs/about/all/b2b-suite.md
+++ b/docs/dg/dev/b2b-suite.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/b2b-suite.html
 ---
 title: B2B Suite
 description: The Spryker B2B Suite is a showcase that demonstrates ready-to-use B2B-specific Spryker features in a live implementation.
@@ -7,24 +6,13 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/b2b-suite
 originalArticleId: 8007db6c-8e30-4de3-ade0-990e6cea9d36
 redirect_from:
-  - /2021080/docs/b2b-suite
-  - /2021080/docs/en/b2b-suite
-  - /docs/b2b-suite
-  - /docs/en/b2b-suite
-  - /v5/docs/b2b-suite
-  - /v5/docs/en/b2b-suite
-  - /v4/docs/b2b-suite
-  - /v4/docs/en/b2b-suite
-  - /v4/docs/b2c-suite
-  - /v4/docs/en/b2c-suite
-  - /v6/docs/b2b-suite
-  - /v6/docs/en/b2b-suite
+- /docs/scos/user/intro-to-spryker/b2b-suite.html
 related:
   - title: B2C Suite
     link: docs/scos/user/intro-to-spryker/b2c-suite.html
 ---
 
-The Spryker B2B Suite is a collection of ready-to-use B2B-specific features. Of course, every B2B project has its own set of features that meet its business needs and B2C features can be used as well, but the most common features for B2B commerce are as follows.
+The Spryker B2B Suite is a collection of ready-to-use B2B-specific features:
 
 <details>
 <summary markdown='span'>B2B feature list</summary>
@@ -96,6 +84,7 @@ The Spryker B2B Suite is a collection of ready-to-use B2B-specific features. Of
 </details>
 
 ## B2B Demo Shop
+
 To demonstrate the B2B features in a live implementation, we use a B2B Demo Shop. The B2B Demo Shop is a showcase that is preloaded with a combination of modules and functionalities best suited for B2B commerce. This Demo Shop is our recommended starting point for all standard B2B commerce projects. It comes with the new modern look-and-feel and atomic design approach. New features for the B2B Demo Shop are released every several months.
 
 {% wistia gfmntivjsn 960 720 %}
diff --git a/docs/about/all/b2c-suite.md b/docs/dg/dev/b2c-suite.md
similarity index 100%
rename from docs/about/all/b2c-suite.md
rename to docs/dg/dev/b2c-suite.md
diff --git a/docs/about/all/master-suite.md b/docs/dg/dev/master-suite.md
similarity index 65%
rename from docs/about/all/master-suite.md
rename to docs/dg/dev/master-suite.md
index f94d9a56e69..8fad990446b 100644
--- a/docs/about/all/master-suite.md
+++ b/docs/dg/dev/master-suite.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/master-suite.html
 ---
 title: Master Suite
 last_updated: Jun 16, 2021
@@ -6,26 +5,11 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/master-suite
 originalArticleId: c0bbeeda-3569-485b-9954-39a34c695152
 redirect_from:
-  - /2021080/docs/master-suite
-  - /2021080/docs/en/master-suite
-  - /docs/master-suite
-  - /docs/en/master-suite
-  - /v5/docs/master-suite
-  - /v5/docs/en/master-suite
-  - /v4/docs/master-suite
-  - /v4/docs/en/master-suite
-  - /v3/docs/demoshops
-  - /v3/docs/en/demoshops
-  - /v2/docs/demoshops
-  - /v2/docs/en/demoshops
-  - /v1/docs/demoshops
-  - /v1/docs/en/demoshops
-  - /v6/docs/master-suite
-  - /v6/docs/en/master-suite
+- /docs/scos/user/intro-to-spryker/master-suite.html
 ---
 
-Master Suite represents a collection of both [B2B](/docs/scos/user/intro-to-spryker/b2b-suite.html) and [B2C](/docs/scos/user/intro-to-spryker/b2c-suite.html) modules. However, unlike B2B and B2C Demo Shops, the code in the [Master Suite project repository](https://github.com/spryker-shop/suite) is released as soon as it is ready. If you have an implementation that combines B2B and B2C, you can benefit from the full range of SCOS functionality. 
+Master Suite represents a collection of both [B2B](/docs/scos/user/intro-to-spryker/b2b-suite.html) and [B2C](/docs/scos/user/intro-to-spryker/b2c-suite.html) modules. However, unlike B2B and B2C Demo Shops, the code in the [Master Suite project repository](https://github.com/spryker-shop/suite) is released as soon as it is ready. If you have an implementation that combines B2B and B2C, you can benefit from the full range of SCOS functionality.
 
-Or if you want to take a single feature or module from the larger SCOS scope, you can take single modules from the following GitHub repository paths:
+Or if you want to take a single feature or module from the larger SCOS scope, you can take single modules from the following GitHub repositories:
 * [https://github.com/spryker-shop/*](https://github.com/spryker-shop/)
 * [https://github.com/spryker/*](https://github.com/spryker/)
diff --git a/docs/about/all/spryker-release-process.md b/docs/dg/dev/product-and-code-releases.md
similarity index 68%
rename from docs/about/all/spryker-release-process.md
rename to docs/dg/dev/product-and-code-releases.md
index 22d122a5e48..92651d6fb58 100644
--- a/docs/about/all/spryker-release-process.md
+++ b/docs/dg/dev/product-and-code-releases.md
@@ -1,26 +1,15 @@
-  - /docs/scos/user/intro-to-spryker/spryker-release-process.html
 ---
-title: Spryker release process
+title: Product and code releases
 last_updated: Jun 16, 2021
 template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/spryker-release-process
 originalArticleId: 3195aac4-0b8e-43a7-b540-0222f567c9fc
 redirect_from:
-  - /2021080/docs/spryker-release-process
-  - /2021080/docs/en/spryker-release-process
-  - /docs/spryker-release-process
-  - /docs/en/spryker-release-process
-  - /v5/docs/spryker-release-process
-  - /v5/docs/en/spryker-release-process
-  - /v4/docs/spryker-release-process
-  - /v4/docs/en/spryker-release-process
-  - /v6/docs/spryker-release-process
-  - /v6/docs/en/spryker-release-process
----
+- /docs/scos/user/intro-to-spryker/spryker-release-process.html
 
-Spryker has always prided itself on the fast pace of innovation and rapid development of new functionality. New features and enhancements are shipped almost daily.
+---
 
-Many customers benefit from these continuous releases by having immediate access to new, sometimes even beta, versions of the Spryker modules. At the same time, with the growth of our product, we faced a necessity to also have a more structured and organized release approach. To accommodate both the fast pace of innovation and predictability of the upgrade process, we support two types of releases: atomic (code) releases and product releases.
+To accommodate both the fast pace of innovation and predictability of the upgrade process, we support two types of releases: atomic (code) releases and product releases.
 
 ![Product releases flow](https://spryker.s3.eu-central-1.amazonaws.com/docs/About/Releases/Release+notes/image2018-8-10_17-10-26.png)
 

From 2a59053b56193dc805a76ff699baa56efb8eeb3e Mon Sep 17 00:00:00 2001
From: Andrii Tserkovnyi <andrii.tserkovnyi@spryker.com>
Date: Tue, 5 Mar 2024 18:21:58 +0200
Subject: [PATCH 03/26] redirects

---
 docs/about/all/docs-updates.md                |  3 +-
 docs/about/all/intro-to-spryker.md            | 26 +------------
 .../release-notes-202211.0.md                 |  3 +-
 .../patch-releases-202212.0.md                |  3 +-
 .../release-notes-202212.0.md                 |  3 +-
 .../security-release-notes-202212.0.md        | 37 ++++++++++---------
 .../security-release-notes-202302.0.md        |  5 ++-
 .../security-release-notes-202304.0.md        |  9 +++--
 .../release-notes-202307.0.md                 |  3 +-
 .../security-release-notes-202307.0.md        |  5 ++-
 .../release-notes-202311.0.md                 |  3 +-
 .../releases/release-notes/release-notes.md   |  3 +-
 .../security-release-notes-202306.0.md        | 27 +++++++-------
 .../security-release-notes-202309.0.md        |  9 +++--
 .../security-release-notes-202312.0.md        |  3 +-
 docs/about/all/releases/releases.md           | 18 +--------
 .../back-office-for-marketplace-operator.md   |  3 +-
 .../marketplace-b2b-suite.md                  |  3 +-
 .../marketplace-b2c-suite.md                  |  3 +-
 .../marketplace-concept.md                    |  3 +-
 .../marketplace-personas.md                   |  3 +-
 .../marketplace-storefront.md                 |  3 +-
 .../merchant-onboarding.md                    |  3 +-
 .../spryker-marketplace/merchant-portal.md    |  3 +-
 .../spryker-marketplace.md                    |  3 +-
 docs/about/all/support/case-escalation.md     |  3 +-
 docs/about/all/support/escalations.md         |  8 +---
 docs/about/all/support/getting-support.md     | 18 +--------
 .../support/guidelines-for-new-gdpr-rules.md  | 18 +--------
 .../all/support/handling-security-issues.md   | 18 +--------
 .../all/support/how-spryker-support-works.md  |  8 +---
 .../support/how-to-contact-spryker-support.md |  8 +---
 ...-to-get-the-most-out-of-spryker-support.md |  8 +---
 ...e-secrets-with-the-spryker-support-team.md | 12 ++----
 .../support/how-to-use-the-support-portal.md  |  8 +---
 .../special-prepare-for-a-busy-season.md      |  8 +---
 docs/about/all/support/understand-slas.md     | 12 ++----
 ...erstanding-project-and-core-level-fixes.md |  8 +---
 .../support/understanding-ticket-status.md    |  8 +---
 docs/about/all/whats-new/ie11-end-of-life.md  |  3 +-
 ...inimum-version-for-all-spryker-projects.md |  3 +-
 .../2019.11-security-audit-by-sektioneins.md  | 18 +--------
 ...ion-test-by-port-zero-executive-summary.md | 10 +----
 docs/about/all/whats-new/security-updates.md  |  3 +-
 .../whats-new/supported-versions-of-php.md    | 18 +--------
 .../upcoming-major-module-releases.md         |  8 +---
 docs/about/all/whats-new/whats-new.md         | 18 +--------
 47 files changed, 115 insertions(+), 298 deletions(-)

diff --git a/docs/about/all/docs-updates.md b/docs/about/all/docs-updates.md
index 162814ded64..fd97568db29 100644
--- a/docs/about/all/docs-updates.md
+++ b/docs/about/all/docs-updates.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/docs-updates.html
 ---
 title: Docs updates
 description: Spryker docs release notes
@@ -6,6 +5,8 @@ template: concept-topic-template
 last_updated: Jan 5, 2024
 redirect_from:
 - /docs/scos/user/intro-to-spryker/docs-release-notes.html
+- /docs/scos/user/intro-to-spryker/docs-updates.html
+
 ---
 
 ## January 2024
diff --git a/docs/about/all/intro-to-spryker.md b/docs/about/all/intro-to-spryker.md
index 3fb8a78cdc0..675ed71429e 100644
--- a/docs/about/all/intro-to-spryker.md
+++ b/docs/about/all/intro-to-spryker.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/intro-to-spryker.html
 ---
 title: Intro to Spryker
 description: The Spryker Commerce OS or SCOS is a completely modular, API-first, headless commerce technology for transactional business models in a B2B or B2C context.
@@ -7,30 +6,7 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/about-spryker
 originalArticleId: 0798f4ee-6a6b-46ed-baa8-e7e885700585
 redirect_from:
-  - /2021080/docs/about-spryker
-  - /2021080/docs/en/about-spryker
-  - /docs/about-spryker
-  - /docs/en/about-spryker
-  - /v5/docs/about-spryker
-  - /v5/docs/en/about-spryker
-  - /v4/docs/about-spryker
-  - /v4/docs/en/about-spryker
-  - /v4/docs/understanding-spryker
-  - /v4/docs/en/understanding-spryker
-  - /v3/docs/about-spryker
-  - /v3/docs/en/about-spryker
-  - /v3/docs/understanding-spryker
-  - /v3/docs/en/understanding-spryker
-  - /v2/docs/about-spryker
-  - /v2/docs/en/about-spryker
-  - /v2/docs/understanding-spryker
-  - /v2/docs/en/understanding-spryker
-  - /v1/docs/about-spryker
-  - /v1/docs/en/about-spryker
-  - /v1/docs/understanding-spryker
-  - /v1/docs/en/understanding-spryker
-  - /v6/docs/about-spryker
-  - /v6/docs/en/about-spryker
+  - /docs/scos/user/intro-to-spryker/intro-to-spryker.html
   - /docs/scos/user/intro-to-spryker/whats-new/roadmap.html
   - /docs/fes/dev/launching-storefronts.html
   - /docs/fes/dev/installing-applications.html
diff --git a/docs/about/all/releases/release-notes/release-notes-202211.0/release-notes-202211.0.md b/docs/about/all/releases/release-notes/release-notes-202211.0/release-notes-202211.0.md
index 1e08a91c41c..e5a2f56b060 100644
--- a/docs/about/all/releases/release-notes/release-notes-202211.0/release-notes-202211.0.md
+++ b/docs/about/all/releases/release-notes/release-notes-202211.0/release-notes-202211.0.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202211.0/release-notes-202211.0.html
 ---
 title: Release notes 202211.0
 last_updated: November 22, 2022
@@ -6,6 +5,8 @@ template: concept-topic-template
 description: Release notes for the Spryker SCOS release 202211.0
 redirect_from:  
   - /docs/marketplace/user/intro-to-spryker-marketplace/release-notes/release-notes-202211.0.html
+  - /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202211.0/release-notes-202211.0.html
+
 ---
 
 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.
diff --git a/docs/about/all/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.md b/docs/about/all/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.md
index 16376d4ee2f..a0a343f1885 100644
--- a/docs/about/all/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.md
+++ b/docs/about/all/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.html
 ---
 title: Patch releases 202212.0
 description: Patch releases for the Spryker release 202212.0
@@ -6,6 +5,8 @@ last_updated: Jan 31, 2023
 template: concept-topic-template
 redirect_from:
   - /docs/marketplace/user/intro-to-spryker-marketplace/release-notes/release-notes-202212.0/patch-releases-202212.0.html
+  - /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.html
+
 ---
 
 {% include scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.md %} <!-- To edit, see /_includes/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.md-->
diff --git a/docs/about/all/releases/release-notes/release-notes-202212.0/release-notes-202212.0.md b/docs/about/all/releases/release-notes/release-notes-202212.0/release-notes-202212.0.md
index db859b25b2e..57bb4d18171 100644
--- a/docs/about/all/releases/release-notes/release-notes-202212.0/release-notes-202212.0.md
+++ b/docs/about/all/releases/release-notes/release-notes-202212.0/release-notes-202212.0.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/release-notes-202212.0.html
 ---
 title: Release notes 202212.0
 description: Release notes for the Spryker SCOS release 202212.0
@@ -7,6 +6,8 @@ template: concept-topic-template
 redirect_from:
   - /docs/marketplace/user/intro-to-spryker-marketplace/release-notes-202212.0/release-notes-202212.0.html
   - /docs/marketplace/user/intro-to-spryker-marketplace/release-notes/release-notes-202212.0/release-notes-202212.0.html
+  - /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/release-notes-202212.0.html
+
 ---
 
 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.
diff --git a/docs/about/all/releases/release-notes/release-notes-202212.0/security-release-notes-202212.0.md b/docs/about/all/releases/release-notes/release-notes-202212.0/security-release-notes-202212.0.md
index 335c41bcd7a..050e7456f94 100644
--- a/docs/about/all/releases/release-notes/release-notes-202212.0/security-release-notes-202212.0.md
+++ b/docs/about/all/releases/release-notes/release-notes-202212.0/security-release-notes-202212.0.md
@@ -1,10 +1,11 @@
-  - /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/security-release-notes-202212.0.html
 ---
 title: Security release notes 202212.0
 description: Security release notes for the Spryker Product release 202212.0
 last_updated: Dec 21, 2022
 template: concept-topic-template
 redirect_from:
+- /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/security-release-notes-202212.0.html
+
 ---
 
 The following information pertains to security-related issues that have been recently resolved. All issues are listed by description and affected modules.
@@ -43,7 +44,7 @@ composer update spryker/cms-gui`
 ```
 3. Add `Spryker\Zed\Gui\Communication\Plugin\Form\SanitizeXssTypeExtensionFormPlugin` to `\Pyz\Zed\Form\FormDependencyProvider::getFormPlugins()` on the project level.
 
-## Twig - twig could load a template outside of a configured directory when the filesystem loader was used 
+## Twig - twig could load a template outside of a configured directory when the filesystem loader was used
 There was a vulnerability in PHP package twig/twig. When using the filesystem loader to load templates for which the name is user input, it was possible to use the source or include a statement to read arbitrary files from outside of the templates directory.
 
 **Changes:**
@@ -77,7 +78,7 @@ WishlistPage module:
 spryker/wishlist (8.6.0 or earlier)
 
 **How to get the fix:**
-1. Update the module: 
+1. Update the module:
 ```bash
 `composer update spryker/wishlist`
 ```
@@ -89,18 +90,18 @@ spryker/wishlist (8.6.0 or earlier)
 
 ## User enumeration when creating a customer via the API
 It was possible to enumerate users if creating them via the API. The message in response was "Customer with this email already exists."
- 
+
 **Changes:**
 The response message has been changed as follows: "If this email address is already in use, you will receive a password reset link. Otherwise you must first validate your e-mail address to finish registration. Please check your e-mail."
 
 **Affected modules:**
-No changes. 
+No changes.
 
 **How to get the fix:**
 Update the translation in the `data/import/common/common/glossary.csv for customer.authorization.invalid_account` key.
 
-## ZED token default value can be empty 
-The default Zed tokens could be empty if it was not set during installation. 
+## ZED token default value can be empty
+The default Zed tokens could be empty if it was not set during installation.
 
 **Changes:**
 We've removed the default value `SPRYKER_ZED_REQUEST_TOKEN`. The value has to be set or the fallback value must be properly handled with an exception.
@@ -189,13 +190,13 @@ CustomerPage module:
 - Adjusted `RegisterForm::addLastNameField)` by adding field validation to avoid special characters.
 
 **Affected modules:**
-- spryker/customer (7.45.0 or earlier)	
-- spryker/sales (11.32.0 or earlier)	
-- spryker/user (3.13.6 or earlier)	
+- spryker/customer (7.45.0 or earlier)
+- spryker/sales (11.32.0 or earlier)
+- spryker/user (3.13.6 or earlier)
 
 
 **How to get the fix:**
-1. Update the modules: 
+1. Update the modules:
 ```bash
 composer update spryker/company-user-gui
 ```
@@ -218,7 +219,7 @@ spryker/customer: 7.46.0
 spryker/merchant-profile-merchant-portal-gui: 1.6.0
 spryker/merchant-user-gui: 1.2.0
 spryker/sales: 11.33.0
-spryker/user: 3.14.0	
+spryker/user: 3.14.0
 spryker/user-merchant-portal-gui: 1.6.0
 spryker-shop/company-page: 2.20.0
 spryker-shop/customer-page: 2.39.0
@@ -235,7 +236,7 @@ spryker/application (3.28.0 or earlier)
 
 
 **How to get the fix:**
-1. Update the module: 
+1. Update the module:
 ```bash
 composer update spryker/application
 ```
@@ -255,7 +256,7 @@ Adjusted `GraphController::drawAction()`, so that if format is not supported, an
 - spryker/state-machine (2.15.1 or less)
 
 **How to get the fix:**
-1. Update the following modules: 
+1. Update the following modules:
 ```bash
 composer update spryker/oms
 ```
@@ -278,7 +279,7 @@ CompanyUnitAddressGui module:
 spryker/company-unit-address-gui (1.1.0 or earlier)
 
 **How to get the fix:**
-1. Update the modules: 
+1. Update the modules:
 ```bash
 composer update spryker/company-unit-address-gui
 ```
@@ -322,7 +323,7 @@ codeception/codeception (3.1.3 or less, and 4.0.0 - 4.1.21)
 
 **How to get the fix:**
 1. Change  *codeception/codeception* version to ^4.1.22 in composer.json on the project level.
-2. Update this module: 
+2. Update this module:
 ```bash
 composer update codeception/codeception
 ```
@@ -354,7 +355,7 @@ spryker/gui (3.43.0 or earlier)
 composer update spryker/gui
 ```
 2. Make sure that for the spryker/gui module, the current version is equal to or later than 3.43.1.
-3. Run the following command: 
+3. Run the following command:
 ```bash
 npm list <packagename>
 ```
@@ -429,7 +430,7 @@ spryker/company-role-gui (1.6.1 or earlier)
 **How to get the fix:**
 Update the modules:
 ```bash
-composer update spryker/company-role-gui 
+composer update spryker/company-role-gui
 ```
 Make sure that for the spryker/company-role-gui module, the current version is equal to or later than 1.6.2.
 
diff --git a/docs/about/all/releases/release-notes/release-notes-202302.0/security-release-notes-202302.0.md b/docs/about/all/releases/release-notes/release-notes-202302.0/security-release-notes-202302.0.md
index 377d8af9684..7f9465cc55c 100644
--- a/docs/about/all/releases/release-notes/release-notes-202302.0/security-release-notes-202302.0.md
+++ b/docs/about/all/releases/release-notes/release-notes-202302.0/security-release-notes-202302.0.md
@@ -1,10 +1,11 @@
-  - /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202302.0/security-release-notes-202302.0.html
 ---
 title: Security release notes 202302.0
 description: Security release notes for the Spryker Product release 202302.0
 last_updated: Mar 21, 2023
 template: concept-topic-template
 redirect_from:
+- /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202302.0/security-release-notes-202302.0.html
+
 ---
 
 This document describes the security-related issues we have recently resolved. All issues are listed by description and affected modules.
@@ -88,7 +89,7 @@ composer require spryker/sales:"~11.<your-minor>.<your-patch>"
 composer show spryker/sales # Verify the version
 ```
 
-When upgrading your `spryker/sales` module next time, consider selecting your next version according to the following guidelines. 
+When upgrading your `spryker/sales` module next time, consider selecting your next version according to the following guidelines.
 
 ### Upgrade on spryker/sales module versions 11.36.0 or later
 
diff --git a/docs/about/all/releases/release-notes/release-notes-202304.0/security-release-notes-202304.0.md b/docs/about/all/releases/release-notes/release-notes-202304.0/security-release-notes-202304.0.md
index f4f57e41678..3911e66bb1c 100644
--- a/docs/about/all/releases/release-notes/release-notes-202304.0/security-release-notes-202304.0.md
+++ b/docs/about/all/releases/release-notes/release-notes-202304.0/security-release-notes-202304.0.md
@@ -1,10 +1,11 @@
-  - /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202304.0/security-release-notes-202304.0.html
 ---
 title: Security release notes 202304.0
 description: Security release notes for the Spryker Product release 202304.0
 last_updated: Apr 21, 2023
 template: concept-topic-template
 redirect_from:
+- /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202304.0/security-release-notes-202304.0.html
+
 ---
 
 The following information pertains to security-related issues that have been recently resolved. All issues are listed by description and affected modules.
@@ -105,7 +106,7 @@ composer require spryker/cms:"~7.12.0"
 composer show spryker/cms # Verify the version
 ```
 
-2. Update `spryker/cms-block-gui`: 
+2. Update `spryker/cms-block-gui`:
    * If your version of `spryker/cms-block-gui` is earlier than 2.0.0, update it to version 2.10.0:
     ```bash
     composer require spryker/cms-block-gui:"~2.10.0"
@@ -285,7 +286,7 @@ class RabbitMqConfig extends SprykerRabbitMqConfig
             CustomerStorageConfig::CUSTOMER_INVALIDATED_SYNC_STORAGE_QUEUE,
         ];
     }
-    
+
     ...
 }
 ```
@@ -426,7 +427,7 @@ class SynchronizationDependencyProvider extends SprykerSynchronizationDependency
 
 In this case, an outdated version of jQuery was used (3.5.1). This version was released on 4 May, 2020 and affected by publicly known vulnerabilities.
 
-### Changes 
+### Changes
 
 Updated JQuery to the required version 3.6.3.
 
diff --git a/docs/about/all/releases/release-notes/release-notes-202307.0/release-notes-202307.0.md b/docs/about/all/releases/release-notes/release-notes-202307.0/release-notes-202307.0.md
index 07dd0c1ab97..d5767fd2f91 100644
--- a/docs/about/all/releases/release-notes/release-notes-202307.0/release-notes-202307.0.md
+++ b/docs/about/all/releases/release-notes/release-notes-202307.0/release-notes-202307.0.md
@@ -1,10 +1,11 @@
-  - /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202307.0/release-notes-202307.0.html
 ---
 title: Release notes 202307.0
 description: Release notes for the Spryker SCOS release 202307.0
 last_updated: Jul 31, 2023
 template: concept-topic-template
 redirect_from:
+- /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202307.0/release-notes-202307.0.html
+
 ---
 
 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.
diff --git a/docs/about/all/releases/release-notes/release-notes-202307.0/security-release-notes-202307.0.md b/docs/about/all/releases/release-notes/release-notes-202307.0/security-release-notes-202307.0.md
index 6c4dd213fbd..7967438514d 100644
--- a/docs/about/all/releases/release-notes/release-notes-202307.0/security-release-notes-202307.0.md
+++ b/docs/about/all/releases/release-notes/release-notes-202307.0/security-release-notes-202307.0.md
@@ -1,10 +1,11 @@
-  - /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202307.0/security-release-notes-202307.0.html
 ---
 title: Security release notes 202307.0
 description: Security release notes for the Spryker Summer 2023 Cross-Product Release
 last_updated: Jul 26, 2023
 template: concept-topic-template
 redirect_from:
+- /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202307.0/security-release-notes-202307.0.html
+
 ---
 
 The following information pertains to security-related issues that have been recently resolved. All issues are listed by description and affected modules.
@@ -13,7 +14,7 @@ If you need any additional support with this content, [contact our support](http
 
 ## Directory traversal in ZED
 
-It was possible to exploit a directory traversal vulnerability affecting the backend function of drawing graphs in order to determine whether a directory or an XML file exists on the file system. This was possible by submitting a malicious value in the process parameter within the URL of the affected function. 
+It was possible to exploit a directory traversal vulnerability affecting the backend function of drawing graphs in order to determine whether a directory or an XML file exists on the file system. This was possible by submitting a malicious value in the process parameter within the URL of the affected function.
 
 **Introduced changes:**
 Proper input validation controls have been implemented for the vulnerable parameter.
diff --git a/docs/about/all/releases/release-notes/release-notes-202311.0/release-notes-202311.0.md b/docs/about/all/releases/release-notes/release-notes-202311.0/release-notes-202311.0.md
index 99478ad0be6..79f1827a6a9 100644
--- a/docs/about/all/releases/release-notes/release-notes-202311.0/release-notes-202311.0.md
+++ b/docs/about/all/releases/release-notes/release-notes-202311.0/release-notes-202311.0.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202311.0/release-notes-202311.0.html
 ---
 title: Release notes 202311.0
 description: Release notes for the Spryker SCOS release 202311.0
@@ -6,6 +5,8 @@ last_updated: Nov 7, 2023
 template: concept-topic-template
 redirect_from:
 - /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202204.0/release-notes-202204.0.html
+- /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202311.0/release-notes-202311.0.html
+
 ---
 
 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.
diff --git a/docs/about/all/releases/release-notes/release-notes.md b/docs/about/all/releases/release-notes/release-notes.md
index 26fab71b26b..1add842ac60 100644
--- a/docs/about/all/releases/release-notes/release-notes.md
+++ b/docs/about/all/releases/release-notes/release-notes.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes.html
 ---
 title: Release Notes
 description: The article describes the release flow of features and enhancements.
@@ -7,6 +6,8 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/release-notes
 originalArticleId: 2da5568d-0a6b-4d0a-945f-8de92cb69ee1
 redirect_from:
+- /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes.html
+
 related:
   - title: Release notes 202204.0
     link: docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202204.0/release-notes-202204.0.html
diff --git a/docs/about/all/releases/release-notes/security-release-notes-202306.0.md b/docs/about/all/releases/release-notes/security-release-notes-202306.0.md
index c3a518f0c1f..9c452a20854 100644
--- a/docs/about/all/releases/release-notes/security-release-notes-202306.0.md
+++ b/docs/about/all/releases/release-notes/security-release-notes-202306.0.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202306.0.html
 ---
 title: Security release notes 202306.0
 description: Security release notes for the Spryker Product release 202306.0
@@ -6,19 +5,21 @@ last_updated: Jul 11, 2023
 template: concept-topic-template
 redirect_from:
     - /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202306.0/security-release-notes-202306.0.html
+    - /docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202306.0.html
+
 ---
 
 The following information pertains to security-related issues that have been recently resolved. All issues are listed by description and affected modules.
 
 If you need any additional support with this content, [contact our support](https://support.spryker.com/). If you found a new security vulnerability, inform us through [security@spryker.com](mailto:security@spryker.com).
 
-## Stored XSS in product pages 
+## Stored XSS in product pages
 
 Administrators can place a malicious payload into the description section of new and existing product pages in the Back Office application. This payload is then executed to all users of the shop that visit the affected product pages, resulting in a Cross-Site Scripting (XSS) vulnerability.
 
 ### Affected modules
 
-`spryker/product-management`: 0.19.3-0.19.35 
+`spryker/product-management`: 0.19.3-0.19.35
 
 ### Introduced changes
 
@@ -45,17 +46,17 @@ composer require spryker/product-management:"~0.19.36" spryker/gui:"~3.48.0" spr
 composer show spryker/product-management # Verify the version
 ```
 
-## Cross-company role manipulation 
+## Cross-company role manipulation
 
-Due to missing access validation controls on the backend, an administrator user of a company was able to create and update roles for other companies. This was possible due to the possibility to manipulate the company ID parameter included in the HTTP requests of the role creation functionality. 
+Due to missing access validation controls on the backend, an administrator user of a company was able to create and update roles for other companies. This was possible due to the possibility to manipulate the company ID parameter included in the HTTP requests of the role creation functionality.
 
 ### Affected modules
 
-`spryker-shop/company-page`: 1.0.0-2.21.0 
+`spryker-shop/company-page`: 1.0.0-2.21.0
 
 ### Introduced changes
 
-Access validation controls have been implemented to prevent administrators from being able to create and edit roles for other companies. 
+Access validation controls have been implemented to prevent administrators from being able to create and edit roles for other companies.
 
 ### How to get the fix
 
@@ -78,7 +79,7 @@ Attackers were able to bypass the redirect URL validation for URLs provided thro
 
 ### Introduced changes
 
-Additional validation controls have been implemented to prevent an attacker from being able to manipulate the location of the URL redirection. 
+Additional validation controls have been implemented to prevent an attacker from being able to manipulate the location of the URL redirection.
 
 ### How to get the fix
 
@@ -269,7 +270,7 @@ class ErrorHandlerConfig extends SprykerErrorHandlerConfigAlias
 13. Register plugins in `src/Pyz/Yves/EventDispatcher/EventDispatcherDependencyProvider.php`:
 
 ```php
-class EventDispatcherDependencyProvider extends SprykerEventDispatcherDependencyProvider 
+class EventDispatcherDependencyProvider extends SprykerEventDispatcherDependencyProvider
 {
 ...
     protected function getEventDispatcherPlugins(): array
@@ -306,7 +307,7 @@ console transfer:generate
 4. Register plugins in `src/Pyz/Zed/EventDispatcher/EventDispatcherDependencyProvider.php`:
 
 ```php
-class EventDispatcherDependencyProvider extends SprykerEventDispatcherDependencyProvider 
+class EventDispatcherDependencyProvider extends SprykerEventDispatcherDependencyProvider
 {
 ...
     protected function getEventDispatcherPlugins(): array
@@ -358,7 +359,7 @@ $config[SecurityBlockerMerchantPortalConstants::MERCHANT_PORTAL_USER_BLOCKING_TT
 $config[SecurityBlockerMerchantPortalConstants::MERCHANT_PORTAL_USER_BLOCKING_NUMBER_OF_ATTEMPTS] = 9;
 ```
 
-7. Add translations to `data/import/common/common/glossary.csv` : 
+7. Add translations to `data/import/common/common/glossary.csv` :
 
 ```csv
 security_blocker_merchant_portal_gui.error.account_blocked,"Too many log in attempts from your address. Please wait %minutes% minutes before trying again.",en_US
@@ -477,7 +478,7 @@ composer show spryker/merchant-profile-gui # Verify the version
 
 ## Outdated third-party library guzzlehttp/psr7
 
-An outdated version of the `guzzlehttp/psr7` library was identified to affect Spryker’s applications. The version in use, 2.4.3, was affected by a publicly known vulnerability that could let an attacker sneak in a newline (\n) into both the header names and values (CVE-2023-29197). 
+An outdated version of the `guzzlehttp/psr7` library was identified to affect Spryker’s applications. The version in use, 2.4.3, was affected by a publicly known vulnerability that could let an attacker sneak in a newline (\n) into both the header names and values (CVE-2023-29197).
 
 ### Affected modules
 
@@ -546,7 +547,7 @@ The following security-related HTTP headers can be implemented:
 
 ### How to get the fix
 
-To implement a fix for this vulnerability: 
+To implement a fix for this vulnerability:
 
 1. Update the `event-dispatcher`, `glue-backend-api-application`, `glue-storefront-api-application`, `HTTP`, and `merchant-portal-application` modules:
 
diff --git a/docs/about/all/releases/release-notes/security-release-notes-202309.0.md b/docs/about/all/releases/release-notes/security-release-notes-202309.0.md
index 2a7d251fd6f..053f4172b67 100644
--- a/docs/about/all/releases/release-notes/security-release-notes-202309.0.md
+++ b/docs/about/all/releases/release-notes/security-release-notes-202309.0.md
@@ -1,10 +1,11 @@
-  - /docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202309.0.html
 ---
 title: Security release notes 202309.0
 description: Security release notes for 202309.0
 last_updated: Oct 4, 2023
 template: concept-topic-template
 redirect_from:
+- /docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202309.0.html
+
 ---
 
 The following information pertains to security-related issues that have been recently resolved. All issues are listed by description and affected modules.
@@ -27,7 +28,7 @@ Proper validation controls have been implemented for the files uploaded via the
 
 ### How to get the fix
 
-To implement a fix for this vulnerability: 
+To implement a fix for this vulnerability:
 
 1. Upgrade the `spryker/file-manager` module version to 2.3.0:
 
@@ -54,7 +55,7 @@ composer show spryker/file-manager-gui # Verify the version
 
 ```bash
 composer require spryker/file-manager-data-import:"~2.1.0"
-composer show spryker/file-manager-data-import # Verify the version 
+composer show spryker/file-manager-data-import # Verify the version
 ```
 
 5. Upgrade the `spryker/price-product-schedule-gui` module version to 2.6.0:
@@ -163,7 +164,7 @@ The login portal was vulnerable to credential stuffing—an attack in which an a
 
 ### Introduced changes
 
-Possibility to limit the number of login attempts performed from a single IP address. 
+Possibility to limit the number of login attempts performed from a single IP address.
 
 ### How to get the fix
 
diff --git a/docs/about/all/releases/release-notes/security-release-notes-202312.0.md b/docs/about/all/releases/release-notes/security-release-notes-202312.0.md
index 9bf2c1f9ba1..fe04a2ef0e5 100644
--- a/docs/about/all/releases/release-notes/security-release-notes-202312.0.md
+++ b/docs/about/all/releases/release-notes/security-release-notes-202312.0.md
@@ -1,10 +1,11 @@
-  - /docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202312.0.html
 ---
 title: Security release notes 202312.0
 description: Security release notes for 202312.0
 last_updated: Dec 18, 2023
 template: concept-topic-template
 redirect_from:
+- /docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202312.0.html
+
 ---
 
 The following information pertains to security-related issues that have been recently resolved. All issues are listed by description and affected modules.
diff --git a/docs/about/all/releases/releases.md b/docs/about/all/releases/releases.md
index 21bbb9be7bc..183616ce8ad 100644
--- a/docs/about/all/releases/releases.md
+++ b/docs/about/all/releases/releases.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/releases/releases.html
 ---
 title: Releases
 description: This section contains the notes for each release made by Spryker.
@@ -7,22 +6,7 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/releases
 originalArticleId: e2f76a3b-1e2e-4c57-8812-bf46dac54b10
 redirect_from:
-  - /2021080/docs/releases
-  - /2021080/docs/en/releases
-  - /docs/releases
-  - /docs/en/releases
-  - /v5/docs/releases
-  - /v5/docs/en/releases
-  - /v4/docs/releases
-  - /v4/docs/en/releases
-  - /v3/docs/releases
-  - /v3/docs/en/releases
-  - /v2/docs/releases
-  - /v2/docs/en/releases
-  - /v1/docs/releases
-  - /v1/docs/en/releases
-  - /v6/docs/releases
-  - /v6/docs/en/releases
+  - /docs/scos/user/intro-to-spryker/releases/releases.html
   - /docs/scos/user/intro-to-spryker/releases/releases-archive.html
   - /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-april-1-2017.html
   - /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-april-2-2017.html
diff --git a/docs/about/all/spryker-marketplace/back-office-for-marketplace-operator.md b/docs/about/all/spryker-marketplace/back-office-for-marketplace-operator.md
index 317f5ff99a7..3657a2b78df 100644
--- a/docs/about/all/spryker-marketplace/back-office-for-marketplace-operator.md
+++ b/docs/about/all/spryker-marketplace/back-office-for-marketplace-operator.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/spryker-marketplace/back-office-for-marketplace-operator.html
 ---
 title: Back Office for Marketplace Operator
 description: This document describes how a marketplace operator works in the Back Office.
@@ -6,6 +5,8 @@ template: concept-topic-template
 last_updated: Sep 21, 2023
 redirect_from:
   - /docs/marketplace/user/intro-to-spryker-marketplace/back-office-for-marketplace-operator.html
+  - /docs/scos/user/intro-to-spryker/spryker-marketplace/back-office-for-marketplace-operator.html
+
 ---
 
 A *marketplace operator* is a company that owns the marketplace. In a marketplace business model, one or more of such a company's employees represent a marketplace operator and manage the store. We call such users as [marketplace administrators](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-personas.html#marketplace-administrator). Depending on the marketplace model, the marketplace operator either manages only other merchants' orders or also sells products as a [main merchant](/docs/pbc/all/merchant-management/{{site.version}}/marketplace/marketplace-merchant-feature-overview/main-merchant.html)).  
diff --git a/docs/about/all/spryker-marketplace/marketplace-b2b-suite.md b/docs/about/all/spryker-marketplace/marketplace-b2b-suite.md
index 9506c692ec8..4884dc63800 100644
--- a/docs/about/all/spryker-marketplace/marketplace-b2b-suite.md
+++ b/docs/about/all/spryker-marketplace/marketplace-b2b-suite.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2b-suite.html
 ---
 title: Marketplace B2B Suite
 description: The Spryker Marketplace B2B Demo Shop is a showcase that demonstrates ready-to-use Marketplace B2B-specific Spryker features in a live implementation.
@@ -6,6 +5,8 @@ last_updated: May 12, 2022
 template: concept-topic-template
 redirect_from:
   - /docs/marketplace/user/intro-to-spryker-marketplace/marketplace-b2b-demo-shop.html
+  - /docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2b-suite.html
+
 ---
 
 The Spryker B2B Marketplace Demo Shop is a collection of ready-to-use B2B-Marketplace-specific features.
diff --git a/docs/about/all/spryker-marketplace/marketplace-b2c-suite.md b/docs/about/all/spryker-marketplace/marketplace-b2c-suite.md
index c41f28a4a6f..f17b88b953a 100644
--- a/docs/about/all/spryker-marketplace/marketplace-b2c-suite.md
+++ b/docs/about/all/spryker-marketplace/marketplace-b2c-suite.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2c-suite.html
 ---
 title: Marketplace B2C Suite
 description: The Spryker Marketplace B2C Demo Shop is a showcase that demonstrates ready-to-use Marketplace B2C-specific Spryker features in a live implementation.
@@ -6,6 +5,8 @@ last_updated: May 12, 2022
 template: concept-topic-template
 redirect_from:
   - /docs/marketplace/user/intro-to-spryker-marketplace/marketplace-b2c-demo-shop.html
+  - /docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2c-suite.html
+
 ---
 
 The Spryker B2C Marketplace Demo Shop is a collection of ready-to-use B2C-Marketplace-specific features.
diff --git a/docs/about/all/spryker-marketplace/marketplace-concept.md b/docs/about/all/spryker-marketplace/marketplace-concept.md
index 6b5e3f4aa39..e3450e9e208 100644
--- a/docs/about/all/spryker-marketplace/marketplace-concept.md
+++ b/docs/about/all/spryker-marketplace/marketplace-concept.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-concept.html
 ---
 title: Marketplace concept
 description: This document describes what a Marketplace is in the Spryker Commerce OS.
@@ -7,6 +6,8 @@ last_updated: Sep 21, 2023
 redirect_from:
   - /docs/marketplace/user/intro-to-the-spryker-marketplace/marketplace-concept.html
   - /docs/marketplace/user/intro-to-spryker-marketplace/marketplace-concept.html
+  - /docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-concept.html
+
 ---
 
 An online *Marketplace* is a type of e-commerce business where products or services are sold and fulfilled by multiple sellers (*merchants*). A growing number of large companies are adopting the Marketplace business model to create new revenue streams, differentiate from the competition, get a better ROI, and increase customer loyalty by adding more products or services to their assortment.
diff --git a/docs/about/all/spryker-marketplace/marketplace-personas.md b/docs/about/all/spryker-marketplace/marketplace-personas.md
index 011acff8957..db25084c355 100644
--- a/docs/about/all/spryker-marketplace/marketplace-personas.md
+++ b/docs/about/all/spryker-marketplace/marketplace-personas.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-personas.html
 ---
 title: Marketplace personas
 description: This document describes key users that cooperate in the Marketplace environment.
@@ -6,6 +5,8 @@ last_updated: Aug 31, 2022
 template: concept-topic-template
 redirect_from:
   - /docs/marketplace/user/intro-to-spryker-marketplace/marketplace-personas.html
+  - /docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-personas.html
+
 ---
 
 A marketplace extension provided by Spryker Cloud Commerce OS covers a wide range of needs for sellers and buyers and presupposes the fulfillment of multiple actions by various types of users in different areas of the Marketplace. This document describes the different types of users—personas that function within the Marketplace.
diff --git a/docs/about/all/spryker-marketplace/marketplace-storefront.md b/docs/about/all/spryker-marketplace/marketplace-storefront.md
index fbd072412a4..bbfb3772fdc 100644
--- a/docs/about/all/spryker-marketplace/marketplace-storefront.md
+++ b/docs/about/all/spryker-marketplace/marketplace-storefront.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-storefront.html
 ---
 title: Marketplace Storefront
 description: This document describes the peculiarities of the Marketplace Storefront application.
@@ -6,6 +5,8 @@ template: concept-topic-template
 last_updated: Sep 25, 2023
 redirect_from:
   - /docs/marketplace/user/intro-to-spryker-marketplace/marketplace-storefront.html
+  - /docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-storefront.html
+
 ---
 
 *Marketplace Storefront* is a web application designed for the [marketplace business model](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-concept.html). Based on the regular Storefront, it supports all [Spryker Commerce OS](/docs/scos/user/intro-to-spryker/intro-to-spryker.html) features. Marketplace functionality lets buyers browse for products and view and purchase them across different merchants.
diff --git a/docs/about/all/spryker-marketplace/merchant-onboarding.md b/docs/about/all/spryker-marketplace/merchant-onboarding.md
index d2ee872c92a..5db40267ab9 100644
--- a/docs/about/all/spryker-marketplace/merchant-onboarding.md
+++ b/docs/about/all/spryker-marketplace/merchant-onboarding.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/spryker-marketplace/merchant-onboarding.html
 ---
 title:  Merchant onboarding
 description: This document describes the onboarding process for merchants and gives step-by-step instructions for marketplace operators.
@@ -6,6 +5,8 @@ template: concept-topic-template
 redirect_from:
 last_updated: Mar 29, 2023
   - /docs/marketplace/user/intro-to-spryker-marketplace/merchant-onboarding.html
+  - /docs/scos/user/intro-to-spryker/spryker-marketplace/merchant-onboarding.html
+
 ---
 
 This document describes how to onboard merchants.
diff --git a/docs/about/all/spryker-marketplace/merchant-portal.md b/docs/about/all/spryker-marketplace/merchant-portal.md
index 11540cdd0f5..7569095bcb6 100644
--- a/docs/about/all/spryker-marketplace/merchant-portal.md
+++ b/docs/about/all/spryker-marketplace/merchant-portal.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/spryker-marketplace/merchant-portal.html
 ---
 title: Merchant Portal
 description: This document describes the peculiarities of the Merchant Portal application.
@@ -6,6 +5,8 @@ template: concept-topic-template
 last_updated: Dec 4, 2023
 redirect_from:
   - /docs/marketplace/user/intro-to-spryker-marketplace/merchant-portal.html
+  - /docs/scos/user/intro-to-spryker/spryker-marketplace/merchant-portal.html
+
 ---
 
 The Merchant Portal is a section from the Back office for the [Marketplace merchants](/docs/pbc/all/merchant-management/{{site.version}}/marketplace/marketplace-merchant-feature-overview/marketplace-merchant-feature-overview.html). After [installation](/docs/dg/dev/set-up-spryker-locally/install-spryker/install-spryker.html), the Merchant Portal is accessible via the this link: `http://mp.de.spryker.local/security-merchant-portal-gui/login`.
diff --git a/docs/about/all/spryker-marketplace/spryker-marketplace.md b/docs/about/all/spryker-marketplace/spryker-marketplace.md
index 48769e15a04..e1eea9108fb 100644
--- a/docs/about/all/spryker-marketplace/spryker-marketplace.md
+++ b/docs/about/all/spryker-marketplace/spryker-marketplace.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/spryker-marketplace/spryker-marketplace.html
 ---
 title: Spryker Marketplace
 description: This document is an overview of Spryker Marketplace
@@ -7,6 +6,8 @@ last_updated: Sep 25, 2023
 redirect_from:
   - /docs/marketplace/user/intro-to-the-spryker-marketplace/marketplace-concept.html
   - /docs/marketplace/user/intro-to-spryker-marketplace/intro-to-spryker-marketplace.html
+  - /docs/scos/user/intro-to-spryker/spryker-marketplace/spryker-marketplace.html
+
 ---
 
 
diff --git a/docs/about/all/support/case-escalation.md b/docs/about/all/support/case-escalation.md
index eacae2ed70e..de369fd0550 100644
--- a/docs/about/all/support/case-escalation.md
+++ b/docs/about/all/support/case-escalation.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/support/case-escalation.html
 ---
 title: Case escalation
 last_updated: Sep 6, 2021
@@ -7,7 +6,7 @@ originalLink: https://documentation.spryker.com/docs/scos/user/intro-to-spryker/
 originalArticleId: af927b8c-2fc0-46ab-a54d-4ae83d18ca89
 redirect_from:
   - /docs/scos/user/intro-to-spryker/support/understanding-ticket-status.html#how-are-bug-tickets-prioritized
-  - /2021080/docs/en/case-priorities
+  - /docs/scos/user/intro-to-spryker/support/case-escalation.html
   - /docs/scos/user/intro-to-spryker/support/business-impact-and-case-priorities.html
 ---
 
diff --git a/docs/about/all/support/escalations.md b/docs/about/all/support/escalations.md
index 3ba3f6c7262..08a7deb7549 100644
--- a/docs/about/all/support/escalations.md
+++ b/docs/about/all/support/escalations.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/support/escalations.html
 ---
 title: Escalations
 last_updated: Oct 25, 2021
@@ -6,12 +5,7 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/case-escalation
 originalArticleId: 42b43d4c-fb40-4663-a210-1bdea01b4b22
 redirect_from:
-  - /2021080/docs/case-escalation
-  - /2021080/docs/en/case-escalation
-  - /docs/case-escalation
-  - /docs/en/case-escalation
-  - /v6/docs/case-escalation
-  - /v6/docs/en/case-escalation
+- /docs/scos/user/intro-to-spryker/support/escalations.html
 ---
 
 You might wonder how we manage escalations. Let's start with how we define escalations at Spryker.
diff --git a/docs/about/all/support/getting-support.md b/docs/about/all/support/getting-support.md
index 999a5482d16..3cbb01d54aa 100644
--- a/docs/about/all/support/getting-support.md
+++ b/docs/about/all/support/getting-support.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/support/getting-support.html
 ---
 title: Getting support
 last_updated: Jun 16, 2021
@@ -6,22 +5,7 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/getting-support
 originalArticleId: db44af78-45b9-497b-a5b7-2474f1d1460b
 redirect_from:
-  - /2021080/docs/getting-support
-  - /2021080/docs/en/getting-support
-  - /docs/getting-support
-  - /docs/en/getting-support
-  - /v5/docs/getting-support
-  - /v5/docs/en/getting-support
-  - /v4/docs/getting-support
-  - /v4/docs/en/getting-support
-  - /v3/docs/getting-support
-  - /v3/docs/en/getting-support
-  - /v2/docs/getting-support
-  - /v2/docs/en/getting-support
-  - /v1/docs/getting-support
-  - /v1/docs/en/getting-support
-  - /v6/docs/getting-support
-  - /v6/docs/en/getting-support
+  - /docs/scos/user/intro-to-spryker/support/getting-support.html
   - /docs/scos/user/intro-to-spryker/support/handling-new-feature-requests.html
 related:
   - title: How to use the Support Portal
diff --git a/docs/about/all/support/guidelines-for-new-gdpr-rules.md b/docs/about/all/support/guidelines-for-new-gdpr-rules.md
index 51008d2d544..d4f1426a415 100644
--- a/docs/about/all/support/guidelines-for-new-gdpr-rules.md
+++ b/docs/about/all/support/guidelines-for-new-gdpr-rules.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/support/guidelines-for-new-gdpr-rules.html
 ---
 title: Guidelines for new GDPR rules
 description: GDPR contains rules relating to the protection and control of personal data.
@@ -7,22 +6,7 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/guidelines-for-new-gdpr-rules
 originalArticleId: 256c82f9-5bae-4788-ab23-1ed7398edb1a
 redirect_from:
-  - /2021080/docs/guidelines-for-new-gdpr-rules
-  - /2021080/docs/en/guidelines-for-new-gdpr-rules
-  - /docs/guidelines-for-new-gdpr-rules
-  - /docs/en/guidelines-for-new-gdpr-rules
-  - /v6/docs/guidelines-for-new-gdpr-rules
-  - /v6/docs/en/guidelines-for-new-gdpr-rules
-  - /v5/docs/guidelines-for-new-gdpr-rules
-  - /v5/docs/en/guidelines-for-new-gdpr-rules
-  - /v4/docs/guidelines-for-new-gdpr-rules
-  - /v4/docs/en/guidelines-for-new-gdpr-rules
-  - /v3/docs/guidelines-for-new-gdpr-rules
-  - /v3/docs/en/guidelines-for-new-gdpr-rules
-  - /v2/docs/guidelines-for-new-gdpr-rules
-  - /v2/docs/en/guidelines-for-new-gdpr-rules
-  - /v1/docs/guidelines-for-new-gdpr-rules
-  - /v1/docs/en/guidelines-for-new-gdpr-rules
+- /docs/scos/user/intro-to-spryker/support/guidelines-for-new-gdpr-rules.html
 ---
 
 {% info_block errorBox %}
diff --git a/docs/about/all/support/handling-security-issues.md b/docs/about/all/support/handling-security-issues.md
index d0700ce6f99..a0d620c0093 100644
--- a/docs/about/all/support/handling-security-issues.md
+++ b/docs/about/all/support/handling-security-issues.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/support/handling-security-issues.html
 ---
 title: Handling security issues
 description: Use this article to learn how to report a security issue and to understand how we handle these reports.
@@ -7,22 +6,7 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/handling-security-issues
 originalArticleId: f4e006a1-e49e-4d54-beac-f0cbea5ebff2
 redirect_from:
-  - /2021080/docs/handling-security-issues
-  - /2021080/docs/en/handling-security-issues
-  - /docs/handling-security-issues
-  - /docs/en/handling-security-issues
-  - /v5/docs/handling-security-issues
-  - /v5/docs/en/handling-security-issues
-  - /v4/docs/handling-security-issues
-  - /v4/docs/en/handling-security-issues
-  - /v3/docs/handling-security-issues
-  - /v3/docs/en/handling-security-issues
-  - /v2/docs/handling-security-issues
-  - /v2/docs/en/handling-security-issues
-  - /v1/docs/handling-security-issues
-  - /v1/docs/en/handling-security-issues
-  - /v6/docs/handling-security-issues
-  - /v6/docs/en/handling-security-issues
+- /docs/scos/user/intro-to-spryker/support/handling-security-issues.html
 ---
 
 If you find a security issue in a Spryker product, please report it to us.
diff --git a/docs/about/all/support/how-spryker-support-works.md b/docs/about/all/support/how-spryker-support-works.md
index a070e7bc313..a85daca99f4 100644
--- a/docs/about/all/support/how-spryker-support-works.md
+++ b/docs/about/all/support/how-spryker-support-works.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html
 ---
 title: How Spryker Support works
 last_updated: Jun 16, 2021
@@ -6,12 +5,7 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/how-spryker-support-works-1
 originalArticleId: 2923122e-fde2-4893-98df-1375f8cc7742
 redirect_from:
-  - /2021080/docs/how-spryker-support-works-1
-  - /2021080/docs/en/how-spryker-support-works-1
-  - /docs/how-spryker-support-works-1
-  - /docs/en/how-spryker-support-works-1
-  - /v6/docs/how-spryker-support-works-1
-  - /v6/docs/en/how-spryker-support-works-1
+- /docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html
 related:
   - title: How to get the most out of Spryker Support
     link: docs/scos/user/intro-to-spryker/support/how-to-get-the-most-out-of-spryker-support.html
diff --git a/docs/about/all/support/how-to-contact-spryker-support.md b/docs/about/all/support/how-to-contact-spryker-support.md
index 56ec3817688..50a371f0b22 100644
--- a/docs/about/all/support/how-to-contact-spryker-support.md
+++ b/docs/about/all/support/how-to-contact-spryker-support.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/support/how-to-contact-spryker-support.html
 ---
 title: How to contact Spryker Support
 last_updated: Jun 16, 2021
@@ -6,12 +5,7 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/how-to-contact-spryker-support
 originalArticleId: f9c8d398-7305-4a0c-9dbd-b88d5ce7f988
 redirect_from:
-  - /2021080/docs/how-to-contact-spryker-support
-  - /2021080/docs/en/how-to-contact-spryker-support
-  - /docs/how-to-contact-spryker-support
-  - /docs/en/how-to-contact-spryker-support
-  - /v6/docs/how-to-contact-spryker-support
-  - /v6/docs/en/how-to-contact-spryker-support
+- /docs/scos/user/intro-to-spryker/support/how-to-contact-spryker-support.html
 related:
   - title: How Spryker Support works
     link: docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html
diff --git a/docs/about/all/support/how-to-get-the-most-out-of-spryker-support.md b/docs/about/all/support/how-to-get-the-most-out-of-spryker-support.md
index 54e7ae9762f..96230318227 100644
--- a/docs/about/all/support/how-to-get-the-most-out-of-spryker-support.md
+++ b/docs/about/all/support/how-to-get-the-most-out-of-spryker-support.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/support/how-to-get-the-most-out-of-spryker-support.html
 ---
 title: How to get the most out of Spryker Support
 last_updated: Jun 16, 2021
@@ -6,12 +5,7 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/how-to-get-the-most-out-of-spryker-support
 originalArticleId: 3ab286da-5f06-4035-bc52-0b0237ed410f
 redirect_from:
-  - /2021080/docs/how-to-get-the-most-out-of-spryker-support
-  - /2021080/docs/en/how-to-get-the-most-out-of-spryker-support
-  - /docs/how-to-get-the-most-out-of-spryker-support
-  - /docs/en/how-to-get-the-most-out-of-spryker-support
-  - /v6/docs/how-to-get-the-most-out-of-spryker-support
-  - /v6/docs/en/how-to-get-the-most-out-of-spryker-support
+- /docs/scos/user/intro-to-spryker/support/how-to-get-the-most-out-of-spryker-support.html
 related:
   - title: How Spryker Support works
     link: docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html
diff --git a/docs/about/all/support/how-to-share-secrets-with-the-spryker-support-team.md b/docs/about/all/support/how-to-share-secrets-with-the-spryker-support-team.md
index 2b550daf85f..3d9cfa8465d 100644
--- a/docs/about/all/support/how-to-share-secrets-with-the-spryker-support-team.md
+++ b/docs/about/all/support/how-to-share-secrets-with-the-spryker-support-team.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/support/how-to-share-secrets-with-the-spryker-support-team.html
 ---
 title: How to share secrets with the Spryker Support Team
 description: Learn how to share secrets with the Spryker Support Team
@@ -7,12 +6,7 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/how-to-share-secrets-with-the-spryker-support-team
 originalArticleId: a52e18a4-1aee-4f08-a132-82940f1f207e
 redirect_from:
-  - /2021080/docs/how-to-share-secrets-with-the-spryker-support-team
-  - /2021080/docs/en/how-to-share-secrets-with-the-spryker-support-team
-  - /docs/how-to-share-secrets-with-the-spryker-support-team
-  - /docs/en/how-to-share-secrets-with-the-spryker-support-team
-  - /v6/docs/how-to-share-secrets-with-the-spryker-support-team
-  - /v6/docs/en/how-to-share-secrets-with-the-spryker-support-team
+- /docs/scos/user/intro-to-spryker/support/how-to-share-secrets-with-the-spryker-support-team.html
 ---
 
 This document explains how you can securely share secrets or credentials with the [Spryker Support Team](/docs/scos/user/intro-to-spryker/support/getting-support.html). In general, the safest way to share secrets is not to share them, but if the situation demands it, we ask you to share secrets only the way described in this document.
@@ -29,7 +23,7 @@ Register in our [Slack community](https://spryker.com/support/).
 
 ## Process for sharing the secrets
 
-Stick to the following process when sharing secrets with the Spryker Support Team. 
+Stick to the following process when sharing secrets with the Spryker Support Team.
 
 {% info_block warningBox %}
 
@@ -45,7 +39,7 @@ Do not include information on what the secret content is for—for example, if y
 
 {% endinfo_block %}
 
-2. In the **Case Details**, in the **Link Passphrase** field add the secret link. 
+2. In the **Case Details**, in the **Link Passphrase** field add the secret link.
 3. Create a comment on the case that the team must retrieve the secret link.
 3. The Team retrieves the link and then clears the field and provide a comment.
 4. Add the passphrase to the link in the same—now empty—field.
diff --git a/docs/about/all/support/how-to-use-the-support-portal.md b/docs/about/all/support/how-to-use-the-support-portal.md
index 2febc7030c1..e3c8ba70c8e 100644
--- a/docs/about/all/support/how-to-use-the-support-portal.md
+++ b/docs/about/all/support/how-to-use-the-support-portal.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/support/how-to-use-the-support-portal.html
 ---
 title: How to use the Support Portal
 last_updated: Sep 28, 2021
@@ -6,12 +5,7 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/how-to-use-the-support-portal
 originalArticleId: b215730b-98ee-4661-8281-c45104e51044
 redirect_from:
-  - /2021080/docs/how-to-use-the-support-portal
-  - /2021080/docs/en/how-to-use-the-support-portal
-  - /docs/how-to-use-the-support-portal
-  - /docs/en/how-to-use-the-support-portal
-  - /v6/docs/how-to-use-the-support-portal
-  - /v6/docs/en/how-to-use-the-support-portal
+- /docs/scos/user/intro-to-spryker/support/how-to-use-the-support-portal.html
 related:
   - title: How Spryker Support works
     link: docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html
diff --git a/docs/about/all/support/special-prepare-for-a-busy-season.md b/docs/about/all/support/special-prepare-for-a-busy-season.md
index 9f37b3f596b..ce648705294 100644
--- a/docs/about/all/support/special-prepare-for-a-busy-season.md
+++ b/docs/about/all/support/special-prepare-for-a-busy-season.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/support/special-prepare-for-a-busy-season.html
 ---
 title: Special- Prepare for a busy season
 last_updated: Jun 16, 2021
@@ -6,12 +5,7 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/special-prepare-for-a-busy-season
 originalArticleId: 03eeeab9-d5fd-4b18-80f9-5a1dd3fcf33e
 redirect_from:
-  - /2021080/docs/special-prepare-for-a-busy-season
-  - /2021080/docs/en/special-prepare-for-a-busy-season
-  - /docs/special-prepare-for-a-busy-season
-  - /docs/en/special-prepare-for-a-busy-season
-  - /v6/docs/special-prepare-for-a-busy-season
-  - /v6/docs/en/special-prepare-for-a-busy-season
+- /docs/scos/user/intro-to-spryker/support/special-prepare-for-a-busy-season.html
 ---
 
 This document helps you prepare for a traditionally very busy season of the year: Black Friday, Cyber Monday, and the Holiday Season but it helps you whenever you expect your shop to receive record-breaking traffic. In this document, you can find recommendations written for business decision-makers, hosting providers, and Spryker developers. So feel free to forward our recommendations to your colleagues!
diff --git a/docs/about/all/support/understand-slas.md b/docs/about/all/support/understand-slas.md
index 085f83b9db9..ec75287ded3 100644
--- a/docs/about/all/support/understand-slas.md
+++ b/docs/about/all/support/understand-slas.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/support/understand-slas.html
 ---
 title: Understand SLAs
 last_updated: Sep 6, 2021
@@ -6,12 +5,7 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/understand-slas
 originalArticleId: 8cc87de0-43f6-4d9c-b65b-3ec9cad7a38b
 redirect_from:
-  - /2021080/docs/understand-slas
-  - /2021080/docs/en/understand-slas
-  - /docs/understand-slas
-  - /docs/en/understand-slas
-  - /v6/docs/understand-slas
-  - /v6/docs/en/understand-slas
+- /docs/scos/user/intro-to-spryker/support/understand-slas.html
 ---
 
 Like any legal text, Service Level Agreements (SLAs) can be hard to understand for the uninitiated. We strive to keep our SLAs clear and comprehensive, but sometimes it is better to explain some core concepts more verbose.
@@ -39,7 +33,7 @@ To make sure that we resolve the right cases first, we need to triage and priori
 
 ## What you can expect from us
 
-In our SLAs, we guarantee certain [First Response Times](/docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html#first-response-time). 
+In our SLAs, we guarantee certain [First Response Times](/docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html#first-response-time).
 You can expect us to react to your cases within the time that is specified in your SLA. While we work to resolve high-priority issues as fast as possible, we do not and cannot guarantee resolution times for the issues you open with us because of the breadth of cases we offer to work on. Guaranteeing resolution times would make it necessary for us to make the definition of the cases we accept stricter, which ultimately will makes it harder and more bureaucratic for you to work with us.
 
 ### Infrastructure support
@@ -62,4 +56,4 @@ Also, subscribe to our new newsletter (soon to come) and be sure to check out ou
 This is a general recommendation that not only can teach you and your team how to build great shops with Spryker Code, but we offer several courses for all kinds of Spryker stakeholders. Currently, we offer developer courses, business courses, and sales courses with other interesting courses currently being developed.
 
 ### Learn more about how we work
-We are working on being more transparent about how we work internally because we believe it makes working with us easier. To learn about our processes, take a look at the other articles in the Support section of our documentation 
+We are working on being more transparent about how we work internally because we believe it makes working with us easier. To learn about our processes, take a look at the other articles in the Support section of our documentation
diff --git a/docs/about/all/support/understanding-project-and-core-level-fixes.md b/docs/about/all/support/understanding-project-and-core-level-fixes.md
index 6aa2934b937..3b611d3699b 100644
--- a/docs/about/all/support/understanding-project-and-core-level-fixes.md
+++ b/docs/about/all/support/understanding-project-and-core-level-fixes.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/support/understanding-project-and-core-level-fixes.html
 ---
 title: Understanding Project and Core Level Fixes
 last_updated: Jun 16, 2021
@@ -6,12 +5,7 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/understanding-project-and-core-level-fixes
 originalArticleId: cbc63cb1-4eb5-4d96-903a-b0eade141458
 redirect_from:
-  - /2021080/docs/understanding-project-and-core-level-fixes
-  - /2021080/docs/en/understanding-project-and-core-level-fixes
-  - /docs/understanding-project-and-core-level-fixes
-  - /docs/en/understanding-project-and-core-level-fixes
-  - /v6/docs/understanding-project-and-core-level-fixes
-  - /v6/docs/en/understanding-project-and-core-level-fixes
+- /docs/scos/user/intro-to-spryker/support/understanding-project-and-core-level-fixes.html
 ---
 
 This document explains the differences between project and core level fixes to problems and bugs.
diff --git a/docs/about/all/support/understanding-ticket-status.md b/docs/about/all/support/understanding-ticket-status.md
index 71ab9b012a8..6c6518501f3 100644
--- a/docs/about/all/support/understanding-ticket-status.md
+++ b/docs/about/all/support/understanding-ticket-status.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/support/understanding-ticket-status.html
 ---
 title: Understanding ticket status
 last_updated: Oct 8, 2021
@@ -6,12 +5,7 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/understanding-ticket-status
 originalArticleId: ca538168-f995-48b4-8caf-d295647d2701
 redirect_from:
-  - /2021080/docs/understanding-ticket-status
-  - /2021080/docs/en/understanding-ticket-status
-  - /docs/understanding-ticket-status
-  - /docs/en/understanding-ticket-status
-  - /v6/docs/understanding-ticket-status
-  - /v6/docs/en/understanding-ticket-status
+- /docs/scos/user/intro-to-spryker/support/understanding-ticket-status.html
 ---
 
 When you report an issue, and we discover an underlying problem with Spryker, we create a Jira Bug Ticket. Then, this ticket is handed over to our development department, and our colleagues evaluate how to address the problem best and resolve it. After the issue is resolved, it is then released to our repositories.
diff --git a/docs/about/all/whats-new/ie11-end-of-life.md b/docs/about/all/whats-new/ie11-end-of-life.md
index 09944bdcc32..ae1d1bdeac9 100644
--- a/docs/about/all/whats-new/ie11-end-of-life.md
+++ b/docs/about/all/whats-new/ie11-end-of-life.md
@@ -1,10 +1,11 @@
-  - /docs/scos/user/intro-to-spryker/whats-new/ie11-end-of-life.html
 ---
 title: IE11 end of life
 description: Microsoft announced that the Internet Explorer 11 desktop application would be retired on June 15, 2022, for specific versions of Windows 10. Legacy Internet Explorer-based websites and applications will continue to work with Microsoft Edge’s built-in Internet Explorer mode.
 last_updated: June 8, 2022
 template: concept-topic-template
 redirect_from:
+- /docs/scos/user/intro-to-spryker/whats-new/ie11-end-of-life.html
+
 ---
 
 Microsoft announced that the Internet Explorer 11 (IE11) desktop application would be retired on June 15, 2022, for specific versions of Windows 10. Legacy Internet Explorer-based websites and applications will continue to work with Microsoft Edge’s built-in Internet Explorer mode.
diff --git a/docs/about/all/whats-new/php8-as-a-minimum-version-for-all-spryker-projects.md b/docs/about/all/whats-new/php8-as-a-minimum-version-for-all-spryker-projects.md
index 18e39332136..fcd9e00db2b 100644
--- a/docs/about/all/whats-new/php8-as-a-minimum-version-for-all-spryker-projects.md
+++ b/docs/about/all/whats-new/php8-as-a-minimum-version-for-all-spryker-projects.md
@@ -1,10 +1,11 @@
-  - /docs/scos/user/intro-to-spryker/whats-new/php8-as-a-minimum-version-for-all-spryker-projects.html
 ---
 title: PHP 8.1 as the minimum version for all Spryker projects
 description: End of November 2022, Spryker will release a new version of its Demo Shops requiring PHP 8.1 as the minimum version.
 last_updated: November 22, 2022
 template: concept-topic-template
 redirect_from:
+- /docs/scos/user/intro-to-spryker/whats-new/php8-as-a-minimum-version-for-all-spryker-projects.html
+
 ---
 
 
diff --git a/docs/about/all/whats-new/security-audit-reports/2019.11-security-audit-by-sektioneins.md b/docs/about/all/whats-new/security-audit-reports/2019.11-security-audit-by-sektioneins.md
index ee7ccf5063f..67c94efe577 100644
--- a/docs/about/all/whats-new/security-audit-reports/2019.11-security-audit-by-sektioneins.md
+++ b/docs/about/all/whats-new/security-audit-reports/2019.11-security-audit-by-sektioneins.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/whats-new/security-audit-reports/2019.11-security-audit-by-sektioneins.html
 ---
 title: 2019.11 — Security audit by SektionEins
 description: This page contains the report of the audit performed on Spryker Commerce OS.
@@ -7,22 +6,7 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/security-audit
 originalArticleId: 7da78594-14c0-4a77-9296-4ad39a2c085a
 redirect_from:
-  - /2021080/docs/security-audit
-  - /2021080/docs/en/security-audit
-  - /docs/security-audit
-  - /docs/en/security-audit
-  - /v5/docs/security-audit
-  - /v5/docs/en/security-audit
-  - /v4/docs/security-audit
-  - /v4/docs/en/security-audit
-  - /v3/docs/security-audit
-  - /v3/docs/en/security-audit
-  - /v2/docs/security-audit
-  - /v2/docs/en/security-audit
-  - /v1/docs/security-audit
-  - /v1/docs/en/security-audit
-  - /v6/docs/security-audit
-  - /v6/docs/en/security-audit
+- /docs/scos/user/intro-to-spryker/whats-new/security-audit-reports/2019.11-security-audit-by-sektioneins.html
 related:
   - title: Code Sniffer
     link: docs/scos/dev/sdk/development-tools/code-sniffer.html
diff --git a/docs/about/all/whats-new/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.md b/docs/about/all/whats-new/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.md
index 144eaca3626..a1b0025ea7b 100644
--- a/docs/about/all/whats-new/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.md
+++ b/docs/about/all/whats-new/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/whats-new/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.html
 ---
 title: 2020.11 — Penetration test by Port Zero (executive summary)
 description: Results of penetration tests of the Spryker Commerce B2C and Spryker Commerce B2B.
@@ -7,15 +6,10 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/penetration-test-executive-summary
 originalArticleId: f8c99d22-23ad-4812-9eab-b7cd80bd2386
 redirect_from:
-  - /2021080/docs/penetration-test-executive-summary
-  - /2021080/docs/en/penetration-test-executive-summary
-  - /docs/penetration-test-executive-summary
-  - /docs/en/penetration-test-executive-summary
-  - /v6/docs/penetration-test-executive-summary
-  - /v6/docs/en/penetration-test-executive-summary
+- /docs/scos/user/intro-to-spryker/whats-new/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.html
 ---
 
-During October and November 2020 the “Spryker Commerce B2C” & “Spryker Commerce B2B” of Spryker Systems GmbH were tested for security vulnerabilities and risks. The penetration testers of Port Zero GmbH rated all security vulnerabilities and gave tips for improving and fixing the issues in the penetration test report. 
+During October and November 2020 the “Spryker Commerce B2C” & “Spryker Commerce B2B” of Spryker Systems GmbH were tested for security vulnerabilities and risks. The penetration testers of Port Zero GmbH rated all security vulnerabilities and gave tips for improving and fixing the issues in the penetration test report.
 
 The penetration test was conducted voluntarily and is based on the recognized industry standard of the "OWASP Testing Guide v4.1 (2020)" as well as on the "Implementation Concept for Penetration Tests" of the German Federal Office for Information Security.
 Overall, the security of *Spryker Commerce B2C* and *Spryker Commerce B2B* gave a positive impression. The penetration test revealed some information leakages, including subdomain names, software in use, version numbers, and TCP timestamps (all available without login). However, regarding Transport Layer Security (TLS), a very high-security standard (see Appendix) is in place. The security of the central authentication mechanisms and session management is working well.
diff --git a/docs/about/all/whats-new/security-updates.md b/docs/about/all/whats-new/security-updates.md
index 3d1dadcdb79..bd88139cb26 100644
--- a/docs/about/all/whats-new/security-updates.md
+++ b/docs/about/all/whats-new/security-updates.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/whats-new/security-updates.html
 ---
 title: Security updates
 description: Learn about the security updates that happened to the Spryker Commerce OS.
@@ -7,6 +6,8 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/security-updates
 originalArticleId: 52f64151-dd88-406c-8408-9c08d9c0bb2d
 redirect_from:
+- /docs/scos/user/intro-to-spryker/whats-new/security-updates.html
+
 related:
   - title: Security release notes 202306.0
     link: docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202306.0/security-release-notes-202306.0.html
diff --git a/docs/about/all/whats-new/supported-versions-of-php.md b/docs/about/all/whats-new/supported-versions-of-php.md
index b05a79c0b4b..0dbb5076d9c 100644
--- a/docs/about/all/whats-new/supported-versions-of-php.md
+++ b/docs/about/all/whats-new/supported-versions-of-php.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/whats-new/supported-versions-of-php.html
 ---
 title: Supported versions of PHP
 description: This document provides information about the PHP versions Spryker supports.
@@ -7,22 +6,7 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/supported-versions-of-php
 originalArticleId: 9eba7382-df72-44fd-b601-a3de5c592455
 redirect_from:
-  - /2021080/docs/supported-versions-of-php
-  - /2021080/docs/en/supported-versions-of-php
-  - /docs/supported-versions-of-php
-  - /docs/en/supported-versions-of-php
-  - /v5/docs/supported-versions-of-php
-  - /v5/docs/en/supported-versions-of-php
-  - /v4/docs/supported-versions-of-php
-  - /v4/docs/en/supported-versions-of-php
-  - /v3/docs/supported-versions-of-php
-  - /v3/docs/en/supported-versions-of-php
-  - /v2/docs/supported-versions-of-php
-  - /v2/docs/en/supported-versions-of-php
-  - /v1/docs/supported-versions-of-php
-  - /v1/docs/en/supported-versions-of-php
-  - /v6/docs/supported-versions-of-php
-  - /v6/docs/en/supported-versions-of-php
+- /docs/scos/user/intro-to-spryker/whats-new/supported-versions-of-php.html
 ---
 
 ## PHP 8
diff --git a/docs/about/all/whats-new/upcoming-major-module-releases.md b/docs/about/all/whats-new/upcoming-major-module-releases.md
index 9a351606f02..c6ab8fdf7a5 100644
--- a/docs/about/all/whats-new/upcoming-major-module-releases.md
+++ b/docs/about/all/whats-new/upcoming-major-module-releases.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/whats-new/upcoming-major-module-releases.html
 ---
 title: Upcoming major module releases
 description: Learn what modules and when will have the next major versions release
@@ -7,12 +6,7 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/upcoming-major-module-releases
 originalArticleId: e02b704f-db3a-4c76-a522-b81e326b0c08
 redirect_from:
-  - /2021080/docs/upcoming-major-module-releases
-  - /2021080/docs/en/upcoming-major-module-releases
-  - /docs/upcoming-major-module-releases
-  - /docs/en/upcoming-major-module-releases
-  - /v6/docs/upcoming-major-module-releases
-  - /v6/docs/en/upcoming-major-module-releases
+  - /docs/scos/user/intro-to-spryker/whats-new/upcoming-major-module-releases.html
   - /docs/marketplace/user/intro-to-spryker-marketplace/upcoming-major-module-releases.html
 ---
 
diff --git a/docs/about/all/whats-new/whats-new.md b/docs/about/all/whats-new/whats-new.md
index 6f1348170de..025aac10659 100644
--- a/docs/about/all/whats-new/whats-new.md
+++ b/docs/about/all/whats-new/whats-new.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/whats-new/whats-new.html
 ---
 title: What's new
 description: This article contains information about what’s new and changed in the Spryker Commerce OS.
@@ -7,22 +6,7 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/whats-new
 originalArticleId: 630e2d18-944a-4623-95ac-761984d1eedb
 redirect_from:
-  - /2021080/docs/whats-new
-  - /2021080/docs/en/whats-new
-  - /docs/whats-new
-  - /docs/en/whats-new
-  - /v5/docs/whats-new
-  - /v5/docs/en/whats-new
-  - /v4/docs/whats-new
-  - /v4/docs/en/whats-new
-  - /v3/docs/whats-new
-  - /v3/docs/en/whats-new
-  - /v2/docs/whats-new
-  - /v2/docs/en/whats-new
-  - /v1/docs/whats-new
-  - /v1/docs/en/whats-new
-  - /v6/docs/whats-new
-  - /v6/docs/en/whats-new
+  - /docs/scos/user/intro-to-spryker/whats-new/whats-new.html
   - /docs/scos/user/intro-to-spryker/whats-new/vat-rates-reduction-in-germany-between-july-2020-and-january-2021.html
 ---
 

From c028815fdd1c80b2c40407ccbe46dc3532df8853 Mon Sep 17 00:00:00 2001
From: Andrii Tserkovnyi <andrii.tserkovnyi@spryker.com>
Date: Wed, 6 Mar 2024 15:36:03 +0200
Subject: [PATCH 04/26] rename

---
 _data/sidebars/about_all_sidebar.yml          |  29 +-
 _data/sidebars/dg_dev_sidebar.yml             |   4 +
 .../all => _drafts/for-commerce-quest}/faq.md |   0
 .../mvp-project-structuring.md                |   0
 docs/{dg/dev => about/all}/b2b-suite.md       |   0
 docs/{dg/dev => about/all}/b2c-suite.md       |   0
 docs/about/all/intro-to-spryker.md            |  38 +-
 docs/about/all/releases/releases.md           |   2 +
 .../2019.11-security-audit-by-sektioneins.md  |   0
 ...ion-test-by-port-zero-executive-summary.md |   0
 .../back-office-for-marketplace-operator.md   |   4 +-
 ...pport.md => contacting-spryker-support.md} |   2 +-
 docs/about/all/support/escalations.md         |  14 +-
 ...etting-the-most-out-of-spryker-support.md} |   4 +-
 ...-secrets-with-the-spryker-support-team.md} |  13 +-
 ...-portal.md => using-the-support-portal.md} |   6 +-
 docs/about/all/whats-new/ie11-end-of-life.md  |  31 --
 docs/about/all/whats-new/security-updates.md  |  22 -
 .../upcoming-major-module-releases.md         |  25 --
 docs/about/all/whats-new/whats-new.md         | 400 ------------------
 .../dev}/supported-versions-of-php.md         |   0
 .../upgrade-and-migrate/upgrade-to-php-81.md} |  13 +-
 22 files changed, 55 insertions(+), 552 deletions(-)
 rename {docs/about/all => _drafts/for-commerce-quest}/faq.md (100%)
 rename {docs/about/all => _drafts/for-commerce-quest}/mvp-project-structuring.md (100%)
 rename docs/{dg/dev => about/all}/b2b-suite.md (100%)
 rename docs/{dg/dev => about/all}/b2c-suite.md (100%)
 rename docs/about/all/{whats-new => }/security-audit-reports/2019.11-security-audit-by-sektioneins.md (100%)
 rename docs/about/all/{whats-new => }/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.md (100%)
 rename docs/about/all/support/{how-to-contact-spryker-support.md => contacting-spryker-support.md} (97%)
 rename docs/about/all/support/{how-to-get-the-most-out-of-spryker-support.md => getting-the-most-out-of-spryker-support.md} (99%)
 rename docs/about/all/support/{how-to-share-secrets-with-the-spryker-support-team.md => share-secrets-with-the-spryker-support-team.md} (85%)
 rename docs/about/all/support/{how-to-use-the-support-portal.md => using-the-support-portal.md} (98%)
 delete mode 100644 docs/about/all/whats-new/ie11-end-of-life.md
 delete mode 100644 docs/about/all/whats-new/security-updates.md
 delete mode 100644 docs/about/all/whats-new/upcoming-major-module-releases.md
 delete mode 100644 docs/about/all/whats-new/whats-new.md
 rename docs/{about/all/whats-new => dg/dev}/supported-versions-of-php.md (100%)
 rename docs/{about/all/whats-new/php8-as-a-minimum-version-for-all-spryker-projects.md => dg/dev/upgrade-and-migrate/upgrade-to-php-81.md} (70%)

diff --git a/_data/sidebars/about_all_sidebar.yml b/_data/sidebars/about_all_sidebar.yml
index 0e2a01cda39..8b555ccb0de 100644
--- a/_data/sidebars/about_all_sidebar.yml
+++ b/_data/sidebars/about_all_sidebar.yml
@@ -42,25 +42,13 @@ entries:
             url: /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/security-release-notes-202212.0.html
     - title: Docs updates
       url: /docs/scos/user/intro-to-spryker/docs-release-notes.html
-    - title: What's new
-      url: /docs/scos/user/intro-to-spryker/whats-new/whats-new.html
+    - title: Security audit reports
       nested:
-      - title: PHP 8.1 as a minimum version for all Spryker projects
-        url: /docs/scos/user/intro-to-spryker/whats-new/php8-as-a-minimum-version-for-all-spryker-projects.html
-      - title: Supported versions of PHP
-        url: /docs/scos/user/intro-to-spryker/whats-new/supported-versions-of-php.html
-      - title: IE11 end of life
-        url: /docs/scos/user/intro-to-spryker/whats-new/ie11-end-of-life.html
-      - title: Security audit reports
-        nested:
-        - title: 2019.11 - Security audit by SektionEins
-          url: /docs/scos/user/intro-to-spryker/whats-new/security-audit-reports/2019.11-security-audit-by-sektioneins.html
-        - title: 2020.11 - Penetration test by Port Zero (executive summary)
-          url: /docs/scos/user/intro-to-spryker/whats-new/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.html
-      - title: Upcoming major module releases
-        url: /docs/scos/user/intro-to-spryker/whats-new/upcoming-major-module-releases.html
-      - title: Security updates
-        url: /docs/scos/user/intro-to-spryker/whats-new/security-updates.html
+      - title: 2019.11 - Security audit by SektionEins
+        url: /docs/scos/user/intro-to-spryker/whats-new/security-audit-reports/2019.11-security-audit-by-sektioneins.html
+      - title: 2020.11 - Penetration test by Port Zero (executive summary)
+        url: /docs/scos/user/intro-to-spryker/whats-new/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.html
+
     - title: Support
       nested:
       - title: How Spryker Support works
@@ -91,8 +79,7 @@ entries:
         url: /docs/scos/user/intro-to-spryker/support/how-to-contact-spryker-support.html
       - title: Understanding Project and Core Level Fixes
         url: /docs/scos/user/intro-to-spryker/support/understanding-project-and-core-level-fixes.html
-    - title: FAQ
-      url: /docs/scos/user/intro-to-spryker/faq.html
+
     - title: Supported browsers
       url: /docs/scos/user/intro-to-spryker/supported-browsers.html
     - title: Spryker Marketplace
@@ -115,8 +102,6 @@ entries:
       - title: Marketplace B2B Suite
         url: /docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2b-suite.html
 
-    - title: MVP project structuring
-      url: /docs/scos/user/intro-to-spryker/mvp-project-structuring.html
     - title: Spryker Academy
       url: /docs/scos/user/intro-to-spryker/spryker-academy.html
     - title: Contribute to the documentation
diff --git a/_data/sidebars/dg_dev_sidebar.yml b/_data/sidebars/dg_dev_sidebar.yml
index fc1ff1744f8..a59b5c08a7c 100644
--- a/_data/sidebars/dg_dev_sidebar.yml
+++ b/_data/sidebars/dg_dev_sidebar.yml
@@ -812,6 +812,8 @@ entries:
         url: /docs/dg/dev/upgrade-and-migrate/upgrade-to-angular-12.html
       - title: Upgrade to Angular 15
         url: /docs/dg/dev/upgrade-and-migrate/upgrade-to-angular-15.html
+      - title: Upgrade to PHP 8.1
+        url: /docs/dg/dev/upgrade-and-migrate/upgrade-to-php-81.html        
       - title: Upgrade to Symfony 5
         url: /docs/dg/dev/upgrade-and-migrate/upgrade-to-symfony-5.html
       - title: Upgrade to Symfony 6
@@ -1420,6 +1422,8 @@ entries:
 
   - title: Product and code releases
     url: /docs/dg/dev/product-and-code-releases.html
+  - title: Supported versions of PHP
+    url: /docs/dg/dev/supported-versions-of-php.html
 
   - title: Miscellaneous guides
     url: /docs/dg/dev/miscellaneous-guides/miscellaneous-guides.html
diff --git a/docs/about/all/faq.md b/_drafts/for-commerce-quest/faq.md
similarity index 100%
rename from docs/about/all/faq.md
rename to _drafts/for-commerce-quest/faq.md
diff --git a/docs/about/all/mvp-project-structuring.md b/_drafts/for-commerce-quest/mvp-project-structuring.md
similarity index 100%
rename from docs/about/all/mvp-project-structuring.md
rename to _drafts/for-commerce-quest/mvp-project-structuring.md
diff --git a/docs/dg/dev/b2b-suite.md b/docs/about/all/b2b-suite.md
similarity index 100%
rename from docs/dg/dev/b2b-suite.md
rename to docs/about/all/b2b-suite.md
diff --git a/docs/dg/dev/b2c-suite.md b/docs/about/all/b2c-suite.md
similarity index 100%
rename from docs/dg/dev/b2c-suite.md
rename to docs/about/all/b2c-suite.md
diff --git a/docs/about/all/intro-to-spryker.md b/docs/about/all/intro-to-spryker.md
index 4edfed3aff0..10032e9368e 100644
--- a/docs/about/all/intro-to-spryker.md
+++ b/docs/about/all/intro-to-spryker.md
@@ -1,6 +1,6 @@
 ---
 title: Intro to Spryker
-description: The Spryker Commerce OS or SCOS is a completely modular, API-first, headless commerce technology for transactional business models in a B2B or B2C context.
+description: High-level overview of Spryker Cloud Commerce OS
 last_updated: Sep 9, 2021
 template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/about-spryker
@@ -12,35 +12,39 @@ redirect_from:
   - /docs/fes/dev/installing-applications.html
   - /docs/scos/user/intro-to-spryker/roadmap.html
   - /docs/scos/user/intro-to-spryker/about-spryker-documentation.html
----
+  - /docs/scos/user/intro-to-spryker/mvp-project-structuring.html
+  - /docs/scos/user/intro-to-spryker/faq.html
+  - /docs/scos/user/intro-to-spryker/whats-new/upcoming-major-module-releases.html
+  - /docs/marketplace/user/intro-to-spryker-marketplace/upcoming-major-module-releases.html
+  - /docs/scos/user/intro-to-spryker/whats-new/ie11-end-of-life.html
+  - /docs/scos/user/intro-to-spryker/whats-new/whats-new.html
+  - /docs/scos/user/intro-to-spryker/whats-new/vat-rates-reduction-in-germany-between-july-2020-and-january-2021.html
 
-## What is the Spryker Commerce OS?
+---
 
-The Spryker Commerce OS (SCOS) is a completely modular B2B and B2C e-commerce technology. With the modular application and API-based integration with all possible customer touchpoints (front-ends), SCOS provides significantly shorter time-to-market and reduced total cost of ownership, while increasing your ROI due to the digital best practices.
+The Spryker Cloud Commerce OS (SCCOS) is a completely modular B2B and B2C e-commerce technology. With the modular application and API-based integration with all possible customer touchpoints (front-ends), Spryker provides significantly shorter time-to-market and reduced total cost of ownership, while increasing your ROI due to the digital best practices.
 ![image](https://spryker.s3.eu-central-1.amazonaws.com/docs/About/About+Spryker/Spryker-OS-Overview-RGB-JULY19_Spryker-OS-Overview.png)
 
 We establish a unique advantage for our customers by creating a commerce operating system that revolves around two cornerstones for success: modular and layered architectures.
 
-### Modular architecture
+## Modular architecture
 
 Modular architecture, or modularity of the Spryker Commerce OS, means that the system is composed of small parts called modules. The Spryker Commerce OS consists of over 750 modules. Some of them are mandatory and required by the OS to run, but many are optional and designed to provide certain functionality or connectivity to either internal or external systems.
 The modules combine to create features and have limited dependencies. The limited dependencies imply less development effort, increasing your return on investment and lowering the total cost of ownership.
+
 ![image](https://spryker.s3.eu-central-1.amazonaws.com/docs/About/About+Spryker/modularity_transparent.png)
 
-#### Benefits of the Spryker modular architecture:
+Spryker's code is stored on GitHub under the [Spryker repository](https://github.com/spryker). Here you can find a complete list of all the modules, along with a description and a link to the relevant documentation for each module.
+
+
+### Benefits of the Spryker modular architecture:
 
 * You *take only the modules or features that you need* for your project, without overloading it with redundant code and investing effort in something you don’t need.
 * You can *grow a project easily* using any of the wide selection of modules.
 * You can *add, delete, and test new features* without worrying about breaking or pausing your production shop site.
 * We adhere to the atomic release approach. This means that each module is released independently and has its own version. It is developed and tested so as to ensure backward compatibility with other modules that you might not want to update. This means you can *take new and update existing modules or features right after they have been released*.
 
-{% info_block infoBox %}
-
-The Spryker OS code is stored in GitHub under the [Spryker repository](https://github.com/spryker). Here you can find a complete list of all the modules, along with a description and a link to the relevant documentation for each module.
-
-{% endinfo_block %}
-
-### Layered architecture
+## Layered architecture
 
 Layered Architecture is used to separate your commercial offering and sales channels.
 When your commercial offering is hooked directly to an online web store, expanding to different channels and methods of selling poses a huge challenge in most cases. If you create a clear separation between what you are selling and how you are selling it, you gain the freedom and flexibility in choosing sales methods and channels.
@@ -58,14 +62,14 @@ SCOS is split into four different layers:
 ![image](https://spryker.s3.eu-central-1.amazonaws.com/docs/About/About+Spryker/spryker_layers_s.png)
 
 
-#### Benefits of the layered architecture
+### Benefits of the layered architecture
 
 * We confine long and resource-intensive processes to the Business and Persistence layers, which ensures *high performance*. The presentation side is separated from the rest of the OS to make sure that only lean processes are executed there. Basically, anything that can wait or can impact the purchase process is offloaded to an area that does not impact the performance.
 * Separate front- and back-end means *developers can work in parallel*, allowing for faster implementation, testing, and better optimization—all for less internal cost.
 * Since your commercial offering is not dependent on a single channel, you can *focus your effort on growth and improvement*, rather than on solutions, extensions, and sometimes hacks to “make things work”.
 * The separation ensures that *essential information is not tied-up with the presentation*. You can easily swap out, extend, replace this information, as well as change the ways it is presented.
 
-## Spryker B2B/B2C Demo Shops
+## Spryker B2B and B2C Demo Shops
 
 Our [B2B](/docs/scos/user/intro-to-spryker/b2b-suite.html) and [B2C Demo Shops](/docs/scos/user/intro-to-spryker/b2c-suite.html) showcase Spryker functionality and help you choose the best possible starting point and set of features based on your business needs. The Demo Shops pose a clear starting point and upgrade path for everything you base your project on. We ship our B2B/B2C Demo Shops as a part of the product, covered by the same commercial license and the same support and LTS (long-term support) rules as individual Spryker Commerce OS modules.
 
@@ -75,9 +79,9 @@ The recommended starting points for all standard commerce projects are our [B2B]
 
 Apart from that, if your business case does not fit in one of the proposed models, you can start building your project by cherry-picking the modules you need. Since they are released under a commercial license with stable and predictable release cycles, you can build your e-commerce business with reliance and certainty. Our engineers make sure that each module is reliable, backward compatible, and fully regression-tested, and all our releases are supported with an LTS flag (12 months).
 
-## What’s next?
+## Next steps
 
-This documentation site contains lots of information on Spryker Commerce OS. Select one of the topics below depending on what you want to do next:
+Select one of the topics below depending on what you want to do next:
 
 * [What's new](/docs/scos/user/intro-to-spryker/whats-new/whats-new.html): general information about Spryker, news, and release notes.
 * [Setup](/docs/dg/dev/set-up-spryker-locally/set-up-spryker-locally.html): installation of Spryker.
diff --git a/docs/about/all/releases/releases.md b/docs/about/all/releases/releases.md
index 183616ce8ad..ba0cbabb650 100644
--- a/docs/about/all/releases/releases.md
+++ b/docs/about/all/releases/releases.md
@@ -30,6 +30,8 @@ redirect_from:
   - /docs/scos/user/intro-to-spryker/releases/archive/2018/release-notes-february-1-2018.html
   - /docs/scos/user/intro-to-spryker/releases/archive/2018/release-notes-march-2018.html
   - /docs/scos/user/intro-to-spryker/releases/archive/2018/release-notes-april-2018.html
+  - /docs/scos/user/intro-to-spryker/whats-new/security-updates.html
+
 ---
 
 This section contains the notes for each [Product release](/docs/scos/user/intro-to-spryker/spryker-release-process.html#product-releases) made by Spryker. Make sure that you check this section from time-to-time to stay up to date with the improvements, bug fixes and new features that are delivered by our team.
diff --git a/docs/about/all/whats-new/security-audit-reports/2019.11-security-audit-by-sektioneins.md b/docs/about/all/security-audit-reports/2019.11-security-audit-by-sektioneins.md
similarity index 100%
rename from docs/about/all/whats-new/security-audit-reports/2019.11-security-audit-by-sektioneins.md
rename to docs/about/all/security-audit-reports/2019.11-security-audit-by-sektioneins.md
diff --git a/docs/about/all/whats-new/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.md b/docs/about/all/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.md
similarity index 100%
rename from docs/about/all/whats-new/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.md
rename to docs/about/all/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.md
diff --git a/docs/about/all/spryker-marketplace/back-office-for-marketplace-operator.md b/docs/about/all/spryker-marketplace/back-office-for-marketplace-operator.md
index 3657a2b78df..2f465d3d19f 100644
--- a/docs/about/all/spryker-marketplace/back-office-for-marketplace-operator.md
+++ b/docs/about/all/spryker-marketplace/back-office-for-marketplace-operator.md
@@ -9,11 +9,11 @@ redirect_from:
 
 ---
 
-A *marketplace operator* is a company that owns the marketplace. In a marketplace business model, one or more of such a company's employees represent a marketplace operator and manage the store. We call such users as [marketplace administrators](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-personas.html#marketplace-administrator). Depending on the marketplace model, the marketplace operator either manages only other merchants' orders or also sells products as a [main merchant](/docs/pbc/all/merchant-management/{{site.version}}/marketplace/marketplace-merchant-feature-overview/main-merchant.html)).  
+A *marketplace operator* is a company that owns the marketplace. In a marketplace business model, one or more of such a company's employees represent a marketplace operator and manage the store. We call such users [marketplace administrators](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-personas.html#marketplace-administrator). Depending on the marketplace model, the marketplace operator either manages only other merchants' orders or also sells products as a [main merchant](/docs/pbc/all/merchant-management/{{site.version}}/marketplace/marketplace-merchant-feature-overview/main-merchant.html).
 
 ## Merchant management
 
-Merchant accounts are created in the Back Office, and a [marketplace administrator](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-personas.html#marketplace-administrator) is required to facilitate their creation. In the **Marketplace&nbsp;<span aria-label="and then">></span> Merchants** section of the Back Office, a marketplace operator manages merchants, that is:
+Merchant accounts are created in the Back Office, and a [marketplace administrator](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-personas.html#marketplace-administrator) is required to facilitate their creation. In the **Marketplace&nbsp;<span aria-label="and then">></span> Merchants** section of the Back Office, a marketplace operator manages merchants as follows:
 
 * Creates merchants
 * Edits merchants
diff --git a/docs/about/all/support/how-to-contact-spryker-support.md b/docs/about/all/support/contacting-spryker-support.md
similarity index 97%
rename from docs/about/all/support/how-to-contact-spryker-support.md
rename to docs/about/all/support/contacting-spryker-support.md
index 50a371f0b22..329c90ebf12 100644
--- a/docs/about/all/support/how-to-contact-spryker-support.md
+++ b/docs/about/all/support/contacting-spryker-support.md
@@ -1,5 +1,5 @@
 ---
-title: How to contact Spryker Support
+title: Contacting Spryker Support
 last_updated: Jun 16, 2021
 template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/how-to-contact-spryker-support
diff --git a/docs/about/all/support/escalations.md b/docs/about/all/support/escalations.md
index 08a7deb7549..2a91dc38b6a 100644
--- a/docs/about/all/support/escalations.md
+++ b/docs/about/all/support/escalations.md
@@ -8,12 +8,10 @@ redirect_from:
 - /docs/scos/user/intro-to-spryker/support/escalations.html
 ---
 
-You might wonder how we manage escalations. Let's start with how we define escalations at Spryker.
-
-## What is an escalation?
 An escalation is a situation that usually involves a partner or customer having an urgent or especially important problem that cannot immediately be solved to the satisfaction of everyone involved, and the problem is escalated to senior leadership or other departments in an effort to resolve the problem.
 
-### Example of a situation leading up to an escalation
+## Example of a situation leading up to an escalation
+
 Customer A discovers a problem with Spryker that has a significant impact on their plans to launch a new feature next week. They open a support case with Spryker. The support representative dealing with the case informs the customer that they have verified the bug, and a report has been filed with development to fix the bug. The mention that the bug is most likely to be fixed within 3-4 weeks, which conflicts with the customer's feature release.
 
 While Support always tries to accommodate the plans of customers and partners, this might not always be possible. Naturally, this leads to frustration, and company A might feel the need to reach out to their account manager, partner manager, customer success manager, or even a member of Spryker leadership to force or at least expedite problem resolution that way.
@@ -21,15 +19,18 @@ While Support always tries to accommodate the plans of customers and partners, t
 While this strategy might feel like the right thing to do (we need to do something right?), it produces suboptimal results and consumes resources, nerves, and time. It also puts a strain on the relationship with the customer or partner and often introduces a lot of emotions that can stand in the way of orderly resolution.
 
 ## How do we want to deal with escalations?
+
 In Support, we acknowledge that we cannot always produce a satisfying result. We do not always get it right, and sometimes our hands might simply be tied. Escalations happen, and it is important for us to steer them into a constructive and orderly direction right away that ensures:
 1. It is easy for a customer or partner to escalate an issue.
 2. The customer's or partner's problem is evaluated by the right audience.
 3. The stakeholders align quickly to find a feasible strategy going forward.
 
-### How can I initiate an escalation?
+### Initiate an escalation
+
 Creating an [Emergency Case](/docs/scos/user/intro-to-spryker/support/how-to-use-the-support-portal.html#emergencies) always starts an escalation. You will receive an email notifying you that an escalation has been started.
 
-### Process
+### The escalation process
+
 The escalation process is designed in a way to create visibility for the right audience and is built in a robust way to ensure quality standards. Facing a problem with significant business impact is stressful and we tried to build a streamlined process that is easy to follow for partners and customers and easy to operate for our support reps. An escalation has seven statuses. The customer and partner receive email notifications when the status changes.
 
 `STARTED`. A customer or partner has created an emergency case. Internal stakeholders are informed and began evaluating the information provided. In cases where the Emergency Case option is misused, the Escalation is canceled, and the requester is informed about it.
@@ -43,6 +44,7 @@ The escalation process is designed in a way to create visibility for the right a
 After a valid escalation is over, Post Mortem is held and the results are shared with the partner and customer. The point of this is to make it less likely that a similar situation that causes an escalation likely can occur in the future. If the escalation was caused by infrastructure problems in production systems, a technical Root Cause Analysis (RCA) will also be shared.
 
 ### What we ask from you during an escalation
+
 This is the most effective way to bring your issue to the attention of a broad audience. We ask you to not misuse this option to expedite regular bug resolution or case processing. It makes several people in Spryker very busy and might therefore even have the opposite effect.
 
 When you start an escalation, refrain from contacting other Spryker personnel about the same issue on different channels. This introduces confusion and information asymmetry which reduces the effectiveness of this process significantly.
diff --git a/docs/about/all/support/how-to-get-the-most-out-of-spryker-support.md b/docs/about/all/support/getting-the-most-out-of-spryker-support.md
similarity index 99%
rename from docs/about/all/support/how-to-get-the-most-out-of-spryker-support.md
rename to docs/about/all/support/getting-the-most-out-of-spryker-support.md
index 96230318227..bbe4da3499f 100644
--- a/docs/about/all/support/how-to-get-the-most-out-of-spryker-support.md
+++ b/docs/about/all/support/getting-the-most-out-of-spryker-support.md
@@ -1,5 +1,5 @@
 ---
-title: How to get the most out of Spryker Support
+title: Getting the most out of Spryker Support
 last_updated: Jun 16, 2021
 template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/how-to-get-the-most-out-of-spryker-support
@@ -36,7 +36,7 @@ If you are not sure how you can whitelist these email addresses, forward this re
 
 -->
 
-## Include all the intel
+## Provide all the information
 
 The goal of every ambitious support team is to increase the number of tickets that can be solved with the first engagement. The ideal support case is opened with all the information needed to assess, reproduce, and solve the problem. The first response can then already include the solution to the problem.
 
diff --git a/docs/about/all/support/how-to-share-secrets-with-the-spryker-support-team.md b/docs/about/all/support/share-secrets-with-the-spryker-support-team.md
similarity index 85%
rename from docs/about/all/support/how-to-share-secrets-with-the-spryker-support-team.md
rename to docs/about/all/support/share-secrets-with-the-spryker-support-team.md
index 3d9cfa8465d..30e25476646 100644
--- a/docs/about/all/support/how-to-share-secrets-with-the-spryker-support-team.md
+++ b/docs/about/all/support/share-secrets-with-the-spryker-support-team.md
@@ -1,5 +1,5 @@
 ---
-title: How to share secrets with the Spryker Support Team
+title: Share secrets with the Spryker Support Team
 description: Learn how to share secrets with the Spryker Support Team
 last_updated: Jun 16, 2021
 template: concept-topic-template
@@ -19,18 +19,11 @@ Spryker employees never ask for credentials. We delete and don’t work with any
 
 ## Prerequisites
 
-Register in our [Slack community](https://spryker.com/support/).
+* Register in our [Slack community](https://spryker.com/support/).
+* Open a support case.
 
 ## Process for sharing the secrets
 
-Stick to the following process when sharing secrets with the Spryker Support Team.
-
-{% info_block warningBox %}
-
-Having an active related case is a prerequesite to sharing a secret with the team.
-
-{% endinfo_block %}
-
 1. Create a secret message by navigating to [One-Time Secret](https://onetimesecret.com/) and inserting your secret there. Make sure to configure a passphrase for your secret.
 
 {% info_block warningBox %}
diff --git a/docs/about/all/support/how-to-use-the-support-portal.md b/docs/about/all/support/using-the-support-portal.md
similarity index 98%
rename from docs/about/all/support/how-to-use-the-support-portal.md
rename to docs/about/all/support/using-the-support-portal.md
index e3c8ba70c8e..007c98ac313 100644
--- a/docs/about/all/support/how-to-use-the-support-portal.md
+++ b/docs/about/all/support/using-the-support-portal.md
@@ -1,5 +1,5 @@
 ---
-title: How to use the Support Portal
+title: Using the Support Portal
 last_updated: Sep 28, 2021
 template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/how-to-use-the-support-portal
@@ -13,9 +13,7 @@ related:
     link: docs/scos/user/intro-to-spryker/support/how-to-get-the-most-out-of-spryker-support.html
 ---
 
-## Overview
-
-This document describes how to use the support portal to create and manage your cases
+This document describes how to use the support portal to create and manage your cases.
 
 ## Prerequisites
 
diff --git a/docs/about/all/whats-new/ie11-end-of-life.md b/docs/about/all/whats-new/ie11-end-of-life.md
deleted file mode 100644
index ae1d1bdeac9..00000000000
--- a/docs/about/all/whats-new/ie11-end-of-life.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: IE11 end of life
-description: Microsoft announced that the Internet Explorer 11 desktop application would be retired on June 15, 2022, for specific versions of Windows 10. Legacy Internet Explorer-based websites and applications will continue to work with Microsoft Edge’s built-in Internet Explorer mode.
-last_updated: June 8, 2022
-template: concept-topic-template
-redirect_from:
-- /docs/scos/user/intro-to-spryker/whats-new/ie11-end-of-life.html
-
----
-
-Microsoft announced that the Internet Explorer 11 (IE11) desktop application would be retired on June 15, 2022, for specific versions of Windows 10. Legacy Internet Explorer-based websites and applications will continue to work with Microsoft Edge’s built-in Internet Explorer mode.
-
-It is time to say goodbye to IE11 for Spryker Yves. We have been preparing for this sunsetting for over five months already, and we believe this is the best way forward for you to give your shoppers the best possible experience.
-
-Since the inception of Yves, browser compatibility has been and continues to be very relevant to our development roadmap and evolution.
-
-## Why have we decided to end IE11 support?
-
-In short, it is important for us that anyone who lands on a Spryker-powered website has the best possible user experience. IE11 does not provide the website visitor with a modern and reliable experience.
-
-For merchants, there’s a race: PCI and related standards will force you to stop accepting old clients, while Microsoft and the whole web industry are trying to get them to update. Merchants will be caught in the middle, with potentially unhappy customers contacting the merchant when they can’t complete their purchases.
-
-Browsers like Chrome, Firefox, Safari, Opera, and even Microsoft Edge are evolving and continually being updated and improved to match web standards, and this is a good thing. Internet Explorer, on the other hand, is not evolving. Microsoft advises against using this browser as the default browser choice. The Microsoft 365 Apps team is said goodbye to IE11 on August 17, 2021.
-
-## Timeline
-
-We have decided to end IE11 support for Spryker as our next product release, estimated for Q4 2022.
-
-## How should you prepare
-
-If IE11 is not relevant to your browser quota, you can rest assured that you are safe. There is no need to implement anything as the people who visit your platform are not extensively “laggards”, so you can focus on other more priority tasks. On the other hand, if you do have a customer base with a significant percentage of people using IE11, we got you covered. We will provide code snippets to be compatible with polyfills so that they can continue to have the most functionality in their deprecated browsers.
diff --git a/docs/about/all/whats-new/security-updates.md b/docs/about/all/whats-new/security-updates.md
deleted file mode 100644
index bd88139cb26..00000000000
--- a/docs/about/all/whats-new/security-updates.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Security updates
-description: Learn about the security updates that happened to the Spryker Commerce OS.
-last_updated: Jul 12, 2023
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/security-updates
-originalArticleId: 52f64151-dd88-406c-8408-9c08d9c0bb2d
-redirect_from:
-- /docs/scos/user/intro-to-spryker/whats-new/security-updates.html
-
-related:
-  - title: Security release notes 202306.0
-    link: docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202306.0/security-release-notes-202306.0.html
-  - title: Security release notes 202304.0
-    link: docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202304.0/security-release-notes-202304.0.html
-  - title: Security release notes 202212.0
-    link: docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/security-release-notes-202212.0.html
----
-
-To receive a security updates email, please request the subscription at [support@spryker.com](mailto:support@spryker.com).
-
-Check out our Security Release notes in the [Release Notes](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes.html) article for each respective release.
diff --git a/docs/about/all/whats-new/upcoming-major-module-releases.md b/docs/about/all/whats-new/upcoming-major-module-releases.md
deleted file mode 100644
index c6ab8fdf7a5..00000000000
--- a/docs/about/all/whats-new/upcoming-major-module-releases.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: Upcoming major module releases
-description: Learn what modules and when will have the next major versions release
-last_updated: Sep 27, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/upcoming-major-module-releases
-originalArticleId: e02b704f-db3a-4c76-a522-b81e326b0c08
-redirect_from:
-  - /docs/scos/user/intro-to-spryker/whats-new/upcoming-major-module-releases.html
-  - /docs/marketplace/user/intro-to-spryker-marketplace/upcoming-major-module-releases.html
----
-
-
-
-[Major module releases](/docs/scos/dev/architecture/module-api/semantic-versioning-major-vs.-minor-vs.-patch-release.html) might require some development efforts from projects. To help you plan in advance, we will be providing information on modules for which we plan major releases on this page.
-
-<!--
-| MODULE | DATE | REASON FOR THE MAJOR VERSION |
-| --- | --- | --- |
--->
-{% info_block infoBox "Info" %}
-
-To learn about Marketplace-related upcoming major releases, see [Marketplace upcoming major module releases](/docs/marketplace/user/intro-to-spryker-marketplace/upcoming-major-module-releases.html).
-
-{% endinfo_block %}
diff --git a/docs/about/all/whats-new/whats-new.md b/docs/about/all/whats-new/whats-new.md
deleted file mode 100644
index 025aac10659..00000000000
--- a/docs/about/all/whats-new/whats-new.md
+++ /dev/null
@@ -1,400 +0,0 @@
----
-title: What's new
-description: This article contains information about what’s new and changed in the Spryker Commerce OS.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/whats-new
-originalArticleId: 630e2d18-944a-4623-95ac-761984d1eedb
-redirect_from:
-  - /docs/scos/user/intro-to-spryker/whats-new/whats-new.html
-  - /docs/scos/user/intro-to-spryker/whats-new/vat-rates-reduction-in-germany-between-july-2020-and-january-2021.html
----
-
-<!--
-
-Used to be http://spryker.github.io/getting-started/whats-new/
-
-Learn more about the new [GDPR regulations](/docs/scos/user/intro-to-spryker/support/guidelines-for-new-gdpr-rules.html) taking affect on May the 25th, 2018.
-
-Click  here for information on how to navigate through the Academy.
--->
-
-The following page is a report of what’s new and changed in the Spryker Commerce OS.
-
-To subscribe to our release notes and security updates, see the following articles:
-
-* [Releases](/docs/scos/user/intro-to-spryker/releases/releases.html)
-* [Release notes](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes.html)
-* [Security Updates](/docs/scos/user/intro-to-spryker/whats-new/security-updates.html)
-
-<!--
-<details>
-<summary markdown='span'>April 2018 Release</summary>
-
-[Release Notes - April - 2018](/docs/scos/user/intro-to-spryker/releases/archive/2018/release-notes-april-2018.html)
-
-
-* New: Reorder
-* New: Own Orders of Customers in the Administration Interface
-* Improved: Checkout Shipment Pre-Check Plugin
-* Improved: Country on the Order Details Page in the Administrator Interface
-* Improved: Extension Points for Post (De)activation of CMS Pages and Categories Update
-
-<br>
-</details>
-
-<details>
-<summary markdown='span'>March 2018 Release</summary>
-
-[Release Notes - March - 2018](/docs/scos/user/intro-to-spryker/releases/archive/2018/release-notes-march-2018.html)
-
-
-* New: Gift Cards
-* New: Setting a New Password For the Administration Interface Users
-* New: Multi-store Products Availability
-* Improved: Obsolete Touch Records Cleanup
-* Improved: Elasticsearch 5 Upgrade
-
-<br>
-</details>
-
-<details>
-<summary markdown='span'>February 2018 - Release #2</summary>
-
-[Release Notes - February - 2 2018](/docs/scos/user/intro-to-spryker/releases/archive/2018/release-notes-february-2-2018.html)
-
-
-* New: CMS Blocks Per Store
-* New: Discounts Per Store
-* New: Time To Live For Products
-* Improved: Configurable Cookie Path
-* Improved: Full Compatibility To Symfony 28 And Then 30
-* Improved: Compatibility To PHP 7.2
-
-<br>
-</details>
-
-<details>
-<summary markdown='span'>February 2018 - Release #1</summary>
-
-[Release Notes - February - 1 2018](/docs/scos/user/intro-to-spryker/releases/archive/2018/release-notes-february-1-2018.html)
-
-
-* New: Product Search Widget
-* New: Multi-Store Product Abstract
-* Improved: Multiple Mappings Per Single Import
-* Improved: Fixing Compatibility Issues In All FormTypes
-* Improved: New Fields on Customer Account Page
-
-<br>
-</details>
-
-<details>
-<summary markdown='span'>January 2018 Release</summary>
-
-[Release Notes - January - 2018](/docs/scos/user/intro-to-spryker/releases/archive/2018/release-notes-january-2018.html)
-
-
-* New: Multi-Currency Product Options
-* New: Category Filters
-* New: Adding Multiple Products to Cart
-* Improved: Use of Logger Plugin by Log Module
-* Improved: Fixing a Misleading Name in Sales Query Container
-* Improved: Order Placement Process Refactoring
-* Improved: Changing the Table Column Type From the Project Code
-* Improved: Configuring SSL Verification in Zed Request Client
-
-<br>
-</details>
-
-<details>
-<summary markdown='span'>December 2017 Release</summary>
-
-[Release Notes - December - 2017](/docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-december-2017.html)
-
-
-* New: Initial Release of Heidelpay Module
-* New: Arvato RSS Release 2.0.0
-* Improved: Spryker Install Tool
-* Improved: Discount Calculation Performance with High Number of Criterias in Discount Rule
-* Improved: Module Config Shared Between Layers and Between Modules
-* Improved:bCatalog View Mode
-* Improved: Zed Side Email Validation on Newsletter Subscription and Guest Form
-* Improved: Preparing Console Module for Standalone Usage
-
-<br>
-</details>
-
-<details>
-<summary markdown='span'>November 2017 - Release #2</summary>
-
-[Release Notes - November - 2 2017](/docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-november-2-2017.html)
-
-* Improved: Inspinia Update
-* Improved: Filter Out Certain Orders from Listing in Yves Customer Account
-* Improved: Limits for Sequence Numbers
-* Improved: Double Click Protection for Submit Action in Zed Administrative Interface
-* Improved: Success Codes for NewRelic Record Deployment Response
-
-<br>
-</details>
-
-<details>
-<summary markdown='span'>November 2017 - Release #1</summary>
-
-[Release Notes - November - 1 2017](/docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-november-1-2017.html)
-
-* New: Multi-currency for Shipments
-* New: Introducing Infrastructure for Upcoming Publish &amp; Synchronisation
-* Improved: State Machine Sub-process Reuse
-* Improved: Aggregated Reservations for Availability Updates
-* Improved: Dedicated Log Configuration Plugins
-* Improved: Decoupling JavaScript Dependency in CMS
-
-<br>
-</details>
-
-<details>
-<summary markdown='span'>October 2017 - Release #2</summary>
-
-[Release Notes - October - 2 2017](/docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-october-2-2017.html)
-
-* New: Multi-currency for Discounts
-* Improved: Twig Data Access Optimisation
-* Improved: Code Sniffer for Project Modules
-* Improved: Architecture Sniffer for Custom Paths in Project or Vendor
-
-<br>
-</details>
-
-<details>
-<summary markdown='span'>October 2017 - Release #1</summary>
-
-[Release Notes - October - 1 2017](/docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-october-1-2017.html)
-
-* New: CMS Page Preview
-* New: Validity Dates for Navigation Nodes
-* New: Multi-currency for Orders
-* Improved: oryx-for-zed Version Update to 1.1.1
-* Improved: New Interface to Allow Shipment and Payment Method Grouping
-* Improved: Logging Exceptions in a Human-readable Format
-* Improved: CallbackHandler for Exception Logging
-* Improved: Cache for Already Located Classes
-* Improved: fromArray() Method Performance
-* Improved: StorageClient Optimization
-* Improved: Add-to-cart Function Performance
-* Improved: Force HTTPS
-* Improved: Failed Add-to-cart Items from Wishlist
-* Improved: OMS Performance Due to Missing Indexes in PostgreSQL
-* Improved: Standalone Facets
-
-<br>
-</details>
-
-<details>
-<summary markdown='span'>September 2017 - Release #2</summary>
-
-[Release Notes - September - 2 2017](/docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-september-2-2017.html)
-
-* New: Discount Promotion Products
-* New: Product Reviews and Ratings
-* New: Multi Currency Infrastructure
-* New: Propel Migration Check Console Command
-* New: Config Profiler
-* Improved: Product Availability Retrieval Enhancement
-* Improved: Touch Aware Data Importers to Touch Inactive
-* Improved: Validator Updates for Transfers
-* Improved: Navigation Redis Entry Optimization
-* Improved: Kernel Class Resolver Performance
-* Improved: Missing Index for Stock Table
-* Improved: Price Check Query Performance
-* Improved: Output Execution Time for Importers
-* Improved: Mget Cache
-
-<br>
-</details>
-
-<details>
-<summary markdown='span'>September 2017 - Release #1</summary>
-
-[Release Notes - September - 1 2017](/docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-september-1-2017.html)
-
-* New: Attribute Management for High Number of Attributes
-* New: Remove Payment when Cart is Modified
-* Improved: Template Validation to CMS Blocks
-* Improved: Order Countries
-* Improved: Remove Empty Catch Block
-* Improved: Customer Group Optimization
-* Improved: Cache for Navigation
-
-<br>
-</details>
-
-<details>
-<summary markdown='span'>August 2017 - Release #2</summary>
-
-[Release Notes - August - 2 2017](/docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-august-2-2017.html)
-
-* New: Order Details Improvement
-* Improved: Enable isSearchable Checkbox for CMS Page
-* Improved: Initial Grand Total Calculator
-* Improved: Product Price Size
-* Improved: Query Only Non Assigned Product Abstracts for Assignment
-* Improved: Remove Voucher Pool Key From Discount When Type Changes
-* Improved: Restore Password Link Generation
-* Improved: Unique Name Validation for Carriers
-
-<br>
-</details>
-
-<details>
-<summary markdown='span'>August 2017 - Release #1</summary>
-
-[Release Notes - August - 1 2017](/docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-august-1-2017.html)
-
-* New: Shipment Discount
-* Improved: Create Injection Points for Project Logic for Twig
-* Improved: Optional Category Template
-* Improved: Shipment Delivery Time
-* Improved: Reset Password
-* Improved: NULL Password in Config for Storage
-* Improved: Missing Breadcrumbs
-* Improved: Elasticsearch Client Config
-* Improved: Architecture Sniffer
-* Improved: Increment Counter for Unlimited Vouchers
-* Improved: Change Path to last_yves_request Log
-* Improved: Allow Check for Breadcrumbs in Communication
-* Improved: Exclusive Custom Search and Storage Client Configuration
-* Improved: Update to Allow symfony/http-kernel V2 or V3
-
-<br>
-</details>
-
-<details>
-<summary markdown='span'>July 2017 - Release #2</summary>
-
-[Release Notes - July - 2 2017](/docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-july-2-2017.html)
-
-* New: Filter by Product Labels
-* New: Data Importers
-* New: New Products and Dynamic Labels
-* New: Category Template and CMS Block Position
-* Improved: Possibility to Add ServiceProvider to ConsoleBootstrap
-* Improved: CORS Headers
-* Improved: Storage Client Cache
-
-<br>
-</details>
-
-<details>
-<summary markdown='span'>July 2017 - Release #1</summary>
-
-[Release Notes - July - 1 2017](/docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-july-1-2017.html)
-
-* New: Selecting Product Variant in the Cart
-* New: Improvements and New Features for CMS Blocks
-* New: FileSystem Filemanager
-* New: On Sale Products
-* New: Discount Rules Based On Product Labels
-* New: Multiple Payment Methods for One Sales Order
-* New: CMS Content Widgets
-* Improved: Validation for Attributes
-* Improved: Customer Address Country Options
-* Improved: Configuration for CMS Placeholders
-* Improved: Subscribe to Newsletter Without Customer Account
-* Improved: Enabled Open Range Queries for Filters
-* Improved: Stock Management
-* Improved: Interface for Subscription Handler
-* Improved: Discount Filter
-* Improved: Beta: HTTP OPTIONS Pre-flight Request Support
-
-<br>
-</details>
-
-<details>
-<summary markdown='span'>June 2017 - Release #2</summary>
-
-[Release Notes - June - 2 2017](/docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-june-2-2017.html)
-
-* New: Delete Customer Account
-* New: Product Sets
-* New: Product Labels
-* Improved: Calculation
-* Improved: Config Options to Define Ports for Yves and Zed
-* Improved: Hashing Algorithm for Zed Authentication
-
-<br>
-</details>
-
-<details>
-<summary markdown='span'>June 2017 - Release #1</summary>
-
-[Release Notes - June - 1 2017](/docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-june-1-2017.html)
-
-* Improved: Session Service Provider Enhancement
-* Improved: Autoload Entry for BC
-* Improved: Combining Product Images
-* Improved: GetConfig for DependencyProvider
-* Improved: Moving Glob to Finder
-
-<br>
-</details>
-
-<details>
-<summary markdown='span'>May 2017 - Release #2</summary>
-
-[Release Notes - May - 2 2017](/docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-may-2-2017.html)
-
-* New: CMS Page Draft and Page Versioning
-* New: Rest API - BETA
-* Improved: Removing Image from Image Set
-* Improved: GUI Group Buttons
-* Improved: Application Store for Testify
-* Improved: Logging of Custom Exceptions in Yves
-* Improved: Extended Data Set for DataFeed - BETA
-
-<br>
-</details>
-
-<details>
-<summary markdown='span'>May 2017 - Release #1</summary>
-
-[Release Notes - May - 1 2017](/docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-may-1-2017.html)
-
-* New: Product Groups
-* Improved: CodeStyle checker
-* Improved: PropelQueryBuilder Filtering and PropelOrm Formatting
-
-<br>
-</details>
-
-<details>
-<summary markdown='span'>April 2017 - Release #2</summary>
-
-[Release Notes - April - 2 2017](/docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-april-2-2017.html)
-
-* New: Multiple Wishlists
-* New: Generated Directory Removal
-* New: Data Feeds - BETA
-* Improved: Twig Cache Warmup
-* Improved: Zed Navigation Fix
-
-
-<br>
-</details>
-
-<details>
-<summary markdown='span'>April 2017 - Release #1</summary>
-
-[Release Notes - April - 1 2017](/docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-april-1-2017.html)
-
-* New: Product Relations
-* New: Event module
-* New: Propel Query Builder - BETA
-* Improved: 3rd party integrations
-
-
-<br>
-</details>
-
--->
diff --git a/docs/about/all/whats-new/supported-versions-of-php.md b/docs/dg/dev/supported-versions-of-php.md
similarity index 100%
rename from docs/about/all/whats-new/supported-versions-of-php.md
rename to docs/dg/dev/supported-versions-of-php.md
diff --git a/docs/about/all/whats-new/php8-as-a-minimum-version-for-all-spryker-projects.md b/docs/dg/dev/upgrade-and-migrate/upgrade-to-php-81.md
similarity index 70%
rename from docs/about/all/whats-new/php8-as-a-minimum-version-for-all-spryker-projects.md
rename to docs/dg/dev/upgrade-and-migrate/upgrade-to-php-81.md
index fcd9e00db2b..085c02cf6b2 100644
--- a/docs/about/all/whats-new/php8-as-a-minimum-version-for-all-spryker-projects.md
+++ b/docs/dg/dev/upgrade-and-migrate/upgrade-to-php-81.md
@@ -1,5 +1,5 @@
 ---
-title: PHP 8.1 as the minimum version for all Spryker projects
+title: Upgrade to PHP 8.1
 description: End of November 2022, Spryker will release a new version of its Demo Shops requiring PHP 8.1 as the minimum version.
 last_updated: November 22, 2022
 template: concept-topic-template
@@ -8,16 +8,9 @@ redirect_from:
 
 ---
 
+PHP 8.1 is the minimum supported version for Demo Shops.
 
-End of November 2022, Spryker will release a new version of its Demo Shops, which will require PHP 8.1 as their minimum PHP version. PHP 8.0 will no longer be supported. Spryker's new module releases will only be compatible with PHP version 8.1 or later. See [Supported versions of PHP](/docs/scos/user/intro-to-spryker/whats-new/supported-versions-of-php.html) for details about the supported PHP versions.
-
-## Impacts
-
-Backwards compatibility remains unaffected. If your project followed our recommendations and requirements in the past twelve months, you will not experience any upgradability issues.
-
-## Migration steps
-
-To migrate your project to the 8.1 version of PHP, follow these steps:
+To upgrade PHP to 8.1, follow the steps:
 
 1. Update your modules manually in `composer.json`.
 Use the major lock `^` or the minor lock `~` if you have changes on the project level for respective module constraints.

From a979a7511c9700cf65e00aa1664f4fcacba88628 Mon Sep 17 00:00:00 2001
From: Andrii Tserkovnyi <andrii.tserkovnyi@spryker.com>
Date: Thu, 7 Mar 2024 16:09:39 +0200
Subject: [PATCH 05/26] rename

---
 _data/sidebars/about_all_sidebar.yml          | 10 +--
 .../202307.0/feature-integration-guides.md    |  2 +-
 .../{intro-to-spryker.md => about-spryker.md} |  2 +-
 .../all/about-the-docs/about-spryker-docs.md  | 24 ++++++
 ...dd-global-sections-to-the-documentation.md |  0
 ...-and-edit-diagrams-in-the-documentation.md |  0
 .../contribute-to-the-docs.md}                |  2 +-
 .../edit-the-documentation-locally.md         |  0
 ...dit-the-documentation-via-pull-requests.md |  0
 .../report-documentation-issues.md            |  0
 .../review-pull-requests.md                   |  0
 .../install-recommended-vs-code-extensions.md |  0
 .../run-the-documentation-locally.md          |  0
 .../examples.md                               |  0
 ...rules-and-guidance-for-adding-documents.md |  0
 .../markdown-syntax.md                        |  0
 .../spelling.md                               |  0
 .../spryker-documentation-style-guide.md      |  0
 .../word-list.md                              |  0
 .../about-spryker-documentation.md            |  0
 .../all/releases/product-and-code-releases.md | 76 +++++++++++++++++++
 .../releases/release-notes/release-notes.md   |  3 -
 docs/about/all/releases/releases.md           | 57 --------------
 .../all/support/contacting-spryker-support.md |  8 +-
 docs/about/all/support/getting-support.md     |  4 +-
 ...getting-the-most-out-of-spryker-support.md |  2 +-
 ...s.md => guidelines-for-gdpr-compliance.md} |  2 +-
 .../all/support/how-spryker-support-works.md  |  4 +-
 ... preparing-for-heavy-loads-and-traffic.md} |  2 +-
 ...lation.md => prioritzing-support-cases.md} | 12 +--
 ... => project-level-and-core-level-fixes.md} |  2 +-
 ...reporting-and-handling-security-issues.md} |  4 +-
 ...e-secrets-with-the-spryker-support-team.md |  4 +-
 ...lations.md => support-case-escalations.md} |  2 +-
 ...t-status.md => support-ticket-statuses.md} |  4 +-
 ...derstand-slas.md => understanding-slas.md} |  4 +-
 .../all/support/using-the-support-portal.md   |  8 +-
 docs/about/all/supported-browsers.md          |  8 +-
 docs/ca/dev/environment-provisioning.md       |  2 +-
 docs/dg/dev/product-and-code-releases.md      | 30 --------
 .../dev/troubleshooting/troubleshooting.md    |  2 +-
 41 files changed, 146 insertions(+), 134 deletions(-)
 rename docs/about/all/{intro-to-spryker.md => about-spryker.md} (99%)
 create mode 100644 docs/about/all/about-the-docs/about-spryker-docs.md
 rename docs/about/all/{about-the-documentation => about-the-docs}/add-global-sections-to-the-documentation.md (100%)
 rename docs/about/all/{about-the-documentation/contribute-to-the-documentation => about-the-docs/contribute-to-the-docs}/add-and-edit-diagrams-in-the-documentation.md (100%)
 rename docs/about/all/{about-the-documentation/contribute-to-the-documentation/contribute-to-the-documentation.md => about-the-docs/contribute-to-the-docs/contribute-to-the-docs.md} (98%)
 rename docs/about/all/{about-the-documentation/contribute-to-the-documentation => about-the-docs/contribute-to-the-docs}/edit-the-documentation-locally.md (100%)
 rename docs/about/all/{about-the-documentation/contribute-to-the-documentation => about-the-docs/contribute-to-the-docs}/edit-the-documentation-via-pull-requests.md (100%)
 rename docs/about/all/{about-the-documentation/contribute-to-the-documentation => about-the-docs/contribute-to-the-docs}/report-documentation-issues.md (100%)
 rename docs/about/all/{about-the-documentation/contribute-to-the-documentation => about-the-docs/contribute-to-the-docs}/review-pull-requests.md (100%)
 rename docs/about/all/{about-the-documentation => about-the-docs}/install-recommended-vs-code-extensions.md (100%)
 rename docs/about/all/{about-the-documentation => about-the-docs}/run-the-documentation-locally.md (100%)
 rename docs/about/all/{about-the-documentation => about-the-docs}/spryker-documentation-style-guide/examples.md (100%)
 rename docs/about/all/{about-the-documentation => about-the-docs}/spryker-documentation-style-guide/general-rules-and-guidance-for-adding-documents.md (100%)
 rename docs/about/all/{about-the-documentation => about-the-docs}/spryker-documentation-style-guide/markdown-syntax.md (100%)
 rename docs/about/all/{about-the-documentation => about-the-docs}/spryker-documentation-style-guide/spelling.md (100%)
 rename docs/about/all/{about-the-documentation => about-the-docs}/spryker-documentation-style-guide/spryker-documentation-style-guide.md (100%)
 rename docs/about/all/{about-the-documentation => about-the-docs}/spryker-documentation-style-guide/word-list.md (100%)
 delete mode 100644 docs/about/all/about-the-documentation/about-spryker-documentation.md
 create mode 100644 docs/about/all/releases/product-and-code-releases.md
 delete mode 100644 docs/about/all/releases/releases.md
 rename docs/about/all/support/{guidelines-for-new-gdpr-rules.md => guidelines-for-gdpr-compliance.md} (99%)
 rename docs/about/all/support/{special-prepare-for-a-busy-season.md => preparing-for-heavy-loads-and-traffic.md} (98%)
 rename docs/about/all/support/{case-escalation.md => prioritzing-support-cases.md} (90%)
 rename docs/about/all/support/{understanding-project-and-core-level-fixes.md => project-level-and-core-level-fixes.md} (97%)
 rename docs/about/all/support/{handling-security-issues.md => reporting-and-handling-security-issues.md} (95%)
 rename docs/about/all/support/{escalations.md => support-case-escalations.md} (99%)
 rename docs/about/all/support/{understanding-ticket-status.md => support-ticket-statuses.md} (98%)
 rename docs/about/all/support/{understand-slas.md => understanding-slas.md} (96%)
 delete mode 100644 docs/dg/dev/product-and-code-releases.md

diff --git a/_data/sidebars/about_all_sidebar.yml b/_data/sidebars/about_all_sidebar.yml
index 8b555ccb0de..516a53c1be3 100644
--- a/_data/sidebars/about_all_sidebar.yml
+++ b/_data/sidebars/about_all_sidebar.yml
@@ -7,7 +7,7 @@ entries:
     url: /docs/scos/user/intro-to-spryker/intro-to-spryker.html
     nested:
     - title: Releases
-      url: /docs/scos/user/intro-to-spryker/releases/releases.html
+      url: /docs/scos/user/intro-to-spryker/releases/product-and-code-releases.html
       nested:
       - title: Release notes
         url: /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes.html
@@ -61,16 +61,16 @@ entries:
         url: /docs/scos/user/intro-to-spryker/support/special-prepare-for-a-busy-season.html
       - title: How to use the Support Portal
         url: /docs/scos/user/intro-to-spryker/support/how-to-use-the-support-portal.html
-      - title: How to share secrets with the Spryker Support Team
-        url: /docs/scos/user/intro-to-spryker/support/how-to-share-secrets-with-the-spryker-support-team.html
+      - title: Share secrets with the Spryker Support Team
+        url: /docs/scos/user/intro-to-spryker/support/share-secrets-with-the-spryker-support-team.html
       - title: Understanding ticket status
         url: /docs/scos/user/intro-to-spryker/support/understanding-ticket-status.html
       - title: Handling security issues
         url: /docs/scos/user/intro-to-spryker/support/handling-security-issues.html
       - title: Guidelines for new GDPR rules
         url: /docs/scos/user/intro-to-spryker/support/guidelines-for-new-gdpr-rules.html
-      - title: How to get the most out of Spryker Support
-        url: /docs/scos/user/intro-to-spryker/support/how-to-get-the-most-out-of-spryker-support.html
+      - title: Getting the most out of Spryker Support
+        url: /docs/scos/user/intro-to-spryker/support/getting-the-most-out-of-spryker-support.html
       - title: Understand SLAs
         url: /docs/scos/user/intro-to-spryker/support/understand-slas.html
       - title: Escalations
diff --git a/_includes/pbc/all/install-features/202307.0/feature-integration-guides.md b/_includes/pbc/all/install-features/202307.0/feature-integration-guides.md
index 1b24aed2528..f8c9e0551e7 100644
--- a/_includes/pbc/all/install-features/202307.0/feature-integration-guides.md
+++ b/_includes/pbc/all/install-features/202307.0/feature-integration-guides.md
@@ -4,6 +4,6 @@ The integration guides provide step-by-step instructions on how to enable indivi
 
 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.
+If you have spotted an issue with either of the guides, 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/about/all/intro-to-spryker.md b/docs/about/all/about-spryker.md
similarity index 99%
rename from docs/about/all/intro-to-spryker.md
rename to docs/about/all/about-spryker.md
index 10032e9368e..536683cad12 100644
--- a/docs/about/all/intro-to-spryker.md
+++ b/docs/about/all/about-spryker.md
@@ -1,5 +1,5 @@
 ---
-title: Intro to Spryker
+title: About Spryker
 description: High-level overview of Spryker Cloud Commerce OS
 last_updated: Sep 9, 2021
 template: concept-topic-template
diff --git a/docs/about/all/about-the-docs/about-spryker-docs.md b/docs/about/all/about-the-docs/about-spryker-docs.md
new file mode 100644
index 00000000000..0a9fa03df8b
--- /dev/null
+++ b/docs/about/all/about-the-docs/about-spryker-docs.md
@@ -0,0 +1,24 @@
+---
+title: About Spryker docs
+description: One-stop hub for everything about Spryker
+last_updated: Mar 4, 2024
+template: concept-topic-template
+---
+
+Spryker docs are your one-stop hub for all the information about Spryker Cloud Commerce OS.
+
+## The source of truth
+
+When it comes to knowledge sharing, we rely on the docs as the main source of truth. Both external and internal users refer to the docs when developing projects, designing [Spryker Safari courses](), creating new or customizing the existing functionality.
+
+## Owned by the Spryker community
+
+The expertise in Spryker is shared among the many engineers and entrepreneurs creating all sorts of projects based on Spryker. That's why the docs are open to any type of contribution: from simple bug fixes to sharing how you managed to solve a complex problem or build around an interesting use case.
+
+## What's in the docs
+
+The docs are focused on covering all the functionality that comes with Spryker and how to build projects with that functionality. Because the docs are community-owned, the content adapts to the users' demands. If you don't find the information you are looking for, feel free to [create an issue](https://github.com/spryker/spryker-docs/issues) and we will look into covering the topic. Or ask the Spryker community at [CommerceQuest](https://commercequest.space/).
+
+## Next step
+
+[Contribute to the docs](/docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.html)
diff --git a/docs/about/all/about-the-documentation/add-global-sections-to-the-documentation.md b/docs/about/all/about-the-docs/add-global-sections-to-the-documentation.md
similarity index 100%
rename from docs/about/all/about-the-documentation/add-global-sections-to-the-documentation.md
rename to docs/about/all/about-the-docs/add-global-sections-to-the-documentation.md
diff --git a/docs/about/all/about-the-documentation/contribute-to-the-documentation/add-and-edit-diagrams-in-the-documentation.md b/docs/about/all/about-the-docs/contribute-to-the-docs/add-and-edit-diagrams-in-the-documentation.md
similarity index 100%
rename from docs/about/all/about-the-documentation/contribute-to-the-documentation/add-and-edit-diagrams-in-the-documentation.md
rename to docs/about/all/about-the-docs/contribute-to-the-docs/add-and-edit-diagrams-in-the-documentation.md
diff --git a/docs/about/all/about-the-documentation/contribute-to-the-documentation/contribute-to-the-documentation.md b/docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.md
similarity index 98%
rename from docs/about/all/about-the-documentation/contribute-to-the-documentation/contribute-to-the-documentation.md
rename to docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.md
index 5015701cf2c..8e6434c67d7 100644
--- a/docs/about/all/about-the-documentation/contribute-to-the-documentation/contribute-to-the-documentation.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.md
@@ -1,5 +1,5 @@
 ---
-title: Contribute to the documentation
+title: Contribute to the docs
 description: Learn how you can contribute to the Spryker docs.
 last_updated: Jul 18, 2022
 template: howto-guide-template
diff --git a/docs/about/all/about-the-documentation/contribute-to-the-documentation/edit-the-documentation-locally.md b/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-documentation-locally.md
similarity index 100%
rename from docs/about/all/about-the-documentation/contribute-to-the-documentation/edit-the-documentation-locally.md
rename to docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-documentation-locally.md
diff --git a/docs/about/all/about-the-documentation/contribute-to-the-documentation/edit-the-documentation-via-pull-requests.md b/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-documentation-via-pull-requests.md
similarity index 100%
rename from docs/about/all/about-the-documentation/contribute-to-the-documentation/edit-the-documentation-via-pull-requests.md
rename to docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-documentation-via-pull-requests.md
diff --git a/docs/about/all/about-the-documentation/contribute-to-the-documentation/report-documentation-issues.md b/docs/about/all/about-the-docs/contribute-to-the-docs/report-documentation-issues.md
similarity index 100%
rename from docs/about/all/about-the-documentation/contribute-to-the-documentation/report-documentation-issues.md
rename to docs/about/all/about-the-docs/contribute-to-the-docs/report-documentation-issues.md
diff --git a/docs/about/all/about-the-documentation/contribute-to-the-documentation/review-pull-requests.md b/docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.md
similarity index 100%
rename from docs/about/all/about-the-documentation/contribute-to-the-documentation/review-pull-requests.md
rename to docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.md
diff --git a/docs/about/all/about-the-documentation/install-recommended-vs-code-extensions.md b/docs/about/all/about-the-docs/install-recommended-vs-code-extensions.md
similarity index 100%
rename from docs/about/all/about-the-documentation/install-recommended-vs-code-extensions.md
rename to docs/about/all/about-the-docs/install-recommended-vs-code-extensions.md
diff --git a/docs/about/all/about-the-documentation/run-the-documentation-locally.md b/docs/about/all/about-the-docs/run-the-documentation-locally.md
similarity index 100%
rename from docs/about/all/about-the-documentation/run-the-documentation-locally.md
rename to docs/about/all/about-the-docs/run-the-documentation-locally.md
diff --git a/docs/about/all/about-the-documentation/spryker-documentation-style-guide/examples.md b/docs/about/all/about-the-docs/spryker-documentation-style-guide/examples.md
similarity index 100%
rename from docs/about/all/about-the-documentation/spryker-documentation-style-guide/examples.md
rename to docs/about/all/about-the-docs/spryker-documentation-style-guide/examples.md
diff --git a/docs/about/all/about-the-documentation/spryker-documentation-style-guide/general-rules-and-guidance-for-adding-documents.md b/docs/about/all/about-the-docs/spryker-documentation-style-guide/general-rules-and-guidance-for-adding-documents.md
similarity index 100%
rename from docs/about/all/about-the-documentation/spryker-documentation-style-guide/general-rules-and-guidance-for-adding-documents.md
rename to docs/about/all/about-the-docs/spryker-documentation-style-guide/general-rules-and-guidance-for-adding-documents.md
diff --git a/docs/about/all/about-the-documentation/spryker-documentation-style-guide/markdown-syntax.md b/docs/about/all/about-the-docs/spryker-documentation-style-guide/markdown-syntax.md
similarity index 100%
rename from docs/about/all/about-the-documentation/spryker-documentation-style-guide/markdown-syntax.md
rename to docs/about/all/about-the-docs/spryker-documentation-style-guide/markdown-syntax.md
diff --git a/docs/about/all/about-the-documentation/spryker-documentation-style-guide/spelling.md b/docs/about/all/about-the-docs/spryker-documentation-style-guide/spelling.md
similarity index 100%
rename from docs/about/all/about-the-documentation/spryker-documentation-style-guide/spelling.md
rename to docs/about/all/about-the-docs/spryker-documentation-style-guide/spelling.md
diff --git a/docs/about/all/about-the-documentation/spryker-documentation-style-guide/spryker-documentation-style-guide.md b/docs/about/all/about-the-docs/spryker-documentation-style-guide/spryker-documentation-style-guide.md
similarity index 100%
rename from docs/about/all/about-the-documentation/spryker-documentation-style-guide/spryker-documentation-style-guide.md
rename to docs/about/all/about-the-docs/spryker-documentation-style-guide/spryker-documentation-style-guide.md
diff --git a/docs/about/all/about-the-documentation/spryker-documentation-style-guide/word-list.md b/docs/about/all/about-the-docs/spryker-documentation-style-guide/word-list.md
similarity index 100%
rename from docs/about/all/about-the-documentation/spryker-documentation-style-guide/word-list.md
rename to docs/about/all/about-the-docs/spryker-documentation-style-guide/word-list.md
diff --git a/docs/about/all/about-the-documentation/about-spryker-documentation.md b/docs/about/all/about-the-documentation/about-spryker-documentation.md
deleted file mode 100644
index e69de29bb2d..00000000000
diff --git a/docs/about/all/releases/product-and-code-releases.md b/docs/about/all/releases/product-and-code-releases.md
new file mode 100644
index 00000000000..f5037a93571
--- /dev/null
+++ b/docs/about/all/releases/product-and-code-releases.md
@@ -0,0 +1,76 @@
+---
+title: Product and code releases
+last_updated: Mar 4, 2024
+template: concept-topic-template
+originalLink: https://documentation.spryker.com/2021080/docs/spryker-release-process
+originalArticleId: 3195aac4-0b8e-43a7-b540-0222f567c9fc
+redirect_from:
+- /docs/scos/user/intro-to-spryker/releases/releases.html
+- /docs/scos/user/intro-to-spryker/releases/releases-archive.html
+- /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-april-1-2017.html
+- /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-april-2-2017.html
+- /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-may-1-2017.html
+- /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-may-2-2017.html
+- /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-june-1-2017.html
+- /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-june-2-2017.html
+- /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-july-1-2017.html
+- /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-july-2-2017.html
+- /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-august-1-2017.html
+- /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-august-2-2017.html
+- /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-september-1-2017.html
+- /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-september-2-2017.html
+- /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-october-1-2017.html
+- /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-october-2-2017.html
+- /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-november-1-2017.html
+- /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-november-2-2017.html
+- /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-december-2017.html
+- /docs/scos/user/intro-to-spryker/releases/archive/2018/release-notes-january-2018.html
+- /docs/scos/user/intro-to-spryker/releases/archive/2018/release-notes-february-2-2018.html
+- /docs/scos/user/intro-to-spryker/releases/archive/2018/release-notes-february-1-2018.html
+- /docs/scos/user/intro-to-spryker/releases/archive/2018/release-notes-march-2018.html
+- /docs/scos/user/intro-to-spryker/releases/archive/2018/release-notes-april-2018.html
+- /docs/scos/user/intro-to-spryker/whats-new/security-updates.html
+- /docs/scos/user/intro-to-spryker/spryker-release-process.html
+
+---
+
+To accommodate both the fast pace of innovation and predictability of the upgrade process, we support two types of releases: atomic (code) releases and product releases.
+
+![Product releases flow](https://spryker.s3.eu-central-1.amazonaws.com/docs/About/Releases/Release+notes/image2018-8-10_17-10-26.png)
+
+## Atomic (code) releases
+
+Atomic, or code release approach, implies that we introduce changes gradually and release updates only for the modified modules. So you don’t need to invest time in updating all the modules available in your project every time there is an update. Each Spryker module is released independently and has its own version. Also, every module has its own repository and dependencies declared in a `composer.json` file, which means you can select a specific module version and update it separately.
+
+New versions of the existing Spryker modules as well as new modules are released as soon as they are ready in the [Spryker Commerce OS \(SCOS\) project repository](https://github.com/spryker-shop/suite).
+
+The main benefit of the Code Releases is that customers who urgently need this new functionality can get access to it immediately. Such speed comes, of course, with some drawbacks.
+
+We are making sure to provide draft documentation for the new functionality, as well as a module-level migration guide. Still, we cannot deliver full documentation and training materials at that time. Our QA team validates the newly released functionality and overall quality of the module but cannot thoroughly check the new module's compatibility with other modules in all required combinations.
+
+Also, Code Releases are not incorporated into the Demo Shops and can contain beta versions on modules.
+
+## Product releases
+
+A product release is done every several months. The product release has its own version and is accompanied by [release notes](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes.html).  The product release code is stored in our [B2B Demo Shop repository](https://github.com/spryker-shop/b2b-demo-shop) and [B2C Demo Shop repository](https://github.com/spryker-shop/b2c-demo-shop) and includes a specific feature set that we believe is best suitable for each vertical.
+
+A product release does not include beta modules. All of its features are integrated and tested in the Demo Shops, as well as fully documented.
+
+## Release history
+
+See [release-history](https://api.release.spryker.com/release-history) for latest releases including necessary project changes.
+It also comes with an RSS feed.
+
+## Mailing lists
+
+We recommend that you subscribe to our release newsletter and security updates mailing lists so that we can let you know about new features and be immediately informed of any security updates that you need to know about.
+
+To join our release notes mailing list, subscribe here:
+
+<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="b4d730db-d20e-4bb4-bd80-4cd7c9a2dc21" id="hubspot-1"></div>
+
+To receive the security updates, please request the subsription at [support@spryker.com](mailto:support@spryker.com).
+
+## Next steps
+
+* [Release notes](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes.html)
diff --git a/docs/about/all/releases/release-notes/release-notes.md b/docs/about/all/releases/release-notes/release-notes.md
index 1add842ac60..91a640e53ae 100644
--- a/docs/about/all/releases/release-notes/release-notes.md
+++ b/docs/about/all/releases/release-notes/release-notes.md
@@ -8,9 +8,6 @@ originalArticleId: 2da5568d-0a6b-4d0a-945f-8de92cb69ee1
 redirect_from:
 - /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes.html
 
-related:
-  - title: Release notes 202204.0
-    link: docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202204.0/release-notes-202204.0.html
 ---
 
 Here you can find the latest Product release notes and the archived content.
diff --git a/docs/about/all/releases/releases.md b/docs/about/all/releases/releases.md
deleted file mode 100644
index ba0cbabb650..00000000000
--- a/docs/about/all/releases/releases.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: Releases
-description: This section contains the notes for each release made by Spryker.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/releases
-originalArticleId: e2f76a3b-1e2e-4c57-8812-bf46dac54b10
-redirect_from:
-  - /docs/scos/user/intro-to-spryker/releases/releases.html
-  - /docs/scos/user/intro-to-spryker/releases/releases-archive.html
-  - /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-april-1-2017.html
-  - /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-april-2-2017.html
-  - /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-may-1-2017.html
-  - /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-may-2-2017.html
-  - /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-june-1-2017.html
-  - /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-june-2-2017.html
-  - /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-july-1-2017.html
-  - /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-july-2-2017.html
-  - /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-august-1-2017.html
-  - /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-august-2-2017.html
-  - /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-september-1-2017.html
-  - /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-september-2-2017.html
-  - /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-october-1-2017.html
-  - /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-october-2-2017.html
-  - /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-november-1-2017.html
-  - /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-november-2-2017.html
-  - /docs/scos/user/intro-to-spryker/releases/archive/2017/release-notes-december-2017.html
-  - /docs/scos/user/intro-to-spryker/releases/archive/2018/release-notes-january-2018.html
-  - /docs/scos/user/intro-to-spryker/releases/archive/2018/release-notes-february-2-2018.html
-  - /docs/scos/user/intro-to-spryker/releases/archive/2018/release-notes-february-1-2018.html
-  - /docs/scos/user/intro-to-spryker/releases/archive/2018/release-notes-march-2018.html
-  - /docs/scos/user/intro-to-spryker/releases/archive/2018/release-notes-april-2018.html
-  - /docs/scos/user/intro-to-spryker/whats-new/security-updates.html
-
----
-
-This section contains the notes for each [Product release](/docs/scos/user/intro-to-spryker/spryker-release-process.html#product-releases) made by Spryker. Make sure that you check this section from time-to-time to stay up to date with the improvements, bug fixes and new features that are delivered by our team.
-
-## Release history
-
-See [release-history](https://api.release.spryker.com/release-history) for latest releases including necessary project changes.
-It also comes with an RSS feed.
-
-## Mailing lists
-
-We recommend that you subscribe to our release newsletter and security updates mailing lists so that we can let you know about new features and be immediately informed of any security updates that you need to know about.
-
-To join our release notes mailing list, subscribe here:
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="b4d730db-d20e-4bb4-bd80-4cd7c9a2dc21" id="hubspot-1"></div>
-
-To receive the security updates, please request the subsription at [support@spryker.com](mailto:support@spryker.com).
-
-## Next steps
-
-* [Checking for newer versions](/docs/dg/dev/set-up-spryker-locally/manage-dependencies-with-composer.html)
-* [Release notes](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes.html)
diff --git a/docs/about/all/support/contacting-spryker-support.md b/docs/about/all/support/contacting-spryker-support.md
index 329c90ebf12..1a40a7fe3d7 100644
--- a/docs/about/all/support/contacting-spryker-support.md
+++ b/docs/about/all/support/contacting-spryker-support.md
@@ -9,8 +9,8 @@ redirect_from:
 related:
   - title: How Spryker Support works
     link: docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html
-  - title: How to get the most out of Spryker Support
-    link: docs/scos/user/intro-to-spryker/support/how-to-get-the-most-out-of-spryker-support.html
+  - title: Getting the most out of Spryker Support
+    link: docs/scos/user/intro-to-spryker/support/getting-the-most-out-of-spryker-support.html
   - title: How to use the Support Portal
     link: docs/scos/user/intro-to-spryker/support/how-to-use-the-support-portal.html
 ---
@@ -21,8 +21,8 @@ related:
 *Photo by [@snapwire](https://www.pexels.com/@snapwire)*
 
 -->
-To contact Spryker Support, use [Spryker Support Portal](https://support.spryker.com)
+To contact Spryker Support, use [Spryker Support Portal](https://support.spryker.com).
 
 Opening a case using this form is the preferred way, as the form helps you include information we need to get working on a case immediately and speed up our case resolution time.
 
-If your case is not an emergency, take the time to learn [How Spryker Support works](/docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html) and [How to get the most out of Spryker Support](/docs/scos/user/intro-to-spryker/support/how-to-get-the-most-out-of-spryker-support.html). Both documents give valuable insights into the inner workings of Spryker Support and let you help us to provide an excellent support experience for you.
+If your case is not an emergency, take the time to learn [How Spryker Support works](/docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html) and [Getting the most out of Spryker Support](/docs/scos/user/intro-to-spryker/support/getting-the-most-out-of-spryker-support.html). Both documents give valuable insights into the inner workings of Spryker Support and let you help us to provide an excellent support experience for you.
diff --git a/docs/about/all/support/getting-support.md b/docs/about/all/support/getting-support.md
index 3cbb01d54aa..3ab20cccd00 100644
--- a/docs/about/all/support/getting-support.md
+++ b/docs/about/all/support/getting-support.md
@@ -12,8 +12,8 @@ related:
     link: docs/scos/user/intro-to-spryker/support/how-to-use-the-support-portal.html
   - title: How Spryker Support works
     link: docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html
-  - title: How to get the most out of Spryker Support
-    link: docs/scos/user/intro-to-spryker/support/how-to-get-the-most-out-of-spryker-support.html
+  - title: Getting the most out of Spryker Support
+    link: docs/scos/user/intro-to-spryker/support/getting-the-most-out-of-spryker-support.html
 
 ---
 
diff --git a/docs/about/all/support/getting-the-most-out-of-spryker-support.md b/docs/about/all/support/getting-the-most-out-of-spryker-support.md
index bbe4da3499f..e84bf0513cc 100644
--- a/docs/about/all/support/getting-the-most-out-of-spryker-support.md
+++ b/docs/about/all/support/getting-the-most-out-of-spryker-support.md
@@ -5,7 +5,7 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/how-to-get-the-most-out-of-spryker-support
 originalArticleId: 3ab286da-5f06-4035-bc52-0b0237ed410f
 redirect_from:
-- /docs/scos/user/intro-to-spryker/support/how-to-get-the-most-out-of-spryker-support.html
+- /docs/scos/user/intro-to-spryker/support/getting-the-most-out-of-spryker-support.html
 related:
   - title: How Spryker Support works
     link: docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html
diff --git a/docs/about/all/support/guidelines-for-new-gdpr-rules.md b/docs/about/all/support/guidelines-for-gdpr-compliance.md
similarity index 99%
rename from docs/about/all/support/guidelines-for-new-gdpr-rules.md
rename to docs/about/all/support/guidelines-for-gdpr-compliance.md
index d4f1426a415..884de3d9e95 100644
--- a/docs/about/all/support/guidelines-for-new-gdpr-rules.md
+++ b/docs/about/all/support/guidelines-for-gdpr-compliance.md
@@ -1,5 +1,5 @@
 ---
-title: Guidelines for new GDPR rules
+title: Guidelines for GDPR compliance
 description: GDPR contains rules relating to the protection and control of personal data.
 last_updated: Jun 16, 2021
 template: concept-topic-template
diff --git a/docs/about/all/support/how-spryker-support-works.md b/docs/about/all/support/how-spryker-support-works.md
index a85daca99f4..535588d6d3a 100644
--- a/docs/about/all/support/how-spryker-support-works.md
+++ b/docs/about/all/support/how-spryker-support-works.md
@@ -7,8 +7,8 @@ originalArticleId: 2923122e-fde2-4893-98df-1375f8cc7742
 redirect_from:
 - /docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html
 related:
-  - title: How to get the most out of Spryker Support
-    link: docs/scos/user/intro-to-spryker/support/how-to-get-the-most-out-of-spryker-support.html
+  - title: Getting the most out of Spryker Support
+    link: docs/scos/user/intro-to-spryker/support/getting-the-most-out-of-spryker-support.html
   - title: How to use the Support Portal
     link: docs/scos/user/intro-to-spryker/support/how-to-use-the-support-portal.html
 ---
diff --git a/docs/about/all/support/special-prepare-for-a-busy-season.md b/docs/about/all/support/preparing-for-heavy-loads-and-traffic.md
similarity index 98%
rename from docs/about/all/support/special-prepare-for-a-busy-season.md
rename to docs/about/all/support/preparing-for-heavy-loads-and-traffic.md
index ce648705294..ab16cbfdaca 100644
--- a/docs/about/all/support/special-prepare-for-a-busy-season.md
+++ b/docs/about/all/support/preparing-for-heavy-loads-and-traffic.md
@@ -1,5 +1,5 @@
 ---
-title: Special- Prepare for a busy season
+title: Preparing for heavy loads and traffic
 last_updated: Jun 16, 2021
 template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/special-prepare-for-a-busy-season
diff --git a/docs/about/all/support/case-escalation.md b/docs/about/all/support/prioritzing-support-cases.md
similarity index 90%
rename from docs/about/all/support/case-escalation.md
rename to docs/about/all/support/prioritzing-support-cases.md
index de369fd0550..e7d27e2b428 100644
--- a/docs/about/all/support/case-escalation.md
+++ b/docs/about/all/support/prioritzing-support-cases.md
@@ -1,5 +1,5 @@
 ---
-title: Case escalation
+title: Prioritizing support cases
 last_updated: Sep 6, 2021
 template: concept-topic-template
 originalLink: https://documentation.spryker.com/docs/scos/user/intro-to-spryker/support/understanding-ticket-status.html#how-are-bug-tickets-prioritized
@@ -10,15 +10,15 @@ redirect_from:
   - /docs/scos/user/intro-to-spryker/support/business-impact-and-case-priorities.html
 ---
 
-## How does Spryker prioritize cases?
-While we are trying to solve cases on time, we need to triage and prioritize cases on a daily basis. When you create cases, you can already indicate how urgent a case is for you by choosing the correct case type and business impact and provide adequate info to help us assess how important your case is in relation to other cases that are in our backlog. At the end of the day, how high or low a case is prioritized by the support team is a function of the following:
+
+While we are trying to solve cases on time, we need to triage and prioritize cases on a daily basis. When you create a case, you can indicate how urgent it's for you by choosing the correct case type and business impact and provide adequate info to help us assess how important your case is in relation to other cases that are in our backlog. At the end of the day, how high or low a case is prioritized by the support team is a function of the following:
 * The business impact specified by the partner/customer and the explanation provided for it
 * The subject matter
 * The overall state and context of the project
 
-{% info_block infoBox "Info" %}
+{% info_block infoBox "" %}
 
-Prioritization is only one aspect that influences how fast your case is solved. To learn important tips about what you can do to speed up resolution times, see [How to get the most out of Spryker Support](/docs/scos/user/intro-to-spryker/support/how-to-get-the-most-out-of-spryker-support.html).
+Prioritization is only one aspect that influences how fast your case is solved. To learn important tips about what you can do to speed up resolution times, see [Getting the most out of Spryker Support](/docs/scos/user/intro-to-spryker/support/getting-the-most-out-of-spryker-support.html).
 
 {% endinfo_block %}
 
@@ -28,7 +28,7 @@ By specifying the business impact, you can tell us directly how severely an issu
 
 *P1—Urgent*: this is reserved for outages on production environments, security incidents, or issues that directly impact the normal flow of your business and for which you were not able to find an appropriate workaround.
 Here are some examples of cases with P1 business impact:
-* Your Spryker Shop is no longer reachable.
+* Your shop is no longer reachable.
 * You suspect that there is a security flaw that is actively being exploited.
 * It is no longer possible for customers to use your shop in an intended way, and this impacts your revenue.
 * An issue blocks you from going live with your shop.
diff --git a/docs/about/all/support/understanding-project-and-core-level-fixes.md b/docs/about/all/support/project-level-and-core-level-fixes.md
similarity index 97%
rename from docs/about/all/support/understanding-project-and-core-level-fixes.md
rename to docs/about/all/support/project-level-and-core-level-fixes.md
index 3b611d3699b..86753a74659 100644
--- a/docs/about/all/support/understanding-project-and-core-level-fixes.md
+++ b/docs/about/all/support/project-level-and-core-level-fixes.md
@@ -1,5 +1,5 @@
 ---
-title: Understanding Project and Core Level Fixes
+title: Project-level and core-level fixes
 last_updated: Jun 16, 2021
 template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/understanding-project-and-core-level-fixes
diff --git a/docs/about/all/support/handling-security-issues.md b/docs/about/all/support/reporting-and-handling-security-issues.md
similarity index 95%
rename from docs/about/all/support/handling-security-issues.md
rename to docs/about/all/support/reporting-and-handling-security-issues.md
index a0d620c0093..f9de17e4eb3 100644
--- a/docs/about/all/support/handling-security-issues.md
+++ b/docs/about/all/support/reporting-and-handling-security-issues.md
@@ -1,5 +1,5 @@
 ---
-title: Handling security issues
+title: Reporting and handling security issues
 description: Use this article to learn how to report a security issue and to understand how we handle these reports.
 last_updated: Jun 16, 2021
 template: concept-topic-template
@@ -9,7 +9,7 @@ redirect_from:
 - /docs/scos/user/intro-to-spryker/support/handling-security-issues.html
 ---
 
-If you find a security issue in a Spryker product, please report it to us.
+If you find a security issue in a Spryker product, report it to us.
 
 ## Reporting a security issue
 
diff --git a/docs/about/all/support/share-secrets-with-the-spryker-support-team.md b/docs/about/all/support/share-secrets-with-the-spryker-support-team.md
index 30e25476646..e76cf940037 100644
--- a/docs/about/all/support/share-secrets-with-the-spryker-support-team.md
+++ b/docs/about/all/support/share-secrets-with-the-spryker-support-team.md
@@ -1,12 +1,12 @@
 ---
 title: Share secrets with the Spryker Support Team
-description: Learn how to share secrets with the Spryker Support Team
+description: Learn Share secrets with the Spryker Support Team
 last_updated: Jun 16, 2021
 template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/how-to-share-secrets-with-the-spryker-support-team
 originalArticleId: a52e18a4-1aee-4f08-a132-82940f1f207e
 redirect_from:
-- /docs/scos/user/intro-to-spryker/support/how-to-share-secrets-with-the-spryker-support-team.html
+- /docs/scos/user/intro-to-spryker/support/share-secrets-with-the-spryker-support-team.html
 ---
 
 This document explains how you can securely share secrets or credentials with the [Spryker Support Team](/docs/scos/user/intro-to-spryker/support/getting-support.html). In general, the safest way to share secrets is not to share them, but if the situation demands it, we ask you to share secrets only the way described in this document.
diff --git a/docs/about/all/support/escalations.md b/docs/about/all/support/support-case-escalations.md
similarity index 99%
rename from docs/about/all/support/escalations.md
rename to docs/about/all/support/support-case-escalations.md
index 2a91dc38b6a..bf15e9a459e 100644
--- a/docs/about/all/support/escalations.md
+++ b/docs/about/all/support/support-case-escalations.md
@@ -1,5 +1,5 @@
 ---
-title: Escalations
+title: Support case escalations
 last_updated: Oct 25, 2021
 template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/case-escalation
diff --git a/docs/about/all/support/understanding-ticket-status.md b/docs/about/all/support/support-ticket-statuses.md
similarity index 98%
rename from docs/about/all/support/understanding-ticket-status.md
rename to docs/about/all/support/support-ticket-statuses.md
index 6c6518501f3..e16db186d0b 100644
--- a/docs/about/all/support/understanding-ticket-status.md
+++ b/docs/about/all/support/support-ticket-statuses.md
@@ -1,5 +1,5 @@
 ---
-title: Understanding ticket status
+title: Support ticket statuses
 last_updated: Oct 8, 2021
 template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/understanding-ticket-status
@@ -52,5 +52,5 @@ Before getting processed, most bug tickets spend some time in the `New` status.
 
 For Cloud tickets, we are currently starting a Beta Test where we communicate ETAs to our partners and customers. These ETAs are not binding delivery dates but should serve as a rough indicator of when we can finish a particular task. These ETAs are communicated by a status notification (email) and are listed in the case detail view on the support portals.
 
-## How are bug tickets prioritized?
+## Prioritizing bug tickets
 In general, bugs that impact many customers, business, and security receive the highest priority and are regularly put on the top of the queue. However, even if things are not clear-cut, we take the prioritization of bug tickets very seriously. We have a team comprised of members of various teams, such as Customer Success, Support, and Engineering, meeting weekly to make sure prioritization is evaluated regularly and from different perspectives.
diff --git a/docs/about/all/support/understand-slas.md b/docs/about/all/support/understanding-slas.md
similarity index 96%
rename from docs/about/all/support/understand-slas.md
rename to docs/about/all/support/understanding-slas.md
index ec75287ded3..15a73208358 100644
--- a/docs/about/all/support/understand-slas.md
+++ b/docs/about/all/support/understanding-slas.md
@@ -1,5 +1,5 @@
 ---
-title: Understand SLAs
+title: Understanding SLAs
 last_updated: Sep 6, 2021
 template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/understand-slas
@@ -26,7 +26,7 @@ At Spryker people from around the world work together to provide outstanding pro
 If you discover a problem with Spryker Software, please let us know immediately. Avoid ignoring a problem that you find, or work around it without reporting it to us. Not only would this prevent us from making our software better, but your workaround might not be maintainable and could cause you problems with upgradability or reduce your flexibility sometime in the future.
 
 ### Bring the right information
-Ensure that every case you open with us includes the information we need to work on it. To learn what info matters most, see [How to get the most out of Spryker Support](/docs/scos/user/intro-to-spryker/support/how-to-get-the-most-out-of-spryker-support.html).
+Ensure that every case you open with us includes the information we need to work on it. To learn what info matters most, see [Getting the most out of Spryker Support](/docs/scos/user/intro-to-spryker/support/getting-the-most-out-of-spryker-support.html).
 
 ### Assess business impact realistically
 To make sure that we resolve the right cases first, we need to triage and prioritize. You can help us to do this better if you assess and specify the business impact of your problem appropriately. For a more detailed explanation of what business impact is and how priorities work have a look into this [article](/docs/scos/user/intro-to-spryker/support/understanding-ticket-status.html#how-are-bug-tickets-prioritized).
diff --git a/docs/about/all/support/using-the-support-portal.md b/docs/about/all/support/using-the-support-portal.md
index 007c98ac313..96234d89d2f 100644
--- a/docs/about/all/support/using-the-support-portal.md
+++ b/docs/about/all/support/using-the-support-portal.md
@@ -9,8 +9,8 @@ redirect_from:
 related:
   - title: How Spryker Support works
     link: docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html
-  - title: How to get the most out of Spryker Support
-    link: docs/scos/user/intro-to-spryker/support/how-to-get-the-most-out-of-spryker-support.html
+  - title: Getting the most out of Spryker Support
+    link: docs/scos/user/intro-to-spryker/support/getting-the-most-out-of-spryker-support.html
 ---
 
 This document describes how to use the support portal to create and manage your cases.
@@ -18,11 +18,11 @@ This document describes how to use the support portal to create and manage your
 ## Prerequisites
 
 You already have a customer login provisioned for you. If you do not have an account yet, request one using this form.
-You can log in to the[ support portal](https://support.spryker.com) by using the login button on the top right.
+You can log in to the [support portal](https://support.spryker.com) by using the login button on the top right.
 
 ## Create new cases
 
-To create new cases, you can use the **Create a case** drop-down menu and select the respective case type, or click on the case type on the landing page. When creating cases, make use of the recommendations explained in [How to share secrets with the Spryker Support Team](/docs/scos/user/intro-to-spryker/support/how-to-share-secrets-with-the-spryker-support-team.html).
+To create new cases, you can use the **Create a case** drop-down menu and select the respective case type, or click on the case type on the landing page. When creating cases, make use of the recommendations explained in [Share secrets with the Spryker Support Team](/docs/scos/user/intro-to-spryker/support/share-secrets-with-the-spryker-support-team.html).
 
 ### Questions
 
diff --git a/docs/about/all/supported-browsers.md b/docs/about/all/supported-browsers.md
index 97f02258f22..a587cc4e603 100644
--- a/docs/about/all/supported-browsers.md
+++ b/docs/about/all/supported-browsers.md
@@ -10,13 +10,13 @@ redirect_from:
   - /docs/marketplace/dev/setup/202212.0/marketplace-supported-browsers.html
   - /docs/marketplace/dev/setup/202204.0/marketplace-supported-browsers.html
   - /docs/scos/user/intro-to-spryker/supported-browsers.html
-  
----
 
+---
+Spryker Cloud Commerce OS supports the following browsers.
 
 ## Base shop supported browsers
 
-The Spryker Commerce OS supports the following browsers for all frontend-related projects and products—[B2B Demo Shop](/docs/scos/user/intro-to-spryker/b2b-suite.html), [B2C Demo Shop](/docs/scos/user/intro-to-spryker/b2c-suite.html), [Master Suite](/docs/scos/user/intro-to-spryker/master-suite.html):
+[B2B suite](/docs/scos/user/intro-to-spryker/b2b-suite.html), [B2C suite](/docs/scos/user/intro-to-spryker/b2c-suite.html), and [Master suite](/docs/scos/user/intro-to-spryker/master-suite.html) support the following browsers:
 
 | DESKTOP: BACK OFFICE AND STOREFRONT | MOBILE: STOREFRONT | TABLET: STOREFRONT |
 | --- | --- | --- |
@@ -25,6 +25,8 @@ The Spryker Commerce OS supports the following browsers for all frontend-related
 
 ## Marketplace supported browsers
 
+[Marketplace B2C suite](/docs/about/all/spryker-marketplace/marketplace-b2c-suite.html) and [Marketplace B2B suite](/docs/about/all/spryker-marketplace/marketplace-b2b-suite.html) suite support the following browsers:
+
 | DESKTOP (MARKETPLACE AND MERCHANT PORTAL) | MOBILE (MARKETPLACE ONLY) | TABLET (MARKETPLACE AND MERCHANT PORTAL) |
 | --- | --- | --- |
 | *Browsers*: <ul><li> Windows, macOS: Chrome (latest version)</li> <li>Windows: Firefox (latest version)</li><li>Windows: Edge (latest version)</li><li>macOS: Safari (latest version)</li></ul> *Windows versions*:<ul><li>Windows 10</li><li>Windows 7</li></ul>*macOS versions*:<ul><li> Catalina 10 or later</li></ul>*Screen resolutions*:<ul><li>1024-1920 width</li></ul> | *Browsers*: <ul><li>iOS: Safari</li><li>Android: Chrome</li></ul>*Screen resolutions*:<ul><li>360x640—for example, Samsung Galaxy S8 or S9)</li><li>375x667—for example, iPhone 7 or 8</li><li>iPhone X, Xs, Xr</li></ul>*Android versions*:<ul><li>8.0</li></ul>*iOS versions*:<ul><li>iOS 13 or later</li></ul> | *Browsers*: <ul><li>iOS: Safari</li><li>Android: Chrome</li></ul>*iOS versions*:<ul><li>iOS 13</li></ul>*Screen resolutions*:<ul><li>1024x703—for example, iPad Air</li></ul> |
diff --git a/docs/ca/dev/environment-provisioning.md b/docs/ca/dev/environment-provisioning.md
index 39a09d820c3..87e1b951291 100644
--- a/docs/ca/dev/environment-provisioning.md
+++ b/docs/ca/dev/environment-provisioning.md
@@ -99,7 +99,7 @@ Similar to project names, you can't switch between these models after the enviro
 
 The repository is the place where the customer's Spryker application code resides. Spryker supports only GitHub, GitLab, and Bitbucket code hosting services. If the customer code base isn't ready, the Spryker team provisions the environment with the previously chosen Demo Dhop model from the most recent release using GitHub.
 
-GitHub: If the customer uses GitHub, provide a link to the GitHub repository, including a branch and a valid GitHub token. This allows code pipelines to access the repository. Ensure that you securely share the GitHub token according to [Spryker recommendations](/docs/scos/user/intro-to-spryker/support/how-to-share-secrets-with-the-spryker-support-team.html).
+GitHub: If the customer uses GitHub, provide a link to the GitHub repository, including a branch and a valid GitHub token. This allows code pipelines to access the repository. Ensure that you securely share the GitHub token according to [Spryker recommendations](/docs/scos/user/intro-to-spryker/support/share-secrets-with-the-spryker-support-team.html).
 
 GitLab and Bitbucket: Connecting GitLab and Bitbucket repositories directly to pipelines isn't supported. Therefore, we have to enable the codecommit feature during provisioning. Connections with pipelines can be established only after the environment is provisioned. If possible, grant GitLab or Bitbucket access to the Spryker engineer working on this request. If not, we'll use your deploy file along with the Spryker Demo Shop during provisioning. For detailed information about the connection process, see [Connect a GitLab code repository](/docs/ca/dev/connect-a-code-repository.html#connect-a-gitlab-code-repository) section in "Connecting a code repository".
 
diff --git a/docs/dg/dev/product-and-code-releases.md b/docs/dg/dev/product-and-code-releases.md
deleted file mode 100644
index 92651d6fb58..00000000000
--- a/docs/dg/dev/product-and-code-releases.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: Product and code releases
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/spryker-release-process
-originalArticleId: 3195aac4-0b8e-43a7-b540-0222f567c9fc
-redirect_from:
-- /docs/scos/user/intro-to-spryker/spryker-release-process.html
-
----
-
-To accommodate both the fast pace of innovation and predictability of the upgrade process, we support two types of releases: atomic (code) releases and product releases.
-
-![Product releases flow](https://spryker.s3.eu-central-1.amazonaws.com/docs/About/Releases/Release+notes/image2018-8-10_17-10-26.png)
-
-## Atomic (code) releases
-Atomic, or code release approach, implies that we introduce changes gradually and release updates only for the modified modules. So you don’t need to invest time in updating all the modules available in your project every time there is an update. Each Spryker module is released independently and has its own version. Also, every module has its own repository and dependencies declared in a `composer.json` file, which means you can select a specific module version and update it separately.
-
-New versions of the existing Spryker modules as well as new modules are released as soon as they are ready in the [Spryker Commerce OS \(SCOS\) project repository](https://github.com/spryker-shop/suite).
-
-The main benefit of the Code Releases is that customers who urgently need this new functionality can get access to it immediately. Such speed comes, of course, with some drawbacks.
-
-We are making sure to provide draft documentation for the new functionality, as well as a module-level migration guide. Still, we cannot deliver full documentation and training materials at that time. Our QA team validates the newly released functionality and overall quality of the module but cannot thoroughly check the new module's compatibility with other modules in all required combinations.
-
-Also, Code Releases are not incorporated into the Demo Shops and can contain beta versions on modules.
-
-## Product releases
-A product release is done every several months. The product release has its own version and is accompanied by [release notes](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes.html).  The product release code is stored in our [B2B Demo Shop repository](https://github.com/spryker-shop/b2b-demo-shop) and [B2C Demo Shop repository](https://github.com/spryker-shop/b2c-demo-shop) and includes a specific feature set that we believe is best suitable for each vertical.
-
-A product release does not include beta modules. All of its features are integrated and tested in the Demo Shops, as well as fully documented.
diff --git a/docs/scos/dev/troubleshooting/troubleshooting.md b/docs/scos/dev/troubleshooting/troubleshooting.md
index 250a10b28a4..510671c88fc 100644
--- a/docs/scos/dev/troubleshooting/troubleshooting.md
+++ b/docs/scos/dev/troubleshooting/troubleshooting.md
@@ -33,5 +33,5 @@ This section gives answers to common troubleshooting questions and includes the
 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:
 
 * [How Spryker support works](/docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html)
-* [How to get the most out of support](/docs/scos/user/intro-to-spryker/support/how-to-get-the-most-out-of-spryker-support.html)
+* [How to get the most out of support](/docs/scos/user/intro-to-spryker/support/getting-the-most-out-of-spryker-support.html)
 * [Understanding ticket status](/docs/scos/user/intro-to-spryker/support/understanding-ticket-status.html)

From de6a2873b999e4e07b9606f5fbf0b825446d0177 Mon Sep 17 00:00:00 2001
From: Andrii Tserkovnyi <andrii.tserkovnyi@spryker.com>
Date: Fri, 8 Mar 2024 11:22:23 +0200
Subject: [PATCH 06/26] rename

---
 ...2.0.md => patch-release-notes-202212.0.md} |  0
 .../all/about-the-docs/about-spryker-docs.md  |  2 +-
 ....md => add-global-sections-to-the-docs.md} |  4 +--
 ...d => add-and-edit-diagrams-in-the-docs.md} |  2 +-
 ...on-locally.md => edit-the-docs-locally.md} |  5 ++--
 ...d => edit-the-docs-using-a-web-browser.md} |  2 +-
 ...tation-issues.md => report-docs-issues.md} |  2 +-
 ...ion-locally.md => run-the-docs-locally.md} |  2 +-
 ...ral-rules-and-guidance-for-adding-docs.md} |  2 +-
 .../markdown-syntax.md                        |  0
 .../spryker-docs-style-guide.md}              |  2 +-
 .../style-guide-examples.md}                  |  2 +-
 .../style-guide-spelling.md}                  |  2 +-
 .../word-list.md                              |  0
 .../all/releases/product-and-code-releases.md |  3 +-
 .../release-notes-202211.0.md                 |  0
 .../patch-release-notes-202212.0.md}          |  2 +-
 .../release-notes-202212.0.md                 |  0
 .../security-release-notes-202212.0.md        |  0
 .../release-notes-202307.0.md                 |  0
 .../security-release-notes-202307.0.md        |  0
 .../release-notes-202311.0.md                 |  0
 .../releases/release-notes/release-notes.md   | 22 ---------------
 .../security-release-notes-202302.0.md        |  0
 .../security-release-notes-202304.0.md        |  0
 .../security-release-notes-202306.0.md        |  0
 .../security-release-notes-202309.0.md        |  0
 .../security-release-notes-202312.0.md        |  0
 .../all/support/contacting-spryker-support.md | 28 -------------------
 docs/about/all/support/getting-support.md     |  7 +++--
 docs/ca/dev/preparation-for-going-live.md     |  2 +-
 31 files changed, 23 insertions(+), 68 deletions(-)
 rename _includes/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/{patch-releases-202212.0.md => patch-release-notes-202212.0.md} (100%)
 rename docs/about/all/about-the-docs/{add-global-sections-to-the-documentation.md => add-global-sections-to-the-docs.md} (98%)
 rename docs/about/all/about-the-docs/contribute-to-the-docs/{add-and-edit-diagrams-in-the-documentation.md => add-and-edit-diagrams-in-the-docs.md} (98%)
 rename docs/about/all/about-the-docs/contribute-to-the-docs/{edit-the-documentation-locally.md => edit-the-docs-locally.md} (97%)
 rename docs/about/all/about-the-docs/contribute-to-the-docs/{edit-the-documentation-via-pull-requests.md => edit-the-docs-using-a-web-browser.md} (99%)
 rename docs/about/all/about-the-docs/contribute-to-the-docs/{report-documentation-issues.md => report-docs-issues.md} (98%)
 rename docs/about/all/about-the-docs/{run-the-documentation-locally.md => run-the-docs-locally.md} (99%)
 rename docs/about/all/about-the-docs/{spryker-documentation-style-guide/general-rules-and-guidance-for-adding-documents.md => style-guide/general-rules-and-guidance-for-adding-docs.md} (99%)
 rename docs/about/all/about-the-docs/{spryker-documentation-style-guide => style-guide}/markdown-syntax.md (100%)
 rename docs/about/all/about-the-docs/{spryker-documentation-style-guide/spryker-documentation-style-guide.md => style-guide/spryker-docs-style-guide.md} (96%)
 rename docs/about/all/about-the-docs/{spryker-documentation-style-guide/examples.md => style-guide/style-guide-examples.md} (97%)
 rename docs/about/all/about-the-docs/{spryker-documentation-style-guide/spelling.md => style-guide/style-guide-spelling.md} (92%)
 rename docs/about/all/about-the-docs/{spryker-documentation-style-guide => style-guide}/word-list.md (100%)
 rename docs/about/all/releases/{release-notes/release-notes-202211.0 => }/release-notes-202211.0.md (100%)
 rename docs/about/all/releases/{release-notes/release-notes-202212.0/patch-releases-202212.0.md => release-notes-202212.0/patch-release-notes-202212.0.md} (94%)
 rename docs/about/all/releases/{release-notes => }/release-notes-202212.0/release-notes-202212.0.md (100%)
 rename docs/about/all/releases/{release-notes => }/release-notes-202212.0/security-release-notes-202212.0.md (100%)
 rename docs/about/all/releases/{release-notes => }/release-notes-202307.0/release-notes-202307.0.md (100%)
 rename docs/about/all/releases/{release-notes => }/release-notes-202307.0/security-release-notes-202307.0.md (100%)
 rename docs/about/all/releases/{release-notes/release-notes-202311.0 => }/release-notes-202311.0.md (100%)
 delete mode 100644 docs/about/all/releases/release-notes/release-notes.md
 rename docs/about/all/releases/{release-notes/release-notes-202302.0 => }/security-release-notes-202302.0.md (100%)
 rename docs/about/all/releases/{release-notes/release-notes-202304.0 => }/security-release-notes-202304.0.md (100%)
 rename docs/about/all/releases/{release-notes => }/security-release-notes-202306.0.md (100%)
 rename docs/about/all/releases/{release-notes => }/security-release-notes-202309.0.md (100%)
 rename docs/about/all/releases/{release-notes => }/security-release-notes-202312.0.md (100%)
 delete mode 100644 docs/about/all/support/contacting-spryker-support.md

diff --git a/_includes/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.md b/_includes/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/patch-release-notes-202212.0.md
similarity index 100%
rename from _includes/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.md
rename to _includes/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/patch-release-notes-202212.0.md
diff --git a/docs/about/all/about-the-docs/about-spryker-docs.md b/docs/about/all/about-the-docs/about-spryker-docs.md
index 0a9fa03df8b..2bcbbf6eca1 100644
--- a/docs/about/all/about-the-docs/about-spryker-docs.md
+++ b/docs/about/all/about-the-docs/about-spryker-docs.md
@@ -9,7 +9,7 @@ Spryker docs are your one-stop hub for all the information about Spryker Cloud C
 
 ## The source of truth
 
-When it comes to knowledge sharing, we rely on the docs as the main source of truth. Both external and internal users refer to the docs when developing projects, designing [Spryker Safari courses](), creating new or customizing the existing functionality.
+When it comes to knowledge sharing, we rely on the docs as the main source of truth. Both external and internal users refer to the docs when developing projects, designing [Spryker Safari courses](https://safari.spryker.com/learn), creating new or customizing the existing functionality.
 
 ## Owned by the Spryker community
 
diff --git a/docs/about/all/about-the-docs/add-global-sections-to-the-documentation.md b/docs/about/all/about-the-docs/add-global-sections-to-the-docs.md
similarity index 98%
rename from docs/about/all/about-the-docs/add-global-sections-to-the-documentation.md
rename to docs/about/all/about-the-docs/add-global-sections-to-the-docs.md
index a00775aa2a9..eea15bdbb57 100644
--- a/docs/about/all/about-the-docs/add-global-sections-to-the-documentation.md
+++ b/docs/about/all/about-the-docs/add-global-sections-to-the-docs.md
@@ -1,5 +1,5 @@
 ---
-title: Add global sections to the documentation
+title: Add global sections to the docs
 description: Learn how to add a new global section to Spryker docs.
 last_updated: Jul 18, 2022
 template: howto-guide-template
@@ -291,4 +291,4 @@ task :check_mp_dev do
 ...  
 ```
 
-After you merge the PR and it's deployed to master, you will be able to search across the new section.
+After you merge the PR and it's deployed to master, you will see the added section on the website.
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/add-and-edit-diagrams-in-the-documentation.md b/docs/about/all/about-the-docs/contribute-to-the-docs/add-and-edit-diagrams-in-the-docs.md
similarity index 98%
rename from docs/about/all/about-the-docs/contribute-to-the-docs/add-and-edit-diagrams-in-the-documentation.md
rename to docs/about/all/about-the-docs/contribute-to-the-docs/add-and-edit-diagrams-in-the-docs.md
index f6d0123b26c..8702514796b 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/add-and-edit-diagrams-in-the-documentation.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/add-and-edit-diagrams-in-the-docs.md
@@ -1,5 +1,5 @@
 ---
-title: Add and edit diagrams in the documentation
+title: Add and edit diagrams in the docs
 description: Learn how to add and edit diagrams.net diagrams in Spryker documentation.
 last_updated: Dec 22, 2022
 template: howto-guide-template
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-documentation-locally.md b/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-locally.md
similarity index 97%
rename from docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-documentation-locally.md
rename to docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-locally.md
index 34bc02f5912..1c4da038bdf 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-documentation-locally.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-locally.md
@@ -1,10 +1,11 @@
-  - /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/edit-the-documentation-locally.html
 ---
-title: Edit the documentation locally
+title: Edit the docs locally
 description: Learn how edit the documentation on your machine.
 last_updated: Jan 23, 2023
 template: howto-guide-template
 redirect_from:
+- /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/edit-the-documentation-locally.html
+
 ---
 
 
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-documentation-via-pull-requests.md b/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.md
similarity index 99%
rename from docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-documentation-via-pull-requests.md
rename to docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.md
index 0711320b03e..3b33d1e5fda 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-documentation-via-pull-requests.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.md
@@ -1,5 +1,5 @@
 ---
-title: Edit the documentation using only a web browser
+title: Edit the docs using a web browser
 description: Learn how you can propose changes to the Spryker docs
 last_updated: Jul 18, 2022
 template: howto-guide-template
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/report-documentation-issues.md b/docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.md
similarity index 98%
rename from docs/about/all/about-the-docs/contribute-to-the-docs/report-documentation-issues.md
rename to docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.md
index 92c80e68386..be47e546d98 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/report-documentation-issues.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.md
@@ -1,5 +1,5 @@
 ---
-title: Report documentation issues
+title: Report docs issues
 description: Learn how to report an issue with Spryker docs.
 last_updated: Jul 18, 2022
 template: howto-guide-template
diff --git a/docs/about/all/about-the-docs/run-the-documentation-locally.md b/docs/about/all/about-the-docs/run-the-docs-locally.md
similarity index 99%
rename from docs/about/all/about-the-docs/run-the-documentation-locally.md
rename to docs/about/all/about-the-docs/run-the-docs-locally.md
index 9469b4fd58d..aaa5ff5d0dd 100644
--- a/docs/about/all/about-the-docs/run-the-documentation-locally.md
+++ b/docs/about/all/about-the-docs/run-the-docs-locally.md
@@ -1,5 +1,5 @@
 ---
-title: Run the documentation locally
+title: Run the docs locally
 description: Find out how you can build the Spryker documentation site
 last_updated: Jul 18, 2022
 template: howto-guide-template
diff --git a/docs/about/all/about-the-docs/spryker-documentation-style-guide/general-rules-and-guidance-for-adding-documents.md b/docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.md
similarity index 99%
rename from docs/about/all/about-the-docs/spryker-documentation-style-guide/general-rules-and-guidance-for-adding-documents.md
rename to docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.md
index 6b8dbd8124b..bb2147a0ae9 100644
--- a/docs/about/all/about-the-docs/spryker-documentation-style-guide/general-rules-and-guidance-for-adding-documents.md
+++ b/docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.md
@@ -1,5 +1,5 @@
 ---
-title: General rules and guidance for adding documents
+title: General rules and guidance for adding docs
 description: Learn how to style and format your docs.
 last_updated: Jul 18, 2022
 template: concept-topic-template
diff --git a/docs/about/all/about-the-docs/spryker-documentation-style-guide/markdown-syntax.md b/docs/about/all/about-the-docs/style-guide/markdown-syntax.md
similarity index 100%
rename from docs/about/all/about-the-docs/spryker-documentation-style-guide/markdown-syntax.md
rename to docs/about/all/about-the-docs/style-guide/markdown-syntax.md
diff --git a/docs/about/all/about-the-docs/spryker-documentation-style-guide/spryker-documentation-style-guide.md b/docs/about/all/about-the-docs/style-guide/spryker-docs-style-guide.md
similarity index 96%
rename from docs/about/all/about-the-docs/spryker-documentation-style-guide/spryker-documentation-style-guide.md
rename to docs/about/all/about-the-docs/style-guide/spryker-docs-style-guide.md
index b3b26950e75..f69d5f58537 100644
--- a/docs/about/all/about-the-docs/spryker-documentation-style-guide/spryker-documentation-style-guide.md
+++ b/docs/about/all/about-the-docs/style-guide/spryker-docs-style-guide.md
@@ -1,5 +1,5 @@
 ---
-title: Spryker documentation style guide
+title: Spryker docs style guide
 description:
 last_updated: Mar 23, 2023
 template: concept-topic-template
diff --git a/docs/about/all/about-the-docs/spryker-documentation-style-guide/examples.md b/docs/about/all/about-the-docs/style-guide/style-guide-examples.md
similarity index 97%
rename from docs/about/all/about-the-docs/spryker-documentation-style-guide/examples.md
rename to docs/about/all/about-the-docs/style-guide/style-guide-examples.md
index 16439a1565c..4800aded423 100644
--- a/docs/about/all/about-the-docs/spryker-documentation-style-guide/examples.md
+++ b/docs/about/all/about-the-docs/style-guide/style-guide-examples.md
@@ -1,5 +1,5 @@
 ---
-title: Examples
+title: "Style guide: Examples"
 description: Guidance for introducing examples in Spryker documentation
 last_updated: Mar 23, 2023
 template: concept-topic-template
diff --git a/docs/about/all/about-the-docs/spryker-documentation-style-guide/spelling.md b/docs/about/all/about-the-docs/style-guide/style-guide-spelling.md
similarity index 92%
rename from docs/about/all/about-the-docs/spryker-documentation-style-guide/spelling.md
rename to docs/about/all/about-the-docs/style-guide/style-guide-spelling.md
index 960aac603d9..de50dda01d8 100644
--- a/docs/about/all/about-the-docs/spryker-documentation-style-guide/spelling.md
+++ b/docs/about/all/about-the-docs/style-guide/style-guide-spelling.md
@@ -1,5 +1,5 @@
 ---
-title: Spelling
+title: "Style guide: Spelling"
 description: Guidance for spelling in Spryker documentation
 last_updated: Mar 23, 2023
 template: concept-topic-template
diff --git a/docs/about/all/about-the-docs/spryker-documentation-style-guide/word-list.md b/docs/about/all/about-the-docs/style-guide/word-list.md
similarity index 100%
rename from docs/about/all/about-the-docs/spryker-documentation-style-guide/word-list.md
rename to docs/about/all/about-the-docs/style-guide/word-list.md
diff --git a/docs/about/all/releases/product-and-code-releases.md b/docs/about/all/releases/product-and-code-releases.md
index f5037a93571..9a795a639aa 100644
--- a/docs/about/all/releases/product-and-code-releases.md
+++ b/docs/about/all/releases/product-and-code-releases.md
@@ -31,6 +31,7 @@ redirect_from:
 - /docs/scos/user/intro-to-spryker/releases/archive/2018/release-notes-april-2018.html
 - /docs/scos/user/intro-to-spryker/whats-new/security-updates.html
 - /docs/scos/user/intro-to-spryker/spryker-release-process.html
+- /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes.html
 
 ---
 
@@ -52,7 +53,7 @@ Also, Code Releases are not incorporated into the Demo Shops and can contain bet
 
 ## Product releases
 
-A product release is done every several months. The product release has its own version and is accompanied by [release notes](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes.html).  The product release code is stored in our [B2B Demo Shop repository](https://github.com/spryker-shop/b2b-demo-shop) and [B2C Demo Shop repository](https://github.com/spryker-shop/b2c-demo-shop) and includes a specific feature set that we believe is best suitable for each vertical.
+A product release happens every several months. A product release has its own version and is accompanied by release notes with a respective version. The product release code is stored in our [B2B Demo Shop repository](https://github.com/spryker-shop/b2b-demo-shop) and [B2C Demo Shop repository](https://github.com/spryker-shop/b2c-demo-shop) and includes a specific feature set that we believe is best suitable for each vertical.
 
 A product release does not include beta modules. All of its features are integrated and tested in the Demo Shops, as well as fully documented.
 
diff --git a/docs/about/all/releases/release-notes/release-notes-202211.0/release-notes-202211.0.md b/docs/about/all/releases/release-notes-202211.0.md
similarity index 100%
rename from docs/about/all/releases/release-notes/release-notes-202211.0/release-notes-202211.0.md
rename to docs/about/all/releases/release-notes-202211.0.md
diff --git a/docs/about/all/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.md b/docs/about/all/releases/release-notes-202212.0/patch-release-notes-202212.0.md
similarity index 94%
rename from docs/about/all/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.md
rename to docs/about/all/releases/release-notes-202212.0/patch-release-notes-202212.0.md
index a0a343f1885..4d00d38671c 100644
--- a/docs/about/all/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.md
+++ b/docs/about/all/releases/release-notes-202212.0/patch-release-notes-202212.0.md
@@ -1,5 +1,5 @@
 ---
-title: Patch releases 202212.0
+title: Patch release notes 202212.0
 description: Patch releases for the Spryker release 202212.0
 last_updated: Jan 31, 2023
 template: concept-topic-template
diff --git a/docs/about/all/releases/release-notes/release-notes-202212.0/release-notes-202212.0.md b/docs/about/all/releases/release-notes-202212.0/release-notes-202212.0.md
similarity index 100%
rename from docs/about/all/releases/release-notes/release-notes-202212.0/release-notes-202212.0.md
rename to docs/about/all/releases/release-notes-202212.0/release-notes-202212.0.md
diff --git a/docs/about/all/releases/release-notes/release-notes-202212.0/security-release-notes-202212.0.md b/docs/about/all/releases/release-notes-202212.0/security-release-notes-202212.0.md
similarity index 100%
rename from docs/about/all/releases/release-notes/release-notes-202212.0/security-release-notes-202212.0.md
rename to docs/about/all/releases/release-notes-202212.0/security-release-notes-202212.0.md
diff --git a/docs/about/all/releases/release-notes/release-notes-202307.0/release-notes-202307.0.md b/docs/about/all/releases/release-notes-202307.0/release-notes-202307.0.md
similarity index 100%
rename from docs/about/all/releases/release-notes/release-notes-202307.0/release-notes-202307.0.md
rename to docs/about/all/releases/release-notes-202307.0/release-notes-202307.0.md
diff --git a/docs/about/all/releases/release-notes/release-notes-202307.0/security-release-notes-202307.0.md b/docs/about/all/releases/release-notes-202307.0/security-release-notes-202307.0.md
similarity index 100%
rename from docs/about/all/releases/release-notes/release-notes-202307.0/security-release-notes-202307.0.md
rename to docs/about/all/releases/release-notes-202307.0/security-release-notes-202307.0.md
diff --git a/docs/about/all/releases/release-notes/release-notes-202311.0/release-notes-202311.0.md b/docs/about/all/releases/release-notes-202311.0.md
similarity index 100%
rename from docs/about/all/releases/release-notes/release-notes-202311.0/release-notes-202311.0.md
rename to docs/about/all/releases/release-notes-202311.0.md
diff --git a/docs/about/all/releases/release-notes/release-notes.md b/docs/about/all/releases/release-notes/release-notes.md
deleted file mode 100644
index 91a640e53ae..00000000000
--- a/docs/about/all/releases/release-notes/release-notes.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Release Notes
-description: The article describes the release flow of features and enhancements.
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/release-notes
-originalArticleId: 2da5568d-0a6b-4d0a-945f-8de92cb69ee1
-redirect_from:
-- /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes.html
-
----
-
-Here you can find the latest Product release notes and the archived content.
-
-Due to the nature of the Spryker Commerce OS, we have Product Releases every several months. Every Product Release has its own version. The release notes contain the respective release version in their names.
-The Product Release code is stored in the [B2B Demo Shop repository](https://github.com/spryker-shop/b2b-demo-shop) and [B2C Demo Shop repository](https://github.com/spryker-shop/b2c-demo-shop).
-
-For more information about our release process, see: [Spryker Release Process](/docs/scos/user/intro-to-spryker/spryker-release-process.html).
-
-To receive release notes email, subscribe here:
-
-<div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="b4d730db-d20e-4bb4-bd80-4cd7c9a2dc21" id="hubspot-1"></div>
diff --git a/docs/about/all/releases/release-notes/release-notes-202302.0/security-release-notes-202302.0.md b/docs/about/all/releases/security-release-notes-202302.0.md
similarity index 100%
rename from docs/about/all/releases/release-notes/release-notes-202302.0/security-release-notes-202302.0.md
rename to docs/about/all/releases/security-release-notes-202302.0.md
diff --git a/docs/about/all/releases/release-notes/release-notes-202304.0/security-release-notes-202304.0.md b/docs/about/all/releases/security-release-notes-202304.0.md
similarity index 100%
rename from docs/about/all/releases/release-notes/release-notes-202304.0/security-release-notes-202304.0.md
rename to docs/about/all/releases/security-release-notes-202304.0.md
diff --git a/docs/about/all/releases/release-notes/security-release-notes-202306.0.md b/docs/about/all/releases/security-release-notes-202306.0.md
similarity index 100%
rename from docs/about/all/releases/release-notes/security-release-notes-202306.0.md
rename to docs/about/all/releases/security-release-notes-202306.0.md
diff --git a/docs/about/all/releases/release-notes/security-release-notes-202309.0.md b/docs/about/all/releases/security-release-notes-202309.0.md
similarity index 100%
rename from docs/about/all/releases/release-notes/security-release-notes-202309.0.md
rename to docs/about/all/releases/security-release-notes-202309.0.md
diff --git a/docs/about/all/releases/release-notes/security-release-notes-202312.0.md b/docs/about/all/releases/security-release-notes-202312.0.md
similarity index 100%
rename from docs/about/all/releases/release-notes/security-release-notes-202312.0.md
rename to docs/about/all/releases/security-release-notes-202312.0.md
diff --git a/docs/about/all/support/contacting-spryker-support.md b/docs/about/all/support/contacting-spryker-support.md
deleted file mode 100644
index 1a40a7fe3d7..00000000000
--- a/docs/about/all/support/contacting-spryker-support.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Contacting Spryker Support
-last_updated: Jun 16, 2021
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/how-to-contact-spryker-support
-originalArticleId: f9c8d398-7305-4a0c-9dbd-b88d5ce7f988
-redirect_from:
-- /docs/scos/user/intro-to-spryker/support/how-to-contact-spryker-support.html
-related:
-  - title: How Spryker Support works
-    link: docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html
-  - title: Getting the most out of Spryker Support
-    link: docs/scos/user/intro-to-spryker/support/getting-the-most-out-of-spryker-support.html
-  - title: How to use the Support Portal
-    link: docs/scos/user/intro-to-spryker/support/how-to-use-the-support-portal.html
----
-
-<!--
-![image.png](https://cdn.document360.io/9fafa0d5-d76f-40c5-8b02-ab9515d3e879/Images/Documentation/image%28132%29.png)
-
-*Photo by [@snapwire](https://www.pexels.com/@snapwire)*
-
--->
-To contact Spryker Support, use [Spryker Support Portal](https://support.spryker.com).
-
-Opening a case using this form is the preferred way, as the form helps you include information we need to get working on a case immediately and speed up our case resolution time.
-
-If your case is not an emergency, take the time to learn [How Spryker Support works](/docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html) and [Getting the most out of Spryker Support](/docs/scos/user/intro-to-spryker/support/getting-the-most-out-of-spryker-support.html). Both documents give valuable insights into the inner workings of Spryker Support and let you help us to provide an excellent support experience for you.
diff --git a/docs/about/all/support/getting-support.md b/docs/about/all/support/getting-support.md
index 3ab20cccd00..2f8e70155e3 100644
--- a/docs/about/all/support/getting-support.md
+++ b/docs/about/all/support/getting-support.md
@@ -7,6 +7,8 @@ originalArticleId: db44af78-45b9-497b-a5b7-2474f1d1460b
 redirect_from:
   - /docs/scos/user/intro-to-spryker/support/getting-support.html
   - /docs/scos/user/intro-to-spryker/support/handling-new-feature-requests.html
+  - /docs/scos/user/intro-to-spryker/support/how-to-contact-spryker-support.html
+
 related:
   - title: How to use the Support Portal
     link: docs/scos/user/intro-to-spryker/support/how-to-use-the-support-portal.html
@@ -17,9 +19,10 @@ related:
 
 ---
 
-If you need technical help for issues that can't be resolved with our documentation, you can always count on our support team.
+If you need technical help for issues that can't be resolved with the help of the docs, you can always count on our support team. If your case is not an emergency, take the time to learn [How Spryker Support works](/docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html) and [how to get the most out of Spryker Support](/docs/scos/user/intro-to-spryker/support/getting-the-most-out-of-spryker-support.html). Both documents give valuable insights into the inner workings of Spryker Support and let you help us to provide an excellent support experience for you.
+
 
 Depending on the types of issues, there are several ways to report them and request support from us:
 * For bug reports and product issues, feel free to create a case for our support team at the [support portal](https://support.spryker.com).
 * For security-related issues, follow the instructions at [Security Support](/docs/scos/user/intro-to-spryker/support/handling-security-issues.html).
-* For general discussions of Spryker-related questions, join our Spryker community forum at [CommerceQuest](https://commercequest.space/).
+* For general discussions of Spryker-related questions, join the Spryker community at [CommerceQuest](https://commercequest.space/).
diff --git a/docs/ca/dev/preparation-for-going-live.md b/docs/ca/dev/preparation-for-going-live.md
index 15494a9d70a..ffbd7059c5e 100644
--- a/docs/ca/dev/preparation-for-going-live.md
+++ b/docs/ca/dev/preparation-for-going-live.md
@@ -71,7 +71,7 @@ After pointing the domain name to your Spryker project, some of your customers m
   - Minimize the use of personal credentials and choose work-specific accounts based on each environment (production, staging, testing). We highly recommend employing Centralized Credential Management to securely store and manage these credentials.
   - Install all the [security updates](/docs/scos/user/intro-to-spryker/whats-new/security-updates.html) from all Spryker packages.
   - Install all the security updates from all the external packages. To check if your project modules require security updates, you can use the [Security checker](/docs/scos/dev/guidelines/keeping-a-project-upgradable/upgradability-guidelines/spryker-security-checker.html).
-- Perform compliance and legal checks. To ensure the platform complies with relevant legal and regulatory requirements, especially for international operations, consult your legal team. Make sure to check [Guidelines for new GDPR rules](/docs/scos/user/intro-to-spryker/support/guidelines-for-new-gdpr-rules.html).
+- Perform compliance and legal checks. To ensure the platform complies with relevant legal and regulatory requirements, especially for international operations, consult your legal team. Make sure to check [Guidelines for GDPR compliance](/docs/scos/user/intro-to-spryker/support/guidelines-for-new-gdpr-rules.html).
 - Make sure that the Back Office Access Control List (ACL) setup is configured correctly to manage user permissions and access rights within the system's administrative interface. For instructions on how to configure ACL, see [Users and rights overview](/docs/pbc/all/user-management/{{site.version}}/base-shop/user-and-rights-overview.html).
 
 ### Testing

From 24105c0a1c6f2b6bb99348d2c027f0395da8095a Mon Sep 17 00:00:00 2001
From: Andrii Tserkovnyi <andrii.tserkovnyi@spryker.com>
Date: Fri, 8 Mar 2024 12:21:04 +0200
Subject: [PATCH 07/26] sidebar

---
 _data/sidebars/about_all_sidebar.yml        | 70 +++++++++------------
 _scripts/sidebar_checker/sidebar_checker.sh |  4 +-
 2 files changed, 33 insertions(+), 41 deletions(-)

diff --git a/_data/sidebars/about_all_sidebar.yml b/_data/sidebars/about_all_sidebar.yml
index 516a53c1be3..731be5e2e00 100644
--- a/_data/sidebars/about_all_sidebar.yml
+++ b/_data/sidebars/about_all_sidebar.yml
@@ -2,46 +2,36 @@ title: About Spryker
 entries:
   - product: About Spryker
     nested:
-      - title:
-  - title: Intro to Spryker
-    url: /docs/scos/user/intro-to-spryker/intro-to-spryker.html
-    nested:
+    - title: About Spryker
+      url: /docs/about/all/about-spryker.html
     - title: Releases
       url: /docs/scos/user/intro-to-spryker/releases/product-and-code-releases.html
       nested:
-      - title: Release notes
-        url: /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes.html
+      - title: Security release notes 202312.0
+        url: /docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202312.0.html
+      - title: Release notes 202311.0
+        url: /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202311.0.html
+      - title: Security release notes 202309.0
+        url: /docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202309.0.html
+      - title: Release notes 202307.0
+        url: /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202307.0.html
         nested:
-        - title: Security release notes 202312.0
-          url: /docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202312.0.html
-        - title: Release notes 202311.0
-          url: /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202311.0/release-notes-202311.0.html
-        - title: Security release notes 202309.0
-          url: /docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202309.0.html
-        - title: Release notes 202307.0
-          url: /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202307.0/release-notes-202307.0.html
-          nested:
         - title: Security release notes 202307.0
           url: /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202307.0/security-release-notes-202307.0.html
-        - title: Security release notes 202306.0
-          url: /docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202306.0.html
-        - title: Release notes 202304.0
-          nested:
-          - title: Security release notes 202304.0
-            url: /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202304.0/security-release-notes-202304.0.html
-        - title: Release notes 202302.0
-          nested:
-          - title: Security release notes 202302.0
-            url: /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202302.0/security-release-notes-202302.0.html
-        - title: Release notes 202212.0
-          url: /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/release-notes-202212.0.html
-          nested:
-          - title: Patch releases 202212.0
-            url: /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.html
-          - title: Security release notes 202212.0
-            url: /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/security-release-notes-202212.0.html
-    - title: Docs updates
-      url: /docs/scos/user/intro-to-spryker/docs-release-notes.html
+      - title: Security release notes 202306.0
+        url: /docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202306.0.html
+      - title: Security release notes 202304.0
+        url: /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202304.0/security-release-notes-202304.0.html
+      - title: Security release notes 202302.0
+        url: /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202302.0/security-release-notes-202302.0.html
+      - title: Release notes 202212.0
+        url: /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/release-notes-202212.0.html
+        nested:
+        - title: Patch releases 202212.0
+          url: /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.html
+        - title: Security release notes 202212.0
+          url: /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/security-release-notes-202212.0.html
+
     - title: Security audit reports
       nested:
       - title: 2019.11 - Security audit by SektionEins
@@ -49,15 +39,17 @@ entries:
       - title: 2020.11 - Penetration test by Port Zero (executive summary)
         url: /docs/scos/user/intro-to-spryker/whats-new/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.html
 
+    - title: Docs updates
+      url: /docs/scos/user/intro-to-spryker/docs-release-notes.html
+
     - title: Support
+      url: /docs/scos/user/intro-to-spryker/support/getting-support.html
       nested:
       - title: How Spryker Support works
         url: /docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html
-      - title: Case escalation
+      - title: Support case escalation
         url: /docs/scos/user/intro-to-spryker/support/case-escalation.html
-      - title: Getting support
-        url: /docs/scos/user/intro-to-spryker/support/getting-support.html
-      - title: Special- Prepare for a busy season
+      - title: Preparing for heavy loads and traffic
         url: /docs/scos/user/intro-to-spryker/support/special-prepare-for-a-busy-season.html
       - title: How to use the Support Portal
         url: /docs/scos/user/intro-to-spryker/support/how-to-use-the-support-portal.html
@@ -67,7 +59,7 @@ entries:
         url: /docs/scos/user/intro-to-spryker/support/understanding-ticket-status.html
       - title: Handling security issues
         url: /docs/scos/user/intro-to-spryker/support/handling-security-issues.html
-      - title: Guidelines for new GDPR rules
+      - title: Guidelines for GDPR compliance
         url: /docs/scos/user/intro-to-spryker/support/guidelines-for-new-gdpr-rules.html
       - title: Getting the most out of Spryker Support
         url: /docs/scos/user/intro-to-spryker/support/getting-the-most-out-of-spryker-support.html
diff --git a/_scripts/sidebar_checker/sidebar_checker.sh b/_scripts/sidebar_checker/sidebar_checker.sh
index 4726320fbc9..07e956593b4 100644
--- a/_scripts/sidebar_checker/sidebar_checker.sh
+++ b/_scripts/sidebar_checker/sidebar_checker.sh
@@ -1,10 +1,10 @@
 #!/bin/bash
 
 # Define doc folder paths
-FOLDERS=("docs/acp/user" "docs/ca/dev" "docs/pbc/all" "docs/scos/dev" "docs/scos/user" "docs/scu/dev" "docs/sdk/dev")
+FOLDERS=("docs/ca/dev" "docs/pbc/all" "docs/about/all" "docs/ca/devscu" "docs/dg/dev")
 
 # Define sidebar file paths
-SIDEBARS=("_data/sidebars/acp_user_sidebar.yml" "_data/sidebars/ca_dev_sidebar.yml" "_data/sidebars/pbc_all_sidebar.yml" "_data/sidebars/scos_dev_sidebar.yml" "_data/sidebars/scos_user_sidebar.yml" "_data/sidebars/scu_dev_sidebar.yml" "_data/sidebars/sdk_dev_sidebar.yml")
+SIDEBARS=("_data/sidebars/ca_dev_sidebar.yml" "_data/sidebars/ca_devscu_sidebar.yml" "_data/sidebars/pbc_all_sidebar.yml" "_data/sidebars/dg_dev_sidebar.yml" "_data/sidebars/about_all_sidebar.yml")
 
 # Define sidebar titles
 TITLES=("ACP User" "Cloud Dev" "PBC All" "SCOS Dev" "SCOS User" "SCU Dev" "SDK Dev")

From 4b2e1e8de6db7323e0f37e31e1b4023d9e0c0592 Mon Sep 17 00:00:00 2001
From: Andrii Tserkovnyi <andrii.tserkovnyi@spryker.com>
Date: Tue, 12 Mar 2024 15:20:03 +0200
Subject: [PATCH 08/26] merge master

---
 .github/workflows/ci.yml                      | 28 +++++++++++++++++++
 .../patch-release-notes-202212.0.md           |  2 +-
 2 files changed, 29 insertions(+), 1 deletion(-)

diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 047b04d40bd..fc84f24cb18 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -33,6 +33,34 @@ jobs:
           name: build-result
           path: result.tar.gz
 
+  link_validation_check_about:
+    name: Links validation (check_about)
+    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_about_all-htmlproofer
+
+      - uses: actions/download-artifact@v2
+
+      - name: Unpack artifacts
+        run: tar -xf build-result/result.tar.gz
+
+      - run: bundle exec rake check_about          
+
   link_validation_check_ca:
     name: Links validation (check_ca)
     needs: jekyll_build
diff --git a/docs/about/all/releases/release-notes-202212.0/patch-release-notes-202212.0.md b/docs/about/all/releases/release-notes-202212.0/patch-release-notes-202212.0.md
index 4d00d38671c..407e2f31fb6 100644
--- a/docs/about/all/releases/release-notes-202212.0/patch-release-notes-202212.0.md
+++ b/docs/about/all/releases/release-notes-202212.0/patch-release-notes-202212.0.md
@@ -9,4 +9,4 @@ redirect_from:
 
 ---
 
-{% include scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.md %} <!-- To edit, see /_includes/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.md-->
+{% include scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/patch-release-notes-202212.0.md %} <!-- To edit, see /_includes/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/patch-release-notes-202212.0.md-->

From 313cdeee0efdf347cfa361f1e0b125bc49b8af4f Mon Sep 17 00:00:00 2001
From: Andrii Tserkovnyi <andrii.tserkovnyi@spryker.com>
Date: Tue, 12 Mar 2024 15:35:30 +0200
Subject: [PATCH 09/26] links

---
 Rakefile              | 2 +-
 _includes/topnav.html | 2 +-
 _layouts/home.html    | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/Rakefile b/Rakefile
index 43f65842d23..fd0f01c1f18 100644
--- a/Rakefile
+++ b/Rakefile
@@ -93,7 +93,7 @@ task :check_ca do
   HTMLProofer.check_directory("./_site", options).run
 end
 
-task :check_about_all do
+task :check_about do
   options = commonOptions.dup
   options[:ignore_files] = [
     /docs\/ca\/.+/,
diff --git a/_includes/topnav.html b/_includes/topnav.html
index fab5c50c64c..1fc1dcfb83f 100644
--- a/_includes/topnav.html
+++ b/_includes/topnav.html
@@ -57,7 +57,7 @@
                                               </a>
                                           </li>
                                           <li>
-                                              <a href="/docs/about/all/intro-to-spryker.html" class="main-nav__drop-link">
+                                              <a href="/docs/about/all/about-spryker.html" class="main-nav__drop-link">
                                               About Spryker
                                               </a>
                                           </li>
diff --git a/_layouts/home.html b/_layouts/home.html
index e9f8930555e..c59f6df221f 100644
--- a/_layouts/home.html
+++ b/_layouts/home.html
@@ -45,7 +45,7 @@ <h2 class="card__heading-title">Business User guides</h2>
                     </div>
                     <div class="card__footer">
                         <ul class="card__links">
-                            <li><a href="/docs/about/all/intro-to-spryker.html">About Spryker</a></li>
+                            <li><a href="/docs/about/all/about-spryker.html">About Spryker</a></li>
                         </ul>
                     </div>
                 </div>

From 2ddc0e7694c0a47472223a8855f76fa6f4a94e8c Mon Sep 17 00:00:00 2001
From: Andrii Tserkovnyi <andrii.tserkovnyi@spryker.com>
Date: Tue, 12 Mar 2024 15:50:44 +0200
Subject: [PATCH 10/26] links

---
 README.md                                     |   2 +-
 _data/sidebars/about_all_sidebar.yml          | 110 +++++++++---------
 _data/sidebars/dg_dev_sidebar.yml             |   2 -
 .../features.md                               |   2 +-
 ...g-spryker-with-devvm-on-macos-and-linux.md |   2 +-
 ...nstalling-spryker-with-devvm-on-windows.md |   2 +-
 .../installing-spryker-without-docker.md      |   2 +-
 .../contributing-to-documentation.md          |   2 +-
 docs/about/all/about-spryker.md               |   6 +-
 .../add-global-sections-to-the-docs.md        |  14 +--
 .../add-and-edit-diagrams-in-the-docs.md      |   8 +-
 .../contribute-to-the-docs.md                 |  20 ++--
 .../edit-the-docs-locally.md                  |   2 +-
 .../edit-the-docs-using-a-web-browser.md      |  16 +--
 .../report-docs-issues.md                     |  12 +-
 .../review-pull-requests.md                   |  12 +-
 .../install-recommended-vs-code-extensions.md |  12 +-
 .../about-the-docs/run-the-docs-locally.md    |  12 +-
 ...eral-rules-and-guidance-for-adding-docs.md |  14 +--
 .../style-guide/markdown-syntax.md            |  12 +-
 docs/about/all/b2b-suite.md                   |   2 +-
 docs/about/all/b2c-suite.md                   |   2 +-
 docs/about/all/docs-updates.md                |  32 ++---
 .../all/releases/product-and-code-releases.md |   2 +-
 .../all/releases/release-notes-202211.0.md    |   2 +-
 .../security-release-notes-202302.0.md        |   2 +-
 .../2019.11-security-audit-by-sektioneins.md  |   2 +-
 .../back-office-for-marketplace-operator.md   |   8 +-
 .../marketplace-concept.md                    |   2 +-
 .../marketplace-personas.md                   |   2 +-
 .../marketplace-storefront.md                 |   4 +-
 .../merchant-onboarding.md                    |   8 +-
 .../spryker-marketplace.md                    |  16 +--
 docs/about/all/support/getting-support.md     |  10 +-
 ...getting-the-most-out-of-spryker-support.md |   8 +-
 .../all/support/how-spryker-support-works.md  |   4 +-
 .../all/support/prioritzing-support-cases.md  |   2 +-
 ...e-secrets-with-the-spryker-support-team.md |   2 +-
 .../all/support/support-case-escalations.md   |   2 +-
 docs/about/all/support/understanding-slas.md  |   6 +-
 .../all/support/using-the-support-portal.md   |   8 +-
 docs/about/all/supported-browsers.md          |   2 +-
 .../email-service/email-quota-restrictions.md |   2 +-
 docs/ca/dev/environment-provisioning.md       |   2 +-
 ...ormance-testing-in-staging-enivronments.md |   4 +-
 docs/ca/dev/preparation-for-going-live.md     |   6 +-
 .../integrating-code-releases.md              |   2 +-
 ...are-a-project-for-spryker-code-upgrader.md |   2 +-
 docs/dg/dev/acp/acp-overview.md               |   2 +-
 .../app-composition-platform-installation.md  |  10 +-
 ...oning-major-vs.-minor-vs.-patch-release.md |   2 +-
 .../backend-development/cronjobs/cronjobs.md  |   2 +-
 docs/dg/dev/code-contribution-guide.md        |   2 +-
 .../data-import-optimization-guidelines.md    |   2 +-
 .../data-import-optimization-guidelines.md    |   2 +-
 .../data-import-optimization-guidelines.md    |   2 +-
 .../dev/development-getting-started-guide.md  |  10 +-
 ...zation-example-b2b-product-details-page.md |   2 +-
 ...zation-example-b2c-product-details-page.md |   2 +-
 ...zation-example-b2b-product-details-page.md |   2 +-
 ...zation-example-b2c-product-details-page.md |   2 +-
 ...zation-example-b2b-product-details-page.md |   2 +-
 ...zation-example-b2c-product-details-page.md |   2 +-
 .../configure-the-included-section.md         |   2 +-
 .../extend-a-rest-api-resource.md             |   2 +-
 .../old-glue-infrastructure/glue-rest-api.md  |   2 +-
 .../configure-the-included-section.md         |   2 +-
 .../extend-a-rest-api-resource.md             |   2 +-
 .../old-glue-infrastructure/glue-rest-api.md  |   2 +-
 .../configure-the-included-section.md         |   2 +-
 .../extend-a-rest-api-resource.md             |   2 +-
 .../old-glue-infrastructure/glue-rest-api.md  |   2 +-
 .../configure-services.md                     |   4 +-
 docs/dg/dev/master-suite.md                   |   2 +-
 .../install/choose-an-installation-mode.md    |   2 +-
 .../install-in-demo-mode-on-windows.md        |   2 +-
 .../install-in-development-mode-on-windows.md |   2 +-
 .../202212.0/system-requirements.md           |   4 +-
 .../202307.0/system-requirements.md           |   4 +-
 .../202311.0/system-requirements.md           |   4 +-
 .../troubleshooting-performance-issues.md     |   2 +-
 .../dg/dev/troubleshooting/troubleshooting.md |   6 +-
 ...-upgrading-projects-with-spryker-jarvis.md |   2 +-
 .../feature-or-module-updates.md              |   2 +-
 ...nstalling-features-and-updating-modules.md |   2 +-
 .../dev/updating-spryker/updating-spryker.md  |  14 +--
 .../multiple-carts-feature-overview.md        |   2 +-
 ...ble-guest-checkout-in-the-b2b-demo-shop.md |   2 +-
 .../multiple-carts-feature-overview.md        |   2 +-
 ...ble-guest-checkout-in-the-b2b-demo-shop.md |   2 +-
 .../multiple-carts-feature-overview.md        |   2 +-
 ...ble-guest-checkout-in-the-b2b-demo-shop.md |   2 +-
 .../email-as-a-cms-block-overview.md          |   2 +-
 ...refront-pages-using-templates-and-slots.md |   2 +-
 .../email-as-a-cms-block-overview.md          |   2 +-
 ...refront-pages-using-templates-and-slots.md |   2 +-
 .../email-as-a-cms-block-overview.md          |   2 +-
 ...refront-pages-using-templates-and-slots.md |   2 +-
 .../main-merchant.md                          |   4 +-
 .../main-merchant.md                          |   4 +-
 .../main-merchant.md                          |   4 +-
 ...merchant-custom-prices-feature-overview.md |   2 +-
 ...merchant-custom-prices-feature-overview.md |   2 +-
 ...merchant-custom-prices-feature-overview.md |   2 +-
 .../category-management-feature-overview.md   |   2 +-
 ...oduct-approval-process-feature-overview.md |   2 +-
 .../category-management-feature-overview.md   |   2 +-
 ...oduct-approval-process-feature-overview.md |   2 +-
 .../category-management-feature-overview.md   |   2 +-
 .../split-products-by-stores.md               |   2 +-
 ...oduct-approval-process-feature-overview.md |   2 +-
 .../category-management-feature-overview.md   |   2 +-
 .../standard-filters-overview.md              |   2 +-
 .../standard-filters-overview.md              |   2 +-
 .../standard-filters-overview.md              |   2 +-
 .../glue-api-search-the-product-catalog.md    |   2 +-
 ...-multi-store-environment-best-practices.md |   2 +-
 .../marketplace/manage-availability.md        |   4 +-
 ...-multi-store-environment-best-practices.md |   2 +-
 .../marketplace/manage-availability.md        |   4 +-
 ...-multi-store-environment-best-practices.md |   2 +-
 .../marketplace/manage-availability.md        |   4 +-
 122 files changed, 304 insertions(+), 306 deletions(-)

diff --git a/README.md b/README.md
index 651c6155417..e4cc9af9bdd 100644
--- a/README.md
+++ b/README.md
@@ -13,7 +13,7 @@ To build the documentation site with Docker, run this command:
 
 ## Contribute
 
-For the specific Markdown syntax we use in documentation, see [Markdown syntax](/docs/scos/user/intro-to-spryker/contributing-to-documentation/markdown-syntax.html). For the general style, syntax, and formatting rules, see [Style, syntax, formatting, and general rules](/docs/scos/user/intro-to-spryker/contributing-to-documentation/style-formatting-general-rules.html).
+For the specific Markdown syntax we use in documentation, see [Markdown syntax](/docs/about/all/contributing-to-documentation/markdown-syntax.html). For the general style, syntax, and formatting rules, see [Style, syntax, formatting, and general rules](/docs/about/all/contributing-to-documentation/style-formatting-general-rules.html).
 
 To suggest changes, follow the steps:
 
diff --git a/_data/sidebars/about_all_sidebar.yml b/_data/sidebars/about_all_sidebar.yml
index 731be5e2e00..aa728c30d42 100644
--- a/_data/sidebars/about_all_sidebar.yml
+++ b/_data/sidebars/about_all_sidebar.yml
@@ -5,130 +5,130 @@ entries:
     - title: About Spryker
       url: /docs/about/all/about-spryker.html
     - title: Releases
-      url: /docs/scos/user/intro-to-spryker/releases/product-and-code-releases.html
+      url: /docs/about/all/releases/product-and-code-releases.html
       nested:
       - title: Security release notes 202312.0
-        url: /docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202312.0.html
+        url: /docs/about/all/releases/release-notes/security-release-notes-202312.0.html
       - title: Release notes 202311.0
-        url: /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202311.0.html
+        url: /docs/about/all/releases/release-notes/release-notes-202311.0.html
       - title: Security release notes 202309.0
-        url: /docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202309.0.html
+        url: /docs/about/all/releases/release-notes/security-release-notes-202309.0.html
       - title: Release notes 202307.0
-        url: /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202307.0.html
+        url: /docs/about/all/releases/release-notes/release-notes-202307.0.html
         nested:
         - title: Security release notes 202307.0
-          url: /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202307.0/security-release-notes-202307.0.html
+          url: /docs/about/all/releases/release-notes/release-notes-202307.0/security-release-notes-202307.0.html
       - title: Security release notes 202306.0
-        url: /docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202306.0.html
+        url: /docs/about/all/releases/release-notes/security-release-notes-202306.0.html
       - title: Security release notes 202304.0
-        url: /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202304.0/security-release-notes-202304.0.html
+        url: /docs/about/all/releases/release-notes/release-notes-202304.0/security-release-notes-202304.0.html
       - title: Security release notes 202302.0
-        url: /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202302.0/security-release-notes-202302.0.html
+        url: /docs/about/all/releases/release-notes/release-notes-202302.0/security-release-notes-202302.0.html
       - title: Release notes 202212.0
-        url: /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/release-notes-202212.0.html
+        url: /docs/about/all/releases/release-notes/release-notes-202212.0/release-notes-202212.0.html
         nested:
         - title: Patch releases 202212.0
-          url: /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.html
+          url: /docs/about/all/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.html
         - title: Security release notes 202212.0
-          url: /docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/security-release-notes-202212.0.html
+          url: /docs/about/all/releases/release-notes/release-notes-202212.0/security-release-notes-202212.0.html
 
     - title: Security audit reports
       nested:
       - title: 2019.11 - Security audit by SektionEins
-        url: /docs/scos/user/intro-to-spryker/whats-new/security-audit-reports/2019.11-security-audit-by-sektioneins.html
+        url: /docs/about/all/whats-new/security-audit-reports/2019.11-security-audit-by-sektioneins.html
       - title: 2020.11 - Penetration test by Port Zero (executive summary)
-        url: /docs/scos/user/intro-to-spryker/whats-new/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.html
+        url: /docs/about/all/whats-new/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.html
 
     - title: Docs updates
-      url: /docs/scos/user/intro-to-spryker/docs-release-notes.html
+      url: /docs/about/all/docs-release-notes.html
 
     - title: Support
-      url: /docs/scos/user/intro-to-spryker/support/getting-support.html
+      url: /docs/about/all/support/getting-support.html
       nested:
       - title: How Spryker Support works
-        url: /docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html
+        url: /docs/about/all/support/how-spryker-support-works.html
       - title: Support case escalation
-        url: /docs/scos/user/intro-to-spryker/support/case-escalation.html
+        url: /docs/about/all/support/case-escalation.html
       - title: Preparing for heavy loads and traffic
-        url: /docs/scos/user/intro-to-spryker/support/special-prepare-for-a-busy-season.html
+        url: /docs/about/all/support/special-prepare-for-a-busy-season.html
       - title: How to use the Support Portal
-        url: /docs/scos/user/intro-to-spryker/support/how-to-use-the-support-portal.html
+        url: /docs/about/all/support/how-to-use-the-support-portal.html
       - title: Share secrets with the Spryker Support Team
-        url: /docs/scos/user/intro-to-spryker/support/share-secrets-with-the-spryker-support-team.html
+        url: /docs/about/all/support/share-secrets-with-the-spryker-support-team.html
       - title: Understanding ticket status
-        url: /docs/scos/user/intro-to-spryker/support/understanding-ticket-status.html
+        url: /docs/about/all/support/understanding-ticket-status.html
       - title: Handling security issues
-        url: /docs/scos/user/intro-to-spryker/support/handling-security-issues.html
+        url: /docs/about/all/support/handling-security-issues.html
       - title: Guidelines for GDPR compliance
-        url: /docs/scos/user/intro-to-spryker/support/guidelines-for-new-gdpr-rules.html
+        url: /docs/about/all/support/guidelines-for-new-gdpr-rules.html
       - title: Getting the most out of Spryker Support
-        url: /docs/scos/user/intro-to-spryker/support/getting-the-most-out-of-spryker-support.html
+        url: /docs/about/all/support/getting-the-most-out-of-spryker-support.html
       - title: Understand SLAs
-        url: /docs/scos/user/intro-to-spryker/support/understand-slas.html
+        url: /docs/about/all/support/understand-slas.html
       - title: Escalations
-        url: /docs/scos/user/intro-to-spryker/support/escalations.html
+        url: /docs/about/all/support/escalations.html
       - title: How to contact Spryker Support
-        url: /docs/scos/user/intro-to-spryker/support/how-to-contact-spryker-support.html
+        url: /docs/about/all/support/how-to-contact-spryker-support.html
       - title: Understanding Project and Core Level Fixes
-        url: /docs/scos/user/intro-to-spryker/support/understanding-project-and-core-level-fixes.html
+        url: /docs/about/all/support/understanding-project-and-core-level-fixes.html
 
     - title: Supported browsers
-      url: /docs/scos/user/intro-to-spryker/supported-browsers.html
+      url: /docs/about/all/supported-browsers.html
     - title: Spryker Marketplace
-      url: /docs/scos/user/intro-to-spryker/spryker-marketplace/spryker-marketplace.html
+      url: /docs/about/all/spryker-marketplace/spryker-marketplace.html
       nested:
       - title: Marketplace concept
-        url: /docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-concept.html
+        url: /docs/about/all/spryker-marketplace/marketplace-concept.html
       - title: Marketplace personas
-        url: /docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-personas.html
+        url: /docs/about/all/spryker-marketplace/marketplace-personas.html
       - title: Back Office for Marketplace Operator
-        url: /docs/scos/user/intro-to-spryker/spryker-marketplace/back-office-for-marketplace-operator.html
+        url: /docs/about/all/spryker-marketplace/back-office-for-marketplace-operator.html
       - title: Merchant onboarding
-        url: /docs/scos/user/intro-to-spryker/spryker-marketplace/merchant-onboarding.html
+        url: /docs/about/all/spryker-marketplace/merchant-onboarding.html
       - title: Marketplace Storefront
-        url: /docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-storefront.html
+        url: /docs/about/all/spryker-marketplace/marketplace-storefront.html
       - title: Merchant Portal
-        url: /docs/scos/user/intro-to-spryker/spryker-marketplace/merchant-portal.html
+        url: /docs/about/all/spryker-marketplace/merchant-portal.html
       - title: Marketplace B2C Suite
-        url: /docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2c-suite.html
+        url: /docs/about/all/spryker-marketplace/marketplace-b2c-suite.html
       - title: Marketplace B2B Suite
-        url: /docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2b-suite.html
+        url: /docs/about/all/spryker-marketplace/marketplace-b2b-suite.html
 
     - title: Spryker Academy
-      url: /docs/scos/user/intro-to-spryker/spryker-academy.html
+      url: /docs/about/all/spryker-academy.html
     - title: Contribute to the documentation
-      url: /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/contribute-to-the-documentation.html
+      url: /docs/about/all/contribute-to-the-documentation/contribute-to-the-documentation.html
       nested:
       - title: Edit the documentation via pull requests
-        url: /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
+        url: /docs/about/all/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
       - title: Edit the documentation locally
-        url: /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/edit-the-documentation-locally.html
+        url: /docs/about/all/contribute-to-the-documentation/edit-the-documentation-locally.html
       - title: General rules and guidance for adding new documents
-        url: /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/general-rules-and-guidance-for-adding-new-documents.html
+        url: /docs/about/all/contribute-to-the-documentation/general-rules-and-guidance-for-adding-new-documents.html
       - title: Markdown syntax
-        url: /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/markdown-syntax.html
+        url: /docs/about/all/contribute-to-the-documentation/markdown-syntax.html
       - title: Spryker documentation style guide
-        url: /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/spryker-documentation-style-guide/spryker-documentation-style-guide.html
+        url: /docs/about/all/contribute-to-the-documentation/spryker-documentation-style-guide/spryker-documentation-style-guide.html
         nested:
           - title: Examples
-            url: /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/spryker-documentation-style-guide/examples.html
+            url: /docs/about/all/contribute-to-the-documentation/spryker-documentation-style-guide/examples.html
           - title: Spelling
-            url: /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/spryker-documentation-style-guide/spelling.html
+            url: /docs/about/all/contribute-to-the-documentation/spryker-documentation-style-guide/spelling.html
           - title: Word list
-            url: /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/spryker-documentation-style-guide/word-list.html
+            url: /docs/about/all/contribute-to-the-documentation/spryker-documentation-style-guide/word-list.html
 
       - title: Add and edit diagrams
-        url: /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/add-and-edit-diagrams-in-the-documentation.html
+        url: /docs/about/all/contribute-to-the-documentation/add-and-edit-diagrams-in-the-documentation.html
       - title: Install recommended VS Code extensions
-        url: /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/install-recommended-vs-code-extensions.html
+        url: /docs/about/all/contribute-to-the-documentation/install-recommended-vs-code-extensions.html
       - title: Report documentation issues
-        url: /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/report-documentation-issues.html
+        url: /docs/about/all/contribute-to-the-documentation/report-documentation-issues.html
       - title: Build the documentation site
-        url: /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/build-the-documentation-site.html
+        url: /docs/about/all/contribute-to-the-documentation/build-the-documentation-site.html
       - title: Review pull requests
-        url: /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/review-pull-requests.html
+        url: /docs/about/all/contribute-to-the-documentation/review-pull-requests.html
       - title: Add product sections to the documentation
-        url: /docs/scos/user/intro-to-spryker/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
+        url: /docs/about/all/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
 
 
 
diff --git a/_data/sidebars/dg_dev_sidebar.yml b/_data/sidebars/dg_dev_sidebar.yml
index 6e942b26117..e801a0a9da5 100644
--- a/_data/sidebars/dg_dev_sidebar.yml
+++ b/_data/sidebars/dg_dev_sidebar.yml
@@ -1517,8 +1517,6 @@ entries:
       - title: Troubleshooting updates
         url: /docs/dg/dev/updating-spryker/troubleshooting-updates.html
 
-  - title: Product and code releases
-    url: /docs/dg/dev/product-and-code-releases.html
   - title: Supported versions of PHP
     url: /docs/dg/dev/supported-versions-of-php.html
 
diff --git a/_drafts/deprecated-after-pbc-migration/features.md b/_drafts/deprecated-after-pbc-migration/features.md
index 99da53f22f5..8ea50cec7b6 100644
--- a/_drafts/deprecated-after-pbc-migration/features.md
+++ b/_drafts/deprecated-after-pbc-migration/features.md
@@ -21,7 +21,7 @@ The **Features** section is divided into capabilities. Each capability contains
 
 In the feature documentation, you can find the following information:
 
-* A short feature summary with guidelines designed for different [personas](/docs/scos/user/intro-to-spryker/about-spryker-documentation.html#personas).
+* A short feature summary with guidelines designed for different [personas](/docs/about/all/about-spryker-documentation.html#personas).
 * A detailed feature overview, workflows, database structure, and more.
 
 {% info_block infoBox "Reference documentation" %}
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 5532de83f05..d11042f971e 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
@@ -47,7 +47,7 @@ We will soon deprecate the DevVM and stop supporting it. Therefore, we highly re
 
 {% endinfo_block %}
 
-To install the [B2B Demo Shop](/docs/scos/user/intro-to-spryker/b2b-suite.html) or [B2C Demo Shop](/docs/scos/user/intro-to-spryker/b2c-suite.html) on MacOS or Linux with DevVM, follow the steps below.
+To install the [B2B Demo Shop](/docs/about/all/b2b-suite.html) or [B2C Demo Shop](/docs/about/all/b2c-suite.html) on MacOS or Linux with DevVM, follow the steps below.
 
 ## 1. Install prerequisites
 
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 77350ae3e7b..c0531543e18 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
@@ -35,7 +35,7 @@ We will soon deprecate the DevVM and stop supporting it. Therefore, we highly re
 
 {% endinfo_block %}
 
-To install the Demo Shop for [B2B](/docs/scos/user/intro-to-spryker/b2b-suite.html) or [B2C](/docs/scos/user/intro-to-spryker/b2c-suite.html) implementations on Windows with Spryker development virtual machine (DevVM), follow the steps below.
+To install the Demo Shop for [B2B](/docs/about/all/b2b-suite.html) or [B2C](/docs/about/all/b2c-suite.html) implementations on Windows with Spryker development virtual machine (DevVM), follow the steps below.
 
 ## 1. Install prerequisites
 
diff --git a/_drafts/deprecated-devvm/installing-spryker-without-docker.md b/_drafts/deprecated-devvm/installing-spryker-without-docker.md
index 18ce301692b..a89cc305d9d 100644
--- a/_drafts/deprecated-devvm/installing-spryker-without-docker.md
+++ b/_drafts/deprecated-devvm/installing-spryker-without-docker.md
@@ -30,7 +30,7 @@ related:
     link: docs/scos/dev/set-up-spryker-locally/redis-configuration.html
 ---
 
-To install [B2B Demo Shop](/docs/scos/user/intro-to-spryker/b2b-suite.html) or [B2C Demo Shop](/docs/scos/user/intro-to-spryker/b2c-suite.html) without Docker, follow the steps below.
+To install [B2B Demo Shop](/docs/about/all/b2b-suite.html) or [B2C Demo Shop](/docs/about/all/b2c-suite.html) without Docker, follow the steps below.
 
 ### Minimum requirements
 
diff --git a/_drafts/drafts-dev/contributing-to-documentation.md b/_drafts/drafts-dev/contributing-to-documentation.md
index e5f5170ac8b..8206c0203d1 100644
--- a/_drafts/drafts-dev/contributing-to-documentation.md
+++ b/_drafts/drafts-dev/contributing-to-documentation.md
@@ -13,7 +13,7 @@ To report issues and fix documentation, you need a [GitHub account](https://gith
 
 {% endinfo_block %}
 
-We use [Markdown](https://guides.github.com/features/mastering-markdown/) to write documentation and [Jekyll](https://jekyllrb.com/) to build the documentation site. You do not necessarily need to build the documentation site locally on your machine to propose your changes, but if you want to, follow the instructions in [Build documentation site](/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/build-the-documentation-site.html).
+We use [Markdown](https://guides.github.com/features/mastering-markdown/) to write documentation and [Jekyll](https://jekyllrb.com/) to build the documentation site. You do not necessarily need to build the documentation site locally on your machine to propose your changes, but if you want to, follow the instructions in [Build documentation site](/docs/about/all/contribute-to-the-documentation/build-the-documentation-site.html).
 
 ## Next steps
 Build the documentation site locally
diff --git a/docs/about/all/about-spryker.md b/docs/about/all/about-spryker.md
index c605a7e5279..e02363f6e12 100644
--- a/docs/about/all/about-spryker.md
+++ b/docs/about/all/about-spryker.md
@@ -71,11 +71,11 @@ SCOS is split into four different layers:
 
 ## Spryker B2B and B2C Demo Shops
 
-Our [B2B](/docs/scos/user/intro-to-spryker/b2b-suite.html) and [B2C Demo Shops](/docs/scos/user/intro-to-spryker/b2c-suite.html) showcase Spryker functionality and help you choose the best possible starting point and set of features based on your business needs. The Demo Shops pose a clear starting point and upgrade path for everything you base your project on. We ship our B2B/B2C Demo Shops as a part of the product, covered by the same commercial license and the same support and LTS (long-term support) rules as individual Spryker Commerce OS modules.
+Our [B2B](/docs/about/all/b2b-suite.html) and [B2C Demo Shops](/docs/about/all/b2c-suite.html) showcase Spryker functionality and help you choose the best possible starting point and set of features based on your business needs. The Demo Shops pose a clear starting point and upgrade path for everything you base your project on. We ship our B2B/B2C Demo Shops as a part of the product, covered by the same commercial license and the same support and LTS (long-term support) rules as individual Spryker Commerce OS modules.
 
 ## I am a new customer, where should I start?
 
-The recommended starting points for all standard commerce projects are our [B2B](/docs/scos/user/intro-to-spryker/b2b-suite.html#b2b-demo-shop) and [B2C Demo Shops](/docs/scos/user/intro-to-spryker/b2c-suite.html#b2c-demo-shop). We have taken the time to identify the best combination of modules and functionalities for each particular business type and to keep development as lean as possible. Thus, the only thing that remains is to identify your business requirements and select the shop that fits your needs best.
+The recommended starting points for all standard commerce projects are our [B2B](/docs/about/all/b2b-suite.html#b2b-demo-shop) and [B2C Demo Shops](/docs/about/all/b2c-suite.html#b2c-demo-shop). We have taken the time to identify the best combination of modules and functionalities for each particular business type and to keep development as lean as possible. Thus, the only thing that remains is to identify your business requirements and select the shop that fits your needs best.
 
 Apart from that, if your business case does not fit in one of the proposed models, you can start building your project by cherry-picking the modules you need. Since they are released under a commercial license with stable and predictable release cycles, you can build your e-commerce business with reliance and certainty. Our engineers make sure that each module is reliable, backward compatible, and fully regression-tested, and all our releases are supported with an LTS flag (12 months).
 
@@ -83,7 +83,7 @@ Apart from that, if your business case does not fit in one of the proposed model
 
 Select one of the topics below depending on what you want to do next:
 
-* [What's new](/docs/scos/user/intro-to-spryker/whats-new/whats-new.html): general information about Spryker, news, and release notes.
+* [What's new](/docs/about/all/whats-new/whats-new.html): general information about Spryker, news, and release notes.
 * [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.
diff --git a/docs/about/all/about-the-docs/add-global-sections-to-the-docs.md b/docs/about/all/about-the-docs/add-global-sections-to-the-docs.md
index eea15bdbb57..d78fd06f54b 100644
--- a/docs/about/all/about-the-docs/add-global-sections-to-the-docs.md
+++ b/docs/about/all/about-the-docs/add-global-sections-to-the-docs.md
@@ -11,17 +11,17 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/build-the-documentation-site.html
+    link: docs/about/all/contribute-to-the-documentation/build-the-documentation-site.html
   - title: Edit documentation via pull requests
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
+    link: docs/about/all/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
   - title: Report documentation issues
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/report-documentation-issues.html
+    link: docs/about/all/contribute-to-the-documentation/report-documentation-issues.html
   - title: Review pull requests
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/review-pull-requests.html
+    link: docs/about/all/contribute-to-the-documentation/review-pull-requests.html
   - title: Style, syntax, formatting, and general rules
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/style-formatting-general-rules.html
+    link: docs/about/all/contribute-to-the-documentation/style-formatting-general-rules.html
   - title: Markdown syntax
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/markdown-syntax.html
+    link: docs/about/all/contribute-to-the-documentation/markdown-syntax.html
 ---
 
 This document describes how to add global sections to the documentation, like the existing Development or Cloud administration sections.
@@ -38,7 +38,7 @@ In the `/docs` directory, create a folder for the section per role. In this exam
 
 In `_data/sidebars`, create sidebars for the new section per role: `{product_name}_{role}_sidebar.yml`. For the *acp* section with user and developer roles, create `acp_dev_sidebar.yml` and `acp_user_sidebar.yml` sidebar files.
 
-To learn how to populate sidebar files, see [Sidebars](/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/general-rules-and-guidance-for-adding-new-documents.html#sidebars).
+To learn how to populate sidebar files, see [Sidebars](/docs/about/all/contribute-to-the-documentation/general-rules-and-guidance-for-adding-new-documents.html#sidebars).
 
 ## 3. Update the configuration
 
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/add-and-edit-diagrams-in-the-docs.md b/docs/about/all/about-the-docs/contribute-to-the-docs/add-and-edit-diagrams-in-the-docs.md
index 8702514796b..ec5510fa20e 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/add-and-edit-diagrams-in-the-docs.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/add-and-edit-diagrams-in-the-docs.md
@@ -8,9 +8,9 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/build-the-documentation-site.html
+    link: docs/about/all/contribute-to-the-documentation/build-the-documentation-site.html
   - title: Edit documentation via pull requests
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
+    link: docs/about/all/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
 ---
 
 We are using [diagrams.net](https://www.diagrams.net/) to create and collaborate on diagrams. diagrams.net provides both a web and desktop applications. To download the latest desktop version, go to [diagrams.net](https://www.diagrams.net/) and click **Download**. Alternatively, you can work on diagrams in a [web app](https://app.diagrams.net/). You can store diagrams in any suitable source.
@@ -24,7 +24,7 @@ After creating a diagram, to embed it into a document, do the following:
     This generates code for embedding the diagram.
 3. To copy the code, click **Copy**.
 4. Open the document you want to add the diagram to in an editor.
-    For instructions about editing the documentation, see [Edit documentation via pull requests](/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/edit-documentation-via-pull-requests.html).
+    For instructions about editing the documentation, see [Edit documentation via pull requests](/docs/about/all/contribute-to-the-documentation/edit-documentation-via-pull-requests.html).
 5. Paste the code into the needed place of a document and submit a PR.
     After the PR is merged, the diagram appears on the page.
 
@@ -40,7 +40,7 @@ After creating a diagram, to embed it into a document, do the following:
     This generates code for embedding the diagram.
 6. To copy the code, click **Copy**.
 7. Open the document containing the original diagram in an editor.
-        For instructions about editing the documentation, see [Edit documentation via pull requests](/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/edit-documentation-via-pull-requests.html).
+        For instructions about editing the documentation, see [Edit documentation via pull requests](/docs/about/all/contribute-to-the-documentation/edit-documentation-via-pull-requests.html).
 8. Replace the original code with the one you've copied.
 9. Submit a PR with the changes.
     After the PR is merged, the updated diagram appears on the page.
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.md b/docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.md
index 8e6434c67d7..c78f6aea260 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.md
@@ -9,25 +9,25 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/build-the-documentation-site.html
+    link: docs/about/all/contribute-to-the-documentation/build-the-documentation-site.html
   - title: Add product sections to the documentation
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
+    link: docs/about/all/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
   - title: Edit documentation via pull requests
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
+    link: docs/about/all/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
   - title: Report documentation issues
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/report-documentation-issues.html
+    link: docs/about/all/contribute-to-the-documentation/report-documentation-issues.html
   - title: Review pull requests
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/review-pull-requests.html
+    link: docs/about/all/contribute-to-the-documentation/review-pull-requests.html
   - title: Style, syntax, formatting, and general rules
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/style-formatting-general-rules.html
+    link: docs/about/all/contribute-to-the-documentation/style-formatting-general-rules.html
   - title: Markdown syntax
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/markdown-syntax.html
+    link: docs/about/all/contribute-to-the-documentation/markdown-syntax.html
 ---
 
 We at Spryker aim to constantly improve the content we provide our customers and partners with. You can get involved in improving the Spryker documentation by:
 
-* [Reporting issues via GitHub](/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/report-documentation-issues.html).
-* [Editing documentation by creating pull requests on GitHub](/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/edit-documentation-via-pull-requests.html).
-* [Reviewing pull requests](/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/review-pull-requests.html).
+* [Reporting issues via GitHub](/docs/about/all/contribute-to-the-documentation/report-documentation-issues.html).
+* [Editing documentation by creating pull requests on GitHub](/docs/about/all/contribute-to-the-documentation/edit-documentation-via-pull-requests.html).
+* [Reviewing pull requests](/docs/about/all/contribute-to-the-documentation/review-pull-requests.html).
 
 Therefore, to contribute to the Spryker documentation, you must have a GitHub account. For information about how to create it, see [Signing up for a new GitHub account](https://docs.github.com/en/get-started/signing-up-for-github/signing-up-for-a-new-github-account) in the official GitHub documentation.
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-locally.md b/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-locally.md
index 1c4da038bdf..0ecbde38936 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-locally.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-locally.md
@@ -61,7 +61,7 @@ At this point, you are most likely to know which document you want to edit. To f
 
 1. Open the document you want to edit in an editor.
 2. Add the needed changes.
-    You'd help us a lot by following [Markdown syntax](/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/markdown-syntax.html) and [general rules](/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/style-formatting-general-rules.html), but it's completely optional. We are grateful for your contribution in any form.
+    You'd help us a lot by following [Markdown syntax](/docs/about/all/contribute-to-the-documentation/markdown-syntax.html) and [general rules](/docs/about/all/contribute-to-the-documentation/style-formatting-general-rules.html), but it's completely optional. We are grateful for your contribution in any form.
 3. Save the edited document.
 4. In GitHub Desktop, double-check your changes in the **Changes** tab.
 5. Below the list of edited files, enter the name and description of your changes. The name of your fist commit will be used as the pull request's name.
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.md b/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.md
index 3b33d1e5fda..8eab0bbbf62 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.md
@@ -11,24 +11,24 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/build-the-documentation-site.html
+    link: docs/about/all/contribute-to-the-documentation/build-the-documentation-site.html
   - title: Addi product sections to the documentation
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
+    link: docs/about/all/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
   - title: Report documentation issues
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/report-documentation-issues.html
+    link: docs/about/all/contribute-to-the-documentation/report-documentation-issues.html
   - title: Review pull requests
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/review-pull-requests.html
+    link: docs/about/all/contribute-to-the-documentation/review-pull-requests.html
   - title: Style, syntax, formatting, and general rules
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/style-formatting-general-rules.html
+    link: docs/about/all/contribute-to-the-documentation/style-formatting-general-rules.html
   - title: Markdown syntax
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/markdown-syntax.html
+    link: docs/about/all/contribute-to-the-documentation/markdown-syntax.html
 ---
 
 The Spryker documentation is hosted on GitHub, in the [spryker-docs](https://github.com/spryker/spryker-docs) repository. Therefore, to contribute to the Spryker documents, you have to use GitHub. For more information about what GitHub is, see [About Git](https://docs.github.com/en/get-started/using-git/about-git).
 
 {% info_block infoBox "Info" %}
 
-We write the Spryker documentation using Markdown. If you don’t know Markdown yet, check the [GitHub Markdown Guide](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax). For the documentation-specific Markdown elements and HTML syntax used where Markdown is not enough, see [Markdown syntax](/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/markdown-syntax.html).
+We write the Spryker documentation using Markdown. If you don’t know Markdown yet, check the [GitHub Markdown Guide](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax). For the documentation-specific Markdown elements and HTML syntax used where Markdown is not enough, see [Markdown syntax](/docs/about/all/contribute-to-the-documentation/markdown-syntax.html).
 
 {% endinfo_block %}
 
@@ -36,7 +36,7 @@ This instruction explains how to contribute to the Spryker documentation by crea
 
 {% info_block infoBox "Info" %}
 
-For information about the structure of the Spryker documentation, as well as style and formatting rules, see [Style, syntax, formatting, and general rules](/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/style-formatting-general-rules.html).
+For information about the structure of the Spryker documentation, as well as style and formatting rules, see [Style, syntax, formatting, and general rules](/docs/about/all/contribute-to-the-documentation/style-formatting-general-rules.html).
 
 
 Note that Spryker documentation is written in US English.
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.md b/docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.md
index be47e546d98..4494aaca96d 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.md
@@ -9,17 +9,17 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/build-the-documentation-site.html
+    link: docs/about/all/contribute-to-the-documentation/build-the-documentation-site.html
   - title: Add product sections to the documentation
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
+    link: docs/about/all/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
   - title: Edit documentation via pull requests
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
+    link: docs/about/all/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
   - title: Review pull requests
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/review-pull-requests.html
+    link: docs/about/all/contribute-to-the-documentation/review-pull-requests.html
   - title: Style, syntax, formatting, and general rules
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/style-formatting-general-rules.html
+    link: docs/about/all/contribute-to-the-documentation/style-formatting-general-rules.html
   - title: Markdown syntax
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/markdown-syntax.html
+    link: docs/about/all/contribute-to-the-documentation/markdown-syntax.html
 ---
 
 To report an issue with a Spryker document, do the following:
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.md b/docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.md
index 7aeafe54e2d..ed1c28b7fa5 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.md
@@ -9,17 +9,17 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/build-the-documentation-site.html
+    link: docs/about/all/contribute-to-the-documentation/build-the-documentation-site.html
   - title: Add product sections to the documentation
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
+    link: docs/about/all/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
   - title: Edit documentation via pull requests
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
+    link: docs/about/all/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
   - title: Report documentation issues
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/report-documentation-issues.html
+    link: docs/about/all/contribute-to-the-documentation/report-documentation-issues.html
   - title: Style, syntax, formatting, and general rules
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/style-formatting-general-rules.html
+    link: docs/about/all/contribute-to-the-documentation/style-formatting-general-rules.html
   - title: Markdown syntax
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/markdown-syntax.html
+    link: docs/about/all/contribute-to-the-documentation/markdown-syntax.html
 ---
 
 When someone requests your review of a pull request, you get an email about the request. <!--Also, a message with the review request is displayed on the pull request page:IMAGE-->
diff --git a/docs/about/all/about-the-docs/install-recommended-vs-code-extensions.md b/docs/about/all/about-the-docs/install-recommended-vs-code-extensions.md
index dc7049a8392..2fef35067f3 100644
--- a/docs/about/all/about-the-docs/install-recommended-vs-code-extensions.md
+++ b/docs/about/all/about-the-docs/install-recommended-vs-code-extensions.md
@@ -8,17 +8,17 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/build-the-documentation-site.html
+    link: docs/about/all/contribute-to-the-documentation/build-the-documentation-site.html
   - title: Addi product sections to the documentation
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
+    link: docs/about/all/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
   - title: Report documentation issues
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/report-documentation-issues.html
+    link: docs/about/all/contribute-to-the-documentation/report-documentation-issues.html
   - title: Review pull requests
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/review-pull-requests.html
+    link: docs/about/all/contribute-to-the-documentation/review-pull-requests.html
   - title: Style, syntax, formatting, and general rules
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/style-formatting-general-rules.html
+    link: docs/about/all/contribute-to-the-documentation/style-formatting-general-rules.html
   - title: Markdown syntax
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/markdown-syntax.html
+    link: docs/about/all/contribute-to-the-documentation/markdown-syntax.html
 ---
 
 We recommend the following VS Code extensions for writing and reviewing documents:
diff --git a/docs/about/all/about-the-docs/run-the-docs-locally.md b/docs/about/all/about-the-docs/run-the-docs-locally.md
index aaa5ff5d0dd..d8ea45cb969 100644
--- a/docs/about/all/about-the-docs/run-the-docs-locally.md
+++ b/docs/about/all/about-the-docs/run-the-docs-locally.md
@@ -9,17 +9,17 @@ redirect_from:
 
 related:
   - title: Add product sections to the documentation
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
+    link: docs/about/all/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
   - title: Edit documentation via pull requests
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
+    link: docs/about/all/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
   - title: Report documentation issues
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/report-documentation-issues.html
+    link: docs/about/all/contribute-to-the-documentation/report-documentation-issues.html
   - title: Review pull requests
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/review-pull-requests.html
+    link: docs/about/all/contribute-to-the-documentation/review-pull-requests.html
   - title: Style, syntax, formatting, and general rules
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/style-formatting-general-rules.html
+    link: docs/about/all/contribute-to-the-documentation/style-formatting-general-rules.html
   - title: Markdown syntax
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/markdown-syntax.html
+    link: docs/about/all/contribute-to-the-documentation/markdown-syntax.html
 ---
 
 We use [Jekyll](https://jekyllrb.com/) to build the Spryker documentation site. To build it locally, you need to:
diff --git a/docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.md b/docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.md
index a8667d7eb1b..6e3533f4fbd 100644
--- a/docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.md
+++ b/docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.md
@@ -10,17 +10,17 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/build-the-documentation-site.html
+    link: docs/about/all/contribute-to-the-documentation/build-the-documentation-site.html
   - title: Add product sections to the documentation
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
+    link: docs/about/all/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
   - title: Edit documentation via pull requests
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
+    link: docs/about/all/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
   - title: Report documentation issues
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/report-documentation-issues.html
+    link: docs/about/all/contribute-to-the-documentation/report-documentation-issues.html
   - title: Review pull requests
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/review-pull-requests.html
+    link: docs/about/all/contribute-to-the-documentation/review-pull-requests.html
   - title: Markdown syntax
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/markdown-syntax.html
+    link: docs/about/all/contribute-to-the-documentation/markdown-syntax.html
 ---
 
 This document describes the directory structure, templates, front matter, and versioning of Spryker documentation.
@@ -33,7 +33,7 @@ The main directory for holding all the documents is [docs](https://github.com/sp
 
 ## Creating documents and categories
 
-We use [Markdown (.md)](https://en.wikipedia.org/wiki/Markdown) to write documents. All documents reside in the [docs](https://github.com/spryker/spryker-docs/tree/master/docs) directory. For details about how this directory is organized, see [Directory structure](#directory-structure). You can use any text editor for creating the files in Markdown, like [VSCode](https://code.visualstudio.com). For information about specific Markdown syntax for documentation, see [Markdown syntax](/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/markdown-syntax.html).
+We use [Markdown (.md)](https://en.wikipedia.org/wiki/Markdown) to write documents. All documents reside in the [docs](https://github.com/spryker/spryker-docs/tree/master/docs) directory. For details about how this directory is organized, see [Directory structure](#directory-structure). You can use any text editor for creating the files in Markdown, like [VSCode](https://code.visualstudio.com). For information about specific Markdown syntax for documentation, see [Markdown syntax](/docs/about/all/contribute-to-the-documentation/markdown-syntax.html).
 
 You can create new pages in any documentation category or sub-category under the *realm* directories (`user`, `dev`). You can also create directories for new categories under the *realm* directories.
 
diff --git a/docs/about/all/about-the-docs/style-guide/markdown-syntax.md b/docs/about/all/about-the-docs/style-guide/markdown-syntax.md
index db620ee2a8a..223a64db77a 100644
--- a/docs/about/all/about-the-docs/style-guide/markdown-syntax.md
+++ b/docs/about/all/about-the-docs/style-guide/markdown-syntax.md
@@ -9,17 +9,17 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/build-the-documentation-site.html
+    link: docs/about/all/contribute-to-the-documentation/build-the-documentation-site.html
   - title: Adding product sections to the documentation
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
+    link: docs/about/all/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
   - title: Edit documentation via pull requests
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
+    link: docs/about/all/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
   - title: Report documentation issues
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/report-documentation-issues.html
+    link: docs/about/all/contribute-to-the-documentation/report-documentation-issues.html
   - title: Review pull requests
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/review-pull-requests.html
+    link: docs/about/all/contribute-to-the-documentation/review-pull-requests.html
   - title: Style, syntax, formatting, and general rules
-    link: docs/scos/user/intro-to-spryker/contribute-to-the-documentation/style-formatting-general-rules.html
+    link: docs/about/all/contribute-to-the-documentation/style-formatting-general-rules.html
 ---
 
 We use Markdown to write the Spryker documentation. This document contains the Markdown syntax of the page elements used on the Spryker documentation website, specifically:
diff --git a/docs/about/all/b2b-suite.md b/docs/about/all/b2b-suite.md
index 1e663976f72..711139eb284 100644
--- a/docs/about/all/b2b-suite.md
+++ b/docs/about/all/b2b-suite.md
@@ -9,7 +9,7 @@ redirect_from:
 - /docs/scos/user/intro-to-spryker/b2b-suite.html
 related:
   - title: B2C Suite
-    link: docs/scos/user/intro-to-spryker/b2c-suite.html
+    link: docs/about/all/b2c-suite.html
 ---
 
 The Spryker B2B Suite is a collection of ready-to-use B2B-specific features:
diff --git a/docs/about/all/b2c-suite.md b/docs/about/all/b2c-suite.md
index 1e0c91792c8..cb280ecb5fd 100644
--- a/docs/about/all/b2c-suite.md
+++ b/docs/about/all/b2c-suite.md
@@ -19,7 +19,7 @@ redirect_from:
   - /v6/docs/en/b2c-suite
 related:
   - title: B2B Suite
-    link: docs/scos/user/intro-to-spryker/b2b-suite.html
+    link: docs/about/all/b2b-suite.html
 ---
 
 The Spryker B2С Suite is a collection of ready-to-use B2С-specific features. Of course, every B2С project has its own set of features that meet its business needs and B2B features can be used as well, but the most common features for B2C commerce are as follows.
diff --git a/docs/about/all/docs-updates.md b/docs/about/all/docs-updates.md
index 0af4085ef40..5a56e22e196 100644
--- a/docs/about/all/docs-updates.md
+++ b/docs/about/all/docs-updates.md
@@ -167,7 +167,7 @@ In December 2023, we have added and updated the following pages:
 - [Decoupled Glue infrastructure: Integrate the authentication](/docs/dg/dev/upgrade-and-migrate/migrate-to-decoupled-glue-infrastructure/decoupled-glue-infrastructure-integrate-the-authentication.html): Learn how to create an authentication token for the Storefront and Backend API applications in a Spryker project.
 - [Create Glue API authorization strategies](/docs/dg/dev/glue-api/202311.0/create-glue-api-authorization-strategies.html): Learn how to create a new authorization strategy.
 - [Preparation for going live](/docs/ca/dev/preparation-for-going-live.html): Learn how to prepare a Spryker project for going live.
-- [Security release notes 202312.0](/docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202312.0.html).
+- [Security release notes 202312.0](/docs/about/all/releases/release-notes/security-release-notes-202312.0.html).
 - [Checkout feature overview](/docs/pbc/all/cart-and-checkout/202404.0/base-shop/feature-overviews/checkout-feature-overview/checkout-feature-overview.html).
 - [Install the Checkout Glue API](/docs/pbc/all/cart-and-checkout/202404.0/base-shop/install-and-upgrade/install-glue-api/install-the-checkout-glue-api.html).
 - [Shipment feature overview](/docs/pbc/all/carrier-management/202311.0/base-shop/shipment-feature-overview.html).
@@ -249,8 +249,8 @@ In November 2023, we have added and updated the following pages:
 - [Backend API Marketplace B2C Demo Shop reference](/docs/dg/dev/glue-api/202311.0/backend-glue-infrastructure/backend-api-marketplace-b2c-demo-shop-reference.html).
 - [REST API Marketplace B2B Demo Shop reference](/docs/dg/dev/glue-api/202311.0/old-glue-infrastructure/rest-api-marketplace-b2b-demo-shop-reference.html).
 - [REST API Marketplace B2C Demo Shop reference](/docs/dg/dev/glue-api/202311.0/old-glue-infrastructure/rest-api-marketplace-b2c-demo-shop-reference.html).
-- [Release notes 202311.0](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202311.0/release-notes-202311.0.html).
-- [Security release notes 202312.0](/docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202312.0.html).
+- [Release notes 202311.0](/docs/about/all/releases/release-notes/release-notes-202311.0/release-notes-202311.0.html).
+- [Security release notes 202312.0](/docs/about/all/releases/release-notes/security-release-notes-202312.0.html).
 
 ### Updated pages
 
@@ -278,7 +278,7 @@ In October 2023, we have added and updated the following pages:
 - [Data Exchange](/docs/pbc/all/data-exchange/202311.0/data-exchange.html): Get an overview of the Data Exchange features: Data Importers and Data Exporters, Data Exchange API, Spryker Middleware powered by Alumio.
 - [Data Exchange FAQ](/docs/pbc/all/data-exchange/202311.0/data-exchange-faq.html).
 - [Install the Data Exchange API + Inventory Management feature](/docs/pbc/all/data-exchange/202311.0/install-and-upgrade/install-the-data-exchange-api-inventory-management-feature.html).
-- [Security release notes 202309.0](/docs/scos/user/intro-to-spryker/releases/release-notes/security-release-notes-202309.0.html).
+- [Security release notes 202309.0](/docs/about/all/releases/release-notes/security-release-notes-202309.0.html).
 - [Upgrade the Chart module](/docs/pbc/all/back-office/202307.0/install-and-upgrade/upgrade-the-chart-module.html): Learn how to upgrade the Chart module from version 1.5.0 to version 1.6.1.
 - Oryx components docs:
     - [Oryx: Building components](/docs/dg/dev/frontend-development/202307.0/oryx/building-components/oryx-building-components.html): Learn about the building blocks of the Oryx applications: the components.
@@ -369,8 +369,8 @@ In August 2023, we have added and updated the following pages:
 ### New pages
 
 - [HowTo: Reduce Jenkins execution by up to 80% without P&S and Data importers refactoring](/docs/dg/dev/backend-development/cronjobs/optimizing-jenkins-execution.html): Learn how to save Jenkins-related costs or speed up background jobs processing by implementing a single custom worker for all stores.
-- [Release notes 202307.0](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202307.0/release-notes-202307.0.html).
-- [Security release notes 202307.0](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202307.0/security-release-notes-202307.0.html).
+- [Release notes 202307.0](/docs/about/all/releases/release-notes/release-notes-202307.0/release-notes-202307.0.html).
+- [Security release notes 202307.0](/docs/about/all/releases/release-notes/release-notes-202307.0/security-release-notes-202307.0.html).
 - [Spryker security checker](/docs/dg/dev/guidelines/keeping-a-project-upgradable/upgradability-guidelines/spryker-security-checker.html): Learn how to check for security fixes in the Spryker modules.
 - [Open-source vulnerabilities checker](/docs/dg/dev/guidelines/keeping-a-project-upgradable/upgradability-guidelines/open-source-vulnerabilities.html): Learn how to check if your PHP application depends on PHP packages with known security vulnerabilities.
 - [Dynamic multistore docs](/docs/pbc/all/dynamic-multistore/202307.0/dynamic-multistore.html):
@@ -415,7 +415,7 @@ In July 2023, we have added and updated the following pages:
 - [Oryx: Color system](/docs/dg/dev/frontend-development/202212.0/oryx/building-applications/styling/oryx-color-system.html): Documentation on colors in Oryx.
 - [Best practises: Jenkins stability](/docs/ca/dev/best-practices/best-practises-jenkins-stability.html): Best practices for maintaining Jenkins stability.
 - [HowTo: Reduce Jenkins execution by up to 80% without P&S and Data importers refactoring](/docs/dg/dev/backend-development/cronjobs/optimizing-jenkins-execution.html): Save Jenkins-related costs or speed up background jobs processing by implementing a single custom Worker for all stores.
-- [Release notes 202307.0](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202307.0/release-notes-202307.0.html): Release notes for the Spryker SCOS release 202307.0
+- [Release notes 202307.0](/docs/about/all/releases/release-notes/release-notes-202307.0/release-notes-202307.0.html): Release notes for the Spryker SCOS release 202307.0
 - [Install the Product Rating and Reviews Glue API](/docs/pbc/all/ratings-reviews/202307.0/install-and-upgrade/install-the-product-rating-and-reviews-glue-api.html): This document describes how to integrate the [Product Rating and Reviews](/docs/pbc/all/ratings-reviews/{{site.version}}/ratings-and-reviews.html) Glue API feature into a Spryker project.
 - [Configure Usercentrics](/docs/pbc/all/usercentrics/configure-usercentrics.html): Find out how you can configure Usercentrics in your Spryker shop.
 - [Ratings and Reviews data import](/docs/pbc/all/ratings-reviews/202204.0/import-and-export-data/ratings-and-reviews-data-import.html): Details about data import files for the Ratings and Reviews PBC.
@@ -428,20 +428,20 @@ In July 2023, we have added and updated the following pages:
 - [Integrate Usercentrics](/docs/pbc/all/usercentrics/integrate-usercentrics.html): Find out how you can integrate Usercentrics in your Spryker shop.
 - [Usercentrics](/docs/pbc/all/usercentrics/usercentrics.html): [Usercentrics](https://usercentrics.com/) is the Consent Management Platform (CMP) that lets you obtain and manage the consent of your users to use cookies across your store.
 - [Adding variables in the parameter store](/docs/ca/dev/add-variables-in-the-parameter-store.html): Added reserved variable sub-section and removed deprecated text.
-- [Security Release Notes 202306.0](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202306.0/security-release-notes-202306.0.html): Added missing security HTTP headers.
+- [Security Release Notes 202306.0](/docs/about/all/releases/release-notes/release-notes-202306.0/security-release-notes-202306.0.html): Added missing security HTTP headers.
 - [Merchant Users Overview](/docs/pbc/all/merchant-management/202212.0/marketplace/marketplace-merchant-feature-overview/merchant-users-overview.html): Added information about the assignment of groups for the merchant user.
 - [Handle data with Publish and Synchronization](/docs/dg/dev/backend-development/data-manipulation/data-publishing/handle-data-with-publish-and-synchronization.html): Publish and Synchronization (P&S) lets you export data from Spryker backend (Zed) to external endpoints.
 - [Install the Spryker Core feature](/docs/pbc/all/miscellaneous/202307.0/install-and-upgrade/install-features/install-the-spryker-core-feature.html): Updated code sample.
 - [Install Docker prerequisites on Linux](/docs/dg/dev/set-up-spryker-locally/install-spryker/install-docker-prerequisites/install-docker-prerequisites-on-linux.html): Learn about the steps you need to take before you can start working with Spryker in Docker on Linux.
 - [Payment Service Provider](/docs/pbc/all/payment-service-provider/202212.0/payment-service-provider.html): Different payment methods for your shop.
 - [System requirements](/docs/scos/dev/system-requirements/202304.0/system-requirements.html): This document provides the configuration that a system must have in order for the Spryker project to run smoothly and efficiently.
-- [Supported browsers](/docs/scos/user/intro-to-spryker/supported-browsers.html): This document lists browsers supported by Spryker Cloud Commerce OS.
+- [Supported browsers](/docs/about/all/supported-browsers.html): This document lists browsers supported by Spryker Cloud Commerce OS.
 - [Install the shipment feature](/docs/pbc/all/carrier-management/202311.0/base-shop/install-and-upgrade/install-features/install-the-shipment-feature.html)
 - [App Composition Platform installation](/docs/acp/user/app-composition-platform-installation.html)
 - [App manifest](/docs/dg/dev/acp/develop-an-app/app-manifest.html): App Manifest is a set of JSON files that contain all the necessary information to register an application in the Application Tenant Registry Service and to display information about the application in the Application Catalog.
 - [Development strategies](/docs/dg/dev/backend-development/extend-spryker/development-strategies.html): Development strategies that you can use when building a Spryker project.
 - [Project development guidelines](/docs/dg/dev/guidelines/project-development-guidelines.html): This document describes the strategies a project team can take while building a Spryker-based project.
-- [Handling security issues](/docs/scos/user/intro-to-spryker/support/handling-security-issues.html): Use this document to learn how to report a security issue and to understand how we handle these reports.     
+- [Handling security issues](/docs/about/all/support/handling-security-issues.html): Use this document to learn how to report a security issue and to understand how we handle these reports.     
 - [Install the Measurement Units feature](/docs/pbc/all/product-information-management/202307.0/base-shop/install-and-upgrade/install-features/install-the-measurement-units-feature.html): The guide describes how to integrate the [Measurement Units](/docs/pbc/all/product-information-management/202307.0/base-shop/feature-overviews/measurement-units-feature-overview.html) feature into your project.
 
 For more details about these and other updates to the Spryker docs in July 2023, refer to the [docs release notes page on GitHub](https://github.com/spryker/spryker-docs/releases).
@@ -451,7 +451,7 @@ For more details about these and other updates to the Spryker docs in July 2023,
 In June 2023, we have added and updated the following pages:
 
 ### New pages
-- [Security release notes 202306.0](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202306.0/security-release-notes-202306.0.html).
+- [Security release notes 202306.0](/docs/about/all/releases/release-notes/release-notes-202306.0/security-release-notes-202306.0.html).
 - [Oryx: Presets](/docs/dg/dev/frontend-development/202212.0/oryx/building-applications/oryx-presets.html): Learn how you can use presets to install predefined applications.
 - [Service Points feature integration guide](/docs/pbc/all/service-point-management/202311.0/unified-commerce/install-features/install-the-service-points-feature.html).
 - [Shipment + Service Points feature integration guide](/docs/pbc/all/carrier-management/202311.0/unified-commerce/install-features/install-the-shipment-service-points-feature.html).
@@ -461,9 +461,9 @@ In June 2023, we have added and updated the following pages:
     - [File details - shipment_type_store.csv](/docs/pbc/all/carrier-management/202311.0/base-shop/import-and-export-data/import-file-details-shipment-type-store.csv.html).
     - [File details - shipment_type.csv](/docs/pbc/all/carrier-management/202311.0/base-shop/import-and-export-data/import-file-details-shipment-type.csv.html).
 - [Migration guide - Upgrade Node.js to v18 and npm to v9](/docs/dg/dev/upgrade-and-migrate/upgrade-nodejs-to-v18-and-npm-to-v9.html).
-- [Spryker documentation style guide](/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/spryker-documentation-style-guide/spryker-documentation-style-guide.html):
-    - [Examples](/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/spryker-documentation-style-guide/examples.html).
-    - [Spelling](/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/spryker-documentation-style-guide/spelling.html).
+- [Spryker documentation style guide](/docs/about/all/contribute-to-the-documentation/spryker-documentation-style-guide/spryker-documentation-style-guide.html):
+    - [Examples](/docs/about/all/contribute-to-the-documentation/spryker-documentation-style-guide/examples.html).
+    - [Spelling](/docs/about/all/contribute-to-the-documentation/spryker-documentation-style-guide/spelling.html).
 
 ## Updated pages
 - [Environments overview](/docs/ca/dev/environments-overview.html).
@@ -492,7 +492,7 @@ In May 2023, we have added and updated the following pages:
 
 ### New pages
 
-- [Docs release notes](/docs/scos/user/intro-to-spryker/docs-release-notes.html)
+- [Docs release notes](/docs/about/all/docs-release-notes.html)
 - Multistore documentation:
     - [Multistore setup options](/docs/ca/dev/multi-store-setups/multistore-setup-options.html): Learn about all the setup options you have for a multi-store environment.
     - [Checklist for a new store implementation](/docs/ca/dev/multi-store-setups/checklist-for-a-new-store-implementation.html): Overview of the high-level tasks and responsibilities of Spryker and Customer when setting up a new store.
@@ -558,7 +558,7 @@ In April 2023, we have added and updated the following pages:
 - Warehouse picking feature integration guides:
     - [Install the Warehouse picking feature](/docs/pbc/all/warehouse-management-system/202311.0/unified-commerce/install-and-upgrade/install-the-warehouse-picking-feature.html)
     - [Install the Warehouse picking + Product feature](/docs/pbc/all/warehouse-management-system/202311.0/unified-commerce/install-and-upgrade/install-the-warehouse-picking-feature.html)
-- [Security release notes 202304.0](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202304.0/security-release-notes-202304.0.html)
+- [Security release notes 202304.0](/docs/about/all/releases/release-notes/release-notes-202304.0/security-release-notes-202304.0.html)
 - [Releases vs Customization types](/docs/dg/dev/sdks/sdk/customization-strategies-and-upgradability.html): Learn about the customization strategies and release types you can use to integrate releases and customize your project.
 
 ### Updated pages
diff --git a/docs/about/all/releases/product-and-code-releases.md b/docs/about/all/releases/product-and-code-releases.md
index 9a795a639aa..a7c0e68d315 100644
--- a/docs/about/all/releases/product-and-code-releases.md
+++ b/docs/about/all/releases/product-and-code-releases.md
@@ -74,4 +74,4 @@ To receive the security updates, please request the subsription at [support@spry
 
 ## Next steps
 
-* [Release notes](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes.html)
+* [Release notes](/docs/about/all/releases/release-notes/release-notes.html)
diff --git a/docs/about/all/releases/release-notes-202211.0.md b/docs/about/all/releases/release-notes-202211.0.md
index e5a2f56b060..0e31963052a 100644
--- a/docs/about/all/releases/release-notes-202211.0.md
+++ b/docs/about/all/releases/release-notes-202211.0.md
@@ -17,4 +17,4 @@ With 202211.0, Spryker released a new version of its Demo Shops requiring PHP 8.
 Backward compatibility remains unaffected. If your project followed our recommendations and requirements in the past twelve months, you will not experience any upgradability issues.
 
 **Documentation:**
-[How to migrate](/docs/scos/user/intro-to-spryker/whats-new/php8-as-a-minimum-version-for-all-spryker-projects.html#migration-steps)
+[How to migrate](/docs/about/all/whats-new/php8-as-a-minimum-version-for-all-spryker-projects.html#migration-steps)
diff --git a/docs/about/all/releases/security-release-notes-202302.0.md b/docs/about/all/releases/security-release-notes-202302.0.md
index 7f9465cc55c..f7676754102 100644
--- a/docs/about/all/releases/security-release-notes-202302.0.md
+++ b/docs/about/all/releases/security-release-notes-202302.0.md
@@ -154,7 +154,7 @@ This involves additional migration effort because of a required upgrade to PHP 8
 
 {% endinfo_block %}
 
-To upgrade to PHP 8.0, see [Supported versions of PHP](/docs/scos/user/intro-to-spryker/whats-new/supported-versions-of-php.html).
+To upgrade to PHP 8.0, see [Supported versions of PHP](/docs/about/all/whats-new/supported-versions-of-php.html).
 
 Ensure that you have the security fix applied to the PHP8 version.
 
diff --git a/docs/about/all/security-audit-reports/2019.11-security-audit-by-sektioneins.md b/docs/about/all/security-audit-reports/2019.11-security-audit-by-sektioneins.md
index 67c94efe577..e3198d19625 100644
--- a/docs/about/all/security-audit-reports/2019.11-security-audit-by-sektioneins.md
+++ b/docs/about/all/security-audit-reports/2019.11-security-audit-by-sektioneins.md
@@ -16,7 +16,7 @@ Between October 7th and November 22nd, 2019 SektionEins performed a source code
 
 [SektionEins](https://www.sektioneins.de/) conducted the audit.
 
-The evaluation of the Commerce OS was done without having prior knowledge of the source code, to protect it from attackers. Where it was the case, the found vulnerabilities were verified using the [B2B](/docs/scos/user/intro-to-spryker/b2b-suite.html) and [B2C Demo Shops](/docs/scos/user/intro-to-spryker/b2c-suite.html).
+The evaluation of the Commerce OS was done without having prior knowledge of the source code, to protect it from attackers. Where it was the case, the found vulnerabilities were verified using the [B2B](/docs/about/all/b2b-suite.html) and [B2C Demo Shops](/docs/about/all/b2c-suite.html).
 
 Here is the summary of the security audit report:
 
diff --git a/docs/about/all/spryker-marketplace/back-office-for-marketplace-operator.md b/docs/about/all/spryker-marketplace/back-office-for-marketplace-operator.md
index 2f465d3d19f..c9a04d5e5de 100644
--- a/docs/about/all/spryker-marketplace/back-office-for-marketplace-operator.md
+++ b/docs/about/all/spryker-marketplace/back-office-for-marketplace-operator.md
@@ -9,11 +9,11 @@ redirect_from:
 
 ---
 
-A *marketplace operator* is a company that owns the marketplace. In a marketplace business model, one or more of such a company's employees represent a marketplace operator and manage the store. We call such users [marketplace administrators](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-personas.html#marketplace-administrator). Depending on the marketplace model, the marketplace operator either manages only other merchants' orders or also sells products as a [main merchant](/docs/pbc/all/merchant-management/{{site.version}}/marketplace/marketplace-merchant-feature-overview/main-merchant.html).
+A *marketplace operator* is a company that owns the marketplace. In a marketplace business model, one or more of such a company's employees represent a marketplace operator and manage the store. We call such users [marketplace administrators](/docs/about/all/spryker-marketplace/marketplace-personas.html#marketplace-administrator). Depending on the marketplace model, the marketplace operator either manages only other merchants' orders or also sells products as a [main merchant](/docs/pbc/all/merchant-management/{{site.version}}/marketplace/marketplace-merchant-feature-overview/main-merchant.html).
 
 ## Merchant management
 
-Merchant accounts are created in the Back Office, and a [marketplace administrator](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-personas.html#marketplace-administrator) is required to facilitate their creation. In the **Marketplace&nbsp;<span aria-label="and then">></span> Merchants** section of the Back Office, a marketplace operator manages merchants as follows:
+Merchant accounts are created in the Back Office, and a [marketplace administrator](/docs/about/all/spryker-marketplace/marketplace-personas.html#marketplace-administrator) is required to facilitate their creation. In the **Marketplace&nbsp;<span aria-label="and then">></span> Merchants** section of the Back Office, a marketplace operator manages merchants as follows:
 
 * Creates merchants
 * Edits merchants
@@ -58,10 +58,10 @@ For detailed instructions on managing returns, see [Managing marketplace returns
 
 ## Main merchant sales
 
-In an [enterprise marketplace business model](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-concept.html), apart from managing the marketplace, a marketplace operator sells products as a [main merchant](/docs/pbc/all/merchant-management/{{site.version}}/marketplace/marketplace-merchant-feature-overview/main-merchant.html). In the Back Office, they manage their orders and returns in **Sales&nbsp;<span aria-label="and then">></span> My Orders** and **Sales&nbsp;<span aria-label="and then">></span> My returns** sections, respectively. With their own orders, they can perform the same actions as they do with other merchants' as described in [Order management](#order-management) and [Return management](#return-management). Apart from that, they can create and edit shipments for their orders.
+In an [enterprise marketplace business model](/docs/about/all/spryker-marketplace/marketplace-concept.html), apart from managing the marketplace, a marketplace operator sells products as a [main merchant](/docs/pbc/all/merchant-management/{{site.version}}/marketplace/marketplace-merchant-feature-overview/main-merchant.html). In the Back Office, they manage their orders and returns in **Sales&nbsp;<span aria-label="and then">></span> My Orders** and **Sales&nbsp;<span aria-label="and then">></span> My returns** sections, respectively. With their own orders, they can perform the same actions as they do with other merchants' as described in [Order management](#order-management) and [Return management](#return-management). Apart from that, they can create and edit shipments for their orders.
 
 For detailed instructions about managing main merchant orders and returns, see [Managing main merchant orders](/docs/pbc/all/order-management-system/{{site.version}}/marketplace/manage-in-the-back-office/manage-main-merchant-orders.html) and [Managing main merchant returns](/docs/pbc/all/return-management/{{site.version}}/marketplace/manage-in-the-back-office/manage-main-merchant-returns.html).
 
 ## Read next
 
-[Marketplace Storefront](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-storefront.html)
+[Marketplace Storefront](/docs/about/all/spryker-marketplace/marketplace-storefront.html)
diff --git a/docs/about/all/spryker-marketplace/marketplace-concept.md b/docs/about/all/spryker-marketplace/marketplace-concept.md
index e3450e9e208..35f715c7c16 100644
--- a/docs/about/all/spryker-marketplace/marketplace-concept.md
+++ b/docs/about/all/spryker-marketplace/marketplace-concept.md
@@ -37,4 +37,4 @@ Check out this video to learn more about the Marketplace in the Spryker Commerce
 
 ## Read next
 
-[Marketplace personas](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-personas.html)
+[Marketplace personas](/docs/about/all/spryker-marketplace/marketplace-personas.html)
diff --git a/docs/about/all/spryker-marketplace/marketplace-personas.md b/docs/about/all/spryker-marketplace/marketplace-personas.md
index db25084c355..4f2ee823550 100644
--- a/docs/about/all/spryker-marketplace/marketplace-personas.md
+++ b/docs/about/all/spryker-marketplace/marketplace-personas.md
@@ -39,4 +39,4 @@ A *buyer* is a user who actively uses the Storefront. It is either a registered
 
 ## Read next
 
-[Back Office for Marketplace Operator](/docs/scos/user/intro-to-spryker/spryker-marketplace/back-office-for-marketplace-operator.html)
+[Back Office for Marketplace Operator](/docs/about/all/spryker-marketplace/back-office-for-marketplace-operator.html)
diff --git a/docs/about/all/spryker-marketplace/marketplace-storefront.md b/docs/about/all/spryker-marketplace/marketplace-storefront.md
index bbfb3772fdc..c53de3895e7 100644
--- a/docs/about/all/spryker-marketplace/marketplace-storefront.md
+++ b/docs/about/all/spryker-marketplace/marketplace-storefront.md
@@ -9,7 +9,7 @@ redirect_from:
 
 ---
 
-*Marketplace Storefront* is a web application designed for the [marketplace business model](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-concept.html). Based on the regular Storefront, it supports all [Spryker Commerce OS](/docs/scos/user/intro-to-spryker/intro-to-spryker.html) features. Marketplace functionality lets buyers browse for products and view and purchase them across different merchants.
+*Marketplace Storefront* is a web application designed for the [marketplace business model](/docs/about/all/spryker-marketplace/marketplace-concept.html). Based on the regular Storefront, it supports all [Spryker Commerce OS](/docs/about/all/intro-to-spryker.html) features. Marketplace functionality lets buyers browse for products and view and purchase them across different merchants.
 
 In most sections of the Marketplace Storefront, customers can see who the seller of a product or offer is.
 
@@ -122,4 +122,4 @@ For an example, see the [Spryker merchant profile](https://www.de.b2c-marketplac
 
 ## Read next
 
-[Merchant Portal](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-storefront.html)
+[Merchant Portal](/docs/about/all/spryker-marketplace/marketplace-storefront.html)
diff --git a/docs/about/all/spryker-marketplace/merchant-onboarding.md b/docs/about/all/spryker-marketplace/merchant-onboarding.md
index 5db40267ab9..9cd580c6cff 100644
--- a/docs/about/all/spryker-marketplace/merchant-onboarding.md
+++ b/docs/about/all/spryker-marketplace/merchant-onboarding.md
@@ -10,11 +10,11 @@ last_updated: Mar 29, 2023
 ---
 
 This document describes how to onboard merchants.
-Once created and approved, merchants become official marketplace members and can create products and offers to sell, fulfill orders and manage their profile in [Merchant Portal](/docs/scos/user/intro-to-spryker/spryker-marketplace/merchant-portal.html).
+Once created and approved, merchants become official marketplace members and can create products and offers to sell, fulfill orders and manage their profile in [Merchant Portal](/docs/about/all/spryker-marketplace/merchant-portal.html).
 
 There are two primary roles: *operator* and *merchant*:
-* An [operator](/docs/scos/user/intro-to-spryker/spryker-marketplace/back-office-for-marketplace-operator.html) is a company that owns and administers the platform.
-* A [merchant](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-personas.html#merchant-user) is a business entity or individual that sells products on the operator's platform. The operator is responsible and engaged with the merchants to determine how they conduct their operations on the platform. The operator can be a merchant as well.
+* An [operator](/docs/about/all/spryker-marketplace/back-office-for-marketplace-operator.html) is a company that owns and administers the platform.
+* A [merchant](/docs/about/all/spryker-marketplace/marketplace-personas.html#merchant-user) is a business entity or individual that sells products on the operator's platform. The operator is responsible and engaged with the merchants to determine how they conduct their operations on the platform. The operator can be a merchant as well.
 
 The merchant onboarding process consists of seven steps. Each step requires specific actions that merchants, operators, or both need to take.
 
@@ -79,7 +79,7 @@ In the Merchant Portal, merchants can [create and update products](/docs/pbc/all
 {% info_block infoBox %}
 
 Based on the product volume, we recommend the following:
-- If the number of products to be created or edited is small, merchants can use the interface in the [Merchant Portal](/docs/scos/user/intro-to-spryker/spryker-marketplace/merchant-portal.html).
+- If the number of products to be created or edited is small, merchants can use the interface in the [Merchant Portal](/docs/about/all/spryker-marketplace/merchant-portal.html).
 - For large volumes, use a file and data importers or integrate with the merchant PIM or ERP system through the [Spryker Middleware](/docs/dg/dev/backend-development/data-manipulation/data-ingestion/spryker-link-middleware.html).
 
 {% endinfo_block %}
diff --git a/docs/about/all/spryker-marketplace/spryker-marketplace.md b/docs/about/all/spryker-marketplace/spryker-marketplace.md
index e1eea9108fb..e43e3959ee1 100644
--- a/docs/about/all/spryker-marketplace/spryker-marketplace.md
+++ b/docs/about/all/spryker-marketplace/spryker-marketplace.md
@@ -14,22 +14,22 @@ redirect_from:
 
 In this section, you will find all the information about Spryker Marketplace and how to start developing one.
 
-If you are new to Spryker, first see our [Intro to Spryker](/docs/scos/user/intro-to-spryker/intro-to-spryker.html).
+If you are new to Spryker, first see our [Intro to Spryker](/docs/about/all/intro-to-spryker.html).
 
 ## Overview of Spryker Marketplace
 
 To learn what Spryker Marketplace is, read the following documents:
 
-* [Marketplace concept](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-concept.html)
-* [Marketplace personas](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-personas.html)
-* [Back Office for Marketplace Operator](/docs/scos/user/intro-to-spryker/spryker-marketplace/back-office-for-marketplace-operator.html)
-* [Marketplace Storefront](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-storefront.html)
-* [Merchant Portal](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-storefront.html)
+* [Marketplace concept](/docs/about/all/spryker-marketplace/marketplace-concept.html)
+* [Marketplace personas](/docs/about/all/spryker-marketplace/marketplace-personas.html)
+* [Back Office for Marketplace Operator](/docs/about/all/spryker-marketplace/back-office-for-marketplace-operator.html)
+* [Marketplace Storefront](/docs/about/all/spryker-marketplace/marketplace-storefront.html)
+* [Merchant Portal](/docs/about/all/spryker-marketplace/marketplace-storefront.html)
 
 
 ## How do I start with Spryker Marketplace?
 
-For new projects, we provide [B2C](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2c-suite.html) and [B2B Demo Marketplace](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2b-suite.html) templates, which are a great starting point.
+For new projects, we provide [B2C](/docs/about/all/spryker-marketplace/marketplace-b2c-suite.html) and [B2B Demo Marketplace](/docs/about/all/spryker-marketplace/marketplace-b2b-suite.html) templates, which are a great starting point.
 
 Even if you don't need marketplace features at first, but you are going to use them in the future, the Demo Marketplaces are still the best starting point. You can just ignore the marketplace features until you actually want to use them.
 
@@ -41,4 +41,4 @@ To upgrade to marketplace from a regular Demo Shop, follow [How-To: Upgrade Spry
 
 ## Read next
 
-[Marketplace concept](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-concept.html)
+[Marketplace concept](/docs/about/all/spryker-marketplace/marketplace-concept.html)
diff --git a/docs/about/all/support/getting-support.md b/docs/about/all/support/getting-support.md
index 2f8e70155e3..5ae5182a38b 100644
--- a/docs/about/all/support/getting-support.md
+++ b/docs/about/all/support/getting-support.md
@@ -11,18 +11,18 @@ redirect_from:
 
 related:
   - title: How to use the Support Portal
-    link: docs/scos/user/intro-to-spryker/support/how-to-use-the-support-portal.html
+    link: docs/about/all/support/how-to-use-the-support-portal.html
   - title: How Spryker Support works
-    link: docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html
+    link: docs/about/all/support/how-spryker-support-works.html
   - title: Getting the most out of Spryker Support
-    link: docs/scos/user/intro-to-spryker/support/getting-the-most-out-of-spryker-support.html
+    link: docs/about/all/support/getting-the-most-out-of-spryker-support.html
 
 ---
 
-If you need technical help for issues that can't be resolved with the help of the docs, you can always count on our support team. If your case is not an emergency, take the time to learn [How Spryker Support works](/docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html) and [how to get the most out of Spryker Support](/docs/scos/user/intro-to-spryker/support/getting-the-most-out-of-spryker-support.html). Both documents give valuable insights into the inner workings of Spryker Support and let you help us to provide an excellent support experience for you.
+If you need technical help for issues that can't be resolved with the help of the docs, you can always count on our support team. If your case is not an emergency, take the time to learn [How Spryker Support works](/docs/about/all/support/how-spryker-support-works.html) and [how to get the most out of Spryker Support](/docs/about/all/support/getting-the-most-out-of-spryker-support.html). Both documents give valuable insights into the inner workings of Spryker Support and let you help us to provide an excellent support experience for you.
 
 
 Depending on the types of issues, there are several ways to report them and request support from us:
 * For bug reports and product issues, feel free to create a case for our support team at the [support portal](https://support.spryker.com).
-* For security-related issues, follow the instructions at [Security Support](/docs/scos/user/intro-to-spryker/support/handling-security-issues.html).
+* For security-related issues, follow the instructions at [Security Support](/docs/about/all/support/handling-security-issues.html).
 * For general discussions of Spryker-related questions, join the Spryker community at [CommerceQuest](https://commercequest.space/).
diff --git a/docs/about/all/support/getting-the-most-out-of-spryker-support.md b/docs/about/all/support/getting-the-most-out-of-spryker-support.md
index e84bf0513cc..a7fae3d82f0 100644
--- a/docs/about/all/support/getting-the-most-out-of-spryker-support.md
+++ b/docs/about/all/support/getting-the-most-out-of-spryker-support.md
@@ -8,16 +8,16 @@ redirect_from:
 - /docs/scos/user/intro-to-spryker/support/getting-the-most-out-of-spryker-support.html
 related:
   - title: How Spryker Support works
-    link: docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html
+    link: docs/about/all/support/how-spryker-support-works.html
   - title: How to use the Support Portal
-    link: docs/scos/user/intro-to-spryker/support/how-to-use-the-support-portal.html
+    link: docs/about/all/support/how-to-use-the-support-portal.html
 ---
 
 We are very proud to have outstanding First Response Times (currently, they average around 35 minutes in busy weeks). However, a first response seldom immediately includes the solution to your problem. So how can we shorten Case Resolution Time?
 
-There are many of factors influencing [case resolution time](/docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html#case-resolution-time). Some of them are determined by internal Spryker factor conditions, like availability of developer and engineering resources; others are external. One of these external factors is the question whether a case is immediately actionable. If a case contains all the information necessary for us to get working on it, it will be solved faster. How can you help us in this regard? Let's take a look at the form that is used to open a case with us:
+There are many of factors influencing [case resolution time](/docs/about/all/support/how-spryker-support-works.html#case-resolution-time). Some of them are determined by internal Spryker factor conditions, like availability of developer and engineering resources; others are external. One of these external factors is the question whether a case is immediately actionable. If a case contains all the information necessary for us to get working on it, it will be solved faster. How can you help us in this regard? Let's take a look at the form that is used to open a case with us:
 
-We are very proud to have outstanding [first response times](/docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html#first-response-time) (currently they average at around 35 Minutes in busy weeks), however, a first response does seldom immediately include the solution to your problem. So how can we shorten case resolution Time?
+We are very proud to have outstanding [first response times](/docs/about/all/support/how-spryker-support-works.html#first-response-time) (currently they average at around 35 Minutes in busy weeks), however, a first response does seldom immediately include the solution to your problem. So how can we shorten case resolution Time?
 
 ## Whitelist our email addresses
 
diff --git a/docs/about/all/support/how-spryker-support-works.md b/docs/about/all/support/how-spryker-support-works.md
index 535588d6d3a..713b44d50d4 100644
--- a/docs/about/all/support/how-spryker-support-works.md
+++ b/docs/about/all/support/how-spryker-support-works.md
@@ -8,9 +8,9 @@ redirect_from:
 - /docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html
 related:
   - title: Getting the most out of Spryker Support
-    link: docs/scos/user/intro-to-spryker/support/getting-the-most-out-of-spryker-support.html
+    link: docs/about/all/support/getting-the-most-out-of-spryker-support.html
   - title: How to use the Support Portal
-    link: docs/scos/user/intro-to-spryker/support/how-to-use-the-support-portal.html
+    link: docs/about/all/support/how-to-use-the-support-portal.html
 ---
 
 We believe that you can only deliver great support when you are on the same page as your customers. Being transparent about our performance metrics and processes is a necessary step towards that.
diff --git a/docs/about/all/support/prioritzing-support-cases.md b/docs/about/all/support/prioritzing-support-cases.md
index e7d27e2b428..bf9a6083dfe 100644
--- a/docs/about/all/support/prioritzing-support-cases.md
+++ b/docs/about/all/support/prioritzing-support-cases.md
@@ -18,7 +18,7 @@ While we are trying to solve cases on time, we need to triage and prioritize cas
 
 {% info_block infoBox "" %}
 
-Prioritization is only one aspect that influences how fast your case is solved. To learn important tips about what you can do to speed up resolution times, see [Getting the most out of Spryker Support](/docs/scos/user/intro-to-spryker/support/getting-the-most-out-of-spryker-support.html).
+Prioritization is only one aspect that influences how fast your case is solved. To learn important tips about what you can do to speed up resolution times, see [Getting the most out of Spryker Support](/docs/about/all/support/getting-the-most-out-of-spryker-support.html).
 
 {% endinfo_block %}
 
diff --git a/docs/about/all/support/share-secrets-with-the-spryker-support-team.md b/docs/about/all/support/share-secrets-with-the-spryker-support-team.md
index e76cf940037..2de03d7f76f 100644
--- a/docs/about/all/support/share-secrets-with-the-spryker-support-team.md
+++ b/docs/about/all/support/share-secrets-with-the-spryker-support-team.md
@@ -9,7 +9,7 @@ redirect_from:
 - /docs/scos/user/intro-to-spryker/support/share-secrets-with-the-spryker-support-team.html
 ---
 
-This document explains how you can securely share secrets or credentials with the [Spryker Support Team](/docs/scos/user/intro-to-spryker/support/getting-support.html). In general, the safest way to share secrets is not to share them, but if the situation demands it, we ask you to share secrets only the way described in this document.
+This document explains how you can securely share secrets or credentials with the [Spryker Support Team](/docs/about/all/support/getting-support.html). In general, the safest way to share secrets is not to share them, but if the situation demands it, we ask you to share secrets only the way described in this document.
 
 {% info_block warningBox %}
 
diff --git a/docs/about/all/support/support-case-escalations.md b/docs/about/all/support/support-case-escalations.md
index bf15e9a459e..223ee812028 100644
--- a/docs/about/all/support/support-case-escalations.md
+++ b/docs/about/all/support/support-case-escalations.md
@@ -27,7 +27,7 @@ In Support, we acknowledge that we cannot always produce a satisfying result. We
 
 ### Initiate an escalation
 
-Creating an [Emergency Case](/docs/scos/user/intro-to-spryker/support/how-to-use-the-support-portal.html#emergencies) always starts an escalation. You will receive an email notifying you that an escalation has been started.
+Creating an [Emergency Case](/docs/about/all/support/how-to-use-the-support-portal.html#emergencies) always starts an escalation. You will receive an email notifying you that an escalation has been started.
 
 ### The escalation process
 
diff --git a/docs/about/all/support/understanding-slas.md b/docs/about/all/support/understanding-slas.md
index 15a73208358..e410169bc45 100644
--- a/docs/about/all/support/understanding-slas.md
+++ b/docs/about/all/support/understanding-slas.md
@@ -26,14 +26,14 @@ At Spryker people from around the world work together to provide outstanding pro
 If you discover a problem with Spryker Software, please let us know immediately. Avoid ignoring a problem that you find, or work around it without reporting it to us. Not only would this prevent us from making our software better, but your workaround might not be maintainable and could cause you problems with upgradability or reduce your flexibility sometime in the future.
 
 ### Bring the right information
-Ensure that every case you open with us includes the information we need to work on it. To learn what info matters most, see [Getting the most out of Spryker Support](/docs/scos/user/intro-to-spryker/support/getting-the-most-out-of-spryker-support.html).
+Ensure that every case you open with us includes the information we need to work on it. To learn what info matters most, see [Getting the most out of Spryker Support](/docs/about/all/support/getting-the-most-out-of-spryker-support.html).
 
 ### Assess business impact realistically
-To make sure that we resolve the right cases first, we need to triage and prioritize. You can help us to do this better if you assess and specify the business impact of your problem appropriately. For a more detailed explanation of what business impact is and how priorities work have a look into this [article](/docs/scos/user/intro-to-spryker/support/understanding-ticket-status.html#how-are-bug-tickets-prioritized).
+To make sure that we resolve the right cases first, we need to triage and prioritize. You can help us to do this better if you assess and specify the business impact of your problem appropriately. For a more detailed explanation of what business impact is and how priorities work have a look into this [article](/docs/about/all/support/understanding-ticket-status.html#how-are-bug-tickets-prioritized).
 
 ## What you can expect from us
 
-In our SLAs, we guarantee certain [First Response Times](/docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html#first-response-time).
+In our SLAs, we guarantee certain [First Response Times](/docs/about/all/support/how-spryker-support-works.html#first-response-time).
 You can expect us to react to your cases within the time that is specified in your SLA. While we work to resolve high-priority issues as fast as possible, we do not and cannot guarantee resolution times for the issues you open with us because of the breadth of cases we offer to work on. Guaranteeing resolution times would make it necessary for us to make the definition of the cases we accept stricter, which ultimately will makes it harder and more bureaucratic for you to work with us.
 
 ### Infrastructure support
diff --git a/docs/about/all/support/using-the-support-portal.md b/docs/about/all/support/using-the-support-portal.md
index 96234d89d2f..93b242878f7 100644
--- a/docs/about/all/support/using-the-support-portal.md
+++ b/docs/about/all/support/using-the-support-portal.md
@@ -8,9 +8,9 @@ redirect_from:
 - /docs/scos/user/intro-to-spryker/support/how-to-use-the-support-portal.html
 related:
   - title: How Spryker Support works
-    link: docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html
+    link: docs/about/all/support/how-spryker-support-works.html
   - title: Getting the most out of Spryker Support
-    link: docs/scos/user/intro-to-spryker/support/getting-the-most-out-of-spryker-support.html
+    link: docs/about/all/support/getting-the-most-out-of-spryker-support.html
 ---
 
 This document describes how to use the support portal to create and manage your cases.
@@ -22,7 +22,7 @@ You can log in to the [support portal](https://support.spryker.com) by using the
 
 ## Create new cases
 
-To create new cases, you can use the **Create a case** drop-down menu and select the respective case type, or click on the case type on the landing page. When creating cases, make use of the recommendations explained in [Share secrets with the Spryker Support Team](/docs/scos/user/intro-to-spryker/support/share-secrets-with-the-spryker-support-team.html).
+To create new cases, you can use the **Create a case** drop-down menu and select the respective case type, or click on the case type on the landing page. When creating cases, make use of the recommendations explained in [Share secrets with the Spryker Support Team](/docs/about/all/support/share-secrets-with-the-spryker-support-team.html).
 
 ### Questions
 
@@ -34,7 +34,7 @@ Problems can be reports suspecting a bug or issues with our hosting. Please make
 
 ### Emergencies
 
-Emergencies are reserved for problems that have significant business impact now or very soon. Emergency cases regularly start an [escalation](/docs/scos/user/intro-to-spryker/support/escalations.html). Please do not use this case type to simply try to speed up requests or problem reports. Emergencies need to be associated with significant risk or business impact, like revenue, security, or go-lives.
+Emergencies are reserved for problems that have significant business impact now or very soon. Emergency cases regularly start an [escalation](/docs/about/all/support/escalations.html). Please do not use this case type to simply try to speed up requests or problem reports. Emergencies need to be associated with significant risk or business impact, like revenue, security, or go-lives.
 
 ### Platform change requests
 
diff --git a/docs/about/all/supported-browsers.md b/docs/about/all/supported-browsers.md
index a587cc4e603..977d743d158 100644
--- a/docs/about/all/supported-browsers.md
+++ b/docs/about/all/supported-browsers.md
@@ -16,7 +16,7 @@ Spryker Cloud Commerce OS supports the following browsers.
 
 ## Base shop supported browsers
 
-[B2B suite](/docs/scos/user/intro-to-spryker/b2b-suite.html), [B2C suite](/docs/scos/user/intro-to-spryker/b2c-suite.html), and [Master suite](/docs/scos/user/intro-to-spryker/master-suite.html) support the following browsers:
+[B2B suite](/docs/about/all/b2b-suite.html), [B2C suite](/docs/about/all/b2c-suite.html), and [Master suite](/docs/about/all/master-suite.html) support the following browsers:
 
 | DESKTOP: BACK OFFICE AND STOREFRONT | MOBILE: STOREFRONT | TABLET: STOREFRONT |
 | --- | --- | --- |
diff --git a/docs/ca/dev/email-service/email-quota-restrictions.md b/docs/ca/dev/email-service/email-quota-restrictions.md
index 5ae8e798394..21337a0589a 100644
--- a/docs/ca/dev/email-service/email-quota-restrictions.md
+++ b/docs/ca/dev/email-service/email-quota-restrictions.md
@@ -15,4 +15,4 @@ SCCOS non-production email service has the following quotas:
 
 Recipients of emails need to be individually [verified](/docs/ca/dev/verify-email-addresses.html) for non-production systems.
 
-Reach out to [Spryker Support](/docs/scos/user/intro-to-spryker/support/getting-support.html) if these quotas are insufficient to support your use case.
\ No newline at end of file
+Reach out to [Spryker Support](/docs/about/all/support/getting-support.html) if these quotas are insufficient to support your use case.
\ No newline at end of file
diff --git a/docs/ca/dev/environment-provisioning.md b/docs/ca/dev/environment-provisioning.md
index 87e1b951291..8743089837d 100644
--- a/docs/ca/dev/environment-provisioning.md
+++ b/docs/ca/dev/environment-provisioning.md
@@ -99,7 +99,7 @@ Similar to project names, you can't switch between these models after the enviro
 
 The repository is the place where the customer's Spryker application code resides. Spryker supports only GitHub, GitLab, and Bitbucket code hosting services. If the customer code base isn't ready, the Spryker team provisions the environment with the previously chosen Demo Dhop model from the most recent release using GitHub.
 
-GitHub: If the customer uses GitHub, provide a link to the GitHub repository, including a branch and a valid GitHub token. This allows code pipelines to access the repository. Ensure that you securely share the GitHub token according to [Spryker recommendations](/docs/scos/user/intro-to-spryker/support/share-secrets-with-the-spryker-support-team.html).
+GitHub: If the customer uses GitHub, provide a link to the GitHub repository, including a branch and a valid GitHub token. This allows code pipelines to access the repository. Ensure that you securely share the GitHub token according to [Spryker recommendations](/docs/about/all/support/share-secrets-with-the-spryker-support-team.html).
 
 GitLab and Bitbucket: Connecting GitLab and Bitbucket repositories directly to pipelines isn't supported. Therefore, we have to enable the codecommit feature during provisioning. Connections with pipelines can be established only after the environment is provisioned. If possible, grant GitLab or Bitbucket access to the Spryker engineer working on this request. If not, we'll use your deploy file along with the Spryker Demo Shop during provisioning. For detailed information about the connection process, see [Connect a GitLab code repository](/docs/ca/dev/connect-a-code-repository.html#connect-a-gitlab-code-repository) section in "Connecting a code repository".
 
diff --git a/docs/ca/dev/performance-testing-in-staging-enivronments.md b/docs/ca/dev/performance-testing-in-staging-enivronments.md
index cb62597822b..e647422d276 100644
--- a/docs/ca/dev/performance-testing-in-staging-enivronments.md
+++ b/docs/ca/dev/performance-testing-in-staging-enivronments.md
@@ -42,8 +42,8 @@ The purpose of this guide is to show you how to integrate Spryker's load testing
 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.
-- [B2C Demo Shop](/docs/scos/user/intro-to-spryker/b2c-suite.html): A starting point for B2C implementations.
+- [B2B Demo Shop](/docs/about/all//b2b-suite.html): A boilerplate for B2B commerce projects.
+- [B2C Demo Shop](/docs/about/all/b2c-suite.html): A starting point for B2C implementations.
 
 If you wish to start with a demo shop that has been pre-configured with the Spryker load testing module, you can use the [Spryker Suite Demo Shop](https://github.com/spryker-shop/suite).
 
diff --git a/docs/ca/dev/preparation-for-going-live.md b/docs/ca/dev/preparation-for-going-live.md
index ffbd7059c5e..791a8030f8b 100644
--- a/docs/ca/dev/preparation-for-going-live.md
+++ b/docs/ca/dev/preparation-for-going-live.md
@@ -50,7 +50,7 @@ After pointing the domain name to your Spryker project, some of your customers m
 
 ### Application
 
-- Upgrade your project's code to the [latest Demo Shop release](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes.html). Or at least upgrade to a release that fully supports the Docker SDK (202009.0 and later).
+- Upgrade your project's code to the [latest Demo Shop release](/docs/about/all/releases/release-notes/release-notes.html). Or at least upgrade to a release that fully supports the Docker SDK (202009.0 and later).
 - Update `spryker/twig` to version 3.15.2 or later because this and later versions have important stability improvements over version 3.15.1.
 - Migrate the project's database to MariaDB.
 - Split the project's Zed endpoints as described in [Integrating separate endpoint bootstraps](/docs/scos/dev/technical-enhancement-integration-guides/integrating-separate-endpoint-bootstraps.html).
@@ -69,9 +69,9 @@ After pointing the domain name to your Spryker project, some of your customers m
   - Apply Spryker [security guidelines](/docs/scos/dev/guidelines/security-guidelines.html).
   - Make sure that you don't have any plain-text passwords, private keys, or API secrets in config files or Git repositories.
   - Minimize the use of personal credentials and choose work-specific accounts based on each environment (production, staging, testing). We highly recommend employing Centralized Credential Management to securely store and manage these credentials.
-  - Install all the [security updates](/docs/scos/user/intro-to-spryker/whats-new/security-updates.html) from all Spryker packages.
+  - Install all the [security updates](/docs/about/all/whats-new/security-updates.html) from all Spryker packages.
   - Install all the security updates from all the external packages. To check if your project modules require security updates, you can use the [Security checker](/docs/scos/dev/guidelines/keeping-a-project-upgradable/upgradability-guidelines/spryker-security-checker.html).
-- Perform compliance and legal checks. To ensure the platform complies with relevant legal and regulatory requirements, especially for international operations, consult your legal team. Make sure to check [Guidelines for GDPR compliance](/docs/scos/user/intro-to-spryker/support/guidelines-for-new-gdpr-rules.html).
+- Perform compliance and legal checks. To ensure the platform complies with relevant legal and regulatory requirements, especially for international operations, consult your legal team. Make sure to check [Guidelines for GDPR compliance](/docs/about/all/support/guidelines-for-new-gdpr-rules.html).
 - Make sure that the Back Office Access Control List (ACL) setup is configured correctly to manage user permissions and access rights within the system's administrative interface. For instructions on how to configure ACL, see [Users and rights overview](/docs/pbc/all/user-management/{{site.version}}/base-shop/user-and-rights-overview.html).
 
 ### Testing
diff --git a/docs/ca/devscu/integrating-code-releases/integrating-code-releases.md b/docs/ca/devscu/integrating-code-releases/integrating-code-releases.md
index b5d78c98fbd..f714bf184ae 100644
--- a/docs/ca/devscu/integrating-code-releases/integrating-code-releases.md
+++ b/docs/ca/devscu/integrating-code-releases/integrating-code-releases.md
@@ -46,4 +46,4 @@ If you see errors in the generated code, do the following:
 1. Double-check if your code follows the upgradability guidelines by [running the Evaluator](/docs/dg/dev/guidelines/keeping-a-project-upgradable/run-the-evaluator-tool.html).
     After fixing the upgradability issues, close the PR with errors and restart the Upgrader to get a new PR.
 2. If you see any quick fixes, try manually correcting the errors.
-3. [Contact us](/docs/scos/user/intro-to-spryker/support/how-to-use-the-support-portal.html) for further assistance. 
+3. [Contact us](/docs/about/all/support/how-to-use-the-support-portal.html) for further assistance. 
diff --git a/docs/ca/devscu/prepare-a-project-for-spryker-code-upgrader.md b/docs/ca/devscu/prepare-a-project-for-spryker-code-upgrader.md
index e0b2783558c..56a57f1d1ed 100644
--- a/docs/ca/devscu/prepare-a-project-for-spryker-code-upgrader.md
+++ b/docs/ca/devscu/prepare-a-project-for-spryker-code-upgrader.md
@@ -42,7 +42,7 @@ The Upgrader supports only projects that run in [cloud environments](/docs/ca/de
 
 For a smooth experience, make sure that your environments meet the minimum technical requirements:
 
-* PHP 8.1+. The Upgrader supports a minimum version of PHP 8.0. However, PHP 8.0 reached end of life in November 2023, so make sure to update PHP to the [recommended version](/docs/scos/user/intro-to-spryker/whats-new/supported-versions-of-php.html). To check if your PHP version is supported, [run the evaluator tool](/docs/dg/dev/guidelines/keeping-a-project-upgradable/run-the-evaluator-tool.html).
+* PHP 8.1+. The Upgrader supports a minimum version of PHP 8.0. However, PHP 8.0 reached end of life in November 2023, so make sure to update PHP to the [recommended version](/docs/about/all/whats-new/supported-versions-of-php.html). To check if your PHP version is supported, [run the evaluator tool](/docs/dg/dev/guidelines/keeping-a-project-upgradable/run-the-evaluator-tool.html).
 * Composer 2.5+
 * Git 2.24+
 * PHPStan 1.9+
diff --git a/docs/dg/dev/acp/acp-overview.md b/docs/dg/dev/acp/acp-overview.md
index e23b9f4cd6b..e6eb62806db 100644
--- a/docs/dg/dev/acp/acp-overview.md
+++ b/docs/dg/dev/acp/acp-overview.md
@@ -36,7 +36,7 @@ The ACP has the following advantages:
 
 ## Installing the ACP catalog
 
-With the Spryker product release [202212.0](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202212.0/release-notes-202212.0.html) the ACP catalog is integrated into the Back Office by default, but not registered with ACP yet. 
+With the Spryker product release [202212.0](/docs/about/all/releases/release-notes/release-notes-202212.0/release-notes-202212.0.html) the ACP catalog is integrated into the Back Office by default, but not registered with ACP yet. 
 
 You can access the ACP catalog only if you are a SCCOS customer and have additionally been enabled for ACP, which means that your SCCOS is properly set up and registered with the ACP. Check [ACP installation](/docs/acp/user/app-composition-platform-installation.html) for details on how to install and enable the ACP catalog for your version of SCCOS.
 
diff --git a/docs/dg/dev/acp/app-composition-platform-installation.md b/docs/dg/dev/acp/app-composition-platform-installation.md
index 36d6f3793f3..2163ed99fa0 100644
--- a/docs/dg/dev/acp/app-composition-platform-installation.md
+++ b/docs/dg/dev/acp/app-composition-platform-installation.md
@@ -39,13 +39,13 @@ The actions and level of effort required to make your project ACP-ready may vary
 
 To make your project ACP-ready, different update steps are necessary depending on the template version on which your project was started:
 
-- SCCOS product release [202211.0](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202211.0/release-notes-202211.0.html) includes a basic ACP setup. All ACP modules (apps and platform) requiere updates.
+- SCCOS product release [202211.0](/docs/about/all/releases/release-notes/release-notes-202211.0/release-notes-202211.0.html) includes a basic ACP setup. All ACP modules (apps and platform) requiere updates.
 
-- SCCOS product release [202311.0](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202311.0/release-notes-202311.0.html) or later: you can skip the configuration step described in this document.
+- SCCOS product release [202311.0](/docs/about/all/releases/release-notes/release-notes-202311.0/release-notes-202311.0.html) or later: you can skip the configuration step described in this document.
 
 {% info_block infoBox "Product version earlier than 202311.0" %}
 
-If you were onboarded with a version older than product release [202211.0](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202211.0/release-notes-202211.0.html), [contact us](https://support.spryker.com/). 
+If you were onboarded with a version older than product release [202211.0](/docs/about/all/releases/release-notes/release-notes-202211.0/release-notes-202211.0.html), [contact us](https://support.spryker.com/). 
 
 {% endinfo_block %}
 
@@ -55,7 +55,7 @@ To get your project ACP-ready, it is important to make sure that your project mo
 
 #### ACP modules
 
-Starting with the Spryker product release [202311.0](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202311.0/release-notes-202311.0.html), the ACP catalog is included by default in the Spryker Cloud Commerc OS product. However, you should still make sure that your Spryker project uses the latest versions of the following modules:
+Starting with the Spryker product release [202311.0](/docs/about/all/releases/release-notes/release-notes-202311.0/release-notes-202311.0.html), the ACP catalog is included by default in the Spryker Cloud Commerc OS product. However, you should still make sure that your Spryker project uses the latest versions of the following modules:
 
 * `spryker/app-catalog-gui: ^1.4.1` or later
 * `spryker/message-broker: ^1.10.0` or later
@@ -79,7 +79,7 @@ For each app you wish to use, ensure that you have the latest app-related SCOS m
 
 {% info_block infoBox "This step can be omitted for Product version later than 202311.0" %}
 
-If your version is based on product release [202311.0](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes-202311.0/release-notes-202311.0.html) or later, you can skip this section. 
+If your version is based on product release [202311.0](/docs/about/all/releases/release-notes/release-notes-202311.0/release-notes-202311.0.html) or later, you can skip this section. 
 
 {% endinfo_block %}
 
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 ebbd9c3f34f..0c86722113a 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
@@ -54,7 +54,7 @@ Usually, you need to run `composer update` to get Spryker Core updates, because
 
 {% info_block infoBox %}
 
-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.
+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/about/all/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/dg/dev/troubleshooting/troubleshooting-general-technical-issues/troubleshooting-general-technical-issues.html).
 
diff --git a/docs/dg/dev/backend-development/cronjobs/cronjobs.md b/docs/dg/dev/backend-development/cronjobs/cronjobs.md
index 4a53511a22f..82831ea4ce3 100644
--- a/docs/dg/dev/backend-development/cronjobs/cronjobs.md
+++ b/docs/dg/dev/backend-development/cronjobs/cronjobs.md
@@ -35,7 +35,7 @@ Basic module schema:
 
 ## Cronjob schedulers
 
-[Demo Shops](/docs/scos/user/intro-to-spryker/intro-to-spryker.html#spryker-b2bb2c-demo-shops) are shipped with Jenkins as a default scheduler. Jenkins manages running and monitoring jobs. If you migrated to another scheduler and want to migrate back to Jenkins, see [Migrate to Jenkins](/docs/dg/dev/backend-development/cronjobs/migrate-to-jenkins.html).
+[Demo Shops](/docs/about/all/intro-to-spryker.html#spryker-b2bb2c-demo-shops) are shipped with Jenkins as a default scheduler. Jenkins manages running and monitoring jobs. If you migrated to another scheduler and want to migrate back to Jenkins, see [Migrate to Jenkins](/docs/dg/dev/backend-development/cronjobs/migrate-to-jenkins.html).
 
 If your project has very specific requirements, you can [create a custom scheduler](/docs/dg/dev/backend-development/cronjobs/create-a-custom-scheduler.html).
 
diff --git a/docs/dg/dev/code-contribution-guide.md b/docs/dg/dev/code-contribution-guide.md
index 714359d347d..0e78e89cf80 100644
--- a/docs/dg/dev/code-contribution-guide.md
+++ b/docs/dg/dev/code-contribution-guide.md
@@ -49,4 +49,4 @@ If you create a PR and feel that the issue is important, [contact our support](h
 ---
 **See also:**
 
-[Contribute to documentation](/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/contribute-to-the-documentation.html)
+[Contribute to documentation](/docs/about/all/contribute-to-the-documentation/contribute-to-the-documentation.html)
diff --git a/docs/dg/dev/data-import/202212.0/data-import-optimization-guidelines.md b/docs/dg/dev/data-import/202212.0/data-import-optimization-guidelines.md
index d257fb7fe8b..522dce81cb0 100644
--- a/docs/dg/dev/data-import/202212.0/data-import-optimization-guidelines.md
+++ b/docs/dg/dev/data-import/202212.0/data-import-optimization-guidelines.md
@@ -123,7 +123,7 @@ Let's say you already started to work with the batch operation, one of the chall
 
 ### Database vendor approach
 
-Spryker supports PostgreSQL, MySQL, and MariaDB. When working with databases, it's good to know their related features. For example, one of the great features we like is [CTE](https://www.postgresql.org/docs/9.1/queries-with.html). If you are inserting or updating big amounts of data, like millions of millions, use CTE as a replaceable for multiple inserts and updates. You can find examples of implementations in our [Demo Shops](/docs/scos/user/intro-to-spryker/intro-to-spryker.html#spryker-b2bb2c-demo-shops).
+Spryker supports PostgreSQL, MySQL, and MariaDB. When working with databases, it's good to know their related features. For example, one of the great features we like is [CTE](https://www.postgresql.org/docs/9.1/queries-with.html). If you are inserting or updating big amounts of data, like millions of millions, use CTE as a replaceable for multiple inserts and updates. You can find examples of implementations in our [Demo Shops](/docs/about/all/intro-to-spryker.html#spryker-b2bb2c-demo-shops).
 
 ## Rules for Publish and Synchronize
 
diff --git a/docs/dg/dev/data-import/202307.0/data-import-optimization-guidelines.md b/docs/dg/dev/data-import/202307.0/data-import-optimization-guidelines.md
index c01435646e3..2b2704acecc 100644
--- a/docs/dg/dev/data-import/202307.0/data-import-optimization-guidelines.md
+++ b/docs/dg/dev/data-import/202307.0/data-import-optimization-guidelines.md
@@ -123,7 +123,7 @@ Let's say you already started to work with the batch operation, one of the chall
 
 ### Database vendor approach
 
-Spryker supports PostgreSQL, MySQL, and MariaDB. When working with databases, it's good to know their related features. For example, one of the great features we like is [CTE](https://www.postgresql.org/docs/9.1/queries-with.html). If you are inserting or updating big amounts of data, like millions of millions, use CTE as a replaceable for multiple inserts and updates. You can find examples of implementations in our [Demo Shops](/docs/scos/user/intro-to-spryker/intro-to-spryker.html#spryker-b2bb2c-demo-shops).
+Spryker supports PostgreSQL, MySQL, and MariaDB. When working with databases, it's good to know their related features. For example, one of the great features we like is [CTE](https://www.postgresql.org/docs/9.1/queries-with.html). If you are inserting or updating big amounts of data, like millions of millions, use CTE as a replaceable for multiple inserts and updates. You can find examples of implementations in our [Demo Shops](/docs/about/all/intro-to-spryker.html#spryker-b2bb2c-demo-shops).
 
 ## Rules for Publish and Synchronize
 
diff --git a/docs/dg/dev/data-import/202311.0/data-import-optimization-guidelines.md b/docs/dg/dev/data-import/202311.0/data-import-optimization-guidelines.md
index e46e7388af6..c590aaf49f0 100644
--- a/docs/dg/dev/data-import/202311.0/data-import-optimization-guidelines.md
+++ b/docs/dg/dev/data-import/202311.0/data-import-optimization-guidelines.md
@@ -116,7 +116,7 @@ Let's say you already started to work with the batch operation, one of the chall
 
 ### Database vendor approach
 
-Spryker supports PostgreSQL, MySQL, and MariaDB. When working with databases, it's good to know their related features. For example, one of the great features we like is [CTE](https://www.postgresql.org/docs/9.1/queries-with.html). If you are inserting or updating big amounts of data, like millions of millions, use CTE as a replaceable for multiple inserts and updates. You can find examples of implementations in our [Demo Shops](/docs/scos/user/intro-to-spryker/intro-to-spryker.html#spryker-b2bb2c-demo-shops).
+Spryker supports PostgreSQL, MySQL, and MariaDB. When working with databases, it's good to know their related features. For example, one of the great features we like is [CTE](https://www.postgresql.org/docs/9.1/queries-with.html). If you are inserting or updating big amounts of data, like millions of millions, use CTE as a replaceable for multiple inserts and updates. You can find examples of implementations in our [Demo Shops](/docs/about/all/intro-to-spryker.html#spryker-b2bb2c-demo-shops).
 
 ## Rules for Publish and Synchronize
 
diff --git a/docs/dg/dev/development-getting-started-guide.md b/docs/dg/dev/development-getting-started-guide.md
index dbaa2ec473d..013df94cee7 100644
--- a/docs/dg/dev/development-getting-started-guide.md
+++ b/docs/dg/dev/development-getting-started-guide.md
@@ -19,10 +19,10 @@ Spryker Demo Shops are a good starting point for any project. They are shipped w
 
 You can choose from the following options:
 
-* [B2C Demo Shop](/docs/scos/user/intro-to-spryker/b2c-suite.html)
-* [B2B Demo Shop](/docs/scos/user/intro-to-spryker//b2b-suite.html)
-* [Marketplace B2C Demo Shop](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2c-suite.html)
-* [Marketplace B2B Demo Shop](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2b-suite.html)
+* [B2C Demo Shop](/docs/about/all/b2c-suite.html)
+* [B2B Demo Shop](/docs/about/all//b2b-suite.html)
+* [Marketplace B2C Demo Shop](/docs/about/all/spryker-marketplace/marketplace-b2c-suite.html)
+* [Marketplace B2B Demo Shop](/docs/about/all/spryker-marketplace/marketplace-b2b-suite.html)
 
 You can run Spryker on MacOS, Linux, and Windows with WSL1 or WSL2. For installation instructions, see [Set up Spryker locally](/docs/dg/dev/set-up-spryker-locally/set-up-spryker-locally.html).
 
@@ -49,7 +49,7 @@ For more information about deploy files, see [Deploy file](/docs/dg/dev/sdks/the
 
 A Spryker module is a single-function unit that has well-defined dependencies and can be updated independently. [Composer](/docs/dg/dev/set-up-spryker-locally/manage-dependencies-with-composer.html) is used for installing and managing module dependencies.
 
-To define your strategy when implementing updates, learn about our [module and feature release process](/docs/scos/user/intro-to-spryker/spryker-release-process.html).
+To define your strategy when implementing updates, learn about our [module and feature release process](/docs/about/all/spryker-release-process.html).
 
 
 You will use the following commands to manage modules with Composer:
diff --git a/docs/dg/dev/frontend-development/202212.0/yves/atomic-frontend/frontend-customization-example-b2b-product-details-page.md b/docs/dg/dev/frontend-development/202212.0/yves/atomic-frontend/frontend-customization-example-b2b-product-details-page.md
index 8481678e966..87a61fcfb84 100644
--- a/docs/dg/dev/frontend-development/202212.0/yves/atomic-frontend/frontend-customization-example-b2b-product-details-page.md
+++ b/docs/dg/dev/frontend-development/202212.0/yves/atomic-frontend/frontend-customization-example-b2b-product-details-page.md
@@ -22,7 +22,7 @@ related:
     link: docs/dg/dev/frontend-development/page.version/yves/atomic-frontend/frontend-customization-example-b2c-product-details-page.html
 ---
 
-In Spryker, front-end elements have dedicated SCSS styles. To show you how to customize the Spryker front end, we broke down the *Product Details* page from our [B2B Demo Shop](/docs/scos/user/intro-to-spryker/b2b-suite.html#b2b-demo-shop) into separate elements with their respective style files. To customize a particular element, you adjust the code in the respective style file.
+In Spryker, front-end elements have dedicated SCSS styles. To show you how to customize the Spryker front end, we broke down the *Product Details* page from our [B2B Demo Shop](/docs/about/all/b2b-suite.html#b2b-demo-shop) into separate elements with their respective style files. To customize a particular element, you adjust the code in the respective style file.
 
 You can see the [full version of this page](https://www.de.b2b.demo-spryker.com/en/soennecken-permanentmarker-4mm-rundspitze-M22663) in our B2B Demo Shop.
 
diff --git a/docs/dg/dev/frontend-development/202212.0/yves/atomic-frontend/frontend-customization-example-b2c-product-details-page.md b/docs/dg/dev/frontend-development/202212.0/yves/atomic-frontend/frontend-customization-example-b2c-product-details-page.md
index d872e5b0bef..a0d12865cfa 100644
--- a/docs/dg/dev/frontend-development/202212.0/yves/atomic-frontend/frontend-customization-example-b2c-product-details-page.md
+++ b/docs/dg/dev/frontend-development/202212.0/yves/atomic-frontend/frontend-customization-example-b2c-product-details-page.md
@@ -22,7 +22,7 @@ related:
     link: docs/dg/dev/frontend-development/page.version/yves/atomic-frontend/frontend-customization-example-b2b-product-details-page.html
 ---
 
-In Spryker, front-end elements have dedicated SCSS styles. To show you how to customize the Spryker front end, we broke down the *Product Details* page from our [B2C Demo Shop](/docs/scos/user/intro-to-spryker/b2c-suite.html#b2c-demo-shop) into separate elements with their respective style files. To customize a particular element, you adjust the code in the respective style file.
+In Spryker, front-end elements have dedicated SCSS styles. To show you how to customize the Spryker front end, we broke down the *Product Details* page from our [B2C Demo Shop](/docs/about/all/b2c-suite.html#b2c-demo-shop) into separate elements with their respective style files. To customize a particular element, you adjust the code in the respective style file.
 
 You can see the [full version of this page](https://www.de.b2c.demo-spryker.com/en/acer-aspire-s7-134) in our B2C Demo Shop.
 
diff --git a/docs/dg/dev/frontend-development/202307.0/yves/atomic-frontend/frontend-customization-example-b2b-product-details-page.md b/docs/dg/dev/frontend-development/202307.0/yves/atomic-frontend/frontend-customization-example-b2b-product-details-page.md
index f588841cc10..57c20b423ab 100644
--- a/docs/dg/dev/frontend-development/202307.0/yves/atomic-frontend/frontend-customization-example-b2b-product-details-page.md
+++ b/docs/dg/dev/frontend-development/202307.0/yves/atomic-frontend/frontend-customization-example-b2b-product-details-page.md
@@ -22,7 +22,7 @@ related:
     link: docs/dg/dev/frontend-development/page.version/yves/atomic-frontend/frontend-customization-example-b2c-product-details-page.html
 ---
 
-In Spryker, front-end elements have dedicated SCSS styles. To show you how to customize the Spryker front end, we broke down the *Product Details* page from our [B2B Demo Shop](/docs/scos/user/intro-to-spryker/b2b-suite.html#b2b-demo-shop) into separate elements with their respective style files. To customize a particular element, you adjust the code in the respective style file.
+In Spryker, front-end elements have dedicated SCSS styles. To show you how to customize the Spryker front end, we broke down the *Product Details* page from our [B2B Demo Shop](/docs/about/all/b2b-suite.html#b2b-demo-shop) into separate elements with their respective style files. To customize a particular element, you adjust the code in the respective style file.
 
 You can see the [full version of this page](https://www.de.b2b.demo-spryker.com/en/soennecken-permanentmarker-4mm-rundspitze-M22663) in our B2B Demo Shop.
 
diff --git a/docs/dg/dev/frontend-development/202307.0/yves/atomic-frontend/frontend-customization-example-b2c-product-details-page.md b/docs/dg/dev/frontend-development/202307.0/yves/atomic-frontend/frontend-customization-example-b2c-product-details-page.md
index 1f57fee5e4a..a15cdbd47fa 100644
--- a/docs/dg/dev/frontend-development/202307.0/yves/atomic-frontend/frontend-customization-example-b2c-product-details-page.md
+++ b/docs/dg/dev/frontend-development/202307.0/yves/atomic-frontend/frontend-customization-example-b2c-product-details-page.md
@@ -22,7 +22,7 @@ related:
     link: docs/dg/dev/frontend-development/page.version/yves/atomic-frontend/frontend-customization-example-b2b-product-details-page.html
 ---
 
-In Spryker, front-end elements have dedicated SCSS styles. To show you how to customize the Spryker front end, we broke down the *Product Details* page from our [B2C Demo Shop](/docs/scos/user/intro-to-spryker/b2c-suite.html#b2c-demo-shop) into separate elements with their respective style files. To customize a particular element, you adjust the code in the respective style file.
+In Spryker, front-end elements have dedicated SCSS styles. To show you how to customize the Spryker front end, we broke down the *Product Details* page from our [B2C Demo Shop](/docs/about/all/b2c-suite.html#b2c-demo-shop) into separate elements with their respective style files. To customize a particular element, you adjust the code in the respective style file.
 
 You can see the [full version of this page](https://www.de.b2c.demo-spryker.com/en/acer-aspire-s7-134) in our B2C Demo Shop.
 
diff --git a/docs/dg/dev/frontend-development/202311.0/yves/atomic-frontend/frontend-customization-example-b2b-product-details-page.md b/docs/dg/dev/frontend-development/202311.0/yves/atomic-frontend/frontend-customization-example-b2b-product-details-page.md
index 6ad73af1237..1e9b73f5579 100644
--- a/docs/dg/dev/frontend-development/202311.0/yves/atomic-frontend/frontend-customization-example-b2b-product-details-page.md
+++ b/docs/dg/dev/frontend-development/202311.0/yves/atomic-frontend/frontend-customization-example-b2b-product-details-page.md
@@ -15,7 +15,7 @@ related:
     link: docs/dg/dev/frontend-development/page.version/yves/atomic-frontend/frontend-customization-example-b2c-product-details-page.html
 ---
 
-In Spryker, front-end elements have dedicated SCSS styles. To show you how to customize the Spryker front end, we broke down the *Product Details* page from our [B2B Demo Shop](/docs/scos/user/intro-to-spryker/b2b-suite.html#b2b-demo-shop) into separate elements with their respective style files. To customize a particular element, you adjust the code in the respective style file.
+In Spryker, front-end elements have dedicated SCSS styles. To show you how to customize the Spryker front end, we broke down the *Product Details* page from our [B2B Demo Shop](/docs/about/all/b2b-suite.html#b2b-demo-shop) into separate elements with their respective style files. To customize a particular element, you adjust the code in the respective style file.
 
 You can see the [full version of this page](https://www.de.b2b.demo-spryker.com/en/soennecken-permanentmarker-4mm-rundspitze-M22663) in our B2B Demo Shop.
 
diff --git a/docs/dg/dev/frontend-development/202311.0/yves/atomic-frontend/frontend-customization-example-b2c-product-details-page.md b/docs/dg/dev/frontend-development/202311.0/yves/atomic-frontend/frontend-customization-example-b2c-product-details-page.md
index ef4313f4570..490123e9d58 100644
--- a/docs/dg/dev/frontend-development/202311.0/yves/atomic-frontend/frontend-customization-example-b2c-product-details-page.md
+++ b/docs/dg/dev/frontend-development/202311.0/yves/atomic-frontend/frontend-customization-example-b2c-product-details-page.md
@@ -15,7 +15,7 @@ related:
     link: docs/dg/dev/frontend-development/page.version/yves/atomic-frontend/frontend-customization-example-b2b-product-details-page.html
 ---
 
-In Spryker, front-end elements have dedicated SCSS styles. To show you how to customize the Spryker front end, we broke down the *Product Details* page from our [B2C Demo Shop](/docs/scos/user/intro-to-spryker/b2c-suite.html#b2c-demo-shop) into separate elements with their respective style files. To customize a particular element, you adjust the code in the respective style file.
+In Spryker, front-end elements have dedicated SCSS styles. To show you how to customize the Spryker front end, we broke down the *Product Details* page from our [B2C Demo Shop](/docs/about/all/b2c-suite.html#b2c-demo-shop) into separate elements with their respective style files. To customize a particular element, you adjust the code in the respective style file.
 
 You can see the [full version of this page](https://www.de.b2c.demo-spryker.com/en/acer-aspire-s7-134) in our B2C Demo Shop.
 
diff --git a/docs/dg/dev/glue-api/202212.0/configure-the-included-section.md b/docs/dg/dev/glue-api/202212.0/configure-the-included-section.md
index b45c8ff6c01..dc500c2d2d7 100644
--- a/docs/dg/dev/glue-api/202212.0/configure-the-included-section.md
+++ b/docs/dg/dev/glue-api/202212.0/configure-the-included-section.md
@@ -28,7 +28,7 @@ You can decide whether Glue REST API includes the sections in all responses by d
 |**Enabled** | The **included** and **relationships** sections contain only the resources whose names were passed in the query string (resource `concrete-product-image-sets` per the example). | The included section contains all the included resources (if any). |
 |**Disabled** | The response does not contain the included section with related resources. |  The included section contains all the included resources (if any).|
 
-By default, the option is enabled on the Spryker Core level but disabled on the project level in all [Spryker Demo Shops](/docs/scos/user/intro-to-spryker/intro-to-spryker.html#spryker-b2bb2c-demo-shops) (B2B Demo Shop, B2C Demo Shop and Master Shop Suite).
+By default, the option is enabled on the Spryker Core level but disabled on the project level in all [Spryker Demo Shops](/docs/about/all/intro-to-spryker.html#spryker-b2bb2c-demo-shops) (B2B Demo Shop, B2C Demo Shop and Master Shop Suite).
 
 {% info_block infoBox %}
 
diff --git a/docs/dg/dev/glue-api/202212.0/glue-api-tutorials/extend-a-rest-api-resource.md b/docs/dg/dev/glue-api/202212.0/glue-api-tutorials/extend-a-rest-api-resource.md
index 275204f699a..53aec1339ee 100644
--- a/docs/dg/dev/glue-api/202212.0/glue-api-tutorials/extend-a-rest-api-resource.md
+++ b/docs/dg/dev/glue-api/202212.0/glue-api-tutorials/extend-a-rest-api-resource.md
@@ -46,7 +46,7 @@ The following guide relies on your knowledge of the structure of the Glue REST A
 
 {% info_block infoBox %}
 
-If you have a development virtual machine with the [B2C Demo Shop](/docs/scos/user/intro-to-spryker/intro-to-spryker.html#spryker-b2bb2c-demo-shops) installed, all the required components are available out of the box.
+If you have a development virtual machine with the [B2C Demo Shop](/docs/about/all/intro-to-spryker.html#spryker-b2bb2c-demo-shops) installed, all the required components are available out of the box.
 
 Assume that you modify the product storage data to match your product requirements—for example, you add the `manufacturerCountry` field to the product data not as an attribute but as another field in the database.
 
diff --git a/docs/dg/dev/glue-api/202212.0/old-glue-infrastructure/glue-rest-api.md b/docs/dg/dev/glue-api/202212.0/old-glue-infrastructure/glue-rest-api.md
index aec364ddc2a..5e143c8dfb9 100644
--- a/docs/dg/dev/glue-api/202212.0/old-glue-infrastructure/glue-rest-api.md
+++ b/docs/dg/dev/glue-api/202212.0/old-glue-infrastructure/glue-rest-api.md
@@ -48,7 +48,7 @@ For more details, see REST API reference:
 
 To help you understand possible use cases, we provide a sample app as an exemplary implementation (which is not a starting point for development). It can coexist with a shop as a second touchpoint in the project. From a technological perspective, it is based on our customers' interests. The app is single-page application based on a React JS library.
 
-It delivers a full customer experience from browsing the catalog to placing an order. The application helps you understand how you can use the predefined APIs to create a B2C user experience. As an example, the full power of Elasticsearch, which is already present in our [B2B](/docs/scos/user/intro-to-spryker/b2b-suite.html) and [B2C Demo Shops](/docs/scos/user/intro-to-spryker/b2c-suite.html), is leveraged through dedicated endpoints to deliver catalog search functionality with autocompletion, autosuggestion, facets, sorting, and pagination.
+It delivers a full customer experience from browsing the catalog to placing an order. The application helps you understand how you can use the predefined APIs to create a B2C user experience. As an example, the full power of Elasticsearch, which is already present in our [B2B](/docs/about/all/b2b-suite.html) and [B2C Demo Shops](/docs/about/all/b2c-suite.html), is leveraged through dedicated endpoints to deliver catalog search functionality with autocompletion, autosuggestion, facets, sorting, and pagination.
 
 {% info_block infoBox %}
 
diff --git a/docs/dg/dev/glue-api/202307.0/configure-the-included-section.md b/docs/dg/dev/glue-api/202307.0/configure-the-included-section.md
index d789e6036ab..66d5edb34cd 100644
--- a/docs/dg/dev/glue-api/202307.0/configure-the-included-section.md
+++ b/docs/dg/dev/glue-api/202307.0/configure-the-included-section.md
@@ -29,7 +29,7 @@ You can decide whether Glue REST API includes the sections in all responses by d
 |**Enabled** | The **included** and **relationships** sections contain only the resources whose names were passed in the query string (resource `concrete-product-image-sets` per the example). | The included section contains all the included resources (if any). |
 |**Disabled** | The response does not contain the included section with related resources. |  The included section contains all the included resources (if any).|
 
-By default, the option is enabled on the Spryker Core level but disabled on the project level in all [Spryker Demo Shops](/docs/scos/user/intro-to-spryker/intro-to-spryker.html#spryker-b2bb2c-demo-shops) (B2B Demo Shop, B2C Demo Shop and Master Shop Suite).
+By default, the option is enabled on the Spryker Core level but disabled on the project level in all [Spryker Demo Shops](/docs/about/all/intro-to-spryker.html#spryker-b2bb2c-demo-shops) (B2B Demo Shop, B2C Demo Shop and Master Shop Suite).
 
 {% info_block infoBox %}
 
diff --git a/docs/dg/dev/glue-api/202307.0/glue-api-tutorials/extend-a-rest-api-resource.md b/docs/dg/dev/glue-api/202307.0/glue-api-tutorials/extend-a-rest-api-resource.md
index 5505f70aa1b..86b6e652c19 100644
--- a/docs/dg/dev/glue-api/202307.0/glue-api-tutorials/extend-a-rest-api-resource.md
+++ b/docs/dg/dev/glue-api/202307.0/glue-api-tutorials/extend-a-rest-api-resource.md
@@ -46,7 +46,7 @@ The following guide relies on your knowledge of the structure of the Glue REST A
 
 {% info_block infoBox %}
 
-If you have a development virtual machine with the [B2C Demo Shop](/docs/scos/user/intro-to-spryker/intro-to-spryker.html#spryker-b2bb2c-demo-shops) installed, all the required components are available out of the box.
+If you have a development virtual machine with the [B2C Demo Shop](/docs/about/all/intro-to-spryker.html#spryker-b2bb2c-demo-shops) installed, all the required components are available out of the box.
 
 Assume that you modify the product storage data to match your product requirements—for example, you add the `manufacturerCountry` field to the product data not as an attribute but as another field in the database.
 
diff --git a/docs/dg/dev/glue-api/202307.0/old-glue-infrastructure/glue-rest-api.md b/docs/dg/dev/glue-api/202307.0/old-glue-infrastructure/glue-rest-api.md
index bd4348189d4..eb9df2c6ba9 100644
--- a/docs/dg/dev/glue-api/202307.0/old-glue-infrastructure/glue-rest-api.md
+++ b/docs/dg/dev/glue-api/202307.0/old-glue-infrastructure/glue-rest-api.md
@@ -49,7 +49,7 @@ For more details, see REST API reference:
 
 To help you understand possible use cases, we provide a sample app as an exemplary implementation (which is not a starting point for development). It can coexist with a shop as a second touchpoint in the project. From a technological perspective, it is based on our customers' interests. The app is single-page application based on a React JS library.
 
-It delivers a full customer experience from browsing the catalog to placing an order. The application helps you understand how you can use the predefined APIs to create a B2C user experience. As an example, the full power of Elasticsearch, which is already present in our [B2B](/docs/scos/user/intro-to-spryker/b2b-suite.html) and [B2C Demo Shops](/docs/scos/user/intro-to-spryker/b2c-suite.html), is leveraged through dedicated endpoints to deliver catalog search functionality with autocompletion, autosuggestion, facets, sorting, and pagination.
+It delivers a full customer experience from browsing the catalog to placing an order. The application helps you understand how you can use the predefined APIs to create a B2C user experience. As an example, the full power of Elasticsearch, which is already present in our [B2B](/docs/about/all/b2b-suite.html) and [B2C Demo Shops](/docs/about/all/b2c-suite.html), is leveraged through dedicated endpoints to deliver catalog search functionality with autocompletion, autosuggestion, facets, sorting, and pagination.
 
 {% info_block infoBox %}
 
diff --git a/docs/dg/dev/glue-api/202311.0/configure-the-included-section.md b/docs/dg/dev/glue-api/202311.0/configure-the-included-section.md
index c2667d57f0f..4ee9d5967d6 100644
--- a/docs/dg/dev/glue-api/202311.0/configure-the-included-section.md
+++ b/docs/dg/dev/glue-api/202311.0/configure-the-included-section.md
@@ -30,7 +30,7 @@ You can decide whether Glue REST API includes the sections in all responses by d
 |**Enabled** | The **included** and **relationships** sections contain only the resources whose names were passed in the query string (resource `concrete-product-image-sets` per the example). | The included section contains all the included resources (if any). |
 |**Disabled** | The response does not contain the included section with related resources. |  The included section contains all the included resources (if any).|
 
-By default, the option is enabled on the Spryker Core level but disabled on the project level in all [Spryker Demo Shops](/docs/scos/user/intro-to-spryker/intro-to-spryker.html#spryker-b2bb2c-demo-shops) (B2B Demo Shop, B2C Demo Shop and Master Shop Suite).
+By default, the option is enabled on the Spryker Core level but disabled on the project level in all [Spryker Demo Shops](/docs/about/all/intro-to-spryker.html#spryker-b2bb2c-demo-shops) (B2B Demo Shop, B2C Demo Shop and Master Shop Suite).
 
 {% info_block infoBox %}
 
diff --git a/docs/dg/dev/glue-api/202311.0/glue-api-tutorials/extend-a-rest-api-resource.md b/docs/dg/dev/glue-api/202311.0/glue-api-tutorials/extend-a-rest-api-resource.md
index ffde2a84005..d1bfd3532f2 100644
--- a/docs/dg/dev/glue-api/202311.0/glue-api-tutorials/extend-a-rest-api-resource.md
+++ b/docs/dg/dev/glue-api/202311.0/glue-api-tutorials/extend-a-rest-api-resource.md
@@ -32,7 +32,7 @@ The following guide relies on your knowledge of the structure of the Glue REST A
 
 {% info_block infoBox %}
 
-If you have a development virtual machine with the [B2C Demo Shop](/docs/scos/user/intro-to-spryker/intro-to-spryker.html#spryker-b2bb2c-demo-shops) installed, all the required components are available out of the box.
+If you have a development virtual machine with the [B2C Demo Shop](/docs/about/all/intro-to-spryker.html#spryker-b2bb2c-demo-shops) installed, all the required components are available out of the box.
 
 Assume that you modify the product storage data to match your product requirements—for example, you add the `manufacturerCountry` field to the product data not as an attribute but as another field in the database.
 
diff --git a/docs/dg/dev/glue-api/202311.0/old-glue-infrastructure/glue-rest-api.md b/docs/dg/dev/glue-api/202311.0/old-glue-infrastructure/glue-rest-api.md
index a00c6a1148f..132e44eff01 100644
--- a/docs/dg/dev/glue-api/202311.0/old-glue-infrastructure/glue-rest-api.md
+++ b/docs/dg/dev/glue-api/202311.0/old-glue-infrastructure/glue-rest-api.md
@@ -45,7 +45,7 @@ For more details, see REST API reference:
 
 To help you understand possible use cases, we provide a sample app as an exemplary implementation (which is not a starting point for development). It can coexist with a shop as a second touchpoint in the project. From a technological perspective, it is based on our customers' interests. The app is single-page application based on a React JS library.
 
-It delivers a full customer experience from browsing the catalog to placing an order. The application helps you understand how you can use the predefined APIs to create a B2C user experience. As an example, the full power of Elasticsearch, which is already present in our [B2B](/docs/scos/user/intro-to-spryker/b2b-suite.html) and [B2C Demo Shops](/docs/scos/user/intro-to-spryker/b2c-suite.html), is leveraged through dedicated endpoints to deliver catalog search functionality with autocompletion, autosuggestion, facets, sorting, and pagination.
+It delivers a full customer experience from browsing the catalog to placing an order. The application helps you understand how you can use the predefined APIs to create a B2C user experience. As an example, the full power of Elasticsearch, which is already present in our [B2B](/docs/about/all/b2b-suite.html) and [B2C Demo Shops](/docs/about/all/b2c-suite.html), is leveraged through dedicated endpoints to deliver catalog search functionality with autocompletion, autosuggestion, facets, sorting, and pagination.
 
 {% info_block infoBox %}
 
diff --git a/docs/dg/dev/integrate-and-configure/configure-services.md b/docs/dg/dev/integrate-and-configure/configure-services.md
index 30b0ccc29c1..7521512f0fd 100644
--- a/docs/dg/dev/integrate-and-configure/configure-services.md
+++ b/docs/dg/dev/integrate-and-configure/configure-services.md
@@ -508,7 +508,7 @@ image:
 
 
 
-3. Submit an infrastructure change request via the [Support Portal](/docs/scos/user/intro-to-spryker/support/how-to-use-the-support-portal.html).
+3. Submit an infrastructure change request via the [Support Portal](/docs/about/all/support/how-to-use-the-support-portal.html).
   We will confirm that a New Relic APM account is available for you and ensure that the correct application naming convention is set up to cascade to the appropriate APM.
 
 Once New Relic is enabled, in the New Relic dashboard, you may see either `company-staging-newrelic-app` or `YVES-DE (docker.dev)`. New Relic displays these APM names by the application name setup in the configuration files.
@@ -518,7 +518,7 @@ Once New Relic is enabled, in the New Relic dashboard, you may see either `compa
 
 {% info_block infoBox %}
 
-If you update the name of an application, [contact support](/docs/scos/user/intro-to-spryker/support/how-to-use-the-support-portal.html) to update the changes in your APM.
+If you update the name of an application, [contact support](/docs/about/all/support/how-to-use-the-support-portal.html) to update the changes in your APM.
 
 {% endinfo_block %}
 
diff --git a/docs/dg/dev/master-suite.md b/docs/dg/dev/master-suite.md
index 8fad990446b..3192fdbff8b 100644
--- a/docs/dg/dev/master-suite.md
+++ b/docs/dg/dev/master-suite.md
@@ -8,7 +8,7 @@ redirect_from:
 - /docs/scos/user/intro-to-spryker/master-suite.html
 ---
 
-Master Suite represents a collection of both [B2B](/docs/scos/user/intro-to-spryker/b2b-suite.html) and [B2C](/docs/scos/user/intro-to-spryker/b2c-suite.html) modules. However, unlike B2B and B2C Demo Shops, the code in the [Master Suite project repository](https://github.com/spryker-shop/suite) is released as soon as it is ready. If you have an implementation that combines B2B and B2C, you can benefit from the full range of SCOS functionality.
+Master Suite represents a collection of both [B2B](/docs/about/all/b2b-suite.html) and [B2C](/docs/about/all/b2c-suite.html) modules. However, unlike B2B and B2C Demo Shops, the code in the [Master Suite project repository](https://github.com/spryker-shop/suite) is released as soon as it is ready. If you have an implementation that combines B2B and B2C, you can benefit from the full range of SCOS functionality.
 
 Or if you want to take a single feature or module from the larger SCOS scope, you can take single modules from the following GitHub repositories:
 * [https://github.com/spryker-shop/*](https://github.com/spryker-shop/)
diff --git a/docs/dg/dev/set-up-spryker-locally/install-spryker/install/choose-an-installation-mode.md b/docs/dg/dev/set-up-spryker-locally/install-spryker/install/choose-an-installation-mode.md
index 86e381145ea..2a0d3f903fd 100644
--- a/docs/dg/dev/set-up-spryker-locally/install-spryker/install/choose-an-installation-mode.md
+++ b/docs/dg/dev/set-up-spryker-locally/install-spryker/install/choose-an-installation-mode.md
@@ -64,7 +64,7 @@ In Demo mode, the following functionalities are missing or disabled:
 
 Demo mode is used in the following cases:
 
-* To check or show the functionalities of [B2B](/docs/scos/user/intro-to-spryker/b2b-suite.html)/[B2C demo shops](/docs/scos/user/intro-to-spryker/b2c-suite.html).
+* To check or show the functionalities of [B2B](/docs/about/all/b2b-suite.html)/[B2C demo shops](/docs/about/all/b2c-suite.html).
 * To check a custom build or a new feature.
 * To test or deploy an application using Continuous Integration and Continuous Delivery tools.
 
diff --git a/docs/dg/dev/set-up-spryker-locally/install-spryker/install/install-in-demo-mode-on-windows.md b/docs/dg/dev/set-up-spryker-locally/install-spryker/install/install-in-demo-mode-on-windows.md
index 6cdb62fb1a4..427a831cac6 100644
--- a/docs/dg/dev/set-up-spryker-locally/install-spryker/install/install-in-demo-mode-on-windows.md
+++ b/docs/dg/dev/set-up-spryker-locally/install-spryker/install/install-in-demo-mode-on-windows.md
@@ -28,7 +28,7 @@ Depending on the needed WSL version, follow one of the guides:
 1. Open Ubuntu.
 2. Open a terminal.
 3. Create a new folder and navigate into it.
-4. Clone *one* of the [Demo Shops](/docs/scos/user/intro-to-spryker/intro-to-spryker.html#spryker-b2bb2c-demo-shops) and navigate into its folder:
+4. Clone *one* of the [Demo Shops](/docs/about/all/intro-to-spryker.html#spryker-b2bb2c-demo-shops) and navigate into its folder:
 
     * B2C Demo Shop:
 
diff --git a/docs/dg/dev/set-up-spryker-locally/install-spryker/install/install-in-development-mode-on-windows.md b/docs/dg/dev/set-up-spryker-locally/install-spryker/install/install-in-development-mode-on-windows.md
index 66e776969a9..dcc02e3a59b 100644
--- a/docs/dg/dev/set-up-spryker-locally/install-spryker/install/install-in-development-mode-on-windows.md
+++ b/docs/dg/dev/set-up-spryker-locally/install-spryker/install/install-in-development-mode-on-windows.md
@@ -40,7 +40,7 @@ Recommended: `/home/jdoe/workspace/project`.
 2. Open a terminal.
 3. Create a new folder and navigate into it.
 
-4. Clone *one* of the [Demo Shops](/docs/scos/user/intro-to-spryker/intro-to-spryker.html#spryker-b2bb2c-demo-shops):
+4. Clone *one* of the [Demo Shops](/docs/about/all/intro-to-spryker.html#spryker-b2bb2c-demo-shops):
 
     * B2C Demo Shop:
 
diff --git a/docs/dg/dev/system-requirements/202212.0/system-requirements.md b/docs/dg/dev/system-requirements/202212.0/system-requirements.md
index 4f1fb308845..9388025347c 100644
--- a/docs/dg/dev/system-requirements/202212.0/system-requirements.md
+++ b/docs/dg/dev/system-requirements/202212.0/system-requirements.md
@@ -19,7 +19,7 @@ redirect_from:
 | OS                                        | Native: Linux                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
 | Web Server                                | NginX—preferred. But any webserver which supports PHP will work such as lighttpd, Apache, Cherokee.                                                                                                                                                                                                                                                                                                                                                                   |
 | Databases                                 | Depending on the project, one of the databases: MariaDB >= 10.4—preferred, PostgreSQL >=9.6, or MySQL >=5.7.                                                                                                                                                                                                                                                                                                                                                          |
-| PHP                                       | Spryker supports PHP `>=8.0` with the following extensions: `curl`, `json`, `mysql`, `pdo-sqlite`, `sqlite3`, `gd`, `intl`, `mysqli`, `pgsql`, `ssh2`, `gmp`, `mcrypt`, `pdo-mysql`, `readline`, `twig`, `imagick`, `memcache`, `pdo-pgsql`, `redis`, `xml`, `bz2`, `mbstring`. See [Supported Versions of PHP](/docs/scos/user/intro-to-spryker/whats-new/supported-versions-of-php.html) for details on the supported PHP versions. |
+| PHP                                       | Spryker supports PHP `>=8.0` with the following extensions: `curl`, `json`, `mysql`, `pdo-sqlite`, `sqlite3`, `gd`, `intl`, `mysqli`, `pgsql`, `ssh2`, `gmp`, `mcrypt`, `pdo-mysql`, `readline`, `twig`, `imagick`, `memcache`, `pdo-pgsql`, `redis`, `xml`, `bz2`, `mbstring`. See [Supported Versions of PHP](/docs/about/all/whats-new/supported-versions-of-php.html) for details on the supported PHP versions. |
 | SSL                                       | For production systems, a valid security certificate is required for HTTPS.                                                                                                                                                                                                                                                                                                                                                                                           |
 | Redis                                     | Version >=3.2, >=5.0                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
 | Elasticsearch                             | Version 7.x                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
@@ -41,7 +41,7 @@ redirect_from:
 |---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | Web Server                                | NginX—preferred. But any webserver which supports PHP will work such as lighttpd, Apache, Cherokee.                                                                                                                                                                                                                                                                                                                                       |
 | Databases                               | Depending on the project, one of the databases: MariaDB >= 10.4—preferred, PostgreSQL >=9.6, or MySQL >=5.7.                                                                                                                                                                                                                                                                                                                              |
-| PHP                                       | Spryker supports PHP `>=8.0` with the following extensions: `curl`, `json`, `mysql`, `pdo-sqlite`, `sqlite3`, `gd`, `intl`, `mysqli`, `pgsql`, `ssh2`, `gmp`, `mcrypt`, `pdo-mysql`, `readline`, `twig`, `imagick`, `memcache`, `pdo-pgsql`, `redis`, `xml`, `bz2`, `mbstring`. For details about the supported PHP versions, see [Supported Versions of PHP](/docs/scos/user/intro-to-spryker/whats-new/supported-versions-of-php.html). |
+| PHP                                       | Spryker supports PHP `>=8.0` with the following extensions: `curl`, `json`, `mysql`, `pdo-sqlite`, `sqlite3`, `gd`, `intl`, `mysqli`, `pgsql`, `ssh2`, `gmp`, `mcrypt`, `pdo-mysql`, `readline`, `twig`, `imagick`, `memcache`, `pdo-pgsql`, `redis`, `xml`, `bz2`, `mbstring`. For details about the supported PHP versions, see [Supported Versions of PHP](/docs/about/all/whats-new/supported-versions-of-php.html). |
 | SSL                                       | For production systems, a valid security certificate is required for HTTPS.                                                                                                                                                                                                                                                                                                                                                               |
 | Redis                                     | Version >=3.2, >=5.0                                                                                                                                                                                                                                                                                                                                                                                                                      |
 | Elasticsearch                             | Version 6.*x* or 7.*x*                                                                                                                                                                                                                                                                                                                                                                                                                    |
diff --git a/docs/dg/dev/system-requirements/202307.0/system-requirements.md b/docs/dg/dev/system-requirements/202307.0/system-requirements.md
index 784ab3289d5..fa6353d2904 100644
--- a/docs/dg/dev/system-requirements/202307.0/system-requirements.md
+++ b/docs/dg/dev/system-requirements/202307.0/system-requirements.md
@@ -21,7 +21,7 @@ redirect_from:
 | OS                                        | Native: Linux                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
 | Web Server                                | NginX—preferred. But any webserver which supports PHP will work such as lighttpd, Apache, Cherokee.                                                                                                                                                                                                                                                                                                                                                                   |
 | Databases                                 | Depending on the project, one of the databases: MariaDB >= 10.4—preferred, PostgreSQL >=9.6, or MySQL >=5.7.                                                                                                                                                                                                                                                                                                                                                          |
-| PHP                                       | Spryker supports PHP `>=8.1` with the following extensions: `curl`, `json`, `mysql`, `pdo-sqlite`, `sqlite3`, `gd`, `intl`, `mysqli`, `pgsql`, `ssh2`, `gmp`, `mcrypt`, `pdo-mysql`, `readline`, `twig`, `imagick`, `memcache`, `pdo-pgsql`, `redis`, `xml`, `bz2`, and `mbstring`. For details about the supported PHP versions, see [Supported Versions of PHP](/docs/scos/user/intro-to-spryker/whats-new/supported-versions-of-php.html) |
+| PHP                                       | Spryker supports PHP `>=8.1` with the following extensions: `curl`, `json`, `mysql`, `pdo-sqlite`, `sqlite3`, `gd`, `intl`, `mysqli`, `pgsql`, `ssh2`, `gmp`, `mcrypt`, `pdo-mysql`, `readline`, `twig`, `imagick`, `memcache`, `pdo-pgsql`, `redis`, `xml`, `bz2`, and `mbstring`. For details about the supported PHP versions, see [Supported Versions of PHP](/docs/about/all/whats-new/supported-versions-of-php.html) |
 | SSL                                       | For production systems, a valid security certificate is required for HTTPS.                                                                                                                                                                                                                                                                                                                                                                                           |
 | Redis                                     | Version >=3.2, >=5.0                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
 | Elasticsearch                             | Version 7.*x*                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
@@ -40,7 +40,7 @@ redirect_from:
 |---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | Web Server                                | NginX—preferred. But any webserver which supports PHP will work such as lighttpd, Apache, Cherokee.                                                                                                                                                                                                                                                                                                                                                                       |
 | Databases                               | Depending on the project, one of the databases: MariaDB >= 10.4—preferred, PostgreSQL >=9.6, or MySQL >=5.7.                                                                                                                                                                                                                                                                                                                                                              |
-| PHP                                       | Spryker supports PHP `>=8.1` with the following extensions: `curl`, `json`, `mysql`, `pdo-sqlite`, `sqlite3`, `gd`, `intl`, `mysqli`, `pgsql`, `ssh2`, `gmp`, `mcrypt`, `pdo-mysql`, `readline`, `twig`, `imagick`, `memcache`, `pdo-pgsql`, `redis`, `xml`, `bz2`, `mbstring`. For details about the supported PHP versions, see [Supported Versions of PHP](/docs/scos/user/intro-to-spryker/whats-new/supported-versions-of-php.html). |
+| PHP                                       | Spryker supports PHP `>=8.1` with the following extensions: `curl`, `json`, `mysql`, `pdo-sqlite`, `sqlite3`, `gd`, `intl`, `mysqli`, `pgsql`, `ssh2`, `gmp`, `mcrypt`, `pdo-mysql`, `readline`, `twig`, `imagick`, `memcache`, `pdo-pgsql`, `redis`, `xml`, `bz2`, `mbstring`. For details about the supported PHP versions, see [Supported Versions of PHP](/docs/about/all/whats-new/supported-versions-of-php.html). |
 | SSL                                       | For production systems, a valid security certificate is required for HTTPS.                                                                                                                                                                                                                                                                                                                                                                                               |
 | Redis                                     | Version >=3.2, >=5.0                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
 | Elasticsearch                             | Version 6.*x* or 7.*x*                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
diff --git a/docs/dg/dev/system-requirements/202311.0/system-requirements.md b/docs/dg/dev/system-requirements/202311.0/system-requirements.md
index 0defe7c7033..0971569345d 100644
--- a/docs/dg/dev/system-requirements/202311.0/system-requirements.md
+++ b/docs/dg/dev/system-requirements/202311.0/system-requirements.md
@@ -23,7 +23,7 @@ redirect_from:
 | OS                                        | Native: Linux                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
 | Web Server                                | NginX—preferred. But any webserver which supports PHP will work such as lighttpd, Apache, Cherokee.                                                                                                                                                                                                                                                                                                                                                                   |
 | Databases                                 | Depending on the project, one of the databases: MariaDB >= 10.4—preferred, PostgreSQL >=9.6, or MySQL >=5.7.                                                                                                                                                                                                                                                                                                                                                          |
-| PHP                                       | Spryker supports PHP `>=8.1` with the following extensions: `curl`, `json`, `mysql`, `pdo-sqlite`, `sqlite3`, `gd`, `intl`, `mysqli`, `pgsql`, `ssh2`, `gmp`, `mcrypt`, `pdo-mysql`, `readline`, `twig`, `imagick`, `memcache`, `pdo-pgsql`, `redis`, `xml`, `bz2`, and `mbstring`. For details about the supported PHP versions, see [Supported Versions of PHP](/docs/scos/user/intro-to-spryker/whats-new/supported-versions-of-php.html) |
+| PHP                                       | Spryker supports PHP `>=8.1` with the following extensions: `curl`, `json`, `mysql`, `pdo-sqlite`, `sqlite3`, `gd`, `intl`, `mysqli`, `pgsql`, `ssh2`, `gmp`, `mcrypt`, `pdo-mysql`, `readline`, `twig`, `imagick`, `memcache`, `pdo-pgsql`, `redis`, `xml`, `bz2`, and `mbstring`. For details about the supported PHP versions, see [Supported Versions of PHP](/docs/about/all/whats-new/supported-versions-of-php.html) |
 | SSL                                       | For production systems, a valid security certificate is required for HTTPS.                                                                                                                                                                                                                                                                                                                                                                                           |
 | Redis                                     | Version >=3.2, >=5.0                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
 | Elasticsearch                             | Version 7.*x*                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
@@ -42,7 +42,7 @@ redirect_from:
 |---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | Web Server                                | NginX—preferred. But any webserver which supports PHP will work such as lighttpd, Apache, Cherokee.                                                                                                                                                                                                                                                                                                                                                                       |
 | Databases                               | Depending on the project, one of the databases: MariaDB >= 10.4—preferred, PostgreSQL >=9.6, or MySQL >=5.7.                                                                                                                                                                                                                                                                                                                                                              |
-| PHP                                       | Spryker supports PHP `>=8.1` with the following extensions: `curl`, `json`, `mysql`, `pdo-sqlite`, `sqlite3`, `gd`, `intl`, `mysqli`, `pgsql`, `ssh2`, `gmp`, `mcrypt`, `pdo-mysql`, `readline`, `twig`, `imagick`, `memcache`, `pdo-pgsql`, `redis`, `xml`, `bz2`, `mbstring`. For details about the supported PHP versions, see [Supported Versions of PHP](/docs/scos/user/intro-to-spryker/whats-new/supported-versions-of-php.html). |
+| PHP                                       | Spryker supports PHP `>=8.1` with the following extensions: `curl`, `json`, `mysql`, `pdo-sqlite`, `sqlite3`, `gd`, `intl`, `mysqli`, `pgsql`, `ssh2`, `gmp`, `mcrypt`, `pdo-mysql`, `readline`, `twig`, `imagick`, `memcache`, `pdo-pgsql`, `redis`, `xml`, `bz2`, `mbstring`. For details about the supported PHP versions, see [Supported Versions of PHP](/docs/about/all/whats-new/supported-versions-of-php.html). |
 | SSL                                       | For production systems, a valid security certificate is required for HTTPS.                                                                                                                                                                                                                                                                                                                                                                                               |
 | Redis                                     | Version >=3.2, >=5.0                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
 | Elasticsearch                             | Version 6.*x* or 7.*x*                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-performance-issues/troubleshooting-performance-issues.md b/docs/dg/dev/troubleshooting/troubleshooting-performance-issues/troubleshooting-performance-issues.md
index ac35f40126f..4fe88d46c2f 100644
--- a/docs/dg/dev/troubleshooting/troubleshooting-performance-issues/troubleshooting-performance-issues.md
+++ b/docs/dg/dev/troubleshooting/troubleshooting-performance-issues/troubleshooting-performance-issues.md
@@ -104,5 +104,5 @@ Blackfire groups some actions, so after each round of optimization, you will see
   - Repeat.
 4. Check if your result is still good for future growth. Return to the previous step if needed.
 5. Share your experience:
-  - [Contribute to public documentation](/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/contribute-to-the-documentation.html).
+  - [Contribute to public documentation](/docs/about/all/contribute-to-the-documentation/contribute-to-the-documentation.html).
   - Share it with [Spryker Community](https://spryker.com/community/).
diff --git a/docs/dg/dev/troubleshooting/troubleshooting.md b/docs/dg/dev/troubleshooting/troubleshooting.md
index 63da07eebce..b988c3611bd 100644
--- a/docs/dg/dev/troubleshooting/troubleshooting.md
+++ b/docs/dg/dev/troubleshooting/troubleshooting.md
@@ -34,6 +34,6 @@ This section gives answers to common troubleshooting questions and includes the
 
 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:
 
-* [How Spryker support works](/docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html)
-* [How to get the most out of support](/docs/scos/user/intro-to-spryker/support/getting-the-most-out-of-spryker-support.html)
-* [Understanding ticket status](/docs/scos/user/intro-to-spryker/support/understanding-ticket-status.html)
+* [How Spryker support works](/docs/about/all/support/how-spryker-support-works.html)
+* [How to get the most out of support](/docs/about/all/support/getting-the-most-out-of-spryker-support.html)
+* [Understanding ticket status](/docs/about/all/support/understanding-ticket-status.html)
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 7e64ae53f14..6bf377220a0 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
@@ -71,7 +71,7 @@ To migrate to a newer product release, use the Jarvis *basic* view. This view li
 This view is especially useful when:
 
 * You have a Spryker-based product and finished the main development part of it.
-* Your project uses feature repositories, or the project is based on the Spyker[ B2B Demo Shop](/docs/scos/user/intro-to-spryker/b2b-suite.html) or the [B2C Demo Shop](/docs/scos/user/intro-to-spryker/b2c-suite.html).
+* Your project uses feature repositories, or the project is based on the Spyker[ B2B Demo Shop](/docs/about/all/b2b-suite.html) or the [B2C Demo Shop](/docs/about/all/b2c-suite.html).
 
 Use this view if you want to stay up-to-date with Spryker and get new features of every Spryker product release.
 
diff --git a/docs/dg/dev/updating-spryker/feature-or-module-updates.md b/docs/dg/dev/updating-spryker/feature-or-module-updates.md
index c646ec52825..1b2f860735d 100644
--- a/docs/dg/dev/updating-spryker/feature-or-module-updates.md
+++ b/docs/dg/dev/updating-spryker/feature-or-module-updates.md
@@ -9,7 +9,7 @@ redirect_from:
 
 When you know that you need to update your project, you need to decide if you want to do updates on the *feature* or the *module* level.
 
-Features are released every several month as part of [Product Releases](/docs/scos/user/intro-to-spryker/spryker-release-process.html#product-releases). Modules updates are released as frequently as several times per day and are part of [Code Releases](/docs/scos/user/intro-to-spryker/spryker-release-process.html#atomic-code-releases).
+Features are released every several month as part of [Product Releases](/docs/about/all/spryker-release-process.html#product-releases). Modules updates are released as frequently as several times per day and are part of [Code Releases](/docs/about/all/spryker-release-process.html#atomic-code-releases).
 
 The table below shows when it might be more relevant for you to make updates at the feature level and when at the module level.
 
diff --git a/docs/dg/dev/updating-spryker/installing-features-and-updating-modules.md b/docs/dg/dev/updating-spryker/installing-features-and-updating-modules.md
index e7828d00521..5e703eb30e4 100644
--- a/docs/dg/dev/updating-spryker/installing-features-and-updating-modules.md
+++ b/docs/dg/dev/updating-spryker/installing-features-and-updating-modules.md
@@ -59,7 +59,7 @@ Sometimes, you may want to install a feature of a version higher than that of yo
 
 A new feature may require a higher major version of a specific module. In this case, do a [single module update](#update-to-a-major-versions-and-install-new-packages).
 
-You can learn about new Spryker features from the [release notes](/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes.html). Not to miss new release notes, we recommend [subscribing to our release newsletter](/docs/scos/user/intro-to-spryker/releases/releases.html).
+You can learn about new Spryker features from the [release notes](/docs/about/all/releases/release-notes/release-notes.html). Not to miss new release notes, we recommend [subscribing to our release newsletter](/docs/about/all/releases/releases.html).
 
 ## Next steps
 
diff --git a/docs/dg/dev/updating-spryker/updating-spryker.md b/docs/dg/dev/updating-spryker/updating-spryker.md
index 63a004c6a1e..c713b6f8b58 100644
--- a/docs/dg/dev/updating-spryker/updating-spryker.md
+++ b/docs/dg/dev/updating-spryker/updating-spryker.md
@@ -25,11 +25,11 @@ This article gives answers to these questions and provides recommendations that
 The smallest building block of Spryker is a *module*. Usually, a module does not represent a complete functionality. A complete functionality, or a *feature*, is represented by an aggregation of a set of modules. A feature is a virtual entity, which binds together a number of modules to satisfy certain functionalities. Check out the [Spryker feature repository](https://github.com/spryker-feature/) for detailed information about each feature.
 
 The set of features makes up a *product*. Spryker offers the following products:
-* [B2B Demo Shop](/docs/scos/user/intro-to-spryker/b2b-suite.html)
-* [B2C Demo Shop](/docs/scos/user/intro-to-spryker/b2c-suite.html)
-* [B2B Demo Marketplace](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2b-suite.html)
-* [B2C Demo Marketplace](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2c-suite.html)
-* [Master Suite](/docs/scos/user/intro-to-spryker/master-suite.html)
+* [B2B Demo Shop](/docs/about/all/b2b-suite.html)
+* [B2C Demo Shop](/docs/about/all/b2c-suite.html)
+* [B2B Demo Marketplace](/docs/about/all/spryker-marketplace/marketplace-b2b-suite.html)
+* [B2C Demo Marketplace](/docs/about/all/spryker-marketplace/marketplace-b2c-suite.html)
+* [Master Suite](/docs/about/all/master-suite.html)
 
 Schematically, the Spryker product structure looks like this:
 
@@ -40,7 +40,7 @@ Schematically, the Spryker product structure looks like this:
 The most typical reasons to update modules or features are the following:
 * There are important security or bug fixes that have been introduced recently.
 * You want a new specific feature or module in your project, which requires a newer version of your modules.
-* Your project has been started shortly before a new [product release](/docs/scos/user/intro-to-spryker/spryker-release-process.html#product-releases).
+* Your project has been started shortly before a new [product release](/docs/about/all/spryker-release-process.html#product-releases).
 * You experience some issues with the shop that you would like to report or consult about.
 * If you plan to extend your shop in future with new features from the ones that exist in Spryker or are coming out soon, your project should be always up to date. It will ease the new feature installation and reduce the migration efforts, allowing you to get the desired functionality faster.
 
@@ -50,7 +50,7 @@ The more outdated your module versions become, the more effort will be needed to
 
 {% endinfo_block %}
 
-The most *reasonable strategy* of staying up to date is sticking to the Spryker release cycle and updating modules whenever there is a new release announcement. To get notified about releases,  [subscribe to the release notes](/docs/scos/user/intro-to-spryker/releases/releases.html). During the active development phase, it makes sense to do updates more often, for example, monthly.
+The most *reasonable strategy* of staying up to date is sticking to the Spryker release cycle and updating modules whenever there is a new release announcement. To get notified about releases,  [subscribe to the release notes](/docs/about/all/releases/releases.html). During the active development phase, it makes sense to do updates more often, for example, monthly.
 
 ## Spryker Safari materials
 
diff --git a/docs/pbc/all/cart-and-checkout/202212.0/base-shop/feature-overviews/multiple-carts-feature-overview.md b/docs/pbc/all/cart-and-checkout/202212.0/base-shop/feature-overviews/multiple-carts-feature-overview.md
index f819b1b8a22..72a647857bb 100644
--- a/docs/pbc/all/cart-and-checkout/202212.0/base-shop/feature-overviews/multiple-carts-feature-overview.md
+++ b/docs/pbc/all/cart-and-checkout/202212.0/base-shop/feature-overviews/multiple-carts-feature-overview.md
@@ -118,7 +118,7 @@ On the storefront, company users can perform the following actions by using the
 * To add a customer order reference to an order, see [Custom Order Reference feature overview](/docs/pbc/all/order-management-system/{{site.version}}/base-shop/order-management-feature-overview/custom-order-reference-overview.html).
 
 
-This video explains how to use shopping carts in the Spryker [B2B Demo Shop](/docs/scos/user/intro-to-spryker/b2b-suite.html).
+This video explains how to use shopping carts in the Spryker [B2B Demo Shop](/docs/about/all/b2b-suite.html).
 
 {% wistia s776wlo9ds 960 720 %}
 
diff --git a/docs/pbc/all/cart-and-checkout/202212.0/base-shop/tutorials-and-howtos/enable-guest-checkout-in-the-b2b-demo-shop.md b/docs/pbc/all/cart-and-checkout/202212.0/base-shop/tutorials-and-howtos/enable-guest-checkout-in-the-b2b-demo-shop.md
index 9f82cf8b136..5cf10b101f1 100644
--- a/docs/pbc/all/cart-and-checkout/202212.0/base-shop/tutorials-and-howtos/enable-guest-checkout-in-the-b2b-demo-shop.md
+++ b/docs/pbc/all/cart-and-checkout/202212.0/base-shop/tutorials-and-howtos/enable-guest-checkout-in-the-b2b-demo-shop.md
@@ -18,7 +18,7 @@ related:
     link: docs/scos/dev/back-end-development/data-manipulation/datapayload-conversion/checkout/checkout-steps.html
 ---
 
-As B2B environments usually implement complex business logic, in the [B2B Demo Shop](/docs/scos/user/intro-to-spryker/b2b-suite.html), guest users cannot check out by default. However, in some cases, you may need guest checkout to be enabled.
+As B2B environments usually implement complex business logic, in the [B2B Demo Shop](/docs/about/all/b2b-suite.html), guest users cannot check out by default. However, in some cases, you may need guest checkout to be enabled.
 
 {% info_block infoBox "Exemplary implementation" %}
 
diff --git a/docs/pbc/all/cart-and-checkout/202307.0/base-shop/feature-overviews/multiple-carts-feature-overview.md b/docs/pbc/all/cart-and-checkout/202307.0/base-shop/feature-overviews/multiple-carts-feature-overview.md
index fec20b8707f..378eadaff73 100644
--- a/docs/pbc/all/cart-and-checkout/202307.0/base-shop/feature-overviews/multiple-carts-feature-overview.md
+++ b/docs/pbc/all/cart-and-checkout/202307.0/base-shop/feature-overviews/multiple-carts-feature-overview.md
@@ -119,7 +119,7 @@ On the storefront, company users can perform the following actions by using the
 * To add a customer order reference to an order, see [Custom Order Reference feature overview](/docs/pbc/all/order-management-system/{{site.version}}/base-shop/order-management-feature-overview/custom-order-reference-overview.html).
 
 
-This video explains how to use shopping carts in the Spryker [B2B Demo Shop](/docs/scos/user/intro-to-spryker/b2b-suite.html).
+This video explains how to use shopping carts in the Spryker [B2B Demo Shop](/docs/about/all/b2b-suite.html).
 
 {% wistia s776wlo9ds 960 720 %}
 
diff --git a/docs/pbc/all/cart-and-checkout/202307.0/base-shop/tutorials-and-howtos/enable-guest-checkout-in-the-b2b-demo-shop.md b/docs/pbc/all/cart-and-checkout/202307.0/base-shop/tutorials-and-howtos/enable-guest-checkout-in-the-b2b-demo-shop.md
index 1b5162571fe..005878f6f1f 100644
--- a/docs/pbc/all/cart-and-checkout/202307.0/base-shop/tutorials-and-howtos/enable-guest-checkout-in-the-b2b-demo-shop.md
+++ b/docs/pbc/all/cart-and-checkout/202307.0/base-shop/tutorials-and-howtos/enable-guest-checkout-in-the-b2b-demo-shop.md
@@ -13,7 +13,7 @@ related:
     link: docs/scos/dev/back-end-development/data-manipulation/datapayload-conversion/checkout/checkout-steps.html
 ---
 
-As B2B environments usually implement complex business logic, in the [B2B Demo Shop](/docs/scos/user/intro-to-spryker/b2b-suite.html), guest users cannot check out by default. However, in some cases, you may need guest checkout to be enabled.
+As B2B environments usually implement complex business logic, in the [B2B Demo Shop](/docs/about/all/b2b-suite.html), guest users cannot check out by default. However, in some cases, you may need guest checkout to be enabled.
 
 {% info_block infoBox "Exemplary implementation" %}
 
diff --git a/docs/pbc/all/cart-and-checkout/202311.0/base-shop/feature-overviews/multiple-carts-feature-overview.md b/docs/pbc/all/cart-and-checkout/202311.0/base-shop/feature-overviews/multiple-carts-feature-overview.md
index 85a8df51944..e3d42cffb30 100644
--- a/docs/pbc/all/cart-and-checkout/202311.0/base-shop/feature-overviews/multiple-carts-feature-overview.md
+++ b/docs/pbc/all/cart-and-checkout/202311.0/base-shop/feature-overviews/multiple-carts-feature-overview.md
@@ -120,7 +120,7 @@ On the storefront, company users can perform the following actions by using the
 * To add a customer order reference to an order, see [Custom Order Reference feature overview](/docs/pbc/all/order-management-system/{{site.version}}/base-shop/order-management-feature-overview/custom-order-reference-overview.html).
 
 
-This video explains how to use shopping carts in the Spryker [B2B Demo Shop](/docs/scos/user/intro-to-spryker/b2b-suite.html).
+This video explains how to use shopping carts in the Spryker [B2B Demo Shop](/docs/about/all/b2b-suite.html).
 
 {% wistia s776wlo9ds 960 720 %}
 
diff --git a/docs/pbc/all/cart-and-checkout/202311.0/base-shop/tutorials-and-howtos/enable-guest-checkout-in-the-b2b-demo-shop.md b/docs/pbc/all/cart-and-checkout/202311.0/base-shop/tutorials-and-howtos/enable-guest-checkout-in-the-b2b-demo-shop.md
index 43ba87cd926..89fc498f738 100644
--- a/docs/pbc/all/cart-and-checkout/202311.0/base-shop/tutorials-and-howtos/enable-guest-checkout-in-the-b2b-demo-shop.md
+++ b/docs/pbc/all/cart-and-checkout/202311.0/base-shop/tutorials-and-howtos/enable-guest-checkout-in-the-b2b-demo-shop.md
@@ -13,7 +13,7 @@ related:
     link: docs/scos/dev/back-end-development/data-manipulation/datapayload-conversion/checkout/checkout-steps.html
 ---
 
-As B2B environments usually implement complex business logic, in the [B2B Demo Shop](/docs/scos/user/intro-to-spryker/b2b-suite.html), guest users cannot check out by default. However, in some cases, you may need guest checkout to be enabled.
+As B2B environments usually implement complex business logic, in the [B2B Demo Shop](/docs/about/all/b2b-suite.html), guest users cannot check out by default. However, in some cases, you may need guest checkout to be enabled.
 
 {% info_block infoBox "Exemplary implementation" %}
 
diff --git a/docs/pbc/all/content-management-system/202212.0/base-shop/cms-feature-overview/email-as-a-cms-block-overview.md b/docs/pbc/all/content-management-system/202212.0/base-shop/cms-feature-overview/email-as-a-cms-block-overview.md
index b62b335a0e8..f27dc09bc61 100644
--- a/docs/pbc/all/content-management-system/202212.0/base-shop/cms-feature-overview/email-as-a-cms-block-overview.md
+++ b/docs/pbc/all/content-management-system/202212.0/base-shop/cms-feature-overview/email-as-a-cms-block-overview.md
@@ -54,7 +54,7 @@ The email format itself is defined on the code level, the tales serving as ident
 
 
 ### Default email templates
-There is a number of email templates with the respective Email CMS Blocks available in the [Spryker Demo Shops](/docs/scos/user/intro-to-spryker/intro-to-spryker.html#spryker-b2bb2c-demo-shops).
+There is a number of email templates with the respective Email CMS Blocks available in the [Spryker Demo Shops](/docs/about/all/intro-to-spryker.html#spryker-b2bb2c-demo-shops).
 
 The following table contains the list of the default email templates, their Email CMS Blocks, and their purpose.
 
diff --git a/docs/pbc/all/content-management-system/202212.0/base-shop/manage-in-the-back-office/best-practices-add-content-to-the-storefront-pages-using-templates-and-slots.md b/docs/pbc/all/content-management-system/202212.0/base-shop/manage-in-the-back-office/best-practices-add-content-to-the-storefront-pages-using-templates-and-slots.md
index 3f2e4a468a3..10fc01ed244 100644
--- a/docs/pbc/all/content-management-system/202212.0/base-shop/manage-in-the-back-office/best-practices-add-content-to-the-storefront-pages-using-templates-and-slots.md
+++ b/docs/pbc/all/content-management-system/202212.0/base-shop/manage-in-the-back-office/best-practices-add-content-to-the-storefront-pages-using-templates-and-slots.md
@@ -30,7 +30,7 @@ To do that, you need to create content items, insert them into CMS blocks, assig
 
 {% info_block infoBox "Examplary content" %}
 
-All the content used in this guide is shipped by default in our [B2B Demo Shop](/docs/scos/user/intro-to-spryker/b2b-suite.html) and [B2C Demo Shop](/docs/scos/user/intro-to-spryker/b2c-suite.html).
+All the content used in this guide is shipped by default in our [B2B Demo Shop](/docs/about/all/b2b-suite.html) and [B2C Demo Shop](/docs/about/all/b2c-suite.html).
 
 {% endinfo_block %}
 
diff --git a/docs/pbc/all/content-management-system/202307.0/base-shop/cms-feature-overview/email-as-a-cms-block-overview.md b/docs/pbc/all/content-management-system/202307.0/base-shop/cms-feature-overview/email-as-a-cms-block-overview.md
index 972ad2bc880..05800146ba6 100644
--- a/docs/pbc/all/content-management-system/202307.0/base-shop/cms-feature-overview/email-as-a-cms-block-overview.md
+++ b/docs/pbc/all/content-management-system/202307.0/base-shop/cms-feature-overview/email-as-a-cms-block-overview.md
@@ -54,7 +54,7 @@ The email format itself is defined on the code level, the tales serving as ident
 
 
 ### Default email templates
-There is a number of email templates with the respective Email CMS Blocks available in the [Spryker Demo Shops](/docs/scos/user/intro-to-spryker/intro-to-spryker.html#spryker-b2bb2c-demo-shops).
+There is a number of email templates with the respective Email CMS Blocks available in the [Spryker Demo Shops](/docs/about/all/intro-to-spryker.html#spryker-b2bb2c-demo-shops).
 
 The following table contains the list of the default email templates, their Email CMS Blocks, and their purpose.
 
diff --git a/docs/pbc/all/content-management-system/202307.0/base-shop/manage-in-the-back-office/best-practices-add-content-to-the-storefront-pages-using-templates-and-slots.md b/docs/pbc/all/content-management-system/202307.0/base-shop/manage-in-the-back-office/best-practices-add-content-to-the-storefront-pages-using-templates-and-slots.md
index c284b2e32a1..7aa77a40ebb 100644
--- a/docs/pbc/all/content-management-system/202307.0/base-shop/manage-in-the-back-office/best-practices-add-content-to-the-storefront-pages-using-templates-and-slots.md
+++ b/docs/pbc/all/content-management-system/202307.0/base-shop/manage-in-the-back-office/best-practices-add-content-to-the-storefront-pages-using-templates-and-slots.md
@@ -30,7 +30,7 @@ To do that, you need to create content items, insert them into CMS blocks, assig
 
 {% info_block infoBox "Examplary content" %}
 
-All the content used in this guide is shipped by default in our [B2B Demo Shop](/docs/scos/user/intro-to-spryker/b2b-suite.html) and [B2C Demo Shop](/docs/scos/user/intro-to-spryker/b2c-suite.html).
+All the content used in this guide is shipped by default in our [B2B Demo Shop](/docs/about/all/b2b-suite.html) and [B2C Demo Shop](/docs/about/all/b2c-suite.html).
 
 {% endinfo_block %}
 
diff --git a/docs/pbc/all/content-management-system/202311.0/base-shop/cms-feature-overview/email-as-a-cms-block-overview.md b/docs/pbc/all/content-management-system/202311.0/base-shop/cms-feature-overview/email-as-a-cms-block-overview.md
index 559c3ef0c76..8d811f52ebc 100644
--- a/docs/pbc/all/content-management-system/202311.0/base-shop/cms-feature-overview/email-as-a-cms-block-overview.md
+++ b/docs/pbc/all/content-management-system/202311.0/base-shop/cms-feature-overview/email-as-a-cms-block-overview.md
@@ -55,7 +55,7 @@ The email format itself is defined on the code level, the tales serving as ident
 
 
 ### Default email templates
-There is a number of email templates with the respective Email CMS Blocks available in the [Spryker Demo Shops](/docs/scos/user/intro-to-spryker/intro-to-spryker.html#spryker-b2bb2c-demo-shops).
+There is a number of email templates with the respective Email CMS Blocks available in the [Spryker Demo Shops](/docs/about/all/intro-to-spryker.html#spryker-b2bb2c-demo-shops).
 
 The following table contains the list of the default email templates, their Email CMS Blocks, and their purpose.
 
diff --git a/docs/pbc/all/content-management-system/202311.0/base-shop/manage-in-the-back-office/best-practices-add-content-to-the-storefront-pages-using-templates-and-slots.md b/docs/pbc/all/content-management-system/202311.0/base-shop/manage-in-the-back-office/best-practices-add-content-to-the-storefront-pages-using-templates-and-slots.md
index 3f35885d036..7e9c47d82ac 100644
--- a/docs/pbc/all/content-management-system/202311.0/base-shop/manage-in-the-back-office/best-practices-add-content-to-the-storefront-pages-using-templates-and-slots.md
+++ b/docs/pbc/all/content-management-system/202311.0/base-shop/manage-in-the-back-office/best-practices-add-content-to-the-storefront-pages-using-templates-and-slots.md
@@ -31,7 +31,7 @@ To do that, you need to create content items, insert them into CMS blocks, assig
 
 {% info_block infoBox "Examplary content" %}
 
-All the content used in this guide is shipped by default in our [B2B Demo Shop](/docs/scos/user/intro-to-spryker/b2b-suite.html) and [B2C Demo Shop](/docs/scos/user/intro-to-spryker/b2c-suite.html).
+All the content used in this guide is shipped by default in our [B2B Demo Shop](/docs/about/all/b2b-suite.html) and [B2C Demo Shop](/docs/about/all/b2c-suite.html).
 
 {% endinfo_block %}
 
diff --git a/docs/pbc/all/merchant-management/202212.0/marketplace/marketplace-merchant-feature-overview/main-merchant.md b/docs/pbc/all/merchant-management/202212.0/marketplace/marketplace-merchant-feature-overview/main-merchant.md
index 30f10de929f..4b53f568e3d 100644
--- a/docs/pbc/all/merchant-management/202212.0/marketplace/marketplace-merchant-feature-overview/main-merchant.md
+++ b/docs/pbc/all/merchant-management/202212.0/marketplace/marketplace-merchant-feature-overview/main-merchant.md
@@ -12,13 +12,13 @@ related:
     link: docs/pbc/all/return-management/page.version/marketplace/manage-in-the-back-office/manage-main-merchant-returns.html
 ---
 
-The Spryker Marketplace platform offers sales opportunities to everyone. To help support the [Enterprise Marketplace](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-concept.html) model, not only the 3rd party merchants but also the company owner of the Marketplace store can sell their products and offers online. We call this company the *main merchant*.
+The Spryker Marketplace platform offers sales opportunities to everyone. To help support the [Enterprise Marketplace](/docs/about/all/spryker-marketplace/marketplace-concept.html) model, not only the 3rd party merchants but also the company owner of the Marketplace store can sell their products and offers online. We call this company the *main merchant*.
 
 Thus, the main merchant acts as a common [marketplace merchant](/docs/pbc/all/merchant-management/{{page.version}}/marketplace/marketplace-merchant-feature-overview/marketplace-merchant-feature-overview.html) having all its characteristics.
 
 ## Main merchant orders and returns
 
-Being both a [marketplace operator](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-personas.html) and a seller and already performing tasks in the Back Office, the main merchant manages their [merchant orders](/docs/pbc/all/order-management-system/{{page.version}}/marketplace/marketplace-order-management-feature-overview/merchant-order-overview.html) also in the Back Office. For details, see [Managing main merchant orders](/docs/pbc/all/order-management-system/{{page.version}}/marketplace/manage-merchant-orders.html).
+Being both a [marketplace operator](/docs/about/all/spryker-marketplace/marketplace-personas.html) and a seller and already performing tasks in the Back Office, the main merchant manages their [merchant orders](/docs/pbc/all/order-management-system/{{page.version}}/marketplace/marketplace-order-management-feature-overview/merchant-order-overview.html) also in the Back Office. For details, see [Managing main merchant orders](/docs/pbc/all/order-management-system/{{page.version}}/marketplace/manage-merchant-orders.html).
 
 ## Main merchant state machine
 
diff --git a/docs/pbc/all/merchant-management/202307.0/marketplace/marketplace-merchant-feature-overview/main-merchant.md b/docs/pbc/all/merchant-management/202307.0/marketplace/marketplace-merchant-feature-overview/main-merchant.md
index 943b3136131..f3edf0f33c7 100644
--- a/docs/pbc/all/merchant-management/202307.0/marketplace/marketplace-merchant-feature-overview/main-merchant.md
+++ b/docs/pbc/all/merchant-management/202307.0/marketplace/marketplace-merchant-feature-overview/main-merchant.md
@@ -12,13 +12,13 @@ related:
     link: docs/pbc/all/return-management/page.version/marketplace/manage-in-the-back-office/manage-main-merchant-returns.html
 ---
 
-The Spryker Marketplace platform offers sales opportunities to everyone. To help support the [Enterprise Marketplace](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-concept.html) model, not only the 3rd party merchants but also the company owner of the Marketplace store can sell their products and offers online. We call this company the *main merchant*.
+The Spryker Marketplace platform offers sales opportunities to everyone. To help support the [Enterprise Marketplace](/docs/about/all/spryker-marketplace/marketplace-concept.html) model, not only the 3rd party merchants but also the company owner of the Marketplace store can sell their products and offers online. We call this company the *main merchant*.
 
 Thus, the main merchant acts as a common [marketplace merchant](/docs/pbc/all/merchant-management/{{page.version}}/marketplace/marketplace-merchant-feature-overview/marketplace-merchant-feature-overview.html) having all its characteristics.
 
 ## Main merchant orders and returns
 
-Being both a [marketplace operator](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-personas.html) and a seller and already performing tasks in the Back Office, the main merchant manages their [merchant orders](/docs/pbc/all/order-management-system/{{page.version}}/marketplace/marketplace-order-management-feature-overview/merchant-order-overview.html) also in the Back Office. For details, see [Managing main merchant orders](/docs/pbc/all/order-management-system/{{page.version}}/marketplace/manage-merchant-orders.html).
+Being both a [marketplace operator](/docs/about/all/spryker-marketplace/marketplace-personas.html) and a seller and already performing tasks in the Back Office, the main merchant manages their [merchant orders](/docs/pbc/all/order-management-system/{{page.version}}/marketplace/marketplace-order-management-feature-overview/merchant-order-overview.html) also in the Back Office. For details, see [Managing main merchant orders](/docs/pbc/all/order-management-system/{{page.version}}/marketplace/manage-merchant-orders.html).
 
 ## Main merchant state machine
 
diff --git a/docs/pbc/all/merchant-management/202311.0/marketplace/marketplace-merchant-feature-overview/main-merchant.md b/docs/pbc/all/merchant-management/202311.0/marketplace/marketplace-merchant-feature-overview/main-merchant.md
index 2ceb28363bf..28f54430e2c 100644
--- a/docs/pbc/all/merchant-management/202311.0/marketplace/marketplace-merchant-feature-overview/main-merchant.md
+++ b/docs/pbc/all/merchant-management/202311.0/marketplace/marketplace-merchant-feature-overview/main-merchant.md
@@ -12,13 +12,13 @@ related:
     link: docs/pbc/all/return-management/page.version/marketplace/manage-in-the-back-office/manage-main-merchant-returns.html
 ---
 
-The Spryker Marketplace platform offers sales opportunities to everyone. To help support the [Enterprise Marketplace](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-concept.html) model, not only the 3rd party merchants but also the company owner of the Marketplace store can sell their products and offers online. We call this company the *main merchant*.
+The Spryker Marketplace platform offers sales opportunities to everyone. To help support the [Enterprise Marketplace](/docs/about/all/spryker-marketplace/marketplace-concept.html) model, not only the 3rd party merchants but also the company owner of the Marketplace store can sell their products and offers online. We call this company the *main merchant*.
 
 Thus, the main merchant acts as a common [marketplace merchant](/docs/pbc/all/merchant-management/{{page.version}}/marketplace/marketplace-merchant-feature-overview/marketplace-merchant-feature-overview.html) having all its characteristics.
 
 ## Main merchant orders and returns
 
-Being both a [marketplace operator](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-personas.html) and a seller and already performing tasks in the Back Office, the main merchant manages their [merchant orders](/docs/pbc/all/order-management-system/{{page.version}}/marketplace/marketplace-order-management-feature-overview/merchant-order-overview.html) also in the Back Office. For details, see [Managing main merchant orders](/docs/pbc/all/order-management-system/{{page.version}}/marketplace/manage-merchant-orders.html).
+Being both a [marketplace operator](/docs/about/all/spryker-marketplace/marketplace-personas.html) and a seller and already performing tasks in the Back Office, the main merchant manages their [merchant orders](/docs/pbc/all/order-management-system/{{page.version}}/marketplace/marketplace-order-management-feature-overview/merchant-order-overview.html) also in the Back Office. For details, see [Managing main merchant orders](/docs/pbc/all/order-management-system/{{page.version}}/marketplace/manage-merchant-orders.html).
 
 ## Main merchant state machine
 
diff --git a/docs/pbc/all/price-management/202212.0/base-shop/merchant-custom-prices-feature-overview.md b/docs/pbc/all/price-management/202212.0/base-shop/merchant-custom-prices-feature-overview.md
index bb8d8e45cf1..93514d2bcf0 100644
--- a/docs/pbc/all/price-management/202212.0/base-shop/merchant-custom-prices-feature-overview.md
+++ b/docs/pbc/all/price-management/202212.0/base-shop/merchant-custom-prices-feature-overview.md
@@ -18,7 +18,7 @@ related:
     link: docs/pbc/all/price-management/page.version/base-shop/tutorials-and-howtos/howto-manage-business-unit-specific-prices-via-data-import.html
 ---
 
-In B2B commerce transactions, prices are typically negotiated in contracts. Therefore, merchants and their clients, who are usually company business units, expect to see their own prices in the shop. With the *Merchant Custom Prices* feature, the shop owners of the [B2B Demo Shop](/docs/scos/user/intro-to-spryker/b2b-suite.html) can provide different prices for merchants and their clients. This way, the relationship between merchants and buyers is reflected more accurately, and the shop owners can set different prices for various customers.
+In B2B commerce transactions, prices are typically negotiated in contracts. Therefore, merchants and their clients, who are usually company business units, expect to see their own prices in the shop. With the *Merchant Custom Prices* feature, the shop owners of the [B2B Demo Shop](/docs/about/all/b2b-suite.html) can provide different prices for merchants and their clients. This way, the relationship between merchants and buyers is reflected more accurately, and the shop owners can set different prices for various customers.
 
 
 When talking about product prices that depend on the customers they refer to, and we differentiate between two types: default and specific.
diff --git a/docs/pbc/all/price-management/202307.0/base-shop/merchant-custom-prices-feature-overview.md b/docs/pbc/all/price-management/202307.0/base-shop/merchant-custom-prices-feature-overview.md
index 65615033c21..847a5fd24fb 100644
--- a/docs/pbc/all/price-management/202307.0/base-shop/merchant-custom-prices-feature-overview.md
+++ b/docs/pbc/all/price-management/202307.0/base-shop/merchant-custom-prices-feature-overview.md
@@ -18,7 +18,7 @@ related:
     link: docs/pbc/all/price-management/page.version/base-shop/tutorials-and-howtos/howto-manage-business-unit-specific-prices-via-data-import.html
 ---
 
-In B2B commerce transactions, prices are typically negotiated in contracts. Therefore, merchants and their clients, who are usually company business units, expect to see their own prices in the shop. With the *Merchant Custom Prices* feature, the shop owners of the [B2B Demo Shop](/docs/scos/user/intro-to-spryker/b2b-suite.html) can provide different prices for merchants and their clients. This way, the relationship between merchants and buyers is reflected more accurately, and the shop owners can set different prices for various customers.
+In B2B commerce transactions, prices are typically negotiated in contracts. Therefore, merchants and their clients, who are usually company business units, expect to see their own prices in the shop. With the *Merchant Custom Prices* feature, the shop owners of the [B2B Demo Shop](/docs/about/all/b2b-suite.html) can provide different prices for merchants and their clients. This way, the relationship between merchants and buyers is reflected more accurately, and the shop owners can set different prices for various customers.
 
 
 When talking about product prices that depend on the customers they refer to, and we differentiate between two types: default and specific.
diff --git a/docs/pbc/all/price-management/202311.0/base-shop/merchant-custom-prices-feature-overview.md b/docs/pbc/all/price-management/202311.0/base-shop/merchant-custom-prices-feature-overview.md
index 0fadace5d5e..d94367653ac 100644
--- a/docs/pbc/all/price-management/202311.0/base-shop/merchant-custom-prices-feature-overview.md
+++ b/docs/pbc/all/price-management/202311.0/base-shop/merchant-custom-prices-feature-overview.md
@@ -19,7 +19,7 @@ related:
     link: docs/pbc/all/price-management/page.version/base-shop/tutorials-and-howtos/howto-manage-business-unit-specific-prices-via-data-import.html
 ---
 
-In B2B commerce transactions, prices are typically negotiated in contracts. Therefore, merchants and their clients, who are usually company business units, expect to see their own prices in the shop. With the *Merchant Custom Prices* feature, the shop owners of the [B2B Demo Shop](/docs/scos/user/intro-to-spryker/b2b-suite.html) can provide different prices for merchants and their clients. This way, the relationship between merchants and buyers is reflected more accurately, and the shop owners can set different prices for various customers.
+In B2B commerce transactions, prices are typically negotiated in contracts. Therefore, merchants and their clients, who are usually company business units, expect to see their own prices in the shop. With the *Merchant Custom Prices* feature, the shop owners of the [B2B Demo Shop](/docs/about/all/b2b-suite.html) can provide different prices for merchants and their clients. This way, the relationship between merchants and buyers is reflected more accurately, and the shop owners can set different prices for various customers.
 
 
 When talking about product prices that depend on the customers they refer to, and we differentiate between two types: default and specific.
diff --git a/docs/pbc/all/product-information-management/202212.0/base-shop/feature-overviews/category-management-feature-overview.md b/docs/pbc/all/product-information-management/202212.0/base-shop/feature-overviews/category-management-feature-overview.md
index a9ed8622dee..75e4152bd19 100644
--- a/docs/pbc/all/product-information-management/202212.0/base-shop/feature-overviews/category-management-feature-overview.md
+++ b/docs/pbc/all/product-information-management/202212.0/base-shop/feature-overviews/category-management-feature-overview.md
@@ -70,7 +70,7 @@ The Category Management feature has the following functional constraints, which
 * A store can only be linked to one root category tree, but in the future, a store can have multiple root category trees.
 * Category URLs are locale-dependent.
 * Category URLs are available in all the stores that share the same locales.
-* Price Range Filter is not supported with merchant relations. That is why this filter is not included in the [B2B demo shop](/docs/scos/user/intro-to-spryker/b2b-suite.html). However, in the [B2C demo shop](/docs/scos/user/intro-to-spryker/b2c-suite.html), you can still filter the products using the price range filter.
+* Price Range Filter is not supported with merchant relations. That is why this filter is not included in the [B2B demo shop](/docs/about/all/b2b-suite.html). However, in the [B2C demo shop](/docs/about/all/b2c-suite.html), you can still filter the products using the price range filter.
 
 ## Related Business User documents
 
diff --git a/docs/pbc/all/product-information-management/202212.0/marketplace/marketplace-product-approval-process-feature-overview.md b/docs/pbc/all/product-information-management/202212.0/marketplace/marketplace-product-approval-process-feature-overview.md
index 81bd6678408..156548a7c4c 100644
--- a/docs/pbc/all/product-information-management/202212.0/marketplace/marketplace-product-approval-process-feature-overview.md
+++ b/docs/pbc/all/product-information-management/202212.0/marketplace/marketplace-product-approval-process-feature-overview.md
@@ -11,7 +11,7 @@ related:
   - title: Sending the product for approval
     link: docs/pbc/all/product-information-management/page.version/marketplace/manage-in-the-merchant-portal/abstract-products/create-marketplace-abstract-products.html#sending-the-product-for-approval
 ---
-The [marketplace operator](/docs/scos/user/intro-to-spryker/spryker-marketplace/back-office-for-marketplace-operator.html) is primarily responsible for ensuring the quality of data in the marketplace, including merchants, products, and offers. To control those things in the marketplace, the approval mechanism is a key feature.
+The [marketplace operator](/docs/about/all/spryker-marketplace/back-office-for-marketplace-operator.html) is primarily responsible for ensuring the quality of data in the marketplace, including merchants, products, and offers. To control those things in the marketplace, the approval mechanism is a key feature.
 
 The *Marketplace Product Approval Process* allows marketplace owners to verify the products of merchants before showing them to customers.
 
diff --git a/docs/pbc/all/product-information-management/202307.0/base-shop/feature-overviews/category-management-feature-overview.md b/docs/pbc/all/product-information-management/202307.0/base-shop/feature-overviews/category-management-feature-overview.md
index aa345298765..045a64450db 100644
--- a/docs/pbc/all/product-information-management/202307.0/base-shop/feature-overviews/category-management-feature-overview.md
+++ b/docs/pbc/all/product-information-management/202307.0/base-shop/feature-overviews/category-management-feature-overview.md
@@ -70,7 +70,7 @@ The Category Management feature has the following functional constraints, which
 * A store can only be linked to one root category tree, but in the future, a store can have multiple root category trees.
 * Category URLs are locale-dependent.
 * Category URLs are available in all the stores that share the same locales.
-* Price Range Filter is not supported with merchant relations. That is why this filter is not included in the [B2B demo shop](/docs/scos/user/intro-to-spryker/b2b-suite.html). However, in the [B2C demo shop](/docs/scos/user/intro-to-spryker/b2c-suite.html), you can still filter the products using the price range filter.
+* Price Range Filter is not supported with merchant relations. That is why this filter is not included in the [B2B demo shop](/docs/about/all/b2b-suite.html). However, in the [B2C demo shop](/docs/about/all/b2c-suite.html), you can still filter the products using the price range filter.
 
 ## Related Business User documents
 
diff --git a/docs/pbc/all/product-information-management/202307.0/marketplace/marketplace-product-approval-process-feature-overview.md b/docs/pbc/all/product-information-management/202307.0/marketplace/marketplace-product-approval-process-feature-overview.md
index 252fc0b3877..f645d9935ed 100644
--- a/docs/pbc/all/product-information-management/202307.0/marketplace/marketplace-product-approval-process-feature-overview.md
+++ b/docs/pbc/all/product-information-management/202307.0/marketplace/marketplace-product-approval-process-feature-overview.md
@@ -11,7 +11,7 @@ related:
   - title: Sending the product for approval
     link: docs/pbc/all/product-information-management/page.version/marketplace/manage-in-the-merchant-portal/abstract-products/create-marketplace-abstract-products.html#sending-the-product-for-approval
 ---
-The [marketplace operator](/docs/scos/user/intro-to-spryker/spryker-marketplace/back-office-for-marketplace-operator.html) is primarily responsible for ensuring the quality of data in the marketplace, including merchants, products, and offers. To control those things in the marketplace, the approval mechanism is a key feature.
+The [marketplace operator](/docs/about/all/spryker-marketplace/back-office-for-marketplace-operator.html) is primarily responsible for ensuring the quality of data in the marketplace, including merchants, products, and offers. To control those things in the marketplace, the approval mechanism is a key feature.
 
 The *Marketplace Product Approval Process* allows marketplace owners to verify the products of merchants before showing them to customers.
 
diff --git a/docs/pbc/all/product-information-management/202311.0/base-shop/feature-overviews/category-management-feature-overview.md b/docs/pbc/all/product-information-management/202311.0/base-shop/feature-overviews/category-management-feature-overview.md
index b12f2d3df49..d38a23d98c1 100644
--- a/docs/pbc/all/product-information-management/202311.0/base-shop/feature-overviews/category-management-feature-overview.md
+++ b/docs/pbc/all/product-information-management/202311.0/base-shop/feature-overviews/category-management-feature-overview.md
@@ -71,7 +71,7 @@ The Category Management feature has the following functional constraints, which
 * A store can only be linked to one root category tree, but in the future, a store can have multiple root category trees.
 * Category URLs are locale-dependent.
 * Category URLs are available in all the stores that share the same locales.
-* Price Range Filter is not supported with merchant relations. That is why this filter is not included in the [B2B demo shop](/docs/scos/user/intro-to-spryker/b2b-suite.html). However, in the [B2C demo shop](/docs/scos/user/intro-to-spryker/b2c-suite.html), you can still filter the products using the price range filter.
+* Price Range Filter is not supported with merchant relations. That is why this filter is not included in the [B2B demo shop](/docs/about/all/b2b-suite.html). However, in the [B2C demo shop](/docs/about/all/b2c-suite.html), you can still filter the products using the price range filter.
 
 ## Related Business User documents
 
diff --git a/docs/pbc/all/product-information-management/202311.0/base-shop/tutorials-and-howtos/split-products-by-stores.md b/docs/pbc/all/product-information-management/202311.0/base-shop/tutorials-and-howtos/split-products-by-stores.md
index 6baa9fabb0a..20df3721088 100644
--- a/docs/pbc/all/product-information-management/202311.0/base-shop/tutorials-and-howtos/split-products-by-stores.md
+++ b/docs/pbc/all/product-information-management/202311.0/base-shop/tutorials-and-howtos/split-products-by-stores.md
@@ -24,7 +24,7 @@ To separate products by stores, follow the steps below.
 
 ## Prerequisites
 
-This example is convenient to consider on the basis of the [B2C Demo Shop](/docs/scos/user/intro-to-spryker/b2c-suite.html).
+This example is convenient to consider on the basis of the [B2C Demo Shop](/docs/about/all/b2c-suite.html).
 Follow the [installation guide](/docs/dg/dev/set-up-spryker-locally/install-spryker/install/install-in-development-mode-on-macos-and-linux.html) to set it up.
 
 ## 1. Add the AclEntity package to the system
diff --git a/docs/pbc/all/product-information-management/202311.0/marketplace/marketplace-product-approval-process-feature-overview.md b/docs/pbc/all/product-information-management/202311.0/marketplace/marketplace-product-approval-process-feature-overview.md
index 2385831645e..a40d05872d9 100644
--- a/docs/pbc/all/product-information-management/202311.0/marketplace/marketplace-product-approval-process-feature-overview.md
+++ b/docs/pbc/all/product-information-management/202311.0/marketplace/marketplace-product-approval-process-feature-overview.md
@@ -12,7 +12,7 @@ related:
   - title: Sending the product for approval
     link: docs/pbc/all/product-information-management/page.version/marketplace/manage-in-the-merchant-portal/abstract-products/create-marketplace-abstract-products.html#sending-the-product-for-approval
 ---
-The [marketplace operator](/docs/scos/user/intro-to-spryker/spryker-marketplace/back-office-for-marketplace-operator.html) is primarily responsible for ensuring the quality of data in the marketplace, including merchants, products, and offers. To control those things in the marketplace, the approval mechanism is a key feature.
+The [marketplace operator](/docs/about/all/spryker-marketplace/back-office-for-marketplace-operator.html) is primarily responsible for ensuring the quality of data in the marketplace, including merchants, products, and offers. To control those things in the marketplace, the approval mechanism is a key feature.
 
 The *Marketplace Product Approval Process* allows marketplace owners to verify the products of merchants before showing them to customers.
 
diff --git a/docs/pbc/all/product-information-management/202403.0/base-shop/feature-overviews/category-management-feature-overview.md b/docs/pbc/all/product-information-management/202403.0/base-shop/feature-overviews/category-management-feature-overview.md
index b4d6ebf7e23..ba5bd631e87 100644
--- a/docs/pbc/all/product-information-management/202403.0/base-shop/feature-overviews/category-management-feature-overview.md
+++ b/docs/pbc/all/product-information-management/202403.0/base-shop/feature-overviews/category-management-feature-overview.md
@@ -69,7 +69,7 @@ The Category Management feature has the following functional constraints, which
 * A store can only be linked to one root category tree, but in the future, a store can have multiple root category trees.
 * Category URLs are locale-dependent.
 * Category URLs are available in all the stores that share the same locales.
-* Price Range Filter is not supported with merchant relations. That is why this filter is not included in the [B2B demo shop](/docs/scos/user/intro-to-spryker/b2b-suite.html). However, in the [B2C demo shop](/docs/scos/user/intro-to-spryker/b2c-suite.html), you can still filter the products using the price range filter.
+* Price Range Filter is not supported with merchant relations. That is why this filter is not included in the [B2B demo shop](/docs/about/all/b2b-suite.html). However, in the [B2C demo shop](/docs/about/all/b2c-suite.html), you can still filter the products using the price range filter.
 
 ## Related Business User documents
 
diff --git a/docs/pbc/all/search/202212.0/base-shop/search-feature-overview/standard-filters-overview.md b/docs/pbc/all/search/202212.0/base-shop/search-feature-overview/standard-filters-overview.md
index 99b48e9f066..5520b364b05 100644
--- a/docs/pbc/all/search/202212.0/base-shop/search-feature-overview/standard-filters-overview.md
+++ b/docs/pbc/all/search/202212.0/base-shop/search-feature-overview/standard-filters-overview.md
@@ -40,7 +40,7 @@ Products appropriate for the active filters are displayed in the results.
 Filter preferences can be configured in the **Back Office&nbsp;<span aria-label="and then">></span> Search and Filters&nbsp;<span aria-label="and then">></span> Filter Preferences**. Filter options depend on the attributes configured for the products.
 
 ## Current constraints
-Price Range Filter is not supported with the Merchant Relations, that is why this filter is not included in the B2B demo shop. However, in [the B2C demo shop](/docs/scos/user/intro-to-spryker/intro-to-spryker.html#spryker-b2bb2c-demo-shops), you can still filter the products using the price range filter.
+Price Range Filter is not supported with the Merchant Relations, that is why this filter is not included in the B2B demo shop. However, in [the B2C demo shop](/docs/about/all/intro-to-spryker.html#spryker-b2bb2c-demo-shops), you can still filter the products using the price range filter.
 
 ## Related Business User documents
 
diff --git a/docs/pbc/all/search/202307.0/base-shop/search-feature-overview/standard-filters-overview.md b/docs/pbc/all/search/202307.0/base-shop/search-feature-overview/standard-filters-overview.md
index 98452266351..01c67af505e 100644
--- a/docs/pbc/all/search/202307.0/base-shop/search-feature-overview/standard-filters-overview.md
+++ b/docs/pbc/all/search/202307.0/base-shop/search-feature-overview/standard-filters-overview.md
@@ -42,7 +42,7 @@ Products appropriate for the active filters are displayed in the results.
 Filter preferences can be configured in the **Back Office&nbsp;<span aria-label="and then">></span> Search and Filters&nbsp;<span aria-label="and then">></span> Filter Preferences**. Filter options depend on the attributes configured for the products.
 
 ## Current constraints
-Price Range Filter is not supported with the Merchant Relations, that is why this filter is not included in the B2B demo shop. However, in [the B2C demo shop](/docs/scos/user/intro-to-spryker/intro-to-spryker.html#spryker-b2bb2c-demo-shops), you can still filter the products using the price range filter.
+Price Range Filter is not supported with the Merchant Relations, that is why this filter is not included in the B2B demo shop. However, in [the B2C demo shop](/docs/about/all/intro-to-spryker.html#spryker-b2bb2c-demo-shops), you can still filter the products using the price range filter.
 
 ## Related Business User documents
 
diff --git a/docs/pbc/all/search/202311.0/base-shop/search-feature-overview/standard-filters-overview.md b/docs/pbc/all/search/202311.0/base-shop/search-feature-overview/standard-filters-overview.md
index b25b18dd5d8..3a3f6a47b47 100644
--- a/docs/pbc/all/search/202311.0/base-shop/search-feature-overview/standard-filters-overview.md
+++ b/docs/pbc/all/search/202311.0/base-shop/search-feature-overview/standard-filters-overview.md
@@ -43,7 +43,7 @@ Products appropriate for the active filters are displayed in the results.
 Filter preferences can be configured in the **Back Office&nbsp;<span aria-label="and then">></span> Search and Filters&nbsp;<span aria-label="and then">></span> Filter Preferences**. Filter options depend on the attributes configured for the products.
 
 ## Current constraints
-Price Range Filter is not supported with the Merchant Relations, that is why this filter is not included in the B2B demo shop. However, in [the B2C demo shop](/docs/scos/user/intro-to-spryker/intro-to-spryker.html#spryker-b2bb2c-demo-shops), you can still filter the products using the price range filter.
+Price Range Filter is not supported with the Merchant Relations, that is why this filter is not included in the B2B demo shop. However, in [the B2C demo shop](/docs/about/all/intro-to-spryker.html#spryker-b2bb2c-demo-shops), you can still filter the products using the price range filter.
 
 ## Related Business User documents
 
diff --git a/docs/pbc/all/search/202403.0/base-shop/manage-using-glue-api/glue-api-search-the-product-catalog.md b/docs/pbc/all/search/202403.0/base-shop/manage-using-glue-api/glue-api-search-the-product-catalog.md
index b76142fed85..863cb865ecd 100644
--- a/docs/pbc/all/search/202403.0/base-shop/manage-using-glue-api/glue-api-search-the-product-catalog.md
+++ b/docs/pbc/all/search/202403.0/base-shop/manage-using-glue-api/glue-api-search-the-product-catalog.md
@@ -80,7 +80,7 @@ To search by products, send the request:
 | `GET https://glue.mysprykershop.com/catalog-search?q=Sony&sort=name_desc`                          | Set sorting order descending.                                                                                                                           |
 | `GET https://glue.mysprykershop.com/catalog-search?q=Sony&sort=rating`                             | Sort found products by rating.                                                                                                                          |
 | `GET https://glue.mysprykershop.com/catalog-search?q=Sony&sort=price_asc`                          | Sort found products by price ascending.                                                                                                                 |
-| `GET https://glue.mysprykershop.com/catalog-search?q=Sony&sort=popularity`                         | Sort found products by popularity. <br> Available only in the [Master Suite](/docs/scos/user/intro-to-spryker/master-suite.html) for now.   |
+| `GET https://glue.mysprykershop.com/catalog-search?q=Sony&sort=popularity`                         | Sort found products by popularity. <br> Available only in the [Master Suite](/docs/about/all/master-suite.html) for now.   |
 | `GET https://glue.mysprykershop.com/catalog-search?q=Sony&page=3`                                  | Set a page to retrieve the search results from.                                                                                                         |
 | `GET https://glue.mysprykershop.com/catalog-search?q=Sony&ipp=24`                                  | Set number of products per page.                                                                                                                        |
 | `GET https://glue.mysprykershop.com/catalog-search?merchant_name=Spryker`                          | Filter the results by Merchant name. <br> Available only with the Marketplace.** |
diff --git a/docs/pbc/all/warehouse-management-system/202212.0/base-shop/extend-and-customize/manage-stocks-in-a-multi-store-environment-best-practices.md b/docs/pbc/all/warehouse-management-system/202212.0/base-shop/extend-and-customize/manage-stocks-in-a-multi-store-environment-best-practices.md
index ef291a17897..bfe3f19c727 100644
--- a/docs/pbc/all/warehouse-management-system/202212.0/base-shop/extend-and-customize/manage-stocks-in-a-multi-store-environment-best-practices.md
+++ b/docs/pbc/all/warehouse-management-system/202212.0/base-shop/extend-and-customize/manage-stocks-in-a-multi-store-environment-best-practices.md
@@ -68,7 +68,7 @@ There is a console command to export all reservations: `/Spryker/Zed/Oms/Communi
 
 {% info_block infoBox "" %}
 
-This is the default scenario implemented in the [Spryker Demo Shops](/docs/scos/user/intro-to-spryker/intro-to-spryker.html).
+This is the default scenario implemented in the [Spryker Demo Shops](/docs/about/all/intro-to-spryker.html).
 
 {% endinfo_block %}
 
diff --git a/docs/pbc/all/warehouse-management-system/202212.0/marketplace/manage-availability.md b/docs/pbc/all/warehouse-management-system/202212.0/marketplace/manage-availability.md
index fc1f945746a..e3a623fa9fb 100644
--- a/docs/pbc/all/warehouse-management-system/202212.0/marketplace/manage-availability.md
+++ b/docs/pbc/all/warehouse-management-system/202212.0/marketplace/manage-availability.md
@@ -25,7 +25,7 @@ For multi-store projects, you can filter the products according to the store the
 
 {% info_block infoBox "Info" %}
 
-For the [Marketplace](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-concept.html) project, you can also filter the products according to the merchant the product belongs to.
+For the [Marketplace](/docs/about/all/spryker-marketplace/marketplace-concept.html) project, you can also filter the products according to the merchant the product belongs to.
 
 {% endinfo_block %}
 
@@ -51,7 +51,7 @@ The **Abstract Product** contains a drop-down list where you can select the stor
 
 {% info_block infoBox "Info" %}
 
-For the [Marketplace](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-concept.html) project, a merchant name is available for a specific product. The availability of a certain merchant warehouse is provided.
+For the [Marketplace](/docs/about/all/spryker-marketplace/marketplace-concept.html) project, a merchant name is available for a specific product. The availability of a certain merchant warehouse is provided.
 
 {% endinfo_block %}
 
diff --git a/docs/pbc/all/warehouse-management-system/202307.0/base-shop/extend-and-customize/manage-stocks-in-a-multi-store-environment-best-practices.md b/docs/pbc/all/warehouse-management-system/202307.0/base-shop/extend-and-customize/manage-stocks-in-a-multi-store-environment-best-practices.md
index 207108c56f0..32aea1dbe14 100644
--- a/docs/pbc/all/warehouse-management-system/202307.0/base-shop/extend-and-customize/manage-stocks-in-a-multi-store-environment-best-practices.md
+++ b/docs/pbc/all/warehouse-management-system/202307.0/base-shop/extend-and-customize/manage-stocks-in-a-multi-store-environment-best-practices.md
@@ -68,7 +68,7 @@ There is a console command to export all reservations: `/Spryker/Zed/Oms/Communi
 
 {% info_block infoBox "" %}
 
-This is the default scenario implemented in the [Spryker Demo Shops](/docs/scos/user/intro-to-spryker/intro-to-spryker.html).
+This is the default scenario implemented in the [Spryker Demo Shops](/docs/about/all/intro-to-spryker.html).
 
 {% endinfo_block %}
 
diff --git a/docs/pbc/all/warehouse-management-system/202307.0/marketplace/manage-availability.md b/docs/pbc/all/warehouse-management-system/202307.0/marketplace/manage-availability.md
index fc1f945746a..e3a623fa9fb 100644
--- a/docs/pbc/all/warehouse-management-system/202307.0/marketplace/manage-availability.md
+++ b/docs/pbc/all/warehouse-management-system/202307.0/marketplace/manage-availability.md
@@ -25,7 +25,7 @@ For multi-store projects, you can filter the products according to the store the
 
 {% info_block infoBox "Info" %}
 
-For the [Marketplace](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-concept.html) project, you can also filter the products according to the merchant the product belongs to.
+For the [Marketplace](/docs/about/all/spryker-marketplace/marketplace-concept.html) project, you can also filter the products according to the merchant the product belongs to.
 
 {% endinfo_block %}
 
@@ -51,7 +51,7 @@ The **Abstract Product** contains a drop-down list where you can select the stor
 
 {% info_block infoBox "Info" %}
 
-For the [Marketplace](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-concept.html) project, a merchant name is available for a specific product. The availability of a certain merchant warehouse is provided.
+For the [Marketplace](/docs/about/all/spryker-marketplace/marketplace-concept.html) project, a merchant name is available for a specific product. The availability of a certain merchant warehouse is provided.
 
 {% endinfo_block %}
 
diff --git a/docs/pbc/all/warehouse-management-system/202311.0/base-shop/extend-and-customize/manage-stocks-in-a-multi-store-environment-best-practices.md b/docs/pbc/all/warehouse-management-system/202311.0/base-shop/extend-and-customize/manage-stocks-in-a-multi-store-environment-best-practices.md
index 658ce1a6887..f179f1b54ad 100644
--- a/docs/pbc/all/warehouse-management-system/202311.0/base-shop/extend-and-customize/manage-stocks-in-a-multi-store-environment-best-practices.md
+++ b/docs/pbc/all/warehouse-management-system/202311.0/base-shop/extend-and-customize/manage-stocks-in-a-multi-store-environment-best-practices.md
@@ -69,7 +69,7 @@ There is a console command to export all reservations: `/Spryker/Zed/Oms/Communi
 
 {% info_block infoBox "" %}
 
-This is the default scenario implemented in the [Spryker Demo Shops](/docs/scos/user/intro-to-spryker/intro-to-spryker.html).
+This is the default scenario implemented in the [Spryker Demo Shops](/docs/about/all/intro-to-spryker.html).
 
 {% endinfo_block %}
 
diff --git a/docs/pbc/all/warehouse-management-system/202311.0/marketplace/manage-availability.md b/docs/pbc/all/warehouse-management-system/202311.0/marketplace/manage-availability.md
index fc1f945746a..e3a623fa9fb 100644
--- a/docs/pbc/all/warehouse-management-system/202311.0/marketplace/manage-availability.md
+++ b/docs/pbc/all/warehouse-management-system/202311.0/marketplace/manage-availability.md
@@ -25,7 +25,7 @@ For multi-store projects, you can filter the products according to the store the
 
 {% info_block infoBox "Info" %}
 
-For the [Marketplace](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-concept.html) project, you can also filter the products according to the merchant the product belongs to.
+For the [Marketplace](/docs/about/all/spryker-marketplace/marketplace-concept.html) project, you can also filter the products according to the merchant the product belongs to.
 
 {% endinfo_block %}
 
@@ -51,7 +51,7 @@ The **Abstract Product** contains a drop-down list where you can select the stor
 
 {% info_block infoBox "Info" %}
 
-For the [Marketplace](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-concept.html) project, a merchant name is available for a specific product. The availability of a certain merchant warehouse is provided.
+For the [Marketplace](/docs/about/all/spryker-marketplace/marketplace-concept.html) project, a merchant name is available for a specific product. The availability of a certain merchant warehouse is provided.
 
 {% endinfo_block %}
 

From 08ed9956570539a6f0c8951e02fde51cebafa4ac Mon Sep 17 00:00:00 2001
From: Andrii Tserkovnyi <andrii.tserkovnyi@spryker.com>
Date: Tue, 12 Mar 2024 15:52:45 +0200
Subject: [PATCH 11/26] Update about-spryker.md

---
 docs/about/all/about-spryker.md | 88 ++++++++++++++++++++-------------
 1 file changed, 53 insertions(+), 35 deletions(-)

diff --git a/docs/about/all/about-spryker.md b/docs/about/all/about-spryker.md
index e02363f6e12..1154e8c90b7 100644
--- a/docs/about/all/about-spryker.md
+++ b/docs/about/all/about-spryker.md
@@ -22,69 +22,87 @@ redirect_from:
 
 ---
 
-The Spryker Cloud Commerce OS (SCCOS) is a completely modular B2B and B2C e-commerce technology. With the modular application and API-based integration with all possible customer touchpoints (front-ends), Spryker provides significantly shorter time-to-market and reduced total cost of ownership, while increasing your ROI due to the digital best practices.
+
+
+Spryker Cloud Commerce OS (SCCOS) is a completely modular e-commerce technology. With the modular design and API-based integration with all possible touchpoints, Spryker supports most business models: B2B, B2C, and marketplace.
+
 ![image](https://spryker.s3.eu-central-1.amazonaws.com/docs/About/About+Spryker/Spryker-OS-Overview-RGB-JULY19_Spryker-OS-Overview.png)
 
-We establish a unique advantage for our customers by creating a commerce operating system that revolves around two cornerstones for success: modular and layered architectures.
 
 ## Modular architecture
 
-Modular architecture, or modularity of the Spryker Commerce OS, means that the system is composed of small parts called modules. The Spryker Commerce OS consists of over 750 modules. Some of them are mandatory and required by the OS to run, but many are optional and designed to provide certain functionality or connectivity to either internal or external systems.
-The modules combine to create features and have limited dependencies. The limited dependencies imply less development effort, increasing your return on investment and lowering the total cost of ownership.
+Modular architecture or modularity means that the system is composed of small parts called modules. A module is the smalles functionality unit in Spryker. Some modules are required to run Spryker, but many are optional and  provide certain functionality or connectivity to internal or external systems. Spryker consists of over 750 modules.
 
-![image](https://spryker.s3.eu-central-1.amazonaws.com/docs/About/About+Spryker/modularity_transparent.png)
+Modules combine into features and have limited dependencies. Limited dependencies result in less development effort, increasing your return on investment and lowering the total cost of ownership.
 
-Spryker's code is stored on GitHub under the [Spryker repository](https://github.com/spryker). Here you can find a complete list of all the modules, along with a description and a link to the relevant documentation for each module.
+![image](https://spryker.s3.eu-central-1.amazonaws.com/docs/About/About+Spryker/modularity_transparent.png)
 
+For a complete list of modules, see the [Spryker repository](https://github.com/spryker).
 
-### Benefits of the Spryker modular architecture:
+### Benefits of the modular architecture
 
-* You *take only the modules or features that you need* for your project, without overloading it with redundant code and investing effort in something you don’t need.
-* You can *grow a project easily* using any of the wide selection of modules.
-* You can *add, delete, and test new features* without worrying about breaking or pausing your production shop site.
-* We adhere to the atomic release approach. This means that each module is released independently and has its own version. It is developed and tested so as to ensure backward compatibility with other modules that you might not want to update. This means you can *take new and update existing modules or features right after they have been released*.
+* You take only the modules or features needed for your project, without overloading it with redundant code and investing effort into something you don’t need.
+* You can easily grow your project by adding new modules at any time.
+* You can add, delete, and test new features without worrying about breaking or pausing your live shop.
+* Thanks to the atomic release approach, each module is released independently, has its own version, and is backward compatible. You can install and update the needed modules right after they are released without having to update any other installed modules.
 
 ## Layered architecture
 
-Layered Architecture is used to separate your commercial offering and sales channels.
-When your commercial offering is hooked directly to an online web store, expanding to different channels and methods of selling poses a huge challenge in most cases. If you create a clear separation between what you are selling and how you are selling it, you gain the freedom and flexibility in choosing sales methods and channels.
-Separation is established by using layers.
+Layered architecture separates your commercial offering and sales channels. When your commercial offering is hooked directly to an online web store, expanding to different channels and methods of selling poses a huge challenge in most cases. Spryker lets you create a clear separation between what you are selling and how you are selling it, so you get the flexibility in choosing sales methods and channels.
 
-SCOS is split into four different layers:
+Spryker is split into four different layers:
 
-* The *presentation layer* is a selling point that can be an online store, a mobile app, a voice skill, and anything else used to effectuate a commercial transaction.
+* The *presentation layer* is a selling point that can be an online store, a mobile app, a voice skill, and anything else used to fulfill a commercial transaction.
 * The *business layer* includes your products, pricing, stock, and general information surrounding your commercial offering.
 * The *communication layer* connects the presentation layer to the business layer and transfers information between the business layer and the different presentation layers you may have.
 * The *persistence layer* covers all the data storage and processing, such as database queries and advanced calculations.
 
-<!---![Spryker layers](https://spryker.s3.eu-central-1.amazonaws.com/docs/About/About+Spryker/spryker_layers.png)-->
-
-![image](https://spryker.s3.eu-central-1.amazonaws.com/docs/About/About+Spryker/spryker_layers_s.png)
+![spryker-layers](https://spryker.s3.eu-central-1.amazonaws.com/docs/About/About+Spryker/spryker_layers_s.png)
 
 
 ### Benefits of the layered architecture
 
-* We confine long and resource-intensive processes to the Business and Persistence layers, which ensures *high performance*. The presentation side is separated from the rest of the OS to make sure that only lean processes are executed there. Basically, anything that can wait or can impact the purchase process is offloaded to an area that does not impact the performance.
-* Separate front- and back-end means *developers can work in parallel*, allowing for faster implementation, testing, and better optimization—all for less internal cost.
-* Since your commercial offering is not dependent on a single channel, you can *focus your effort on growth and improvement*, rather than on solutions, extensions, and sometimes hacks to “make things work”.
-* The separation ensures that *essential information is not tied-up with the presentation*. You can easily swap out, extend, replace this information, as well as change the ways it is presented.
+* We confine long and resource-intensive processes to the business and persistence layers, which ensures high performance on the presentation layer. The presentation side is separated from the rest of the OS to make sure that only lean processes are executed there. Anything that can impact the purchase process is offloaded to an area that does not impact the performance.
+* Separate frontend and backend means developers can work in parallel, allowing for faster implementation, testing, and better optimization—all for less internal cost.
+* Because your commercial offering is not dependent on a single channel, you can focus your effort on growth and improvement, rather than on solutions, extensions, and sometimes workarounds to make things work.
+* Essential information is not tied up with the presentation. You can easily swap out, extend, replace this information, as well as change the ways it is presented.
 
-## Spryker B2B and B2C Demo Shops
 
-Our [B2B](/docs/about/all/b2b-suite.html) and [B2C Demo Shops](/docs/about/all/b2c-suite.html) showcase Spryker functionality and help you choose the best possible starting point and set of features based on your business needs. The Demo Shops pose a clear starting point and upgrade path for everything you base your project on. We ship our B2B/B2C Demo Shops as a part of the product, covered by the same commercial license and the same support and LTS (long-term support) rules as individual Spryker Commerce OS modules.
+## Managed cloud platform
 
-## I am a new customer, where should I start?
+Being a managed cloud platform, Spryker lets you develop applications without spending resources on setting up, managing, and scaling the infrastructure. All the cloud environments, like staging, development, and production, are provided during the onboarding. Included CI/CD tools and deployment pipelines enable your team to efficiently develop, test, and deploy your applications.
 
-The recommended starting points for all standard commerce projects are our [B2B](/docs/about/all/b2b-suite.html#b2b-demo-shop) and [B2C Demo Shops](/docs/about/all/b2c-suite.html#b2c-demo-shop). We have taken the time to identify the best combination of modules and functionalities for each particular business type and to keep development as lean as possible. Thus, the only thing that remains is to identify your business requirements and select the shop that fits your needs best.
+We take care of the infrastructure security and provide you with guidelines for keeping your project secure. Our 24/7 support team monitors your applications and informs you about potential issues to avoid downtimes.  
 
-Apart from that, if your business case does not fit in one of the proposed models, you can start building your project by cherry-picking the modules you need. Since they are released under a commercial license with stable and predictable release cycles, you can build your e-commerce business with reliance and certainty. Our engineers make sure that each module is reliable, backward compatible, and fully regression-tested, and all our releases are supported with an LTS flag (12 months).
+### Benefits of cloud
 
-## Next steps
+* Infrastructure scales with your project and traffic
+* Increased speed
+* Better control over costs
+* Enhanced security
+* CI/CD pipelines speed up development
+* Flexible management of resources
+
+## Customizable system
 
-Select one of the topics below depending on what you want to do next:
+Being highly customizable at its core, Spryker is designed to cater the the most complex use cases. The functionality shipped by default can be extended and customized. Each module is released with an extension point so you can adjust it to your needs. On top of customizing the existing functionality, you can introduce completely new components.
+
+Glue API enables you to integrate any external systems and touchpoints, making your shop an all-in-one commerce system.
+
+## Demo Shops
+
+Demo Shops are fully functional shops with collections of features that match different business models. They serve as a starting point and let you quickly get started with the development of your project.
+
+If you want to check out how Spryker works, Demo Shops also quick to install on your machine. The following Demo Shops are available:
+
+* [B2B](/docs/scos/user/intro-to-spryker/b2b-suite.html)
+* [B2C Demo Shops](/docs/scos/user/intro-to-spryker/b2c-suite.html)
+* [Marketplace B2B Suite](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2b-suite.html)
+* [Marketplace B2C Suite](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2c-suite.html)
+
+Demo Shops are covered by the same commercial license and the same support and long-term support rules as individual modules.
+
+## Next steps
 
-* [What's new](/docs/about/all/whats-new/whats-new.html): general information about Spryker, news, and release notes.
-* [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/dg/dev/development-getting-started-guide.html): technical information and guides for developers.
+* To start developing your project or check out how Spryker works, [set up Spryker locally](/docs/dg/dev/set-up-spryker-locally/set-up-spryker-locally.html).
+* For the catalog of functionality and related guides, see [Packaged Business Capabilities](/docs/pbc/all/pbc.html).

From 7ed7279ac8262cae9e914786f9e9f1be415ea101 Mon Sep 17 00:00:00 2001
From: Andrii Tserkovnyi <andrii.tserkovnyi@spryker.com>
Date: Tue, 12 Mar 2024 15:57:52 +0200
Subject: [PATCH 12/26] Update about-spryker.md

---
 docs/about/all/about-spryker.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/about/all/about-spryker.md b/docs/about/all/about-spryker.md
index 1154e8c90b7..4d6ae64a805 100644
--- a/docs/about/all/about-spryker.md
+++ b/docs/about/all/about-spryker.md
@@ -74,7 +74,7 @@ Being a managed cloud platform, Spryker lets you develop applications without sp
 
 We take care of the infrastructure security and provide you with guidelines for keeping your project secure. Our 24/7 support team monitors your applications and informs you about potential issues to avoid downtimes.  
 
-### Benefits of cloud
+### Benefits of cloud infrastructure
 
 * Infrastructure scales with your project and traffic
 * Increased speed

From 15a73d50008979d789399da1741428f880836021 Mon Sep 17 00:00:00 2001
From: Andrii Tserkovnyi <andrii.tserkovnyi@spryker.com>
Date: Tue, 12 Mar 2024 16:01:58 +0200
Subject: [PATCH 13/26] Update about-spryker.md

---
 docs/about/all/about-spryker.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/about/all/about-spryker.md b/docs/about/all/about-spryker.md
index 4d6ae64a805..00711428693 100644
--- a/docs/about/all/about-spryker.md
+++ b/docs/about/all/about-spryker.md
@@ -96,9 +96,9 @@ Demo Shops are fully functional shops with collections of features that match di
 If you want to check out how Spryker works, Demo Shops also quick to install on your machine. The following Demo Shops are available:
 
 * [B2B](/docs/scos/user/intro-to-spryker/b2b-suite.html)
-* [B2C Demo Shops](/docs/scos/user/intro-to-spryker/b2c-suite.html)
-* [Marketplace B2B Suite](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2b-suite.html)
-* [Marketplace B2C Suite](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2c-suite.html)
+* [B2C](/docs/scos/user/intro-to-spryker/b2c-suite.html)
+* [Marketplace B2B](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2b-suite.html)
+* [Marketplace B2C](/docs/scos/user/intro-to-spryker/spryker-marketplace/marketplace-b2c-suite.html)
 
 Demo Shops are covered by the same commercial license and the same support and long-term support rules as individual modules.
 

From 9564337b4bf8746701775c6ad82dd954c5791f14 Mon Sep 17 00:00:00 2001
From: Andrii Tserkovnyi <andrii.tserkovnyi@spryker.com>
Date: Tue, 12 Mar 2024 16:52:27 +0200
Subject: [PATCH 14/26] links

---
 _data/sidebars/about_all_sidebar.yml          | 22 +++++++++----------
 docs/about/all/b2c-suite.md                   | 12 +---------
 .../all/releases/product-and-code-releases.md |  2 +-
 docs/ca/dev/preparation-for-going-live.md     |  2 +-
 ...oning-major-vs.-minor-vs.-patch-release.md |  2 +-
 ...nstalling-features-and-updating-modules.md |  2 +-
 6 files changed, 16 insertions(+), 26 deletions(-)

diff --git a/_data/sidebars/about_all_sidebar.yml b/_data/sidebars/about_all_sidebar.yml
index aa728c30d42..8e5b836dbea 100644
--- a/_data/sidebars/about_all_sidebar.yml
+++ b/_data/sidebars/about_all_sidebar.yml
@@ -8,29 +8,29 @@ entries:
       url: /docs/about/all/releases/product-and-code-releases.html
       nested:
       - title: Security release notes 202312.0
-        url: /docs/about/all/releases/release-notes/security-release-notes-202312.0.html
+        url: /docs/about/all/releases/security-release-notes-202312.0.html
       - title: Release notes 202311.0
-        url: /docs/about/all/releases/release-notes/release-notes-202311.0.html
+        url: /docs/about/all/releases/release-notes-202311.0.html
       - title: Security release notes 202309.0
-        url: /docs/about/all/releases/release-notes/security-release-notes-202309.0.html
+        url: /docs/about/all/releases/security-release-notes-202309.0.html
       - title: Release notes 202307.0
-        url: /docs/about/all/releases/release-notes/release-notes-202307.0.html
+        url: /docs/about/all/releases/release-notes-202307.0.html
         nested:
         - title: Security release notes 202307.0
-          url: /docs/about/all/releases/release-notes/release-notes-202307.0/security-release-notes-202307.0.html
+          url: /docs/about/all/releases/release-notes-202307.0/security-release-notes-202307.0.html
       - title: Security release notes 202306.0
-        url: /docs/about/all/releases/release-notes/security-release-notes-202306.0.html
+        url: /docs/about/all/releases/security-release-notes-202306.0.html
       - title: Security release notes 202304.0
-        url: /docs/about/all/releases/release-notes/release-notes-202304.0/security-release-notes-202304.0.html
+        url: /docs/about/all/releases/release-notes-202304.0/security-release-notes-202304.0.html
       - title: Security release notes 202302.0
-        url: /docs/about/all/releases/release-notes/release-notes-202302.0/security-release-notes-202302.0.html
+        url: /docs/about/all/releases/release-notes-202302.0/security-release-notes-202302.0.html
       - title: Release notes 202212.0
-        url: /docs/about/all/releases/release-notes/release-notes-202212.0/release-notes-202212.0.html
+        url: /docs/about/all/releases/release-notes-202212.0/release-notes-202212.0.html
         nested:
         - title: Patch releases 202212.0
-          url: /docs/about/all/releases/release-notes/release-notes-202212.0/patch-releases-202212.0.html
+          url: /docs/about/all/releases/release-notes-202212.0/patch-releases-202212.0.html
         - title: Security release notes 202212.0
-          url: /docs/about/all/releases/release-notes/release-notes-202212.0/security-release-notes-202212.0.html
+          url: /docs/about/all/releases/release-notes-202212.0/security-release-notes-202212.0.html
 
     - title: Security audit reports
       nested:
diff --git a/docs/about/all/b2c-suite.md b/docs/about/all/b2c-suite.md
index cb280ecb5fd..767067680a2 100644
--- a/docs/about/all/b2c-suite.md
+++ b/docs/about/all/b2c-suite.md
@@ -1,4 +1,3 @@
-  - /docs/scos/user/intro-to-spryker/b2c-suite.html
 ---
 title: B2C Suite
 description: The Spryker B2C Suite is a showcase that demonstrates ready-to-use B2C-specific Spryker features in a live implementation.
@@ -7,16 +6,7 @@ template: concept-topic-template
 originalLink: https://documentation.spryker.com/2021080/docs/b2c-suite
 originalArticleId: 6d82adcb-2778-4f70-9c44-4463851a1d38
 redirect_from:
-  - /2021080/docs/b2c-suite
-  - /2021080/docs/en/b2c-suite
-  - /docs/b2c-suite
-  - /docs/en/b2c-suite
-  - /v5/docs/b2c-suite
-  - /v5/docs/en/b2c-suite
-  - /v4/docs/b2c-suite
-  - /v4/docs/en/b2c-suite
-  - /v6/docs/b2c-suite
-  - /v6/docs/en/b2c-suite
+- /docs/scos/user/intro-to-spryker/b2c-suite.html
 related:
   - title: B2B Suite
     link: docs/about/all/b2b-suite.html
diff --git a/docs/about/all/releases/product-and-code-releases.md b/docs/about/all/releases/product-and-code-releases.md
index a7c0e68d315..b457a7ec80a 100644
--- a/docs/about/all/releases/product-and-code-releases.md
+++ b/docs/about/all/releases/product-and-code-releases.md
@@ -74,4 +74,4 @@ To receive the security updates, please request the subsription at [support@spry
 
 ## Next steps
 
-* [Release notes](/docs/about/all/releases/release-notes/release-notes.html)
+* [Release notes](/docs/about/all/releases/product-and-code-releases.html)
diff --git a/docs/ca/dev/preparation-for-going-live.md b/docs/ca/dev/preparation-for-going-live.md
index 22dc367aa28..9ebbbd844f4 100644
--- a/docs/ca/dev/preparation-for-going-live.md
+++ b/docs/ca/dev/preparation-for-going-live.md
@@ -50,7 +50,7 @@ After pointing the domain name to your Spryker project, some of your customers m
 
 ### Application
 
-- Upgrade your project's code to the [latest Demo Shop release](/docs/about/all/releases/release-notes/release-notes.html). Or at least upgrade to a release that fully supports the Docker SDK (202009.0 and later).
+- Upgrade your project's code to the [latest Demo Shop release](/docs/about/all/releases/product-and-code-releases.html). Or at least upgrade to a release that fully supports the Docker SDK (202009.0 and later).
 - Update `spryker/twig` to version 3.15.2 or later because this and later versions have important stability improvements over version 3.15.1.
 - Migrate the project's database to MariaDB.
 - Split the project's Zed endpoints as described in [Integrating separate endpoint bootstraps](/docs/scos/dev/technical-enhancement-integration-guides/integrating-separate-endpoint-bootstraps.html).
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 0c86722113a..5eb2001d008 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
@@ -54,7 +54,7 @@ Usually, you need to run `composer update` to get Spryker Core updates, because
 
 {% info_block infoBox %}
 
-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/about/all/releases/release-notes/release-notes.html) published after the project's start.
+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/about/all/releases/product-and-code-releases.html) published after the project's start.
 
 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).
 
diff --git a/docs/dg/dev/updating-spryker/installing-features-and-updating-modules.md b/docs/dg/dev/updating-spryker/installing-features-and-updating-modules.md
index 5e703eb30e4..57dfa995303 100644
--- a/docs/dg/dev/updating-spryker/installing-features-and-updating-modules.md
+++ b/docs/dg/dev/updating-spryker/installing-features-and-updating-modules.md
@@ -59,7 +59,7 @@ Sometimes, you may want to install a feature of a version higher than that of yo
 
 A new feature may require a higher major version of a specific module. In this case, do a [single module update](#update-to-a-major-versions-and-install-new-packages).
 
-You can learn about new Spryker features from the [release notes](/docs/about/all/releases/release-notes/release-notes.html). Not to miss new release notes, we recommend [subscribing to our release newsletter](/docs/about/all/releases/releases.html).
+You can learn about new Spryker features from the [release notes](/docs/about/all/releases/product-and-code-releases.html). Not to miss new release notes, we recommend [subscribing to our release newsletter](/docs/about/all/releases/releases.html).
 
 ## Next steps
 

From 6be71f10886dac7d724a6ad70e8b1c76d1945a17 Mon Sep 17 00:00:00 2001
From: Andrii Tserkovnyi <andrii.tserkovnyi@spryker.com>
Date: Thu, 14 Mar 2024 16:21:19 +0200
Subject: [PATCH 15/26] links

---
 docs/about/all/docs-updates.md                | 20 +++++++++----------
 docs/dg/dev/acp/acp-overview.md               |  2 +-
 .../app-composition-platform-installation.md  | 10 +++++-----
 .../dev/development-getting-started-guide.md  |  2 +-
 .../feature-or-module-updates.md              |  2 +-
 .../dev/updating-spryker/updating-spryker.md  |  2 +-
 6 files changed, 19 insertions(+), 19 deletions(-)

diff --git a/docs/about/all/docs-updates.md b/docs/about/all/docs-updates.md
index 2463e32c0ff..0fcee5f1066 100644
--- a/docs/about/all/docs-updates.md
+++ b/docs/about/all/docs-updates.md
@@ -166,7 +166,7 @@ In December 2023, we have added and updated the following pages:
 - [Decoupled Glue infrastructure: Integrate the authentication](/docs/dg/dev/upgrade-and-migrate/migrate-to-decoupled-glue-infrastructure/decoupled-glue-infrastructure-integrate-the-authentication.html): Learn how to create an authentication token for the Storefront and Backend API applications in a Spryker project.
 - [Create Glue API authorization strategies](/docs/dg/dev/glue-api/202311.0/create-glue-api-authorization-strategies.html): Learn how to create a new authorization strategy.
 - [Preparation for going live](/docs/ca/dev/preparation-for-going-live.html): Learn how to prepare a Spryker project for going live.
-- [Security release notes 202312.0](/docs/about/all/releases/release-notes/security-release-notes-202312.0.html).
+- [Security release notes 202312.0](/docs/about/all/releases/security-release-notes-202312.0.html).
 - [Checkout feature overview](/docs/pbc/all/cart-and-checkout/202404.0/base-shop/feature-overviews/checkout-feature-overview/checkout-feature-overview.html).
 - [Install the Checkout Glue API](/docs/pbc/all/cart-and-checkout/202404.0/base-shop/install-and-upgrade/install-glue-api/install-the-checkout-glue-api.html).
 - [Shipment feature overview](/docs/pbc/all/carrier-management/202311.0/base-shop/shipment-feature-overview.html).
@@ -248,8 +248,8 @@ In November 2023, we have added and updated the following pages:
 - [Backend API Marketplace B2C Demo Shop reference](/docs/dg/dev/glue-api/202311.0/backend-glue-infrastructure/backend-api-marketplace-b2c-demo-shop-reference.html).
 - [REST API Marketplace B2B Demo Shop reference](/docs/dg/dev/glue-api/202311.0/old-glue-infrastructure/rest-api-marketplace-b2b-demo-shop-reference.html).
 - [REST API Marketplace B2C Demo Shop reference](/docs/dg/dev/glue-api/202311.0/old-glue-infrastructure/rest-api-marketplace-b2c-demo-shop-reference.html).
-- [Release notes 202311.0](/docs/about/all/releases/release-notes/release-notes-202311.0/release-notes-202311.0.html).
-- [Security release notes 202312.0](/docs/about/all/releases/release-notes/security-release-notes-202312.0.html).
+- [Release notes 202311.0](/docs/about/all/releases/release-notes-202311.0/release-notes-202311.0.html).
+- [Security release notes 202312.0](/docs/about/all/releases/security-release-notes-202312.0.html).
 
 ### Updated pages
 
@@ -277,7 +277,7 @@ In October 2023, we have added and updated the following pages:
 - [Data Exchange](/docs/pbc/all/data-exchange/202311.0/data-exchange.html): Get an overview of the Data Exchange features: Data Importers and Data Exporters, Data Exchange API, Spryker Middleware powered by Alumio.
 - [Data Exchange FAQ](/docs/pbc/all/data-exchange/202311.0/data-exchange-faq.html).
 - [Install the Data Exchange API + Inventory Management feature](/docs/pbc/all/data-exchange/202311.0/install-and-upgrade/install-the-data-exchange-api-inventory-management-feature.html).
-- [Security release notes 202309.0](/docs/about/all/releases/release-notes/security-release-notes-202309.0.html).
+- [Security release notes 202309.0](/docs/about/all/releases/security-release-notes-202309.0.html).
 - [Upgrade the Chart module](/docs/pbc/all/back-office/202307.0/install-and-upgrade/upgrade-the-chart-module.html): Learn how to upgrade the Chart module from version 1.5.0 to version 1.6.1.
 - Oryx components docs:
     - [Oryx: Building components](/docs/dg/dev/frontend-development/202307.0/oryx/building-components/oryx-building-components.html): Learn about the building blocks of the Oryx applications: the components.
@@ -368,8 +368,8 @@ In August 2023, we have added and updated the following pages:
 ### New pages
 
 - [HowTo: Reduce Jenkins execution by up to 80% without P&S and Data importers refactoring](/docs/dg/dev/backend-development/cronjobs/optimizing-jenkins-execution.html): Learn how to save Jenkins-related costs or speed up background jobs processing by implementing a single custom worker for all stores.
-- [Release notes 202307.0](/docs/about/all/releases/release-notes/release-notes-202307.0/release-notes-202307.0.html).
-- [Security release notes 202307.0](/docs/about/all/releases/release-notes/release-notes-202307.0/security-release-notes-202307.0.html).
+- [Release notes 202307.0](/docs/about/all/releases/release-notes-202307.0/release-notes-202307.0.html).
+- [Security release notes 202307.0](/docs/about/all/releases/release-notes-202307.0/security-release-notes-202307.0.html).
 - [Spryker security checker](/docs/dg/dev/guidelines/keeping-a-project-upgradable/upgradability-guidelines/spryker-security-checker.html): Learn how to check for security fixes in the Spryker modules.
 - [Open-source vulnerabilities checker](/docs/dg/dev/guidelines/keeping-a-project-upgradable/upgradability-guidelines/open-source-vulnerabilities.html): Learn how to check if your PHP application depends on PHP packages with known security vulnerabilities.
 - [Dynamic multistore docs](/docs/pbc/all/dynamic-multistore/202307.0/dynamic-multistore.html):
@@ -414,7 +414,7 @@ In July 2023, we have added and updated the following pages:
 - [Oryx: Color system](/docs/dg/dev/frontend-development/202212.0/oryx/building-applications/styling/oryx-color-system.html): Documentation on colors in Oryx.
 - [Best practises: Jenkins stability](/docs/ca/dev/best-practices/best-practises-jenkins-stability.html): Best practices for maintaining Jenkins stability.
 - [HowTo: Reduce Jenkins execution by up to 80% without P&S and Data importers refactoring](/docs/dg/dev/backend-development/cronjobs/optimizing-jenkins-execution.html): Save Jenkins-related costs or speed up background jobs processing by implementing a single custom Worker for all stores.
-- [Release notes 202307.0](/docs/about/all/releases/release-notes/release-notes-202307.0/release-notes-202307.0.html): Release notes for the Spryker SCOS release 202307.0
+- [Release notes 202307.0](/docs/about/all/releases/release-notes-202307.0/release-notes-202307.0.html): Release notes for the Spryker SCOS release 202307.0
 - [Install the Product Rating and Reviews Glue API](/docs/pbc/all/ratings-reviews/202307.0/install-and-upgrade/install-the-product-rating-and-reviews-glue-api.html): This document describes how to integrate the [Product Rating and Reviews](/docs/pbc/all/ratings-reviews/{{site.version}}/ratings-and-reviews.html) Glue API feature into a Spryker project.
 - [Configure Usercentrics](/docs/pbc/all/usercentrics/configure-usercentrics.html): Find out how you can configure Usercentrics in your Spryker shop.
 - [Ratings and Reviews data import](/docs/pbc/all/ratings-reviews/202204.0/import-and-export-data/ratings-and-reviews-data-import.html): Details about data import files for the Ratings and Reviews PBC.
@@ -427,7 +427,7 @@ In July 2023, we have added and updated the following pages:
 - [Integrate Usercentrics](/docs/pbc/all/usercentrics/integrate-usercentrics.html): Find out how you can integrate Usercentrics in your Spryker shop.
 - [Usercentrics](/docs/pbc/all/usercentrics/usercentrics.html): [Usercentrics](https://usercentrics.com/) is the Consent Management Platform (CMP) that lets you obtain and manage the consent of your users to use cookies across your store.
 - [Adding variables in the parameter store](/docs/ca/dev/add-variables-in-the-parameter-store.html): Added reserved variable sub-section and removed deprecated text.
-- [Security Release Notes 202306.0](/docs/about/all/releases/release-notes/release-notes-202306.0/security-release-notes-202306.0.html): Added missing security HTTP headers.
+- [Security Release Notes 202306.0](/docs/about/all/releases/release-notes-202306.0/security-release-notes-202306.0.html): Added missing security HTTP headers.
 - [Merchant Users Overview](/docs/pbc/all/merchant-management/202212.0/marketplace/marketplace-merchant-feature-overview/merchant-users-overview.html): Added information about the assignment of groups for the merchant user.
 - [Handle data with Publish and Synchronization](/docs/dg/dev/backend-development/data-manipulation/data-publishing/handle-data-with-publish-and-synchronization.html): Publish and Synchronization (P&S) lets you export data from Spryker backend (Zed) to external endpoints.
 - [Install the Spryker Core feature](/docs/pbc/all/miscellaneous/202307.0/install-and-upgrade/install-features/install-the-spryker-core-feature.html): Updated code sample.
@@ -450,7 +450,7 @@ For more details about these and other updates to the Spryker docs in July 2023,
 In June 2023, we have added and updated the following pages:
 
 ### New pages
-- [Security release notes 202306.0](/docs/about/all/releases/release-notes/release-notes-202306.0/security-release-notes-202306.0.html).
+- [Security release notes 202306.0](/docs/about/all/releases/release-notes-202306.0/security-release-notes-202306.0.html).
 - [Oryx: Presets](/docs/dg/dev/frontend-development/202212.0/oryx/building-applications/oryx-presets.html): Learn how you can use presets to install predefined applications.
 - [Service Points feature integration guide](/docs/pbc/all/service-point-management/202311.0/unified-commerce/install-features/install-the-service-points-feature.html).
 - [Shipment + Service Points feature integration guide](/docs/pbc/all/carrier-management/202311.0/unified-commerce/install-features/install-the-shipment-service-points-feature.html).
@@ -557,7 +557,7 @@ In April 2023, we have added and updated the following pages:
 - Warehouse picking feature integration guides:
     - [Install the Warehouse picking feature](/docs/pbc/all/warehouse-management-system/202311.0/unified-commerce/install-and-upgrade/install-the-warehouse-picking-feature.html)
     - [Install the Warehouse picking + Product feature](/docs/pbc/all/warehouse-management-system/202311.0/unified-commerce/install-and-upgrade/install-the-warehouse-picking-feature.html)
-- [Security release notes 202304.0](/docs/about/all/releases/release-notes/release-notes-202304.0/security-release-notes-202304.0.html)
+- [Security release notes 202304.0](/docs/about/all/releases/release-notes-202304.0/security-release-notes-202304.0.html)
 - [Releases vs Customization types](/docs/dg/dev/sdks/sdk/customization-strategies-and-upgradability.html): Learn about the customization strategies and release types you can use to integrate releases and customize your project.
 
 ### Updated pages
diff --git a/docs/dg/dev/acp/acp-overview.md b/docs/dg/dev/acp/acp-overview.md
index e6eb62806db..6e26b9c3a77 100644
--- a/docs/dg/dev/acp/acp-overview.md
+++ b/docs/dg/dev/acp/acp-overview.md
@@ -36,7 +36,7 @@ The ACP has the following advantages:
 
 ## Installing the ACP catalog
 
-With the Spryker product release [202212.0](/docs/about/all/releases/release-notes/release-notes-202212.0/release-notes-202212.0.html) the ACP catalog is integrated into the Back Office by default, but not registered with ACP yet. 
+With the Spryker product release [202212.0](/docs/about/all/releases/release-notes-202212.0/release-notes-202212.0.html) the ACP catalog is integrated into the Back Office by default, but not registered with ACP yet.
 
 You can access the ACP catalog only if you are a SCCOS customer and have additionally been enabled for ACP, which means that your SCCOS is properly set up and registered with the ACP. Check [ACP installation](/docs/acp/user/app-composition-platform-installation.html) for details on how to install and enable the ACP catalog for your version of SCCOS.
 
diff --git a/docs/dg/dev/acp/app-composition-platform-installation.md b/docs/dg/dev/acp/app-composition-platform-installation.md
index 2163ed99fa0..8ba58e4d365 100644
--- a/docs/dg/dev/acp/app-composition-platform-installation.md
+++ b/docs/dg/dev/acp/app-composition-platform-installation.md
@@ -39,13 +39,13 @@ The actions and level of effort required to make your project ACP-ready may vary
 
 To make your project ACP-ready, different update steps are necessary depending on the template version on which your project was started:
 
-- SCCOS product release [202211.0](/docs/about/all/releases/release-notes/release-notes-202211.0/release-notes-202211.0.html) includes a basic ACP setup. All ACP modules (apps and platform) requiere updates.
+- SCCOS product release [202211.0](/docs/about/all/releases/release-notes-202211.0/release-notes-202211.0.html) includes a basic ACP setup. All ACP modules (apps and platform) requiere updates.
 
-- SCCOS product release [202311.0](/docs/about/all/releases/release-notes/release-notes-202311.0/release-notes-202311.0.html) or later: you can skip the configuration step described in this document.
+- SCCOS product release [202311.0](/docs/about/all/releases/release-notes-202311.0/release-notes-202311.0.html) or later: you can skip the configuration step described in this document.
 
 {% info_block infoBox "Product version earlier than 202311.0" %}
 
-If you were onboarded with a version older than product release [202211.0](/docs/about/all/releases/release-notes/release-notes-202211.0/release-notes-202211.0.html), [contact us](https://support.spryker.com/). 
+If you were onboarded with a version older than product release [202211.0](/docs/about/all/releases/release-notes-202211.0/release-notes-202211.0.html), [contact us](https://support.spryker.com/). 
 
 {% endinfo_block %}
 
@@ -55,7 +55,7 @@ To get your project ACP-ready, it is important to make sure that your project mo
 
 #### ACP modules
 
-Starting with the Spryker product release [202311.0](/docs/about/all/releases/release-notes/release-notes-202311.0/release-notes-202311.0.html), the ACP catalog is included by default in the Spryker Cloud Commerc OS product. However, you should still make sure that your Spryker project uses the latest versions of the following modules:
+Starting with the Spryker product release [202311.0](/docs/about/all/releases/release-notes-202311.0/release-notes-202311.0.html), the ACP catalog is included by default in the Spryker Cloud Commerc OS product. However, you should still make sure that your Spryker project uses the latest versions of the following modules:
 
 * `spryker/app-catalog-gui: ^1.4.1` or later
 * `spryker/message-broker: ^1.10.0` or later
@@ -79,7 +79,7 @@ For each app you wish to use, ensure that you have the latest app-related SCOS m
 
 {% info_block infoBox "This step can be omitted for Product version later than 202311.0" %}
 
-If your version is based on product release [202311.0](/docs/about/all/releases/release-notes/release-notes-202311.0/release-notes-202311.0.html) or later, you can skip this section. 
+If your version is based on product release [202311.0](/docs/about/all/releases/release-notes-202311.0/release-notes-202311.0.html) or later, you can skip this section. 
 
 {% endinfo_block %}
 
diff --git a/docs/dg/dev/development-getting-started-guide.md b/docs/dg/dev/development-getting-started-guide.md
index 013df94cee7..20088e9f68b 100644
--- a/docs/dg/dev/development-getting-started-guide.md
+++ b/docs/dg/dev/development-getting-started-guide.md
@@ -49,7 +49,7 @@ For more information about deploy files, see [Deploy file](/docs/dg/dev/sdks/the
 
 A Spryker module is a single-function unit that has well-defined dependencies and can be updated independently. [Composer](/docs/dg/dev/set-up-spryker-locally/manage-dependencies-with-composer.html) is used for installing and managing module dependencies.
 
-To define your strategy when implementing updates, learn about our [module and feature release process](/docs/about/all/spryker-release-process.html).
+To define your strategy when implementing updates, learn about our [module and feature release process](/docs/about/all/releases/product-and-code-releases.html).
 
 
 You will use the following commands to manage modules with Composer:
diff --git a/docs/dg/dev/updating-spryker/feature-or-module-updates.md b/docs/dg/dev/updating-spryker/feature-or-module-updates.md
index 1b2f860735d..8bb8cafd063 100644
--- a/docs/dg/dev/updating-spryker/feature-or-module-updates.md
+++ b/docs/dg/dev/updating-spryker/feature-or-module-updates.md
@@ -9,7 +9,7 @@ redirect_from:
 
 When you know that you need to update your project, you need to decide if you want to do updates on the *feature* or the *module* level.
 
-Features are released every several month as part of [Product Releases](/docs/about/all/spryker-release-process.html#product-releases). Modules updates are released as frequently as several times per day and are part of [Code Releases](/docs/about/all/spryker-release-process.html#atomic-code-releases).
+Features are released every several month as part of [Product Releases](/docs/about/all/releases/product-and-code-releases.html#product-releases). Modules updates are released as frequently as several times per day and are part of [Code Releases](/docs/about/all/releases/product-and-code-releases.html#atomic-code-releases).
 
 The table below shows when it might be more relevant for you to make updates at the feature level and when at the module level.
 
diff --git a/docs/dg/dev/updating-spryker/updating-spryker.md b/docs/dg/dev/updating-spryker/updating-spryker.md
index c713b6f8b58..51868a5e05b 100644
--- a/docs/dg/dev/updating-spryker/updating-spryker.md
+++ b/docs/dg/dev/updating-spryker/updating-spryker.md
@@ -40,7 +40,7 @@ Schematically, the Spryker product structure looks like this:
 The most typical reasons to update modules or features are the following:
 * There are important security or bug fixes that have been introduced recently.
 * You want a new specific feature or module in your project, which requires a newer version of your modules.
-* Your project has been started shortly before a new [product release](/docs/about/all/spryker-release-process.html#product-releases).
+* Your project has been started shortly before a new [product release](/docs/about/all/releases/product-and-code-releases.html#product-releases).
 * You experience some issues with the shop that you would like to report or consult about.
 * If you plan to extend your shop in future with new features from the ones that exist in Spryker or are coming out soon, your project should be always up to date. It will ease the new feature installation and reduce the migration efforts, allowing you to get the desired functionality faster.
 

From 8f2a3e7e9d495301692430afaedd365bd0b05eef Mon Sep 17 00:00:00 2001
From: Andrii Tserkovnyi <andrii.tserkovnyi@spryker.com>
Date: Mon, 18 Mar 2024 12:42:04 +0200
Subject: [PATCH 16/26] links

---
 docs/about/all/docs-updates.md                     |  2 +-
 .../spryker-marketplace/marketplace-storefront.md  |  2 +-
 .../all/spryker-marketplace/spryker-marketplace.md |  2 +-
 .../acp/app-composition-platform-installation.md   | 14 +++++++-------
 .../dev/backend-development/cronjobs/cronjobs.md   |  2 +-
 .../data-import-optimization-guidelines.md         |  2 +-
 .../data-import-optimization-guidelines.md         |  2 +-
 .../data-import-optimization-guidelines.md         |  2 +-
 .../202212.0/configure-the-included-section.md     |  2 +-
 .../extend-a-rest-api-resource.md                  |  2 +-
 .../202307.0/configure-the-included-section.md     |  2 +-
 .../extend-a-rest-api-resource.md                  |  2 +-
 .../202311.0/configure-the-included-section.md     |  2 +-
 .../extend-a-rest-api-resource.md                  |  2 +-
 .../install/install-in-demo-mode-on-windows.md     |  2 +-
 .../install-in-development-mode-on-windows.md      |  2 +-
 .../email-as-a-cms-block-overview.md               |  2 +-
 .../email-as-a-cms-block-overview.md               |  2 +-
 .../email-as-a-cms-block-overview.md               |  2 +-
 .../standard-filters-overview.md                   |  2 +-
 .../standard-filters-overview.md                   |  2 +-
 .../standard-filters-overview.md                   |  2 +-
 ...-in-a-multi-store-environment-best-practices.md |  2 +-
 ...-in-a-multi-store-environment-best-practices.md |  2 +-
 ...-in-a-multi-store-environment-best-practices.md |  2 +-
 25 files changed, 31 insertions(+), 31 deletions(-)

diff --git a/docs/about/all/docs-updates.md b/docs/about/all/docs-updates.md
index 0fcee5f1066..59223e7754a 100644
--- a/docs/about/all/docs-updates.md
+++ b/docs/about/all/docs-updates.md
@@ -248,7 +248,7 @@ In November 2023, we have added and updated the following pages:
 - [Backend API Marketplace B2C Demo Shop reference](/docs/dg/dev/glue-api/202311.0/backend-glue-infrastructure/backend-api-marketplace-b2c-demo-shop-reference.html).
 - [REST API Marketplace B2B Demo Shop reference](/docs/dg/dev/glue-api/202311.0/old-glue-infrastructure/rest-api-marketplace-b2b-demo-shop-reference.html).
 - [REST API Marketplace B2C Demo Shop reference](/docs/dg/dev/glue-api/202311.0/old-glue-infrastructure/rest-api-marketplace-b2c-demo-shop-reference.html).
-- [Release notes 202311.0](/docs/about/all/releases/release-notes-202311.0/release-notes-202311.0.html).
+- [Release notes 202311.0](/docs/about/all/releases/release-notes-202311.0.html).
 - [Security release notes 202312.0](/docs/about/all/releases/security-release-notes-202312.0.html).
 
 ### Updated pages
diff --git a/docs/about/all/spryker-marketplace/marketplace-storefront.md b/docs/about/all/spryker-marketplace/marketplace-storefront.md
index c53de3895e7..c62a6747822 100644
--- a/docs/about/all/spryker-marketplace/marketplace-storefront.md
+++ b/docs/about/all/spryker-marketplace/marketplace-storefront.md
@@ -9,7 +9,7 @@ redirect_from:
 
 ---
 
-*Marketplace Storefront* is a web application designed for the [marketplace business model](/docs/about/all/spryker-marketplace/marketplace-concept.html). Based on the regular Storefront, it supports all [Spryker Commerce OS](/docs/about/all/intro-to-spryker.html) features. Marketplace functionality lets buyers browse for products and view and purchase them across different merchants.
+*Marketplace Storefront* is a web application designed for the [marketplace business model](/docs/about/all/spryker-marketplace/marketplace-concept.html). Based on the regular Storefront, it supports all [Spryker Commerce OS](/docs/about/all/about-spryker.html) features. Marketplace functionality lets buyers browse for products and view and purchase them across different merchants.
 
 In most sections of the Marketplace Storefront, customers can see who the seller of a product or offer is.
 
diff --git a/docs/about/all/spryker-marketplace/spryker-marketplace.md b/docs/about/all/spryker-marketplace/spryker-marketplace.md
index e43e3959ee1..0b17ad89281 100644
--- a/docs/about/all/spryker-marketplace/spryker-marketplace.md
+++ b/docs/about/all/spryker-marketplace/spryker-marketplace.md
@@ -14,7 +14,7 @@ redirect_from:
 
 In this section, you will find all the information about Spryker Marketplace and how to start developing one.
 
-If you are new to Spryker, first see our [Intro to Spryker](/docs/about/all/intro-to-spryker.html).
+If you are new to Spryker, first see our [Intro to Spryker](/docs/about/all/about-spryker.html).
 
 ## Overview of Spryker Marketplace
 
diff --git a/docs/dg/dev/acp/app-composition-platform-installation.md b/docs/dg/dev/acp/app-composition-platform-installation.md
index 8ba58e4d365..4b2ad771135 100644
--- a/docs/dg/dev/acp/app-composition-platform-installation.md
+++ b/docs/dg/dev/acp/app-composition-platform-installation.md
@@ -10,7 +10,7 @@ redirect_from:
 
 This document describes how you can make your project ACP-ready and how you install ACP.
 
-# Installing ACP in SCCOS
+## Installing ACP in SCCOS
 
 {% info_block warningBox "Prerequisite" %}
 
@@ -39,13 +39,13 @@ The actions and level of effort required to make your project ACP-ready may vary
 
 To make your project ACP-ready, different update steps are necessary depending on the template version on which your project was started:
 
-- SCCOS product release [202211.0](/docs/about/all/releases/release-notes-202211.0/release-notes-202211.0.html) includes a basic ACP setup. All ACP modules (apps and platform) requiere updates.
+- SCCOS product release [202211.0](/docs/about/all/releases/release-notes-202211.0.html) includes a basic ACP setup. All ACP modules (apps and platform) requiere updates.
 
-- SCCOS product release [202311.0](/docs/about/all/releases/release-notes-202311.0/release-notes-202311.0.html) or later: you can skip the configuration step described in this document.
+- SCCOS product release [202311.0](/docs/about/all/releases/release-notes-202311.0.html) or later: you can skip the configuration step described in this document.
 
 {% info_block infoBox "Product version earlier than 202311.0" %}
 
-If you were onboarded with a version older than product release [202211.0](/docs/about/all/releases/release-notes-202211.0/release-notes-202211.0.html), [contact us](https://support.spryker.com/). 
+If you were onboarded with a version older than product release [202211.0](/docs/about/all/releases/release-notes-202211.0.html), [contact us](https://support.spryker.com/).
 
 {% endinfo_block %}
 
@@ -55,7 +55,7 @@ To get your project ACP-ready, it is important to make sure that your project mo
 
 #### ACP modules
 
-Starting with the Spryker product release [202311.0](/docs/about/all/releases/release-notes-202311.0/release-notes-202311.0.html), the ACP catalog is included by default in the Spryker Cloud Commerc OS product. However, you should still make sure that your Spryker project uses the latest versions of the following modules:
+Starting with the Spryker product release [202311.0](/docs/about/all/releases/release-notes-202311.0.html), the ACP catalog is included by default in the Spryker Cloud Commerc OS product. However, you should still make sure that your Spryker project uses the latest versions of the following modules:
 
 * `spryker/app-catalog-gui: ^1.4.1` or later
 * `spryker/message-broker: ^1.10.0` or later
@@ -79,7 +79,7 @@ For each app you wish to use, ensure that you have the latest app-related SCOS m
 
 {% info_block infoBox "This step can be omitted for Product version later than 202311.0" %}
 
-If your version is based on product release [202311.0](/docs/about/all/releases/release-notes-202311.0/release-notes-202311.0.html) or later, you can skip this section. 
+If your version is based on product release [202311.0](/docs/about/all/releases/release-notes-202311.0.html) or later, you can skip this section.
 
 {% endinfo_block %}
 
@@ -143,7 +143,7 @@ $config[OauthClientConstants::TENANT_IDENTIFIER]
     = $config[MessageBrokerAwsConstants::CONSUMER_ID]
     = $config[AppCatalogGuiConstants::TENANT_IDENTIFIER]
     = getenv('SPRYKER_TENANT_IDENTIFIER') ?: '';
-    
+
 // ----------------------------------------------------------------------------
 // ------------------------------ OAUTH ---------------------------------------
 // ----------------------------------------------------------------------------
diff --git a/docs/dg/dev/backend-development/cronjobs/cronjobs.md b/docs/dg/dev/backend-development/cronjobs/cronjobs.md
index e6aaf11f12d..bb2759261e8 100644
--- a/docs/dg/dev/backend-development/cronjobs/cronjobs.md
+++ b/docs/dg/dev/backend-development/cronjobs/cronjobs.md
@@ -35,7 +35,7 @@ Basic module schema:
 
 ## Cronjob schedulers
 
-[Demo Shops](/docs/about/all/intro-to-spryker.html#demo-shops) are shipped with Jenkins as a default scheduler. Jenkins manages running and monitoring jobs. If you migrated to another scheduler and want to migrate back to Jenkins, see [Migrate to Jenkins](/docs/dg/dev/backend-development/cronjobs/migrate-to-jenkins.html).
+[Demo Shops](/docs/about/all/about-spryker.html#demo-shops) are shipped with Jenkins as a default scheduler. Jenkins manages running and monitoring jobs. If you migrated to another scheduler and want to migrate back to Jenkins, see [Migrate to Jenkins](/docs/dg/dev/backend-development/cronjobs/migrate-to-jenkins.html).
 
 If your project has very specific requirements, you can [create a custom scheduler](/docs/dg/dev/backend-development/cronjobs/create-a-custom-scheduler.html).
 
diff --git a/docs/dg/dev/data-import/202212.0/data-import-optimization-guidelines.md b/docs/dg/dev/data-import/202212.0/data-import-optimization-guidelines.md
index 2e0ae51be79..acf7bf28262 100644
--- a/docs/dg/dev/data-import/202212.0/data-import-optimization-guidelines.md
+++ b/docs/dg/dev/data-import/202212.0/data-import-optimization-guidelines.md
@@ -123,7 +123,7 @@ Let's say you already started to work with the batch operation, one of the chall
 
 ### Database vendor approach
 
-Spryker supports PostgreSQL, MySQL, and MariaDB. When working with databases, it's good to know their related features. For example, one of the great features we like is [CTE](https://www.postgresql.org/docs/9.1/queries-with.html). If you are inserting or updating big amounts of data, like millions of millions, use CTE as a replaceable for multiple inserts and updates. You can find examples of implementations in our [Demo Shops](/docs/about/all/intro-to-spryker.html#demo-shops).
+Spryker supports PostgreSQL, MySQL, and MariaDB. When working with databases, it's good to know their related features. For example, one of the great features we like is [CTE](https://www.postgresql.org/docs/9.1/queries-with.html). If you are inserting or updating big amounts of data, like millions of millions, use CTE as a replaceable for multiple inserts and updates. You can find examples of implementations in our [Demo Shops](/docs/about/all/about-spryker.html#demo-shops).
 
 ## Rules for Publish and Synchronize
 
diff --git a/docs/dg/dev/data-import/202307.0/data-import-optimization-guidelines.md b/docs/dg/dev/data-import/202307.0/data-import-optimization-guidelines.md
index 92133330f19..18cf034270b 100644
--- a/docs/dg/dev/data-import/202307.0/data-import-optimization-guidelines.md
+++ b/docs/dg/dev/data-import/202307.0/data-import-optimization-guidelines.md
@@ -123,7 +123,7 @@ Let's say you already started to work with the batch operation, one of the chall
 
 ### Database vendor approach
 
-Spryker supports PostgreSQL, MySQL, and MariaDB. When working with databases, it's good to know their related features. For example, one of the great features we like is [CTE](https://www.postgresql.org/docs/9.1/queries-with.html). If you are inserting or updating big amounts of data, like millions of millions, use CTE as a replaceable for multiple inserts and updates. You can find examples of implementations in our [Demo Shops](/docs/about/all/intro-to-spryker.html#demo-shops).
+Spryker supports PostgreSQL, MySQL, and MariaDB. When working with databases, it's good to know their related features. For example, one of the great features we like is [CTE](https://www.postgresql.org/docs/9.1/queries-with.html). If you are inserting or updating big amounts of data, like millions of millions, use CTE as a replaceable for multiple inserts and updates. You can find examples of implementations in our [Demo Shops](/docs/about/all/about-spryker.html#demo-shops).
 
 ## Rules for Publish and Synchronize
 
diff --git a/docs/dg/dev/data-import/202311.0/data-import-optimization-guidelines.md b/docs/dg/dev/data-import/202311.0/data-import-optimization-guidelines.md
index f7e3074a2e2..ccce49733e2 100644
--- a/docs/dg/dev/data-import/202311.0/data-import-optimization-guidelines.md
+++ b/docs/dg/dev/data-import/202311.0/data-import-optimization-guidelines.md
@@ -116,7 +116,7 @@ Let's say you already started to work with the batch operation, one of the chall
 
 ### Database vendor approach
 
-Spryker supports PostgreSQL, MySQL, and MariaDB. When working with databases, it's good to know their related features. For example, one of the great features we like is [CTE](https://www.postgresql.org/docs/9.1/queries-with.html). If you are inserting or updating big amounts of data, like millions of millions, use CTE as a replaceable for multiple inserts and updates. You can find examples of implementations in our [Demo Shops](/docs/about/all/intro-to-spryker.html#demo-shops).
+Spryker supports PostgreSQL, MySQL, and MariaDB. When working with databases, it's good to know their related features. For example, one of the great features we like is [CTE](https://www.postgresql.org/docs/9.1/queries-with.html). If you are inserting or updating big amounts of data, like millions of millions, use CTE as a replaceable for multiple inserts and updates. You can find examples of implementations in our [Demo Shops](/docs/about/all/about-spryker.html#demo-shops).
 
 ## Rules for Publish and Synchronize
 
diff --git a/docs/dg/dev/glue-api/202212.0/configure-the-included-section.md b/docs/dg/dev/glue-api/202212.0/configure-the-included-section.md
index c6456f75893..f29a3dd9bad 100644
--- a/docs/dg/dev/glue-api/202212.0/configure-the-included-section.md
+++ b/docs/dg/dev/glue-api/202212.0/configure-the-included-section.md
@@ -28,7 +28,7 @@ You can decide whether Glue REST API includes the sections in all responses by d
 |**Enabled** | The **included** and **relationships** sections contain only the resources whose names were passed in the query string (resource `concrete-product-image-sets` per the example). | The included section contains all the included resources (if any). |
 |**Disabled** | The response does not contain the included section with related resources. |  The included section contains all the included resources (if any).|
 
-By default, the option is enabled on the Spryker Core level but disabled on the project level in all [Spryker Demo Shops](/docs/about/all/intro-to-spryker.html#demo-shops) (B2B Demo Shop, B2C Demo Shop and Master Shop Suite).
+By default, the option is enabled on the Spryker Core level but disabled on the project level in all [Spryker Demo Shops](/docs/about/all/about-spryker.html#demo-shops) (B2B Demo Shop, B2C Demo Shop and Master Shop Suite).
 
 {% info_block infoBox %}
 
diff --git a/docs/dg/dev/glue-api/202212.0/glue-api-tutorials/extend-a-rest-api-resource.md b/docs/dg/dev/glue-api/202212.0/glue-api-tutorials/extend-a-rest-api-resource.md
index 01ee276fab9..2d0748f0cb3 100644
--- a/docs/dg/dev/glue-api/202212.0/glue-api-tutorials/extend-a-rest-api-resource.md
+++ b/docs/dg/dev/glue-api/202212.0/glue-api-tutorials/extend-a-rest-api-resource.md
@@ -46,7 +46,7 @@ The following guide relies on your knowledge of the structure of the Glue REST A
 
 {% info_block infoBox %}
 
-If you have a development virtual machine with the [B2C Demo Shop](/docs/about/all/intro-to-spryker.html#demo-shops) installed, all the required components are available out of the box.
+If you have a development virtual machine with the [B2C Demo Shop](/docs/about/all/about-spryker.html#demo-shops) installed, all the required components are available out of the box.
 
 Assume that you modify the product storage data to match your product requirements—for example, you add the `manufacturerCountry` field to the product data not as an attribute but as another field in the database.
 
diff --git a/docs/dg/dev/glue-api/202307.0/configure-the-included-section.md b/docs/dg/dev/glue-api/202307.0/configure-the-included-section.md
index 3c7bb61ef5b..9f7bf710e4c 100644
--- a/docs/dg/dev/glue-api/202307.0/configure-the-included-section.md
+++ b/docs/dg/dev/glue-api/202307.0/configure-the-included-section.md
@@ -29,7 +29,7 @@ You can decide whether Glue REST API includes the sections in all responses by d
 |**Enabled** | The **included** and **relationships** sections contain only the resources whose names were passed in the query string (resource `concrete-product-image-sets` per the example). | The included section contains all the included resources (if any). |
 |**Disabled** | The response does not contain the included section with related resources. |  The included section contains all the included resources (if any).|
 
-By default, the option is enabled on the Spryker Core level but disabled on the project level in all [Spryker Demo Shops](/docs/about/all/intro-to-spryker.html#demo-shops) (B2B Demo Shop, B2C Demo Shop and Master Shop Suite).
+By default, the option is enabled on the Spryker Core level but disabled on the project level in all [Spryker Demo Shops](/docs/about/all/about-spryker.html#demo-shops) (B2B Demo Shop, B2C Demo Shop and Master Shop Suite).
 
 {% info_block infoBox %}
 
diff --git a/docs/dg/dev/glue-api/202307.0/glue-api-tutorials/extend-a-rest-api-resource.md b/docs/dg/dev/glue-api/202307.0/glue-api-tutorials/extend-a-rest-api-resource.md
index 69135066a11..e0cf1b48c48 100644
--- a/docs/dg/dev/glue-api/202307.0/glue-api-tutorials/extend-a-rest-api-resource.md
+++ b/docs/dg/dev/glue-api/202307.0/glue-api-tutorials/extend-a-rest-api-resource.md
@@ -46,7 +46,7 @@ The following guide relies on your knowledge of the structure of the Glue REST A
 
 {% info_block infoBox %}
 
-If you have a development virtual machine with the [B2C Demo Shop](/docs/about/all/intro-to-spryker.html#demo-shops) installed, all the required components are available out of the box.
+If you have a development virtual machine with the [B2C Demo Shop](/docs/about/all/about-spryker.html#demo-shops) installed, all the required components are available out of the box.
 
 Assume that you modify the product storage data to match your product requirements—for example, you add the `manufacturerCountry` field to the product data not as an attribute but as another field in the database.
 
diff --git a/docs/dg/dev/glue-api/202311.0/configure-the-included-section.md b/docs/dg/dev/glue-api/202311.0/configure-the-included-section.md
index 7f74c942003..2bde2a1df13 100644
--- a/docs/dg/dev/glue-api/202311.0/configure-the-included-section.md
+++ b/docs/dg/dev/glue-api/202311.0/configure-the-included-section.md
@@ -30,7 +30,7 @@ You can decide whether Glue REST API includes the sections in all responses by d
 |**Enabled** | The **included** and **relationships** sections contain only the resources whose names were passed in the query string (resource `concrete-product-image-sets` per the example). | The included section contains all the included resources (if any). |
 |**Disabled** | The response does not contain the included section with related resources. |  The included section contains all the included resources (if any).|
 
-By default, the option is enabled on the Spryker Core level but disabled on the project level in all [Spryker Demo Shops](/docs/about/all/intro-to-spryker.html#demo-shops) (B2B Demo Shop, B2C Demo Shop and Master Shop Suite).
+By default, the option is enabled on the Spryker Core level but disabled on the project level in all [Spryker Demo Shops](/docs/about/all/about-spryker.html#demo-shops) (B2B Demo Shop, B2C Demo Shop and Master Shop Suite).
 
 {% info_block infoBox %}
 
diff --git a/docs/dg/dev/glue-api/202311.0/glue-api-tutorials/extend-a-rest-api-resource.md b/docs/dg/dev/glue-api/202311.0/glue-api-tutorials/extend-a-rest-api-resource.md
index 12c38e8604f..033a28836d4 100644
--- a/docs/dg/dev/glue-api/202311.0/glue-api-tutorials/extend-a-rest-api-resource.md
+++ b/docs/dg/dev/glue-api/202311.0/glue-api-tutorials/extend-a-rest-api-resource.md
@@ -32,7 +32,7 @@ The following guide relies on your knowledge of the structure of the Glue REST A
 
 {% info_block infoBox %}
 
-If you have a development virtual machine with the [B2C Demo Shop](/docs/about/all/intro-to-spryker.html#demo-shops) installed, all the required components are available out of the box.
+If you have a development virtual machine with the [B2C Demo Shop](/docs/about/all/about-spryker.html#demo-shops) installed, all the required components are available out of the box.
 
 Assume that you modify the product storage data to match your product requirements—for example, you add the `manufacturerCountry` field to the product data not as an attribute but as another field in the database.
 
diff --git a/docs/dg/dev/set-up-spryker-locally/install-spryker/install/install-in-demo-mode-on-windows.md b/docs/dg/dev/set-up-spryker-locally/install-spryker/install/install-in-demo-mode-on-windows.md
index c96a3135fcc..388de1aa2bd 100644
--- a/docs/dg/dev/set-up-spryker-locally/install-spryker/install/install-in-demo-mode-on-windows.md
+++ b/docs/dg/dev/set-up-spryker-locally/install-spryker/install/install-in-demo-mode-on-windows.md
@@ -28,7 +28,7 @@ Depending on the needed WSL version, follow one of the guides:
 1. Open Ubuntu.
 2. Open a terminal.
 3. Create a new folder and navigate into it.
-4. Clone *one* of the [Demo Shops](/docs/about/all/intro-to-spryker.html#demo-shops) and navigate into its folder:
+4. Clone *one* of the [Demo Shops](/docs/about/all/about-spryker.html#demo-shops) and navigate into its folder:
 
     * B2C Demo Shop:
 
diff --git a/docs/dg/dev/set-up-spryker-locally/install-spryker/install/install-in-development-mode-on-windows.md b/docs/dg/dev/set-up-spryker-locally/install-spryker/install/install-in-development-mode-on-windows.md
index ebf86586fb1..1f7ed1c36f4 100644
--- a/docs/dg/dev/set-up-spryker-locally/install-spryker/install/install-in-development-mode-on-windows.md
+++ b/docs/dg/dev/set-up-spryker-locally/install-spryker/install/install-in-development-mode-on-windows.md
@@ -40,7 +40,7 @@ Recommended: `/home/jdoe/workspace/project`.
 2. Open a terminal.
 3. Create a new folder and navigate into it.
 
-4. Clone *one* of the [Demo Shops](/docs/about/all/intro-to-spryker.html#demo-shops):
+4. Clone *one* of the [Demo Shops](/docs/about/all/about-spryker.html#demo-shops):
 
     * B2C Demo Shop:
 
diff --git a/docs/pbc/all/content-management-system/202212.0/base-shop/cms-feature-overview/email-as-a-cms-block-overview.md b/docs/pbc/all/content-management-system/202212.0/base-shop/cms-feature-overview/email-as-a-cms-block-overview.md
index bd5348e186e..d46257f28d7 100644
--- a/docs/pbc/all/content-management-system/202212.0/base-shop/cms-feature-overview/email-as-a-cms-block-overview.md
+++ b/docs/pbc/all/content-management-system/202212.0/base-shop/cms-feature-overview/email-as-a-cms-block-overview.md
@@ -54,7 +54,7 @@ The email format itself is defined on the code level, the tales serving as ident
 
 
 ### Default email templates
-There is a number of email templates with the respective Email CMS Blocks available in the [Spryker Demo Shops](/docs/about/all/intro-to-spryker.html#demo-shops).
+There is a number of email templates with the respective Email CMS Blocks available in the [Spryker Demo Shops](/docs/about/all/about-spryker.html#demo-shops).
 
 The following table contains the list of the default email templates, their Email CMS Blocks, and their purpose.
 
diff --git a/docs/pbc/all/content-management-system/202307.0/base-shop/cms-feature-overview/email-as-a-cms-block-overview.md b/docs/pbc/all/content-management-system/202307.0/base-shop/cms-feature-overview/email-as-a-cms-block-overview.md
index b99b694e401..1501b9800ba 100644
--- a/docs/pbc/all/content-management-system/202307.0/base-shop/cms-feature-overview/email-as-a-cms-block-overview.md
+++ b/docs/pbc/all/content-management-system/202307.0/base-shop/cms-feature-overview/email-as-a-cms-block-overview.md
@@ -54,7 +54,7 @@ The email format itself is defined on the code level, the tales serving as ident
 
 
 ### Default email templates
-There is a number of email templates with the respective Email CMS Blocks available in the [Spryker Demo Shops](/docs/about/all/intro-to-spryker.html#demo-shops).
+There is a number of email templates with the respective Email CMS Blocks available in the [Spryker Demo Shops](/docs/about/all/about-spryker.html#demo-shops).
 
 The following table contains the list of the default email templates, their Email CMS Blocks, and their purpose.
 
diff --git a/docs/pbc/all/content-management-system/202311.0/base-shop/cms-feature-overview/email-as-a-cms-block-overview.md b/docs/pbc/all/content-management-system/202311.0/base-shop/cms-feature-overview/email-as-a-cms-block-overview.md
index 3f88558e0ee..90eec753b29 100644
--- a/docs/pbc/all/content-management-system/202311.0/base-shop/cms-feature-overview/email-as-a-cms-block-overview.md
+++ b/docs/pbc/all/content-management-system/202311.0/base-shop/cms-feature-overview/email-as-a-cms-block-overview.md
@@ -55,7 +55,7 @@ The email format itself is defined on the code level, the tales serving as ident
 
 
 ### Default email templates
-There is a number of email templates with the respective Email CMS Blocks available in the [Spryker Demo Shops](/docs/about/all/intro-to-spryker.html#demo-shops).
+There is a number of email templates with the respective Email CMS Blocks available in the [Spryker Demo Shops](/docs/about/all/about-spryker.html#demo-shops).
 
 The following table contains the list of the default email templates, their Email CMS Blocks, and their purpose.
 
diff --git a/docs/pbc/all/search/202212.0/base-shop/search-feature-overview/standard-filters-overview.md b/docs/pbc/all/search/202212.0/base-shop/search-feature-overview/standard-filters-overview.md
index 0393a85997e..21699898263 100644
--- a/docs/pbc/all/search/202212.0/base-shop/search-feature-overview/standard-filters-overview.md
+++ b/docs/pbc/all/search/202212.0/base-shop/search-feature-overview/standard-filters-overview.md
@@ -40,7 +40,7 @@ Products appropriate for the active filters are displayed in the results.
 Filter preferences can be configured in the **Back Office&nbsp;<span aria-label="and then">></span> Search and Filters&nbsp;<span aria-label="and then">></span> Filter Preferences**. Filter options depend on the attributes configured for the products.
 
 ## Current constraints
-Price Range Filter is not supported with the Merchant Relations, that is why this filter is not included in the B2B demo shop. However, in [the B2C demo shop](/docs/about/all/intro-to-spryker.html#demo-shops), you can still filter the products using the price range filter.
+Price Range Filter is not supported with the Merchant Relations, that is why this filter is not included in the B2B demo shop. However, in [the B2C demo shop](/docs/about/all/about-spryker.html#demo-shops), you can still filter the products using the price range filter.
 
 ## Related Business User documents
 
diff --git a/docs/pbc/all/search/202307.0/base-shop/search-feature-overview/standard-filters-overview.md b/docs/pbc/all/search/202307.0/base-shop/search-feature-overview/standard-filters-overview.md
index f7b8631356e..e0743e3bddb 100644
--- a/docs/pbc/all/search/202307.0/base-shop/search-feature-overview/standard-filters-overview.md
+++ b/docs/pbc/all/search/202307.0/base-shop/search-feature-overview/standard-filters-overview.md
@@ -42,7 +42,7 @@ Products appropriate for the active filters are displayed in the results.
 Filter preferences can be configured in the **Back Office&nbsp;<span aria-label="and then">></span> Search and Filters&nbsp;<span aria-label="and then">></span> Filter Preferences**. Filter options depend on the attributes configured for the products.
 
 ## Current constraints
-Price Range Filter is not supported with the Merchant Relations, that is why this filter is not included in the B2B demo shop. However, in [the B2C demo shop](/docs/about/all/intro-to-spryker.html#demo-shops), you can still filter the products using the price range filter.
+Price Range Filter is not supported with the Merchant Relations, that is why this filter is not included in the B2B demo shop. However, in [the B2C demo shop](/docs/about/all/about-spryker.html#demo-shops), you can still filter the products using the price range filter.
 
 ## Related Business User documents
 
diff --git a/docs/pbc/all/search/202311.0/base-shop/search-feature-overview/standard-filters-overview.md b/docs/pbc/all/search/202311.0/base-shop/search-feature-overview/standard-filters-overview.md
index 2db5d69b1be..e0314d2718b 100644
--- a/docs/pbc/all/search/202311.0/base-shop/search-feature-overview/standard-filters-overview.md
+++ b/docs/pbc/all/search/202311.0/base-shop/search-feature-overview/standard-filters-overview.md
@@ -43,7 +43,7 @@ Products appropriate for the active filters are displayed in the results.
 Filter preferences can be configured in the **Back Office&nbsp;<span aria-label="and then">></span> Search and Filters&nbsp;<span aria-label="and then">></span> Filter Preferences**. Filter options depend on the attributes configured for the products.
 
 ## Current constraints
-Price Range Filter is not supported with the Merchant Relations, that is why this filter is not included in the B2B demo shop. However, in [the B2C demo shop](/docs/about/all/intro-to-spryker.html#demo-shops), you can still filter the products using the price range filter.
+Price Range Filter is not supported with the Merchant Relations, that is why this filter is not included in the B2B demo shop. However, in [the B2C demo shop](/docs/about/all/about-spryker.html#demo-shops), you can still filter the products using the price range filter.
 
 ## Related Business User documents
 
diff --git a/docs/pbc/all/warehouse-management-system/202212.0/base-shop/extend-and-customize/manage-stocks-in-a-multi-store-environment-best-practices.md b/docs/pbc/all/warehouse-management-system/202212.0/base-shop/extend-and-customize/manage-stocks-in-a-multi-store-environment-best-practices.md
index bfe3f19c727..533268ebf67 100644
--- a/docs/pbc/all/warehouse-management-system/202212.0/base-shop/extend-and-customize/manage-stocks-in-a-multi-store-environment-best-practices.md
+++ b/docs/pbc/all/warehouse-management-system/202212.0/base-shop/extend-and-customize/manage-stocks-in-a-multi-store-environment-best-practices.md
@@ -68,7 +68,7 @@ There is a console command to export all reservations: `/Spryker/Zed/Oms/Communi
 
 {% info_block infoBox "" %}
 
-This is the default scenario implemented in the [Spryker Demo Shops](/docs/about/all/intro-to-spryker.html).
+This is the default scenario implemented in the [Spryker Demo Shops](/docs/about/all/about-spryker.html).
 
 {% endinfo_block %}
 
diff --git a/docs/pbc/all/warehouse-management-system/202307.0/base-shop/extend-and-customize/manage-stocks-in-a-multi-store-environment-best-practices.md b/docs/pbc/all/warehouse-management-system/202307.0/base-shop/extend-and-customize/manage-stocks-in-a-multi-store-environment-best-practices.md
index 32aea1dbe14..25a40e051a3 100644
--- a/docs/pbc/all/warehouse-management-system/202307.0/base-shop/extend-and-customize/manage-stocks-in-a-multi-store-environment-best-practices.md
+++ b/docs/pbc/all/warehouse-management-system/202307.0/base-shop/extend-and-customize/manage-stocks-in-a-multi-store-environment-best-practices.md
@@ -68,7 +68,7 @@ There is a console command to export all reservations: `/Spryker/Zed/Oms/Communi
 
 {% info_block infoBox "" %}
 
-This is the default scenario implemented in the [Spryker Demo Shops](/docs/about/all/intro-to-spryker.html).
+This is the default scenario implemented in the [Spryker Demo Shops](/docs/about/all/about-spryker.html).
 
 {% endinfo_block %}
 
diff --git a/docs/pbc/all/warehouse-management-system/202311.0/base-shop/extend-and-customize/manage-stocks-in-a-multi-store-environment-best-practices.md b/docs/pbc/all/warehouse-management-system/202311.0/base-shop/extend-and-customize/manage-stocks-in-a-multi-store-environment-best-practices.md
index f179f1b54ad..3bfabc17025 100644
--- a/docs/pbc/all/warehouse-management-system/202311.0/base-shop/extend-and-customize/manage-stocks-in-a-multi-store-environment-best-practices.md
+++ b/docs/pbc/all/warehouse-management-system/202311.0/base-shop/extend-and-customize/manage-stocks-in-a-multi-store-environment-best-practices.md
@@ -69,7 +69,7 @@ There is a console command to export all reservations: `/Spryker/Zed/Oms/Communi
 
 {% info_block infoBox "" %}
 
-This is the default scenario implemented in the [Spryker Demo Shops](/docs/about/all/intro-to-spryker.html).
+This is the default scenario implemented in the [Spryker Demo Shops](/docs/about/all/about-spryker.html).
 
 {% endinfo_block %}
 

From afdad8e0f9d0390d67226d66788a0bc0881cc8a4 Mon Sep 17 00:00:00 2001
From: Andrii Tserkovnyi <andrii.tserkovnyi@spryker.com>
Date: Mon, 18 Mar 2024 16:17:27 +0200
Subject: [PATCH 17/26] links

---
 _data/sidebars/about_all_sidebar.yml                        | 6 +++---
 docs/about/all/releases/security-release-notes-202302.0.md  | 2 +-
 docs/about/all/support/getting-support.md                   | 2 +-
 .../all/support/getting-the-most-out-of-spryker-support.md  | 2 +-
 docs/about/all/support/how-spryker-support-works.md         | 2 +-
 docs/about/all/support/support-case-escalations.md          | 2 +-
 docs/about/all/support/understanding-slas.md                | 2 +-
 .../integrating-code-releases/integrating-code-releases.md  | 2 +-
 .../devscu/prepare-a-project-for-spryker-code-upgrader.md   | 2 +-
 docs/dg/dev/integrate-and-configure/configure-services.md   | 4 ++--
 .../dev/system-requirements/202212.0/system-requirements.md | 4 ++--
 .../dev/system-requirements/202307.0/system-requirements.md | 4 ++--
 .../dev/system-requirements/202311.0/system-requirements.md | 4 ++--
 .../troubleshooting-performance-issues.md                   | 2 +-
 docs/dg/dev/troubleshooting/troubleshooting.md              | 2 +-
 15 files changed, 21 insertions(+), 21 deletions(-)

diff --git a/_data/sidebars/about_all_sidebar.yml b/_data/sidebars/about_all_sidebar.yml
index 8e5b836dbea..d7f34890814 100644
--- a/_data/sidebars/about_all_sidebar.yml
+++ b/_data/sidebars/about_all_sidebar.yml
@@ -52,11 +52,11 @@ entries:
       - title: Preparing for heavy loads and traffic
         url: /docs/about/all/support/special-prepare-for-a-busy-season.html
       - title: How to use the Support Portal
-        url: /docs/about/all/support/how-to-use-the-support-portal.html
+        url: /docs/about/all/support/using-the-support-portal.html
       - title: Share secrets with the Spryker Support Team
         url: /docs/about/all/support/share-secrets-with-the-spryker-support-team.html
       - title: Understanding ticket status
-        url: /docs/about/all/support/understanding-ticket-status.html
+        url: /docs/about/all/support/support-ticket-statuses.html
       - title: Handling security issues
         url: /docs/about/all/support/handling-security-issues.html
       - title: Guidelines for GDPR compliance
@@ -97,7 +97,7 @@ entries:
     - title: Spryker Academy
       url: /docs/about/all/spryker-academy.html
     - title: Contribute to the documentation
-      url: /docs/about/all/contribute-to-the-documentation/contribute-to-the-documentation.html
+      url: /docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.html
       nested:
       - title: Edit the documentation via pull requests
         url: /docs/about/all/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
diff --git a/docs/about/all/releases/security-release-notes-202302.0.md b/docs/about/all/releases/security-release-notes-202302.0.md
index f7676754102..40a1930d7ec 100644
--- a/docs/about/all/releases/security-release-notes-202302.0.md
+++ b/docs/about/all/releases/security-release-notes-202302.0.md
@@ -154,7 +154,7 @@ This involves additional migration effort because of a required upgrade to PHP 8
 
 {% endinfo_block %}
 
-To upgrade to PHP 8.0, see [Supported versions of PHP](/docs/about/all/whats-new/supported-versions-of-php.html).
+To upgrade to PHP 8.0, see [Supported versions of PHP](/docs/dg/dev/supported-versions-of-php.html).
 
 Ensure that you have the security fix applied to the PHP8 version.
 
diff --git a/docs/about/all/support/getting-support.md b/docs/about/all/support/getting-support.md
index 5ae5182a38b..bfca778cf8a 100644
--- a/docs/about/all/support/getting-support.md
+++ b/docs/about/all/support/getting-support.md
@@ -11,7 +11,7 @@ redirect_from:
 
 related:
   - title: How to use the Support Portal
-    link: docs/about/all/support/how-to-use-the-support-portal.html
+    link: docs/about/all/support/using-the-support-portal.html
   - title: How Spryker Support works
     link: docs/about/all/support/how-spryker-support-works.html
   - title: Getting the most out of Spryker Support
diff --git a/docs/about/all/support/getting-the-most-out-of-spryker-support.md b/docs/about/all/support/getting-the-most-out-of-spryker-support.md
index a7fae3d82f0..ed316bc7b6b 100644
--- a/docs/about/all/support/getting-the-most-out-of-spryker-support.md
+++ b/docs/about/all/support/getting-the-most-out-of-spryker-support.md
@@ -10,7 +10,7 @@ related:
   - title: How Spryker Support works
     link: docs/about/all/support/how-spryker-support-works.html
   - title: How to use the Support Portal
-    link: docs/about/all/support/how-to-use-the-support-portal.html
+    link: docs/about/all/support/using-the-support-portal.html
 ---
 
 We are very proud to have outstanding First Response Times (currently, they average around 35 minutes in busy weeks). However, a first response seldom immediately includes the solution to your problem. So how can we shorten Case Resolution Time?
diff --git a/docs/about/all/support/how-spryker-support-works.md b/docs/about/all/support/how-spryker-support-works.md
index 713b44d50d4..992233182b6 100644
--- a/docs/about/all/support/how-spryker-support-works.md
+++ b/docs/about/all/support/how-spryker-support-works.md
@@ -10,7 +10,7 @@ related:
   - title: Getting the most out of Spryker Support
     link: docs/about/all/support/getting-the-most-out-of-spryker-support.html
   - title: How to use the Support Portal
-    link: docs/about/all/support/how-to-use-the-support-portal.html
+    link: docs/about/all/support/using-the-support-portal.html
 ---
 
 We believe that you can only deliver great support when you are on the same page as your customers. Being transparent about our performance metrics and processes is a necessary step towards that.
diff --git a/docs/about/all/support/support-case-escalations.md b/docs/about/all/support/support-case-escalations.md
index 223ee812028..60574972abc 100644
--- a/docs/about/all/support/support-case-escalations.md
+++ b/docs/about/all/support/support-case-escalations.md
@@ -27,7 +27,7 @@ In Support, we acknowledge that we cannot always produce a satisfying result. We
 
 ### Initiate an escalation
 
-Creating an [Emergency Case](/docs/about/all/support/how-to-use-the-support-portal.html#emergencies) always starts an escalation. You will receive an email notifying you that an escalation has been started.
+Creating an [Emergency Case](/docs/about/all/support/using-the-support-portal.html#emergencies) always starts an escalation. You will receive an email notifying you that an escalation has been started.
 
 ### The escalation process
 
diff --git a/docs/about/all/support/understanding-slas.md b/docs/about/all/support/understanding-slas.md
index e410169bc45..5c2df2de301 100644
--- a/docs/about/all/support/understanding-slas.md
+++ b/docs/about/all/support/understanding-slas.md
@@ -29,7 +29,7 @@ If you discover a problem with Spryker Software, please let us know immediately.
 Ensure that every case you open with us includes the information we need to work on it. To learn what info matters most, see [Getting the most out of Spryker Support](/docs/about/all/support/getting-the-most-out-of-spryker-support.html).
 
 ### Assess business impact realistically
-To make sure that we resolve the right cases first, we need to triage and prioritize. You can help us to do this better if you assess and specify the business impact of your problem appropriately. For a more detailed explanation of what business impact is and how priorities work have a look into this [article](/docs/about/all/support/understanding-ticket-status.html#how-are-bug-tickets-prioritized).
+To make sure that we resolve the right cases first, we need to triage and prioritize. You can help us to do this better if you assess and specify the business impact of your problem appropriately. For a more detailed explanation of what business impact is and how priorities work have a look into this [article](/docs/about/all/support/support-ticket-statuses.html#how-are-bug-tickets-prioritized).
 
 ## What you can expect from us
 
diff --git a/docs/ca/devscu/integrating-code-releases/integrating-code-releases.md b/docs/ca/devscu/integrating-code-releases/integrating-code-releases.md
index f714bf184ae..3836b5579fe 100644
--- a/docs/ca/devscu/integrating-code-releases/integrating-code-releases.md
+++ b/docs/ca/devscu/integrating-code-releases/integrating-code-releases.md
@@ -46,4 +46,4 @@ If you see errors in the generated code, do the following:
 1. Double-check if your code follows the upgradability guidelines by [running the Evaluator](/docs/dg/dev/guidelines/keeping-a-project-upgradable/run-the-evaluator-tool.html).
     After fixing the upgradability issues, close the PR with errors and restart the Upgrader to get a new PR.
 2. If you see any quick fixes, try manually correcting the errors.
-3. [Contact us](/docs/about/all/support/how-to-use-the-support-portal.html) for further assistance. 
+3. [Contact us](/docs/about/all/support/using-the-support-portal.html) for further assistance. 
diff --git a/docs/ca/devscu/prepare-a-project-for-spryker-code-upgrader.md b/docs/ca/devscu/prepare-a-project-for-spryker-code-upgrader.md
index 56a57f1d1ed..a4f90c08f0f 100644
--- a/docs/ca/devscu/prepare-a-project-for-spryker-code-upgrader.md
+++ b/docs/ca/devscu/prepare-a-project-for-spryker-code-upgrader.md
@@ -42,7 +42,7 @@ The Upgrader supports only projects that run in [cloud environments](/docs/ca/de
 
 For a smooth experience, make sure that your environments meet the minimum technical requirements:
 
-* PHP 8.1+. The Upgrader supports a minimum version of PHP 8.0. However, PHP 8.0 reached end of life in November 2023, so make sure to update PHP to the [recommended version](/docs/about/all/whats-new/supported-versions-of-php.html). To check if your PHP version is supported, [run the evaluator tool](/docs/dg/dev/guidelines/keeping-a-project-upgradable/run-the-evaluator-tool.html).
+* PHP 8.1+. The Upgrader supports a minimum version of PHP 8.0. However, PHP 8.0 reached end of life in November 2023, so make sure to update PHP to the [recommended version](/docs/dg/dev/supported-versions-of-php.html). To check if your PHP version is supported, [run the evaluator tool](/docs/dg/dev/guidelines/keeping-a-project-upgradable/run-the-evaluator-tool.html).
 * Composer 2.5+
 * Git 2.24+
 * PHPStan 1.9+
diff --git a/docs/dg/dev/integrate-and-configure/configure-services.md b/docs/dg/dev/integrate-and-configure/configure-services.md
index 7521512f0fd..dd3aa89046a 100644
--- a/docs/dg/dev/integrate-and-configure/configure-services.md
+++ b/docs/dg/dev/integrate-and-configure/configure-services.md
@@ -508,7 +508,7 @@ image:
 
 
 
-3. Submit an infrastructure change request via the [Support Portal](/docs/about/all/support/how-to-use-the-support-portal.html).
+3. Submit an infrastructure change request via the [Support Portal](/docs/about/all/support/using-the-support-portal.html).
   We will confirm that a New Relic APM account is available for you and ensure that the correct application naming convention is set up to cascade to the appropriate APM.
 
 Once New Relic is enabled, in the New Relic dashboard, you may see either `company-staging-newrelic-app` or `YVES-DE (docker.dev)`. New Relic displays these APM names by the application name setup in the configuration files.
@@ -518,7 +518,7 @@ Once New Relic is enabled, in the New Relic dashboard, you may see either `compa
 
 {% info_block infoBox %}
 
-If you update the name of an application, [contact support](/docs/about/all/support/how-to-use-the-support-portal.html) to update the changes in your APM.
+If you update the name of an application, [contact support](/docs/about/all/support/using-the-support-portal.html) to update the changes in your APM.
 
 {% endinfo_block %}
 
diff --git a/docs/dg/dev/system-requirements/202212.0/system-requirements.md b/docs/dg/dev/system-requirements/202212.0/system-requirements.md
index 9388025347c..3b161f52caa 100644
--- a/docs/dg/dev/system-requirements/202212.0/system-requirements.md
+++ b/docs/dg/dev/system-requirements/202212.0/system-requirements.md
@@ -19,7 +19,7 @@ redirect_from:
 | OS                                        | Native: Linux                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
 | Web Server                                | NginX—preferred. But any webserver which supports PHP will work such as lighttpd, Apache, Cherokee.                                                                                                                                                                                                                                                                                                                                                                   |
 | Databases                                 | Depending on the project, one of the databases: MariaDB >= 10.4—preferred, PostgreSQL >=9.6, or MySQL >=5.7.                                                                                                                                                                                                                                                                                                                                                          |
-| PHP                                       | Spryker supports PHP `>=8.0` with the following extensions: `curl`, `json`, `mysql`, `pdo-sqlite`, `sqlite3`, `gd`, `intl`, `mysqli`, `pgsql`, `ssh2`, `gmp`, `mcrypt`, `pdo-mysql`, `readline`, `twig`, `imagick`, `memcache`, `pdo-pgsql`, `redis`, `xml`, `bz2`, `mbstring`. See [Supported Versions of PHP](/docs/about/all/whats-new/supported-versions-of-php.html) for details on the supported PHP versions. |
+| PHP                                       | Spryker supports PHP `>=8.0` with the following extensions: `curl`, `json`, `mysql`, `pdo-sqlite`, `sqlite3`, `gd`, `intl`, `mysqli`, `pgsql`, `ssh2`, `gmp`, `mcrypt`, `pdo-mysql`, `readline`, `twig`, `imagick`, `memcache`, `pdo-pgsql`, `redis`, `xml`, `bz2`, `mbstring`. See [Supported Versions of PHP](/docs/dg/dev/supported-versions-of-php.html) for details on the supported PHP versions. |
 | SSL                                       | For production systems, a valid security certificate is required for HTTPS.                                                                                                                                                                                                                                                                                                                                                                                           |
 | Redis                                     | Version >=3.2, >=5.0                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
 | Elasticsearch                             | Version 7.x                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
@@ -41,7 +41,7 @@ redirect_from:
 |---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | Web Server                                | NginX—preferred. But any webserver which supports PHP will work such as lighttpd, Apache, Cherokee.                                                                                                                                                                                                                                                                                                                                       |
 | Databases                               | Depending on the project, one of the databases: MariaDB >= 10.4—preferred, PostgreSQL >=9.6, or MySQL >=5.7.                                                                                                                                                                                                                                                                                                                              |
-| PHP                                       | Spryker supports PHP `>=8.0` with the following extensions: `curl`, `json`, `mysql`, `pdo-sqlite`, `sqlite3`, `gd`, `intl`, `mysqli`, `pgsql`, `ssh2`, `gmp`, `mcrypt`, `pdo-mysql`, `readline`, `twig`, `imagick`, `memcache`, `pdo-pgsql`, `redis`, `xml`, `bz2`, `mbstring`. For details about the supported PHP versions, see [Supported Versions of PHP](/docs/about/all/whats-new/supported-versions-of-php.html). |
+| PHP                                       | Spryker supports PHP `>=8.0` with the following extensions: `curl`, `json`, `mysql`, `pdo-sqlite`, `sqlite3`, `gd`, `intl`, `mysqli`, `pgsql`, `ssh2`, `gmp`, `mcrypt`, `pdo-mysql`, `readline`, `twig`, `imagick`, `memcache`, `pdo-pgsql`, `redis`, `xml`, `bz2`, `mbstring`. For details about the supported PHP versions, see [Supported Versions of PHP](/docs/dg/dev/supported-versions-of-php.html). |
 | SSL                                       | For production systems, a valid security certificate is required for HTTPS.                                                                                                                                                                                                                                                                                                                                                               |
 | Redis                                     | Version >=3.2, >=5.0                                                                                                                                                                                                                                                                                                                                                                                                                      |
 | Elasticsearch                             | Version 6.*x* or 7.*x*                                                                                                                                                                                                                                                                                                                                                                                                                    |
diff --git a/docs/dg/dev/system-requirements/202307.0/system-requirements.md b/docs/dg/dev/system-requirements/202307.0/system-requirements.md
index fa6353d2904..3839124c8fb 100644
--- a/docs/dg/dev/system-requirements/202307.0/system-requirements.md
+++ b/docs/dg/dev/system-requirements/202307.0/system-requirements.md
@@ -21,7 +21,7 @@ redirect_from:
 | OS                                        | Native: Linux                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
 | Web Server                                | NginX—preferred. But any webserver which supports PHP will work such as lighttpd, Apache, Cherokee.                                                                                                                                                                                                                                                                                                                                                                   |
 | Databases                                 | Depending on the project, one of the databases: MariaDB >= 10.4—preferred, PostgreSQL >=9.6, or MySQL >=5.7.                                                                                                                                                                                                                                                                                                                                                          |
-| PHP                                       | Spryker supports PHP `>=8.1` with the following extensions: `curl`, `json`, `mysql`, `pdo-sqlite`, `sqlite3`, `gd`, `intl`, `mysqli`, `pgsql`, `ssh2`, `gmp`, `mcrypt`, `pdo-mysql`, `readline`, `twig`, `imagick`, `memcache`, `pdo-pgsql`, `redis`, `xml`, `bz2`, and `mbstring`. For details about the supported PHP versions, see [Supported Versions of PHP](/docs/about/all/whats-new/supported-versions-of-php.html) |
+| PHP                                       | Spryker supports PHP `>=8.1` with the following extensions: `curl`, `json`, `mysql`, `pdo-sqlite`, `sqlite3`, `gd`, `intl`, `mysqli`, `pgsql`, `ssh2`, `gmp`, `mcrypt`, `pdo-mysql`, `readline`, `twig`, `imagick`, `memcache`, `pdo-pgsql`, `redis`, `xml`, `bz2`, and `mbstring`. For details about the supported PHP versions, see [Supported Versions of PHP](/docs/dg/dev/supported-versions-of-php.html) |
 | SSL                                       | For production systems, a valid security certificate is required for HTTPS.                                                                                                                                                                                                                                                                                                                                                                                           |
 | Redis                                     | Version >=3.2, >=5.0                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
 | Elasticsearch                             | Version 7.*x*                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
@@ -40,7 +40,7 @@ redirect_from:
 |---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | Web Server                                | NginX—preferred. But any webserver which supports PHP will work such as lighttpd, Apache, Cherokee.                                                                                                                                                                                                                                                                                                                                                                       |
 | Databases                               | Depending on the project, one of the databases: MariaDB >= 10.4—preferred, PostgreSQL >=9.6, or MySQL >=5.7.                                                                                                                                                                                                                                                                                                                                                              |
-| PHP                                       | Spryker supports PHP `>=8.1` with the following extensions: `curl`, `json`, `mysql`, `pdo-sqlite`, `sqlite3`, `gd`, `intl`, `mysqli`, `pgsql`, `ssh2`, `gmp`, `mcrypt`, `pdo-mysql`, `readline`, `twig`, `imagick`, `memcache`, `pdo-pgsql`, `redis`, `xml`, `bz2`, `mbstring`. For details about the supported PHP versions, see [Supported Versions of PHP](/docs/about/all/whats-new/supported-versions-of-php.html). |
+| PHP                                       | Spryker supports PHP `>=8.1` with the following extensions: `curl`, `json`, `mysql`, `pdo-sqlite`, `sqlite3`, `gd`, `intl`, `mysqli`, `pgsql`, `ssh2`, `gmp`, `mcrypt`, `pdo-mysql`, `readline`, `twig`, `imagick`, `memcache`, `pdo-pgsql`, `redis`, `xml`, `bz2`, `mbstring`. For details about the supported PHP versions, see [Supported Versions of PHP](/docs/dg/dev/supported-versions-of-php.html). |
 | SSL                                       | For production systems, a valid security certificate is required for HTTPS.                                                                                                                                                                                                                                                                                                                                                                                               |
 | Redis                                     | Version >=3.2, >=5.0                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
 | Elasticsearch                             | Version 6.*x* or 7.*x*                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
diff --git a/docs/dg/dev/system-requirements/202311.0/system-requirements.md b/docs/dg/dev/system-requirements/202311.0/system-requirements.md
index 0971569345d..36c8769a583 100644
--- a/docs/dg/dev/system-requirements/202311.0/system-requirements.md
+++ b/docs/dg/dev/system-requirements/202311.0/system-requirements.md
@@ -23,7 +23,7 @@ redirect_from:
 | OS                                        | Native: Linux                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
 | Web Server                                | NginX—preferred. But any webserver which supports PHP will work such as lighttpd, Apache, Cherokee.                                                                                                                                                                                                                                                                                                                                                                   |
 | Databases                                 | Depending on the project, one of the databases: MariaDB >= 10.4—preferred, PostgreSQL >=9.6, or MySQL >=5.7.                                                                                                                                                                                                                                                                                                                                                          |
-| PHP                                       | Spryker supports PHP `>=8.1` with the following extensions: `curl`, `json`, `mysql`, `pdo-sqlite`, `sqlite3`, `gd`, `intl`, `mysqli`, `pgsql`, `ssh2`, `gmp`, `mcrypt`, `pdo-mysql`, `readline`, `twig`, `imagick`, `memcache`, `pdo-pgsql`, `redis`, `xml`, `bz2`, and `mbstring`. For details about the supported PHP versions, see [Supported Versions of PHP](/docs/about/all/whats-new/supported-versions-of-php.html) |
+| PHP                                       | Spryker supports PHP `>=8.1` with the following extensions: `curl`, `json`, `mysql`, `pdo-sqlite`, `sqlite3`, `gd`, `intl`, `mysqli`, `pgsql`, `ssh2`, `gmp`, `mcrypt`, `pdo-mysql`, `readline`, `twig`, `imagick`, `memcache`, `pdo-pgsql`, `redis`, `xml`, `bz2`, and `mbstring`. For details about the supported PHP versions, see [Supported Versions of PHP](/docs/dg/dev/supported-versions-of-php.html) |
 | SSL                                       | For production systems, a valid security certificate is required for HTTPS.                                                                                                                                                                                                                                                                                                                                                                                           |
 | Redis                                     | Version >=3.2, >=5.0                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
 | Elasticsearch                             | Version 7.*x*                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
@@ -42,7 +42,7 @@ redirect_from:
 |---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | Web Server                                | NginX—preferred. But any webserver which supports PHP will work such as lighttpd, Apache, Cherokee.                                                                                                                                                                                                                                                                                                                                                                       |
 | Databases                               | Depending on the project, one of the databases: MariaDB >= 10.4—preferred, PostgreSQL >=9.6, or MySQL >=5.7.                                                                                                                                                                                                                                                                                                                                                              |
-| PHP                                       | Spryker supports PHP `>=8.1` with the following extensions: `curl`, `json`, `mysql`, `pdo-sqlite`, `sqlite3`, `gd`, `intl`, `mysqli`, `pgsql`, `ssh2`, `gmp`, `mcrypt`, `pdo-mysql`, `readline`, `twig`, `imagick`, `memcache`, `pdo-pgsql`, `redis`, `xml`, `bz2`, `mbstring`. For details about the supported PHP versions, see [Supported Versions of PHP](/docs/about/all/whats-new/supported-versions-of-php.html). |
+| PHP                                       | Spryker supports PHP `>=8.1` with the following extensions: `curl`, `json`, `mysql`, `pdo-sqlite`, `sqlite3`, `gd`, `intl`, `mysqli`, `pgsql`, `ssh2`, `gmp`, `mcrypt`, `pdo-mysql`, `readline`, `twig`, `imagick`, `memcache`, `pdo-pgsql`, `redis`, `xml`, `bz2`, `mbstring`. For details about the supported PHP versions, see [Supported Versions of PHP](/docs/dg/dev/supported-versions-of-php.html). |
 | SSL                                       | For production systems, a valid security certificate is required for HTTPS.                                                                                                                                                                                                                                                                                                                                                                                               |
 | Redis                                     | Version >=3.2, >=5.0                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
 | Elasticsearch                             | Version 6.*x* or 7.*x*                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
diff --git a/docs/dg/dev/troubleshooting/troubleshooting-performance-issues/troubleshooting-performance-issues.md b/docs/dg/dev/troubleshooting/troubleshooting-performance-issues/troubleshooting-performance-issues.md
index 4fe88d46c2f..6ad0b8d72fa 100644
--- a/docs/dg/dev/troubleshooting/troubleshooting-performance-issues/troubleshooting-performance-issues.md
+++ b/docs/dg/dev/troubleshooting/troubleshooting-performance-issues/troubleshooting-performance-issues.md
@@ -104,5 +104,5 @@ Blackfire groups some actions, so after each round of optimization, you will see
   - Repeat.
 4. Check if your result is still good for future growth. Return to the previous step if needed.
 5. Share your experience:
-  - [Contribute to public documentation](/docs/about/all/contribute-to-the-documentation/contribute-to-the-documentation.html).
+  - [Contribute to public documentation](/docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.html).
   - Share it with [Spryker Community](https://spryker.com/community/).
diff --git a/docs/dg/dev/troubleshooting/troubleshooting.md b/docs/dg/dev/troubleshooting/troubleshooting.md
index b988c3611bd..160ec562aa5 100644
--- a/docs/dg/dev/troubleshooting/troubleshooting.md
+++ b/docs/dg/dev/troubleshooting/troubleshooting.md
@@ -36,4 +36,4 @@ If you can not find answer to your questions and require technical support, you
 
 * [How Spryker support works](/docs/about/all/support/how-spryker-support-works.html)
 * [How to get the most out of support](/docs/about/all/support/getting-the-most-out-of-spryker-support.html)
-* [Understanding ticket status](/docs/about/all/support/understanding-ticket-status.html)
+* [Understanding ticket status](/docs/about/all/support/support-ticket-statuses.html)

From e9adb1b43a7a8433900d3c23ec30329101896f4f Mon Sep 17 00:00:00 2001
From: Andrii Tserkovnyi <andrii.tserkovnyi@spryker.com>
Date: Tue, 19 Mar 2024 15:29:51 +0200
Subject: [PATCH 18/26] links

---
 _data/sidebars/about_all_sidebar.yml          | 62 +++++++++----------
 .../contributing-to-documentation.md          |  2 +-
 .../add-global-sections-to-the-docs.md        | 14 ++---
 .../add-and-edit-diagrams-in-the-docs.md      |  8 +--
 .../contribute-to-the-docs.md                 | 20 +++---
 .../edit-the-docs-locally.md                  |  2 +-
 .../edit-the-docs-using-a-web-browser.md      | 16 ++---
 .../report-docs-issues.md                     | 12 ++--
 .../review-pull-requests.md                   | 12 ++--
 .../install-recommended-vs-code-extensions.md | 12 ++--
 .../about-the-docs/run-the-docs-locally.md    | 12 ++--
 ...eral-rules-and-guidance-for-adding-docs.md | 14 ++---
 .../style-guide/markdown-syntax.md            | 12 ++--
 docs/about/all/docs-updates.md                | 12 ++--
 docs/{dg/dev => about/all}/master-suite.md    |  0
 .../all/releases/product-and-code-releases.md |  2 +-
 docs/about/all/spryker-academy.md             | 17 -----
 docs/about/all/support/getting-support.md     |  2 +-
 .../all/support/using-the-support-portal.md   |  2 +-
 docs/ca/dev/preparation-for-going-live.md     |  6 +-
 ...nstalling-features-and-updating-modules.md |  2 +-
 .../dev/updating-spryker/updating-spryker.md  |  2 +-
 22 files changed, 111 insertions(+), 132 deletions(-)
 rename docs/{dg/dev => about/all}/master-suite.md (100%)
 delete mode 100644 docs/about/all/spryker-academy.md

diff --git a/_data/sidebars/about_all_sidebar.yml b/_data/sidebars/about_all_sidebar.yml
index d7f34890814..a8e818339c4 100644
--- a/_data/sidebars/about_all_sidebar.yml
+++ b/_data/sidebars/about_all_sidebar.yml
@@ -14,43 +14,43 @@ entries:
       - title: Security release notes 202309.0
         url: /docs/about/all/releases/security-release-notes-202309.0.html
       - title: Release notes 202307.0
-        url: /docs/about/all/releases/release-notes-202307.0.html
+        url: /docs/about/all/releases/release-notes-202307.0/release-notes-202307.0.html
         nested:
         - title: Security release notes 202307.0
           url: /docs/about/all/releases/release-notes-202307.0/security-release-notes-202307.0.html
       - title: Security release notes 202306.0
         url: /docs/about/all/releases/security-release-notes-202306.0.html
       - title: Security release notes 202304.0
-        url: /docs/about/all/releases/release-notes-202304.0/security-release-notes-202304.0.html
+        url: /docs/about/all/releases/security-release-notes-202304.0.html
       - title: Security release notes 202302.0
-        url: /docs/about/all/releases/release-notes-202302.0/security-release-notes-202302.0.html
+        url: /docs/about/all/releases/security-release-notes-202302.0.html
       - title: Release notes 202212.0
         url: /docs/about/all/releases/release-notes-202212.0/release-notes-202212.0.html
         nested:
         - title: Patch releases 202212.0
-          url: /docs/about/all/releases/release-notes-202212.0/patch-releases-202212.0.html
+          url: /docs/about/all/releases/release-notes-202212.0/patch-release-notes-202212.0.html
         - title: Security release notes 202212.0
           url: /docs/about/all/releases/release-notes-202212.0/security-release-notes-202212.0.html
 
     - title: Security audit reports
       nested:
       - title: 2019.11 - Security audit by SektionEins
-        url: /docs/about/all/whats-new/security-audit-reports/2019.11-security-audit-by-sektioneins.html
+        url: /docs/about/all/security-audit-reports/2019.11-security-audit-by-sektioneins.html
       - title: 2020.11 - Penetration test by Port Zero (executive summary)
-        url: /docs/about/all/whats-new/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.html
+        url: /docs/about/all/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.html
 
     - title: Docs updates
-      url: /docs/about/all/docs-release-notes.html
+      url: /docs/about/all/docs-updates.html
 
     - title: Support
       url: /docs/about/all/support/getting-support.html
       nested:
       - title: How Spryker Support works
         url: /docs/about/all/support/how-spryker-support-works.html
-      - title: Support case escalation
-        url: /docs/about/all/support/case-escalation.html
+      - title: Support case escalations
+        url: /docs/about/all/support/support-case-escalations.html
       - title: Preparing for heavy loads and traffic
-        url: /docs/about/all/support/special-prepare-for-a-busy-season.html
+        url: /docs/about/all/support/preparing-for-heavy-loads-and-traffic.html
       - title: How to use the Support Portal
         url: /docs/about/all/support/using-the-support-portal.html
       - title: Share secrets with the Spryker Support Team
@@ -58,19 +58,17 @@ entries:
       - title: Understanding ticket status
         url: /docs/about/all/support/support-ticket-statuses.html
       - title: Handling security issues
-        url: /docs/about/all/support/handling-security-issues.html
+        url: /docs/about/all/support/reporting-and-handling-security-issues.html
       - title: Guidelines for GDPR compliance
-        url: /docs/about/all/support/guidelines-for-new-gdpr-rules.html
+        url: /docs/about/all/support/guidelines-for-gdpr-compliance.html
       - title: Getting the most out of Spryker Support
         url: /docs/about/all/support/getting-the-most-out-of-spryker-support.html
       - title: Understand SLAs
-        url: /docs/about/all/support/understand-slas.html
+        url: /docs/about/all/support/understanding-slas.html
       - title: Escalations
-        url: /docs/about/all/support/escalations.html
-      - title: How to contact Spryker Support
-        url: /docs/about/all/support/how-to-contact-spryker-support.html
+        url: /docs/about/all/support/support-case-escalations.html
       - title: Understanding Project and Core Level Fixes
-        url: /docs/about/all/support/understanding-project-and-core-level-fixes.html
+        url: /docs/about/all/support/project-level-and-core-level-fixes.html
 
     - title: Supported browsers
       url: /docs/about/all/supported-browsers.html
@@ -94,41 +92,39 @@ entries:
       - title: Marketplace B2B Suite
         url: /docs/about/all/spryker-marketplace/marketplace-b2b-suite.html
 
-    - title: Spryker Academy
-      url: /docs/about/all/spryker-academy.html
     - title: Contribute to the documentation
       url: /docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.html
       nested:
       - title: Edit the documentation via pull requests
-        url: /docs/about/all/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
+        url: /docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
       - title: Edit the documentation locally
-        url: /docs/about/all/contribute-to-the-documentation/edit-the-documentation-locally.html
+        url: /docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-locally.html
       - title: General rules and guidance for adding new documents
-        url: /docs/about/all/contribute-to-the-documentation/general-rules-and-guidance-for-adding-new-documents.html
+        url: /docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.html
       - title: Markdown syntax
-        url: /docs/about/all/contribute-to-the-documentation/markdown-syntax.html
+        url: /docs/about/all/about-the-docs/contribute-to-the-docs/markdown-syntax.html
       - title: Spryker documentation style guide
-        url: /docs/about/all/contribute-to-the-documentation/spryker-documentation-style-guide/spryker-documentation-style-guide.html
+        url: /docs/about/all/about-the-docs/contribute-to-the-docs/spryker-documentation-style-guide/spryker-documentation-style-guide.html
         nested:
           - title: Examples
-            url: /docs/about/all/contribute-to-the-documentation/spryker-documentation-style-guide/examples.html
+            url: /docs/about/all/about-the-docs/contribute-to-the-docs/spryker-documentation-style-guide/examples.html
           - title: Spelling
-            url: /docs/about/all/contribute-to-the-documentation/spryker-documentation-style-guide/spelling.html
+            url: /docs/about/all/about-the-docs/contribute-to-the-docs/spryker-documentation-style-guide/spelling.html
           - title: Word list
-            url: /docs/about/all/contribute-to-the-documentation/spryker-documentation-style-guide/word-list.html
+            url: /docs/about/all/about-the-docs/contribute-to-the-docs/spryker-documentation-style-guide/word-list.html
 
       - title: Add and edit diagrams
-        url: /docs/about/all/contribute-to-the-documentation/add-and-edit-diagrams-in-the-documentation.html
+        url: /docs/about/all/about-the-docs/contribute-to-the-docs/add-and-edit-diagrams-in-the-documentation.html
       - title: Install recommended VS Code extensions
-        url: /docs/about/all/contribute-to-the-documentation/install-recommended-vs-code-extensions.html
+        url: /docs/about/all/about-the-docs/contribute-to-the-docs/install-recommended-vs-code-extensions.html
       - title: Report documentation issues
-        url: /docs/about/all/contribute-to-the-documentation/report-documentation-issues.html
+        url: /docs/about/all/about-the-docs/contribute-to-the-docs/report-documentation-issues.html
       - title: Build the documentation site
-        url: /docs/about/all/contribute-to-the-documentation/build-the-documentation-site.html
+        url: /docs/about/all/about-the-docs/contribute-to-the-docs/build-the-documentation-site.html
       - title: Review pull requests
-        url: /docs/about/all/contribute-to-the-documentation/review-pull-requests.html
+        url: /docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html
       - title: Add product sections to the documentation
-        url: /docs/about/all/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
+        url: /docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-documentation.html
 
 
 
diff --git a/_drafts/drafts-dev/contributing-to-documentation.md b/_drafts/drafts-dev/contributing-to-documentation.md
index 8206c0203d1..8f44c86e9ed 100644
--- a/_drafts/drafts-dev/contributing-to-documentation.md
+++ b/_drafts/drafts-dev/contributing-to-documentation.md
@@ -13,7 +13,7 @@ To report issues and fix documentation, you need a [GitHub account](https://gith
 
 {% endinfo_block %}
 
-We use [Markdown](https://guides.github.com/features/mastering-markdown/) to write documentation and [Jekyll](https://jekyllrb.com/) to build the documentation site. You do not necessarily need to build the documentation site locally on your machine to propose your changes, but if you want to, follow the instructions in [Build documentation site](/docs/about/all/contribute-to-the-documentation/build-the-documentation-site.html).
+We use [Markdown](https://guides.github.com/features/mastering-markdown/) to write documentation and [Jekyll](https://jekyllrb.com/) to build the documentation site. You do not necessarily need to build the documentation site locally on your machine to propose your changes, but if you want to, follow the instructions in [Build documentation site](/docs/about/all/about-the-docs/contribute-to-the-docs/build-the-documentation-site.html).
 
 ## Next steps
 Build the documentation site locally
diff --git a/docs/about/all/about-the-docs/add-global-sections-to-the-docs.md b/docs/about/all/about-the-docs/add-global-sections-to-the-docs.md
index d78fd06f54b..bf00a8b0353 100644
--- a/docs/about/all/about-the-docs/add-global-sections-to-the-docs.md
+++ b/docs/about/all/about-the-docs/add-global-sections-to-the-docs.md
@@ -11,17 +11,17 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/about/all/contribute-to-the-documentation/build-the-documentation-site.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/build-the-documentation-site.html
   - title: Edit documentation via pull requests
-    link: docs/about/all/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
   - title: Report documentation issues
-    link: docs/about/all/contribute-to-the-documentation/report-documentation-issues.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/report-documentation-issues.html
   - title: Review pull requests
-    link: docs/about/all/contribute-to-the-documentation/review-pull-requests.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html
   - title: Style, syntax, formatting, and general rules
-    link: docs/about/all/contribute-to-the-documentation/style-formatting-general-rules.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
-    link: docs/about/all/contribute-to-the-documentation/markdown-syntax.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/markdown-syntax.html
 ---
 
 This document describes how to add global sections to the documentation, like the existing Development or Cloud administration sections.
@@ -38,7 +38,7 @@ In the `/docs` directory, create a folder for the section per role. In this exam
 
 In `_data/sidebars`, create sidebars for the new section per role: `{product_name}_{role}_sidebar.yml`. For the *acp* section with user and developer roles, create `acp_dev_sidebar.yml` and `acp_user_sidebar.yml` sidebar files.
 
-To learn how to populate sidebar files, see [Sidebars](/docs/about/all/contribute-to-the-documentation/general-rules-and-guidance-for-adding-new-documents.html#sidebars).
+To learn how to populate sidebar files, see [Sidebars](/docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.html#sidebars).
 
 ## 3. Update the configuration
 
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/add-and-edit-diagrams-in-the-docs.md b/docs/about/all/about-the-docs/contribute-to-the-docs/add-and-edit-diagrams-in-the-docs.md
index ec5510fa20e..30af46a810e 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/add-and-edit-diagrams-in-the-docs.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/add-and-edit-diagrams-in-the-docs.md
@@ -8,9 +8,9 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/about/all/contribute-to-the-documentation/build-the-documentation-site.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/build-the-documentation-site.html
   - title: Edit documentation via pull requests
-    link: docs/about/all/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
 ---
 
 We are using [diagrams.net](https://www.diagrams.net/) to create and collaborate on diagrams. diagrams.net provides both a web and desktop applications. To download the latest desktop version, go to [diagrams.net](https://www.diagrams.net/) and click **Download**. Alternatively, you can work on diagrams in a [web app](https://app.diagrams.net/). You can store diagrams in any suitable source.
@@ -24,7 +24,7 @@ After creating a diagram, to embed it into a document, do the following:
     This generates code for embedding the diagram.
 3. To copy the code, click **Copy**.
 4. Open the document you want to add the diagram to in an editor.
-    For instructions about editing the documentation, see [Edit documentation via pull requests](/docs/about/all/contribute-to-the-documentation/edit-documentation-via-pull-requests.html).
+    For instructions about editing the documentation, see [Edit documentation via pull requests](/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html).
 5. Paste the code into the needed place of a document and submit a PR.
     After the PR is merged, the diagram appears on the page.
 
@@ -40,7 +40,7 @@ After creating a diagram, to embed it into a document, do the following:
     This generates code for embedding the diagram.
 6. To copy the code, click **Copy**.
 7. Open the document containing the original diagram in an editor.
-        For instructions about editing the documentation, see [Edit documentation via pull requests](/docs/about/all/contribute-to-the-documentation/edit-documentation-via-pull-requests.html).
+        For instructions about editing the documentation, see [Edit documentation via pull requests](/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html).
 8. Replace the original code with the one you've copied.
 9. Submit a PR with the changes.
     After the PR is merged, the updated diagram appears on the page.
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.md b/docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.md
index c78f6aea260..bede7bd3ece 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.md
@@ -9,25 +9,25 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/about/all/contribute-to-the-documentation/build-the-documentation-site.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/build-the-documentation-site.html
   - title: Add product sections to the documentation
-    link: docs/about/all/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-documentation.html
   - title: Edit documentation via pull requests
-    link: docs/about/all/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
   - title: Report documentation issues
-    link: docs/about/all/contribute-to-the-documentation/report-documentation-issues.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/report-documentation-issues.html
   - title: Review pull requests
-    link: docs/about/all/contribute-to-the-documentation/review-pull-requests.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html
   - title: Style, syntax, formatting, and general rules
-    link: docs/about/all/contribute-to-the-documentation/style-formatting-general-rules.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
-    link: docs/about/all/contribute-to-the-documentation/markdown-syntax.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/markdown-syntax.html
 ---
 
 We at Spryker aim to constantly improve the content we provide our customers and partners with. You can get involved in improving the Spryker documentation by:
 
-* [Reporting issues via GitHub](/docs/about/all/contribute-to-the-documentation/report-documentation-issues.html).
-* [Editing documentation by creating pull requests on GitHub](/docs/about/all/contribute-to-the-documentation/edit-documentation-via-pull-requests.html).
-* [Reviewing pull requests](/docs/about/all/contribute-to-the-documentation/review-pull-requests.html).
+* [Reporting issues via GitHub](/docs/about/all/about-the-docs/contribute-to-the-docs/report-documentation-issues.html).
+* [Editing documentation by creating pull requests on GitHub](/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html).
+* [Reviewing pull requests](/docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html).
 
 Therefore, to contribute to the Spryker documentation, you must have a GitHub account. For information about how to create it, see [Signing up for a new GitHub account](https://docs.github.com/en/get-started/signing-up-for-github/signing-up-for-a-new-github-account) in the official GitHub documentation.
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-locally.md b/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-locally.md
index 0ecbde38936..a7e0b088059 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-locally.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-locally.md
@@ -61,7 +61,7 @@ At this point, you are most likely to know which document you want to edit. To f
 
 1. Open the document you want to edit in an editor.
 2. Add the needed changes.
-    You'd help us a lot by following [Markdown syntax](/docs/about/all/contribute-to-the-documentation/markdown-syntax.html) and [general rules](/docs/about/all/contribute-to-the-documentation/style-formatting-general-rules.html), but it's completely optional. We are grateful for your contribution in any form.
+    You'd help us a lot by following [Markdown syntax](/docs/about/all/about-the-docs/contribute-to-the-docs/markdown-syntax.html) and [general rules](/docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html), but it's completely optional. We are grateful for your contribution in any form.
 3. Save the edited document.
 4. In GitHub Desktop, double-check your changes in the **Changes** tab.
 5. Below the list of edited files, enter the name and description of your changes. The name of your fist commit will be used as the pull request's name.
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.md b/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.md
index 8eab0bbbf62..574e19ec2d9 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.md
@@ -11,24 +11,24 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/about/all/contribute-to-the-documentation/build-the-documentation-site.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/build-the-documentation-site.html
   - title: Addi product sections to the documentation
-    link: docs/about/all/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-documentation.html
   - title: Report documentation issues
-    link: docs/about/all/contribute-to-the-documentation/report-documentation-issues.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/report-documentation-issues.html
   - title: Review pull requests
-    link: docs/about/all/contribute-to-the-documentation/review-pull-requests.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html
   - title: Style, syntax, formatting, and general rules
-    link: docs/about/all/contribute-to-the-documentation/style-formatting-general-rules.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
-    link: docs/about/all/contribute-to-the-documentation/markdown-syntax.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/markdown-syntax.html
 ---
 
 The Spryker documentation is hosted on GitHub, in the [spryker-docs](https://github.com/spryker/spryker-docs) repository. Therefore, to contribute to the Spryker documents, you have to use GitHub. For more information about what GitHub is, see [About Git](https://docs.github.com/en/get-started/using-git/about-git).
 
 {% info_block infoBox "Info" %}
 
-We write the Spryker documentation using Markdown. If you don’t know Markdown yet, check the [GitHub Markdown Guide](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax). For the documentation-specific Markdown elements and HTML syntax used where Markdown is not enough, see [Markdown syntax](/docs/about/all/contribute-to-the-documentation/markdown-syntax.html).
+We write the Spryker documentation using Markdown. If you don’t know Markdown yet, check the [GitHub Markdown Guide](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax). For the documentation-specific Markdown elements and HTML syntax used where Markdown is not enough, see [Markdown syntax](/docs/about/all/about-the-docs/contribute-to-the-docs/markdown-syntax.html).
 
 {% endinfo_block %}
 
@@ -36,7 +36,7 @@ This instruction explains how to contribute to the Spryker documentation by crea
 
 {% info_block infoBox "Info" %}
 
-For information about the structure of the Spryker documentation, as well as style and formatting rules, see [Style, syntax, formatting, and general rules](/docs/about/all/contribute-to-the-documentation/style-formatting-general-rules.html).
+For information about the structure of the Spryker documentation, as well as style and formatting rules, see [Style, syntax, formatting, and general rules](/docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html).
 
 
 Note that Spryker documentation is written in US English.
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.md b/docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.md
index 4494aaca96d..470476e16e3 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.md
@@ -9,17 +9,17 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/about/all/contribute-to-the-documentation/build-the-documentation-site.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/build-the-documentation-site.html
   - title: Add product sections to the documentation
-    link: docs/about/all/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-documentation.html
   - title: Edit documentation via pull requests
-    link: docs/about/all/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
   - title: Review pull requests
-    link: docs/about/all/contribute-to-the-documentation/review-pull-requests.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html
   - title: Style, syntax, formatting, and general rules
-    link: docs/about/all/contribute-to-the-documentation/style-formatting-general-rules.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
-    link: docs/about/all/contribute-to-the-documentation/markdown-syntax.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/markdown-syntax.html
 ---
 
 To report an issue with a Spryker document, do the following:
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.md b/docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.md
index ed1c28b7fa5..5c69ab48e92 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.md
@@ -9,17 +9,17 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/about/all/contribute-to-the-documentation/build-the-documentation-site.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/build-the-documentation-site.html
   - title: Add product sections to the documentation
-    link: docs/about/all/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-documentation.html
   - title: Edit documentation via pull requests
-    link: docs/about/all/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
   - title: Report documentation issues
-    link: docs/about/all/contribute-to-the-documentation/report-documentation-issues.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/report-documentation-issues.html
   - title: Style, syntax, formatting, and general rules
-    link: docs/about/all/contribute-to-the-documentation/style-formatting-general-rules.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
-    link: docs/about/all/contribute-to-the-documentation/markdown-syntax.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/markdown-syntax.html
 ---
 
 When someone requests your review of a pull request, you get an email about the request. <!--Also, a message with the review request is displayed on the pull request page:IMAGE-->
diff --git a/docs/about/all/about-the-docs/install-recommended-vs-code-extensions.md b/docs/about/all/about-the-docs/install-recommended-vs-code-extensions.md
index 2fef35067f3..74687f47ee1 100644
--- a/docs/about/all/about-the-docs/install-recommended-vs-code-extensions.md
+++ b/docs/about/all/about-the-docs/install-recommended-vs-code-extensions.md
@@ -8,17 +8,17 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/about/all/contribute-to-the-documentation/build-the-documentation-site.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/build-the-documentation-site.html
   - title: Addi product sections to the documentation
-    link: docs/about/all/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-documentation.html
   - title: Report documentation issues
-    link: docs/about/all/contribute-to-the-documentation/report-documentation-issues.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/report-documentation-issues.html
   - title: Review pull requests
-    link: docs/about/all/contribute-to-the-documentation/review-pull-requests.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html
   - title: Style, syntax, formatting, and general rules
-    link: docs/about/all/contribute-to-the-documentation/style-formatting-general-rules.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
-    link: docs/about/all/contribute-to-the-documentation/markdown-syntax.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/markdown-syntax.html
 ---
 
 We recommend the following VS Code extensions for writing and reviewing documents:
diff --git a/docs/about/all/about-the-docs/run-the-docs-locally.md b/docs/about/all/about-the-docs/run-the-docs-locally.md
index d8ea45cb969..3ce2019a6c5 100644
--- a/docs/about/all/about-the-docs/run-the-docs-locally.md
+++ b/docs/about/all/about-the-docs/run-the-docs-locally.md
@@ -9,17 +9,17 @@ redirect_from:
 
 related:
   - title: Add product sections to the documentation
-    link: docs/about/all/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-documentation.html
   - title: Edit documentation via pull requests
-    link: docs/about/all/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
   - title: Report documentation issues
-    link: docs/about/all/contribute-to-the-documentation/report-documentation-issues.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/report-documentation-issues.html
   - title: Review pull requests
-    link: docs/about/all/contribute-to-the-documentation/review-pull-requests.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html
   - title: Style, syntax, formatting, and general rules
-    link: docs/about/all/contribute-to-the-documentation/style-formatting-general-rules.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
-    link: docs/about/all/contribute-to-the-documentation/markdown-syntax.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/markdown-syntax.html
 ---
 
 We use [Jekyll](https://jekyllrb.com/) to build the Spryker documentation site. To build it locally, you need to:
diff --git a/docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.md b/docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.md
index 6e3533f4fbd..184548e2cd3 100644
--- a/docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.md
+++ b/docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.md
@@ -10,17 +10,17 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/about/all/contribute-to-the-documentation/build-the-documentation-site.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/build-the-documentation-site.html
   - title: Add product sections to the documentation
-    link: docs/about/all/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-documentation.html
   - title: Edit documentation via pull requests
-    link: docs/about/all/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
   - title: Report documentation issues
-    link: docs/about/all/contribute-to-the-documentation/report-documentation-issues.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/report-documentation-issues.html
   - title: Review pull requests
-    link: docs/about/all/contribute-to-the-documentation/review-pull-requests.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html
   - title: Markdown syntax
-    link: docs/about/all/contribute-to-the-documentation/markdown-syntax.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/markdown-syntax.html
 ---
 
 This document describes the directory structure, templates, front matter, and versioning of Spryker documentation.
@@ -33,7 +33,7 @@ The main directory for holding all the documents is [docs](https://github.com/sp
 
 ## Creating documents and categories
 
-We use [Markdown (.md)](https://en.wikipedia.org/wiki/Markdown) to write documents. All documents reside in the [docs](https://github.com/spryker/spryker-docs/tree/master/docs) directory. For details about how this directory is organized, see [Directory structure](#directory-structure). You can use any text editor for creating the files in Markdown, like [VSCode](https://code.visualstudio.com). For information about specific Markdown syntax for documentation, see [Markdown syntax](/docs/about/all/contribute-to-the-documentation/markdown-syntax.html).
+We use [Markdown (.md)](https://en.wikipedia.org/wiki/Markdown) to write documents. All documents reside in the [docs](https://github.com/spryker/spryker-docs/tree/master/docs) directory. For details about how this directory is organized, see [Directory structure](#directory-structure). You can use any text editor for creating the files in Markdown, like [VSCode](https://code.visualstudio.com). For information about specific Markdown syntax for documentation, see [Markdown syntax](/docs/about/all/about-the-docs/contribute-to-the-docs/markdown-syntax.html).
 
 You can create new pages in any documentation category or sub-category under the *realm* directories (`user`, `dev`). You can also create directories for new categories under the *realm* directories.
 
diff --git a/docs/about/all/about-the-docs/style-guide/markdown-syntax.md b/docs/about/all/about-the-docs/style-guide/markdown-syntax.md
index 223a64db77a..84d20627569 100644
--- a/docs/about/all/about-the-docs/style-guide/markdown-syntax.md
+++ b/docs/about/all/about-the-docs/style-guide/markdown-syntax.md
@@ -9,17 +9,17 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/about/all/contribute-to-the-documentation/build-the-documentation-site.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/build-the-documentation-site.html
   - title: Adding product sections to the documentation
-    link: docs/about/all/contribute-to-the-documentation/add-global-sections-to-the-documentation.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-documentation.html
   - title: Edit documentation via pull requests
-    link: docs/about/all/contribute-to-the-documentation/edit-documentation-via-pull-requests.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
   - title: Report documentation issues
-    link: docs/about/all/contribute-to-the-documentation/report-documentation-issues.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/report-documentation-issues.html
   - title: Review pull requests
-    link: docs/about/all/contribute-to-the-documentation/review-pull-requests.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html
   - title: Style, syntax, formatting, and general rules
-    link: docs/about/all/contribute-to-the-documentation/style-formatting-general-rules.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
 ---
 
 We use Markdown to write the Spryker documentation. This document contains the Markdown syntax of the page elements used on the Spryker documentation website, specifically:
diff --git a/docs/about/all/docs-updates.md b/docs/about/all/docs-updates.md
index 59223e7754a..4fec02aadde 100644
--- a/docs/about/all/docs-updates.md
+++ b/docs/about/all/docs-updates.md
@@ -440,7 +440,7 @@ In July 2023, we have added and updated the following pages:
 - [App manifest](/docs/dg/dev/acp/develop-an-app/app-manifest.html): App Manifest is a set of JSON files that contain all the necessary information to register an application in the Application Tenant Registry Service and to display information about the application in the Application Catalog.
 - [Development strategies](/docs/dg/dev/backend-development/extend-spryker/development-strategies.html): Development strategies that you can use when building a Spryker project.
 - [Project development guidelines](/docs/dg/dev/guidelines/project-development-guidelines.html): This document describes the strategies a project team can take while building a Spryker-based project.
-- [Handling security issues](/docs/about/all/support/handling-security-issues.html): Use this document to learn how to report a security issue and to understand how we handle these reports.     
+- [Handling security issues](/docs/about/all/support/reporting-and-handling-security-issues.html): Use this document to learn how to report a security issue and to understand how we handle these reports.     
 - [Install the Measurement Units feature](/docs/pbc/all/product-information-management/202307.0/base-shop/install-and-upgrade/install-features/install-the-measurement-units-feature.html): The guide describes how to integrate the [Measurement Units](/docs/pbc/all/product-information-management/202307.0/base-shop/feature-overviews/measurement-units-feature-overview.html) feature into your project.
 
 For more details about these and other updates to the Spryker docs in July 2023, refer to the [docs release notes page on GitHub](https://github.com/spryker/spryker-docs/releases).
@@ -460,9 +460,9 @@ In June 2023, we have added and updated the following pages:
     - [File details - shipment_type_store.csv](/docs/pbc/all/carrier-management/202311.0/base-shop/import-and-export-data/import-file-details-shipment-type-store.csv.html).
     - [File details - shipment_type.csv](/docs/pbc/all/carrier-management/202311.0/base-shop/import-and-export-data/import-file-details-shipment-type.csv.html).
 - [Migration guide - Upgrade Node.js to v18 and npm to v9](/docs/dg/dev/upgrade-and-migrate/upgrade-nodejs-to-v18-and-npm-to-v9.html).
-- [Spryker documentation style guide](/docs/about/all/contribute-to-the-documentation/spryker-documentation-style-guide/spryker-documentation-style-guide.html):
-    - [Examples](/docs/about/all/contribute-to-the-documentation/spryker-documentation-style-guide/examples.html).
-    - [Spelling](/docs/about/all/contribute-to-the-documentation/spryker-documentation-style-guide/spelling.html).
+- [Spryker documentation style guide](/docs/about/all/about-the-docs/contribute-to-the-docs/spryker-documentation-style-guide/spryker-documentation-style-guide.html):
+    - [Examples](/docs/about/all/about-the-docs/contribute-to-the-docs/spryker-documentation-style-guide/examples.html).
+    - [Spelling](/docs/about/all/about-the-docs/contribute-to-the-docs/spryker-documentation-style-guide/spelling.html).
 
 ## Updated pages
 - [Environments overview](/docs/ca/dev/environments-overview.html).
@@ -491,7 +491,7 @@ In May 2023, we have added and updated the following pages:
 
 ### New pages
 
-- [Docs release notes](/docs/about/all/docs-release-notes.html)
+- [Docs release notes](/docs/about/all/docs-updates.html)
 - Multistore documentation:
     - [Multistore setup options](/docs/ca/dev/multi-store-setups/multistore-setup-options.html): Learn about all the setup options you have for a multi-store environment.
     - [Checklist for a new store implementation](/docs/ca/dev/multi-store-setups/checklist-for-a-new-store-implementation.html): Overview of the high-level tasks and responsibilities of Spryker and Customer when setting up a new store.
@@ -557,7 +557,7 @@ In April 2023, we have added and updated the following pages:
 - Warehouse picking feature integration guides:
     - [Install the Warehouse picking feature](/docs/pbc/all/warehouse-management-system/202311.0/unified-commerce/install-and-upgrade/install-the-warehouse-picking-feature.html)
     - [Install the Warehouse picking + Product feature](/docs/pbc/all/warehouse-management-system/202311.0/unified-commerce/install-and-upgrade/install-the-warehouse-picking-feature.html)
-- [Security release notes 202304.0](/docs/about/all/releases/release-notes-202304.0/security-release-notes-202304.0.html)
+- [Security release notes 202304.0](/docs/about/all/releases/security-release-notes-202304.0.html)
 - [Releases vs Customization types](/docs/dg/dev/sdks/sdk/customization-strategies-and-upgradability.html): Learn about the customization strategies and release types you can use to integrate releases and customize your project.
 
 ### Updated pages
diff --git a/docs/dg/dev/master-suite.md b/docs/about/all/master-suite.md
similarity index 100%
rename from docs/dg/dev/master-suite.md
rename to docs/about/all/master-suite.md
diff --git a/docs/about/all/releases/product-and-code-releases.md b/docs/about/all/releases/product-and-code-releases.md
index b457a7ec80a..b246dcad1e4 100644
--- a/docs/about/all/releases/product-and-code-releases.md
+++ b/docs/about/all/releases/product-and-code-releases.md
@@ -70,7 +70,7 @@ To join our release notes mailing list, subscribe here:
 
 <div class="hubspot-form js-hubspot-form" data-portal-id="2770802" data-form-id="b4d730db-d20e-4bb4-bd80-4cd7c9a2dc21" id="hubspot-1"></div>
 
-To receive the security updates, please request the subsription at [support@spryker.com](mailto:support@spryker.com).
+To receive the security updates, request a subscription at [support@spryker.com](mailto:support@spryker.com).
 
 ## Next steps
 
diff --git a/docs/about/all/spryker-academy.md b/docs/about/all/spryker-academy.md
deleted file mode 100644
index f7a6528e08e..00000000000
--- a/docs/about/all/spryker-academy.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: Spryker Academy
-description: Spryker Academy is a dedicated resource for learning Spryker Commerce OS through a variety of self-paced and instructor-led courses.
-last_updated: Sep 6, 2022
-template: concept-topic-template
-originalLink: https://documentation.spryker.com/2021080/docs/spryker-videos
-originalArticleId: e1db0ef0-24d3-4862-b493-c4bf8a4adad7
-redirect_from:
-  - /docs/scos/user/intro-to-spryker/spryker-academy.html
-  - /docs/scos/user/intro-to-spryker/videos-and-webinars/spryker-videos.html
-  - /docs/scos/user/intro-to-spryker/202204.0/videos-and-webinars/spryker-videos.html
-  - /docs/scos/user/intro-to-spryker/spryker-videos.html
----
-
-We believe that good technology doesn’t stop with the code. You also need examples and information to help you convert your vision into reality.
-
-[Spryker Academy](https://academy.spryker.com/learn) is a dedicated resource for learning our Spryker Commerce OS through a variety of self-paced and instructor-led courses.
diff --git a/docs/about/all/support/getting-support.md b/docs/about/all/support/getting-support.md
index bfca778cf8a..444b524d0f7 100644
--- a/docs/about/all/support/getting-support.md
+++ b/docs/about/all/support/getting-support.md
@@ -24,5 +24,5 @@ If you need technical help for issues that can't be resolved with the help of th
 
 Depending on the types of issues, there are several ways to report them and request support from us:
 * For bug reports and product issues, feel free to create a case for our support team at the [support portal](https://support.spryker.com).
-* For security-related issues, follow the instructions at [Security Support](/docs/about/all/support/handling-security-issues.html).
+* For security-related issues, follow the instructions at [Security Support](/docs/about/all/support/reporting-and-handling-security-issues.html).
 * For general discussions of Spryker-related questions, join the Spryker community at [CommerceQuest](https://commercequest.space/).
diff --git a/docs/about/all/support/using-the-support-portal.md b/docs/about/all/support/using-the-support-portal.md
index 93b242878f7..d3ec27b04d1 100644
--- a/docs/about/all/support/using-the-support-portal.md
+++ b/docs/about/all/support/using-the-support-portal.md
@@ -34,7 +34,7 @@ Problems can be reports suspecting a bug or issues with our hosting. Please make
 
 ### Emergencies
 
-Emergencies are reserved for problems that have significant business impact now or very soon. Emergency cases regularly start an [escalation](/docs/about/all/support/escalations.html). Please do not use this case type to simply try to speed up requests or problem reports. Emergencies need to be associated with significant risk or business impact, like revenue, security, or go-lives.
+Emergencies are reserved for problems that have significant business impact now or very soon. Emergency cases regularly start an [escalation](/docs/about/all/support/support-case-escalations.html). Please do not use this case type to simply try to speed up requests or problem reports. Emergencies need to be associated with significant risk or business impact, like revenue, security, or go-lives.
 
 ### Platform change requests
 
diff --git a/docs/ca/dev/preparation-for-going-live.md b/docs/ca/dev/preparation-for-going-live.md
index 9ebbbd844f4..d691e28f36f 100644
--- a/docs/ca/dev/preparation-for-going-live.md
+++ b/docs/ca/dev/preparation-for-going-live.md
@@ -69,9 +69,9 @@ After pointing the domain name to your Spryker project, some of your customers m
   - Apply Spryker [security guidelines](/docs/scos/dev/guidelines/security-guidelines.html).
   - Make sure that you don't have any plain-text passwords, private keys, or API secrets in config files or Git repositories.
   - Minimize the use of personal credentials and choose work-specific accounts based on each environment (production, staging, testing). We highly recommend employing Centralized Credential Management to securely store and manage these credentials.
-  - Install all the [security updates](/docs/about/all/whats-new/security-updates.html) from all Spryker packages.
+  - Install all the [security updates](/docs/about/all/releases/product-and-code-releases.html) from all Spryker packages.
   - Install all the security updates from all the external packages. To check if your project modules require security updates, you can use the [Security checker](/docs/scos/dev/guidelines/keeping-a-project-upgradable/upgradability-guidelines/spryker-security-checker.html).
-- Perform compliance and legal checks. To ensure the platform complies with relevant legal and regulatory requirements, especially for international operations, consult your legal team. Make sure to check [Guidelines for GDPR compliance](/docs/about/all/support/guidelines-for-new-gdpr-rules.html).
+- Perform compliance and legal checks. To ensure the platform complies with relevant legal and regulatory requirements, especially for international operations, consult your legal team. Make sure to check [Guidelines for GDPR compliance](/docs/about/all/support/guidelines-for-gdpr-compliance.html).
 - Make sure that the Back Office Access Control List (ACL) setup is configured correctly to manage user permissions and access rights within the system's administrative interface. For instructions on how to configure ACL, see [Users and rights overview](/docs/pbc/all/user-management/{{site.version}}/base-shop/user-and-rights-overview.html).
 
 ### Testing
@@ -101,7 +101,7 @@ Make sure you've addressed all the items from the following checklists.
 - We highly recommend you to set up an Application Performance Monitoring (APM). The APM tools help you identify performance bottlenecks in your application. You can request NewRelic APM from Spryker (subject to additional fees).
 - To watch the system's performance and configure alerting mechanisms, establish a robust post-launch monitoring plan. To ensure effective investigation in case of security incidents, we recommend configuring logs to gather in a centralized SIEM system.
 - Verify that your deploy file is set up correctly and aligns with your project needs. Verify that your project works and operates the production endpoints. You can set both testing and production endpoints in your deploy file. Your developers need to mock a "live" operation of the project with its production endpoints by adjusting their local host entries.
-- Deploy the production environment regularly. This lets you detect potential issues early enough to fix them before going live. For instructions, see [Deploying in a production environment](/docs/ca/dev/deploy-in-a-production-environment.html). Make sure to test all [recipes](/docs/dg/dev/sdks/the-docker-sdk/installation-recipes-of-deployment-pipelines.html#staging-and-production-environment-recipes). 
+- Deploy the production environment regularly. This lets you detect potential issues early enough to fix them before going live. For instructions, see [Deploying in a production environment](/docs/ca/dev/deploy-in-a-production-environment.html). Make sure to test all [recipes](/docs/dg/dev/sdks/the-docker-sdk/installation-recipes-of-deployment-pipelines.html#staging-and-production-environment-recipes).
 - Make sure the DNS names and strategy for your shop are clear. Do the following:
     - You know how users are going to access your shop. Verify that you control access to the DNS to be able to manage DNS. For example, you want to use `spryker.com` as the domain for your shop, but you want a user to access the Storefront by the `www.spryker.com` subdomain. For details on how to set up DNS for your application, see [Set up DNS](/docs/ca/dev/set-up-dns.html).
     - Optional: Delegate DNS. To find out how to delegate a DNS name, see [Setting up a custom SSL certificate](/docs/ca/dev/setting-up-a-custom-ssl-certificate.html).
diff --git a/docs/dg/dev/updating-spryker/installing-features-and-updating-modules.md b/docs/dg/dev/updating-spryker/installing-features-and-updating-modules.md
index 57dfa995303..7c3d526aac2 100644
--- a/docs/dg/dev/updating-spryker/installing-features-and-updating-modules.md
+++ b/docs/dg/dev/updating-spryker/installing-features-and-updating-modules.md
@@ -59,7 +59,7 @@ Sometimes, you may want to install a feature of a version higher than that of yo
 
 A new feature may require a higher major version of a specific module. In this case, do a [single module update](#update-to-a-major-versions-and-install-new-packages).
 
-You can learn about new Spryker features from the [release notes](/docs/about/all/releases/product-and-code-releases.html). Not to miss new release notes, we recommend [subscribing to our release newsletter](/docs/about/all/releases/releases.html).
+You can learn about new Spryker features from the [release notes](/docs/about/all/releases/product-and-code-releases.html). Not to miss new release notes, we recommend [subscribing to our release newsletter](/docs/about/all/releases/product-and-code-releases.html).
 
 ## Next steps
 
diff --git a/docs/dg/dev/updating-spryker/updating-spryker.md b/docs/dg/dev/updating-spryker/updating-spryker.md
index 51868a5e05b..a59038e8b7a 100644
--- a/docs/dg/dev/updating-spryker/updating-spryker.md
+++ b/docs/dg/dev/updating-spryker/updating-spryker.md
@@ -50,7 +50,7 @@ The more outdated your module versions become, the more effort will be needed to
 
 {% endinfo_block %}
 
-The most *reasonable strategy* of staying up to date is sticking to the Spryker release cycle and updating modules whenever there is a new release announcement. To get notified about releases,  [subscribe to the release notes](/docs/about/all/releases/releases.html). During the active development phase, it makes sense to do updates more often, for example, monthly.
+The most *reasonable strategy* of staying up to date is sticking to the Spryker release cycle and updating modules whenever there is a new release announcement. To get notified about releases,  [subscribe to the release notes](/docs/about/all/releases/product-and-code-releases.html). During the active development phase, it makes sense to do updates more often, for example, monthly.
 
 ## Spryker Safari materials
 

From ae6fe1a82e703c72919a140cc1f056553c0c365d Mon Sep 17 00:00:00 2001
From: Andrii Tserkovnyi <andrii.tserkovnyi@spryker.com>
Date: Tue, 19 Mar 2024 15:48:41 +0200
Subject: [PATCH 19/26] links

---
 _data/sidebars/about_all_sidebar.yml          | 20 +++++++++----------
 .../contributing-to-documentation.md          |  2 +-
 _includes/footer.html                         |  2 +-
 _scripts/sidebar_checker/sidebar_checker.sh   |  2 +-
 .../add-global-sections-to-the-docs.md        |  6 +++---
 .../add-and-edit-diagrams-in-the-docs.md      |  2 +-
 .../contribute-to-the-docs.md                 | 10 +++++-----
 .../edit-the-docs-locally.md                  |  2 +-
 .../edit-the-docs-using-a-web-browser.md      | 10 +++++-----
 .../report-docs-issues.md                     |  6 +++---
 .../review-pull-requests.md                   |  8 ++++----
 .../install-recommended-vs-code-extensions.md |  8 ++++----
 .../about-the-docs/run-the-docs-locally.md    |  6 +++---
 ...eral-rules-and-guidance-for-adding-docs.md | 10 +++++-----
 .../style-guide/markdown-syntax.md            |  6 +++---
 docs/about/all/docs-updates.md                |  6 +++---
 docs/about/all/support/understanding-slas.md  |  2 +-
 17 files changed, 54 insertions(+), 54 deletions(-)

diff --git a/_data/sidebars/about_all_sidebar.yml b/_data/sidebars/about_all_sidebar.yml
index a8e818339c4..eddb5389d67 100644
--- a/_data/sidebars/about_all_sidebar.yml
+++ b/_data/sidebars/about_all_sidebar.yml
@@ -102,29 +102,29 @@ entries:
       - title: General rules and guidance for adding new documents
         url: /docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.html
       - title: Markdown syntax
-        url: /docs/about/all/about-the-docs/contribute-to-the-docs/markdown-syntax.html
+        url: /docs/about/all/about-the-docs/style-guide/markdown-syntax.html
       - title: Spryker documentation style guide
-        url: /docs/about/all/about-the-docs/contribute-to-the-docs/spryker-documentation-style-guide/spryker-documentation-style-guide.html
+        url: /docs/about/all/about-the-docs/style-guide/spryker-docs-style-guide.html
         nested:
           - title: Examples
-            url: /docs/about/all/about-the-docs/contribute-to-the-docs/spryker-documentation-style-guide/examples.html
+            url: /docs/about/all/about-the-docs/contribute-to-the-docs/style-guide/examples.html
           - title: Spelling
-            url: /docs/about/all/about-the-docs/contribute-to-the-docs/spryker-documentation-style-guide/spelling.html
+            url: /docs/about/all/about-the-docs/contribute-to-the-docs/style-guide/spelling.html
           - title: Word list
-            url: /docs/about/all/about-the-docs/contribute-to-the-docs/spryker-documentation-style-guide/word-list.html
+            url: /docs/about/all/about-the-docs/contribute-to-the-docs/style-guide/word-list.html
 
       - title: Add and edit diagrams
-        url: /docs/about/all/about-the-docs/contribute-to-the-docs/add-and-edit-diagrams-in-the-documentation.html
+        url: /docs/about/all/about-the-docs/contribute-to-the-docs/add-and-edit-diagrams-in-the-docs.html
       - title: Install recommended VS Code extensions
-        url: /docs/about/all/about-the-docs/contribute-to-the-docs/install-recommended-vs-code-extensions.html
+        url: /docs/about/all/about-the-docs/install-recommended-vs-code-extensions.html
       - title: Report documentation issues
-        url: /docs/about/all/about-the-docs/contribute-to-the-docs/report-documentation-issues.html
+        url: /docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html
       - title: Build the documentation site
-        url: /docs/about/all/about-the-docs/contribute-to-the-docs/build-the-documentation-site.html
+        url: /docs/about/all/about-the-docs/run-the-docs-locally.html
       - title: Review pull requests
         url: /docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html
       - title: Add product sections to the documentation
-        url: /docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-documentation.html
+        url: /docs/about/all/about-the-docs/add-global-sections-to-the-docs.html
 
 
 
diff --git a/_drafts/drafts-dev/contributing-to-documentation.md b/_drafts/drafts-dev/contributing-to-documentation.md
index 8f44c86e9ed..c837648877a 100644
--- a/_drafts/drafts-dev/contributing-to-documentation.md
+++ b/_drafts/drafts-dev/contributing-to-documentation.md
@@ -13,7 +13,7 @@ To report issues and fix documentation, you need a [GitHub account](https://gith
 
 {% endinfo_block %}
 
-We use [Markdown](https://guides.github.com/features/mastering-markdown/) to write documentation and [Jekyll](https://jekyllrb.com/) to build the documentation site. You do not necessarily need to build the documentation site locally on your machine to propose your changes, but if you want to, follow the instructions in [Build documentation site](/docs/about/all/about-the-docs/contribute-to-the-docs/build-the-documentation-site.html).
+We use [Markdown](https://guides.github.com/features/mastering-markdown/) to write documentation and [Jekyll](https://jekyllrb.com/) to build the documentation site. You do not necessarily need to build the documentation site locally on your machine to propose your changes, but if you want to, follow the instructions in [Build documentation site](/docs/about/all/about-the-docs/run-the-docs-locally.html).
 
 ## Next steps
 Build the documentation site locally
diff --git a/_includes/footer.html b/_includes/footer.html
index 7b941743e4d..21444c4f100 100644
--- a/_includes/footer.html
+++ b/_includes/footer.html
@@ -11,7 +11,7 @@
                             <li><a target="_blank" rel="noopener" href="https://docs.spryker.com/docs/scos/user/intro-to-spryker/releases/release-notes/release-notes.html">Release Notes</a></li>
                             <li><a target="_blank" rel="noopener" href="https://spryker.force.com/support/s/">Support</a></li>
                             <li><a target="_blank" rel="noopener" href="https://spryker.com/en/events/">Events</a></li>
-                            <li><a target="_blank" rel="noopener" href="https://safari.spryker.com">Spryker Academy</a></li>
+                            <li><a target="_blank" rel="noopener" href="https://safari.spryker.com">Spryker Safari</a></li>
                         </ul>
                     </nav>
                 </div>
diff --git a/_scripts/sidebar_checker/sidebar_checker.sh b/_scripts/sidebar_checker/sidebar_checker.sh
index 07e956593b4..361d91275b8 100644
--- a/_scripts/sidebar_checker/sidebar_checker.sh
+++ b/_scripts/sidebar_checker/sidebar_checker.sh
@@ -7,7 +7,7 @@ FOLDERS=("docs/ca/dev" "docs/pbc/all" "docs/about/all" "docs/ca/devscu" "docs/dg
 SIDEBARS=("_data/sidebars/ca_dev_sidebar.yml" "_data/sidebars/ca_devscu_sidebar.yml" "_data/sidebars/pbc_all_sidebar.yml" "_data/sidebars/dg_dev_sidebar.yml" "_data/sidebars/about_all_sidebar.yml")
 
 # Define sidebar titles
-TITLES=("ACP User" "Cloud Dev" "PBC All" "SCOS Dev" "SCOS User" "SCU Dev" "SDK Dev")
+TITLES=("CA Dev" "CA Devscu" "PBC All" "DG Dev" "About All")
 
 # Define output file path
 OUTPUT_FILE="_scripts/sidebar_checker/missing-documents.yml"
diff --git a/docs/about/all/about-the-docs/add-global-sections-to-the-docs.md b/docs/about/all/about-the-docs/add-global-sections-to-the-docs.md
index bf00a8b0353..c6ba6342414 100644
--- a/docs/about/all/about-the-docs/add-global-sections-to-the-docs.md
+++ b/docs/about/all/about-the-docs/add-global-sections-to-the-docs.md
@@ -11,17 +11,17 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/build-the-documentation-site.html
+    link: docs/about/all/about-the-docs/run-the-docs-locally.html
   - title: Edit documentation via pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
   - title: Report documentation issues
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/report-documentation-issues.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html
   - title: Review pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html
   - title: Style, syntax, formatting, and general rules
     link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/markdown-syntax.html
+    link: docs/about/all/about-the-docs/style-guide/markdown-syntax.html
 ---
 
 This document describes how to add global sections to the documentation, like the existing Development or Cloud administration sections.
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/add-and-edit-diagrams-in-the-docs.md b/docs/about/all/about-the-docs/contribute-to-the-docs/add-and-edit-diagrams-in-the-docs.md
index 30af46a810e..239cdc8b209 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/add-and-edit-diagrams-in-the-docs.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/add-and-edit-diagrams-in-the-docs.md
@@ -8,7 +8,7 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/build-the-documentation-site.html
+    link: docs/about/all/about-the-docs/run-the-docs-locally.html
   - title: Edit documentation via pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
 ---
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.md b/docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.md
index bede7bd3ece..55e545bda41 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.md
@@ -9,24 +9,24 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/build-the-documentation-site.html
+    link: docs/about/all/about-the-docs/run-the-docs-locally.html
   - title: Add product sections to the documentation
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-documentation.html
+    link: docs/about/all/about-the-docs/add-global-sections-to-the-docs.html
   - title: Edit documentation via pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
   - title: Report documentation issues
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/report-documentation-issues.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html
   - title: Review pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html
   - title: Style, syntax, formatting, and general rules
     link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/markdown-syntax.html
+    link: docs/about/all/about-the-docs/style-guide/markdown-syntax.html
 ---
 
 We at Spryker aim to constantly improve the content we provide our customers and partners with. You can get involved in improving the Spryker documentation by:
 
-* [Reporting issues via GitHub](/docs/about/all/about-the-docs/contribute-to-the-docs/report-documentation-issues.html).
+* [Reporting issues via GitHub](/docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html).
 * [Editing documentation by creating pull requests on GitHub](/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html).
 * [Reviewing pull requests](/docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html).
 
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-locally.md b/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-locally.md
index a7e0b088059..3370325183c 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-locally.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-locally.md
@@ -61,7 +61,7 @@ At this point, you are most likely to know which document you want to edit. To f
 
 1. Open the document you want to edit in an editor.
 2. Add the needed changes.
-    You'd help us a lot by following [Markdown syntax](/docs/about/all/about-the-docs/contribute-to-the-docs/markdown-syntax.html) and [general rules](/docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html), but it's completely optional. We are grateful for your contribution in any form.
+    You'd help us a lot by following [Markdown syntax](/docs/about/all/about-the-docs/style-guide/markdown-syntax.html) and [general rules](/docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html), but it's completely optional. We are grateful for your contribution in any form.
 3. Save the edited document.
 4. In GitHub Desktop, double-check your changes in the **Changes** tab.
 5. Below the list of edited files, enter the name and description of your changes. The name of your fist commit will be used as the pull request's name.
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.md b/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.md
index 574e19ec2d9..6d9e80649d3 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.md
@@ -11,24 +11,24 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/build-the-documentation-site.html
+    link: docs/about/all/about-the-docs/run-the-docs-locally.html
   - title: Addi product sections to the documentation
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-documentation.html
+    link: docs/about/all/about-the-docs/add-global-sections-to-the-docs.html
   - title: Report documentation issues
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/report-documentation-issues.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html
   - title: Review pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html
   - title: Style, syntax, formatting, and general rules
     link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/markdown-syntax.html
+    link: docs/about/all/about-the-docs/style-guide/markdown-syntax.html
 ---
 
 The Spryker documentation is hosted on GitHub, in the [spryker-docs](https://github.com/spryker/spryker-docs) repository. Therefore, to contribute to the Spryker documents, you have to use GitHub. For more information about what GitHub is, see [About Git](https://docs.github.com/en/get-started/using-git/about-git).
 
 {% info_block infoBox "Info" %}
 
-We write the Spryker documentation using Markdown. If you don’t know Markdown yet, check the [GitHub Markdown Guide](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax). For the documentation-specific Markdown elements and HTML syntax used where Markdown is not enough, see [Markdown syntax](/docs/about/all/about-the-docs/contribute-to-the-docs/markdown-syntax.html).
+We write the Spryker documentation using Markdown. If you don’t know Markdown yet, check the [GitHub Markdown Guide](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax). For the documentation-specific Markdown elements and HTML syntax used where Markdown is not enough, see [Markdown syntax](/docs/about/all/about-the-docs/style-guide/markdown-syntax.html).
 
 {% endinfo_block %}
 
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.md b/docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.md
index 470476e16e3..71d0a5db12d 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.md
@@ -9,9 +9,9 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/build-the-documentation-site.html
+    link: docs/about/all/about-the-docs/run-the-docs-locally.html
   - title: Add product sections to the documentation
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-documentation.html
+    link: docs/about/all/about-the-docs/add-global-sections-to-the-docs.html
   - title: Edit documentation via pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
   - title: Review pull requests
@@ -19,7 +19,7 @@ related:
   - title: Style, syntax, formatting, and general rules
     link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/markdown-syntax.html
+    link: docs/about/all/about-the-docs/style-guide/markdown-syntax.html
 ---
 
 To report an issue with a Spryker document, do the following:
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.md b/docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.md
index 5c69ab48e92..f4349b41183 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.md
@@ -9,17 +9,17 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/build-the-documentation-site.html
+    link: docs/about/all/about-the-docs/run-the-docs-locally.html
   - title: Add product sections to the documentation
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-documentation.html
+    link: docs/about/all/about-the-docs/add-global-sections-to-the-docs.html
   - title: Edit documentation via pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
   - title: Report documentation issues
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/report-documentation-issues.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html
   - title: Style, syntax, formatting, and general rules
     link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/markdown-syntax.html
+    link: docs/about/all/about-the-docs/style-guide/markdown-syntax.html
 ---
 
 When someone requests your review of a pull request, you get an email about the request. <!--Also, a message with the review request is displayed on the pull request page:IMAGE-->
diff --git a/docs/about/all/about-the-docs/install-recommended-vs-code-extensions.md b/docs/about/all/about-the-docs/install-recommended-vs-code-extensions.md
index 74687f47ee1..1b8f888b0b3 100644
--- a/docs/about/all/about-the-docs/install-recommended-vs-code-extensions.md
+++ b/docs/about/all/about-the-docs/install-recommended-vs-code-extensions.md
@@ -8,17 +8,17 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/build-the-documentation-site.html
+    link: docs/about/all/about-the-docs/run-the-docs-locally.html
   - title: Addi product sections to the documentation
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-documentation.html
+    link: docs/about/all/about-the-docs/add-global-sections-to-the-docs.html
   - title: Report documentation issues
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/report-documentation-issues.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html
   - title: Review pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html
   - title: Style, syntax, formatting, and general rules
     link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/markdown-syntax.html
+    link: docs/about/all/about-the-docs/style-guide/markdown-syntax.html
 ---
 
 We recommend the following VS Code extensions for writing and reviewing documents:
diff --git a/docs/about/all/about-the-docs/run-the-docs-locally.md b/docs/about/all/about-the-docs/run-the-docs-locally.md
index 3ce2019a6c5..143cb6c5c80 100644
--- a/docs/about/all/about-the-docs/run-the-docs-locally.md
+++ b/docs/about/all/about-the-docs/run-the-docs-locally.md
@@ -9,17 +9,17 @@ redirect_from:
 
 related:
   - title: Add product sections to the documentation
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-documentation.html
+    link: docs/about/all/about-the-docs/add-global-sections-to-the-docs.html
   - title: Edit documentation via pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
   - title: Report documentation issues
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/report-documentation-issues.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html
   - title: Review pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html
   - title: Style, syntax, formatting, and general rules
     link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/markdown-syntax.html
+    link: docs/about/all/about-the-docs/style-guide/markdown-syntax.html
 ---
 
 We use [Jekyll](https://jekyllrb.com/) to build the Spryker documentation site. To build it locally, you need to:
diff --git a/docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.md b/docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.md
index 184548e2cd3..3c0c2b113f1 100644
--- a/docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.md
+++ b/docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.md
@@ -10,17 +10,17 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/build-the-documentation-site.html
+    link: docs/about/all/about-the-docs/run-the-docs-locally.html
   - title: Add product sections to the documentation
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-documentation.html
+    link: docs/about/all/about-the-docs/add-global-sections-to-the-docs.html
   - title: Edit documentation via pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
   - title: Report documentation issues
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/report-documentation-issues.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html
   - title: Review pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html
   - title: Markdown syntax
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/markdown-syntax.html
+    link: docs/about/all/about-the-docs/style-guide/markdown-syntax.html
 ---
 
 This document describes the directory structure, templates, front matter, and versioning of Spryker documentation.
@@ -33,7 +33,7 @@ The main directory for holding all the documents is [docs](https://github.com/sp
 
 ## Creating documents and categories
 
-We use [Markdown (.md)](https://en.wikipedia.org/wiki/Markdown) to write documents. All documents reside in the [docs](https://github.com/spryker/spryker-docs/tree/master/docs) directory. For details about how this directory is organized, see [Directory structure](#directory-structure). You can use any text editor for creating the files in Markdown, like [VSCode](https://code.visualstudio.com). For information about specific Markdown syntax for documentation, see [Markdown syntax](/docs/about/all/about-the-docs/contribute-to-the-docs/markdown-syntax.html).
+We use [Markdown (.md)](https://en.wikipedia.org/wiki/Markdown) to write documents. All documents reside in the [docs](https://github.com/spryker/spryker-docs/tree/master/docs) directory. For details about how this directory is organized, see [Directory structure](#directory-structure). You can use any text editor for creating the files in Markdown, like [VSCode](https://code.visualstudio.com). For information about specific Markdown syntax for documentation, see [Markdown syntax](/docs/about/all/about-the-docs/style-guide/markdown-syntax.html).
 
 You can create new pages in any documentation category or sub-category under the *realm* directories (`user`, `dev`). You can also create directories for new categories under the *realm* directories.
 
diff --git a/docs/about/all/about-the-docs/style-guide/markdown-syntax.md b/docs/about/all/about-the-docs/style-guide/markdown-syntax.md
index 84d20627569..01047077bdc 100644
--- a/docs/about/all/about-the-docs/style-guide/markdown-syntax.md
+++ b/docs/about/all/about-the-docs/style-guide/markdown-syntax.md
@@ -9,13 +9,13 @@ redirect_from:
 
 related:
   - title: Build the documentation site
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/build-the-documentation-site.html
+    link: docs/about/all/about-the-docs/run-the-docs-locally.html
   - title: Adding product sections to the documentation
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-documentation.html
+    link: docs/about/all/about-the-docs/add-global-sections-to-the-docs.html
   - title: Edit documentation via pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
   - title: Report documentation issues
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/report-documentation-issues.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html
   - title: Review pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html
   - title: Style, syntax, formatting, and general rules
diff --git a/docs/about/all/docs-updates.md b/docs/about/all/docs-updates.md
index 4fec02aadde..2c80b5a43f2 100644
--- a/docs/about/all/docs-updates.md
+++ b/docs/about/all/docs-updates.md
@@ -460,9 +460,9 @@ In June 2023, we have added and updated the following pages:
     - [File details - shipment_type_store.csv](/docs/pbc/all/carrier-management/202311.0/base-shop/import-and-export-data/import-file-details-shipment-type-store.csv.html).
     - [File details - shipment_type.csv](/docs/pbc/all/carrier-management/202311.0/base-shop/import-and-export-data/import-file-details-shipment-type.csv.html).
 - [Migration guide - Upgrade Node.js to v18 and npm to v9](/docs/dg/dev/upgrade-and-migrate/upgrade-nodejs-to-v18-and-npm-to-v9.html).
-- [Spryker documentation style guide](/docs/about/all/about-the-docs/contribute-to-the-docs/spryker-documentation-style-guide/spryker-documentation-style-guide.html):
-    - [Examples](/docs/about/all/about-the-docs/contribute-to-the-docs/spryker-documentation-style-guide/examples.html).
-    - [Spelling](/docs/about/all/about-the-docs/contribute-to-the-docs/spryker-documentation-style-guide/spelling.html).
+- [Spryker documentation style guide](/docs/about/all/about-the-docs/style-guide/spryker-docs-style-guide.html):
+    - [Examples](/docs/about/all/about-the-docs/contribute-to-the-docs/style-guide/examples.html).
+    - [Spelling](/docs/about/all/about-the-docs/contribute-to-the-docs/style-guide/spelling.html).
 
 ## Updated pages
 - [Environments overview](/docs/ca/dev/environments-overview.html).
diff --git a/docs/about/all/support/understanding-slas.md b/docs/about/all/support/understanding-slas.md
index 5c2df2de301..c4d052030f2 100644
--- a/docs/about/all/support/understanding-slas.md
+++ b/docs/about/all/support/understanding-slas.md
@@ -52,7 +52,7 @@ Our Spryker Community on [CommerceQuest](https://commercequest.space/), a vibran
 
 Also, subscribe to our new newsletter (soon to come) and be sure to check out our Technical News Page (soon to come), for the latest important news.
 
-### Enroll in the Spryker Academy
+### Enroll in the Spryker Safari
 This is a general recommendation that not only can teach you and your team how to build great shops with Spryker Code, but we offer several courses for all kinds of Spryker stakeholders. Currently, we offer developer courses, business courses, and sales courses with other interesting courses currently being developed.
 
 ### Learn more about how we work

From f3e3596287064b6191d6034a4751c9b108e1b23b Mon Sep 17 00:00:00 2001
From: Andrii Tserkovnyi <andrii.tserkovnyi@spryker.com>
Date: Wed, 20 Mar 2024 10:53:20 +0200
Subject: [PATCH 20/26] sidebar

---
 _data/sidebars/about_all_sidebar.yml          | 38 +++++++++++--------
 ...quests.md => review-docs-pull-requests.md} |  0
 .../all/{ => about-the-docs}/docs-updates.md  |  0
 3 files changed, 23 insertions(+), 15 deletions(-)
 rename docs/about/all/about-the-docs/contribute-to-the-docs/{review-pull-requests.md => review-docs-pull-requests.md} (100%)
 rename docs/about/all/{ => about-the-docs}/docs-updates.md (100%)

diff --git a/_data/sidebars/about_all_sidebar.yml b/_data/sidebars/about_all_sidebar.yml
index eddb5389d67..6988035ca58 100644
--- a/_data/sidebars/about_all_sidebar.yml
+++ b/_data/sidebars/about_all_sidebar.yml
@@ -39,9 +39,6 @@ entries:
       - title: 2020.11 - Penetration test by Port Zero (executive summary)
         url: /docs/about/all/security-audit-reports/2020.11-penetration-test-by-port-zero-executive-summary.html
 
-    - title: Docs updates
-      url: /docs/about/all/docs-updates.html
-
     - title: Support
       url: /docs/about/all/support/getting-support.html
       nested:
@@ -92,13 +89,25 @@ entries:
       - title: Marketplace B2B Suite
         url: /docs/about/all/spryker-marketplace/marketplace-b2b-suite.html
 
-    - title: Contribute to the documentation
-      url: /docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.html
+    - title: About the docs
+      url: /docs/about/all/about-the-docs/about-spryker-docs.html
       nested:
-      - title: Edit the documentation via pull requests
-        url: /docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
-      - title: Edit the documentation locally
-        url: /docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-locally.html
+      - title: Docs updates
+        url: /docs/about/all/about-the-docs/docs-updates.html
+      - title: Contribute
+        url: /docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.html
+        nested:
+          - title: Edit the docs using a web browser
+            url: /docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
+          - title: Edit the docs locally
+            url: /docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-locally.html
+          - title: Add and edit diagrams
+            url: /docs/about/all/about-the-docs/contribute-to-the-docs/add-and-edit-diagrams-in-the-docs.html
+          - title: Report docs issues
+            url: /docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html
+          - title: Review pull requests
+            url: /docs/about/all/about-the-docs/contribute-to-the-docs/review-docs-pull-requests.html
+
       - title: General rules and guidance for adding new documents
         url: /docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.html
       - title: Markdown syntax
@@ -113,16 +122,15 @@ entries:
           - title: Word list
             url: /docs/about/all/about-the-docs/contribute-to-the-docs/style-guide/word-list.html
 
-      - title: Add and edit diagrams
-        url: /docs/about/all/about-the-docs/contribute-to-the-docs/add-and-edit-diagrams-in-the-docs.html
+url: /docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.html
+
+
       - title: Install recommended VS Code extensions
         url: /docs/about/all/about-the-docs/install-recommended-vs-code-extensions.html
-      - title: Report documentation issues
-        url: /docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html
+
       - title: Build the documentation site
         url: /docs/about/all/about-the-docs/run-the-docs-locally.html
-      - title: Review pull requests
-        url: /docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html
+
       - title: Add product sections to the documentation
         url: /docs/about/all/about-the-docs/add-global-sections-to-the-docs.html
 
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.md b/docs/about/all/about-the-docs/contribute-to-the-docs/review-docs-pull-requests.md
similarity index 100%
rename from docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.md
rename to docs/about/all/about-the-docs/contribute-to-the-docs/review-docs-pull-requests.md
diff --git a/docs/about/all/docs-updates.md b/docs/about/all/about-the-docs/docs-updates.md
similarity index 100%
rename from docs/about/all/docs-updates.md
rename to docs/about/all/about-the-docs/docs-updates.md

From 9a3a852bc6e517baf512ac166323d1a47664771a Mon Sep 17 00:00:00 2001
From: Andrii Tserkovnyi <andrii.tserkovnyi@spryker.com>
Date: Fri, 22 Mar 2024 12:34:01 +0200
Subject: [PATCH 21/26] sidebar

---
 _data/sidebars/about_all_sidebar.yml          | 39 ++++++++-----------
 .../add-global-sections-to-the-docs.md        |  0
 .../install-recommended-vs-code-extensions.md |  0
 3 files changed, 16 insertions(+), 23 deletions(-)
 rename docs/about/all/about-the-docs/{ => contribute-to-the-docs}/add-global-sections-to-the-docs.md (100%)
 rename docs/about/all/about-the-docs/{ => contribute-to-the-docs}/install-recommended-vs-code-extensions.md (100%)

diff --git a/_data/sidebars/about_all_sidebar.yml b/_data/sidebars/about_all_sidebar.yml
index 6988035ca58..8e9d122dacc 100644
--- a/_data/sidebars/about_all_sidebar.yml
+++ b/_data/sidebars/about_all_sidebar.yml
@@ -97,43 +97,36 @@ entries:
       - title: Contribute
         url: /docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.html
         nested:
-          - title: Edit the docs using a web browser
+          - title: Edit using a web browser
             url: /docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
-          - title: Edit the docs locally
+          - title: Edit locally
             url: /docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-locally.html
           - title: Add and edit diagrams
             url: /docs/about/all/about-the-docs/contribute-to-the-docs/add-and-edit-diagrams-in-the-docs.html
-          - title: Report docs issues
+          - title: Report issues
             url: /docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html
           - title: Review pull requests
             url: /docs/about/all/about-the-docs/contribute-to-the-docs/review-docs-pull-requests.html
+          - title: Add global sections
+            url: /docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-docs.html
+          - title: Install recommended VS Code extensions
+            url: /docs/about/all/about-the-docs/contribute-to-the-docs/install-recommended-vs-code-extensions.html
 
-      - title: General rules and guidance for adding new documents
-        url: /docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.html
-      - title: Markdown syntax
-        url: /docs/about/all/about-the-docs/style-guide/markdown-syntax.html
-      - title: Spryker documentation style guide
+      - title: Style guide
         url: /docs/about/all/about-the-docs/style-guide/spryker-docs-style-guide.html
         nested:
           - title: Examples
-            url: /docs/about/all/about-the-docs/contribute-to-the-docs/style-guide/examples.html
+            url: /docs/about/all/about-the-docs/style-guide/style-guide-examples.html
           - title: Spelling
-            url: /docs/about/all/about-the-docs/contribute-to-the-docs/style-guide/spelling.html
+            url: /docs/about/all/about-the-docs/style-guide/style-guide-spelling.html
           - title: Word list
-            url: /docs/about/all/about-the-docs/contribute-to-the-docs/style-guide/word-list.html
+            url: /docs/about/all/about-the-docs/style-guide/word-list.html
+          - title: General rules and guidance for adding docs
+            url: /docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.html
+          - title: Markdown syntax
+            url: /docs/about/all/about-the-docs/style-guide/markdown-syntax.html
 
-url: /docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.html
-
-
-      - title: Install recommended VS Code extensions
-        url: /docs/about/all/about-the-docs/install-recommended-vs-code-extensions.html
-
-      - title: Build the documentation site
+      - title: Run the docs locally
         url: /docs/about/all/about-the-docs/run-the-docs-locally.html
 
-      - title: Add product sections to the documentation
-        url: /docs/about/all/about-the-docs/add-global-sections-to-the-docs.html
-
-
-
 ...
diff --git a/docs/about/all/about-the-docs/add-global-sections-to-the-docs.md b/docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-docs.md
similarity index 100%
rename from docs/about/all/about-the-docs/add-global-sections-to-the-docs.md
rename to docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-docs.md
diff --git a/docs/about/all/about-the-docs/install-recommended-vs-code-extensions.md b/docs/about/all/about-the-docs/contribute-to-the-docs/install-recommended-vs-code-extensions.md
similarity index 100%
rename from docs/about/all/about-the-docs/install-recommended-vs-code-extensions.md
rename to docs/about/all/about-the-docs/contribute-to-the-docs/install-recommended-vs-code-extensions.md

From b7b201b2ef3b7d2ef1a68ead6c592222c08b9afb Mon Sep 17 00:00:00 2001
From: Andrii Tserkovnyi <andrii.tserkovnyi@spryker.com>
Date: Fri, 22 Mar 2024 16:03:17 +0200
Subject: [PATCH 22/26] links

---
 docs/about/all/about-the-docs/about-spryker-docs.md           | 2 +-
 .../contribute-to-the-docs/add-global-sections-to-the-docs.md | 2 +-
 .../contribute-to-the-docs/contribute-to-the-docs.md          | 4 ++--
 .../edit-the-docs-using-a-web-browser.md                      | 2 +-
 .../install-recommended-vs-code-extensions.md                 | 2 +-
 .../contribute-to-the-docs/report-docs-issues.md              | 2 +-
 docs/about/all/about-the-docs/run-the-docs-locally.md         | 2 +-
 .../style-guide/general-rules-and-guidance-for-adding-docs.md | 2 +-
 docs/about/all/about-the-docs/style-guide/markdown-syntax.md  | 2 +-
 9 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/docs/about/all/about-the-docs/about-spryker-docs.md b/docs/about/all/about-the-docs/about-spryker-docs.md
index 2bcbbf6eca1..f73f5179ef7 100644
--- a/docs/about/all/about-the-docs/about-spryker-docs.md
+++ b/docs/about/all/about-the-docs/about-spryker-docs.md
@@ -9,7 +9,7 @@ Spryker docs are your one-stop hub for all the information about Spryker Cloud C
 
 ## The source of truth
 
-When it comes to knowledge sharing, we rely on the docs as the main source of truth. Both external and internal users refer to the docs when developing projects, designing [Spryker Safari courses](https://safari.spryker.com/learn), creating new or customizing the existing functionality.
+When it comes to knowledge sharing, we rely on the docs as the main source of truth. Both external and internal users refer to the docs when developing projects, designing [Spryker Safari courses](https://safari.spryker.com/), creating new or customizing the existing functionality.
 
 ## Owned by the Spryker community
 
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-docs.md b/docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-docs.md
index c6ba6342414..00f0aa17bf2 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-docs.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-docs.md
@@ -17,7 +17,7 @@ related:
   - title: Report documentation issues
     link: docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html
   - title: Review pull requests
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/review-docs-pull-requests.html
   - title: Style, syntax, formatting, and general rules
     link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.md b/docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.md
index 55e545bda41..208c4e8dd4a 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.md
@@ -17,7 +17,7 @@ related:
   - title: Report documentation issues
     link: docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html
   - title: Review pull requests
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/review-docs-pull-requests.html
   - title: Style, syntax, formatting, and general rules
     link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
@@ -28,6 +28,6 @@ We at Spryker aim to constantly improve the content we provide our customers and
 
 * [Reporting issues via GitHub](/docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html).
 * [Editing documentation by creating pull requests on GitHub](/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html).
-* [Reviewing pull requests](/docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html).
+* [Reviewing pull requests](/docs/about/all/about-the-docs/contribute-to-the-docs/review-docs-pull-requests.html).
 
 Therefore, to contribute to the Spryker documentation, you must have a GitHub account. For information about how to create it, see [Signing up for a new GitHub account](https://docs.github.com/en/get-started/signing-up-for-github/signing-up-for-a-new-github-account) in the official GitHub documentation.
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.md b/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.md
index 6d9e80649d3..53e82e11f7c 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.md
@@ -17,7 +17,7 @@ related:
   - title: Report documentation issues
     link: docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html
   - title: Review pull requests
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/review-docs-pull-requests.html
   - title: Style, syntax, formatting, and general rules
     link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/install-recommended-vs-code-extensions.md b/docs/about/all/about-the-docs/contribute-to-the-docs/install-recommended-vs-code-extensions.md
index 1b8f888b0b3..9ab70988926 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/install-recommended-vs-code-extensions.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/install-recommended-vs-code-extensions.md
@@ -14,7 +14,7 @@ related:
   - title: Report documentation issues
     link: docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html
   - title: Review pull requests
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/review-docs-pull-requests.html
   - title: Style, syntax, formatting, and general rules
     link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.md b/docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.md
index 71d0a5db12d..404e04314b4 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.md
@@ -15,7 +15,7 @@ related:
   - title: Edit documentation via pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
   - title: Review pull requests
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/review-docs-pull-requests.html
   - title: Style, syntax, formatting, and general rules
     link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
diff --git a/docs/about/all/about-the-docs/run-the-docs-locally.md b/docs/about/all/about-the-docs/run-the-docs-locally.md
index 143cb6c5c80..7eb63c9a27b 100644
--- a/docs/about/all/about-the-docs/run-the-docs-locally.md
+++ b/docs/about/all/about-the-docs/run-the-docs-locally.md
@@ -15,7 +15,7 @@ related:
   - title: Report documentation issues
     link: docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html
   - title: Review pull requests
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/review-docs-pull-requests.html
   - title: Style, syntax, formatting, and general rules
     link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
diff --git a/docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.md b/docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.md
index 3c0c2b113f1..70ede876bf6 100644
--- a/docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.md
+++ b/docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.md
@@ -18,7 +18,7 @@ related:
   - title: Report documentation issues
     link: docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html
   - title: Review pull requests
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/review-docs-pull-requests.html
   - title: Markdown syntax
     link: docs/about/all/about-the-docs/style-guide/markdown-syntax.html
 ---
diff --git a/docs/about/all/about-the-docs/style-guide/markdown-syntax.md b/docs/about/all/about-the-docs/style-guide/markdown-syntax.md
index 01047077bdc..d49592cac1c 100644
--- a/docs/about/all/about-the-docs/style-guide/markdown-syntax.md
+++ b/docs/about/all/about-the-docs/style-guide/markdown-syntax.md
@@ -17,7 +17,7 @@ related:
   - title: Report documentation issues
     link: docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html
   - title: Review pull requests
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/review-pull-requests.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/review-docs-pull-requests.html
   - title: Style, syntax, formatting, and general rules
     link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
 ---

From 774cb6700b9958c7adc9b8481b68034f2c76db85 Mon Sep 17 00:00:00 2001
From: Andrii Tserkovnyi <andrii.tserkovnyi@spryker.com>
Date: Mon, 25 Mar 2024 11:10:38 +0200
Subject: [PATCH 23/26] links

---
 _scripts/sidebar_checker/sidebar_checker.sh        |  6 +++---
 .../add-global-sections-to-the-docs.md             |  2 --
 .../contribute-to-the-docs.md                      |  4 +---
 .../edit-the-docs-locally.md                       |  2 +-
 .../edit-the-docs-using-a-web-browser.md           | 14 +-------------
 .../install-recommended-vs-code-extensions.md      |  4 +---
 .../contribute-to-the-docs/report-docs-issues.md   |  4 +---
 .../review-docs-pull-requests.md                   |  4 +---
 docs/about/all/about-the-docs/docs-updates.md      |  8 ++++----
 .../all/about-the-docs/run-the-docs-locally.md     |  4 +---
 .../general-rules-and-guidance-for-adding-docs.md  |  2 +-
 .../about-the-docs/style-guide/markdown-syntax.md  |  4 +---
 docs/about/all/releases/release-notes-202211.0.md  |  2 +-
 docs/about/all/support/understanding-slas.md       |  2 +-
 14 files changed, 18 insertions(+), 44 deletions(-)

diff --git a/_scripts/sidebar_checker/sidebar_checker.sh b/_scripts/sidebar_checker/sidebar_checker.sh
index 361d91275b8..19d1b71b78e 100644
--- a/_scripts/sidebar_checker/sidebar_checker.sh
+++ b/_scripts/sidebar_checker/sidebar_checker.sh
@@ -1,13 +1,13 @@
 #!/bin/bash
 
 # Define doc folder paths
-FOLDERS=("docs/ca/dev" "docs/pbc/all" "docs/about/all" "docs/ca/devscu" "docs/dg/dev")
+FOLDERS=("docs/about/all" "docs/ca/dev" "docs/ca/devscu" "docs/dg/dev" "docs/pbc/all")
 
 # Define sidebar file paths
-SIDEBARS=("_data/sidebars/ca_dev_sidebar.yml" "_data/sidebars/ca_devscu_sidebar.yml" "_data/sidebars/pbc_all_sidebar.yml" "_data/sidebars/dg_dev_sidebar.yml" "_data/sidebars/about_all_sidebar.yml")
+SIDEBARS=("_data/sidebars/about_all_sidebar.yml" "_data/sidebars/ca_dev_sidebar.yml" "_data/sidebars/ca_devscu_sidebar.yml" "_data/sidebars/dg_dev_sidebar.yml" "_data/sidebars/pbc_all_sidebar.yml")
 
 # Define sidebar titles
-TITLES=("CA Dev" "CA Devscu" "PBC All" "DG Dev" "About All")
+TITLES=("About All" "CA Dev" "CA Devscu" "DG Dev" "PBC All")
 
 # Define output file path
 OUTPUT_FILE="_scripts/sidebar_checker/missing-documents.yml"
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-docs.md b/docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-docs.md
index 00f0aa17bf2..f2860914a60 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-docs.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-docs.md
@@ -18,8 +18,6 @@ related:
     link: docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html
   - title: Review pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/review-docs-pull-requests.html
-  - title: Style, syntax, formatting, and general rules
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
     link: docs/about/all/about-the-docs/style-guide/markdown-syntax.html
 ---
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.md b/docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.md
index 208c4e8dd4a..a501084f8a7 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/contribute-to-the-docs.md
@@ -11,15 +11,13 @@ related:
   - title: Build the documentation site
     link: docs/about/all/about-the-docs/run-the-docs-locally.html
   - title: Add product sections to the documentation
-    link: docs/about/all/about-the-docs/add-global-sections-to-the-docs.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-docs.html
   - title: Edit documentation via pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
   - title: Report documentation issues
     link: docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html
   - title: Review pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/review-docs-pull-requests.html
-  - title: Style, syntax, formatting, and general rules
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
     link: docs/about/all/about-the-docs/style-guide/markdown-syntax.html
 ---
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-locally.md b/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-locally.md
index 3370325183c..3eaab586948 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-locally.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-locally.md
@@ -61,7 +61,7 @@ At this point, you are most likely to know which document you want to edit. To f
 
 1. Open the document you want to edit in an editor.
 2. Add the needed changes.
-    You'd help us a lot by following [Markdown syntax](/docs/about/all/about-the-docs/style-guide/markdown-syntax.html) and [general rules](/docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html), but it's completely optional. We are grateful for your contribution in any form.
+    You'd help us a lot by following [Markdown syntax](/docs/about/all/about-the-docs/style-guide/markdown-syntax.html) and [general rules](/docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.html), but it's completely optional. We are grateful for your contribution in any form.
 3. Save the edited document.
 4. In GitHub Desktop, double-check your changes in the **Changes** tab.
 5. Below the list of edited files, enter the name and description of your changes. The name of your fist commit will be used as the pull request's name.
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.md b/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.md
index 53e82e11f7c..40e0c51482a 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.md
@@ -13,13 +13,11 @@ related:
   - title: Build the documentation site
     link: docs/about/all/about-the-docs/run-the-docs-locally.html
   - title: Addi product sections to the documentation
-    link: docs/about/all/about-the-docs/add-global-sections-to-the-docs.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-docs.html
   - title: Report documentation issues
     link: docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html
   - title: Review pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/review-docs-pull-requests.html
-  - title: Style, syntax, formatting, and general rules
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
     link: docs/about/all/about-the-docs/style-guide/markdown-syntax.html
 ---
@@ -34,16 +32,6 @@ We write the Spryker documentation using Markdown. If you don’t know Markdown
 
 This instruction explains how to contribute to the Spryker documentation by creating [pull requests](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) on GitHub.
 
-{% info_block infoBox "Info" %}
-
-For information about the structure of the Spryker documentation, as well as style and formatting rules, see [Style, syntax, formatting, and general rules](/docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html).
-
-
-Note that Spryker documentation is written in US English.
-
-
-{% endinfo_block %}
-
 ## Prerequisites
 
 To start contributing to the Spryker documentation, make sure you have a GitHub account.
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/install-recommended-vs-code-extensions.md b/docs/about/all/about-the-docs/contribute-to-the-docs/install-recommended-vs-code-extensions.md
index 9ab70988926..d7ac4f6fb8e 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/install-recommended-vs-code-extensions.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/install-recommended-vs-code-extensions.md
@@ -10,13 +10,11 @@ related:
   - title: Build the documentation site
     link: docs/about/all/about-the-docs/run-the-docs-locally.html
   - title: Addi product sections to the documentation
-    link: docs/about/all/about-the-docs/add-global-sections-to-the-docs.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-docs.html
   - title: Report documentation issues
     link: docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html
   - title: Review pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/review-docs-pull-requests.html
-  - title: Style, syntax, formatting, and general rules
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
     link: docs/about/all/about-the-docs/style-guide/markdown-syntax.html
 ---
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.md b/docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.md
index 404e04314b4..c05c3a795f0 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.md
@@ -11,13 +11,11 @@ related:
   - title: Build the documentation site
     link: docs/about/all/about-the-docs/run-the-docs-locally.html
   - title: Add product sections to the documentation
-    link: docs/about/all/about-the-docs/add-global-sections-to-the-docs.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-docs.html
   - title: Edit documentation via pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
   - title: Review pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/review-docs-pull-requests.html
-  - title: Style, syntax, formatting, and general rules
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
     link: docs/about/all/about-the-docs/style-guide/markdown-syntax.html
 ---
diff --git a/docs/about/all/about-the-docs/contribute-to-the-docs/review-docs-pull-requests.md b/docs/about/all/about-the-docs/contribute-to-the-docs/review-docs-pull-requests.md
index f4349b41183..4f698e495ae 100644
--- a/docs/about/all/about-the-docs/contribute-to-the-docs/review-docs-pull-requests.md
+++ b/docs/about/all/about-the-docs/contribute-to-the-docs/review-docs-pull-requests.md
@@ -11,13 +11,11 @@ related:
   - title: Build the documentation site
     link: docs/about/all/about-the-docs/run-the-docs-locally.html
   - title: Add product sections to the documentation
-    link: docs/about/all/about-the-docs/add-global-sections-to-the-docs.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-docs.html
   - title: Edit documentation via pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
   - title: Report documentation issues
     link: docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html
-  - title: Style, syntax, formatting, and general rules
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
     link: docs/about/all/about-the-docs/style-guide/markdown-syntax.html
 ---
diff --git a/docs/about/all/about-the-docs/docs-updates.md b/docs/about/all/about-the-docs/docs-updates.md
index 2c80b5a43f2..fee7132c0b4 100644
--- a/docs/about/all/about-the-docs/docs-updates.md
+++ b/docs/about/all/about-the-docs/docs-updates.md
@@ -427,7 +427,7 @@ In July 2023, we have added and updated the following pages:
 - [Integrate Usercentrics](/docs/pbc/all/usercentrics/integrate-usercentrics.html): Find out how you can integrate Usercentrics in your Spryker shop.
 - [Usercentrics](/docs/pbc/all/usercentrics/usercentrics.html): [Usercentrics](https://usercentrics.com/) is the Consent Management Platform (CMP) that lets you obtain and manage the consent of your users to use cookies across your store.
 - [Adding variables in the parameter store](/docs/ca/dev/add-variables-in-the-parameter-store.html): Added reserved variable sub-section and removed deprecated text.
-- [Security Release Notes 202306.0](/docs/about/all/releases/release-notes-202306.0/security-release-notes-202306.0.html): Added missing security HTTP headers.
+- [Security Release Notes 202306.0](/docs/about/all/releases/security-release-notes-202306.0.html): Added missing security HTTP headers.
 - [Merchant Users Overview](/docs/pbc/all/merchant-management/202212.0/marketplace/marketplace-merchant-feature-overview/merchant-users-overview.html): Added information about the assignment of groups for the merchant user.
 - [Handle data with Publish and Synchronization](/docs/dg/dev/backend-development/data-manipulation/data-publishing/handle-data-with-publish-and-synchronization.html): Publish and Synchronization (P&S) lets you export data from Spryker backend (Zed) to external endpoints.
 - [Install the Spryker Core feature](/docs/pbc/all/miscellaneous/202307.0/install-and-upgrade/install-features/install-the-spryker-core-feature.html): Updated code sample.
@@ -450,7 +450,7 @@ For more details about these and other updates to the Spryker docs in July 2023,
 In June 2023, we have added and updated the following pages:
 
 ### New pages
-- [Security release notes 202306.0](/docs/about/all/releases/release-notes-202306.0/security-release-notes-202306.0.html).
+- [Security release notes 202306.0](/docs/about/all/releases/security-release-notes-202306.0.html).
 - [Oryx: Presets](/docs/dg/dev/frontend-development/202212.0/oryx/building-applications/oryx-presets.html): Learn how you can use presets to install predefined applications.
 - [Service Points feature integration guide](/docs/pbc/all/service-point-management/202311.0/unified-commerce/install-features/install-the-service-points-feature.html).
 - [Shipment + Service Points feature integration guide](/docs/pbc/all/carrier-management/202311.0/unified-commerce/install-features/install-the-shipment-service-points-feature.html).
@@ -461,7 +461,7 @@ In June 2023, we have added and updated the following pages:
     - [File details - shipment_type.csv](/docs/pbc/all/carrier-management/202311.0/base-shop/import-and-export-data/import-file-details-shipment-type.csv.html).
 - [Migration guide - Upgrade Node.js to v18 and npm to v9](/docs/dg/dev/upgrade-and-migrate/upgrade-nodejs-to-v18-and-npm-to-v9.html).
 - [Spryker documentation style guide](/docs/about/all/about-the-docs/style-guide/spryker-docs-style-guide.html):
-    - [Examples](/docs/about/all/about-the-docs/contribute-to-the-docs/style-guide/examples.html).
+    - [Examples](/docs/about/all/about-the-docs/contribute-to-the-docs/style-guide/style-guide-examples.html).
     - [Spelling](/docs/about/all/about-the-docs/contribute-to-the-docs/style-guide/spelling.html).
 
 ## Updated pages
@@ -491,7 +491,7 @@ In May 2023, we have added and updated the following pages:
 
 ### New pages
 
-- [Docs release notes](/docs/about/all/docs-updates.html)
+- [Docs release notes](/docs/about/all/about-the-docs/docs-updates.html)
 - Multistore documentation:
     - [Multistore setup options](/docs/ca/dev/multi-store-setups/multistore-setup-options.html): Learn about all the setup options you have for a multi-store environment.
     - [Checklist for a new store implementation](/docs/ca/dev/multi-store-setups/checklist-for-a-new-store-implementation.html): Overview of the high-level tasks and responsibilities of Spryker and Customer when setting up a new store.
diff --git a/docs/about/all/about-the-docs/run-the-docs-locally.md b/docs/about/all/about-the-docs/run-the-docs-locally.md
index 7eb63c9a27b..345e7e8927f 100644
--- a/docs/about/all/about-the-docs/run-the-docs-locally.md
+++ b/docs/about/all/about-the-docs/run-the-docs-locally.md
@@ -9,15 +9,13 @@ redirect_from:
 
 related:
   - title: Add product sections to the documentation
-    link: docs/about/all/about-the-docs/add-global-sections-to-the-docs.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-docs.html
   - title: Edit documentation via pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
   - title: Report documentation issues
     link: docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html
   - title: Review pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/review-docs-pull-requests.html
-  - title: Style, syntax, formatting, and general rules
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
   - title: Markdown syntax
     link: docs/about/all/about-the-docs/style-guide/markdown-syntax.html
 ---
diff --git a/docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.md b/docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.md
index 70ede876bf6..4d302b4d032 100644
--- a/docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.md
+++ b/docs/about/all/about-the-docs/style-guide/general-rules-and-guidance-for-adding-docs.md
@@ -12,7 +12,7 @@ related:
   - title: Build the documentation site
     link: docs/about/all/about-the-docs/run-the-docs-locally.html
   - title: Add product sections to the documentation
-    link: docs/about/all/about-the-docs/add-global-sections-to-the-docs.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-docs.html
   - title: Edit documentation via pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
   - title: Report documentation issues
diff --git a/docs/about/all/about-the-docs/style-guide/markdown-syntax.md b/docs/about/all/about-the-docs/style-guide/markdown-syntax.md
index d49592cac1c..1eb354f4dd8 100644
--- a/docs/about/all/about-the-docs/style-guide/markdown-syntax.md
+++ b/docs/about/all/about-the-docs/style-guide/markdown-syntax.md
@@ -11,15 +11,13 @@ related:
   - title: Build the documentation site
     link: docs/about/all/about-the-docs/run-the-docs-locally.html
   - title: Adding product sections to the documentation
-    link: docs/about/all/about-the-docs/add-global-sections-to-the-docs.html
+    link: docs/about/all/about-the-docs/contribute-to-the-docs/add-global-sections-to-the-docs.html
   - title: Edit documentation via pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/edit-the-docs-using-a-web-browser.html
   - title: Report documentation issues
     link: docs/about/all/about-the-docs/contribute-to-the-docs/report-docs-issues.html
   - title: Review pull requests
     link: docs/about/all/about-the-docs/contribute-to-the-docs/review-docs-pull-requests.html
-  - title: Style, syntax, formatting, and general rules
-    link: docs/about/all/about-the-docs/contribute-to-the-docs/style-formatting-general-rules.html
 ---
 
 We use Markdown to write the Spryker documentation. This document contains the Markdown syntax of the page elements used on the Spryker documentation website, specifically:
diff --git a/docs/about/all/releases/release-notes-202211.0.md b/docs/about/all/releases/release-notes-202211.0.md
index 0e31963052a..2af81029289 100644
--- a/docs/about/all/releases/release-notes-202211.0.md
+++ b/docs/about/all/releases/release-notes-202211.0.md
@@ -17,4 +17,4 @@ With 202211.0, Spryker released a new version of its Demo Shops requiring PHP 8.
 Backward compatibility remains unaffected. If your project followed our recommendations and requirements in the past twelve months, you will not experience any upgradability issues.
 
 **Documentation:**
-[How to migrate](/docs/about/all/whats-new/php8-as-a-minimum-version-for-all-spryker-projects.html#migration-steps)
+[How to migrate](/docs/dg/dev/upgrade-and-migrate/upgrade-to-php-81.html)
diff --git a/docs/about/all/support/understanding-slas.md b/docs/about/all/support/understanding-slas.md
index c4d052030f2..9c67aea1ce6 100644
--- a/docs/about/all/support/understanding-slas.md
+++ b/docs/about/all/support/understanding-slas.md
@@ -29,7 +29,7 @@ If you discover a problem with Spryker Software, please let us know immediately.
 Ensure that every case you open with us includes the information we need to work on it. To learn what info matters most, see [Getting the most out of Spryker Support](/docs/about/all/support/getting-the-most-out-of-spryker-support.html).
 
 ### Assess business impact realistically
-To make sure that we resolve the right cases first, we need to triage and prioritize. You can help us to do this better if you assess and specify the business impact of your problem appropriately. For a more detailed explanation of what business impact is and how priorities work have a look into this [article](/docs/about/all/support/support-ticket-statuses.html#how-are-bug-tickets-prioritized).
+To make sure that we resolve the right cases first, we need to triage and prioritize. You can help us to do this better if you assess and specify the business impact of your problem appropriately. For a more detailed explanation of what business impact is and how priorities work have a look into this [article](/docs/about/all/support/support-ticket-statuses.html#prioritizing-bug-tickets).
 
 ## What you can expect from us
 

From 7514a0adee0782ab9dcca6c4c5ff0fc7b0a35db1 Mon Sep 17 00:00:00 2001
From: Andrii Tserkovnyi <andrii.tserkovnyi@spryker.com>
Date: Mon, 25 Mar 2024 12:15:21 +0200
Subject: [PATCH 24/26] links

---
 _data/sidebars/about_all_sidebar.yml          |  13 +-
 _data/sidebars/dg_dev_sidebar.yml             |   6 +-
 ...nstall-the-inventory-management-feature.md |   1 -
 docs/about/all/about-the-docs/docs-updates.md |   4 +-
 ...api-resolve-search-engine-friendly-urls.md | 160 ------------------
 .../resolving-search-engine-friendly-urls.md  |  10 +-
 6 files changed, 25 insertions(+), 169 deletions(-)
 delete mode 100644 docs/dg/dev/glue-api/202212.0/old-glue-infrastructure/glue-api-resolve-search-engine-friendly-urls.md
 rename docs/dg/dev/glue-api/{202311.0 => 202212.0}/old-glue-infrastructure/resolving-search-engine-friendly-urls.md (95%)

diff --git a/_data/sidebars/about_all_sidebar.yml b/_data/sidebars/about_all_sidebar.yml
index 8e9d122dacc..2b28dfe968f 100644
--- a/_data/sidebars/about_all_sidebar.yml
+++ b/_data/sidebars/about_all_sidebar.yml
@@ -31,6 +31,8 @@ entries:
           url: /docs/about/all/releases/release-notes-202212.0/patch-release-notes-202212.0.html
         - title: Security release notes 202212.0
           url: /docs/about/all/releases/release-notes-202212.0/security-release-notes-202212.0.html
+      - title: Release notes 202211.0
+        url: /docs/about/all/releases/release-notes-202211.0.html
 
     - title: Security audit reports
       nested:
@@ -64,11 +66,20 @@ entries:
         url: /docs/about/all/support/understanding-slas.html
       - title: Escalations
         url: /docs/about/all/support/support-case-escalations.html
-      - title: Understanding Project and Core Level Fixes
+      - title: Prioritizing support cases
+        url: /docs/about/all/support/prioritzing-support-cases.html
+      - title: Understanding project and core level fixes
         url: /docs/about/all/support/project-level-and-core-level-fixes.html
 
     - title: Supported browsers
       url: /docs/about/all/supported-browsers.html
+    - title: Master Suite
+      url: /docs/about/all/master-suite.html
+    - title: B2C Suite
+      url: /docs/about/all/b2c-suite.html
+    - title: B2B Suite
+      url: /docs/about/all/b2b-suite.html
+
     - title: Spryker Marketplace
       url: /docs/about/all/spryker-marketplace/spryker-marketplace.html
       nested:
diff --git a/_data/sidebars/dg_dev_sidebar.yml b/_data/sidebars/dg_dev_sidebar.yml
index e727194d7cc..23206f2e3d2 100644
--- a/_data/sidebars/dg_dev_sidebar.yml
+++ b/_data/sidebars/dg_dev_sidebar.yml
@@ -1300,7 +1300,8 @@ entries:
         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: Prices filter and sorting doesn't work on Frontend
+        url: /docs/dg/dev/troubleshooting/troubleshooting-general-technical-issues/prices-filter-and-sorting-does-t-work-on-frontend.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
@@ -1408,6 +1409,7 @@ entries:
         url: /docs/dg/dev/glue-api/old-glue-infrastructure/glue-api-resolve-search-engine-friendly-urls.html
         include_versions:
         - "202212.0"
+        - "202307.0"
       - title: "Marketplace: Resolve search engine friendly URLs"
         url: /docs/dg/dev/glue-api/old-glue-infrastructure/marketplace-glue-api-resolve-search-engine-friendly-urls.html
       - title: Reference information - GlueApplication errors
@@ -1575,4 +1577,4 @@ entries:
   - title: Example modules
     url: /docs/dg/dev/example-modules.html
   - title: Supported versions of PHP
-    url: /docs/dg/dev/supported-versions-of-php.html    
+    url: /docs/dg/dev/supported-versions-of-php.html
diff --git a/_includes/pbc/all/install-features/202311.0/install-the-inventory-management-feature.md b/_includes/pbc/all/install-features/202311.0/install-the-inventory-management-feature.md
index 6149f731c48..4e46f0f0330 100644
--- a/_includes/pbc/all/install-features/202311.0/install-the-inventory-management-feature.md
+++ b/_includes/pbc/all/install-features/202311.0/install-the-inventory-management-feature.md
@@ -810,4 +810,3 @@ class ProductDependencyProvider extends SprykerProductDependencyProvider
 |--------------------------|----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | Inventory Management API |                                  | [Install the Inventory Management Glue API](/docs/pbc/all/warehouse-management-system/{{page.version}}/base-shop/install-and-upgrade/install-features/install-the-inventory-management-glue-api.html)                |
 | Alternative Products     |                                  | [Alternative Products + Inventory Management feature integration - ongoing](/docs/scos/dev/feature-integration-guides/{{page.version}}/alternative-products-inventory-management-feature-integration.html) |
-| Order Management         |                                  | [Order Management + Inventory Management feature integration](/docs/scos/dev/feature-integration-guides/{{page.version}}/order-management-inventory-management-feature-integration.html)               |
diff --git a/docs/about/all/about-the-docs/docs-updates.md b/docs/about/all/about-the-docs/docs-updates.md
index fee7132c0b4..9a37619f082 100644
--- a/docs/about/all/about-the-docs/docs-updates.md
+++ b/docs/about/all/about-the-docs/docs-updates.md
@@ -461,8 +461,8 @@ In June 2023, we have added and updated the following pages:
     - [File details - shipment_type.csv](/docs/pbc/all/carrier-management/202311.0/base-shop/import-and-export-data/import-file-details-shipment-type.csv.html).
 - [Migration guide - Upgrade Node.js to v18 and npm to v9](/docs/dg/dev/upgrade-and-migrate/upgrade-nodejs-to-v18-and-npm-to-v9.html).
 - [Spryker documentation style guide](/docs/about/all/about-the-docs/style-guide/spryker-docs-style-guide.html):
-    - [Examples](/docs/about/all/about-the-docs/contribute-to-the-docs/style-guide/style-guide-examples.html).
-    - [Spelling](/docs/about/all/about-the-docs/contribute-to-the-docs/style-guide/spelling.html).
+    - [Examples](/docs/about/all/about-the-docs/style-guide/style-guide-examples.html).
+    - [Spelling](/docs/about/all/about-the-docs/style-guide/style-guide-spelling.html).
 
 ## Updated pages
 - [Environments overview](/docs/ca/dev/environments-overview.html).
diff --git a/docs/dg/dev/glue-api/202212.0/old-glue-infrastructure/glue-api-resolve-search-engine-friendly-urls.md b/docs/dg/dev/glue-api/202212.0/old-glue-infrastructure/glue-api-resolve-search-engine-friendly-urls.md
deleted file mode 100644
index 77ca8bf0af6..00000000000
--- a/docs/dg/dev/glue-api/202212.0/old-glue-infrastructure/glue-api-resolve-search-engine-friendly-urls.md
+++ /dev/null
@@ -1,160 +0,0 @@
----
-title: "Glue API: Resolve search engine friendly URLs"
-description: Learn how to resolve search engine friendly URLs via Glue API.
-last_updated: Jun 22, 2021
-template: glue-api-storefront-guide-template
-originalLink: https://documentation.spryker.com/2021080/docs/resolving-search-engine-friendly-urls
-originalArticleId: 41034f7a-96b3-47d8-80ab-6ef8c62b8a4b
-redirect_from:
-  - /docs/scos/dev/glue-api-guides/202212.0/old-glue-infrastructure/resolving-search-engine-friendly-urls.html
-  - /docs/scos/dev/glue-api-guides/202212.0/old-glue-infrastructure/glue-api-resolve-search-engine-friendly-urls.html
-
-related:
-  - title: Install the Spryker Core Glue API
-    link: docs/pbc/all/miscellaneous/page.version/install-and-upgrade/install-glue-api/install-the-spryker-core-glue-api.html
----
-
-{% info_block warningBox %}
-
-This is a document related to the Old Glue infrastructure. For the new one, see [Decoupled Glue API](/docs/dg/dev/glue-api/{{page.version}}/decoupled-glue-api.html)
-
-{% endinfo_block %}
-
-This endpoints allows resolving Search Engine Friendly (SEF) URLs into a resource URL in Glue API.
-
-For SEO purposes, Spryker automatically generates SEF URLs for products and categories. The URLs are returned as a `url` attribute in responses related to abstract products and product categories. For examples of such responses, see:
-* [Retrieve an abstract product](/docs/pbc/all/product-information-management/{{page.version}}/base-shop/manage-using-glue-api/abstract-products/glue-api-retrieve-abstract-products.html#retrieve-an-abstract-product)
-* [Retrieve a category tree](/docs/pbc/all/product-information-management/{{page.version}}/base-shop/manage-using-glue-api/categories/glue-api-retrieve-category-trees.html#retrieve-a-category-tree)
-* [Retrieve a category node](/docs/pbc/all/product-information-management/{{page.version}}/base-shop/manage-using-glue-api/categories/glue-api-retrieve-category-nodes.html#retrieve-a-category-node)
-* [Retrieve a CMS page](/docs/pbc/all/content-management-system/{{page.version}}/base-shop/manage-using-glue-api/glue-api-retrieve-cms-pages.html)
-
-In your development, the endpoints can help you to:
-* significantly boost the SEO presence of your product store
-* increase search engine ranking of your online store
-
-To facilitate their usage, Spryker Glue provides an endpoint that allows resolving a SEO-friendly URL, for example, `http://mysprykershop.com/en/canon-powershot-n-35`, into a URL of the relevant product resource in Glue API, for example, `https://glue.mysprykershop.com/abstract-products/035`. This capability is provided by the URLs API.
-
-
-## Installation
-
-For detailed information on the modules that provide the API functionality and related installation instructions, see [Install the Spryker Core Glue API](/docs/pbc/all/miscellaneous/{{page.version}}/install-and-upgrade/install-glue-api/install-the-spryker-core-glue-api.html).
-
-## Resolve a SEF URL into a Glue API URL
-
-To resolve a SEF URL into a Glue API URL, send the request:
-
-***
-`GET` **/url-resolver?url={% raw %}*{{{% endraw %}SEF URL{% raw %}}}*{% endraw %}**
-***
-
-| PATH PARAMETER  | DESCRIPTION |
-| --------------- | ---------------- |
-| ***{% raw %}{{{% endraw %}SEF URL{% raw %}}}{% endraw %}*** | SEF URL you want to resolve. You can get it when:<ul><li>[retrieving abstract products](/docs/pbc/all/product-information-management/{{page.version}}/base-shop/manage-using-glue-api/abstract-products/glue-api-retrieve-abstract-products.html)</li><li>[retrieving category nodes](/docs/pbc/all/product-information-management/{{page.version}}/base-shop/manage-using-glue-api/categories/glue-api-retrieve-category-nodes.html)</li><li>[Retrieve CMS pages](/docs/pbc/all/content-management-system/{{page.version}}/base-shop/manage-using-glue-api/glue-api-retrieve-cms-pages.html)</li></ul>|
-
-### Request
-
-| HEADER KEY  | HEADER VALUE | REQUIRED | DESCRIPTION    |
-| -------------- | ------------ | ------------ | -------------- |
-| Accept-Language | de          | ✓      | Specifies the locale. |
-
-| REQUEST SAMPLE | USAGE |
-| --- | --- |
-| GET https://glue.mysprykershop.com/url-resolver?url=/de/acer-aspire-s7-134 | Resolve the following URL of a product: `https://mysprykershop.com/de/acer-aspire-s7-134` |
-| GET https://glue.mysprykershop.com/url-resolver?url=/en/computer | Resolve the following URL of a category node: `https://mysprykershop.com/en/computer` |
-| GET https://glue.mysprykershop.com/url-resolver?url=/de/ruecknahmegarantie | Resolve the following URL of a CMS page `https://mysprykershop.com/de/ruecknahmegarantie` |
-
-### Response
-
-<details>
-<summary markdown='span'>Response sample: resolve a product URL</summary>
-
-```json
-{
-    "data": [
-        {
-            "type": "url-resolver",
-            "id": null,
-            "attributes": {
-                "entityType": "abstract-products",
-                "entityId": "134"
-            },
-            "links": {
-                "self": "https://glue.mysprykershop.com/url-resolver?url=/de/acer-aspire-s7-134"
-            }
-        }
-    ],
-    "links": {
-        "self": "https://glue.mysprykershop.com/url-resolver?url=/de/acer-aspire-s7-134"
-    }
-}
-```    
-</details>
-
-<details>
-<summary markdown='span'>Response sample: resolve a category node URL</summary>
-
-```json
-{
-    "data": [
-        {
-            "type": "url-resolver",
-            "id": null,
-            "attributes": {
-                "entityType": "category-nodes",
-                "entityId": "5"
-            },
-            "links": {
-                "self": "https://glue.mysprykershop.com/url-resolver?url=/en/computer"
-            }
-        }
-    ],
-    "links": {
-        "self": "https://glue.mysprykershop.com/url-resolver?url=/en/computer"
-    }
-}
-```
-</details>
-
-<details>
-<summary markdown='span'>Response sample: resolve a CMS page URL</summary>
-
-```json
-{
-    "data": [
-        {
-            "type": "url-resolver",
-            "id": null,
-            "attributes": {
-                "entityType": "cms-pages",
-                "entityId": "8d378933-22f9-54c7-b45e-db68f2d5d9a3"
-            },
-            "links": {
-                "self": "https://glue.mysprykershop.com/url-resolver?url=/en/return-policy"
-            }
-        }
-    ],
-    "links": {
-        "self": "https://glue.mysprykershop.com/url-resolver?url=/en/return-policy"
-    }
-}
-```
-</details>
-
-| ATTRIBUTE | TYPE | DESCRIPTION |
-| --- | --- | --- |
-| entityType | String | Resource type, like `abstract-products` or `category-nodes`, `cms-pages`. |
-| entityId | String | Unique resource identifier. |
-
-Using the information from the response and the Glue server name, you can construct the Glue resource URLs. For example:
-* `https://glue.mysprykershop.com/abstract-products/134`
-* `https://glue.mysprykershop.com/category-nodes/5`
-* `https://glue.mysprykershop.com/cms-pages/8d378933-22f9-54c7-b45e-db68f2d5d9a3`
-
-## Possible errors
-
-| CODE | REASON |
-| --- | --- |
-| 2801 | The `url` parameter is missing. |
-| 2802 | The provided URL does not exist. |
-
-To view generic errors that originate from the Glue Application, see [Reference information: GlueApplication errors](/docs/dg/dev/glue-api/{{page.version}}/old-glue-infrastructure/reference-information-glueapplication-errors.html).
diff --git a/docs/dg/dev/glue-api/202311.0/old-glue-infrastructure/resolving-search-engine-friendly-urls.md b/docs/dg/dev/glue-api/202212.0/old-glue-infrastructure/resolving-search-engine-friendly-urls.md
similarity index 95%
rename from docs/dg/dev/glue-api/202311.0/old-glue-infrastructure/resolving-search-engine-friendly-urls.md
rename to docs/dg/dev/glue-api/202212.0/old-glue-infrastructure/resolving-search-engine-friendly-urls.md
index 991d5adf121..6462c1903d1 100644
--- a/docs/dg/dev/glue-api/202311.0/old-glue-infrastructure/resolving-search-engine-friendly-urls.md
+++ b/docs/dg/dev/glue-api/202212.0/old-glue-infrastructure/resolving-search-engine-friendly-urls.md
@@ -6,9 +6,13 @@ template: glue-api-storefront-guide-template
 originalLink: https://documentation.spryker.com/2021080/docs/resolving-search-engine-friendly-urls
 originalArticleId: 41034f7a-96b3-47d8-80ab-6ef8c62b8a4b
 redirect_from:
-  - /docs/scos/dev/glue-api-guides/202311.0/old-glue-infrastructure/resolving-search-engine-friendly-urls.html
-  - /docs/scos/dev/glue-api-guides/202311.0/resolving-search-engine-friendly-urls.html
-  - /docs/scos/dev/glue-api-guides/202204.0/resolving-search-engine-friendly-urls.html
+  - /2021080/docs/resolving-search-engine-friendly-urls
+  - /2021080/docs/en/resolving-search-engine-friendly-urls
+  - /docs/resolving-search-engine-friendly-urls
+  - /docs/en/resolving-search-engine-friendly-urls
+  - /docs/scos/dev/glue-api-guides/202307.0/resolving-search-engine-friendly-urls.html
+  - /docs/scos/dev/glue-api-guides/202307.0/old-glue-infrastructure/resolving-search-engine-friendly-urls.html
+
 related:
   - title: Install the Spryker Core Glue API
     link: docs/pbc/all/miscellaneous/page.version/install-and-upgrade/install-glue-api/install-the-spryker-core-glue-api.html

From c8884178c7f690f7d9e80443f5d3a1c58b7c01b3 Mon Sep 17 00:00:00 2001
From: Andrii Tserkovnyi <andrii.tserkovnyi@spryker.com>
Date: Mon, 25 Mar 2024 14:51:25 +0200
Subject: [PATCH 25/26] Update dg_dev_sidebar.yml

---
 _data/sidebars/dg_dev_sidebar.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_data/sidebars/dg_dev_sidebar.yml b/_data/sidebars/dg_dev_sidebar.yml
index 23206f2e3d2..945a6cdd9c2 100644
--- a/_data/sidebars/dg_dev_sidebar.yml
+++ b/_data/sidebars/dg_dev_sidebar.yml
@@ -1406,7 +1406,7 @@ entries:
         include_versions:
         - "202212.0"
       - title: Resolve search engine friendly URLs
-        url: /docs/dg/dev/glue-api/old-glue-infrastructure/glue-api-resolve-search-engine-friendly-urls.html
+        url: /docs/dg/dev/glue-api/202212.0/old-glue-infrastructure/resolving-search-engine-friendly-urls.html
         include_versions:
         - "202212.0"
         - "202307.0"

From 555b2f70f6354f44d4b5c4148a1766c7800e40e7 Mon Sep 17 00:00:00 2001
From: Andrii Tserkovnyi <andrii.tserkovnyi@spryker.com>
Date: Mon, 25 Mar 2024 15:18:43 +0200
Subject: [PATCH 26/26] links

---
 ...e-api-retrieve-autocomplete-and-search-suggestions.md | 6 ------
 ...e-api-retrieve-autocomplete-and-search-suggestions.md | 9 +--------
 2 files changed, 1 insertion(+), 14 deletions(-)

diff --git a/docs/pbc/all/search/202311.0/base-shop/manage-using-glue-api/glue-api-retrieve-autocomplete-and-search-suggestions.md b/docs/pbc/all/search/202311.0/base-shop/manage-using-glue-api/glue-api-retrieve-autocomplete-and-search-suggestions.md
index f874b63f386..af85493620b 100644
--- a/docs/pbc/all/search/202311.0/base-shop/manage-using-glue-api/glue-api-retrieve-autocomplete-and-search-suggestions.md
+++ b/docs/pbc/all/search/202311.0/base-shop/manage-using-glue-api/glue-api-retrieve-autocomplete-and-search-suggestions.md
@@ -235,10 +235,4 @@ To retrieve a search suggestion, send the request:
 | abstractProducts.images.externalUrlSmall | String | URL of the product's preview image. |
 | abstractProducts.images.externalUrlLarg | String | URL of the product's large image. |
 
-{% info_block infoBox "SEO-friendly URLs" %}
-
-The `url` attribute of categories and abstract products exposes a SEO-friendly URL of the resource that represents the respective category or product. For information on how to resolve such a URL and retrieve the corresponding resource, see [Resolving search engine friendly URLs](/docs/dg/dev/glue-api/{{page.version}}/old-glue-infrastructure/resolving-search-engine-friendly-urls.html).
-
-{% endinfo_block %}
-
 To view generic errors that originate from the Glue Application, see [Reference information: GlueApplication errors](/docs/dg/dev/glue-api/{{page.version}}/old-glue-infrastructure/reference-information-glueapplication-errors.html).
diff --git a/docs/pbc/all/search/202311.0/marketplace/glue-api-retrieve-autocomplete-and-search-suggestions.md b/docs/pbc/all/search/202311.0/marketplace/glue-api-retrieve-autocomplete-and-search-suggestions.md
index 617aef594e8..e8f3a038719 100644
--- a/docs/pbc/all/search/202311.0/marketplace/glue-api-retrieve-autocomplete-and-search-suggestions.md
+++ b/docs/pbc/all/search/202311.0/marketplace/glue-api-retrieve-autocomplete-and-search-suggestions.md
@@ -1801,14 +1801,7 @@ To retrieve a search suggestion, send the request:
 | cmsPageCollection.name       | String   | Specifies the page title. |
 | cmsPageCollection.url      | String   | Specifies the page URL.   |
 
-
-{% info_block infoBox "SEO-friendly URLs" %}
-
-The `url` attribute of categories and abstract products exposes a SEO-friendly URL of the resource that represents the respective category or product. For information about how to resolve such a URL and retrieve the corresponding resource, see [Resolving search engine friendly URLs](/docs/dg/dev/glue-api/{{page.version}}/old-glue-infrastructure/resolving-search-engine-friendly-urls.html).
-
-{% endinfo_block %}
-
-{% info_block warningBox "Warning" %}
+{% info_block warningBox "" %}
 
 Although CMS pages also expose the `url` parameter, resolving of CMS page SEF URLs is not supported at the moment.