diff --git a/assets/acl-address-schema.svg b/assets/acl-address-schema.svg
deleted file mode 100644
index e24a99b9a..000000000
--- a/assets/acl-address-schema.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/assets/acl-architecture.svg b/assets/acl-architecture.svg
deleted file mode 100644
index 436c06a32..000000000
--- a/assets/acl-architecture.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/assets/ajax-panel-structure.svg b/assets/ajax-panel-structure.svg
deleted file mode 100644
index b48b35e8c..000000000
--- a/assets/ajax-panel-structure.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/assets/app-extension-model.png b/assets/app-extension-model.png
deleted file mode 100644
index a4caec6b5..000000000
Binary files a/assets/app-extension-model.png and /dev/null differ
diff --git a/assets/assignment-service.svg b/assets/assignment-service.svg
deleted file mode 100644
index e8beaa21f..000000000
--- a/assets/assignment-service.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/assets/authentication-overview.svg b/assets/authentication-overview.svg
deleted file mode 100644
index 3fa59d28a..000000000
--- a/assets/authentication-overview.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/assets/b2b-architecture-acl.png b/assets/b2b-architecture-acl.png
deleted file mode 100644
index 09dd803cb..000000000
Binary files a/assets/b2b-architecture-acl.png and /dev/null differ
diff --git a/assets/b2b-architecture-component.png b/assets/b2b-architecture-component.png
deleted file mode 100644
index 13a0219bc..000000000
Binary files a/assets/b2b-architecture-component.png and /dev/null differ
diff --git a/assets/b2b-architecture-components-complete.png b/assets/b2b-architecture-components-complete.png
deleted file mode 100644
index 4d073c099..000000000
Binary files a/assets/b2b-architecture-components-complete.png and /dev/null differ
diff --git a/assets/b2b-architecture-order.png b/assets/b2b-architecture-order.png
deleted file mode 100644
index bd6737297..000000000
Binary files a/assets/b2b-architecture-order.png and /dev/null differ
diff --git a/assets/b2b-architecture-users.png b/assets/b2b-architecture-users.png
deleted file mode 100644
index 14e44353d..000000000
Binary files a/assets/b2b-architecture-users.png and /dev/null differ
diff --git a/assets/b2bSuite-concept-lineItemFullDataStructure.svg b/assets/b2bSuite-concept-lineItemFullDataStructure.svg
new file mode 100644
index 000000000..eed2ef675
--- /dev/null
+++ b/assets/b2bSuite-concept-lineItemFullDataStructure.svg
@@ -0,0 +1,52 @@
+
diff --git a/assets/b2bSuite-concept-lineItemInternalDataStructure.svg b/assets/b2bSuite-concept-lineItemInternalDataStructure.svg
new file mode 100644
index 000000000..8aa3e5185
--- /dev/null
+++ b/assets/b2bSuite-concept-lineItemInternalDataStructure.svg
@@ -0,0 +1,36 @@
+
diff --git a/assets/b2bSuite-concept-lineItemListComponents.svg b/assets/b2bSuite-concept-lineItemListComponents.svg
new file mode 100644
index 000000000..aada1cb81
--- /dev/null
+++ b/assets/b2bSuite-concept-lineItemListComponents.svg
@@ -0,0 +1,89 @@
+
diff --git a/assets/b2bSuite-concept-lineItemListDataStructure.svg b/assets/b2bSuite-concept-lineItemListDataStructure.svg
new file mode 100644
index 000000000..a899335c7
--- /dev/null
+++ b/assets/b2bSuite-concept-lineItemListDataStructure.svg
@@ -0,0 +1,36 @@
+
diff --git a/assets/b2bSuite-concept-orderContingentManagement.svg b/assets/b2bSuite-concept-orderContingentManagement.svg
new file mode 100644
index 000000000..45376362b
--- /dev/null
+++ b/assets/b2bSuite-concept-orderContingentManagement.svg
@@ -0,0 +1,44 @@
+
diff --git a/assets/b2bSuite-concept-systemArchitectureAcl.svg b/assets/b2bSuite-concept-systemArchitectureAcl.svg
new file mode 100644
index 000000000..8c8d708d4
--- /dev/null
+++ b/assets/b2bSuite-concept-systemArchitectureAcl.svg
@@ -0,0 +1,16 @@
+
diff --git a/assets/b2bSuite-concept-systemArchitectureComponentLayering.svg b/assets/b2bSuite-concept-systemArchitectureComponentLayering.svg
new file mode 100644
index 000000000..095cdbb0c
--- /dev/null
+++ b/assets/b2bSuite-concept-systemArchitectureComponentLayering.svg
@@ -0,0 +1,46 @@
+
diff --git a/assets/b2bSuite-concept-systemArchitectureUserManagement.svg b/assets/b2bSuite-concept-systemArchitectureUserManagement.svg
new file mode 100644
index 000000000..30e621aa0
--- /dev/null
+++ b/assets/b2bSuite-concept-systemArchitectureUserManagement.svg
@@ -0,0 +1,33 @@
+
diff --git a/assets/b2bSuite-concept-systemArchitectureWholePicture.svg b/assets/b2bSuite-concept-systemArchitectureWholePicture.svg
new file mode 100644
index 000000000..ee9462c48
--- /dev/null
+++ b/assets/b2bSuite-concept-systemArchitectureWholePicture.svg
@@ -0,0 +1,100 @@
+
diff --git a/assets/b2bSuite-core-assignmentService.svg b/assets/b2bSuite-core-assignmentService.svg
new file mode 100644
index 000000000..f2d424d2f
--- /dev/null
+++ b/assets/b2bSuite-core-assignmentService.svg
@@ -0,0 +1,22 @@
+
diff --git a/assets/b2bSuite-core-authentication.svg b/assets/b2bSuite-core-authentication.svg
new file mode 100644
index 000000000..65848d34d
--- /dev/null
+++ b/assets/b2bSuite-core-authentication.svg
@@ -0,0 +1,94 @@
+
diff --git a/assets/b2bSuite-core-crudServicePattern.svg b/assets/b2bSuite-core-crudServicePattern.svg
new file mode 100644
index 000000000..26360c987
--- /dev/null
+++ b/assets/b2bSuite-core-crudServicePattern.svg
@@ -0,0 +1,51 @@
+
diff --git a/assets/b2bSuite-core-currencyComponent.svg b/assets/b2bSuite-core-currencyComponent.svg
new file mode 100644
index 000000000..90bf53a3c
--- /dev/null
+++ b/assets/b2bSuite-core-currencyComponent.svg
@@ -0,0 +1,83 @@
+
diff --git a/assets/b2bSuite-core-entityAcl.svg b/assets/b2bSuite-core-entityAcl.svg
new file mode 100644
index 000000000..4fa2013f4
--- /dev/null
+++ b/assets/b2bSuite-core-entityAcl.svg
@@ -0,0 +1,201 @@
+
diff --git a/assets/b2bSuite-core-entityAclArchitecture.svg b/assets/b2bSuite-core-entityAclArchitecture.svg
new file mode 100644
index 000000000..b1628c8c1
--- /dev/null
+++ b/assets/b2bSuite-core-entityAclArchitecture.svg
@@ -0,0 +1,53 @@
+
diff --git a/assets/b2bSuite-core-listingService.svg b/assets/b2bSuite-core-listingService.svg
new file mode 100644
index 000000000..beecada60
--- /dev/null
+++ b/assets/b2bSuite-core-listingService.svg
@@ -0,0 +1,35 @@
+
diff --git a/assets/b2bSuite-storefront-ajaxPanel.svg b/assets/b2bSuite-storefront-ajaxPanel.svg
new file mode 100644
index 000000000..42516eb37
--- /dev/null
+++ b/assets/b2bSuite-storefront-ajaxPanel.svg
@@ -0,0 +1,72 @@
+
diff --git a/assets/b2bSuite-storefront-companyComponents.svg b/assets/b2bSuite-storefront-companyComponents.svg
new file mode 100644
index 000000000..7c2787330
--- /dev/null
+++ b/assets/b2bSuite-storefront-companyComponents.svg
@@ -0,0 +1,52 @@
+
diff --git a/assets/b2bSuite-storefront-controller-structure.svg b/assets/b2bSuite-storefront-controller-structure.svg
new file mode 100644
index 000000000..29bf73609
--- /dev/null
+++ b/assets/b2bSuite-storefront-controller-structure.svg
@@ -0,0 +1,116 @@
+
diff --git a/assets/checkout-payment-paymentFlow.svg b/assets/checkout-payment-paymentFlow.svg
new file mode 100644
index 000000000..ca74ad002
--- /dev/null
+++ b/assets/checkout-payment-paymentFlow.svg
@@ -0,0 +1,101 @@
+
diff --git a/assets/commerce-checkout-cartStruct.svg b/assets/commerce-checkout-cartStruct.svg
new file mode 100644
index 000000000..28214fa4e
--- /dev/null
+++ b/assets/commerce-checkout-cartStruct.svg
@@ -0,0 +1,87 @@
+
diff --git a/assets/commerce-content-cms.svg b/assets/commerce-content-cms.svg
new file mode 100644
index 000000000..69d994806
--- /dev/null
+++ b/assets/commerce-content-cms.svg
@@ -0,0 +1,32 @@
+
diff --git a/assets/company-management.svg b/assets/company-management.svg
deleted file mode 100644
index e7ea1a88c..000000000
--- a/assets/company-management.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/assets/concept-api-storeApi-dataAndLogicFlow.png b/assets/concept-api-storeApi-dataAndLogicFlow.png
deleted file mode 100644
index af09d6f53..000000000
Binary files a/assets/concept-api-storeApi-dataAndLogicFlow.png and /dev/null differ
diff --git a/assets/concept-commerce-shoppingExperiences-resolvingCmsPage.png b/assets/concept-commerce-shoppingExperiences-resolvingCmsPage.png
deleted file mode 100644
index a28a8a6de..000000000
Binary files a/assets/concept-commerce-shoppingExperiences-resolvingCmsPage.png and /dev/null differ
diff --git a/assets/concepts-api-storeApiLogic.svg b/assets/concepts-api-storeApiLogic.svg
new file mode 100644
index 000000000..44e68144a
--- /dev/null
+++ b/assets/concepts-api-storeApiLogic.svg
@@ -0,0 +1,34 @@
+
diff --git a/assets/concepts-extensions-apps.svg b/assets/concepts-extensions-apps.svg
new file mode 100644
index 000000000..65d4122cd
--- /dev/null
+++ b/assets/concepts-extensions-apps.svg
@@ -0,0 +1,26 @@
+
diff --git a/assets/concepts-extensions-plugins.svg b/assets/concepts-extensions-plugins.svg
new file mode 100644
index 000000000..0ca5793b1
--- /dev/null
+++ b/assets/concepts-extensions-plugins.svg
@@ -0,0 +1,28 @@
+
diff --git a/assets/concepts-framework-httpCache.svg b/assets/concepts-framework-httpCache.svg
new file mode 100644
index 000000000..2e2c61299
--- /dev/null
+++ b/assets/concepts-framework-httpCache.svg
@@ -0,0 +1,30 @@
+
diff --git a/assets/concepts-storefront-composite-data-loading.png b/assets/concepts-storefront-composite-data-loading.png
deleted file mode 100644
index cd538f9dd..000000000
Binary files a/assets/concepts-storefront-composite-data-loading.png and /dev/null differ
diff --git a/assets/contact-controller-complex-example.svg b/assets/contact-controller-complex-example.svg
deleted file mode 100644
index b9c351e67..000000000
--- a/assets/contact-controller-complex-example.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/assets/crud-service.svg b/assets/crud-service.svg
deleted file mode 100644
index f27f92338..000000000
--- a/assets/crud-service.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/assets/currency-usage.svg b/assets/currency-usage.svg
deleted file mode 100644
index d8339cffd..000000000
--- a/assets/currency-usage.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/assets/extensions-apps-shopwareCommunication.svg b/assets/extensions-apps-shopwareCommunication.svg
new file mode 100644
index 000000000..138c3e68c
--- /dev/null
+++ b/assets/extensions-apps-shopwareCommunication.svg
@@ -0,0 +1,28 @@
+
diff --git a/assets/framework-rules-rulesScope.svg b/assets/framework-rules-rulesScope.svg
new file mode 100644
index 000000000..406f2fc4b
--- /dev/null
+++ b/assets/framework-rules-rulesScope.svg
@@ -0,0 +1,535 @@
+
+
\ No newline at end of file
diff --git a/assets/framework-storefront-comnpositeData.svg b/assets/framework-storefront-comnpositeData.svg
new file mode 100644
index 000000000..74ee9cf7e
--- /dev/null
+++ b/assets/framework-storefront-comnpositeData.svg
@@ -0,0 +1,77 @@
+
diff --git a/assets/hosting-infrastructure-reverseHttpCache.svg b/assets/hosting-infrastructure-reverseHttpCache.svg
new file mode 100644
index 000000000..7ec8f55d8
--- /dev/null
+++ b/assets/hosting-infrastructure-reverseHttpCache.svg
@@ -0,0 +1,26 @@
+
diff --git a/assets/line-item-list-outer-dependencies.svg b/assets/line-item-list-outer-dependencies.svg
deleted file mode 100644
index ae0e665c4..000000000
--- a/assets/line-item-list-outer-dependencies.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/assets/line-item-list-with-listing.svg b/assets/line-item-list-with-listing.svg
deleted file mode 100644
index cd7f1ab97..000000000
--- a/assets/line-item-list-with-listing.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/assets/line-item-list-with-order-context.svg b/assets/line-item-list-with-order-context.svg
deleted file mode 100644
index 5eaaa11c1..000000000
--- a/assets/line-item-list-with-order-context.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/assets/line-item-list-with-order.svg b/assets/line-item-list-with-order.svg
deleted file mode 100644
index 6642fb0c5..000000000
--- a/assets/line-item-list-with-order.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/assets/listing-service.svg b/assets/listing-service.svg
deleted file mode 100644
index 4f6be4d02..000000000
--- a/assets/listing-service.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/assets/order-delivery-state-machine.png b/assets/order-delivery-state-machine.png
deleted file mode 100644
index 90d6d4a0a..000000000
Binary files a/assets/order-delivery-state-machine.png and /dev/null differ
diff --git a/assets/order-payment-state-machine.png b/assets/order-payment-state-machine.png
deleted file mode 100644
index 3cb3a4f47..000000000
Binary files a/assets/order-payment-state-machine.png and /dev/null differ
diff --git a/assets/order-state-machine.png b/assets/order-state-machine.png
deleted file mode 100644
index 313de8ca7..000000000
Binary files a/assets/order-state-machine.png and /dev/null differ
diff --git a/assets/payment-flow-headless.png b/assets/payment-flow-headless.png
deleted file mode 100644
index 93cdb380f..000000000
Binary files a/assets/payment-flow-headless.png and /dev/null differ
diff --git a/assets/plugin-extension-model.png b/assets/plugin-extension-model.png
deleted file mode 100644
index 104a804e3..000000000
Binary files a/assets/plugin-extension-model.png and /dev/null differ
diff --git a/assets/plugins-apps-appBaseGuide.svg b/assets/plugins-apps-appBaseGuide.svg
new file mode 100644
index 000000000..056151551
--- /dev/null
+++ b/assets/plugins-apps-appBaseGuide.svg
@@ -0,0 +1,30 @@
+
diff --git a/assets/reverse-proxy.svg b/assets/reverse-proxy.svg
deleted file mode 100644
index 3c1913176..000000000
--- a/assets/reverse-proxy.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/assets/reverseProxy-setup.svg b/assets/reverseProxy-setup.svg
deleted file mode 100644
index e570d09fa..000000000
--- a/assets/reverseProxy-setup.svg
+++ /dev/null
@@ -1,8 +0,0 @@
-
\ No newline at end of file
diff --git a/assets/rule-classes.png b/assets/rule-classes.png
deleted file mode 100644
index e45c2fb2c..000000000
Binary files a/assets/rule-classes.png and /dev/null differ
diff --git a/assets/shop-app-communication-1-.svg b/assets/shop-app-communication-1-.svg
deleted file mode 100644
index 7bb24a28b..000000000
--- a/assets/shop-app-communication-1-.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/assets/shop-app-communication.svg b/assets/shop-app-communication.svg
deleted file mode 100644
index 4fe2298b4..000000000
--- a/assets/shop-app-communication.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/concepts/api/store-api.md b/concepts/api/store-api.md
index e07127f4d..635d7bccd 100644
--- a/concepts/api/store-api.md
+++ b/concepts/api/store-api.md
@@ -9,7 +9,7 @@ nav:
Every interaction between the store and a customer can be modeled using the Store API. It serves as a normalized layer or an interface to communicate between customer-facing applications and the Shopware Core. It can be used to build custom frontends like SPAs, native apps, or simple catalog apps. It doesn't matter what you want to build as long as you are able to consume a JSON API via HTTP.
-
+
Whenever additional logic is added to Shopware, the method of the corresponding service is exposed via a dedicated HTTP route. At the same time, it can be programmatically used to provide data to a controller or other services in the stack. This way, you can ensure that there is always common logic between the API and the Storefront and almost no redundancy. It also allows us to build core functionalities into our Storefront without compromising support for our API consumers.
diff --git a/concepts/commerce/checkout-concept/cart.md b/concepts/commerce/checkout-concept/cart.md
index 7df8e362d..9f5e92e46 100644
--- a/concepts/commerce/checkout-concept/cart.md
+++ b/concepts/commerce/checkout-concept/cart.md
@@ -31,7 +31,7 @@ The cart has very few hard dependencies on other core entities in Shopware 6. En
An instance of this class represents one single cart. As shown in the diagram below, relations to central Entities of the system are omitted. This allows Shopware 6 to manage multiple carts per user, per sales channel, or across all sales channels. The only identification is a token hash.
-
+
This highly mutable data structure is acted upon from requests and calculated and validated through services. It contains:
diff --git a/concepts/commerce/checkout-concept/payments.md b/concepts/commerce/checkout-concept/payments.md
index 263d6d642..39346c451 100644
--- a/concepts/commerce/checkout-concept/payments.md
+++ b/concepts/commerce/checkout-concept/payments.md
@@ -22,7 +22,7 @@ The payment and checkout flow consist of two essential steps:
These steps are outlined in the diagram below:
-
+
The diagram above shows the payment flow for headless environments; however, for the single-stack scenario (i.e., when the default Storefront is used) the differences are minor and described in the section below.
diff --git a/concepts/commerce/content/shopping-experiences-cms.md b/concepts/commerce/content/shopping-experiences-cms.md
index 45b5a4aa3..568d01e75 100644
--- a/concepts/commerce/content/shopping-experiences-cms.md
+++ b/concepts/commerce/content/shopping-experiences-cms.md
@@ -143,7 +143,7 @@ Whereas the structure of a CMS page remains somewhat static, its content can be
The following diagram illustrates how that works using the example of a category:
-.
+
Let's go through the steps one by one.
diff --git a/concepts/extensions/apps-concept.md b/concepts/extensions/apps-concept.md
index 1e280b349..be4efa3f8 100644
--- a/concepts/extensions/apps-concept.md
+++ b/concepts/extensions/apps-concept.md
@@ -20,7 +20,7 @@ The central interface between your app and Shopware is defined by a dedicated ma
Shopware communicates with your app only exclusively via HTTP-Requests. Therefore you are free to choose a tech stack for your app, as long as you can serve HTTP-Requests. Shopware will notify you of events happening in the shop that your app is interested in by posting to HTTP-Endpoints that you define in the manifest file. While processing these events, your app can use the Shopware API to get additional data that your app needs. A schematic overview of the communication may look like this:
-
+
To secure this communication, a registration handshake is performed during the installation of your app. During this registration, it is verified that Shopware talks to the right app backend server, and your app gets credentials used to authenticate against the API. You can read more on the registration workflow in the [App base guide](../../guides/plugins/apps/app-base-guide).
diff --git a/concepts/extensions/index.md b/concepts/extensions/index.md
index 49307873c..bfb2927ab 100644
--- a/concepts/extensions/index.md
+++ b/concepts/extensions/index.md
@@ -11,13 +11,13 @@ In order to provide users \(i.e., developers\) with a clear abstraction, Shopwar
## Apps
-
+
Starting with Shopware 6.4.0.0, we introduced a new way to extend Shopware using the newly created app system. Apps are not executed within the process of the Shopware Core but are notified about events via webhooks, which they can register. They can modify and interact with Shopware resources through the [Admin REST API](https://shopware.stoplight.io/docs/admin-api/twpxvnspkg3yu-quick-start-guide).
## Plugins
-
+
Plugins are executed within the Shopware Core process and can react to events, execute custom code or extend services. They have direct access to the database and guidelines are in place to ensure update-compatibility, such as a service facade or database migrations.
diff --git a/concepts/framework/architecture/storefront-concept.md b/concepts/framework/architecture/storefront-concept.md
index 9b68bd94b..eee3beebf 100644
--- a/concepts/framework/architecture/storefront-concept.md
+++ b/concepts/framework/architecture/storefront-concept.md
@@ -99,7 +99,7 @@ Once we have set all the necessary information to our page \(`AccountOrderPage`\
To summarize the composition of a page, have a look at this diagram:
-
+
## Translations
diff --git a/concepts/framework/http_cache.md b/concepts/framework/http_cache.md
index 304a31a90..235125e4f 100644
--- a/concepts/framework/http_cache.md
+++ b/concepts/framework/http_cache.md
@@ -22,7 +22,7 @@ So whenever a user requests a page, Shopware will create a result page individua
* A reverse proxy cache
* The web application generates a result
-
+
The reverse proxy is located between the user and the web application and takes care of any requests to the web application. If a user requests a page that has been requested before, chances are that the reverse proxy can just hand out the same result as before, so the web application will not even be asked.
diff --git a/concepts/framework/rules.md b/concepts/framework/rules.md
index abf4cb0fd..e77125a64 100644
--- a/concepts/framework/rules.md
+++ b/concepts/framework/rules.md
@@ -70,7 +70,7 @@ As you can see, a single rule can either contain user defined values or other us
The last building block is the **Rule Scope**. The Scope contains the current runtime state of the application and is necessary to match the data. The whole picture is visualized in the next diagram:
-
+
## Connection to the System
diff --git a/guides/hosting/infrastructure/reverse-http-cache.md b/guides/hosting/infrastructure/reverse-http-cache.md
index 6b5ae0dff..ea3d39338 100644
--- a/guides/hosting/infrastructure/reverse-http-cache.md
+++ b/guides/hosting/infrastructure/reverse-http-cache.md
@@ -24,7 +24,7 @@ In this guide, we will use Varnish as an example for HTTP cache.
This setup is compatible from Shopware version 6.4.
:::
-
+
### Configure Shopware
diff --git a/guides/plugins/apps/app-base-guide.md b/guides/plugins/apps/app-base-guide.md
index b9477efcd..c2fc1c6e1 100644
--- a/guides/plugins/apps/app-base-guide.md
+++ b/guides/plugins/apps/app-base-guide.md
@@ -80,7 +80,7 @@ Additionally, your app will provide a secret that Shopware will use to sign all
The setup workflow is shown in the following schema. Each step will be explained in detail.
-
+
::: info
The timeout for the requests against the app server is 5 seconds.
diff --git a/products/extensions/b2b-suite/concept/line-item-list.md b/products/extensions/b2b-suite/concept/line-item-list.md
index 7f6eb3ce7..9d8e3af33 100644
--- a/products/extensions/b2b-suite/concept/line-item-list.md
+++ b/products/extensions/b2b-suite/concept/line-item-list.md
@@ -17,7 +17,11 @@ The LineItemList component is the central representation of product lists in the
* Guaranteed audit logging
The component is used across multiple different child components throughout the B2B Suite.
-
+
+
+|Symbol|Description|
+|------|------------|
+|| Component |
The yellow colored blocks represent components, while the smaller green ones are context objects that contain the component specific information.
@@ -29,18 +33,18 @@ In most cases, these line items will be products but may include other types (e.
To make this work with the Shopware cart, order, and product listing, the `LineItemReferences` themselves can be set up by different entities.
Schematically a list that is not yet ordered looks like this:
-
+
Whereas an ordered list looks like this:
-
+
As you can see, each `LineItemReference` borrows data from Shopware data structures, but a user of these objects can solely
depend on the `LineItemReference` and `LineItemList` objects for unified access.
This basic pattern revolves against other data structures in the component as well.
-
+
As you can see, the specific data is abstracted away through the order context object.
An object that can either be generated during the Shopware checkout process or be created dynamically through the API.
diff --git a/products/extensions/b2b-suite/concept/system-architecture.md b/products/extensions/b2b-suite/concept/system-architecture.md
index 4a218719a..f8a78140a 100644
--- a/products/extensions/b2b-suite/concept/system-architecture.md
+++ b/products/extensions/b2b-suite/concept/system-architecture.md
@@ -13,7 +13,7 @@ The B2B Suite is a collection of loosely coupled, mostly uniform components pack
A single component with all layers and the maximum of allowed dependencies looks like this:
-
+
The responsibilities from bottom to top:
@@ -39,19 +39,19 @@ There is a small library of shared functionality. It contains a few commonly use
The user management is based on the `StoreFrontAuthentication` component and then provides `Contact` and `Debtor` entities which have `Address`es and `Role`s. These entities are mostly informational and CRUD based. Other parts of the system only depend on the `StoreFrontAuthentication` component but not the specific implementations as *Debtor* or *Contact*.
-
+
### ACL
The `acl` implementation is connected to most other entities provided by the B2B Suite.
-
+
### Order and contingent management
`ContingentGroups`s are connected to `Debtor`s and can have `acl` settings based on `Role`s or `Contact`s. `Order`s are personalized through the `StoreFrontAuthentication`.
-
+
### The whole picture
@@ -62,6 +62,6 @@ Most dependencies are directly derived from requirements. So, the dependency flo
So, for the sake of completeness, this is the whole picture:
-
+
Everything you should get from that is that there is a left to right propagation of dependencies. The components on the left side can be useful entirely without the components on the right side.
diff --git a/products/extensions/b2b-suite/guides/core/assignment-service.md b/products/extensions/b2b-suite/guides/core/assignment-service.md
index b880f1e88..c4b3f00ed 100644
--- a/products/extensions/b2b-suite/guides/core/assignment-service.md
+++ b/products/extensions/b2b-suite/guides/core/assignment-service.md
@@ -14,7 +14,7 @@ The B2B Suite ships with many new entities and therefore provides the means to c
The diagram below shows the usually implemented objects with their outside dependencies.
-
+
## Repository
diff --git a/products/extensions/b2b-suite/guides/core/authentication.md b/products/extensions/b2b-suite/guides/core/authentication.md
index 1c66cf3a7..c5a6c5cdb 100644
--- a/products/extensions/b2b-suite/guides/core/authentication.md
+++ b/products/extensions/b2b-suite/guides/core/authentication.md
@@ -20,7 +20,7 @@ It extends the Shopware default authentication component and provides several be
A schematic overview of the central usage of the Authentication component looks like this:
-
+
| Color | Type | Description |
|--------|:--------:|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|
diff --git a/products/extensions/b2b-suite/guides/core/crud-service.md b/products/extensions/b2b-suite/guides/core/crud-service.md
index 2970e297a..c6d235a00 100644
--- a/products/extensions/b2b-suite/guides/core/crud-service.md
+++ b/products/extensions/b2b-suite/guides/core/crud-service.md
@@ -17,7 +17,7 @@ Although these entities may have special requirements, an exclusively used namin
The diagram below shows the usually implemented objects with their outside dependencies:
-
+
## Entity
diff --git a/products/extensions/b2b-suite/guides/core/currency.md b/products/extensions/b2b-suite/guides/core/currency.md
index 0108e8003..fe28d20c6 100644
--- a/products/extensions/b2b-suite/guides/core/currency.md
+++ b/products/extensions/b2b-suite/guides/core/currency.md
@@ -11,7 +11,7 @@ nav:
The Currency component provides the means for currency calculation in the B2B Suite. The following graph shows components depending on this component:
-
+
## Context
diff --git a/products/extensions/b2b-suite/guides/core/entity-acl.md b/products/extensions/b2b-suite/guides/core/entity-acl.md
index 7488ee18a..47435ee36 100644
--- a/products/extensions/b2b-suite/guides/core/entity-acl.md
+++ b/products/extensions/b2b-suite/guides/core/entity-acl.md
@@ -21,7 +21,7 @@ They provide the means of creating the tables, storing and removing the relation
In order to understand the design decisions of the ACL component, we first take a look at the different requirements imposed on ACL.
As you can see in the graphic below, access control is basically a concern of every technical layer of the application.
-
+
The base ACL component described in this document provides functionality for repository filtering and service checks.
The [Authentication component](authentication) provides the context for the currently logged-in user and the [ACL route](../storefront/acl-routing) component then provides the ability to secure routes and means of inspection for allowed routes.
@@ -58,7 +58,7 @@ CREATE TABLE `b2b_acl_*` (
For example, let's look at the schema part responsible for storing the address access rights.
-
+
As you can see, the addresses (subject) can be allowed in two distinct contexts.
Either through a *role* or through a *contact*. So between these entities are two ACL tables holding the M:N relations.
diff --git a/products/extensions/b2b-suite/guides/core/listing-service.md b/products/extensions/b2b-suite/guides/core/listing-service.md
index 1c185470e..d477c3ecd 100644
--- a/products/extensions/b2b-suite/guides/core/listing-service.md
+++ b/products/extensions/b2b-suite/guides/core/listing-service.md
@@ -17,7 +17,7 @@ To reduce the necessary duplications, there are common implementations for this.
The diagram below shows the usually implemented objects with their outside dependencies.
-
+
## Search struct
diff --git a/products/extensions/b2b-suite/guides/storefront/ajax-panel.md b/products/extensions/b2b-suite/guides/storefront/ajax-panel.md
index 94b958258..a3b71530e 100644
--- a/products/extensions/b2b-suite/guides/storefront/ajax-panel.md
+++ b/products/extensions/b2b-suite/guides/storefront/ajax-panel.md
@@ -65,7 +65,7 @@ One panel can influence another one by defining and linking to an id.
The B2B Suite comes with a library of simple helper plugins to add behavior to the ajax panels.
-
+
As you can see, there is the `AjaxPanelPluginLoader` responsible for initializing and reinitializing plugins inside b2b-panels.
Let's take our last example and extend it with a form plugin:
diff --git a/products/extensions/b2b-suite/guides/storefront/company.md b/products/extensions/b2b-suite/guides/storefront/company.md
index 8a85859f4..3628f9239 100644
--- a/products/extensions/b2b-suite/guides/storefront/company.md
+++ b/products/extensions/b2b-suite/guides/storefront/company.md
@@ -9,7 +9,7 @@ nav:
The company component acts as a container for role related entities by providing a minimalistic interface to the different components. This ensures shared functionality. The following graph shows components that are managed in this component:
-
+
## Context
diff --git a/products/extensions/b2b-suite/guides/storefront/complex-views.md b/products/extensions/b2b-suite/guides/storefront/complex-views.md
index 709ada2e8..159a1271e 100644
--- a/products/extensions/b2b-suite/guides/storefront/complex-views.md
+++ b/products/extensions/b2b-suite/guides/storefront/complex-views.md
@@ -9,7 +9,7 @@ nav:
The B2B Suite comes with a whole UI providing Administration like features in the frontend. The structure is reflected in the naming of the several controller classes. Each controller then uses a canonical naming scheme. The example below shows the *ContactController* with all its assignment controllers.
-
+
As you can see, every controller is associated with one specific component.