shopware · sushmangupta · Dec 4, 2023 · Nov 30, 2023 · Dec 4, 2023
diff --git a/concepts/commerce/catalog/products.md b/concepts/commerce/catalog/products.md
@@ -9,7 +9,7 @@ nav:
 
 Products are sellable entities (physical and digital products) within your shop.
 
-Depending on your setup, Shopware can easily handle thousands of products. However, an upsurge in the product quantity (in millions) needs some tweaks for robust running of the environment as it depends on factors like the number of [categories](../../../../docs/concepts/commerce/catalog/categories), [sales channels](../../../../docs/concepts/commerce/catalog/sales-channels), [product properties](../../../../docs/concepts/commerce/catalog/products#property-groups--options), etc. Every product added to your shop can be made available on one or more [sales channels](../../../../docs/concepts/commerce/catalog/sales-channels).
+Depending on your setup, Shopware can easily handle thousands of products. However, an upsurge in the product quantity (in millions) needs some tweaks for robust running of the environment as it depends on factors like the number of [categories](../../../../docs/concepts/commerce/catalog/categories.md), [sales channels](../../../../docs/concepts/commerce/catalog/sales-channels.md), [product properties](../../../../docs/concepts/commerce/catalog/products.md#property-groups--options), etc. Every product added to your shop can be made available on one or more [sales channels](../../../../docs/concepts/commerce/catalog/sales-channels.md).
 
 Let us start understanding about product more in detail:
 

diff --git a/guides/hosting/installation-updates/composer.md b/guides/hosting/installation-updates/composer.md
@@ -8,7 +8,7 @@ nav:
 # Versioning and Dependencies
 
 ::: danger
-This setup is no longer the recomended way to manage a Shopware installation. Please refer to our [Flex-guide](../../installation/flex#How-do-I-migrate-from-Production-Template-to-Symfony-Flex?) on how to migrate to a symfony flex based setup.
+This setup is no longer the recomended way to manage a Shopware installation. Please refer to our [Flex-guide](../../installation/template.md#how-do-i-migrate-from-production-template-to-symfony-flex) on how to migrate to a symfony flex based setup.
 :::
 
 ## Overview

diff --git a/guides/installation/legacy/docker.md b/guides/installation/legacy/docker.md
@@ -102,7 +102,7 @@ This command creates and starts the containers, watchers, and the sync itself. R
 ./psh.phar install
 ```
 
-For more information, look at Shopware [Installation Overview](overview).
+For more information, look at Shopware [Installation Overview](../index.md#installation-overview).
 
 ## Next steps
 

diff --git a/guides/installation/legacy/from-scratch.md b/guides/installation/legacy/from-scratch.md
@@ -8,7 +8,7 @@ nav:
 # Installation from Scratch
 
 ::: danger
-This approach is no longer recomended. It is kept here as a reference.
+This approach is no longer recommended. It is kept here as a reference.
 :::
 
 If it is *impossible* to get Docker up and running on your development environment, you can install Shopware 6 locally.
@@ -21,7 +21,7 @@ Be aware that this will be a vastly more complex solution since additional syste
 
 - A Linux-based operating system (Windows installation is not covered here, but notes are provided about installing within a WSL instance).
 - An [Apache2 server installation](https://httpd.apache.org/docs/2.4/install.html) within the Linux-based operating system you have selected.
-- Installation of all the required packages mentioned in the [Installation overview](overview). There are two main goals you need to accomplish.
+- Installation of all the required packages mentioned in the [Installation overview](../index.md#installation-overview). There are two main goals you need to accomplish.
 
 Please note that this guide is based on plugin development and contribution. If you need a template for full composer-based shop projects, refer to the [production template](https://github.com/shopware/production).
 
@@ -139,7 +139,7 @@ Within your Apache configuration, you must set your `DocumentRoot` and `Director
 
 ## Setting up Shopware
 
-Before you set up Shopware, you need to clone our Shopware repositories from version control. This is explained in the "Preparatory steps" paragraph of the [Installation overview](overview).
+Before you set up Shopware, you need to clone our Shopware repositories from version control. This is explained in the "Preparatory steps" paragraph of the [Installation overview](../index.md#installation-overview).
 
 ### Starting Shopware installation
 

diff --git a/guides/installation/legacy/mamp.md b/guides/installation/legacy/mamp.md
@@ -97,7 +97,7 @@ brew install composer
 
 ## Checkout Shopware
 
-Before you are able to set up Shopware, you need to checkout Shopware's repositories. This is explained in the "Preparatory steps" of the [Installation overview](overview)  guide. Nevertheless, below you see a brief summary of this process:
+Before you are able to set up Shopware, you need to checkout Shopware's repositories. This is explained in the "Preparatory steps" of the [Installation overview](../index.md#installation-overview).  guide. Nevertheless, below you see a brief summary of this process:
 
 ```bash
 # Choose your own directory

diff --git a/guides/installation/legacy/valet.md b/guides/installation/legacy/valet.md
@@ -19,7 +19,7 @@ This is a modified version of the [official Installation Guide](https://github.c
 
 ## Prerequisites
 
-Before proceeding with this guide, have a look at [Installation overview](overview). Also, your system should be running [brew](https://brew.sh/) and [Composer](https://getcomposer.org/) already.
+Before proceeding with this guide, have a look at [Installation overview](../index.md#installation-overview). Also, your system should be running [brew](https://brew.sh/) and [Composer](https://getcomposer.org/) already.
 
 ## If you have Valet installed
 

diff --git a/guides/plugins/apps/hosting-guide/platform-sh-deployment.md b/guides/plugins/apps/hosting-guide/platform-sh-deployment.md
@@ -13,7 +13,7 @@ nav:
 
 Keep in mind, though, that this is **not** the only way to go for apps. You can, of course, use different services, providers or host everything on a dedicated machine. This guide explains to you how to get started for hosting an app on Platform.sh.
 
-Read more about why this kind of hosting could be useful [here](README) or in there [official documentation](https://docs.platform.sh/).
+Know more about hosting from the [hosting guide](../hosting-guide/index.md) and from the [official documentation](https://docs.platform.sh/).
 
 ## Getting started
 

diff --git a/guides/plugins/apps/starter/starter-admin-extension.md b/guides/plugins/apps/starter/starter-admin-extension.md
@@ -155,4 +155,4 @@ This example showed end-to-end how to create a local dev environment and connect
 
 * Did you know, you can add [new sections](https://shopware.github.io/admin-extension-sdk/docs/guide/api-reference/ui/component-section) to the UI or even [entire modules](https://shopware.github.io/admin-extension-sdk/docs/guide/api-reference/ui/mainModule)?
 * The Admin Extension SDK also offers [TypeScript support](https://shopware.github.io/admin-extension-sdk/docs/guide/getting-started/installation#using-npm-require-bundling) (including autocompletion)
-* Don't want to extend the admin panel? Have a look at [App Scripts](/docs/guides/plugins/apps/app-scripts)
+* Don't want to extend the admin panel? Have a look at [App Scripts](../../../../../docs/guides/plugins/apps/app-scripts/index.md).
diff --git a/guides/plugins/plugins/framework/flow/add-flow-builder-trigger.md b/guides/plugins/plugins/framework/flow/add-flow-builder-trigger.md
@@ -339,7 +339,7 @@ class SendMailAction
 }
 ```
 
-Take a look at the [Add Flow Builder Action](/guides/plugins/plugins/framework/flow/add-flow-builder-action) section of the guide for how to use data in Flow Actions.
+Take a look at the [Add Flow Builder Action](../../../../../guides/plugins/plugins/framework/flow/add-flow-builder-action.md) section of the guide for how to use data in Flow Actions.
 
 ### Add your new event to the flow trigger list
 

diff --git a/products/extensions/b2b-suite/guides/administration/index.md b/products/extensions/b2b-suite/guides/administration/index.md
@@ -7,4 +7,4 @@ nav:
 
 # Administration
 
-B2B Suite Administration modules are built following the official [Shopware Administration](/docs/guides/plugins/plugins/administration) documentation. For a more in-depth guide, please refer to the [User documentation](https://docs.shopware.com/de/shopware-6-de/enterprise-erweiterungen/b2b-suite-administration).
+B2B Suite Administration modules are built following the official [Shopware Administration](../../../../../guides/plugins/plugins/administration/index.md) documentation. For a more in-depth guide, please refer to the [User documentation](https://docs.shopware.com/de/shopware-6-de/enterprise-erweiterungen/b2b-suite-administration).
diff --git a/products/extensions/b2b-suite/guides/core/listing-service.md b/products/extensions/b2b-suite/guides/core/listing-service.md
@@ -49,7 +49,7 @@ class SearchStruct
 }
 ```
 
-A more special `SearchStruct` is the `CompanyFilterStruct`. See the [Company](../../../../../../docs/products/extensions/b2b-suite/guides/storefront/company) module for more details.
+A more special `SearchStruct` is the `CompanyFilterStruct`. See the [Company](../../../../../../docs/products/extensions/b2b-suite/guides/storefront/company.md) module for more details.
 
 ## Repository
 

diff --git a/products/paas/repository.md b/products/paas/repository.md
@@ -15,7 +15,7 @@ This guide explains the repository setup using **GitHub**. You can also integrat
 
 ## Create a Shopware project
 
-Firstly,  create a new project with `composer create-project shopware/platform:dev-flex <folder-name>` using the [Symphony Flex](../../guides/installation/flex) template.
+Firstly,  create a new project with `composer create-project shopware/platform:dev-flex <folder-name>` using the [Symphony Flex](../../guides/installation/template.md) template.
 
 This will create a brand new Shopware 6 project in the given folder. Now, change it into the newly created project and require the PaaS configuration with `composer req paas`.
 
@@ -67,7 +67,7 @@ platform	<paas-url>.git (push)
 
 ## Migrating from old template to the new template
 
-If you have already used the [Shopware PaaS old template](https://github.com/shopware/paas), please follow the guide to [migrate it to the new structure](../../guides/installation/flex#how-to-migrate-from-production-template-to-symfony-flex).
+If you have already used the [Shopware PaaS old template](https://github.com/shopware/paas), please follow the guide to [migrate it to the new structure](../../guides/installation/template.md#how-do-i-migrate-from-production-template-to-symfony-flex).
 
 Following tasks has to be done additionally to the flex migration:
 

diff --git a/resources/guidelines/testing/store/quality-guidelines-apps/index.md b/resources/guidelines/testing/store/quality-guidelines-apps/index.md
@@ -58,8 +58,8 @@ We always test with the [actual SW6 version](https://www.shopware.com/de/downloa
 
 * [Sample app development template](https://github.com/shopwareLabs/AppExample)
 * [App base guide](/docs/guides/plugins/apps/app-base-guide)
-* [Storefront](/docs/guides/plugins/apps/storefront)
-* [Admin](/docs/guides/plugins/apps/administration)
+* [Storefront](/docs/guides/plugins/apps/storefront/index.md)
+* [Admin](/docs/guides/plugins/apps/administration/index.md)
 
 ## Checklist for app testing