diff --git a/concepts/framework/data-abstraction-layer.md b/concepts/framework/data-abstraction-layer.md
index 2447b4c082..69533f588a 100644
--- a/concepts/framework/data-abstraction-layer.md
+++ b/concepts/framework/data-abstraction-layer.md
@@ -35,7 +35,7 @@ This is the recommended way for developers to interface with the DAL or the data
 Before using the repositories, you will need to get them from the [Dependency Injection Container (DIC)](../../guides/plugins/plugins/plugin-fundamentals/dependency-injection).
 This is done with [Constructor injection](https://symfony.com/doc/current/service_container/injection_types.html#constructor-injection), so you will need to extend your services constructor by expecting an EntityRepository:
 
-```php
+```PHP
 // <plugin root>/src/Service/DalExampleService.php
 public function __construct (EntityRepository $productRepository)
 {
@@ -47,11 +47,10 @@ If you are using [Service autowiring](https://symfony.com/doc/current/service_co
 
 Alternatively, configure the `product.repository` service to be injected explicitly:
 
-```html
-// <plugin root>src/Resources/config/service.xml
-<service id="Swag\ExamplePlugin\Service\DalExampleService">
-    <argument type="service" id="product.repository"/>
-</service>
+```PHP
+// <plugin root>src/Resources/config/services.php
+$services->set(Swag\ExamplePlugin\Service\DalExampleService::class)
+    ->args([service('product.repository')]);
 ```
 
 You can read more about dependency injection and service registration in Shopware in the services guides:
diff --git a/guides/hosting/configurations/observability/profiling.md b/guides/hosting/configurations/observability/profiling.md
index d5ce6761a1..b27cdf947a 100644
--- a/guides/hosting/configurations/observability/profiling.md
+++ b/guides/hosting/configurations/observability/profiling.md
@@ -34,7 +34,7 @@ The OpenTelemetry profiler is not installed by default. Checkout the [OpenTeleme
 
 To add custom spans to the profiler, you can use the `Shopware\Core\Profiling\Profiler::trace` method:
 
-```php
+```PHP
 use Shopware\Core\Profiling\Profiler;
 
 $value = Profiler::trace('my-example-trace', function () {
@@ -50,7 +50,7 @@ To add a custom profiler backend, you need to implement the `Shopware\Core\Profi
 
 The following example shows a custom profiler backend that logs the traces to the console:
 
-```php
+```PHP
 
 namespace App\Profiler;
 
@@ -70,10 +70,9 @@ class ConsoleProfiler implements ProfilerInterface
 }
 ```
 
-```XML
-<service id="App\Profiler">
-    <tag name="shopware.profiler" integration="Console"/>
-</service>
+```PHP
+$services->set(App\Profiler::class)
+    ->tag('shopware.profiler', ['integration' => 'Console']);
 ```
 
 The attribute `integration` is used to identify the profiler backend in the configuration.
diff --git a/guides/hosting/performance/session.md b/guides/hosting/performance/session.md
index 421083fc88..5ff3acef07 100644
--- a/guides/hosting/performance/session.md
+++ b/guides/hosting/performance/session.md
@@ -51,15 +51,14 @@ To use one of these handlers, you must create a new service in the dependency in
 
 Example service definition:
 
-```xml
-<service id="session.db" class="Symfony\Component\HttpFoundation\Session\Storage\Handler\PdoSessionHandler">
-    <argument ....></argument>
-</service>
+```PHP
+$services->set('session.db', Symfony\Component\HttpFoundation\Session\Storage\Handler\PdoSessionHandler::class)
+    ->args([/* ... */]);
 ```
 
 Example session configuration:
 
-```yaml
+```YAML
 # config/packages/redis.yml
 framework:
     session:
diff --git a/guides/plugins/plugins/bundle.md b/guides/plugins/plugins/bundle.md
index d1ec4876b2..5a46e7f895 100644
--- a/guides/plugins/plugins/bundle.md
+++ b/guides/plugins/plugins/bundle.md
@@ -33,8 +33,8 @@ project-root/
 │       │   └── Migration1234567890YourMigration.php
 │       └── Resources/
 │           ├── config/
-│           │   ├── services.xml
-│           │   └── routes.xml
+│           │   ├── services.php
+│           │   └── routes.php
 │           ├── views/
 │           │   └── storefront/
 │           │       └── page/
@@ -67,7 +67,7 @@ If you don't need these features, you can use the Symfony bundle class instead.
 
 By default, The namespace `App\` is registered to the `src` folder in any Shopware project to be used for customizations. We recommend using this namespace, if you like to change the project structure, you can change the `App\` namespace in the `composer.json` file of your project.
 
-```php
+```PHP
 // <project root>/src/YourBundleName.php
 <?php declare(strict_types=1);
 
@@ -82,7 +82,7 @@ class YourBundleName extends Bundle
 
 The bundle class needs to be registered in the `config/bundles.php` file of your project.
 
-```php
+```PHP
 // <project root>/config/bundles.php
 //...
 App\YourBundleName\YourBundleName::class => ['all' => true],
@@ -92,7 +92,7 @@ App\YourBundleName\YourBundleName::class => ['all' => true],
 ## Adding services, twig templates, routes, theme, etc
 
 You can add services, twig templates, routes, etc. to your bundle like you would do in a plugin.
-Just create `Resources/config/services.xml` and `Resources/config/routes.xml` files or `Resources/views` for twig templates.
+Just create `Resources/config/services.php` and `Resources/config/routes.php` files or `Resources/views` for twig templates.
 The bundle will be automatically detected and the files will be loaded.
 
 To mark your bundle as a theme, it's enough to implement the `Shopware\Core\Framework\ThemeInterface` interface in your bundle class.
@@ -104,7 +104,7 @@ You can also add a `theme.json` file to define the theme configuration like [des
 Migrations are not automatically detected in bundles.
 To enable migrations, you need to overwrite the `build` method in your bundle class like this:
 
-```php
+```PHP
 // <project root>/src/YourBundleName.php
 <?php declare(strict_types=1);
 
@@ -126,13 +126,13 @@ class YourBundleName extends Bundle
 As Bundles don't have a lifecycle, the migrations are not automatically executed.
 You need to execute them manually via the console command:
 
-```bash
+```BASH
 bin/console database:migrate <BundleName> --all
 ```
 
 If you use [Deployment Helper](../../hosting/installation-updates/deployments/deployment-helper.md), you can add it to the `.shopware-project.yaml` file like this:
 
-```yaml
+```YAML
 deployment:
     hooks:
         pre-update: |
@@ -145,7 +145,7 @@ Shopware-CLI cannot detect bundles automatically, therefore the assets of the bu
 You will need to adjust the `composer.json` file of your project to specify the path to the bundle.
 This is done by adding the `extra` section to the `composer.json` file:
 
-```json
+```JSON
 {
     "extra": {
         "shopware-bundles": {
diff --git a/guides/plugins/plugins/checkout/cart/add-cart-discounts.md b/guides/plugins/plugins/checkout/cart/add-cart-discounts.md
index fa178d6693..653008631d 100644
--- a/guides/plugins/plugins/checkout/cart/add-cart-discounts.md
+++ b/guides/plugins/plugins/checkout/cart/add-cart-discounts.md
@@ -23,7 +23,7 @@ To add a discount to the cart, you should use the processor pattern. For this yo
 
 Let's start with the actual example code:
 
-```php
+```PHP
 // <plugin root>/src/Core/Checkout/ExampleProcessor.php
 <?php declare(strict_types=1);
 
@@ -120,4 +120,4 @@ Shopware comes with a called `LineItemRule`, which requires two parameters:
 
 After adding the definition to the line item, we have to calculate the current price of the discount. Therefore we can use the `PercentagePriceCalculator` of the core. The last step is to add the discount to the new cart which is provided as `Cart $toCalculate`.
 
-That's it for the main code of our custom `CartProcessor`. Now we only have to register it in our `services.xml` using the tag `shopware.cart.processor` and priority `4500`, which is used to get access to the calculation after the [product processor](https://github.com/shopware/shopware/blob/v6.3.4.1/src/Core/Checkout/DependencyInjection/cart.xml#L223-L231) handled the products.
+That's it for the main code of our custom `CartProcessor`. Now we only have to register it in our `services.php` using the tag `shopware.cart.processor` and priority `4500`, which is used to get access to the calculation after the [product processor](https://github.com/shopware/shopware/blob/v6.3.4.1/src/Core/Checkout/DependencyInjection/cart.xml#L223-L231) handled the products.
diff --git a/guides/plugins/plugins/checkout/cart/add-cart-items.md b/guides/plugins/plugins/checkout/cart/add-cart-items.md
index e2affd8092..2b38fd67ad 100644
--- a/guides/plugins/plugins/checkout/cart/add-cart-items.md
+++ b/guides/plugins/plugins/checkout/cart/add-cart-items.md
@@ -27,7 +27,7 @@ So let's add an example product to the cart using code. For that case, you'll ne
 
 Let's have a look at an example.
 
-```php
+```PHP
 // <plugin root>/src/Service/ExampleController.php
 <?php declare(strict_types=1);
 
@@ -100,24 +100,24 @@ Sometimes you really want to have a custom line item handler, e.g. for your own
 
 You need to create a new class which implements the interface `\Shopware\Core\Checkout\Cart\LineItemFactoryHandler\LineItemFactoryInterface` and it needs to be registered in the DI container with the tag `shopware.cart.line_item.factory`.
 
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\BasicExample\Service\ExampleHandler">
-            <tag name="shopware.cart.line_item.factory" />
-        </service>
-    </services>
-</container>
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+use Swag\BasicExample\Service\ExampleHandler;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(ExampleHandler::class)
+        ->tag('shopware.cart.line_item.factory');
+};
 ```
 
 Let's first have a look at an example handler:
 
-```php
+```PHP
 // <plugin root>/src/Service/ExampleHandler.php
 <?php declare(strict_types=1);
 
@@ -168,7 +168,7 @@ Implementing the `LineItemFactoryInterface` will force you to also implement thr
 
 Now you'll need to add a processor for your type. Otherwise your item won't be persisted in the cart. A simple processor for our ExampleHandler could look like this:
 
-```php
+```PHP
 // <plugin root>/Core/Checkout/Cart/ExampleProcessor.php
 <?php declare(strict_types=1);
 
@@ -199,17 +199,21 @@ As you can see, this processor takes an "original cart" as an input and adds all
 
 Of course you can use processors to do much more than this. Have a look at [adding cart processors and collectors](./add-cart-processor-collector).
 
-Now register this processor in your `services.xml` like this:
-
-```html
-// <plugin root>/Resources/config/services.xml
-...
-<services>
-    ...
-    <service id="Swag\BasicExample\Core\Checkout\Cart\ExampleProcessor">
-        <tag name="shopware.cart.processor" priority="4800"/>
-    </service>
-</services>
+Now register this processor in your `services.php` like this:
+
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+use Swag\BasicExample\Core\Checkout\Cart\ExampleProcessor;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(ExampleProcessor::class)
+        ->tag('shopware.cart.processor', ['priority' => 4800]);
+};
 ```
 
 And that's it. You should now be able to create line items of type `example`.
diff --git a/guides/plugins/plugins/checkout/cart/add-cart-validator.md b/guides/plugins/plugins/checkout/cart/add-cart-validator.md
index 940c78b434..0786daf1a9 100644
--- a/guides/plugins/plugins/checkout/cart/add-cart-validator.md
+++ b/guides/plugins/plugins/checkout/cart/add-cart-validator.md
@@ -35,7 +35,7 @@ Your validator has to implement the interface `Shopware\Core\Checkout\Cart\CartV
 
 But let's have a look at the example validator first:
 
-```php
+```PHP
 // <plugin root>/src/Core/Checkout/Cart/Custom/CustomCartValidator.php
 <?php declare(strict_types=1);
 
@@ -76,19 +76,19 @@ One more thing to do is to register your new validator to the [dependency inject
 
 Your validator has to be registered using the tag `shopware.cart.validator`:
 
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\BasicExample\Core\Checkout\Cart\Custom\CustomCartValidator">
-            <tag name="shopware.cart.validator"/>
-        </service>
-    </services>
-</container>
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Core\Checkout\Cart\Custom\CustomCartValidator;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(CustomCartValidator::class)
+        ->tag('shopware.cart.validator');
+};
 ```
 
 ### Adding the custom cart error
@@ -121,7 +121,7 @@ It has to extend from the abstract class `Shopware\Core\Checkout\Cart\Error\Erro
 
 So now let's have a look at the example error class:
 
-```php
+```PHP
 // <plugin root>/src/Core/Checkout/Cart/Custom/Error/CustomCartBlockedError.php
 <?php declare(strict_types=1);
 
@@ -182,7 +182,7 @@ You've defined the error key to be `custom-line-item-blocked` in your custom err
 
 Now let's have a look at an example snippet file:
 
-```javascript
+```JAVASCRIPT
 // <plugin root>/src/Resources/snippet/en\_GB/example.en-GB.json
 {
     "checkout": {
diff --git a/guides/plugins/plugins/checkout/cart/change-price-of-item.md b/guides/plugins/plugins/checkout/cart/change-price-of-item.md
index 49cbce65b6..e8e5afd795 100644
--- a/guides/plugins/plugins/checkout/cart/change-price-of-item.md
+++ b/guides/plugins/plugins/checkout/cart/change-price-of-item.md
@@ -39,7 +39,7 @@ Your collector class has to implement the interface `Shopware\Core\Checkout\Cart
 
 Let's have a look at an example:
 
-```php
+```PHP
 // <plugin root>/src/Core/Checkout/Cart/OverwritePriceCollector.php
 <?php declare(strict_types=1);
 
@@ -137,7 +137,7 @@ Your processor has to implement the interface `Shopware\Core\Checkout\Cart\CartP
 
 But once, again, let's have a look at the example:
 
-```php
+```PHP
 // <plugin root>/src/Core/Checkout/Cart/OverwritePriceCollector.php
 <?php declare(strict_types=1);
 
@@ -263,23 +263,27 @@ One last thing, we need to register our processor and collector to the DI contai
 
 Let's have a look at it:
 
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\BasicExample\Core\Checkout\Cart\OverwritePriceCollector">
-            <argument type="service" id="Shopware\Core\Checkout\Cart\Price\QuantityPriceCalculator"/>
-
-            <!-- after product collector/processor -->
-            <tag name="shopware.cart.processor" priority="4500" />
-            <tag name="shopware.cart.collector" priority="4500" />
-        </service>
-    </services>
-</container>
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Shopware\Core\Checkout\Cart\Price\QuantityPriceCalculator;
+use Swag\BasicExample\Core\Checkout\Cart\OverwritePriceCollector;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(OverwritePriceCollector::class)
+        ->args([
+            service(QuantityPriceCalculator::class),
+        ])
+        // after product collector/processor
+        ->tag('shopware.cart.processor', ['priority' => 4500])
+        ->tag('shopware.cart.collector', ['priority' => 4500]);
+};
 ```
 
 And that's it. Your processor / collector should now be working.
diff --git a/guides/plugins/plugins/checkout/cart/customize-price-calculation.md b/guides/plugins/plugins/checkout/cart/customize-price-calculation.md
index bca121a75a..ee20cdf03a 100644
--- a/guides/plugins/plugins/checkout/cart/customize-price-calculation.md
+++ b/guides/plugins/plugins/checkout/cart/customize-price-calculation.md
@@ -27,7 +27,7 @@ So let's do that real quick. If you're looking for an in-depth explanation, head
 
 Here's an example decorated calculator:
 
-```php
+```PHP
 // <plugin root>/src/Service/CustomProductPriceCalculator.php
 <?php declare(strict_types=1);
 
@@ -81,19 +81,25 @@ Most likely you also want to narrow down which product's prices you want to edit
 
 Do not forget to actually register your decoration to the service container, otherwise it will not have any effect.
 
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\BasicExample\Service\CustomProductPriceCalculator" decorates="Shopware\Core\Content\Product\SalesChannel\Price\ProductPriceCalculator">
-            <argument type="service" id="Swag\BasicExample\Service\CustomProductPriceCalculator.inner" />
-        </service>
-    </services>
-</container>
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Shopware\Core\Content\Product\SalesChannel\Price\ProductPriceCalculator;
+use Swag\BasicExample\Service\CustomProductPriceCalculator;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(CustomProductPriceCalculator::class)
+        ->decorate(ProductPriceCalculator::class)
+        ->args([
+            service('.inner'),
+        ]);
+};
 ```
 
 ## Next steps
diff --git a/guides/plugins/plugins/checkout/cart/tax-provider.md b/guides/plugins/plugins/checkout/cart/tax-provider.md
index 1823b921c4..d7076a09e8 100644
--- a/guides/plugins/plugins/checkout/cart/tax-provider.md
+++ b/guides/plugins/plugins/checkout/cart/tax-provider.md
@@ -23,7 +23,7 @@ Firstly you need to create a class which handles the tax calculation or calls yo
 
 You may then call a tax provider, which will calculate the taxes for you. For example, we simply apply a hefty 50% tax rate for all line-items in the cart.
 
-```php
+```PHP
 // <plugin root>/src/Checkout/Cart/Tax/TaxProvider.php
 <?php declare(strict_types=1);
 
@@ -83,21 +83,21 @@ class TaxProvider extends AbstractTaxProvider
 
 ## Registering the tax provider in the DI container
 
-After you have created your tax provider, you need to register it in the DI container. To do so, you need to create a new service in the `services.xml` file and tag the service as `shopware.tax.provider`.
+After you have created your tax provider, you need to register it in the DI container. To do so, you need to create a new service in the `services.php` file and tag the service as `shopware.tax.provider`.
 
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Checkout\Cart\Tax\TaxProvider;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
 
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
 
-    <services>
-        <service id="Swag\BasicExample\Checkout\Cart\Tax\TaxProvider">
-            <tag name="shopware.tax.provider" />
-        </service>
-    </services>
+    $services->set(TaxProvider::class)
+        ->tag('shopware.tax.provider');
+};
 ```
 
 ## Migrate your tax provider to the database
@@ -108,7 +108,7 @@ To let Shopware know of your new tax provider, you will have to persist it to th
 
 You may want to have a look at the [migration guide](../../plugin-fundamentals/database-migrations) to learn more about migrations.
 
-```php
+```PHP
 // <plugin root>/src/Migration/MigrationTaxProvider.php
 <?php declare(strict_types=1);
 
@@ -161,7 +161,7 @@ A good place for persisting your tax provider to the database would be the `inst
 
 If you do not know of plugin lifecycle methods yet, please refer to our [plugin lifecycle guide](../../plugin-fundamentals/plugin-lifecycle).
 
-```php
+```PHP
 // <plugin root>/src/BasicExample.php
 <?php declare(strict_types=1);
 
diff --git a/guides/plugins/plugins/checkout/document/add-custom-document-type.md b/guides/plugins/plugins/checkout/document/add-custom-document-type.md
index 0b4bafda5d..f448d64bf1 100644
--- a/guides/plugins/plugins/checkout/document/add-custom-document-type.md
+++ b/guides/plugins/plugins/checkout/document/add-custom-document-type.md
@@ -341,14 +341,20 @@ Here's what the function does:
 
 The service definition for our custom renderer would look like this:
 
-```xml
-<service id="Swag\BasicExample\Core\Checkout\Document\Render\ExampleDocumentRenderer">
-    <argument type="service" id="order.repository"/>
-    <argument type="service" id="Shopware\Core\Checkout\Document\Service\DocumentConfigLoader"/>
-    <argument type="service" id="Shopware\Core\System\NumberRange\ValueGenerator\NumberRangeValueGeneratorInterface"/>
-    <argument type="service" id="Shopware\Core\Checkout\Document\Service\DocumentFileRendererRegistry"/>
-    <tag name="document.renderer"/>
-</service>
+```PHP
+use Shopware\Core\Checkout\Document\Service\DocumentConfigLoader;
+use Shopware\Core\Checkout\Document\Service\DocumentFileRendererRegistry;
+use Shopware\Core\System\NumberRange\ValueGenerator\NumberRangeValueGeneratorInterface;
+use Swag\BasicExample\Core\Checkout\Document\Render\ExampleDocumentRenderer;
+
+$services->set(ExampleDocumentRenderer::class)
+    ->args([
+        service('order.repository'),
+        service(DocumentConfigLoader::class),
+        service(NumberRangeValueGeneratorInterface::class),
+        service(DocumentFileRendererRegistry::class),
+    ])
+    ->tag('document.renderer');
 ```
 
 ### Adding a file type renderer
@@ -358,26 +364,33 @@ Depending on the file type we either get the content with `$this->fileRendererRe
 
 ### Registering the renderer in the service container
 
-Now we need to register our custom `ExampleDocumentRenderer` in the service container. Create or update your `services.xml` file:
+Now we need to register our custom `ExampleDocumentRenderer` in the service container. Create or update your `services.php` file:
 
 ::: code-group
 
-```xml [PLUGIN_ROOT/src/Resources/config/services.xml]
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\BasicExample\Core\Checkout\Document\Render\ExampleDocumentRenderer">
-            <argument type="service" id="order.repository"/>
-            <argument type="service" id="Shopware\Core\Checkout\Document\Service\DocumentConfigLoader"/>
-            <argument type="service" id="Shopware\Core\System\NumberRange\ValueGenerator\NumberRangeValueGeneratorInterface"/>
-            <argument type="service" id="Shopware\Core\Checkout\Document\Service\DocumentFileRendererRegistry"/>
-            <tag name="document.renderer"/>
-        </service>
-    </services>
-</container>
+```PHP [PLUGIN_ROOT/src/Resources/config/services.php]
+<?php declare(strict_types=1);
+
+use Shopware\Core\Checkout\Document\Service\DocumentConfigLoader;
+use Shopware\Core\Checkout\Document\Service\DocumentFileRendererRegistry;
+use Shopware\Core\System\NumberRange\ValueGenerator\NumberRangeValueGeneratorInterface;
+use Swag\BasicExample\Core\Checkout\Document\Render\ExampleDocumentRenderer;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(ExampleDocumentRenderer::class)
+        ->args([
+            service('order.repository'),
+            service(DocumentConfigLoader::class),
+            service(NumberRangeValueGeneratorInterface::class),
+            service(DocumentFileRendererRegistry::class),
+        ])
+        ->tag('document.renderer');
+};
 ```
 
 :::
diff --git a/guides/plugins/plugins/checkout/payment/add-payment-plugin.md b/guides/plugins/plugins/checkout/payment/add-payment-plugin.md
index 4b515c128f..966ba95caf 100644
--- a/guides/plugins/plugins/checkout/payment/add-payment-plugin.md
+++ b/guides/plugins/plugins/checkout/payment/add-payment-plugin.md
@@ -39,19 +39,20 @@ Please make sure to add the `shopware.payment.method` tag to your service defini
 
 We'll use a class called `MyCustomPaymentHandler` here.
 
-```xml [<plugin root>/src/Resources/config/services.xml]
-<?xml version="1.0" ?>
-
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\PaymentPlugin\Service\MyCustomPaymentHandler">
-            <tag name="shopware.payment.method"/>
-        </service>
-    </services>
-</container>
+```PHP [<plugin root>/src/Resources/config/services.php]
+<?php declare(strict_types=1);
+
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+use Swag\PaymentPlugin\Service\MyCustomPaymentHandler;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(MyCustomPaymentHandler::class)
+        ->tag('shopware.payment.method');
+};
 ```
 
 Now, let's start with the actual examples.
@@ -116,20 +117,24 @@ class MyCustomPaymentHandler extends AbstractPaymentHandler
 }
 ```
 
-```xml [services.xml]
-<?xml version="1.0" ?>
+```PHP [services.php]
+<?php declare(strict_types=1);
+
+use Shopware\Core\Checkout\Order\Aggregate\OrderTransaction\OrderTransactionStateHandler;
+use Swag\PaymentPlugin\Service\MyCustomPaymentHandler;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
 
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
 
-    <services>
-        <service id="Swag\PaymentPlugin\Service\MyCustomPaymentHandler">
-            <tag name="shopware.payment.method"/>
-            <argument type="service" id="Shopware\Core\Checkout\Order\Aggregate\OrderTransaction\OrderTransactionStateHandler"/>
-        </service>
-    </services>
-</container>
+    $services->set(MyCustomPaymentHandler::class)
+        ->tag('shopware.payment.method')
+        ->args([
+            service(OrderTransactionStateHandler::class),
+        ]);
+};
 ```
 
 :::
@@ -227,20 +232,24 @@ class MyCustomPaymentHandler extends AbstractPaymentHandler
 }
 ```
 
-```xml [services.xml]
-<?xml version="1.0" ?>
+```PHP [services.php]
+<?php declare(strict_types=1);
+
+use Shopware\Core\Checkout\Order\Aggregate\OrderTransaction\OrderTransactionStateHandler;
+use Swag\PaymentPlugin\Service\MyCustomPaymentHandler;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
 
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
 
-    <services>
-        <service id="Swag\PaymentPlugin\Service\MyCustomPaymentHandler">
-            <tag name="shopware.payment.method"/>
-            <argument type="service" id="Shopware\Core\Checkout\Order\Aggregate\OrderTransaction\OrderTransactionStateHandler"/>
-        </service>
-    </services>
-</container>
+    $services->set(MyCustomPaymentHandler::class)
+        ->tag('shopware.payment.method')
+        ->args([
+            service(OrderTransactionStateHandler::class),
+        ]);
+};
 ```
 
 :::
@@ -350,7 +359,7 @@ class MyCustomPaymentHandler extends AbstractPaymentHandler
 
         // In here you should probably call your payment provider to precess the payment
         // $this->myPaymentProvider->processPayment($transaction);
-        
+
         // afterward you should update the transaction with the new state
         $this->transactionStateHandler->process($transaction->getOrderTransactionId(), $context);
 
@@ -359,20 +368,24 @@ class MyCustomPaymentHandler extends AbstractPaymentHandler
 }
 ```
 
-```xml [services.xml]
-<?xml version="1.0" ?>
+```PHP [services.php]
+<?php declare(strict_types=1);
+
+use Shopware\Core\Checkout\Order\Aggregate\OrderTransaction\OrderTransactionStateHandler;
+use Swag\PaymentPlugin\Service\MyCustomPaymentHandler;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
 
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
 
-    <services>
-        <service id="Swag\PaymentPlugin\Service\MyCustomPaymentHandler">
-            <tag name="shopware.payment.method"/>
-            <argument type="service" id="Shopware\Core\Checkout\Order\Aggregate\OrderTransaction\OrderTransactionStateHandler"/>
-        </service>
-    </services>
-</container>
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(MyCustomPaymentHandler::class)
+        ->tag('shopware.payment.method')
+        ->args([
+            service(OrderTransactionStateHandler::class),
+        ]);
+};
 ```
 
 :::
@@ -489,22 +502,27 @@ class MyCustomPaymentHandler extends AbstractPaymentHandler
 
 ```
 
-```xml [services.xml]
-<?xml version="1.0" ?>
-
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\PaymentPlugin\Service\MyCustomPaymentHandler">
-            <tag name="shopware.payment.method"/>
-            <argument type="service" id="order_transaction_capture_refund.repository"/>
-            <argument type="service" id="Shopware\Core\Checkout\Order\Aggregate\OrderTransaction\OrderTransactionStateHandler"/>
-            <argument type="service" id="Shopware\Core\Checkout\Order\Aggregate\OrderTransactionCapture\OrderTransactionCaptureStateHandler"/>
-        </service>
-    </services>
-</container>
+```PHP [services.php]
+<?php declare(strict_types=1);
+
+use Shopware\Core\Checkout\Order\Aggregate\OrderTransaction\OrderTransactionStateHandler;
+use Shopware\Core\Checkout\Order\Aggregate\OrderTransactionCapture\OrderTransactionCaptureStateHandler;
+use Swag\PaymentPlugin\Service\MyCustomPaymentHandler;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(MyCustomPaymentHandler::class)
+        ->tag('shopware.payment.method')
+        ->args([
+            service('order_transaction_capture_refund.repository'),
+            service(OrderTransactionStateHandler::class),
+            service(OrderTransactionCaptureStateHandler::class),
+        ]);
+};
 ```
 
 :::
@@ -567,16 +585,16 @@ class MyCustomPaymentHandler extends AbstractPaymentHandler
             // In here you should probably call your payment provider to create a billing agreement
             // $this->myPaymentProvider->createBillingAgreement($transaction);
         }
-        
+
         // Don't forget to capture the initial payment as well
         // $this->myPaymentProvider->processPayment($transaction);
-        
+
         // afterward you should update the transaction with the new state
         $this->transactionStateHandler->process($transaction->getOrderTransactionId(), $context);
 
         return null;
     }
-    
+
     /**
      * call your PSP here for capturing a recurring payment
      * a valid billing agreement between the customer and the PSP should usually already be in place
@@ -602,20 +620,24 @@ class MyCustomPaymentHandler extends AbstractPaymentHandler
 
 ```
 
-```xml [services.xml]
-<?xml version="1.0" ?>
+```PHP [services.php]
+<?php declare(strict_types=1);
+
+use Shopware\Core\Checkout\Order\Aggregate\OrderTransaction\OrderTransactionStateHandler;
+use Swag\PaymentPlugin\Service\MyCustomPaymentHandler;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
 
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
 
-    <services>
-        <service id="Swag\PaymentPlugin\Service\MyCustomPaymentHandler">
-            <tag name="shopware.payment.method"/>
-            <argument type="service" id="Shopware\Core\Checkout\Order\Aggregate\OrderTransaction\OrderTransactionStateHandler"/>
-        </service>
-    </services>
-</container>
+    $services->set(MyCustomPaymentHandler::class)
+        ->tag('shopware.payment.method')
+        ->args([
+            service(OrderTransactionStateHandler::class),
+        ]);
+};
 ```
 
 :::
@@ -695,7 +717,7 @@ class SwagBasicExample extends Plugin
             'name' => 'Example payment',
             'description' => 'Example payment description',
             'pluginId' => $pluginId,
-            // if true, payment method will also be available after the order 
+            // if true, payment method will also be available after the order
             // is created, e.g. if payment fails and the user wants to try again
             'afterOrderEnabled' => true,
             // the technicalName helps you to identify the payment method uniquely
@@ -784,27 +806,26 @@ Remove any other occurrences of the following tags:
 
 ::: code-group
 
-```xml [services.xml]
-<?xml version="1.0" ?>
-
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\PaymentPlugin\Service\MyCustomPaymentHandler">
-            <!-- this is the new tag for payment handlers -->
-            <tag name="shopware.payment.method"/>
-
-            <!-- remove any of these other tags -->
-            <tag name="shopware.payment.method.sync"/>
-            <tag name="shopware.payment.method.async"/>
-            <tag name="shopware.payment.method.prepared"/>
-            <tag name="shopware.payment.method.recurring"/>
-            <tag name="shopware.payment.method.refund"/>
-        </service>
-    </services>
-</container>
+```PHP [services.php]
+<?php declare(strict_types=1);
+
+use Swag\PaymentPlugin\Service\MyCustomPaymentHandler;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(MyCustomPaymentHandler::class)
+        // this is the new tag for payment handlers
+        ->tag('shopware.payment.method')
+
+        // remove any of these other tags
+        ->tag('shopware.payment.method.sync')
+        ->tag('shopware.payment.method.async')
+        ->tag('shopware.payment.method.prepared')
+        ->tag('shopware.payment.method.recurring')
+        ->tag('shopware.payment.method.refund');
+};
 ```
 
 :::
diff --git a/guides/plugins/plugins/checkout/payment/customize-payment-provider.md b/guides/plugins/plugins/checkout/payment/customize-payment-provider.md
index 486d7e2d17..053df4eb54 100644
--- a/guides/plugins/plugins/checkout/payment/customize-payment-provider.md
+++ b/guides/plugins/plugins/checkout/payment/customize-payment-provider.md
@@ -24,7 +24,7 @@ First, we create a new class that extends from the provider we want to customise
 In this example we customise the class `Shopware\Core\Checkout\Payment\Cart\PaymentHandler\DebitPayment` and name our class `ExampleDebitPayment`.
 The constructor has to accept an instance of `OrderTransactionStateHandler` like the original service and additionally an instance of `DebitPayment` that we want to decorate.
 
-After we've created our customized payment provider class, we have to register it to the DI-container via the `services.xml`.
+After we've created our customized payment provider class, we have to register it to the DI-container via the `services.php`.
 
 ::: code-group
 
@@ -66,20 +66,26 @@ class ExampleDebitPayment extends DebitPayment
 }
 ```
 
-```xml [services.xml]
-<?xml version="1.0" ?>
+```PHP [services.php]
+<?php declare(strict_types=1);
+
+use Shopware\Core\Checkout\Order\Aggregate\OrderTransaction\OrderTransactionStateHandler;
+use Shopware\Core\Checkout\Payment\Cart\PaymentHandler\DebitPayment;
+use Swag\BasicExample\Service\ExampleDebitPayment;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
 
-<container xmlns="http://symfony.com/schema/dic/services"
-xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
 
-    <services>
-        <service id="Swag\BasicExample\Service\ExampleDebitPayment" decorates="Shopware\Core\Checkout\Payment\Cart\PaymentHandler\DebitPayment">
-            <argument type="service" id="Shopware\Core\Checkout\Order\Aggregate\OrderTransaction\OrderTransactionStateHandler"/>
-            <argument type="service" id="Swag\BasicExample\Service\ExampleDebitPayment.inner"/>
-        </service>
-    </services>
-</container>
+    $services->set(ExampleDebitPayment::class)
+        ->decorate(DebitPayment::class)
+        ->args([
+            service(OrderTransactionStateHandler::class),
+            service('.inner'),
+        ]);
+};
 ```
 
 :::
diff --git a/guides/plugins/plugins/content/cms/add-data-to-cms-elements.md b/guides/plugins/plugins/content/cms/add-data-to-cms-elements.md
index b90d11d5fd..dd2a3f49f4 100644
--- a/guides/plugins/plugins/content/cms/add-data-to-cms-elements.md
+++ b/guides/plugins/plugins/content/cms/add-data-to-cms-elements.md
@@ -23,7 +23,7 @@ so head over to the official guide about [Adding a custom CMS element](add-cms-e
 To manipulate the data of these elements during the loading of the configuration,
 we create a `DailyMotionCmsElementResolver` resolver in our plugin.
 
-```php
+```PHP
 // <plugin root>/src/DataResolver/DailyMotionCmsElementResolver.php
 <?php declare(strict_types=1);
 
@@ -60,23 +60,22 @@ In the previous [example](add-cms-element) we added a CMS element with the name
 As you can see the `getType` method of our custom resolver reflects that name by returning the `dailymotion` string.
 This resolver is called every time for an element of the type `dailymotion`.
 
-To register our custom resolver to the service container, we have to register it in the `services.xml` file in our plugin.
+To register our custom resolver to the service container, we have to register it in the `services.php` file in our plugin.
 
 ::: code-group
 
-```xml [PLUGIN_ROOT/src/Resources/config/services.xml]
-<?xml version="1.0" ?>
+```PHP [PLUGIN_ROOT/src/Resources/config/services.php]
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\DataResolver\DailyMotionCmsElementResolver;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
 
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
 
-    <services>
-        <service id="Swag\BasicExample\DataResolver\DailyMotionCmsElementResolver">
-            <tag name="shopware.cms.data_resolver" />
-        </service>
-    </services>
-</container>
+    $services->set(DailyMotionCmsElementResolver::class)
+        ->tag('shopware.cms.data_resolver');
+};
 ```
 
 :::
diff --git a/guides/plugins/plugins/content/mail/add-data-to-mails.md b/guides/plugins/plugins/content/mail/add-data-to-mails.md
index cf117e5c11..18990cda55 100644
--- a/guides/plugins/plugins/content/mail/add-data-to-mails.md
+++ b/guides/plugins/plugins/content/mail/add-data-to-mails.md
@@ -78,22 +78,28 @@ If we add <code v-pre>{{ myCustomData }}</code> to any mail template, it should
 
 Of course you still have to register the decoration to the service container. Beware of the `decorates` attribute of our service.
 
-Here's the respective example `services.xml`:
+Here's the respective example `services.php`:
 
 ::: code-group
 
-```xml [PLUGIN_ROOT/src/Resources/config/services.xml]
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\BasicExample\Service\AddDataToMails" decorates="Shopware\Core\Content\Mail\Service\MailService">
-            <argument type="service" id="Swag\BasicExample\Service\AddDataToMails.inner" />
-        </service>
-    </services>
-</container>
+```PHP [PLUGIN_ROOT/src/Resources/config/services.php]
+<?php declare(strict_types=1);
+
+use Shopware\Core\Content\Mail\Service\MailService;
+use Swag\BasicExample\Service\AddDataToMails;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(AddDataToMails::class)
+        ->decorate(MailService::class)
+        ->args([
+            service('.inner'),
+        ]);
+};
 ```
 
 :::
@@ -142,22 +148,22 @@ class MyMailSubscriber implements EventSubscriberInterface
 
 You have to register the subscriber to the service container as well.
 
-Here's the respective example `services.xml`:
+Here's the respective example `services.php`:
 
 ::: code-group
 
-```xml [PLUGIN_ROOT/src/Resources/config/services.xml]
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\BasicExample\Subscriber\MyMailSubscriber">
-            <tag name="kernel.event_subscriber"/>
-        </service>
-    </services>
-</container>
+```PHP [PLUGIN_ROOT/src/Resources/config/services.php]
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Subscriber\MyMailSubscriber;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(MyMailSubscriber::class)
+        ->tag('kernel.event_subscriber');
+};
 ```
 
 :::
diff --git a/guides/plugins/plugins/content/media/add-custom-file-extension.md b/guides/plugins/plugins/content/media/add-custom-file-extension.md
index ba4a44f79f..6eb0379217 100644
--- a/guides/plugins/plugins/content/media/add-custom-file-extension.md
+++ b/guides/plugins/plugins/content/media/add-custom-file-extension.md
@@ -31,7 +31,7 @@ This is of course done via a [subscriber](../../plugin-fundamentals/listening-to
 
 Have a look at the following code example:
 
-```php
+```PHP
 // <plugin root>/src/Service/Subscriber.php
 <?php declare(strict_types=1);
 
@@ -83,7 +83,7 @@ Have a look at the following example:
 <Tabs>
 <Tab title="CustomImageTypeDetector.php">
 
-```php
+```PHP
 // <plugin root>/src/Core/Content/Media/TypeDetector/CustomImageTypeDetector.php
 <?php declare(strict_types=1);
 
@@ -120,21 +120,21 @@ class CustomImageTypeDetector implements TypeDetectorInterface
 
 </Tab>
 
-<Tab title="services.xml">
-
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\BasicExample\Core\Content\Media\TypeDetector\CustomImageTypeDetector">
-            <tag name="shopware.media_type.detector" priority="10"/>
-        </service>
-    </services>
-</container>
+<Tab title="services.php">
+
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Core\Content\Media\TypeDetector\CustomImageTypeDetector;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(CustomImageTypeDetector::class)
+        ->tag('shopware.media_type.detector', ['priority' => 10]);
+};
 ```
 
 </Tab>
diff --git a/guides/plugins/plugins/content/media/prevent-deletion-of-media-files-referenced-in-your-plugins.md b/guides/plugins/plugins/content/media/prevent-deletion-of-media-files-referenced-in-your-plugins.md
index 9dc1f3be32..9bfb6866c8 100644
--- a/guides/plugins/plugins/content/media/prevent-deletion-of-media-files-referenced-in-your-plugins.md
+++ b/guides/plugins/plugins/content/media/prevent-deletion-of-media-files-referenced-in-your-plugins.md
@@ -44,7 +44,7 @@ In this section, we're going to register a subscriber for the `\Shopware\Core\Co
 
 Have a look at the following code example:
 
-```php
+```PHP
 // <plugin root>/src/Subscriber/UnusedMediaSubscriber.php
 <?php declare(strict_types=1);
 
@@ -89,7 +89,7 @@ If your storage is a relational database such as MySQL you should, when possible
 
 Imagine an extension which provides an image slider feature. An implementation of `getUsedMediaIds` might look something like the following:
 
-```php
+```PHP
 // <plugin root>/src/Subscriber/UnusedMediaSubscriber.php
 private function getUsedMediaIds(array $idsToBeDeleted): array
 {
@@ -121,21 +121,21 @@ Make sure to register your event subscriber to the [Dependency injection contain
 by using the tag `kernel.event_subscriber`.
 
 <Tabs>
-<Tab title="services.xml">
-
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\BasicExample\Subscriber\UnusedMediaSubscriber">
-            <tag name="kernel.event_subscriber"/>
-        </service>
-    </services>
-</container>
+<Tab title="services.php">
+
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Subscriber\UnusedMediaSubscriber;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(UnusedMediaSubscriber::class)
+        ->tag('kernel.event_subscriber');
+};
 ```
 
 </Tab>
diff --git a/guides/plugins/plugins/content/seo/add-custom-seo-url.md b/guides/plugins/plugins/content/seo/add-custom-seo-url.md
index 6e5f0cca55..e775db07a4 100644
--- a/guides/plugins/plugins/content/seo/add-custom-seo-url.md
+++ b/guides/plugins/plugins/content/seo/add-custom-seo-url.md
@@ -40,7 +40,7 @@ For this example, the controller from the [Add custom controller guide](../../st
 
 Let's now have a look at our example controller:
 
-```php
+```PHP
 // <plugin root>/src/Storefront/Controller/ExampleController.php
 <?php declare(strict_types=1);
 
@@ -79,7 +79,7 @@ Don't be confused here, we'll just treat the `seo_url` table like a translation
 
 Let's have a look at an example:
 
-```php
+```PHP
 // <plugin root>/src/Migration/Migration1619094740AddStaticSeoUrl.php
 <?php declare(strict_types=1);
 
@@ -179,7 +179,7 @@ Let's first have a look at such an example class:
 <Tabs>
 <Tab title="ExamplePageSeoUrlRoute.php">
 
-```php
+```PHP
 // <plugin root>/src/Storefront/Framework/Seo/SeoUrlRoute/ExamplePageSeoUrlRoute.php
 <?php declare(strict_types=1);
 
@@ -241,23 +241,27 @@ class ExamplePageSeoUrlRoute implements SeoUrlRouteInterface
 
 </Tab>
 
-<Tab title="services.xml">
+<Tab title="services.php">
 
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Core\Content\Example\ExampleDefinition;
+use Swag\BasicExample\Storefront\Framework\Seo\SeoUrlRoute\ExamplePageSeoUrlRoute;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
 
-    <services>
-        <service id="Swag\BasicExample\Storefront\Framework\Seo\SeoUrlRoute\ExamplePageSeoUrlRoute">
-            <argument type="service" id="Swag\BasicExample\Core\Content\Example\ExampleDefinition"/>
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
 
-            <tag name="shopware.seo_url.route"/>
-        </service>
-    </services>
-</container>
+    $services->set(ExamplePageSeoUrlRoute::class)
+        ->args([
+            service(ExampleDefinition::class),
+        ])
+        ->tag('shopware.seo_url.route');
+};
 ```
 
 </Tab>
@@ -300,7 +304,7 @@ Once again, let's have a look at an example subscriber here:
 <Tabs>
 <Tab title="DynamicSeoUrlPageSubscriber.php">
 
-```php
+```PHP
 // <plugin root>/src/Service/DynamicSeoUrlPageSubscriber.php
 <?php declare(strict_types=1);
 
@@ -335,24 +339,27 @@ class DynamicSeoUrlPageSubscriber implements EventSubscriberInterface
 
 </Tab>
 
-<Tab title="services.xml">
+<Tab title="services.php">
+
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Shopware\Core\Content\Seo\SeoUrlUpdater;
+use Swag\BasicExample\Service\DynamicSeoUrlPageSubscriber;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
 
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
 
-    <services>
-        <!-- ... -->
-        <service id="Swag\BasicExample\Service\DynamicSeoUrlPageSubscriber" >
-            <argument type="service" id="Shopware\Core\Content\Seo\SeoUrlUpdater" />
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
 
-            <tag name="kernel.event_subscriber" />
-        </service>
-    </services>
-</container>
+    $services->set(DynamicSeoUrlPageSubscriber::class)
+        ->args([
+            service(SeoUrlUpdater::class),
+        ])
+        ->tag('kernel.event_subscriber');
+};
 ```
 
 </Tab>
@@ -374,7 +381,7 @@ The most important values you'll have to set in the migration are:
 
 Now here is the said example migration:
 
-```php
+```PHP
 // <plugin root>/src/Migration/Migration1619514731AddExampleSeoUrlTemplate.php
 <?php declare(strict_types=1);
 
@@ -423,7 +430,7 @@ If your entity is deleted, you want the SEO URL to be updated as well. In detail
 
 This can be achieved by using the DAL event `.deleted` and then executing the `update` method again.
 
-```php
+```PHP
 // <plugin root>/src/Service/DynamicSeoUrlPageSubscriber.php
 <?php declare(strict_types=1);
 
@@ -470,7 +477,7 @@ This method will then use the `SeoUrlPersister` and its method `updateSeoUrls` i
 
 Here's an example of such a class:
 
-```php
+```PHP
 // <plugin root>/src/Service/DynamicSeoUrlsService.php
 <?php declare(strict_types=1);
 
@@ -558,7 +565,7 @@ It will then use the built array and all of the other information like the conte
 
 If your custom dynamic content is deleted, you have to set the column `is_deleted` to `1` of the respective `seo_url` entry. This can be achieved with a new method, in this example we'll call it `deleteSeoEntries`. It will receive an array of IDs to be deleted. Those IDs have to match the value of the column `foreign_key` in the `seo_url` table. Also it needs the current context. It will take care of setting the generated SEO URLs to `deleted`. It will **not** delete an entry from the table `seo_url`.
 
-```php
+```PHP
 public function deleteSeoEntries(array $ids, Context $context): void
 {
     $this->seoUrlPersister->updateSeoUrls($context, self::ROUTE_NAME, $ids, []);
@@ -571,7 +578,7 @@ This way the respective SEO URLs will be marked as `is_deleted` for the system.
 
 In the example mentioned above, we're just using a `Context` instance, for whichever language that is. You can be more specific here though, in order to properly define the language ID yourself here and therefore ensuring it is written for the right language.
 
-```php
+```PHP
 $context = new Context(
     $event->getContext()->getSource(),
     $event->getContext()->getRuleIds(),
diff --git a/guides/plugins/plugins/content/seo/extend-robots-txt.md b/guides/plugins/plugins/content/seo/extend-robots-txt.md
index 83abac59e5..e16c81efde 100644
--- a/guides/plugins/plugins/content/seo/extend-robots-txt.md
+++ b/guides/plugins/plugins/content/seo/extend-robots-txt.md
@@ -91,21 +91,26 @@ class RobotsExtensionListener
 
 </Tab>
 
-<Tab title="services.xml">
-
-```XML
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\Example\Listener\RobotsExtensionListener">
-            <argument type="service" id="logger"/>
-            <tag name="kernel.event_listener" event="Shopware\Storefront\Page\Robots\Event\RobotsDirectiveParsingEvent"/>
-        </service>
-    </services>
-</container>
+<Tab title="services.php">
+
+```PHP
+<?php declare(strict_types=1);
+
+use Shopware\Storefront\Page\Robots\Event\RobotsDirectiveParsingEvent;
+use Swag\Example\Listener\RobotsExtensionListener;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(RobotsExtensionListener::class)
+        ->args([
+            service('logger'),
+        ])
+        ->tag('kernel.event_listener', ['event' => RobotsDirectiveParsingEvent::class]);
+};
 ```
 
 </Tab>
@@ -143,20 +148,21 @@ class CustomDirectiveListener
 
 </Tab>
 
-<Tab title="services.xml">
+<Tab title="services.php">
+
+```PHP
+<?php declare(strict_types=1);
 
-```XML
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+use Shopware\Storefront\Page\Robots\Event\RobotsUnknownDirectiveEvent;
+use Swag\Example\Listener\CustomDirectiveListener;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
 
-    <services>
-        <service id="Swag\Example\Listener\CustomDirectiveListener">
-            <tag name="kernel.event_listener" event="Shopware\Storefront\Page\Robots\Event\RobotsUnknownDirectiveEvent"/>
-        </service>
-    </services>
-</container>
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(CustomDirectiveListener::class)
+        ->tag('kernel.event_listener', ['event' => RobotsUnknownDirectiveEvent::class]);
+};
 ```
 
 </Tab>
@@ -243,20 +249,21 @@ class RobotsValidationListener
 
 </Tab>
 
-<Tab title="services.xml">
+<Tab title="services.php">
+
+```PHP
+<?php declare(strict_types=1);
+
+use Shopware\Storefront\Page\Robots\Event\RobotsDirectiveParsingEvent;
+use Swag\Example\Listener\RobotsValidationListener;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
 
-```XML
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
 
-    <services>
-        <service id="Swag\Example\Listener\RobotsValidationListener">
-            <tag name="kernel.event_listener" event="Shopware\Storefront\Page\Robots\Event\RobotsDirectiveParsingEvent"/>
-        </service>
-    </services>
-</container>
+    $services->set(RobotsValidationListener::class)
+        ->tag('kernel.event_listener', ['event' => RobotsDirectiveParsingEvent::class]);
+};
 ```
 
 </Tab>
diff --git a/guides/plugins/plugins/content/sitemap/add-custom-sitemap-entries.md b/guides/plugins/plugins/content/sitemap/add-custom-sitemap-entries.md
index 437eacc8ed..ef34b128b5 100644
--- a/guides/plugins/plugins/content/sitemap/add-custom-sitemap-entries.md
+++ b/guides/plugins/plugins/content/sitemap/add-custom-sitemap-entries.md
@@ -67,7 +67,7 @@ Let's have a look at the example class:
 <Tabs>
 <Tab title="CustomUrlProvider.php">
 
-```php
+```PHP
 // <plugin root>/src/Core/Content/Sitemap/Provider/CustomUrlProvider.php
 <?php declare(strict_types=1);
 
@@ -168,25 +168,29 @@ class CustomUrlProvider extends AbstractUrlProvider
 
 </Tab>
 
-<Tab title="services.xml">
-
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\BasicExample\Core\Content\Sitemap\Provider\CustomUrlProvider" >
-            <argument type="service" id="swag_example.repository" />
-            <argument type="service" id="Doctrine\DBAL\Connection"/>
-            <argument type="service" id="router"/>
-
-            <tag name="shopware.sitemap_url_provider" />
-        </service>
-    </services>
-</container>
+<Tab title="services.php">
+
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Doctrine\DBAL\Connection;
+use Swag\BasicExample\Core\Content\Sitemap\Provider\CustomUrlProvider;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(CustomUrlProvider::class)
+        ->args([
+            service('swag_example.repository'),
+            service(Connection::class),
+            service('router'),
+        ])
+        ->tag('shopware.sitemap_url_provider');
+};
 ```
 
 </Tab>
diff --git a/guides/plugins/plugins/content/sitemap/modify-sitemap-entries.md b/guides/plugins/plugins/content/sitemap/modify-sitemap-entries.md
index 6e1bebdf1a..3eca0bfb1f 100644
--- a/guides/plugins/plugins/content/sitemap/modify-sitemap-entries.md
+++ b/guides/plugins/plugins/content/sitemap/modify-sitemap-entries.md
@@ -39,7 +39,7 @@ Start by decorating the corresponding URL provider, for example
 <Tabs>
 <Tab title="DecoratedProductUrlProvider.php">
 
-```php
+```PHP
 // <plugin root>/src/Core/Content/Sitemap/Provider/DecoratedProductUrlProvider.php
 <?php declare(strict_types=1);
 
@@ -94,22 +94,27 @@ class DecoratedProductUrlProvider extends AbstractUrlProvider
 
 </Tab>
 
-<Tab title="services.xml">
-
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\BasicExample\Core\Content\Sitemap\Provider\DecoratedProductUrlProvider"
-                 decorates="Shopware\Core\Content\Sitemap\Provider\ProductUrlProvider">
-            <argument type="service" id="Swag\BasicExample\Core\Content\Sitemap\Provider\DecoratedProductUrlProvider.inner" />
-        </service>
-    </services>
-</container>
+<Tab title="services.php">
+
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Shopware\Core\Content\Sitemap\Provider\ProductUrlProvider;
+use Swag\BasicExample\Core\Content\Sitemap\Provider\DecoratedProductUrlProvider;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(DecoratedProductUrlProvider::class)
+        ->decorate(ProductUrlProvider::class)
+        ->args([
+            service('.inner'),
+        ]);
+};
 ```
 
 </Tab>
@@ -133,7 +138,7 @@ This is the recommended extension point when you need to:
 <Tabs>
 <Tab title="ProductSitemapQuerySubscriber.php">
 
-```php
+```PHP
 // <plugin root>/src/Core/Content/Sitemap/ProductSitemapQuerySubscriber.php
 <?php declare(strict_types=1);
 
@@ -169,21 +174,21 @@ class ProductSitemapQuerySubscriber implements EventSubscriberInterface
 
 </Tab>
 
-<Tab title="services.xml">
-
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\BasicExample\Core\Content\Sitemap\ProductSitemapQuerySubscriber">
-            <tag name="kernel.event_subscriber" />
-        </service>
-    </services>
-</container>
+<Tab title="services.php">
+
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Core\Content\Sitemap\ProductSitemapQuerySubscriber;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(ProductSitemapQuerySubscriber::class)
+        ->tag('kernel.event_subscriber');
+};
 ```
 
 </Tab>
diff --git a/guides/plugins/plugins/content/stock/implementing-your-own-stock-storage.md b/guides/plugins/plugins/content/stock/implementing-your-own-stock-storage.md
index bab281f2c3..a22c267789 100644
--- a/guides/plugins/plugins/content/stock/implementing-your-own-stock-storage.md
+++ b/guides/plugins/plugins/content/stock/implementing-your-own-stock-storage.md
@@ -26,7 +26,7 @@ First, to communicate stock alterations to a third-party service, you will have
 <Tabs>
 <Tab title="StockStorageDecorator.php">
 
-```php
+```PHP
 // <plugin root>/src/Swag/Example/Service/StockStorageDecorator.php
 <?php declare(strict_types=1);
 
@@ -77,21 +77,27 @@ class StockStorageDecorator extends AbstractStockStorage
 
 </Tab>
 
-<Tab title="services.xml">
-
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\Example\Service\StockStorageDecorator" decorates="Shopware\Core\Content\Product\Stock\StockStorage">
-            <argument type="service" id="Swag\Example\Service\StockStorageDecorator.inner" />
-        </service>
-    </services>
-</container>
+<Tab title="services.php">
+
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Shopware\Core\Content\Product\Stock\StockStorage;
+use Swag\Example\Service\StockStorageDecorator;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(StockStorageDecorator::class)
+        ->decorate(StockStorage::class)
+        ->args([
+            service('.inner'),
+        ]);
+};
 ```
 
 </Tab>
diff --git a/guides/plugins/plugins/content/stock/loading-stock-information-from-different-source.md b/guides/plugins/plugins/content/stock/loading-stock-information-from-different-source.md
index 95c89e4ae4..3e04015605 100644
--- a/guides/plugins/plugins/content/stock/loading-stock-information-from-different-source.md
+++ b/guides/plugins/plugins/content/stock/loading-stock-information-from-different-source.md
@@ -22,7 +22,7 @@ For example, to load stock from a third-party API, you need to decorate `\Shopwa
 <Tabs>
 <Tab title="StockStorageDecorator.php">
 
-```php
+```PHP
 // <plugin root>/src/Swag/Example/Service/StockStorageDecorator.php
 <?php declare(strict_types=1);
 
@@ -75,21 +75,27 @@ class StockStorageDecorator extends AbstractStockStorage
 
 </Tab>
 
-<Tab title="services.xml">
-
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\Example\Service\StockStorageDecorator" decorates="Shopware\Core\Content\Product\Stock\StockStorage">
-            <argument type="service" id="Swag\Example\Service\StockStorageDecorator.inner" />
-        </service>
-    </services>
-</container>
+<Tab title="services.php">
+
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Shopware\Core\Content\Product\Stock\StockStorage;
+use Swag\Example\Service\StockStorageDecorator;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(StockStorageDecorator::class)
+        ->decorate(StockStorage::class)
+        ->args([
+            service('.inner'),
+        ]);
+};
 ```
 
 </Tab>
@@ -114,7 +120,7 @@ There are several required values and some optional values.
 
 For example:
 
-```php
+```PHP
 $stockData = \Shopware\Core\Content\Product\Stock\StockData::fromArray([
     'productId' => 'product-1',
     'stock' => 5,
@@ -127,7 +133,7 @@ $stockData = \Shopware\Core\Content\Product\Stock\StockData::fromArray([
 
 It is also possible to provide arbitrary data via extensions:
 
-```php
+```PHP
 $stockData = \Shopware\Core\Content\Product\Stock\StockData::fromArray([
     'productId' => 'product-1',
     'stock' => 5,
@@ -139,6 +145,6 @@ $stockData->addArrayExtension('extraData', ['foo' => 'bar']);
 
 The values in the `StockData` instance will be used to update the loaded product instance. Furthermore, fetching the `StockData` instance from the product via the `stock_data` extension is possible. For example:
 
-```php
+```PHP
 $stockData = $product->getExtension('stock_data');
 ```
diff --git a/guides/plugins/plugins/elasticsearch/add-product-entity-extension-to-elasticsearch.md b/guides/plugins/plugins/elasticsearch/add-product-entity-extension-to-elasticsearch.md
index 74627021c4..40f10c5da6 100644
--- a/guides/plugins/plugins/elasticsearch/add-product-entity-extension-to-elasticsearch.md
+++ b/guides/plugins/plugins/elasticsearch/add-product-entity-extension-to-elasticsearch.md
@@ -23,44 +23,49 @@ We will extend the product extension with an `OneToOneAssociationField` and `One
 To extend the elasticsearch definition we need to extend the product definition first and add the subscriber. This is described in the above mentioned articles.
 Here we show you how this could look like in the end.
 
-The service.xml with all needed definitions.
-
-```xml
-// <plugin root>/src/Core/Content/DependencyInjection/product.xml
-<?xml version="1.0" ?>
-
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\BasicExample\Extension\Content\Product\CustomExtension">
-            <tag name="shopware.entity.extension"/>
-        </service>
-
-        <service id="Swag\BasicExample\Extension\Content\Product\OneToOneExampleExtensionDefinition">
-            <tag name="shopware.entity.definition" entity="one_to_one_swag_example_extension" />
-        </service>
-
-        <service id="Swag\BasicExample\Extension\Content\Product\OneToManyExampleExtensionDefinition">
-            <tag name="shopware.entity.definition" entity="one_to_many_swag_example_extension" />
-        </service>
-
-        <service id="Swag\BasicExample\Subscriber\ProductSubscriber">
-            <tag name="kernel.event_subscriber"/>
-        </service>
-
-        <service id="Swag\BasicExample\Elasticsearch\Product\MyProductEsDecorator" decorates="Shopware\Elasticsearch\Product\ElasticsearchProductDefinition">
-            <argument type="service" id="Swag\BasicExample\Elasticsearch\Product\MyProductEsDecorator.inner"/>
-            <argument type="service" id="Doctrine\DBAL\Connection"/>
-        </service>
-    </services>
-</container>
+The services.php with all needed definitions.
+
+```PHP
+// <plugin root>/src/Core/Content/DependencyInjection/product.php
+<?php declare(strict_types=1);
+
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+use Swag\BasicExample\Extension\Content\Product\CustomExtension;
+use Swag\BasicExample\Extension\Content\Product\OneToOneExampleExtensionDefinition;
+use Swag\BasicExample\Extension\Content\Product\OneToManyExampleExtensionDefinition;
+use Swag\BasicExample\Subscriber\ProductSubscriber;
+use Swag\BasicExample\Elasticsearch\Product\MyProductEsDecorator;
+use Shopware\Elasticsearch\Product\ElasticsearchProductDefinition;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(CustomExtension::class)
+        ->tag('shopware.entity.extension');
+
+    $services->set(OneToOneExampleExtensionDefinition::class)
+        ->tag('shopware.entity.definition', ['entity' => 'one_to_one_swag_example_extension']);
+
+    $services->set(OneToManyExampleExtensionDefinition::class)
+        ->tag('shopware.entity.definition', ['entity' => 'one_to_many_swag_example_extension']);
+
+    $services->set(ProductSubscriber::class)
+        ->tag('kernel.event_subscriber');
+
+    $services->set(MyProductEsDecorator::class)
+        ->decorate(ElasticsearchProductDefinition::class)
+        ->args([
+            service(MyProductEsDecorator::class . '.inner'),
+            service(\Doctrine\DBAL\Connection::class),
+        ]);
+};
 ```
 
 The product extension `CustomExtension.php` provides the extensions to the product entity.
 
-```php
+```PHP
 // <plugin root>/src/Extension/Content/Product/CustomExtension.php
 <?php declare(strict_types=1);
 
@@ -101,7 +106,7 @@ class CustomExtension extends EntityExtension
 
 The entity definition `OneToManyExampleExtensionDefinition.php`.
 
-```php
+```PHP
 // <plugin root>/src/Extension/Content/Product/OneToManyExampleExtensionDefinition.php
 <?php declare(strict_types=1);
 
@@ -150,7 +155,7 @@ class OneToManyExampleExtensionDefinition extends EntityDefinition
 
 The entity definition `OneToOneExampleExtensionDefinition.php`.
 
-```php
+```PHP
 // <plugin root>/src/Extension/Content/Product/OneToOneExampleExtensionDefinition.php
 <?php declare(strict_types=1);
 
@@ -200,7 +205,7 @@ class OneToOneExampleExtensionDefinition extends EntityDefinition
 Here is a decoration to add a new field named `customString`, an `oneToOneAssociationField` named `oneToOneExampleExtension` and an `oneToManyAssociationField` named `oneToManyExampleExtension` to the index.
 For adding more information from the database you should execute a single query with all document ids `(array_column($documents, 'id'))` and map the values.
 
-```php
+```PHP
 // <plugin root>/src/Elasticsearch/Product/MyProductEsDecorator.php
 <?php
 
diff --git a/guides/plugins/plugins/framework/custom-field/add-custom-field.md b/guides/plugins/plugins/framework/custom-field/add-custom-field.md
index 46a8a796e7..1ffcfaf36c 100644
--- a/guides/plugins/plugins/framework/custom-field/add-custom-field.md
+++ b/guides/plugins/plugins/framework/custom-field/add-custom-field.md
@@ -44,7 +44,7 @@ Also, you may want to add translatable custom fields, which is also covered in v
 
 Let's assume you already got a working and running entity definition. If you want to support custom fields with your custom entity, you may add the `EntityCustomFieldsTrait` to your entity class, so the methods `getCustomFields()` and `setCustomFields()` can be used.
 
-```php
+```PHP
 // <plugin root>/src/Core/Content/Example/ExampleEntity.php
 use Shopware\Core\Framework\DataAbstractionLayer\Entity;
 use Shopware\Core\Framework\DataAbstractionLayer\EntityCustomFieldsTrait;
@@ -65,9 +65,9 @@ class ExampleEntity extends Entity
 
 Now follows the important part. For this to work, you have to add the Data Abstraction Layer \(DAL\) field `CustomFields` to your entity definition.
 
-```php
+```PHP
 // <plugin root>/src/Core/Content/Example/ExampleDefinition.php
-use Shopware\Core\Framework\DataAbstractionLayer\Field\CustomFields;                                                                    
+use Shopware\Core\Framework\DataAbstractionLayer\Field\CustomFields;
 
 [...]
 class ExampleDefinition extends EntityDefinition
@@ -97,7 +97,7 @@ Once again, this example is built upon the [Add custom complex data](../data-han
 
 If you want to support custom fields now, you have to add a new column `custom_fields` of type `JSON` to your migration.
 
-```php
+```PHP
 // <plugin root>/src/Migration/Migration1611664789Example.php
 public function update(Connection $connection): void
 {
@@ -128,9 +128,9 @@ Note the new `custom_fields` column here. It has to be a JSON field and should d
 
 Make sure to understand entity translations in general first, which is explained here [Add data translations](../data-handling/add-data-translations). If you want your custom fields to be translatable, you can simply work with a `TranslatedField` here as well.
 
-```php
+```PHP
 // <plugin root>/src/Core/Content/Example/ExampleDefinition.php
-use Shopware\Core\Framework\DataAbstractionLayer\Field\TranslatedField;                                                               
+use Shopware\Core\Framework\DataAbstractionLayer\Field\TranslatedField;
 
 [...]
 
@@ -156,9 +156,9 @@ Just add the `TranslatedField` and apply `customFields` as a parameter.
 
 In your translated entity definition, you then add the `CustomFields` field instead.
 
-```php
+```PHP
 // <plugin root>/src/Core/Content/Example/Aggregate/ExampleTranslation/ExampleTranslationDefinition.php
-use Shopware\Core\Framework\DataAbstractionLayer\Field\CustomFields;                                                                    
+use Shopware\Core\Framework\DataAbstractionLayer\Field\CustomFields;
 
 [...]
 class ExampleTranslationDefinition extends EntityTranslationDefinition
@@ -190,7 +190,7 @@ So let's assume you've got your own `example` entity up and running, and now you
 
 In that case, you can use your entities' repository and start creating or updating entities with custom fields. If you don't understand what's going on here, head over to our guide about [Writing data](../data-handling/writing-data) first.
 
-```php
+```PHP
 $this->swagExampleRepository->upsert([[
     'id' => '<your ID here>',
     'customFields' => ['swag_example_size' => 15]
@@ -201,7 +201,7 @@ This will execute perfectly fine, and you just saved a custom field with name `s
 
 As already mentioned, you do not have to define a custom field first before saving it. That's because there is no validation happening here yet, you can write whatever valid JSON you want to that column, so the following example would also execute without any issues:
 
-```php
+```PHP
 $this->swagExampleRepository->upsert([[
     'id' => '<your ID here>',
     'customFields' => [ 'foo' => 'bar', 'baz' => [] ]
@@ -216,19 +216,21 @@ So now you've already filled the custom fields of one of your entity instances v
 
 Only if you want your custom field to show up in the Administration and to be editable in there, you have to define the custom fields first in a custom field set. For this you have to use the custom fieldset repository, which can be retrieved from the dependency injection container via the `custom_field_set.repository` key and is used like any other repository.
 
-```xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\BasicExample\CustomFieldClass">
-          <argument type="service" id="custom_field_set.repository"/>
-          ...
-        </service>
-    </services>
-</container>
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+use Swag\BasicExample\CustomFieldClass;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(CustomFieldClass::class)
+        ->args([service('custom_field_set.repository')]);
+};
 ```
 
 If you need to learn how that is done in full, head to our guide regarding [Writing data](../data-handling/writing-data).
@@ -236,7 +238,7 @@ If you need to learn how that is done in full, head to our guide regarding [Writ
 Now use the `create` method of the repository to create a new custom field set.
 Plugin lifecycle events are perfect for this as the container can provide the `custom_field_set.repository` service and can be used to set up on installation and remove the set on removal.
 
-```php
+```PHP
 use Shopware\Core\System\CustomField\CustomFieldTypes;
 use \Shopware\Core\Defaults;
 
@@ -275,7 +277,7 @@ $this->customFieldSetRepository->create([
 This will now create a custom field set with the name `swag_example_set` and the field, `swag_example_size`. This time we also define its type, which should be of type integer here. The type is important to mention, because the Administration will use this information to display a proper field. Also, when trying to write the custom field `swag_example_size`, the value has to be an integer.
 
 The translated labels are added to both the field and the set, which are going to be displayed in the Administration. Also, the fallback language can be defined in case the system language is not guaranteed to be either en_GB or de_DE.
-  
+
 If you have several custom fields and want to order them within a specific order, you can do so with the `customFieldPosition` property.
 
 ::: info
@@ -299,7 +301,7 @@ While theoretically your custom field is now properly defined for the Administra
 On uninstallation of your plugin, you should remove your custom field definition.
 To update or delete a `custom_field_set`, you can use the standard repository methods like `update`, `upsert`, or `delete`:
 
-```php
+```PHP
 $setId = $this->customFieldSetRepository->searchIds((new Criteria())->addFilter(new EqualsFilter('name', 'swag_example_set')), $context)->firstId();
 $this->customFieldSetRepository->delete([['id' => $setId]], $context);
 ```
@@ -314,7 +316,7 @@ UPDATE swag_example SET custom_fields = JSON_REMOVE(custom_fields, '$.swag_examp
 If you have a table with a lot of data, like orders or products, you should not approach it carelessly to avoid overwhelming the database with too many changes at once.
 This can look like this instead:
 
-```php
+```PHP
 $updateLimit = 1000;
 
 do {
diff --git a/guides/plugins/plugins/framework/custom-field/fetching-data-from-entity-selection.md b/guides/plugins/plugins/framework/custom-field/fetching-data-from-entity-selection.md
index 6876c300aa..05ec088e6f 100644
--- a/guides/plugins/plugins/framework/custom-field/fetching-data-from-entity-selection.md
+++ b/guides/plugins/plugins/framework/custom-field/fetching-data-from-entity-selection.md
@@ -25,7 +25,7 @@ To resolve the `id` and getting access to the product we have linked here, we ca
 
 Lets create a `ProductSubscriber` first which will listen to the `ProductEvents::PRODUCT_LOADED_EVENT`.
 
-```php
+```PHP
 // <plugin root>/src/Subscriber/ProductSubscriber.php
 <?php declare(strict_types=1);
 
@@ -50,27 +50,26 @@ class ProductSubscriber implements EventSubscriberInterface
 }
 ```
 
-For this subscriber to work we need to register it in the service container via the `services.xml` file:
+For this subscriber to work we need to register it in the service container via the `services.php` file:
 
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+use Swag\BasicExample\Subscriber\ProductSubscriber;
 
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
 
-    <services>
-        <service id="Swag\BasicExample\Subscriber\ProductSubscriber">
-            <tag name="kernel.event_subscriber"/>
-        </service>
-    </services>
-</container>
+    $services->set(ProductSubscriber::class)
+        ->tag('kernel.event_subscriber');
+};
 ```
 
 Now our `ProductSubscriber` should be called every time a product is loaded, so we can resolve the custom field `custom_linked_product`.
 
-```php
+```PHP
 // <plugin root>/src/Subscriber/ProductSubscriber.php
 <?php declare(strict_types=1);
 
@@ -92,7 +91,7 @@ class ProductSubscriber implements EventSubscriberInterface
     public function onProductLoaded(EntityLoadedEvent $event): void
     {
 
-        // loop through all loaded product      
+        // loop through all loaded product
         /** @var ProductEntity $productEntity */
         foreach ($event->getEntities() as $productEntity) {
             $customFields = $productEntity->getCustomFields();
@@ -116,28 +115,29 @@ Inside the `onProductLoaded` method we can get access to the loaded product enti
 
 But, how we can load the linked product by its `id` if the custom field was set? We have to inject the product repository to achieve it.
 
-First we update the `services.xml` and inject the product repository.
+First we update the `services.php` and inject the product repository.
+
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+use Swag\BasicExample\Subscriber\ProductSubscriber;
 
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
 
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
 
-    <services>
-        <service id="Swag\BasicExample\Subscriber\ProductSubscriber">
-            <argument type="service" id="product.repository"/>
-            <tag name="kernel.event_subscriber"/>
-        </service>
-    </services>
-</container>
+    $services->set(ProductSubscriber::class)
+        ->args([service('product.repository')])
+        ->tag('kernel.event_subscriber');
+};
 ```
 
 Now we can use the product repository in our subscriber.
 
-```php
+```PHP
 // <plugin root>/src/Subscriber/ProductSubscriber.php
 <?php declare(strict_types=1);
 
@@ -154,7 +154,7 @@ class ProductSubscriber implements EventSubscriberInterface
 {
     private EntityRepository $productRepository;
 
-    public function __construct(EntityRepository $productRepository) 
+    public function __construct(EntityRepository $productRepository)
     {
         $this->productRepository = $productRepository;
     }
@@ -167,7 +167,7 @@ As you can see, the product repository was injected and is now available to the
 
 Let's have a look at the final implementation of the subscriber.
 
-```php
+```PHP
 // <plugin root>/src/Subscriber/ProductSubscriber.php
 <?php declare(strict_types=1);
 
@@ -184,7 +184,7 @@ class ProductSubscriber implements EventSubscriberInterface
 {
     private EntityRepository $productRepository;
 
-    public function __construct(EntityRepository $productRepository) 
+    public function __construct(EntityRepository $productRepository)
     {
         $this->productRepository = $productRepository;
     }
diff --git a/guides/plugins/plugins/framework/data-handling/add-complex-data-to-existing-entities.md b/guides/plugins/plugins/framework/data-handling/add-complex-data-to-existing-entities.md
index d7e1ff09d7..35e81865d9 100644
--- a/guides/plugins/plugins/framework/data-handling/add-complex-data-to-existing-entities.md
+++ b/guides/plugins/plugins/framework/data-handling/add-complex-data-to-existing-entities.md
@@ -29,7 +29,7 @@ You add new fields by overriding the method `extendFields` and add your new fiel
 
 Here's an example class called `CustomExtension`:
 
-```php
+```PHP
 // <plugin root>/src/Extension/Content/Product/CustomExtension.php
 <?php declare(strict_types=1);
 
@@ -57,22 +57,21 @@ class CustomExtension extends EntityExtension
 
 Now we have to register our extension via the DI-container. If you don't know how that's done in general, head over to our guide about registering a custom service [Add a custom class / service](../../plugin-fundamentals/add-custom-service) or our guide about the [dependency injection](../../plugin-fundamentals/dependency-injection).
 
-Here's our `services.xml`:
+Here's our `services.php`:
 
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Extension\Content\Product\CustomExtension;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
 
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
 
-    <services>
-        <service id="Swag\BasicExample\Extension\Content\Product\CustomExtension">
-            <tag name="shopware.entity.extension"/>
-        </service>
-    </services>
-</container>
+    $services->set(CustomExtension::class)
+        ->tag('shopware.entity.extension');
+};
 ```
 
 ### Adding a field with a database
@@ -81,7 +80,7 @@ In this guide, you're extending the product entity in order to add a new string
 
 Let's start with the `CustomExtension` class by adding a new field in the `extendFields` method.
 
-```php
+```PHP
 // <plugin root>/src/Extension/Content/Product/CustomExtension.php
 <?php declare(strict_types=1);
 
@@ -123,7 +122,7 @@ Creating a new entity is not explained in this guide, so make sure you know [thi
 
 Our new entity will be located in the same directory as our extension. Let's first have a look at it before going into the explanation:
 
-```php
+```PHP
 // <plugin root>/src/Extension/Content/Product/ExampleExtensionDefinition.php
 <?php declare(strict_types=1);
 
@@ -179,31 +178,30 @@ The fourth parameter is the class of the associated definition, the `ProductDefi
 
 Of course, this new definition also needs to be registered to the DI container:
 
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Extension\Content\Product\CustomExtension;
+use Swag\BasicExample\Extension\Content\Product\ExampleExtensionDefinition;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
 
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
 
-    <services>
-        <service id="Swag\BasicExample\Extension\Content\Product\CustomExtension">
-            <tag name="shopware.entity.extension"/>
-        </service>
+    $services->set(CustomExtension::class)
+        ->tag('shopware.entity.extension');
 
-        <service id="Swag\BasicExample\Extension\Content\Product\ExampleExtensionDefinition">
-            <tag name="shopware.entity.definition" entity="swag_example_extension" />
-        </service>
-    </services>
-</container>
+    $services->set(ExampleExtensionDefinition::class)
+        ->tag('shopware.entity.definition', ['entity' => 'swag_example_extension']);
+};
 ```
 
 #### Adding the new database table
 
 Of course, you have to add the new database table via a [Database migration](../../plugin-fundamentals/database-migrations). Look at the guide linked above to see how exactly this is done. Here's the example migration and how it could look like:
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace Swag\BasicExample\Migration;
@@ -253,7 +251,7 @@ As already mentioned, your new association is automatically loaded every time a
 
 As with every [write operation](writing-data), this is done via the product repository in this example.
 
-```php
+```PHP
 $this->productRepository->upsert([[
     'id' => '<your product ID here>',
     'exampleExtension' => [
@@ -270,7 +268,7 @@ We can use the DAL event which gets fired every time the product entity is loade
 
 Below, you can find an example implementation where we add our extension when the product gets loaded.
 
-```php
+```PHP
 // <plugin root>/src/Subscriber/ProductSubscriber.php
 <?php declare(strict_types=1);
 
@@ -305,22 +303,21 @@ We're registering to the `ProductEvents::PRODUCT_LOADED_EVENT` event, which is f
 
 Please note that its second parameter, the actual value, has to be a struct and not just a string or other kind of scalar value.
 
-After we've created our subscriber, we have to adjust our `services.xml` to register it. Below you can find our `services.xml`.
+After we've created our subscriber, we have to adjust our `services.php` to register it. Below you can find our `services.php`.
+
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
 
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
+use Swag\BasicExample\Subscriber\ProductSubscriber;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
 
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
 
-    <services>
-        <service id="Swag\BasicExample\Subscriber\ProductSubscriber">
-            <tag name="kernel.event_subscriber"/>
-        </service>
-    </services>
-</container>
+    $services->set(ProductSubscriber::class)
+        ->tag('kernel.event_subscriber');
+};
 ```
 
 ## Entity extension vs. Custom fields
@@ -335,7 +332,7 @@ This feature is available since Shopware 6.6.10.0
 
 In case your project or plugin requires many entity extensions, you can register a `BulkEntityExtension` which allows extending multiple entities at once:
 
-```php
+```PHP
 <?php
 
 namespace Examples;
@@ -361,10 +358,9 @@ class MyBulkExtension extends BulkEntityExtension
 
 Each yield defines the entity name which should be extended and the array value defines the fields which should be added. In this example, the `product` and `category` entities are extended.
 
-You must also register the extension in your `services.xml` file and tag it with `shopware.bulk.entity.extension`.
+You must also register the extension in your `services.php` file and tag it with `shopware.bulk.entity.extension`.
 
-```xml
-<service id="Examples\MyBulkExtension">
-   <tag name="shopware.bulk.entity.extension"/>
-</service>
+```PHP
+$services->set(\Examples\MyBulkExtension::class)
+    ->tag('shopware.bulk.entity.extension');
 ```
diff --git a/guides/plugins/plugins/framework/data-handling/add-custom-complex-data.md b/guides/plugins/plugins/framework/data-handling/add-custom-complex-data.md
index bd8add32d3..f11c67e4b4 100644
--- a/guides/plugins/plugins/framework/data-handling/add-custom-complex-data.md
+++ b/guides/plugins/plugins/framework/data-handling/add-custom-complex-data.md
@@ -27,7 +27,7 @@ In this guide we'll name our table `swag_example`, you'll find this name a few m
 
 As already mentioned in the prerequisites, creating a database table is done via plugin migrations [Plugin migrations](../../plugin-fundamentals/database-migrations), head over to this guide to understand how this example works.
 
-```php
+```PHP
 // <plugin root>/src/Migration/Migration1611664789Example.php
 <?php declare(strict_types=1);
 
@@ -81,7 +81,7 @@ This will also be the case for the `Entity` class itself, as well as the `Entity
 
 Start of with creating a new file named `ExampleDefinition.php` in the directory `<plugin root>/src/Core/Content/Example/ExampleDefinition.php`. Below you can see our example definition, which is explained afterwards:
 
-```php
+```PHP
 // <plugin root>/src/Core/Content/Example/ExampleDefinition.php
 <?php declare(strict_types=1);
 
@@ -117,7 +117,7 @@ The method `defineFields` contains all the fields, that your entity or table con
 
 As you can see in your migration, your table consists of the following fields: You've got an `id` field, a `name` field, a `description` and an `active` field. Other than that, the other two columns `created_at` and `updated_at` don't have to be defined in your definition, since they're included by default. You're asked to return a `Shopware\Core\Framework\DataAbstractionLayer\FieldCollection` instance here, which then has to contain an array of your fields. There's several field classes, e.g. an `Shopware\Core\Framework\DataAbstractionLayer\Field\IdField` or a `Shopware\Core\Framework\DataAbstractionLayer\Field\StringField`, which you have to create and pass into the `FieldCollection`, so let's do that.
 
-```php
+```PHP
 // <plugin root>/src/Core/Content/Example/ExampleDefinition.php
 <?php declare(strict_types=1);
 
@@ -163,22 +163,22 @@ Another thing to note is the `addFlags` call on the `IdField`. Those flags are l
 
 If you want to know more about the flags and how to use them, head over to our guide on how to use flags [Using flags](using-flags).
 
-All that's left to do now, is to introduce your `ExampleDefinition` to Shopware by registering your class in your `services.xml` file and by using the `shopware.entity.definition` tag, because Shopware is looking for definitions this way. If your plugin does not have a `services.xml` file yet or you don't know how that's done, head over to our guide about registering a custom service [Add a custom class / service](../../plugin-fundamentals/add-custom-service) or our guide about the [Dependency injection](../../plugin-fundamentals/dependency-injection).
+All that's left to do now, is to introduce your `ExampleDefinition` to Shopware by registering your class in your `services.php` file and by using the `shopware.entity.definition` tag, because Shopware is looking for definitions this way. If your plugin does not have a `services.php` file yet or you don't know how that's done, head over to our guide about registering a custom service [Add a custom class / service](../../plugin-fundamentals/add-custom-service), or our guide about the [Dependency injection](../../plugin-fundamentals/dependency-injection).
 
-Here's the `services.xml` as it should look like:
+Here's the `services.php` as it should look like:
 
-```xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+```PHP
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Core\Content\Example\ExampleDefinition;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
 
-    <services>
-        <service id="Swag\BasicExample\Core\Content\Example\ExampleDefinition">
-            <tag name="shopware.entity.definition" entity="swag_example" />
-        </service>
-    </services>
-</container>
+    $services->set(ExampleDefinition::class)
+        ->tag('shopware.entity.definition', ['entity' => 'swag_example']);
+};
 ```
 
 Please note the tag for your definition and the respective `entity` attribute, which has to contain the technical name of your entity, which you provided in your entity definition. In this case this must be `swag_example`.
@@ -196,7 +196,7 @@ The properties of your entity class have to be at least `protected`, otherwise t
 For the same reason `readonly` properties are not allowed. This holds true not just for `Entity` classes, but for all classes that extend the generic `Struct` class.
 :::
 
-```php
+```PHP
 // <plugin root>/src/Core/Content/Example/ExampleEntity.php
 <?php declare(strict_types=1);
 
@@ -251,7 +251,7 @@ As you can see, it only holds the properties and its respective getters and sett
 
 Now you need your definition to know its custom entity class. This is done by overriding the method `getEntityClass` in your `ExampleDefinition`.
 
-```php
+```PHP
 // <plugin root>/src/Core/Content/Example/ExampleDefinition.php
 class ExampleDefinition extends EntityDefinition
 {
@@ -274,7 +274,7 @@ So create a `ExampleCollection` class in the same directory as your `ExampleDefi
 
 This is how your collection class could then look like:
 
-```php
+```PHP
 // <plugin root>/src/Core/Content/Example/ExampleCollection.php
 <?php declare(strict_types=1);
 
@@ -298,7 +298,7 @@ The class documentation is just another helper to have a proper auto-completion
 
 Now it's time to introduce your custom collection to your `ExampleDefinition` again. This is done by overriding its `getCollectionClass` method.
 
-```php
+```PHP
 // <plugin root>/src/Core/Content/Example/ExampleDefinition.php
 class ExampleDefinition extends EntityDefinition
 {
diff --git a/guides/plugins/plugins/framework/data-handling/add-data-indexer.md b/guides/plugins/plugins/framework/data-handling/add-data-indexer.md
index bd53d3936e..9d87ff4a02 100644
--- a/guides/plugins/plugins/framework/data-handling/add-data-indexer.md
+++ b/guides/plugins/plugins/framework/data-handling/add-data-indexer.md
@@ -12,7 +12,7 @@ This guide is built upon the [Plugin base guide](../../plugin-base-guide), but a
 
 It is possible to add data indexer for your own entities, like the one created in the [Adding custom complex data](./add-custom-complex-data) guide or for existing entities. However, if you want to react on changes of existing entities the preferred way should be subscribing to the events if available. See the [Index data using existing events](#index-data-using-existing-events) section below. To create a new indexer, just create a new class in your plugin:
 
-```php
+```PHP
 // <plugin root>/src/Core/Framework/DataAbstractionLayer/Indexing/ExampleIndexer.php
 <?php declare(strict_types=1);
 
@@ -117,21 +117,27 @@ class ExampleIndexer extends EntityIndexer
 
 With the corresponding service registration:
 
-```xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-                <service id="Swag\BasicExample\Core\Framework\DataAbstractionLayer\Indexing\ExampleIndexer">
-                    <argument type="service" id="Shopware\Core\Framework\DataAbstractionLayer\Dbal\Common\IteratorFactory"/>
-                    <argument type="service" id="customer.repository"/>
-                    <argument type="service" id="Doctrine\DBAL\Connection" />
-                    <tag name="shopware.entity_indexer"/>
-                </service>
-    </services>
-</container>
+```PHP
+<?php declare(strict_types=1);
+
+use Doctrine\DBAL\Connection;
+use Shopware\Core\Framework\DataAbstractionLayer\Dbal\Common\IteratorFactory;
+use Swag\BasicExample\Core\Framework\DataAbstractionLayer\Indexing\ExampleIndexer;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(ExampleIndexer::class)
+        ->args([
+            service(IteratorFactory::class),
+            service('customer.repository'),
+            service(Connection::class),
+        ])
+        ->tag('shopware.entity_indexer');
+};
 ```
 
 The indexer service has to be tagged as `shopware.entity_indexer` in order to work.
@@ -157,7 +163,7 @@ By default, all messages which are returned by the `public function update()` fu
 
 By default, indexing is also active while working with an indexer, which means, that entities that are written over the DAL also trigger `EntityWrittenContainerEvent` events. So the indexers are triggered again. This can lead to an infinite loop. Therefore, the connection should be used directly to alter data in the database. You can find more information about this in the corresponding ADR [when to use plain SQL or the DAL](../../../../../resources/references/adr/2021-05-14-when-to-use-plain-sql-or-dal.md). However, if you want to use the DAL for manipulation data in a data indexer, indexing can be disabled. This can be done by passing adding a flag to the context, as shown in the example below:
 
-```php
+```PHP
 public function update(EntityWrittenContainerEvent $event): ?EntityIndexingMessage
 {
     $updates = $event->getPrimaryKeys(CustomerDefinition::ENTITY_NAME);
@@ -175,7 +181,7 @@ public function update(EntityWrittenContainerEvent $event): ?EntityIndexingMessa
 
 ## Index data using existing events
 
-There are already a bunch of indexers in shopware that you can use. If you take a look at the `CustomerIndexer` or `CategoryIndexer` classes for example, you will see that they dispatch an event in the `handle` method. This should be used for indexing data of the main entities. Among others, the following indexers already exist and dispatch events that can be used for indexing data:  
+There are already a bunch of indexers in shopware that you can use. If you take a look at the `CustomerIndexer` or `CategoryIndexer` classes for example, you will see that they dispatch an event in the `handle` method. This should be used for indexing data of the main entities. Among others, the following indexers already exist and dispatch events that can be used for indexing data:
 
 * `CustomerIndexer`
 * `CategoryIndexer`
@@ -194,7 +200,7 @@ There are already a bunch of indexers in shopware that you can use. If you take
 
 For this we need a new subscriber. If you are not familiar with a subscriber, have a look at our [Listening to events](../../plugin-fundamentals/listening-to-events) guide. For this example, we just write a new entry to the `log_entry` database table, indicating that a customer was updated.
 
-```php
+```PHP
 // <plugin root>/src/Service/Subscriber.php
 <?php declare(strict_types=1);
 
@@ -248,19 +254,22 @@ class Subscriber implements EventSubscriberInterface
 
 The service definition for the subscriber would look like this.
 
-```xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\BasicExample\Service\Subscriber" >
-            <argument type="service" id="Doctrine\DBAL\Connection" />
-            <tag name="kernel.event_subscriber" />
-        </service>
-    </services>
-</container>
+```PHP
+<?php declare(strict_types=1);
+
+use Doctrine\DBAL\Connection;
+use Swag\BasicExample\Service\Subscriber;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(Subscriber::class)
+        ->args([service(Connection::class)])
+        ->tag('kernel.event_subscriber');
+};
 ```
 
 It is recommended to work directly with the `Connection` since the event is dispatched in the context of an indexer. If we would use the Data Abstraction Layer \(DAL\) for writing changes to the database, the indexer  would be triggered again, because it listens for `EntityWrittenContainerEvent` events. This would lead to an infinite loop. Using the `Connection` directly prevents the DAL from dispatching entity written events. Also the performance of plain sql is much higher, which is very important for indexers in general.
diff --git a/guides/plugins/plugins/framework/data-handling/add-data-translations.md b/guides/plugins/plugins/framework/data-handling/add-data-translations.md
index 73ada1fd6f..3834fb26e9 100644
--- a/guides/plugins/plugins/framework/data-handling/add-data-translations.md
+++ b/guides/plugins/plugins/framework/data-handling/add-data-translations.md
@@ -44,7 +44,7 @@ The translation table's columns should be the following:
 
 This is how your migration could look like:
 
-```php
+```PHP
 // <plugin root>/src/Migration/Migration1612863838ExampleTranslation.php
 <?php declare(strict_types=1);
 
@@ -96,7 +96,7 @@ The translation is an aggregation to the `ExampleEntity`. Therefore, you should
 
 Now we can start creating our `ExampleTranslationDefinition` which extends from `Shopware\Core\Framework\DataAbstractionLayer\EntityTranslationDefinition`. Special for entity translation is, that we have to override a method called `getParentDefinitionClass` which returns the definition class of our entity we want to translate. In this case it's `ExampleDefinition`.
 
-```php
+```PHP
 // <plugin root>/src/Core/Content/Example/Aggregate/ExampleTranslation/ExampleTranslationDefinition.php
 <?php declare(strict_types=1);
 
@@ -133,27 +133,27 @@ class ExampleTranslationDefinition extends EntityTranslationDefinition
 
 As you can see, we've implemented a `StringField` for the `name` column, the other fields like the `language_id` will be automatically added by the `EntityTranslationDefinition` since they are base fields of it.
 
-All that's left to do now, is to introduce your `ExampleTranslationDefinition` to Shopware by registering your class in your `services.xml` file and by using the `shopware.entity.definition` tag, because Shopware 6 is looking for definitions this way. Note, that we have to register the translation after the entity we want to translate.
+All that's left to do now, is to introduce your `ExampleTranslationDefinition` to Shopware by registering your class in your `services.php` file and by using the `shopware.entity.definition` tag, because Shopware 6 is looking for definitions this way. Note, that we have to register the translation after the entity we want to translate.
 
-Here's the `services.xml` as it should look like:
+Here's the `services.php` as it should look like:
 
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Core\Content\Example\ExampleDefinition;
+use Swag\BasicExample\Core\Content\Example\Aggregate\ExampleTranslation\ExampleTranslationDefinition;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
 
-    <services>
-        <service id="Swag\BasicExample\Core\Content\Example\ExampleDefinition">
-            <tag name="shopware.entity.definition" entity="swag_example" />
-        </service>
+    $services->set(ExampleDefinition::class)
+        ->tag('shopware.entity.definition', ['entity' => 'swag_example']);
 
-        <service id="Swag\BasicExample\Core\Content\Example\Aggregate\ExampleTranslation\ExampleTranslationDefinition">
-            <tag name="shopware.entity.definition" entity="swag_example_translation" />
-        </service>
-    </services>
-</container>
+    $services->set(ExampleTranslationDefinition::class)
+        ->tag('shopware.entity.definition', ['entity' => 'swag_example_translation']);
+};
 ```
 
 ### Entity class
@@ -162,7 +162,7 @@ So far we introduced our definition, we can create our `ExampleTranslationEntity
 
 Here's our `ExampleTranslationEntity`:
 
-```php
+```PHP
 // <plugin root>/src/Core/Content/Example/Aggregate/ExampleTranslation/ExampleTranslationEntity.php
 <?php declare(strict_types=1);
 
@@ -213,7 +213,7 @@ class ExampleTranslationEntity extends TranslationEntity
 
 Now we need our translation definition to know its custom entity class. This is done by overriding the method `getEntityClass` in our `ExampleTranslationDefinition`.
 
-```php
+```PHP
 // <plugin root>/src/Core/Content/Example/Aggregate/ExampleTranslation/ExampleTranslationDefinition.php
 class ExampleTranslationDefinition extends EntityTranslationDefinition
 {
@@ -232,7 +232,7 @@ As we already know, we should create an `EntityCollection` for our `Entity` too.
 
 Our collection class could then look like this:
 
-```php
+```PHP
 // <plugin root>/src/Core/Content/Example/Aggregate/ExampleTranslation/ExampleTranslationCollection.php
 <?php declare(strict_types=1);
 
@@ -265,7 +265,7 @@ The main entity class, that is the class with the field(s) we are going to trans
 * a `TranslatedField` for the “name” field
 * a `TranslationsAssociationField`, with a reference to the ExampleTranslationDefinition
 
-```php
+```PHP
 // <plugin root>/src/Core/Content/Example/ExampleDefinition.php
 <?php declare(strict_types=1);
 
diff --git a/guides/plugins/plugins/framework/data-handling/entities-via-attributes.md b/guides/plugins/plugins/framework/data-handling/entities-via-attributes.md
index 78cc6237b0..eb95d990b3 100644
--- a/guides/plugins/plugins/framework/data-handling/entities-via-attributes.md
+++ b/guides/plugins/plugins/framework/data-handling/entities-via-attributes.md
@@ -23,7 +23,7 @@ Note: this is only possible since 6.6.9.0
 You have to define a primary key. The primary key is defined by adding the `PrimaryKey` attribute to a property.
 In theory, the primary key can be of any type, but it is recommended to use a `UUID`.
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace Examples;
@@ -46,13 +46,12 @@ For example, you can add the `Field` attribute to a property to define the type
 
 ## Register the entity
 
-To register the entity, you have to add this class to the DI container in the `services.xml` file.
+To register the entity, you have to add this class to the DI container in the `services.php` file.
 This is done by adding the `shopware.entity` tag to the service definition.
 
-```xml
-<service id="Examples\ExampleEntity">
-    <tag name="shopware.entity"/>
-</service>
+```PHP
+$services->set(Examples\ExampleEntity::class)
+    ->tag('shopware.entity');
 ```
 
 That's it.
@@ -66,7 +65,7 @@ To define more fields, you typically use the `Field` attribute.
 The `Field` attribute requires the `type` parameter, which is the type of the field.
 The type can be any of the `FieldType` constants.
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace Examples;
@@ -108,7 +107,7 @@ Use the fully qualified class name reference as value for the `type` parameter.
 This feature is available since Shopware 6.6.9.0.
 :::
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace Examples;
@@ -140,7 +139,7 @@ class ExampleEntity extends Entity
 We also provide a list of special field types, which implement a specific behavior.
 They have their own PHP attribute class, for example the `AutoIncrement` or `ForeignKey` field.
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace Examples;
@@ -172,7 +171,7 @@ class ExampleEntity extends Entity
 
 If you want to store JSON data in a field with its own validation and serialization logic, you can use the `Serialized` attribute and define its own serializer class:
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace Examples;
@@ -203,7 +202,7 @@ class ExampleEntity extends Entity
 To allow custom fields, you can use the `EntityCustomFieldsTrait`.
 This gives you some helper methods to easily work with custom field values out of the box.
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace Examples;
@@ -229,7 +228,7 @@ class ExampleEntity extends Entity
 
 Alternatively you can use the `CustomField` attribute directly, that way you have full control over the custom fields and can add your own helpers.
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace Examples;
@@ -262,7 +261,7 @@ class ExampleEntity extends Entity
 By default, each field of an entity is not exposed in the API.
 To expose a field in the API, you must set the `api` parameter of the `Field` attribute to `true` or specify one of the scopes you want to allow.
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace Examples;
@@ -305,7 +304,7 @@ This field needs to be nullable, as by default it will not be loaded, but this a
 
 Notice: Properties with the `translated` flag must be nullable.
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace Examples;
@@ -342,7 +341,7 @@ However, you can explicitly mark a field as required by adding the `Required` at
 This will automatically add a validation rule to the field.
 This is necessary for fields marked as `translated`, as translated fields must be nullable.
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace Examples;
@@ -372,7 +371,7 @@ class ExampleEntity extends Entity
 It is also possible to define associations between entities.
 You can use one of the following four association types: `OneToOne`, `OneToMany`, `ManyToOne` or `ManyToMany`.
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace Examples;
@@ -437,7 +436,7 @@ Also, you don't have to define any `EntityTranslationDefinition` or `EntityColle
 
 ## Full example
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace Examples;
diff --git a/guides/plugins/plugins/framework/data-handling/reading-data.md b/guides/plugins/plugins/framework/data-handling/reading-data.md
index e7552be6de..304c2869d0 100644
--- a/guides/plugins/plugins/framework/data-handling/reading-data.md
+++ b/guides/plugins/plugins/framework/data-handling/reading-data.md
@@ -27,24 +27,26 @@ Dealing with the Data Abstraction Layer is done by using the automatically gener
 The repository's service name follows this pattern: `entity_name.repository`  
 For products this then would be `product.repository`, so let's do this.
 
-```xml
-// SwagBasicExample/src/Resources/config/services.xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\BasicExample\Service\ReadingData" >
-            <argument type="service" id="product.repository"/>
-        </service>
-    </services>
-</container>
+```PHP
+// SwagBasicExample/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Service\ReadingData;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(ReadingData::class)
+        ->args([service('product.repository')]);
+};
 ```
 
 And here's the respective class including its constructor:
 
-```php
+```PHP
 // SwagBasicExample/src/Service/ReadingData.php
 <?php declare(strict_types=1);
 
@@ -63,20 +65,20 @@ class ReadingData
 }
 ```
 
-So we registered a custom service called `ReadingData` and applied the repository as a constructor parameter. If you want to fetch data for another entity, just switch the `id` in the `services.xml` to whatever repository you need, e.g. `order.repository` for orders.
+So we registered a custom service called `ReadingData` and applied the repository as a constructor parameter. If you want to fetch data for another entity, just switch the `id` in the `services.php` to whatever repository you need, e.g. `order.repository` for orders.
 
 ### Using the repository
 
 Now that you've injected the repository into your service, you can start using it. First of all, for the following examples you'll need two more imports:
 
-```php
+```PHP
 use Shopware\Core\Framework\Context;
 use Shopware\Core\Framework\DataAbstractionLayer\Search\Criteria;
 ```
 
 Let's start with the most basic read action now:
 
-```php
+```PHP
 public function readData(Context $context): void
 {
     $products = $this->productRepository->search(new Criteria(), $context);
@@ -95,7 +97,7 @@ Now let's get into actually filtering your search result to get more precise res
 
 Often you have an ID from an entity and you just want to find the whole dataset related to that ID, so here you go:
 
-```php
+```PHP
 public function readData(Context $context): void
 {
     $product = $this->productRepository->search(new Criteria([$myId]), $context)->first();
@@ -114,7 +116,7 @@ While searching for an ID will do the trick quite often, you might want to searc
 
 In order to do this, you can apply filters to the `Criteria` object, such as an `EqualsFilter`, which accepts a field name and the value to search for. You can find the `EqualsFilter` here: `Shopware\Core\Framework\DataAbstractionLayer\Search\Filter\EqualsFilter`
 
-```php
+```PHP
 public function readData(Context $context): void
 {
     $criteria = new Criteria();
@@ -136,7 +138,7 @@ For this case, you can combine filters using the `OrFilter` or the `AndFilter`,
 
 Let's just build the example mentioned above:
 
-```php
+```PHP
 public function readData(Context $context): void
 {
     $criteria = new Criteria();
@@ -161,7 +163,7 @@ E.g.: Fetch all products, whose name is `Example product`, but also return the t
 
 In that case, you can just use the `addPostFilter` instead of `addFilter`:
 
-```php
+```PHP
 public function readData(Context $context): void
 {
     $criteria = new Criteria();
@@ -181,7 +183,7 @@ There is more than just an `EqualsFilter`, which is the SQL equivalent of `WHERE
 
 Of course associations to other entities are also possible in Shopware 6. If you, for example, want to load all product-reviews, which is an entity itself, related to the product you have found, you can do so by adding associations to the criteria object.
 
-```php
+```PHP
 public function readData(Context $context): void
 {
     $criteria = new Criteria();
@@ -196,7 +198,7 @@ Just like the available entity fields, you can find all possible associations in
 
 Also worth to mention is the fact, that you can chain the association key. E.g. a product-review has another association to the customer, who created that review. If you want access to both the review itself, as well as the customer, you can just write the association like that:
 
-```php
+```PHP
 public function readData(Context $context): void
 {
     $criteria = new Criteria();
@@ -213,7 +215,7 @@ Yes, this is doable. You can apply filters to an association. E.g. "Add all prod
 
 For this we can use `getAssociation` instead, which basically returns its own `Criteria` object, on which you can apply a filter.
 
-```php
+```PHP
 public function readData(Context $context): void
 {
     $criteria = new Criteria();
@@ -231,7 +233,7 @@ Once again: Note, that we used `getAssociation` here now instead of `addAssociat
 
 Another example to clarify what's going on here:
 
-```php
+```PHP
 public function readData(Context $context): void
 {
     // This will always return the product with the given name, no matter if it has a review with 4 or more stars.
@@ -258,7 +260,7 @@ Every `ManyToMany` association comes with a mapping entity, such as the `Product
 
 The following example will **not** work:
 
-```php
+```PHP
 public function readData(Context $context): void
 {
     $criteria = new Criteria();
@@ -274,7 +276,7 @@ Since mapping entities just consist of two primary keys, there is no need to sea
 
 Of course you can also aggregate your data. Just like filters and associations, this can be done by using an `addAggregation` method on the `Criteria` object. Let's create an example aggregation, that returns the average rating for a product:
 
-```php
+```PHP
 public function readData(Context $context): void
 {
     $criteria = new Criteria();
@@ -298,7 +300,7 @@ There's just a few more things missing: Limiting your result intentionally to e.
 
 Let's start with the limiting of the result:
 
-```php
+```PHP
 public function readData(Context $context): void
 {
     $criteria = new Criteria();
@@ -311,7 +313,7 @@ public function readData(Context $context): void
 
 That's quite self-explanatory, isn't it? Just use the `setLimit` method with your desired limit as parameter. Little spoiler: It's the same for the offset!
 
-```php
+```PHP
 public function readData(Context $context): void
 {
     $criteria = new Criteria();
@@ -325,7 +327,7 @@ public function readData(Context $context): void
 
 This way you get the 2nd possible product. But since you didn't define a sorting yourself, the result can be quite confusing, so let's add a sorting.
 
-```php
+```PHP
 public function readData(Context $context): void
 {
     $criteria = new Criteria();
@@ -350,7 +352,7 @@ Imagine you need to iterate over all products of your shop, which contains more
 
 Instead, the `RepositoryIterator` will return a batch of data, which size you can define, with each iteration. Just be sure to not use it unnecessarily, since it will create a new database request with each iteration, which is not needed for smaller chunks of data.
 
-```php
+```PHP
 public function readData(Context $context): void
 {
     $criteria = new Criteria();
@@ -374,7 +376,7 @@ Put differently, you must ensure that your sorting means that there's only one c
 
 For example, ordering products by `manufacturerNumber` alone could cause this issue, because several products can have the same `manufacturerNumber`, so there's several correct orderings of those products. On the other hand, because each product is guaranteed to have a unique ID, sorting by ID is an easy way to mitigate this issue:
 
-```php
+```PHP
 $criteria = new Criteria();
 //This sorting alone would result in sorting that is nondeterministic as several products might have the same value for this field:
 $criteria->addSorting(new FieldSorting('manufacturerNumber'));  
diff --git a/guides/plugins/plugins/framework/data-handling/replacing-associated-data.md b/guides/plugins/plugins/framework/data-handling/replacing-associated-data.md
index b0e5d1e0ab..f9aadc4be3 100644
--- a/guides/plugins/plugins/framework/data-handling/replacing-associated-data.md
+++ b/guides/plugins/plugins/framework/data-handling/replacing-associated-data.md
@@ -25,7 +25,7 @@ So let's start with the main issue going on here. Let's imagine you've created a
 
 The following example will show you how **not** to do it. It's assuming that you've previously assigned the category `Old category` with the ID `oldId` to the product.
 
-```php
+```PHP
 public function replaceData(Context $context): void
 {
     $this->productRepository->update([
@@ -55,25 +55,29 @@ In order to delete it, we once again need its repository. The name for the entit
 
 So let's inject this repository into our class called `ReplacingData`:
 
-```xml
-// SwagBasicExample/src/Resources/config/services.xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\BasicExample\Service\ReplacingData" >
-            <argument type="service" id="product.repository"/>
-            <argument type="service" id="product_category.repository"/>
-        </service>
-    </services>
-</container>
+```PHP
+// SwagBasicExample/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Service\ReplacingData;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(ReplacingData::class)
+        ->args([
+            service('product.repository'),
+            service('product_category.repository'),
+        ]);
+};
 ```
 
 Afterwards, you can just use the `delete` method on the repository, just like you did before in the [Writing data](writing-data) guide.
 
-```php
+```PHP
 public function replaceData(Context $context): void
 {
     $this->productCategoryRepository->delete([
@@ -87,7 +91,7 @@ public function replaceData(Context $context): void
 
 Now the association to the old category was removed and you can now use the code above to add the new category instead.
 
-```php
+```PHP
 public function replaceData(Context $context): void
 {
     $productId = 'myProductId';
@@ -118,7 +122,7 @@ And that's it, you've successfully deleted one association and then replaced it
 
 Replacing `OneToOne` or `ManyToOne` associations works just like expected via an `update` call, e.g. for the tax of a product:
 
-```php
+```PHP
 public function replaceData(Context $context): void
 {
     $this->productRepository->update([
diff --git a/guides/plugins/plugins/framework/data-handling/using-database-events.md b/guides/plugins/plugins/framework/data-handling/using-database-events.md
index 2c6278da94..cd1864a285 100644
--- a/guides/plugins/plugins/framework/data-handling/using-database-events.md
+++ b/guides/plugins/plugins/framework/data-handling/using-database-events.md
@@ -36,7 +36,7 @@ You can use this event to capture state, perform actions, and sync data after an
 
 Below is an example subscriber listening to the generic entity write event and logging the ID's of the written entities.
 
-```php
+```PHP
 // <plugin root>/src/Subscriber/EntityWriteSubscriber.php
 <?php declare(strict_types=1);
 
@@ -102,7 +102,7 @@ You can use this event to capture state and perform actions after an entity is r
 
 Below is an example subscriber listening to the generic entity delete event, filtering for CMS page deletions, and then performing a different action based on whether the delete was successful or not.
 
-```php
+```PHP
 // <plugin root>/src/Subscriber/DeleteSubscriber.php
 <?php declare(strict_types=1);
 
@@ -212,7 +212,7 @@ All of stock entities come with their own event class. To keep the example of th
 
 The example below shows you how to use the constants in your event subscriber:
 
-```php
+```PHP
 // <plugin root>/src/Subscriber/ProductSubscriber.php
 <?php declare(strict_types=1);
 
@@ -246,20 +246,19 @@ class ProductSubscriber implements EventSubscriberInterface
 
 After creating the event subscriber, you have to register it. If you don't know how that's done, head over to our guide about [Listening to events](../../plugin-fundamentals/listening-to-events).
 
-Here's our `services.xml`:
+Here's our `services.php`:
 
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Subscriber\ProductSubscriber;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
 
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
 
-    <services>
-        <service id="Swag\BasicExample\Subscriber\ProductSubscriber">
-            <tag name="kernel.event_subscriber"/>
-        </service>
-    </services>
-</container>
+    $services->set(ProductSubscriber::class)
+        ->tag('kernel.event_subscriber');
+};
 ```
diff --git a/guides/plugins/plugins/framework/data-handling/writing-data.md b/guides/plugins/plugins/framework/data-handling/writing-data.md
index 520a8a9916..ef73087b91 100644
--- a/guides/plugins/plugins/framework/data-handling/writing-data.md
+++ b/guides/plugins/plugins/framework/data-handling/writing-data.md
@@ -32,25 +32,29 @@ Dealing with the Data Abstraction Layer is done by using the automatically gener
 The repository's service name follows this pattern: `entity_name.repository`  
 For products this then would be `product.repository`. Additional to that, you're going to need the `tax` repository later for this guide, so let's add this as well already.
 
-```xml
-// SwagBasicExample/src/Resources/config/services.xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\BasicExample\Service\WritingData" >
-            <argument type="service" id="product.repository"/>
-            <argument type="service" id="tax.repository"/>
-        </service>
-    </services>
-</container>
+```PHP
+// SwagBasicExample/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Service\WritingData;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(WritingData::class)
+        ->args([
+            service('product.repository'),
+            service('tax.repository'),
+        ]);
+};
 ```
 
 And here's the respective class including its constructor:
 
-```php
+```PHP
 // SwagBasicExample/src/Service/WritingData.php
 <?php declare(strict_types=1);
 
@@ -72,7 +76,7 @@ class WritingData
 }
 ```
 
-So we registered a custom service called `WritingData` and applied the repositories as a constructor parameter. If you want to fetch data for another entity, just switch the `id` in the `services.xml` to whatever repository you need, e.g. `order.repository` for orders.
+So we registered a custom service called `WritingData` and applied the repositories as a constructor parameter. If you want to fetch data for another entity, just switch the service reference in the `services.php` to whatever repository you need, e.g. `order.repository` for orders.
 
 ### Creating data
 
@@ -80,7 +84,7 @@ Now that you've injected the repositories into your service, you can start using
 
 Let's start with creating new data, a new product in this case:
 
-```php
+```PHP
 public function writeData(Context $context): void
 {
     $this->productRepository->create([
@@ -105,7 +109,7 @@ private function getTaxId(Context $context): string
 
 First of all, for this example you'll need the following new imports:
 
-```php
+```PHP
 use Shopware\Core\Defaults;
 use Shopware\Core\Framework\Context;
 use Shopware\Core\Framework\DataAbstractionLayer\Search\Criteria;
@@ -130,7 +134,7 @@ And that's it, this will write and create your first entity, a product. Of cours
 
 In Shopware 6 we're using UUIDs for the ID fields in the entities. This comes with a major advantage: You can define your IDs when creating an entity already and thus do not have to figure out which ID your newly created entity received, e.g. by auto-increment.
 
-```php
+```PHP
 public function writeData(): void
 {
     $context = Context::createDefaultContext();
@@ -164,7 +168,7 @@ So note the `id` field we've provided now - even though you're just creating you
 
 So what if you don't want to create a new entity, but rather update an existing one? For that case, you can use the `update` method on the repository. Let's just update our previously created product and change its name.
 
-```php
+```PHP
 public function writeData(Context $context): void
 {
     $criteria = new Criteria();
@@ -197,7 +201,7 @@ In order to create data, we've used the `create` method. For updating data, we'v
 
 Here's an example on how to delete the previously created product:
 
-```php
+```PHP
 public function writeData(Context $context): void
 {
     $criteria = new Criteria();
@@ -225,7 +229,7 @@ If you don't know how to add associations to an entity, maybe to your own entity
 
 Earlier in this guide, you created a product and used an existing tax entity for that case. This is representing a ManyToOne association, but OneToOne associations are handled the same.
 
-```php
+```PHP
 public function writeData(Context $context): void
 {
     $this->productRepository->create([
@@ -256,7 +260,7 @@ OneToMany and ManyToMany associations are handled the same.
 
 An example in the product context would be assigning a category to a product.
 
-```php
+```PHP
 public function writeData(Context $context): void
 {
     $criteria = new Criteria();
@@ -288,7 +292,7 @@ Every `ManyToMany` association comes with a mapping entity. It's important to kn
 
 The following example will fail:
 
-```php
+```PHP
 public function writeData(Context $context): void
 {
     // This is the product_category.repository service
@@ -309,7 +313,7 @@ Your only way to solve this is by replacing the association. Head over to our gu
 
 So you don't want to assign an existing tax entity when creating a product, but rather you'd like to create a new tax entity in the same step. That is also possible, and this section will show you an example on how to do it.
 
-```php
+```PHP
 public function writeData(Context $context): void
 {
     $this->productRepository->create([
@@ -330,7 +334,7 @@ In order to create a tax entity while creating the product, you have to provide
 
 And that's already it - now the tax will be created in the same step when the product is created and will be assigned automatically. This works almost the same for `ToMany` associations.
 
-```php
+```PHP
 public function writeData(Context $context): void
 {
     $this->productRepository->create([
diff --git a/guides/plugins/plugins/framework/event/finding-events.md b/guides/plugins/plugins/framework/event/finding-events.md
index 421154e622..787e19f6c8 100644
--- a/guides/plugins/plugins/framework/event/finding-events.md
+++ b/guides/plugins/plugins/framework/event/finding-events.md
@@ -33,7 +33,7 @@ Finding those "event classes" can be done by searching for the term `@Event` in
 
 You can use those events in a [subscriber](../../plugin-fundamentals/listening-to-events) like the following:
 
-```php
+```PHP
 public static function getSubscribedEvents(): array
 {
     return [
@@ -48,7 +48,7 @@ As you can see, you can either use the event class constants, if available, or t
 You'll then have access to several event specific information, e.g. your listener method will have access to an [EntityWrittenEvent](https://github.com/shopware/shopware/blob/v6.4.0.0/src/Core/Framework/DataAbstractionLayer/Event/EntityWrittenEvent.php)
 instance when subscribing to the `written` event.
 
-```php
+```PHP
 public function onCustomEntityWritten(EntityWrittenEvent $event): void
 {
 }
@@ -72,7 +72,7 @@ There are multiple ways to find them:
 You will most likely look into our Core code quite a lot, while trying to understand what's happening and why things are happening.
 On your journey looking through the code, you may stumble upon code looking like this:
 
-```php
+```PHP
 $someEvent = new SomeEvent($parameters, $moreParameters);
 $this->eventDispatcher->dispatch($someEvent, $someEvent->getName());
 ```
@@ -85,7 +85,7 @@ If the second parameter is not applied, the class name will be used as a fallbac
 
 When subscribing to those events, your event listener method will have access to the previously created event instance.
 
-```php
+```PHP
 public static function getSubscribedEvents(): array
 {
     return [
@@ -121,27 +121,30 @@ Every service, that wants to fire an event sooner or later, needs access to the
 Hence, you can have a look at all the service definitions for the [Dependency injection container](../../plugin-fundamentals/dependency-injection)
 and therefore quickly figure out, which services and classes are having access to the said `event_dispatcher`:
 
-```xml
-<?xml version="1.0" ?>
+```PHP
+<?php declare(strict_types=1);
 
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+use Some\Service;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
 
-    <services>
-        <service id="Some\Service">
-            <argument type="service" id="Another/Service"/>
-            <argument type="service" id="event_dispatcher"/>
-        </service>
-    </services>
-</container>
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(Service::class)
+        ->args([
+            service('Another/Service'),
+            service('event_dispatcher'),
+        ]);
+};
 ```
 
-Therefore, you could simply search for occurrences of the `event_dispatcher` in the respective `.xml` files.
+Therefore, you could simply search for occurrences of the `event_dispatcher` in the respective service definition files.
 
 You can also do this the other way around, by having a look at the service's constructor parameters.
 
-```php
+```PHP
 public function __construct(
     Some\Service $someService,
     EventDispatcherInterface $eventDispatcher
@@ -178,7 +181,7 @@ a `Criteria` instance.
 
 Let's have a look at an [example code](https://github.com/shopware/shopware/blob/v6.4.0.0/src/Core/Content/Product/SalesChannel/Listing/ResolveCriteriaProductListingRoute.php#L55-L59):
 
-```php
+```PHP
 #[Route(path: '/store-api/product-listing/{categoryId}', name: 'store-api.product.listing', methods: ['POST'], defaults: ['_entity' => 'product'])]
 public function load(string $categoryId, Request $request, SalesChannelContext $context, Criteria $criteria): ProductListingRouteResponse
 {
@@ -217,7 +220,7 @@ Therefore, we have added fine-grained route events that are thrown for every rou
 
 To subscribe to a specific event, replace the `{route}` placeholder with the [actual symfony route name](https://symfony.com/doc/current/routing.html), e.g. `store-api.product.listing`.
 
-```php
+```PHP
 public static function getSubscribedEvents(): array
 {
     return [
diff --git a/guides/plugins/plugins/framework/extension/creating-custom-extension.md b/guides/plugins/plugins/framework/extension/creating-custom-extension.md
index 22a8804f65..f86944f5a5 100644
--- a/guides/plugins/plugins/framework/extension/creating-custom-extension.md
+++ b/guides/plugins/plugins/framework/extension/creating-custom-extension.md
@@ -17,7 +17,7 @@ While Shopware provides many built-in extension points, you may need to create c
 
 All extension points must extend the base `Extension` class and define a typed result:
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace MyPlugin\Extension;
@@ -32,14 +32,14 @@ use Shopware\Core\Framework\Log\Package;
 final class MyCustomExtension extends Extension
 {
     public const NAME = 'my-plugin.custom-extension';
-    
+
     public function __construct(
         /**
          * @public
          * @description Input data for processing
          */
         public readonly array $inputData,
-        
+
         /**
          * @public
          * @description Context for the operation
@@ -63,7 +63,7 @@ Let's create a custom extension point for filtering products based on custom bus
 
 ### 1. Define the Extension Class
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace MyPlugin\Extension;
@@ -83,20 +83,20 @@ use Shopware\Core\System\SalesChannel\SalesChannelContext;
 final class CustomProductFilterExtension extends Extension
 {
     public const NAME = 'my-plugin.product-filter';
-    
+
     public function __construct(
         /**
          * @public
          * @description The search criteria for products
          */
         public readonly Criteria $criteria,
-        
+
         /**
          * @public
          * @description The sales channel context
          */
         public readonly SalesChannelContext $context,
-        
+
         /**
          * @public
          * @description Custom filter parameters
@@ -109,7 +109,7 @@ final class CustomProductFilterExtension extends Extension
 
 ### 2. Create the Service that Dispatches the Extension
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace MyPlugin\Service;
@@ -132,7 +132,7 @@ class CustomProductService
         private readonly EntityRepository $productRepository
     ) {
     }
-    
+
     public function filterProducts(
         Criteria $criteria,
         SalesChannelContext $context,
@@ -143,7 +143,7 @@ class CustomProductService
             $context,
             $filterParams
         );
-        
+
         return $this->extensionDispatcher->publish(
             CustomProductFilterExtension::NAME,
             $extension,
@@ -158,7 +158,7 @@ class CustomProductService
 
 ### 3. Create an Event Subscriber
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace MyPlugin\Subscriber;
@@ -173,28 +173,28 @@ class CustomProductFilterSubscriber implements EventSubscriberInterface
         private readonly ProductFilterService $filterService
     ) {
     }
-    
+
     public static function getSubscribedEvents(): array
     {
         return [
             'my-plugin.product-filter.pre' => 'onProductFilter',
         ];
     }
-    
+
     public function onProductFilter(CustomProductFilterExtension $event): void
     {
         // Check if we should apply custom filtering
         if (!$this->shouldApplyCustomFilter($event->filterParams)) {
             return;
         }
-        
+
         // Get filtered product IDs from external API
         $filteredIds = $this->apiService->getFilteredProductIds(
             $event->criteria,
             $event->context,
             $event->filterParams
         );
-        
+
         if (empty($filteredIds)) {
             // No products match the filter
             $event->result = new EntitySearchResult(
@@ -208,21 +208,21 @@ class CustomProductFilterSubscriber implements EventSubscriberInterface
             $event->stopPropagation();
             return;
         }
-        
+
         // Create new criteria with filtered IDs
         $newCriteria = clone $event->criteria;
         $newCriteria->setIds($filteredIds);
-        
+
         // Apply additional filtering
         $filteredProducts = $this->filterService->applyBusinessRules(
             $newCriteria,
             $event->context
         );
-        
+
         $event->result = $filteredProducts;
         $event->stopPropagation();
     }
-    
+
     private function shouldApplyCustomFilter(array $filterParams): bool
     {
         return isset($filterParams['custom_filter']) && $filterParams['custom_filter'] === true;
@@ -232,32 +232,34 @@ class CustomProductFilterSubscriber implements EventSubscriberInterface
 
 ### 4. Register Services
 
-```xml
-<!-- services.xml -->
-<service id="MyPlugin\Service\CustomProductService">
-    <argument type="service" id="Shopware\Core\Framework\Extensions\ExtensionDispatcher"/>
-    <argument type="service" id="product.repository"/>
-</service>
-
-<service id="MyPlugin\Subscriber\CustomProductFilterSubscriber">
-    <argument type="service" id="MyPlugin\Service\ExternalApiService"/>
-    <argument type="service" id="MyPlugin\Service\ProductFilterService"/>
-    <tag name="kernel.event_subscriber"/>
-</service>
+```PHP
+// services.php
+$services->set(MyPlugin\Service\CustomProductService::class)
+    ->args([
+        service(Shopware\Core\Framework\Extensions\ExtensionDispatcher::class),
+        service('product.repository'),
+    ]);
+
+$services->set(MyPlugin\Subscriber\CustomProductFilterSubscriber::class)
+    ->args([
+        service(MyPlugin\Service\ExternalApiService::class),
+        service(MyPlugin\Service\ProductFilterService::class),
+    ])
+    ->tag('kernel.event_subscriber');
 ```
 
 ## Advanced Extension Patterns
 
 ### 1. Conditional Extension Execution
 
-```php
+```PHP
 public function onExtension(MyExtension $event): void
 {
     // Only execute under certain conditions
     if (!$this->shouldExecute($event)) {
         return;
     }
-    
+
     $event->result = $this->customImplementation($event);
     $event->stopPropagation();
 }
@@ -270,7 +272,7 @@ private function shouldExecute(MyExtension $event): bool
 
 ### 2. Extension with Error Handling
 
-```php
+```PHP
 public function onExtension(MyExtension $event): void
 {
     try {
@@ -282,7 +284,7 @@ public function onExtension(MyExtension $event): void
             'error' => $e->getMessage(),
             'extension' => get_class($event)
         ]);
-        
+
         // The extension system will handle the error
         // and potentially dispatch error events
     }
@@ -291,7 +293,7 @@ public function onExtension(MyExtension $event): void
 
 ### 3. Extension with Data Enrichment
 
-```php
+```PHP
 public function onExtension(MyExtension $event): void
 {
     // Don't replace the result, just enrich it
@@ -308,14 +310,14 @@ private function enrichResult($result, MyExtension $event)
         'processedAt' => new \DateTime(),
         'context' => $event->context->getSalesChannelId()
     ]));
-    
+
     return $result;
 }
 ```
 
 ### 4. Multi-Phase Extension
 
-```php
+```PHP
 public static function getSubscribedEvents(): array
 {
     return [
@@ -416,12 +418,12 @@ Use `.error` events to:
 
 Here's a complete example of a plugin that creates and uses a custom extension point:
 
-```php
+```PHP
 // 1. Extension class
 final class ProductRecommendationExtension extends Extension
 {
     public const NAME = 'my-plugin.product-recommendation';
-    
+
     public function __construct(
         public readonly ProductEntity $product,
         public readonly SalesChannelContext $context,
@@ -435,7 +437,7 @@ class ProductRecommendationService
     public function getRecommendations(ProductEntity $product, SalesChannelContext $context): ProductCollection
     {
         $extension = new ProductRecommendationExtension($product, $context);
-        
+
         return $this->extensionDispatcher->publish(
             ProductRecommendationExtension::NAME,
             $extension,
@@ -456,7 +458,7 @@ class ProductRecommendationSubscriber implements EventSubscriberInterface
             'my-plugin.product-recommendation.pre' => 'onGetRecommendations',
         ];
     }
-    
+
     public function onGetRecommendations(ProductRecommendationExtension $event): void
     {
         // Custom AI-powered recommendations
@@ -465,7 +467,7 @@ class ProductRecommendationSubscriber implements EventSubscriberInterface
             $event->context,
             $event->limit
         );
-        
+
         $event->result = $recommendations;
         $event->stopPropagation();
     }
diff --git a/guides/plugins/plugins/framework/extension/finding-extensions.md b/guides/plugins/plugins/framework/extension/finding-extensions.md
index 9bff01776a..b4bc923b82 100644
--- a/guides/plugins/plugins/framework/extension/finding-extensions.md
+++ b/guides/plugins/plugins/framework/extension/finding-extensions.md
@@ -42,7 +42,7 @@ Here are some common Extension Point you might encounter:
 
 #### Product Extensions
 
-```php
+```PHP
 // Product price calculation
 src/Core/Content/Product/Extension/ProductPriceCalculationExtension.php
 
@@ -55,7 +55,7 @@ src/Core/Content/Product/Extension/ProductListingCriteriaExtension.php
 
 #### Cart Extensions
 
-```php
+```PHP
 // Checkout place order
 src/Core/Checkout/Cart/Extension/CheckoutPlaceOrderExtension.php
 
@@ -65,7 +65,7 @@ src/Core/Checkout/Cart/Extension/CheckoutCartRuleLoaderExtension.php
 
 #### CMS Extensions
 
-```php
+```PHP
 // CMS slots data enrichment
 src/Core/Content/Cms/Extension/CmsSlotsDataEnrichExtension.php
 
@@ -81,11 +81,11 @@ Extension Points follow a consistent naming pattern:
 
 Extension Points use a `NAME` constant that defines the event name:
 
-```php
+```PHP
 final class ResolveListingExtension extends Extension
 {
     public const NAME = 'listing-loader.resolve';
-    
+
     // ...
 }
 ```
@@ -95,7 +95,7 @@ final class ResolveListingExtension extends Extension
 Extension Points are dispatched with lifecycle suffixes:
 
 - `{name}.pre` - Before the default implementation
-- `{name}.post` - After the default implementation  
+- `{name}.post` - After the default implementation
 - `{name}.error` - When an error occurs
 
 ## Finding Extension Usage
@@ -104,17 +104,16 @@ Extension Points are dispatched with lifecycle suffixes:
 
 Services that use Extension Points typically inject the `ExtensionDispatcher`:
 
-```xml
-<service id="Some\Service">
-    <argument type="service" id="Shopware\Core\Framework\Extensions\ExtensionDispatcher"/>
-</service>
+```PHP
+$services->set(Some\Service::class)
+    ->args([service(Shopware\Core\Framework\Extensions\ExtensionDispatcher::class)]);
 ```
 
 ### In Constructor Parameters
 
 Look for services that inject the `ExtensionDispatcher`:
 
-```php
+```PHP
 public function __construct(
     private readonly ExtensionDispatcher $extensionDispatcher
 ) {
@@ -125,7 +124,7 @@ public function __construct(
 
 Extension Points are typically dispatched using this pattern:
 
-```php
+```PHP
 $extension = new SomeExtension($parameters);
 $result = $this->extensionDispatcher->publish(
     SomeExtension::NAME,
@@ -147,11 +146,11 @@ $result = $this->extensionDispatcher->publish(
 **Event Name**: `product.calculate-prices`
 **Return Type**: `void`
 
-```php
+```PHP
 final class ProductPriceCalculationExtension extends Extension
 {
     public const NAME = 'product.calculate-prices';
-    
+
     public function __construct(
         public readonly iterable $products,
         public readonly SalesChannelContext $context
@@ -165,11 +164,11 @@ final class ProductPriceCalculationExtension extends Extension
 **Event Name**: `listing-loader.resolve`
 **Return Type**: `EntitySearchResult<ProductCollection>`
 
-```php
+```PHP
 final class ResolveListingExtension extends Extension
 {
     public const NAME = 'listing-loader.resolve';
-    
+
     public function __construct(
         public readonly Criteria $criteria,
         public readonly SalesChannelContext $context
@@ -185,11 +184,11 @@ final class ResolveListingExtension extends Extension
 **Event Name**: `checkout.place-order`
 **Return Type**: `OrderPlaceResult`
 
-```php
+```PHP
 final class CheckoutPlaceOrderExtension extends Extension
 {
     public const NAME = 'checkout.place-order';
-    
+
     public function __construct(
         public readonly Cart $cart,
         public readonly SalesChannelContext $context
@@ -205,11 +204,11 @@ final class CheckoutPlaceOrderExtension extends Extension
 **Event Name**: `cms.slots.data-enrich`
 **Return Type**: `CmsSlotCollection`
 
-```php
+```PHP
 final class CmsSlotsDataEnrichExtension extends Extension
 {
     public const NAME = 'cms.slots.data-enrich';
-    
+
     public function __construct(
         public readonly CmsSlotCollection $slots,
         public readonly SalesChannelContext $context
@@ -223,7 +222,7 @@ final class CmsSlotsDataEnrichExtension extends Extension
 
 Create an event subscriber to listen for Extension Points:
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace MyPlugin\Subscriber;
@@ -239,7 +238,7 @@ class ProductListingSubscriber implements EventSubscriberInterface
             'listing-loader.resolve.pre' => 'onResolveListing',
         ];
     }
-    
+
     public function onResolveListing(ResolveListingExtension $event): void
     {
         // Custom logic here
@@ -253,10 +252,9 @@ class ProductListingSubscriber implements EventSubscriberInterface
 
 Register your subscriber in the service configuration:
 
-```xml
-<service id="MyPlugin\Subscriber\ProductListingSubscriber">
-    <tag name="kernel.event_subscriber"/>
-</service>
+```PHP
+$services->set(MyPlugin\Subscriber\ProductListingSubscriber::class)
+    ->tag('kernel.event_subscriber');
 ```
 
 ## Extension Lifecycle
@@ -270,7 +268,7 @@ Extension Points follow a specific lifecycle:
 
 ### Lifecycle Example
 
-```php
+```PHP
 public function handleExtension(SomeExtension $event): void
 {
     // This runs in the .pre phase
@@ -293,7 +291,7 @@ public function handlePostExtension(SomeExtension $event): void
 
 Always use proper type hints for Extension Point parameters:
 
-```php
+```PHP
 public function onResolveListing(ResolveListingExtension $event): void
 {
     // Type-safe access to properties
@@ -306,14 +304,14 @@ public function onResolveListing(ResolveListingExtension $event): void
 
 Check if a result has already been set:
 
-```php
+```PHP
 public function onExtension(SomeExtension $event): void
 {
     if ($event->result !== null) {
         // Another extension already provided a result
         return;
     }
-    
+
     $event->result = $this->myImplementation($event);
 }
 ```
@@ -322,7 +320,7 @@ public function onExtension(SomeExtension $event): void
 
 Only stop propagation when you're providing a complete replacement:
 
-```php
+```PHP
 public function onExtension(SomeExtension $event): void
 {
     if ($this->shouldReplaceDefault($event)) {
@@ -337,7 +335,7 @@ public function onExtension(SomeExtension $event): void
 
 Extension Points have built-in error handling, but you can also handle errors gracefully:
 
-```php
+```PHP
 public function onExtension(SomeExtension $event): void
 {
     try {
@@ -360,7 +358,7 @@ The Symfony profiler shows all dispatched Extension Points in the "Events" tab.
 
 You can log Extension Point calls to understand the flow:
 
-```php
+```PHP
 public function onExtension(SomeExtension $event): void
 {
     $this->logger->debug('Extension called', [
diff --git a/guides/plugins/plugins/framework/filesystem/filesystem.md b/guides/plugins/plugins/framework/filesystem/filesystem.md
index 5e3028f755..a56e418bc9 100644
--- a/guides/plugins/plugins/framework/filesystem/filesystem.md
+++ b/guides/plugins/plugins/framework/filesystem/filesystem.md
@@ -34,7 +34,7 @@ However, every plugin/bundle gets an own namespace that should be used for priva
 
 To make use of the filesystem, we register a new service, which helps to read and write files to the filesystem.
 
-```php
+```PHP
 // <plugin root>/src/Service/ExampleFilesystemService.php
 <?php declare(strict_types=1);
 
@@ -80,25 +80,29 @@ class ExampleFilesystemService
 
 This service makes use of the private und public filesystem. As you already know, this php class has to be registered as a service in the dependency injection container. This is also the place where we define which filesystem will be handed over to the constructor. To make use of the plugin private and public files, the service definition could look like this:
 
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\BasicExample\Service\ExampleFilesystemService">
-            <argument type="service" id="swag_basic_example.filesystem.public"/>
-            <argument type="service" id="swag_basic_example.filesystem.private"/>
-            <!--
-            There are also predefined file system services
-            <argument type="service" id="shopware.filesystem.private"/>
-            <argument type="service" id="shopware.filesystem.public"/>
-            -->
-        </service>
-    </services>
-</container>
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Service\ExampleFilesystemService;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(ExampleFilesystemService::class)
+        ->args([
+            service('swag_basic_example.filesystem.public'),
+            service('swag_basic_example.filesystem.private'),
+        ]);
+        // There are also predefined file system services:
+        // ->args([
+        //     service('shopware.filesystem.private'),
+        //     service('shopware.filesystem.public'),
+        // ])
+};
 ```
 
 Now, this service can be used to read or write files to the private plugin filesystem or to list all files in the public plugin filesystem. You should visit the [Flysystem API documentation](https://flysystem.thephpleague.com/docs/usage/filesystem-api/) for more information.
diff --git a/guides/plugins/plugins/framework/flow/add-flow-builder-action.md b/guides/plugins/plugins/framework/flow/add-flow-builder-action.md
index bfc7f40e32..ad85cb5bf7 100644
--- a/guides/plugins/plugins/framework/flow/add-flow-builder-action.md
+++ b/guides/plugins/plugins/framework/flow/add-flow-builder-action.md
@@ -33,7 +33,7 @@ To create a custom flow action, firstly you have to make a plugin and install it
 
  First of all, we need to define an aware interface for your own action. I intended to create the `CreateTagAction`, so I need to create a related aware named `TagAware`, will be placed in directory `<plugin root>/src/Core/Framework/Event`. Our new interface has to extend from interfaces `Shopware\Core\Framework\Event\FLowEventAware`:
 
-```php
+```PHP
 // <plugin root>/src/Core/Framework/Event/TagAware.php
 <?php declare(strict_types=1);
 namespace Swag\ExamplePlugin\Core\Framework\Event;
@@ -59,7 +59,7 @@ interface TagAware extends FlowEventAware
 
 In this example, we will name it `CreateTagAction`. It will be placed in the directory `<plugin root>/src/Core/Content/Flow/Dispatching/Action`. Below you can find an example implementation:
 
-```php
+```PHP
 // <plugin root>/src/Core/Content/Flow/Dispatching/Action/CreateTagAction.php
 <?php declare(strict_types=1);
 
@@ -138,14 +138,13 @@ As you can see, several methods are already implemented:
     - Use `$flow->getStore($key)` if you want to get the data from aware interfaces. E.g: `tag_id` in `TagAware`, `customer_id` from `CustomerAware` and so on.
     - Use `$flow->getData($key)` if you want to get the data from original events or additional data. E.g: `tag`, `customer`, `contactFormData` and so on.
 
-You also need to register this action in the container as a service. Make sure to define a tag `<tag name="flow.action" priority="600">` at `<plugin root>/src/Resources/config/services.xml`. This tag will ensure that your action is included in the response of the *`/api/_info/flow-actions.json`* API. The priority attribute will determine the order of the action in the API response.
+You also need to register this action in the container as a service. Make sure to define a tag `flow.action` with `priority: 600` at `<plugin root>/src/Resources/config/services.php`. This tag will ensure that your action is included in the response of the *`/api/_info/flow-actions.json`* API. The priority attribute will determine the order of the action in the API response.
 
-```XML
-// <plugin root>/src/Resources/config/services.xml
-<service id="Swag\CreateTagAction\Core\Content\Flow\Dispatching\Action\CreateTagAction">
-    <argument type="service" id="tag.repository" />
-    <tag name="flow.action" priority="600" key="action.create.tag"/>
-</service>
+```PHP
+// <plugin root>/src/Resources/config/services.php
+$services->set(Swag\CreateTagAction\Core\Content\Flow\Dispatching\Action\CreateTagAction::class)
+    ->args([service('tag.repository')])
+    ->tag('flow.action', ['priority' => 600, 'key' => 'action.create.tag']);
 ```
 
 Great, your own action is created completely. Let's go to the next step.
@@ -163,7 +162,7 @@ There are three scopes for the `CreateTagAction`:
 
 - Just define the empty array in `CreateTagAction::requirements`
 
-```php
+```PHP
     // plugin root>/src/Core/Content/Flow/Dispatching/Action/CreateTagAction.php
     ...
 
@@ -185,7 +184,7 @@ Here, the action name is empty as the action name snippet is not yet defined.
 
 Make the `CreateTagAction` available for all events related to Order and Customer.
 
-```php
+```PHP
     // <plugin root>/src/Core/Content/Flow/Dispatching/Action/CreateTagAction.php
     ...
 
@@ -203,7 +202,7 @@ Make the `CreateTagAction` available for all events related to Order and Custome
 
 - Event must implement the `TagAware`
 
-```php
+```PHP
 // <plugin root>/src/Core/Content/Flow/Subscriber/BusinessEventCollectorSubscriber.php
 <?php declare(strict_types=1);
 
@@ -256,7 +255,7 @@ class BasicExampleEvent extends Event implements TagAware
 
 - Define the `TagAware` in `CreateTagAction::requirements`
 
-```php
+```PHP
     // <plugin root>/src/Core/Content/Flow/Dispatching/Action/CreateTagAction.php
     ...
 
@@ -270,7 +269,7 @@ class BasicExampleEvent extends Event implements TagAware
 
 - To show the new event in Flow Builder Triggers list
 
-```php
+```PHP
 // <plugin root>/src/Core/Content/Subscriber/BusinessEventCollectorSubscriber.php
 <?php declare(strict_types=1);
 namespace Swag\CreateTagAction\Core\Content\Subscriber;
@@ -311,18 +310,18 @@ class BusinessEventCollectorSubscriber implements EventSubscriberInterface
 }
 ```
 
-And don't forget to register your subscriber to the container at `<plugin root>/src/Resources/config/services.xml`.
+And don't forget to register your subscriber to the container at `<plugin root>/src/Resources/config/services.php`.
 
-```xml
-<service id="Swag\CreateTagAction\Core\Content\Subscriber\BusinessEventCollectorSubscriber">
-    <argument type="service" id="Shopware\Core\Framework\Event\BusinessEventCollector"/>
-    <tag name="kernel.event_subscriber"/>
-</service>
+```PHP
+
+$services->set(Swag\CreateTagAction\Core\Content\Subscriber\BusinessEventCollectorSubscriber::class)
+    ->args([service(Shopware\Core\Framework\Event\BusinessEventCollector::class)])
+    ->tag('kernel.event_subscriber');
 ```
 
 - Define the Event snippet
 
-```json
+```JSON
 // <plugin root>/src/Resources/app/administration/src/module/sw-flow/snippet/en-GB.json
 {
   "sw-flow": {
@@ -421,7 +420,7 @@ Component.override('sw-flow-sequence-action', {
             }
             return this.$super('getActionDescriptions', sequence)
         },
-        
+
         getCreateTagDescription(config) {
             const tags = config.tags.join(', ');
 
diff --git a/guides/plugins/plugins/framework/flow/add-flow-builder-trigger.md b/guides/plugins/plugins/framework/flow/add-flow-builder-trigger.md
index 4629c278a4..367a04fa27 100644
--- a/guides/plugins/plugins/framework/flow/add-flow-builder-trigger.md
+++ b/guides/plugins/plugins/framework/flow/add-flow-builder-trigger.md
@@ -52,7 +52,7 @@ In this example, we will name it ExampleEvent to some actions related to custome
 
 Below you can find an example implementation:
 
-```php
+```PHP
 // <plugin root>/src/Core/Checkout/Customer/Event/ExampleEvent.php
 <?php declare(strict_types=1);
 
@@ -137,7 +137,7 @@ You could read here more about the [Storer](../../../../../concepts/framework/fl
 | Shopware\Core\Framework\Event\ProductAware | Shopware\Core\Content\Flow\Dispatching\Storer\ProductStorer |
 | Shopware\Core\Framework\Event\UserAware | Shopware\Core\Content\Flow\Dispatching\Storer\UserStorer |
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace Swag\ExamplePlugin\Core\Checkout\Customer\Event;
@@ -184,7 +184,7 @@ class ExampleEvent extends Event implements CustomerAware, ShopNameAware
 
 In the example above, to get the `customerId` and `shopName` data events, you need to store these data via `CustomerStorer` and `ShopNameStorer`.
 
-```php
+```PHP
 class CustomerStorer extends FlowStorer
 {
 	public function store(FlowEventAware $event, array $stored): array
@@ -210,13 +210,13 @@ class CustomerStorer extends FlowStorer
 	private function getCustomer(string $customerId): Customer
 	{
 		// load customer via $customerId
-		
+
 		return $customer;
 	}
 }
 ```
 
-```php
+```PHP
 class ShopNameStorer extends FlowStorer
 {
     public function store(FlowEventAware $event, array $stored): array
@@ -243,7 +243,7 @@ class ShopNameStorer extends FlowStorer
 
 We already have Aware interfaces, but if you want to use the custom data that is not available, you can define a new Aware interface and a Storer respectively.
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace Swag\ExamplePlugin\Core\Checkout\Customer\Event;
@@ -282,7 +282,7 @@ class ExampleEvent extends Event implements CustomExampleDataAware
 
 Aware:
 
-```php
+```PHP
 #[IsFlowEventAware]
 interface CustomExampleDataAware extends FlowEventAware
 {
@@ -294,7 +294,7 @@ interface CustomExampleDataAware extends FlowEventAware
 
 Storer respective:
 
-```php
+```PHP
 class CustomExampleDataStorer extends FlowStorer
 {
     public function store(FlowEventAware $event, array $stored): array
@@ -321,7 +321,7 @@ class CustomExampleDataStorer extends FlowStorer
 
 In Flow Actions, you can get the data easily via `getStore` and `getData`.
 
-```php
+```PHP
 class SendMailAction
 {
 	public function handleFlow(StorableFlow $flow)
@@ -339,7 +339,7 @@ Take a look at the [Add Flow Builder Action](../../../../../guides/plugins/plugi
 
 At this step, you need to add your new event to the flow trigger list, let us see the code below:
 
-```php
+```PHP
 // <plugin root>/src/Core/Checkout/Customer/Subscriber/BusinessEventCollectorSubscriber.php
 <?php declare(strict_types=1);
 
@@ -382,7 +382,7 @@ class BusinessEventCollectorSubscriber implements EventSubscriberInterface
 
 Please note that your subscriber has to have a higher priority point to ensure your event is added before any subscriber `BusinessEventCollectorEvent` to prevent missing awareness or action. I set 1000 for `onAddExampleEvent` action:
 
-```php
+```PHP
 // <plugin root>/src/Core/Checkout/Customer/Subscriber/BusinessEventCollectorSubscriber.php
 public static function getSubscribedEvents()
 {
@@ -392,14 +392,13 @@ public static function getSubscribedEvents()
 }
 ```
 
-And remember to register your subscriber to the container at `<plugin root>/src/Resources/config/services.xml`
+And remember to register your subscriber to the container at `<plugin root>/src/Resources/config/services.php`
 
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<service id="Swag\ExamplePlugin\Core\Checkout\Customer\Subscriber\BusinessEventCollectorSubscriber">
-    <argument type="service" id="Shopware\Core\Framework\Event\BusinessEventCollector"/>
-    <tag name="kernel.event_subscriber"/>
-</service>
+```PHP
+// <plugin root>/src/Resources/config/services.php
+$services->set(Swag\ExamplePlugin\Core\Checkout\Customer\Subscriber\BusinessEventCollectorSubscriber::class)
+    ->args([service(Shopware\Core\Framework\Event\BusinessEventCollector::class)])
+    ->tag('kernel.event_subscriber');
 ```
 
 Well done, you have successfully created your own flow trigger.
diff --git a/guides/plugins/plugins/framework/rule/add-custom-rules.md b/guides/plugins/plugins/framework/rule/add-custom-rules.md
index 0b1516632d..64edc5a371 100644
--- a/guides/plugins/plugins/framework/rule/add-custom-rules.md
+++ b/guides/plugins/plugins/framework/rule/add-custom-rules.md
@@ -29,7 +29,7 @@ To create a custom rule, we have to implement both backend \(PHP\) code and a us
 
 First of all, we need a new Rule class. In this example, we name it as `FirstMondayOfTheMonthRule`. It will be placed in the directory `<plugin root>/src/Core/Rule`. Our new class has to extend from the abstract class `Shopware\Core\Framework\Rule\Rule`. Below you can find an example implementation.
 
-```php
+```PHP
 // <plugin root>/src/Core/Rule/FirstMondayOfTheMonthRule.php
 <?php declare(strict_types=1);
 
@@ -106,14 +106,14 @@ As you can see, several methods are already implemented:
 * `match`: This checks whether the rule applies. Accordingly, a boolean is returned whether the rule applies or not.
 * `getConstraints`: This method returns an array of the possible fields and its types. You could also return the `NotBlank` class here, to require this field.
 
-After we've created our rule class, we have to register it in our `services.xml` and tag it as `shopware.rule.definition`.
+After we've created our rule class, we have to register it in our `services.php` and tag it as `shopware.rule.definition`.
 Please keep in mind: The variables to be used in the rule have to be 'protected' and not 'private', otherwise they won't work properly.
 
 ::: warning
 Never execute database queries or any other time-consuming operations within the `match()` method of your rule, as it will drastically impact the performance of your store. Stick to the rule scope when evaluating whether your rule matches or not.
 :::
 
-```php
+```PHP
 // Scope usage: Check if the customer is logged in
 $customer = $scope->getSalesChannelContext()->getCustomer();
 $loggedIn = $customer !== null;
@@ -121,7 +121,7 @@ $loggedIn = $customer !== null;
 
 It is possible to add config to our rule. This makes it possible to skip the [Custom rule component](#custom-rule-component) and the [Custom rule Administration template](#custom-rule-administration-template) parts.
 
-```php
+```PHP
     public function getConfig(): RuleConfig
     {
         return (new RuleConfig())->booleanField('isFirstMondayOfTheMonth');
@@ -134,7 +134,7 @@ when [Showing rule in the Administration](#showing-rule-in-the-administration) w
 
 You can access all active rules by using the `getRuleIds` method of the context.
 
-```php
+```PHP
 $context->getRuleIds();
 ```
 
diff --git a/guides/plugins/plugins/framework/store-api/add-store-api-route.md b/guides/plugins/plugins/framework/store-api/add-store-api-route.md
index eb736b4561..5b7320fd55 100644
--- a/guides/plugins/plugins/framework/store-api/add-store-api-route.md
+++ b/guides/plugins/plugins/framework/store-api/add-store-api-route.md
@@ -29,7 +29,7 @@ All fields that should be available through the API require the flag `ApiAware`
 
 First of all, we create an abstract class called `AbstractExampleRoute`. This class has to contain a method `getDecorated` and a method `load` with a `Criteria` and `SalesChannelContext` as parameter. The `load` method has to return an instance of `ExampleRouteResponse`, which we will create later on.
 
-```php
+```PHP
 // <plugin root>/src/Core/Content/Example/SalesChannel/AbstractExampleRoute.php
 <?php declare(strict_types=1);
 
@@ -50,7 +50,7 @@ abstract class AbstractExampleRoute
 
 Now we can create a new class `ExampleRoute` which uses our previously created `AbstractExampleRoute`.
 
-```php
+```PHP
 // <plugin root>/src/Core/Content/Example/SalesChannel/ExampleRoute.php
 <?php declare(strict_types=1);
 
@@ -95,25 +95,27 @@ The `_entity` in the defaults of the `Route` attribute just marks the entity tha
 
 ### Register route class
 
-```xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\BasicExample\Core\Content\Example\SalesChannel\ExampleRoute" >
-            <argument type="service" id="swag_example.repository"/>
-        </service>
-    </services>
-</container>
+```PHP
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Core\Content\Example\SalesChannel\ExampleRoute;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(ExampleRoute::class)
+        ->args([service('swag_example.repository')]);
+};
 ```
 
 ### Route response
 
 After we have created our route, we need to create the mentioned `ExampleRouteResponse`. This class should extend from `Shopware\Core\System\SalesChannel\StoreApiResponse`, consequently inheriting a property `$object` of type `Shopware\Core\Framework\DataAbstractionLayer\Search\EntitySearchResult`. The `StoreApiResponse` parent constructor takes accepts one argument `$object` in order to set the value for the `$object` property (currently we provide this parameter our `ExampleRoute`). Finally, we add a method `getExamples` in which we return our entity collection that we got from the object.
 
-```php
+```PHP
 // <plugin root>/src/Core/Content/Example/SalesChannel/ExampleRouteResponse.php
 <?php declare(strict_types=1);
 
@@ -138,18 +140,17 @@ class ExampleRouteResponse extends StoreApiResponse
 
 ## Register route
 
-The last thing we need to do now is to tell Shopware how to look for new routes in our plugin. This is done with a `routes.xml` file at `<plugin root>/src/Resources/config/` location. Have a look at the official [Symfony documentation](https://symfony.com/doc/current/routing.html) about routes and how they are registered.
+The last thing we need to do now is to tell Shopware how to look for new routes in our plugin. This is done with a `routes.php` file at `<plugin root>/src/Resources/config/` location. Take a look at the official [Symfony documentation](https://symfony.com/doc/current/routing.html) about routes and how they are registered.
+
+```PHP
+// <plugin root>/src/Resources/config/routes.php
+<?php declare(strict_types=1);
 
-```xml
-// <plugin root>/src/Resources/config/routes.xml
-<?xml version="1.0" encoding="UTF-8" ?>
-<routes xmlns="http://symfony.com/schema/routing"
-        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-        xsi:schemaLocation="http://symfony.com/schema/routing
-        https://symfony.com/schema/routing/routing-1.0.xsd">
+use Symfony\Component\Routing\Loader\Configurator\RoutingConfigurator;
 
-    <import resource="../../Core/**/*Route.php" type="attribute" />
-</routes>
+return static function (RoutingConfigurator $routes): void {
+    $routes->import('../../Core/**/*Route.php', 'attribute');
+};
 ```
 
 ## Check route via Symfony debugger
@@ -157,7 +158,7 @@ The last thing we need to do now is to tell Shopware how to look for new routes
 To check if your route was registered correctly, you can use the [Symfony route debugger](https://symfony.com/doc/current/routing.html#debugging-routes).
 
 ```bash
-// 
+//
 $ ./bin/console debug:router store-api.example.search
 ```
 
@@ -165,7 +166,7 @@ $ ./bin/console debug:router store-api.example.search
 
 To add the route to the Stoplight page, a JSON file is needed in a specific [format](https://swagger.io/specification/#paths-object). It contains information about the paths, methods, parameters, and more. You must place the JSON file in `<plugin root>/src/Resources/Schema/StoreApi/` so the shopware internal OpenApi3Generator can find it (for Admin API endpoints, use `AdminApi`).
 
-```javascript
+```JAVASCRIPT
 // <plugin root>/src/Resources/Schema/StoreApi/example.json
 {
   "openapi": "3.0.0",
@@ -225,7 +226,7 @@ Your generated request and response could look like this:
 
 #### Request
 
-```json
+```JSON
 {
   "page": 0,
   "limit": 0,
@@ -277,7 +278,7 @@ Your generated request and response could look like this:
 
 #### Response
 
-```json
+```JSON
 {
   "total": 0,
   "aggregations": {},
@@ -298,7 +299,7 @@ Your generated request and response could look like this:
 
 If you want to access the functionality of your route also from the Storefront you need to make it available there by adding a custom [Storefront controller](../../storefront/add-custom-controller) that will wrap your just created route.
 
-```php
+```PHP
 // <plugin root>/src/Storefront/Controller/ExampleController.php
 <?php declare(strict_types=1);
 
@@ -336,42 +337,41 @@ Additionally, we also use the `'XmlHttpRequest' => true` config option on the ro
 
 ### Register the Controller
 
-```xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\BasicExample\Core\Content\Example\SalesChannel\ExampleRoute" >
-            <argument type="service" id="swag_example.repository"/>
-        </service>
-    
-        <service id="Swag\BasicExample\Storefront\Controller\ExampleController" >
-            <argument type="service" id="Swag\BasicExample\Core\Content\Example\SalesChannel\ExampleRoute"/>
-            <call method="setContainer">
-                <argument type="service" id="service_container"/>
-            </call>
-        </service>
-    </services>
-</container>
+```PHP
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Core\Content\Example\SalesChannel\ExampleRoute;
+use Swag\BasicExample\Storefront\Controller\ExampleController;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(ExampleRoute::class)
+        ->args([service('swag_example.repository')]);
+
+    $services->set(ExampleController::class)
+        ->args([service(ExampleRoute::class)])
+        ->call('setContainer', [service('service_container')]);
+};
 ```
 
 ### Register Storefront api-route
 
-We need to tell Shopware that there is a new API-route for the `storefront` scope by extending the `routes.xml` to also include all Storefront controllers.
+We need to tell Shopware that there is a new API-route for the `storefront` scope by extending the `routes.php` to also include all Storefront controllers.
+
+```PHP
+// <plugin root>/src/Resources/config/routes.php
+<?php declare(strict_types=1);
 
-```xml
-// <plugin root>/src/Resources/config/routes.xml
-<?xml version="1.0" encoding="UTF-8" ?>
-<routes xmlns="http://symfony.com/schema/routing"
-        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-        xsi:schemaLocation="http://symfony.com/schema/routing
-        https://symfony.com/schema/routing/routing-1.0.xsd">
+use Symfony\Component\Routing\Loader\Configurator\RoutingConfigurator;
 
-    <import resource="../../Core/**/*Route.php" type="attribute" />
-    <import resource="../../Storefront/**/*Controller.php" type="attribute" />
-</routes>
+return static function (RoutingConfigurator $routes): void {
+    $routes->import('../../Core/**/*Route.php', 'attribute');
+    $routes->import('../../Storefront/**/*Controller.php', 'attribute');
+};
 ```
 
 ### Requesting your route from the Storefront
@@ -381,7 +381,7 @@ We expect that you have followed that guide and know how to register your custom
 
 When you want to request your custom route you can use the existing `http-client` service for that.
 
-```javascript
+```JAVASCRIPT
 // <plugin root>/src/Resources/app/storefront/src/example-plugin/example-plugin.plugin.js
 const { PluginBaseClass } = window;
 
@@ -397,7 +397,7 @@ export default class ExamplePlugin extends PluginBaseClass {
                 offset: 0,
             }),
         });
-        
+
         if (!response.ok) {
             throw new Error('Request failed');
         }
diff --git a/guides/plugins/plugins/framework/store-api/override-existing-route.md b/guides/plugins/plugins/framework/store-api/override-existing-route.md
index f3fef7fa48..303160dbd1 100644
--- a/guides/plugins/plugins/framework/store-api/override-existing-route.md
+++ b/guides/plugins/plugins/framework/store-api/override-existing-route.md
@@ -21,7 +21,7 @@ Furthermore, you should have a look at our guide about [Adding a Store API route
 
 First, we have to create a new class which extends `AbstractExampleRoute`. In this example we will name it `ExampleRouteDecorator`.
 
-```php
+```PHP
 // <plugin root>/src/Core/Content/Example/SalesChannel/ExampleRouteDecorator.php
 <?php declare(strict_types=1);
 
@@ -72,21 +72,27 @@ As you can see, our decorated route has to extend from the `AbstractExampleRoute
 
 Last, we have to register the decorated route to the DI-container. The `ExampleRouteDecorator` has to be registered after the `ExampleRoute` with the attribute `decorated` which points to the `ExampleRoute`. For the second argument we have to use the `ExampleRouteDecorator.inner`.
 
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Core\Content\Example\SalesChannel\ExampleRoute;
+use Swag\BasicExample\Core\Content\Example\SalesChannel\ExampleRouteDecorator;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
 
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
 
-    <services>
-        ...
+    // ...
 
-        <service id="Swag\BasicExample\Core\Content\Example\SalesChannel\ExampleRouteDecorator" decorates="Swag\BasicExample\Core\Content\Example\SalesChannel\ExampleRoute" public="true">
-            <argument type="service" id="swag_example.repository"/>
-            <argument type="service" id="Swag\BasicExample\Core\Content\Example\SalesChannel\ExampleRouteDecorator.inner"/>
-        </service>
-    </services>
-</container>
+    $services->set(ExampleRouteDecorator::class)
+        ->decorate(ExampleRoute::class)
+        ->public()
+        ->args([
+            service('swag_example.repository'),
+            service('.inner'),
+        ]);
+};
 ```
diff --git a/guides/plugins/plugins/framework/system-check/add-custom-check.md b/guides/plugins/plugins/framework/system-check/add-custom-check.md
index 49ebeab2df..a6e5f7a192 100644
--- a/guides/plugins/plugins/framework/system-check/add-custom-check.md
+++ b/guides/plugins/plugins/framework/system-check/add-custom-check.md
@@ -17,7 +17,7 @@ First, you need to add a new `LocalDiskSpaceCheck` class that extends the `Shopw
 
 Each check contains a set of categorization methods that help to classify the check, and determine when and where it should be executed.
 
-```php
+```PHP
 class LocalDiskSpaceCheck extends BaseCheck
 {
     public function category(): Category
@@ -42,7 +42,7 @@ class LocalDiskSpaceCheck extends BaseCheck
 
 The next step is to implement the actual check logic. We will check if the disk space is below a certain threshold and return the appropriate result.
 
-```php
+```PHP
 class LocalDiskSpaceCheck extends BaseCheck
 {
     public function __construct(
@@ -86,13 +86,14 @@ class LocalDiskSpaceCheck extends BaseCheck
 
 Finally, you need to register the custom check as a service resource.
 
-```xml
-        <service id="%YourNameSpace%\LocalDiskSpaceCheck" >
-            <argument>%shopware.filesystem.public.type%</argument>
-            <argument>%shopware.filesystem.public.config.root%</argument>
-            <argument>%warning_threshold_in_mb%</argument>
-            <tag name="shopware.system_check"/>
-        </service>
+```PHP
+$services->set(YourNameSpace\LocalDiskSpaceCheck::class)
+    ->args([
+        '%shopware.filesystem.public.type%',
+        '%shopware.filesystem.public.config.root%',
+        '%warning_threshold_in_mb%',
+    ])
+    ->tag('shopware.system_check');
 ```
 
 ### Trigger the check
diff --git a/guides/plugins/plugins/framework/system-check/index.md b/guides/plugins/plugins/framework/system-check/index.md
index 5708525f3a..26dc9ad41b 100644
--- a/guides/plugins/plugins/framework/system-check/index.md
+++ b/guides/plugins/plugins/framework/system-check/index.md
@@ -37,7 +37,7 @@ The `SystemChecker` class makes sure the system is working correctly by running
 
 All the system checks in Shopware are tagged with `shopware.system_check`, so you can also fetch all the checks using the Symfony service locator. and run them in your custom flow.
 
-```php
+```PHP
 class CustomSystemChecker
 {
    public function __construct(private readonly iterable $checks)
@@ -51,17 +51,16 @@ class CustomSystemChecker
 }
 ```
 
-```xml
-<service id="YourNamepace\CustomSystemChecker">
-    <argument type="tagged_iterator" tag="shopware.system_check"/>
-</service>
+```PHP
+$services->set(YourNamepace\CustomSystemChecker::class)
+    ->args([tagged_iterator('shopware.system_check')]);
 ```
 
 ### Custom triggers
 
 For customized triggers, you can also inject the `Shopware\Core\Framework\SystemCheck\SystemChecker` service into your service and trigger the checks programmatically.
 
-```php
+```PHP
 $results = $systemChecker->check(SystemCheckExecutionContext::WEB);
 # or also use any custom logic you might have...
 $customChecker->check();
diff --git a/guides/plugins/plugins/plugin-fundamentals/add-custom-commands.md b/guides/plugins/plugins/plugin-fundamentals/add-custom-commands.md
index 3679193170..162c862b63 100644
--- a/guides/plugins/plugins/plugin-fundamentals/add-custom-commands.md
+++ b/guides/plugins/plugins/plugin-fundamentals/add-custom-commands.md
@@ -9,17 +9,11 @@ nav:
 
 Shopware CLI commands are based on [Symfony Console](https://symfony.com/doc/current/console.html). This means that creating custom commands in Shopware plugins follows the standard Symfony approach.
 
-To add a custom command in a Shopware plugin, you must register it as a service in your plugin’s `src/Resources/config/services.xml` and tag it with `console.command`:
+To add a custom command in a Shopware plugin, you must register it as a service in your plugin's `src/Resources/config/services.php` and tag it with `console.command`:
 
-```html
-<services>
-   <!-- ... -->
-
-   <service id="Swag\BasicExample\Command\ExampleCommand">
-       <tag name="console.command"/>
-   </service>
-</services>
-<!-- ... -->
+```PHP
+$services->set(Swag\BasicExample\Command\ExampleCommand::class)
+    ->tag('console.command');
 ```
 
 Commands registered as services in a Shopware plugin are automatically available via `bin/console`.
diff --git a/guides/plugins/plugins/plugin-fundamentals/add-custom-service.md b/guides/plugins/plugins/plugin-fundamentals/add-custom-service.md
index b50af8a6b8..18d6e30608 100644
--- a/guides/plugins/plugins/plugin-fundamentals/add-custom-service.md
+++ b/guides/plugins/plugins/plugin-fundamentals/add-custom-service.md
@@ -18,21 +18,19 @@ Therefore, you can refer to the [Plugin Base Guide](../plugin-base-guide).
 
 ## Adding service
 
-For adding a custom service, you need to provide a `services.xml` file in your plugin.
-Place a file with name `services.xml` into a directory called `src/Resources/config/`.
+For adding a custom service, you need to provide a `services.php` file in your plugin.
+Place a file with name `services.php` into a directory called `src/Resources/config/`.
 
 ::: code-group
 
-```xml [PLUGIN_ROOT/src/Resources/config/services.xml]
-<?xml version="1.0" ?>
+```PHP [PLUGIN_ROOT/src/Resources/config/services.php]
+<?php declare(strict_types=1);
 
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
 
-    <services>
-    </services>
-</container>
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+};
 ```
 
 :::
@@ -41,24 +39,26 @@ Now you have two possibilities to add a service to your plugin.
 
 ### Using autowire and autoconfigure
 
-Set `autowire` and `autoconfigure` to `true` in your `services.xml` file.
+Set `autowire` and `autoconfigure` to `true` in your `services.php` file.
 Symfony will then automatically register your service.
 Read more about it in the [Symfony docs](https://symfony.com/doc/current/service_container.html#creating-configuring-services-in-the-container).
 
 ::: code-group
 
-```xml [PLUGIN_ROOT/src/Resources/config/services.xml]
-<?xml version="1.0" ?>
+```PHP [PLUGIN_ROOT/src/Resources/config/services.php]
+<?php declare(strict_types=1);
+
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
 
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services()
+        ->defaults()
+            ->autowire()
+            ->autoconfigure();
 
-    <services>
-        <defaults autowire="true" autoconfigure="true"/>
-        <prototype namespace="Swag\BasicExample\" resource="../../" exclude="../../{Resources,Migration,*.php}"/>
-    </services>
-</container>
+    $services->load('Swag\\BasicExample\\', '../../')
+        ->exclude('../../{Resources,Migration,*.php}');
+};
 ```
 
 :::
@@ -73,17 +73,17 @@ Use this option if you want to have more control over your service.
 
 ::: code-group
 
-```xml [PLUGIN_ROOT/src/Resources/config/services.xml]
-<?xml version="1.0" ?>
+```PHP [PLUGIN_ROOT/src/Resources/config/services.php]
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Service\ExampleService;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
 
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
 
-    <services>
-        <service id="Swag\BasicExample\Service\ExampleService"/>
-    </services>
-</container>
+    $services->set(ExampleService::class);
+};
 ```
 
 :::
@@ -115,10 +115,10 @@ By default, all services in Shopware 6 are marked as _private_.
 Read more about [private and public services](https://symfony.com/doc/current/service_container.html#public-versus-private-services).
 :::
 
-## Alternatives to XML
+## Alternatives to PHP configuration
 
-Symfony offers two other file formats to define your services: YAML and PHP.
-In Shopware, it is also possible to use one of these.
+Symfony supports two other file formats to define your services: YAML and XML.
+However, starting with Symfony 7.4, XML service configuration has been deprecated, and it will no longer be supported in Symfony 8.0.
 Choose the one that suits you best.
 
 ## Next steps
diff --git a/guides/plugins/plugins/plugin-fundamentals/add-scheduled-task.md b/guides/plugins/plugins/plugin-fundamentals/add-scheduled-task.md
index c6b372c612..6e05553dfe 100644
--- a/guides/plugins/plugins/plugin-fundamentals/add-scheduled-task.md
+++ b/guides/plugins/plugins/plugin-fundamentals/add-scheduled-task.md
@@ -13,7 +13,7 @@ Quite often one might want to run any type of code on a regular basis, e.g. to c
 
 ## Prerequisites
 
-This guide is built upon our [plugin base guide](../plugin-base-guide), but that one is not mandatory. Knowing how the `services.xml` file in a plugin works is also helpful, which will be taught in our guides about [Dependency Injection](dependency-injection) and [Creating a service](add-custom-service). It is shortly explained here as well though, so no worries!
+This guide is built upon our [plugin base guide](../plugin-base-guide), but that one is not mandatory. Knowing how the `services.php` file in a plugin works is also helpful, which will be taught in our guides about [Dependency Injection](dependency-injection) and [Creating a service](add-custom-service). It is shortly explained here as well though, so no worries!
 
 ::: info
 Refer to this video on **[Adding scheduled tasks](https://www.youtube.com/watch?v=88S9P3x6wYE)**. Also available on our free online training ["Shopware 6 Backend Development"](https://academy.shopware.com/courses/shopware-6-backend-development-with-jisse-reitsma).
@@ -21,38 +21,44 @@ Refer to this video on **[Adding scheduled tasks](https://www.youtube.com/watch?
 
 ## Registering scheduled task in the DI container
 
-A `ScheduledTask` and its respective `ScheduledTaskHandler` are registered in a plugin's `services.xml`. For it to be found by Shopware 6 automatically, you need to place the `services.xml` file in a `Resources/config/` directory, relative to the location of your plugin's base class. The path could look like this: `<plugin root>/src/Resources/config/services.xml`.
-
-Here's an example `services.xml` containing a new `ScheduledTask` as well as a new `ScheduledTaskHandler`:
-
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-    <services>
-        <service id="Swag\BasicExample\Service\ScheduledTask\ExampleTask">
-            <tag name="shopware.scheduled.task" />
-        </service>
-        <service id="Swag\BasicExample\Service\ScheduledTask\ExampleTaskHandler">
-            <argument type="service" id="scheduled_task.repository" />
-            <argument type="service" id="logger"/>
-            <tag name="messenger.message_handler" />
-        </service>
-    </services>
-</container>
+A `ScheduledTask` and its respective `ScheduledTaskHandler` are registered in a plugin's `services.php`. For it to be found by Shopware 6 automatically, you need to place the `services.php` file in a `Resources/config/` directory, relative to the location of your plugin's base class. The path could look like this: `<plugin root>/src/Resources/config/services.php`.
+
+Here's an example `services.php` containing a new `ScheduledTask` as well as a new `ScheduledTaskHandler`:
+
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Service\ScheduledTask\ExampleTask;
+use Swag\BasicExample\Service\ScheduledTask\ExampleTaskHandler;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(ExampleTask::class)
+        ->tag('shopware.scheduled.task');
+
+    $services->set(ExampleTaskHandler::class)
+        ->args([
+            service('scheduled_task.repository'),
+            service('logger'),
+        ])
+        ->tag('messenger.message_handler');
+};
 ```
 
 Note the tags required for both the task and its respective handler, `shopware.scheduled.task` and `messenger.message_handler`. Your custom task will now be saved into the database once your plugin is activated.
 
 ## ScheduledTask and its handler
 
-As you might have noticed, the `services.xml` file tries to find both the task itself as well as the new task handler in a directory called `Service/ScheduledTask`. This naming is up to you, Shopware 6 decided to use this name though.
+As you might have noticed, the `services.php` file tries to find both the task itself and the new task handler in a directory called `Service/ScheduledTask`. This naming is up to you, Shopware 6 decided to use this name though.
 
 Here's the an example `ScheduledTask`:
 
-```php
+```PHP
 // <plugin root>/src/Service/ScheduledTask/ExampleTask.php
 <?php declare(strict_types=1);
 
@@ -83,7 +89,7 @@ And that's it for the `ExampleTask` class.
 
 Following will be the respective task handler:
 
-```php
+```PHP
 // <plugin root>/src/Service/ScheduledTask/ExampleTaskHandler.php
 <?php declare(strict_types=1);
 
@@ -102,7 +108,7 @@ class ExampleTaskHandler extends ScheduledTaskHandler
 }
 ```
 
-The task handler, `ExampleTaskHandler` as defined previously in your `services.xml`, will be annotated with `AsMessageHandler` handling the `ExampleTask` class. In addition, the `ScheduledTaskHandler` has to extend from the class `Shopware\Core\Framework\MessageQueue\ScheduledTask\ScheduledTaskHandler`. This also comes with one method that you need to implement first:
+The task handler, `ExampleTaskHandler` as defined previously in your `services.php`, will be annotated with `AsMessageHandler` handling the `ExampleTask` class. In addition, the `ScheduledTaskHandler` has to extend from the class `Shopware\Core\Framework\MessageQueue\ScheduledTask\ScheduledTaskHandler`. This also comes with one method that you need to implement first:
 
 * `run`: This method is executed once your scheduled task is executed. Do everything, that your task is supposed to do here. In this example, it will just create a new file.
 
diff --git a/guides/plugins/plugins/plugin-fundamentals/adjusting-service.md b/guides/plugins/plugins/plugin-fundamentals/adjusting-service.md
index c7c809b0cc..c5705cf464 100644
--- a/guides/plugins/plugins/plugin-fundamentals/adjusting-service.md
+++ b/guides/plugins/plugins/plugin-fundamentals/adjusting-service.md
@@ -21,26 +21,29 @@ Refer to this video on **[Decorating services](https://www.youtube.com/watch?v=R
 
 ## Decorating the service
 
-First of all we have to create a new service for this example which gets decorated in the next step. Then we have to add a new service to our `services.xml` with the attribute `decorates` pointing to our service we want to decorate. Next we have to add our service decorator as argument, but we append an `.inner` to the end of the service to keep the old one as reference.
+First of all we have to create a new service for this example which gets decorated in the next step. Then we have to add a new service to our `services.php` with the `decorate` method pointing to our service we want to decorate. The `.inner` reference is used to keep the old one as reference.
 
-Here's our example `services.xml`:
+Here's our example `services.php`:
 
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Service\ExampleService;
+use Swag\BasicExample\Service\ExampleServiceDecorator;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
 
-<container xmlns="http://symfony.com/schema/dic/services"
-xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
 
-    <services>
-        <service id="Swag\BasicExample\Service\ExampleService" />
+    $services->set(ExampleService::class);
 
-        <service id="Swag\BasicExample\Service\ExampleServiceDecorator" decorates="Swag\BasicExample\Service\ExampleService">
-            <argument type="service" id="Swag\BasicExample\Service\ExampleServiceDecorator.inner" />
-        </service>
-    </services>
-</container>
+    $services->set(ExampleServiceDecorator::class)
+        ->decorate(ExampleService::class)
+        ->args([service('.inner')]);
+};
 ```
 
 Now we have to define an abstract class because it's more beautiful and not so strict like interfaces. With an abstract class we can add new functions easier, you can read more about this at the end of this article. The abstract class has to include an abstract function called `getDecorated()` which has the return type of our instance.
@@ -51,7 +54,7 @@ To avoid misunderstandings: The abstract service class and the implementation of
 
 Therefore, this is how your abstract class could then look like:
 
-```php
+```PHP
 // <plugin root>/src/Service/AbstractExampleService.php
 <?php declare(strict_types=1);
 
@@ -69,7 +72,7 @@ Now we have our abstract class, but no service which uses it. So we create our `
 
 Therefore, your service could then look like this:
 
-```php
+```PHP
 // <plugin root>/src/Service/ExampleService.php
 <?php declare(strict_types=1);
 
@@ -95,7 +98,7 @@ The last step is creating our decorated service called `ExampleServiceDecorator`
 
 Your service could then look like below:
 
-```php
+```PHP
 // <plugin root>/src/Service/ExampleServiceDecorator.php
 <?php declare(strict_types=1);
 
@@ -130,7 +133,7 @@ If you plan to add new functions to your service, it is recommended to add them
 
 Here's our example abstract class:
 
-```php
+```PHP
 // <plugin root>/src/Service/AbstractExampleService.php
 <?php declare(strict_types=1);
 
@@ -151,7 +154,7 @@ abstract class AbstractExampleService
 
 After we have implemented our new function in the abstract class, we implement it in our service too.
 
-```php
+```PHP
 // <plugin root>/src/Service/ExampleService.php
 <?php declare(strict_types=1);
 
diff --git a/guides/plugins/plugins/plugin-fundamentals/dependency-injection.md b/guides/plugins/plugins/plugin-fundamentals/dependency-injection.md
index dd42a95c54..c289514b15 100644
--- a/guides/plugins/plugins/plugin-fundamentals/dependency-injection.md
+++ b/guides/plugins/plugins/plugin-fundamentals/dependency-injection.md
@@ -59,7 +59,7 @@ class ExampleService
 
 ### Using autowire and autoconfigure
 
-If you previously declared `autowire` and `autoconfigure` in your `services.xml` file, you do not need to do anything else.
+If you previously declared `autowire` and `autoconfigure` in your `services.php` file, you do not need to do anything else.
 The `SystemConfigService` will be injected into the `ExampleService` automatically.
 
 ### Explicit declaration
@@ -68,19 +68,21 @@ If you declared the service explicitly, you need to add the `SystemConfigService
 
 ::: code-group
 
-```xml [PLUGIN_ROOT/src/Resources/config/services.xml]
-<?xml version="1.0" ?>
+```PHP [PLUGIN_ROOT/src/Resources/config/services.php]
+<?php declare(strict_types=1);
+
+use Shopware\Core\System\SystemConfig\SystemConfigService;
+use Swag\BasicExample\Service\ExampleService;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
 
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
 
-    <services>
-        <service id="Swag\BasicExample\Service\ExampleService">
-            <argument type="service" id="Shopware\Core\System\SystemConfig\SystemConfigService"/>
-        </service>
-    </services>
-</container>
+    $services->set(ExampleService::class)
+        ->args([service(SystemConfigService::class)]);
+};
 ```
 
 :::
diff --git a/guides/plugins/plugins/plugin-fundamentals/listening-to-events.md b/guides/plugins/plugins/plugin-fundamentals/listening-to-events.md
index f97e196fd5..b2a4ab8b24 100644
--- a/guides/plugins/plugins/plugin-fundamentals/listening-to-events.md
+++ b/guides/plugins/plugins/plugin-fundamentals/listening-to-events.md
@@ -24,8 +24,8 @@ Also available on our free online training ["Shopware 6 Backend Development"](ht
 
 ### Plugin base class
 
-Registering a custom subscriber requires to load a `services.xml` file with your plugin.
-This is done by either placing a file with name `services.xml` into a directory called `src/Resources/config/`.
+Registering a custom subscriber requires loading a `services.php` file with your plugin.
+This is done by either placing a file with name `services.php` into a directory called `src/Resources/config/`.
 
 Basically, that's it already if you're familiar with [Symfony subscribers](https://symfony.com/doc/current/event_dispatcher.html#creating-an-event-subscriber).
 Don't worry, we got you covered here as well.
@@ -37,7 +37,7 @@ As mentioned above, such a subscriber for Shopware 6 looks exactly the same as i
 
 Therefore, this is how your subscriber could then look like:
 
-```php
+```PHP
 // <plugin root>/src/Subscriber/MySubscriber.php
 <?php declare(strict_types=1);
 
@@ -73,7 +73,7 @@ Some entities, like orders or products, are versioned.
 This means that some events are dispatched multiple times for different versions, but they belong to the same entity.
 Therefore, you can check the version of the context to make sure you're only reacting to the live version.
 
-```php
+```PHP
 // <plugin root>/src/Subscriber/MySubscriber.php
 <?php declare(strict_types=1);
 
@@ -103,28 +103,27 @@ class MySubscriber implements EventSubscriberInterface
 }
 ```
 
-Unfortunately, your subscriber is not even loaded yet - this will be done in the previously registered `services.xml` file.
+Unfortunately, your subscriber is not even loaded yet - this will be done in the previously registered `services.php` file.
 
-### Registering your subscriber via services.xml
+### Registering your subscriber via services.php
 
 Registering your subscriber to Shopware 6 is also as simple as it is in Symfony.
-You're simply registering your \(subscriber\) service by mentioning it in the `services.xml`.
+You're simply registering your \(subscriber\) service by mentioning it in the `services.php`.
 The only difference to a normal service is that you need to add the `kernel.event_subscriber` tag to your subscriber for it to be recognized as such.
 
-```php
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Subscriber\MySubscriber;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
 
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
 
-    <services>
-        <service id="Swag\BasicExample\Subscriber\MySubscriber">
-            <tag name="kernel.event_subscriber"/>
-        </service>
-    </services>
-</container>
+    $services->set(MySubscriber::class)
+        ->tag('kernel.event_subscriber');
+};
 ```
 
 That's it, your subscriber service is now automatically loaded at runtime, and it should start listening to the mentioned events to be dispatched.
diff --git a/guides/plugins/plugins/plugin-fundamentals/use-plugin-configuration.md b/guides/plugins/plugins/plugin-fundamentals/use-plugin-configuration.md
index 75620cdfbb..dcbda4828a 100644
--- a/guides/plugins/plugins/plugin-fundamentals/use-plugin-configuration.md
+++ b/guides/plugins/plugins/plugin-fundamentals/use-plugin-configuration.md
@@ -17,7 +17,7 @@ In order to add a plugin configuration, you sure need to provide your plugin fir
 
 The plugin in this example already knows a subscriber, which listens to the `product.loaded` event and therefore will be called every time a product is loaded.
 
-```php
+```PHP
 // <plugin root>/src/Subscriber/MySubscriber.php
 <?php declare(strict_types=1);
 
@@ -45,7 +45,7 @@ class MySubscriber implements EventSubscriberInterface
 
 For this guide, a very small plugin configuration file is available as well:
 
-```xml
+```XML
 // <plugin root>/src/Resources/config/config.xml
 <?xml version="1.0" encoding="UTF-8"?>
 <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -68,26 +68,28 @@ Let's get to the important part. Reading the plugin configuration is based on th
 
 Inject this service into your subscriber using the [DI container](https://symfony.com/doc/current/service_container.html).
 
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
-
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\BasicExample\Subscriber\MySubscriber">
-            <argument type="service" id="Shopware\Core\System\SystemConfig\SystemConfigService" />
-            <tag name="kernel.event_subscriber"/>
-        </service>
-    </services>
-</container>
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Shopware\Core\System\SystemConfig\SystemConfigService;
+use Swag\BasicExample\Subscriber\MySubscriber;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(MySubscriber::class)
+        ->args([service(SystemConfigService::class)])
+        ->tag('kernel.event_subscriber');
+};
 ```
 
 Note the new `argument` being provided to your subscriber. Now create a new field in your subscriber and pass in the `SystemConfigService`:
 
-```php
+```PHP
 // <plugin root>/src/Subscriber/MySubscriber.php
 <?php declare(strict_types=1);
 
@@ -121,7 +123,7 @@ But what would happen, if there were more plugins providing the same technical n
 
 That's why the plugin configurations are always prefixed. By default, the pattern is the following: `<BundleName>.config.<configName>`. Thus, it would be `SwagBasicExample.config.example` here.
 
-```php
+```PHP
 // <plugin root>/src/Subscriber/MySubscriber.php
 <?php declare(strict_types=1);
 
@@ -153,21 +155,21 @@ To access your plugin's configuration from JavaScript in the Administration, you
 
 #### Using injection in Vue components
 
-```javascript
+```JAVASCRIPT
 // Example: Reading plugin configuration in Administration Vue component
 export default Shopware.Component.wrapComponentConfig({
     inject: ['systemConfigApiService'],
-    
+
     async created() {
         await this.loadPluginConfig();
     },
-    
+
     methods: {
         async loadPluginConfig() {
             try {
                 const config = await this.systemConfigApiService.getValues('SwagBasicExample.config');
                 const exampleValue = config['SwagBasicExample.config.example'];
-                
+
                 console.log('Plugin configuration value:', exampleValue);
                 return exampleValue;
             } catch (error) {
@@ -180,14 +182,14 @@ export default Shopware.Component.wrapComponentConfig({
 
 #### Using direct service access
 
-```javascript
+```JAVASCRIPT
 // Example: Reading plugin configuration using direct service access
 async function getPluginConfig() {
     try {
         const systemConfigApiService = Shopware.ApiService.getByName('systemConfigApiService');
         const config = await systemConfigApiService.getValues('SwagBasicExample.config');
         const exampleValue = config['SwagBasicExample.config.example'];
-        
+
         console.log('Plugin configuration value:', exampleValue);
         return exampleValue;
     } catch (error) {
@@ -204,7 +206,7 @@ Your plugin needs the `system_config:read` permission to access this API endpoin
 
 In Storefront templates, you can use the `config()` twig function to access plugin configuration values directly without making API calls:
 
-```twig
+```TWIG
 {# Example: Reading plugin configuration in Storefront templates #}
 {% set exampleValue = config('SwagBasicExample.config.example') %}
 
@@ -217,7 +219,7 @@ In Storefront templates, you can use the `config()` twig function to access plug
 
 For Storefront JavaScript plugins, you can pass configuration values from Twig templates to your JavaScript code:
 
-```twig
+```TWIG
 {# In your Storefront template #}
 <script>
     window.pluginConfig = {
@@ -226,7 +228,7 @@ For Storefront JavaScript plugins, you can pass configuration values from Twig t
 </script>
 ```
 
-```javascript
+```JAVASCRIPT
 // In your Storefront JavaScript plugin
 const { PluginBaseClass } = window;
 
@@ -234,7 +236,7 @@ export default class ExamplePlugin extends PluginBaseClass {
     init() {
         // Access the configuration value passed from Twig
         const exampleConfig = window.pluginConfig?.example;
-        
+
         if (exampleConfig) {
             console.log('Plugin configuration:', exampleConfig);
             // Use the configuration value in your plugin logic
diff --git a/guides/plugins/plugins/redis.md b/guides/plugins/plugins/redis.md
index 934a23e638..8a9abe400d 100644
--- a/guides/plugins/plugins/redis.md
+++ b/guides/plugins/plugins/redis.md
@@ -15,16 +15,17 @@ Once you've set up your Redis connections as explained in the  [Redis configurat
 
 1. Inject `Shopware\Core\Framework\Adapter\Redis\RedisConnectionProvider` and retrieve connections by name:
 
-    ```xml
-    <service id="MyCustomService">
-        <argument type="service" id="Shopware\Core\Framework\Adapter\Redis\RedisConnectionProvider" />
-        <argument>%myservice.redis_connection_name%</argument>
-    </service>
+    ```PHP
+    $services->set(MyCustomService::class)
+        ->args([
+            service(Shopware\Core\Framework\Adapter\Redis\RedisConnectionProvider::class),
+            '%myservice.redis_connection_name%',
+        ]);
     ```
 
     ```php
     class MyCustomService
-    { 
+    {
         public function __construct (
             private RedisConnectionProvider $redisConnectionProvider,
             string $connectionName,
@@ -42,20 +43,18 @@ Once you've set up your Redis connections as explained in the  [Redis configurat
 
 2. Use `Shopware\Core\Framework\Adapter\Redis\RedisConnectionProvider` as factory to define custom services:
 
-    ```xml
-    <service id="my.custom.redis_connection" class="Redis">
-        <factory service="Shopware\Core\Framework\Adapter\Redis\RedisConnectionProvider" method="getConnection" />
-        <argument>%myservice.redis_connection_name%</argument>
-    </service>
+    ```PHP
+    $services->set('my.custom.redis_connection', \Redis::class)
+        ->factory([service(Shopware\Core\Framework\Adapter\Redis\RedisConnectionProvider::class), 'getConnection'])
+        ->args(['%myservice.redis_connection_name%']);
 
-    <service id="MyCustomService">
-        <argument type="service" id="my.custom.redis_connection" />
-    </service>
+    $services->set(MyCustomService::class)
+        ->args([service('my.custom.redis_connection')]);
     ```
 
     ```php
     class MyCustomService
-    { 
+    {
         public function __construct (
             private object $redisConnection,
         ) { }
@@ -71,10 +70,9 @@ Once you've set up your Redis connections as explained in the  [Redis configurat
 
 3. Inject connection directly by name:
 
-    ```xml
-    <service id="MyCustomService">
-        <argument type="service" id="shopware.redis.connection.connection_name" />
-    </service>
+    ```PHP
+    $services->set(MyCustomService::class)
+        ->args([service('shopware.redis.connection.connection_name')]);
     ```
 
    Be cautious with this approach! If you change the Redis connection names in your configuration, it will cause container build errors.
diff --git a/guides/plugins/plugins/storefront/add-cookie-to-manager.md b/guides/plugins/plugins/storefront/add-cookie-to-manager.md
index 08b1dea29f..c84e523708 100644
--- a/guides/plugins/plugins/storefront/add-cookie-to-manager.md
+++ b/guides/plugins/plugins/storefront/add-cookie-to-manager.md
@@ -29,22 +29,21 @@ It is recommended to use an event listener if you're listening to a single event
 
 ### Registering your event listener
 
-Start with creating the `services.xml` and registering your event listener.
-
-```xml
-// <plugin root>/src/Resources/config/services.xml
-<?xml version="1.0" ?>
-
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="PluginName\Listener\CookieListener">
-            <tag name="kernel.event_listener" event="Shopware\Core\Content\Cookie\Event\CookieGroupCollectEvent"/>
-        </service>
-    </services>
-</container>
+Start with creating the `services.php` and registering your event listener.
+
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use PluginName\Listener\CookieListener;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(CookieListener::class)
+        ->tag('kernel.event_listener', ['event' => 'Shopware\Core\Content\Cookie\Event\CookieGroupCollectEvent']);
+};
 ```
 
 In the next step we'll create the actual listener class.
@@ -61,7 +60,7 @@ Since Shopware 6.7.3.0, cookies use structured objects (`CookieEntry` and `Cooki
 
 Let's have a look at an example:
 
-```php
+```PHP
 // <plugin root>/src/Listener/CookieListener.php
 <?php declare(strict_types=1);
 
diff --git a/guides/plugins/plugins/storefront/add-custom-controller.md b/guides/plugins/plugins/storefront/add-custom-controller.md
index 8b51640df3..7ed39df617 100644
--- a/guides/plugins/plugins/storefront/add-custom-controller.md
+++ b/guides/plugins/plugins/storefront/add-custom-controller.md
@@ -135,50 +135,49 @@ class ExampleController extends StorefrontController
 
 :::
 
-### Services.xml example
+### Services.php example
 
 Next, we need to register our controller in the DI-container and make it public.
 
 ::: code-group
 
-```xml [PLUGIN_ROOT/src/Resources/config/services.xml]
-<?xml version="1.0" ?>
-
-<container xmlns="http://symfony.com/schema/dic/services" 
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\BasicExample\Storefront\Controller\ExampleController" public="true">
-            <call method="setContainer">
-                <argument type="service" id="service_container"/>
-            </call>
-        </service>
-    </services>
-</container>
+```PHP [PLUGIN_ROOT/src/Resources/config/services.php]
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Storefront\Controller\ExampleController;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(ExampleController::class)
+        ->public()
+        ->call('setContainer', [service('service_container')]);
+};
 ```
 
 :::
 
-Please also note the `call` tag, which is necessary in order to set the DI container to the controller.
+Please also note the `call` method, which is necessary in order to set the DI container to the controller.
 
-### Routes.xml example
+### Routes.php example
 
 Once we've registered our new controller, we have to tell Shopware how we want it to search for new routes in our plugin.
-This is done with a `routes.xml` file at `<plugin root>/src/Resources/config/` location.
-Have a look at the official [Symfony documentation](https://symfony.com/doc/current/routing.html) about routes and how they are registered.
+This is done with a `routes.php` file at `<plugin root>/src/Resources/config/` location.
+Take a look at the official [Symfony documentation](https://symfony.com/doc/current/routing.html) about routes and how they are registered.
 
 ::: code-group
 
-```xml [PLUGIN_ROOT/src/Resources/config/routes.xml]
-<?xml version="1.0" encoding="UTF-8" ?>
-<routes xmlns="http://symfony.com/schema/routing"
-        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-        xsi:schemaLocation="http://symfony.com/schema/routing
-        https://symfony.com/schema/routing/routing-1.0.xsd">
+```PHP [PLUGIN_ROOT/src/Resources/config/routes.php]
+<?php declare(strict_types=1);
+
+use Symfony\Component\Routing\Loader\Configurator\RoutingConfigurator;
 
-    <import resource="../../Storefront/Controller/*Controller.php" type="attribute" />
-</routes>
+return static function (RoutingConfigurator $routes): void {
+    $routes->import('../../Storefront/Controller/*Controller.php', 'attribute');
+};
 ```
 
 :::
@@ -228,7 +227,7 @@ use Symfony\Component\Routing\Attribute\Route;
 
 #[Route(defaults: [PlatformRequest::ATTRIBUTE_ROUTE_SCOPE => [StorefrontRouteScope::ID]])]
 class ExampleController extends StorefrontController
-{    
+{
     #[Route(path: '/example', name: 'frontend.example.example', methods: ['GET'])]
     public function showExample(Request $request, SalesChannelContext $context): Response
     {
@@ -305,7 +304,7 @@ class SwagBasicExample extends Plugin
 
 Now you can use the route name `swag.test.foo-bar` in your controller without the need for a prefix.
 
-```php
+```PHP
 #[Route(path: '/example', name: 'swag.test.foo-bar', methods: ['GET'])]
 public function showExample(Request $request, SalesChannelContext $context): Response
 {
diff --git a/guides/plugins/plugins/storefront/add-custom-page.md b/guides/plugins/plugins/storefront/add-custom-page.md
index 2c74792bb5..f4ad97f9ee 100644
--- a/guides/plugins/plugins/storefront/add-custom-page.md
+++ b/guides/plugins/plugins/storefront/add-custom-page.md
@@ -148,11 +148,13 @@ Remember to register your new page loader in the DI container:
 
 ::: code-group
 
-```xml [PLUGIN_ROOT/src/Resources/config/services.xml]
-<service id="Swag\BasicExample\Storefront\Page\Example\ExamplePageLoader" public="true">
-    <argument type="service" id="Shopware\Storefront\Page\GenericPageLoader" />
-    <argument type="service" id="event_dispatcher"/>
-</service>
+```PHP [PLUGIN_ROOT/src/Resources/config/services.php]
+$services->set(ExamplePageLoader::class)
+    ->public()
+    ->args([
+        service('Shopware\Storefront\Page\GenericPageLoader'),
+        service('event_dispatcher'),
+    ]);
 ```
 
 :::
@@ -197,19 +199,29 @@ class ExampleController extends StorefrontController
 
 Note, that we've added the page to the template variables.
 
-#### Adjusting the services.xml
+#### Adjusting the services.php
 
-In addition, it is necessary to pass the argument with the ID of the `ExamplePageLoader` class to the [configuration](add-custom-controller#services-xml-example) of the controller service in the `services.xml`.
+In addition, it is necessary to pass the argument with the ID of the `ExamplePageLoader` class to the [configuration](add-custom-controller#services-xml-example) of the controller service in the `services.php`.
 
 ::: code-group
 
-```xml [PLUGIN_ROOT/src/Resources/config/services.xml]
-<service id="Swag\BasicExample\Storefront\Controller\ExampleController" public="true">
-    <argument type="service" id="Swag\BasicExample\Storefront\Page\Example\ExamplePageLoader" />
-    <call method="setContainer">
-        <argument type="service" id="service_container"/>
-    </call>
-</service>
+```PHP [PLUGIN_ROOT/src/Resources/config/services.php]
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Storefront\Controller\ExampleController;
+use Swag\BasicExample\Storefront\Page\Example\ExamplePageLoader;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(ExampleController::class)
+        ->public()
+        ->args([service(ExamplePageLoader::class)])
+        ->call('setContainer', [service('service_container')]);
+};
 ```
 
 :::
diff --git a/guides/plugins/plugins/storefront/add-custom-twig-function.md b/guides/plugins/plugins/storefront/add-custom-twig-function.md
index 1875552df1..255b771bf3 100644
--- a/guides/plugins/plugins/storefront/add-custom-twig-function.md
+++ b/guides/plugins/plugins/storefront/add-custom-twig-function.md
@@ -65,16 +65,14 @@ class SwagCreateMd5Hash extends AbstractExtension
 
 :::
 
-Of course, you can do everything in the `createMd5Hash` function that PHP can do, but the `service.xml` handles registration of the service in the DI container.
+Of course, you can do everything in the `createMd5Hash` function that PHP can do, but the `services.php` handles registration of the service in the DI container.
 
 ::: code-group
 
-```xml [PLUGIN_ROOT/src/Resources/config/services.xml]
-    <services>
-        <service id="SwagBasicExample\Twig\SwagCreateMd5Hash" public="true">
-            <tag name="twig.extension"/> <!--Required-->
-        </service>
-    </services>
+```PHP [PLUGIN_ROOT/src/Resources/config/services.php]
+$services->set(SwagCreateMd5Hash::class)
+        ->public()
+        ->tag('twig.extension'); // Required
 ```
 
 Once done, you can access this `TwigFunction` within your plugin.
diff --git a/guides/plugins/plugins/storefront/add-data-to-storefront-page.md b/guides/plugins/plugins/storefront/add-data-to-storefront-page.md
index f5dc9011ae..942b1f1589 100644
--- a/guides/plugins/plugins/storefront/add-data-to-storefront-page.md
+++ b/guides/plugins/plugins/storefront/add-data-to-storefront-page.md
@@ -43,7 +43,7 @@ In this example, we're going to extend the [FooterPagelet](https://github.com/sh
 All pages or pagelets throw `Loaded` events and this is the right event to subscribe to if you want to add data to the page or pagelet.
 In our case we want to add data to the `FooterPagelet` so we need to subscribe to the `FooterPageletLoadedEvent`.
 
-```php
+```PHP
 // SwagBasicExample/src/Service/AddDataToPage.php
 <?php declare(strict_types=1);
 
@@ -70,12 +70,10 @@ class AddDataToPage implements EventSubscriberInterface
 
 The next thing we need to do is register our subscriber in the DI-Container and tag it as an event subscriber:
 
-```xml
-// Resources/config/services.xml
-<?xml version="1.0" ?>
-<service id="Swag\BasicExample\Service\AddDataToPage" >
-    <tag name="kernel.event_subscriber" />
-</service>
+```PHP
+// Resources/config/services.php
+$services->set(\Swag\BasicExample\Service\AddDataToPage::class)
+    ->tag('kernel.event_subscriber');
 ```
 
 ### Adding data to the page
@@ -95,7 +93,7 @@ First you should read our guide for [adding store-api routes](../framework/store
 
 Our new Route should look like this:
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace Swag\BasicExample\Core\Content\Example\SalesChannel;
@@ -115,7 +113,7 @@ abstract class AbstractProductCountRoute
 }
 ```
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace Swag\BasicExample\Core\Content\Example\SalesChannel;
@@ -162,7 +160,7 @@ class ProductCountRoute extends AbstractProductCountRoute
         $productCountResult = $this->productRepository
             ->aggregate($criteria, $context->getContext())
             ->get('productCount');
-            
+
         return new ProductCountRouteResponse($productCountResult);
     }
 }
@@ -170,38 +168,40 @@ class ProductCountRoute extends AbstractProductCountRoute
 
 ### Register route class
 
-```xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\BasicExample\Core\Content\Example\SalesChannel\ProductCountRoute" >
-            <argument type="service" id="product.repository"/>
-        </service>
-    </services>
-</container>
+```PHP
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Core\Content\Example\SalesChannel\ProductCountRoute;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(ProductCountRoute::class)
+        ->args([service('product.repository')]);
+};
 ```
 
-The routes.xml according to our guide for [adding store-api routes](../framework/store-api/add-store-api-route) should look like this.
+The routes.php according to our guide for [adding store-api routes](../framework/store-api/add-store-api-route) should look like this.
+
+```PHP
+// <plugin root>/src/Resources/config/routes.php
+<?php declare(strict_types=1);
 
-```xml
-<?xml version="1.0" encoding="UTF-8" ?>
-<routes xmlns="http://symfony.com/schema/routing"
-        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-        xsi:schemaLocation="http://symfony.com/schema/routing
-        https://symfony.com/schema/routing/routing-1.0.xsd">
+use Symfony\Component\Routing\Loader\Configurator\RoutingConfigurator;
 
-    <import resource="../../Core/**/*Route.php" type="attribute" />
-</routes>
+return static function (RoutingConfigurator $routes): void {
+    $routes->import('../../Core/**/*Route.php', 'attribute');
+};
 ```
 
 ### ProductCountRouteResponse
 
 The RouteResponse according to our guide for [adding store-api routes](../framework/store-api/add-store-api-route) should look like this
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace Swag\BasicExample\Core\Content\Example\SalesChannel;
@@ -231,7 +231,7 @@ Make sure to also understand the usage of aggregations, since this is what is do
 The only main difference you might notice is, that we're using the `aggregate()` method instead of the `search()` method.
 This will not actually search for any products and return the whole products dataset, but rather just the aggregated data, nothing else.
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace Swag\BasicExample\Service;
@@ -274,23 +274,26 @@ This data will then be available via the name `product_count`, but we'll get to
 
 Now you only have to adjust your service definition to inject the productCountRoute:
 
-```xml
-<?xml version="1.0" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="Swag\BasicExample\Core\Content\Example\SalesChannel\ProductCountRoute" public="true">
-            <argument type="service" id="product.repository"/>
-        </service>
-        
-        <service id="Swag\BasicExample\Service\AddDataToPage" >
-            <argument type="service" id="Swag\BasicExample\Core\Content\Example\SalesChannel\ProductCountRoute"/>
-            <tag name="kernel.event_subscriber" />
-        </service>
-    </services>
-</container>
+```PHP
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Core\Content\Example\SalesChannel\ProductCountRoute;
+use Swag\BasicExample\Service\AddDataToPage;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(ProductCountRoute::class)
+        ->public()
+        ->args([service('product.repository')]);
+
+    $services->set(AddDataToPage::class)
+        ->args([service(ProductCountRoute::class)])
+        ->tag('kernel.event_subscriber');
+};
 ```
 
 ### Displaying the data in the Storefront
diff --git a/guides/plugins/plugins/storefront/add-dynamic-content-via-ajax-calls.md b/guides/plugins/plugins/storefront/add-dynamic-content-via-ajax-calls.md
index 6a85b7eb90..ccf2259b3b 100644
--- a/guides/plugins/plugins/storefront/add-dynamic-content-via-ajax-calls.md
+++ b/guides/plugins/plugins/storefront/add-dynamic-content-via-ajax-calls.md
@@ -54,36 +54,35 @@ As you might have seen, this controller isn't too different from the controller
 The route attribute has an added `defaults: ['XmlHttpRequest' => true]` to allow XmlHttpRequest, and it returns a `JsonResponse` instead of a normal `Response`.
 Using a `JsonResponse` instead of a normal `Response` causes the data structures passed to it to be automatically turned into a `JSON` string.
 
-The following `services.xml` and `routes.xml` are identical as in the before mentioned article, but here they are for reference anyway:
+The following `services.php` and `routes.php` are identical as in the before mentioned article, but here they are for reference anyway:
 
 ::: code-group
 
-```xml [PLUGIN_ROOT/src/Resources/config/services.xml]
-<?xml version="1.0" ?>
-
-<container xmlns="http://symfony.com/schema/dic/services" 
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-
-    <services>
-        <service id="SwagBasicExample\Storefront\Controller\ExampleController" public="true">
-            <call method="setContainer">
-                <argument type="service" id="service_container"/>
-            </call>
-        </service>
-    </services>
-</container>
+```PHP [PLUGIN_ROOT/src/Resources/config/services.php]
+<?php declare(strict_types=1);
+
+use SwagBasicExample\Storefront\Controller\ExampleController;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(ExampleController::class)
+        ->public()
+        ->call('setContainer', [service('service_container')]);
+};
 ```
 
-```xml [PLUGIN_ROOT/src/Resources/config/routes.xml]
-<?xml version="1.0" encoding="UTF-8" ?>
-<routes xmlns="http://symfony.com/schema/routing"
-        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-        xsi:schemaLocation="http://symfony.com/schema/routing
-        https://symfony.com/schema/routing/routing-1.0.xsd">
+```PHP [PLUGIN_ROOT/src/Resources/config/routes.php]
+<?php declare(strict_types=1);
+
+use Symfony\Component\Routing\Loader\Configurator\RoutingConfigurator;
 
-    <import resource="../../Storefront/Controller/**/*Controller.php" type="attribute" />
-</routes>
+return static function (RoutingConfigurator $routes): void {
+    $routes->import('../../Storefront/Controller/**/*Controller.php', 'attribute');
+};
 ```
 
 :::
diff --git a/guides/plugins/plugins/storefront/add-scss-variables-via-subscriber.md b/guides/plugins/plugins/storefront/add-scss-variables-via-subscriber.md
index 541157e21c..9a00dbe45d 100644
--- a/guides/plugins/plugins/storefront/add-scss-variables-via-subscriber.md
+++ b/guides/plugins/plugins/storefront/add-scss-variables-via-subscriber.md
@@ -44,7 +44,7 @@ You can add a new subscriber according to the [Listening to events](../plugin-fu
 <Tabs>
 <Tab title="<plugin root>/src/Subscriber/ThemeVariableSubscriber.php">
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace Swag\BasicExample\Subscriber;
@@ -71,21 +71,20 @@ class ThemeVariableSubscriber implements EventSubscriberInterface
 
 </Tab>
 
-<Tab title="<plugin root>/src/Resources/config/services.xml">
+<Tab title="<plugin root>/src/Resources/config/services.php">
 
-```xml
-<?xml version="1.0" ?>
+```PHP
+<?php declare(strict_types=1);
+
+use Swag\BasicExample\Subscriber\ThemeVariableSubscriber;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
 
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
 
-    <services>
-        <service id="Swag\BasicExample\Subscriber\ThemeVariableSubscriber">
-            <tag name="kernel.event_subscriber"/>
-        </service>
-    </services>
-</container>
+    $services->set(ThemeVariableSubscriber::class)
+        ->tag('kernel.event_subscriber');
+};
 ```
 
 </Tab>
@@ -107,7 +106,7 @@ Inside your `ThemeVariableSubscriber` you can also read values from the plugin c
 
 First, lets add a new plugin configuration field according to the [Plugin Configurations](../plugin-fundamentals/add-plugin-configuration):
 
-```xml
+```XML
 // <plugin root>/src/Resources/config/config.xml
 <?xml version="1.0" encoding="UTF-8"?>
 <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -125,7 +124,7 @@ First, lets add a new plugin configuration field according to the [Plugin Config
 
 As you can see in the example, we add an input field of the type colorpicker for our plugin. In the Administration, the component 'sw-colorpicker' will later be displayed for the selection of the value. You also can set a `defaultValue` which will be pre-selected like the following:
 
-```xml
+```XML
 // <plugin root>/src/Resources/config/config.xml
 <?xml version="1.0" encoding="UTF-8"?>
 <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -147,7 +146,7 @@ In order to be able to read this config, you have to inject the `SystemConfigSer
 <Tabs>
 <Tab title="<plugin root>/src/Subscriber/ThemeVariableSubscriber.php">
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace Swag\BasicExample\Subscriber;
@@ -188,23 +187,25 @@ class ThemeVariableSubscriber implements EventSubscriberInterface
 
 </Tab>
 
-<Tab title="<plugin root>/src/Resources/config/services.xml">
+<Tab title="<plugin root>/src/Resources/config/services.php">
+
+```PHP
+<?php declare(strict_types=1);
+
+use Shopware\Core\System\SystemConfig\SystemConfigService;
+use Swag\BasicExample\Subscriber\ThemeVariableSubscriber;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
 
-```xml
-<?xml version="1.0" ?>
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
 
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
 
-    <services>
-        <service id="Swag\BasicExample\Subscriber\ThemeVariableSubscriber">
-            <!-- add argument `SystemConfigService` -->
-            <argument type="service" id="Shopware\Core\System\SystemConfig\SystemConfigService"/>
-            <tag name="kernel.event_subscriber"/>
-        </service>
-    </services>
-</container>
+    $services->set(ThemeVariableSubscriber::class)
+        // add argument SystemConfigService
+        ->args([service(SystemConfigService::class)])
+        ->tag('kernel.event_subscriber');
+};
 ```
 
 </Tab>
@@ -218,7 +219,7 @@ class ThemeVariableSubscriber implements EventSubscriberInterface
 
 Adding config fields via `$event->addVariable()` for every field individually may be a bit cumbersome in some cases. You could also loop over all config fields and call `addVariable()` for each one. However, this depends on your use case.
 
-```php
+```PHP
 // <plugin root>/src/Subscriber/ThemeVariableSubscriber.php
 <?php declare(strict_types=1);
 
diff --git a/guides/plugins/plugins/storefront/add-translations.md b/guides/plugins/plugins/storefront/add-translations.md
index a59a5a1d0e..d17da3aab9 100644
--- a/guides/plugins/plugins/storefront/add-translations.md
+++ b/guides/plugins/plugins/storefront/add-translations.md
@@ -26,7 +26,7 @@ You can also use subdirectories if you prefer, although we recommend keeping a f
 Use `<domain>.<locale>.json` as the naming pattern for the file.
 
 The domain can be freely defined (we recommend your extension name in kebab case), while the locale **must** map to the ISO string of the supported locale in this snippet file — for example: `my-app.de.json`.
-Locales should follow the ISO string of the supported language, such as `de`, `en`, or `es-AR`.  
+Locales should follow the ISO string of the supported language, such as `de`, `en`, or `es-AR`.
 This format follows [IETF BCP 47](https://datatracker.ietf.org/doc/html/bcp47), restricted to [ISO 639-1 (2-letter) language codes](https://en.wikipedia.org/wiki/ISO_639-1) as used by [Symfony](https://symfony.com/doc/current/reference/constraints/Locale.html), but with dashes (`-`) instead of underscores (`_`).
 
 For more information on selecting proper locales, see our documentation on [Fallback language selection](../../../../concepts/translations/fallback-language-selection.md).
@@ -98,13 +98,13 @@ Or use injection via [DI container](#using-translation-generally-in-php).
 
 Translation without placeholders:
 
-```php
+```PHP
 $this->trans('header.example');
 ```
 
 Translation with placeholders:
 
-```php
+```PHP
 $this->trans('soldProducts', ['%count%' => 3, '%country%' => 'Germany']);
 ```
 
@@ -114,13 +114,13 @@ If we need to use a snippet elsewhere in PHP,
 we can use [Dependency Injection](../plugin-fundamentals/dependency-injection) to inject the `translator` service,
 which implements Symfony's `Symfony\Contracts\Translation\TranslatorInterface`:
 
-```xml
-<service id="Swag\Example\Service\SwagService" public="true" >
-    <argument type="service" id="translator" />
-</service>
+```PHP
+$services->set(Swag\Example\Service\SwagService::class)
+    ->public()
+    ->args([service('translator')]);
 ```
 
-```php
+```PHP
 private TranslatorInterface $translator;
 
 public function __construct(TranslatorInterface $translator)
@@ -131,6 +131,6 @@ public function __construct(TranslatorInterface $translator)
 
 Then, call the `trans` method, which has the same parameters as the method from controllers.
 
-```php
+```PHP
 $this->translator->trans('soldProducts', ['%count%' => 3, '%country%' => 'Germany']);
 ```
diff --git a/products/cli/extension-commands/build.md b/products/cli/extension-commands/build.md
index 457f2eb30f..354d60b0d5 100644
--- a/products/cli/extension-commands/build.md
+++ b/products/cli/extension-commands/build.md
@@ -150,7 +150,7 @@ build:
         - <another_path>
 ```
 
-For example, to exclude the `src/Resources/config/services.xml` file from checksum calculation:
+For example, to exclude the `src/Resources/config/services.php` file from checksum calculation:
 
 ```yaml
 # .shopware-extension.yml
@@ -158,7 +158,7 @@ build:
   zip:
     checksum:
       ignore:
-        - src/Resources/config/services.xml
+        - src/Resources/config/services.php
 ```
 
 To verify the checksum of installed extensions, you can use the [FroshTools](https://github.com/FriendsOfShopware/FroshTools#froshextensionchecksumcheck---check-extension-file-integrity) plugin which provides a checksum verification feature for all extensions.
diff --git a/products/extensions/advanced-search/How-to-add-more-fields-to-product-search.md b/products/extensions/advanced-search/How-to-add-more-fields-to-product-search.md
index a6101e52e9..f74611a939 100644
--- a/products/extensions/advanced-search/How-to-add-more-fields-to-product-search.md
+++ b/products/extensions/advanced-search/How-to-add-more-fields-to-product-search.md
@@ -13,14 +13,16 @@ In this example, we create a field called `productNumberPrefix` to make it searc
 
 **1. Decorate the ElasticsearchDefinition**
 
-```xml
-<service id="YourPluginNameSpace\ElasticsearchProductDefinitionDecorator" decorates="Shopware\Elasticsearch\Product\ElasticsearchProductDefinition">
-    <argument type="service" id=".inner"/>
-    <argument type="service" id="Shopware\Commercial\AdvancedSearch\Domain\Search\SearchLogic"/>
-</service>
+```PHP
+$services->set(YourPluginNameSpace\ElasticsearchProductDefinitionDecorator::class)
+    ->decorate(Shopware\Elasticsearch\Product\ElasticsearchProductDefinition::class)
+    ->args([
+        service('.inner'),
+        service(Shopware\Commercial\AdvancedSearch\Domain\Search\SearchLogic::class),
+    ]);
 ```
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace YourPluginNameSpace;
@@ -87,7 +89,7 @@ class ElasticsearchProductDefinitionDecorator extends AbstractElasticsearchDefin
 
 We need to update these data mapping to the Opensearch's server to make the change effective:
 
-```bash
+```BASH
 // Update the Elasticsearch indices mapping, introduce since 6.5.4.0
 bin/console es:mapping:update
 
@@ -99,11 +101,11 @@ bin/console es:index --no-queue
 
 So now the data is mapped and indexed, we need to make it searchable by adding the new field into the search config. Create a new migration and make sure it is run by reinstalling or updating the plugin:
 
-```bash
+```BASH
 bin/console database:create-migration --name AddNewPrefixProductNumberFieldIntoProductAdvancedSearch --plugin YourPlugin
 ```
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace YourPluginNameSpace\Migration;
diff --git a/products/extensions/advanced-search/How-to-define-your-custom-Elasticsearch-definition.md b/products/extensions/advanced-search/How-to-define-your-custom-Elasticsearch-definition.md
index b67c62647c..0982c5aa47 100644
--- a/products/extensions/advanced-search/How-to-define-your-custom-Elasticsearch-definition.md
+++ b/products/extensions/advanced-search/How-to-define-your-custom-Elasticsearch-definition.md
@@ -13,7 +13,7 @@ Each index will contain multiple language-based fields; refer to the [ADR](/docs
 
 For instance, to define your custom Elasticsearch definition (this definition will be used for later examples).
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace YourPluginNameSpace;
@@ -152,14 +152,16 @@ SQL;
 
 And register it in the container with tag `shopware.es.definition` and `advanced_search.supported_definition`
 
-```xml
-# YourPluginNameSpace should be changed to your respectively ElasticsearchDefinition and Definition classes
-<service id="YourPluginNameSpace\YourCustomElasticsearchDefinition">
-    <argument type="service" id="YourPluginNameSpace\YourCustomDefinition"/>
-    <argument type="service" id="Doctrine\DBAL\Connection"/>
-    <argument type="service" id="Shopware\Commercial\AdvancedSearch\Domain\Search\SearchLogic"/>
-
-    <tag name="shopware.es.definition"/>
-    <tag name="advanced_search.supported_definition"/>
-</service>
+```PHP
+// YourPluginNameSpace should be changed to your respectively ElasticsearchDefinition and Definition classes
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+$services->set(YourPluginNameSpace\YourCustomElasticsearchDefinition::class)
+    ->args([
+        service(YourPluginNameSpace\YourCustomDefinition::class),
+        service('Doctrine\DBAL\Connection'),
+        service(Shopware\Commercial\AdvancedSearch\Domain\Search\SearchLogic::class),
+    ])
+    ->tag('shopware.es.definition')
+    ->tag('advanced_search.supported_definition');
 ```
diff --git a/products/extensions/advanced-search/How-to-modify-search-logic.md b/products/extensions/advanced-search/How-to-modify-search-logic.md
index 366eab766c..deac89a606 100644
--- a/products/extensions/advanced-search/How-to-modify-search-logic.md
+++ b/products/extensions/advanced-search/How-to-modify-search-logic.md
@@ -19,14 +19,16 @@ This class is the central place to build the Elasticsearch query:
 
 To modify the search logic, you can decorate the search logic class and add your own logic into it:
 
-```xml
-<service id="YourPluginNameSpace\Domain\Search\SearchLogicDecorator" decorates="Shopware\Commercial\AdvancedSearch\Domain\Search\SearchLogic">
-    <argument type="service" id=".inner"/>
-    <argument type="service" id="Shopware\Commercial\AdvancedSearch\Domain\Configuration\ConfigurationLoader"/>
-</service>
+```PHP
+$services->set(YourPluginNameSpace\Domain\Search\SearchLogicDecorator::class)
+    ->decorate(Shopware\Commercial\AdvancedSearch\Domain\Search\SearchLogic::class)
+    ->args([
+        service('.inner'),
+        service(Shopware\Commercial\AdvancedSearch\Domain\Configuration\ConfigurationLoader::class),
+    ]);
 ```
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace YourPluginNameSpace;
diff --git a/products/extensions/b2b-components/order-approval/guides/04-add-new-approval-condition.md b/products/extensions/b2b-components/order-approval/guides/04-add-new-approval-condition.md
index 4471a1411a..c845bb26e6 100644
--- a/products/extensions/b2b-components/order-approval/guides/04-add-new-approval-condition.md
+++ b/products/extensions/b2b-components/order-approval/guides/04-add-new-approval-condition.md
@@ -15,7 +15,7 @@ To add a custom rule, following this document [Add custom rule](../../../../../g
 
 Example:
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace YourPluginNameSpace;
@@ -74,12 +74,12 @@ class CartAmountRule extends Rule
 }
 ```
 
-Then, we have to register it in our `services.xml` and tag it as `shopware.approval_rule.definition`
+Then, we have to register it in our `services.php` and tag it as `shopware.approval_rule.definition`
 
-```xml
- <service id="YourPluginNameSpace\CartAmountRule" public="true">
-    <tag name="shopware.approval_rule.definition"/>
- </service>
+```PHP
+$services->set(YourPluginNameSpace\CartAmountRule::class)
+    ->public()
+    ->tag('shopware.approval_rule.definition');
 ```
 
 ## App
diff --git a/products/extensions/b2b-suite-migration/development/adding-component.md b/products/extensions/b2b-suite-migration/development/adding-component.md
index 7d437c144e..1271a7affe 100644
--- a/products/extensions/b2b-suite-migration/development/adding-component.md
+++ b/products/extensions/b2b-suite-migration/development/adding-component.md
@@ -17,10 +17,9 @@ This section guides developers on adding a new component to the migration proces
 - Tag the class with `b2b.migration.configurator`.
    **Example**:
 
-   ```XML
-   <service id="Shopware\Commercial\B2B\B2BSuiteMigration\Components\EmployeeManagement\EmployeeManagementMigrationConfigurator">
-      <tag name="b2b.migration.configurator" priority="9000"/>
-   </service>
+   ```PHP
+   $services->set(Shopware\Commercial\B2B\B2BSuiteMigration\Components\EmployeeManagement\EmployeeManagementMigrationConfigurator::class)
+       ->tag('b2b.migration.configurator', ['priority' => 9000]);
    ```
 
   ```PHP
diff --git a/products/extensions/b2b-suite-migration/development/extending-migration.md b/products/extensions/b2b-suite-migration/development/extending-migration.md
index 772974518b..00071d1284 100644
--- a/products/extensions/b2b-suite-migration/development/extending-migration.md
+++ b/products/extensions/b2b-suite-migration/development/extending-migration.md
@@ -18,10 +18,9 @@ This section explains how to add new fields to an existing entity or introduce n
 
   **Example**:
 
-  ```XML
-  <service id="MigrationExtension\B2BMigration\B2BExtensionMigrationConfigurator">
-      <tag name="b2b.migration.configurator.extension"/>
-  </service>
+  ```PHP
+  $services->set(MigrationExtension\B2BMigration\B2BExtensionMigrationConfigurator::class)
+      ->tag('b2b.migration.configurator.extension');
   ```
 
   ```PHP
diff --git a/products/extensions/b2b-suite-migration/development/handler.md b/products/extensions/b2b-suite-migration/development/handler.md
index a4ae6c15f3..c4e735fc4c 100644
--- a/products/extensions/b2b-suite-migration/development/handler.md
+++ b/products/extensions/b2b-suite-migration/development/handler.md
@@ -53,7 +53,7 @@ Handlers allow custom logic to transform data before mapping it to the target fi
      <field handler="b2b.employee.employee_status_transformer">
          <source>currency_factor</source>
          <source>auth_id.b2b_store_front_auth.customer_id.customer.sales_channel_id.sales_channel.language_id</source>
-  
+
          <target>state_id</target>
          <target>expiration_date</target>
      </field>
@@ -76,15 +76,14 @@ Handlers allow custom logic to transform data before mapping it to the target fi
 
 To use a handler, implement a PHP class (e.g., `RolePermissionsTransformer`) that extends `Shopware\Commercial\B2B\B2BSuiteMigration\Core\Domain\DataTransformer\AbstractFieldTransformer` and tag it with `b2b.migration.transformer` in your service configuration.
 
-```XML
-<service id="Shopware\Commercial\B2B\B2BSuiteMigration\Components\QuoteManagement\DataTransformer\QuoteComment\StateTransformer" lazy="true">
-    <argument type="service" id="Shopware\Core\Framework\Extensions\ExtensionDispatcher"/>
-
-    <tag name="b2b.migration.transformer" />
-</service>
+```PHP
+$services->set(Shopware\Commercial\B2B\B2BSuiteMigration\Components\QuoteManagement\DataTransformer\QuoteComment\StateTransformer::class)
+    ->lazy()
+    ->args([service(Shopware\Core\Framework\Extensions\ExtensionDispatcher::class)])
+    ->tag('b2b.migration.transformer');
 ```
 
-The best practice is to mark this service as `lazy="true"` to improve performance by loading it only when needed.
+The best practice is to mark this service as `lazy` to improve performance by loading it only when needed.
 
 ## Handler Implementation
 
@@ -134,7 +133,7 @@ protected function requiredSourceFields(): array
     ```XML
     <field source="foo" target="permissions" handler="b2b.employee.employee_status_transformer"/>
     ```
-  
+
     ```PHP
     protected function requiredSourceFields(): array
     {
@@ -148,11 +147,11 @@ protected function requiredSourceFields(): array
     <field handler="b2b.employee.employee_status_transformer">
         <source>foo</source>
         <source>bar</source>
-      
+
         <target>permissions</target>
     </field>
     ```
-  
+
     ```PHP
     protected function requiredSourceFields(): array
     {
@@ -180,7 +179,7 @@ protected function _transform(
 - **Return Value**:
   - For a single target field: Return a single value (e.g., string, integer, or JSON-encoded string).
   - For multiple target fields: Return an associative array where keys are target field names and values are the corresponding transformed values.
-  
+
 #### Examples
 
 **_Example 1: Single Source to Single Target_**
@@ -226,7 +225,7 @@ Transform multiple source fields to multiple target fields, such as generating a
     <field handler="b2b.quote_line_item.line_item_price_transformer">
       <source>list_id</source>
       <source>mode</source>
-  
+
       <target>order_id</target>
       <target>order_version_id</target>
     </field>
@@ -241,7 +240,7 @@ public function transform(Field $field, array $sourceRecord): mixed
     if (!isset($field->getSourceElements()['list_id']) || !isset($field->getSourceElements()['mode'])) {
         // Handle missing required source fields
     }
-    
+
     $listId = $sourceRecord['list_id'];
     $mode = $sourceRecord['mode'];
     // Perform transformation logic based on listId and mode
diff --git a/products/extensions/b2b-suite/guides/core/authentication.md b/products/extensions/b2b-suite/guides/core/authentication.md
index c82803a9bc..3320e81209 100644
--- a/products/extensions/b2b-suite/guides/core/authentication.md
+++ b/products/extensions/b2b-suite/guides/core/authentication.md
@@ -54,7 +54,7 @@ CREATE TABLE IF NOT EXISTS `b2b_my` (
 This modifier column allows you to store the context owner independent of the actual source table of the context owner.
 You can access the current context owner always through the identity.
 
-```php
+```PHP
 [...]
 
 /** @var AuthenticationService $authenticationService */
@@ -75,7 +75,7 @@ echo 'The context owner id ' . $ownershipContext->contextOwnerId . '\n';
 
 You can even load the whole identity through the `AuthenticationService`.
 
-```php
+```PHP
 [...]
 
 $ownerIdentity = $authenticationService->getIdentityByAuthId($contextOwnerId);
@@ -87,7 +87,7 @@ $ownerIdentity = $authenticationService->getIdentityByAuthId($contextOwnerId);
 
 Sometimes you want to flag records to be owned by certain identities.
 
-```sql
+```SQL
 CREATE TABLE IF NOT EXISTS `b2b_my` (
     `id` INT(11) NOT NULL AUTO_INCREMENT,
     `auth_id` INT(11) NULL DEFAULT NULL,
@@ -103,7 +103,7 @@ CREATE TABLE IF NOT EXISTS `b2b_my` (
 
 To fill this column, we again access the current identity, but instead of the `contextOwnerId`, we access the `authId`.
 
-```php
+```PHP
 [...]
 
 $ownershipContext = $authenticationService
@@ -119,7 +119,7 @@ The B2B Suite views the context owner as some kind of admin that, from the persp
 
 Therefore, commonly used queries are:
 
-```php
+```PHP
 /** @var Connection $connection */
 $connection = $this->container->get('dbal_connection');
 /** @var Identity $identity */
@@ -174,11 +174,11 @@ Example implementations are either: `Shopware\B2B\Debtor\Framework\DebtorIdentit
 
 In the *CredentialsBuilder*, you create the *CredentialsEntity*, which is used for logging in the B2B Suite.
 
-```php
+```PHP
     public function createCredentials(array $parameters): AbstractCredentialsEntity
     {
         $entity = new CredentialsEntity();
-    
+
         $entity->email = $parameters['email'];
         $entity->salesChannelId = IdValue::create($this->contextProvider->getSalesChannelContext()->getSalesChannel()->getId());
         $entity->customerScope = $this->systemConfigService->get('core.systemWideLoginRegistration.isCustomerBoundToSalesChannel');
@@ -196,23 +196,23 @@ Next, you have to provide the means to register your identity on login. This is
 The *LoginContextService* is passed as an argument to help you retrieve and create the appropriate auth and
 context owner ids. Notice that the interface is designed to be chained to create dependent auth ids on the fly.
 
-```php
+```PHP
 [...]
     public function fetchIdentityByCredentials(CredentialsEntity $credentialsEntity, LoginContextService $contextService, bool $isApi = false): Identity
     {
         if (!$credentialsEntity->email) {
             throw new NotFoundException('Unable to handle context');
         }
-        
+
         $entity = $this->yourEntityRepository->fetchOneByEmail($email);
 
         /** @var DebtorIdentity $debtorIdentity */
         $debtorIdentity = $this->debtorRepository->fetchIdentityById($entity->debtor->id, $contextService);
-        
+
         $authId = $contextService->getAuthId(YourEntityRepository::class, $entity->id, $debtorIdentity->getAuthId());
-        
+
         $this->yourEntityRepository->setAuthId($entity->id, $authId);
-        
+
         return new YourEntityIdentity($authId, (int) $entity->id, YourEntityRepository::TABLE_NAME, $entity, $debtorIdentity);
     }
 [...]
@@ -220,12 +220,10 @@ context owner ids. Notice that the interface is designed to be chained to create
 
 Finally, you register your authentication provider (in our case a repository) as a tagged service through the DIC.
 
-```xml
-<service id="b2b_my.contact_authentication_identity_loader" class="Shopware\B2B\My\AuthenticationIdentityLoader">
-    [...]
-
-    <tag name="b2b_front_auth.authentication_repository" />
-</service>
+```PHP
+$services->set('b2b_my.contact_authentication_identity_loader', Shopware\B2B\My\AuthenticationIdentityLoader::class)
+    // [...]
+    ->tag('b2b_front_auth.authentication_repository');
 ```
 
 ## Sales representative
diff --git a/products/extensions/b2b-suite/guides/core/entity-acl.md b/products/extensions/b2b-suite/guides/core/entity-acl.md
index 5f2bbad1e4..a8690764e6 100644
--- a/products/extensions/b2b-suite/guides/core/entity-acl.md
+++ b/products/extensions/b2b-suite/guides/core/entity-acl.md
@@ -40,10 +40,10 @@ The ACL is represented as M:N relation tables in the database and always looks l
 ```sql
 CREATE TABLE `b2b_acl_*` (
     `id` INT(11) NOT NULL AUTO_INCREMENT,
-    `entity_id` INT(11) NOT NULL, 
+    `entity_id` INT(11) NOT NULL,
     `referenced_entity_id` INT(11) NOT NULL,
     `grantable` TINYINT(4) NOT NULL DEFAULT '0',
-    
+
     [...]
 );
 ```
@@ -73,7 +73,7 @@ The address ACL repository can be retrieved through the DIC by the `b2b_address.
 
 The repository then provides the following methods. If you are already familiar with other ACL implementations, most methods will look quite familiar.
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace Shopware\B2B\Acl\Framework;
@@ -88,16 +88,16 @@ class AclRepository
      * @throws AclUnsupportedContextException
      */
     public function allow($context, IdValue $subjectId, bool $grantable = false): void
-    { 
-        [...] 
+    {
+        [...]
     }
 
     /**
      * @throws AclUnsupportedContextException
      */
-    public function allowAll($context, array $subjectIds, bool $grantable = false): void 
-    { 
-        [...] 
+    public function allowAll($context, array $subjectIds, bool $grantable = false): void
+    {
+        [...]
     }
 
     /**
@@ -119,50 +119,50 @@ class AclRepository
     /**
      * @throws AclUnsupportedContextException
      */
-    public function isAllowed($context, IdValue $subjectId): bool 
-    { 
-        [...] 
+    public function isAllowed($context, IdValue $subjectId): bool
+    {
+        [...]
     }
 
     /**
      * @throws AclUnsupportedContextException
      */
-    public function isGrantable($context, IdValue $subjectId): bool 
-    { 
-        [...] 
+    public function isGrantable($context, IdValue $subjectId): bool
+    {
+        [...]
     }
 
     /**
      * @throws AclUnsupportedContextException
      * @return IdValue[]
      */
-    public function getAllAllowedIds($context): array 
-    { 
-        [...] 
+    public function getAllAllowedIds($context): array
+    {
+        [...]
     }
 
     /**
      * @throws AclUnsupportedContextException
      */
-    public function fetchAllGrantableIds($context): array 
+    public function fetchAllGrantableIds($context): array
     {
-        [...] 
+        [...]
     }
 
     /**
      * @throws AclUnsupportedContextException
      */
-    public function fetchAllDirectlyIds($context): array 
-    { 
-        [...] 
+    public function fetchAllDirectlyIds($context): array
+    {
+        [...]
     }
 
     /**
      * @throws AclUnsupportedContextException
      */
-    public function getUnionizedSqlQuery($context): AclQuery 
-    { 
-        [...] 
+    public function getUnionizedSqlQuery($context): AclQuery
+    {
+        [...]
     }
 }
 ```
@@ -194,14 +194,14 @@ Debtors, for example, are unknown to the ACL, so all debtor identities will trig
 
 A standard use case is to allow records to a user, this simple code snippet can do this:
 
-```php
+```PHP
 $aclAddressRepository = $this->container->get('b2b_address.acl_repository');
 $contactRepository = $this->container->get('b2b_contact.repository');
 
 $contact = $contactRepository->fetchOneById(1);
 
 $aclAddressRepository->allow(
-    $contact, // the contact 
+    $contact, // the contact
     22, // the id of the address
     true // whether the contact may grant access to other contacts
 );
@@ -209,18 +209,18 @@ $aclAddressRepository->allow(
 
 We can then deny the access just by this:
 
-```php
+```PHP
 $aclAdressRepository->deny(
-    $contact, // the contact 
+    $contact, // the contact
     22, // the id of the address
 );
 ```
 
 or just set it not grantable, by
 
-```php
+```PHP
 $aclAdressRepository->allow(
-    $contact, // the contact 
+    $contact, // the contact
     22, // the id of the address
     false // whether the contact may grant access to other contacts
 );
@@ -230,18 +230,18 @@ $aclAdressRepository->allow(
 
 If you want to know whether a certain contact can access an entity, you can call `isAllowed`.
 
-```php
+```PHP
 $aclAdressRepository->isAllowed(
-    $contact, // the contact 
+    $contact, // the contact
     22, // the id of the address
 );
 ```
 
 Or you just want to check whether an entity can be granted by a contact.
 
-```php
+```PHP
 $aclAdressRepository->isGrantable(
-    $contact, // the contact 
+    $contact, // the contact
     22, // the id of the address
 );
 ```
@@ -250,7 +250,7 @@ One of the more complex problems you might face is that you want to filter a que
 
 This can be achieved by this snippet:
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace My\Namespace;
@@ -294,7 +294,7 @@ So let's take a look at the addresses again.
 You first need to define the relations from role and contact to your entity.
 This is achieved by creating small classes that contain particular information:
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace Shopware\B2B\Address\Framework;
@@ -333,7 +333,7 @@ An identical class exists for the `role<->address` relation.
 Now we need to tell the B2B Suite to create the necessary tables. In Shopware, this must be done during the plugin installation process.
 Because the container is not yet set up with the B2B Suite services, we use a static factory method in the following code:
 
-```php
+```PHP
 use Shopware\B2B\Acl\Framework\AclDdlService;
 use Shopware\B2B\Address\Framework\AddressContactTable;
 
@@ -343,19 +343,17 @@ AclDdlService::create()->createTable(new AddressContactTable());
 Now the table exists, but we must still make the table definition accessible through the DIC, so the ACL component can set up appropriate repositories.
 This is achieved through a tag in the service definition:
 
-```xml
-<service id="b2b_address.contact_acl_table" class="Shopware\B2B\Address\Framework\AddressContactAclTable">
-    <tag name="b2b_acl.table"/>
-</service>
+```PHP
+$services->set('b2b_address.contact_acl_table', Shopware\B2B\Address\Framework\AddressContactAclTable::class)
+    ->tag('b2b_acl.table');
 ```
 
-Finally, we need to register the service in the DIC. This is done by this XML snippet:
+Finally, we need to register the service in the DIC. This is done by this PHP snippet:
 
-```xml
-<service id="b2b_address.acl_repository" class="Shopware\B2B\Acl\Framework\AclRepository">
-    <factory service="b2b_acl.repository_factory" method="createRepository"/>
-    <argument type="string">s_user_addresses</argument>
-</service>
+```PHP
+$services->set('b2b_address.acl_repository', Shopware\B2B\Acl\Framework\AclRepository::class)
+    ->factory([service('b2b_acl.repository_factory'), 'createRepository'])
+    ->args(['s_user_addresses']);
 ```
 
 There we are; the addresses are ACL-ified entities.
@@ -367,7 +365,7 @@ other contexts than *contact* and *role*. For this, you have to create a differe
 An `AclContextResolver` is responsible for extracting the primary key out of a given context object and produces a query that joins the main ACL table.
 This is done by implementing `getQuery`, `isMainContext`, and `extractId`.
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace My\Namespace;
@@ -385,19 +383,19 @@ class MyContextResolver extends AclContextResolver
 
     public function extractId($context): int
     {
-        // your implementation here    
+        // your implementation here
     }
 
     public function isMainContext(): bool
     {
-        // your implementation here    
+        // your implementation here
     }
 }
 ```
 
 A rather generic implementation for `getQuery` that just filters for a given `contextId` look like this:
 
-```php
+```PHP
 public function getQuery(string $aclTableName, int $contextId, QueryBuilder $queryBuilder): AclQuery
 {
     $mainPrefix = $this->getNextPrefix();
@@ -416,7 +414,7 @@ Notice the `getMainPrefix` call. This allows the ACL component to be joined with
 
 An implementation of extract id usually looks like this:
 
-```php
+```PHP
 public function extractId($context): int
 {
     if ($context instanceof ContactIdentity) {
diff --git a/products/extensions/b2b-suite/guides/core/overload-classes.md b/products/extensions/b2b-suite/guides/core/overload-classes.md
index 4a8106ccec..4f784e51ce 100644
--- a/products/extensions/b2b-suite/guides/core/overload-classes.md
+++ b/products/extensions/b2b-suite/guides/core/overload-classes.md
@@ -13,67 +13,84 @@ nav:
 
 To add new functionality or overload existing classes to change functionality, the B2B Suite uses the [Dependency Injection](../../../../../guides/plugins/plugins/plugin-fundamentals/dependency-injection) as an extension system instead of events and hooks, which Shopware uses.
 
-### How does a services.xml look like
-
-In the release package, our service.xml looks like this:
-
-```xml
-<?xml version="1.0" encoding="UTF-8" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-    <parameters>
-        <parameter key="b2b_role.repository_class">Shopware\B2B\Role\Framework\RoleRepository</parameter>
-        [...]
-    </parameters>
-    <services>
-        <service id="b2b_role.repository_abstract" abstract="true">
-            <argument type="service" id="dbal_connection"/>
-            <argument type="service" id="b2b_common.repository_dbal_helper"/>
-        </service>
-        [...]
-
-        <service id="b2b_role.repository" class="%b2b_role.repository_class%" parent="b2b_role.repository_abstract"/>
-        [...]
-    </services>
-</container>
+### How does a services.php look like
+
+In the release package, our services.php looks like this:
+
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Shopware\B2B\Role\Framework\RoleRepository;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+    $parameters = $configurator->parameters();
+
+    $parameters->set('b2b_role.repository_class', RoleRepository::class);
+
+    $services->set('b2b_role.repository_abstract')
+        ->abstract(true)
+        ->args([
+            service('dbal_connection'),
+            service('b2b_common.repository_dbal_helper'),
+        ]);
+    // [...]
+
+    $services->set('b2b_role.repository', '%b2b_role.repository_class%')
+        ->parent('b2b_role.repository_abstract');
+    // [...]
+};
 ```
 
 For development (GitHub), it looks like this:
 
-```xml
-<?xml version="1.0" encoding="UTF-8" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-    <services>
-        <service id="b2b_role.repository" class="Shopware\B2B\Role\Framework\RoleRepository">
-            <argument type="service" id="dbal_connection"/>
-            <argument type="service" id="b2b_common.repository_dbal_helper"/>
-        </service>
-
-        <service id="b2b_role.grid_helper" class="Shopware\B2B\Common\Controller\GridHelper">
-            <argument type="service" id="b2b_role.repository"/>
-        </service>
-
-        <service id="b2b_role.crud_service" class="Shopware\B2B\Role\Framework\RoleCrudService">
-            <argument type="service" id="b2b_role.repository"/>
-            <argument type="service" id="b2b_role.validation_service"/>
-        </service>
-
-        <service id="b2b_role.validation_service" class="Shopware\B2B\Role\Framework\RoleValidationService">
-            <argument type="service" id="b2b_common.validation_builder"/>
-            <argument type="service" id="validator"/>
-        </service>
-
-        <service id="b2b_role.acl_route_table" class="Shopware\B2B\Role\Framework\AclRouteAclTable">
-            <tag name="b2b_acl.table"/>
-        </service>
-    </services>
-</container>
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Shopware\B2B\Role\Framework\RoleRepository;
+use Shopware\B2B\Common\Controller\GridHelper;
+use Shopware\B2B\Role\Framework\RoleCrudService;
+use Shopware\B2B\Role\Framework\RoleValidationService;
+use Shopware\B2B\Role\Framework\AclRouteAclTable;
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set('b2b_role.repository', RoleRepository::class)
+        ->args([
+            service('dbal_connection'),
+            service('b2b_common.repository_dbal_helper'),
+        ]);
+
+    $services->set('b2b_role.grid_helper', GridHelper::class)
+        ->args([service('b2b_role.repository')]);
+
+    $services->set('b2b_role.crud_service', RoleCrudService::class)
+        ->args([
+            service('b2b_role.repository'),
+            service('b2b_role.validation_service'),
+        ]);
+
+    $services->set('b2b_role.validation_service', RoleValidationService::class)
+        ->args([
+            service('b2b_common.validation_builder'),
+            service('validator'),
+        ]);
+
+    $services->set('b2b_role.acl_route_table', AclRouteAclTable::class)
+        ->tag('b2b_acl.table');
+};
 ```
 
-We generate the new services.xml files for our package automatically.
+We generate the new services.php files for our package automatically.
 
 ### How do I use it
 
@@ -83,18 +100,23 @@ You only have to change the parameter or overload the service id.
 
 Your service file could look like this:
 
-```xml
-<?xml version="1.0" encoding="UTF-8" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-    <services>
-        <service id="b2b_role.repository" class="Your/Class" parent="b2b_role.repository_abstract">
-            <argument id="Your/own/class" type="service"/>
-        </service>
-        [...]
-    </services>
-</container>
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+use Your\Own\YourClass;
+
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set('b2b_role.repository', YourClass::class)
+        ->parent('b2b_role.repository_abstract')
+        ->args([service(YourClass::class)]);
+    // [...]
+};
 ```
 
 Just define a class with the same service id as our normal class and add our abstract class as the parent.
@@ -102,24 +124,24 @@ After that, add your own arguments or override ours.
 
 An example of your class could look like this:
 
-```php
+```PHP
 <?php declare(strict_types=1);
-    
+
 [...]
-    
+
 class YourRoleRepository extends RoleRepository
 {
     public array $myService;
-        
+
     public function __construct()
     {
         $args = func_get_args();
-        
-        $this->myService = array_pop($args);       
-        
+
+        $this->myService = array_pop($args);
+
         parent::__construct(... $args);
     }
-         
+
     public function updateRole(RoleEntity $role): RoleEntity
     {
         // your stuff
diff --git a/products/extensions/b2b-suite/guides/core/rest-api.md b/products/extensions/b2b-suite/guides/core/rest-api.md
index 9b6e7747c4..ede057e50c 100644
--- a/products/extensions/b2b-suite/guides/core/rest-api.md
+++ b/products/extensions/b2b-suite/guides/core/rest-api.md
@@ -24,7 +24,7 @@ A REST-API Controller is just a plain old PHP-Class, registered to the DIC.
 An action is a public method suffixed with `Action`.
 It always gets called with the request implementation derived from Shopware default `Shopware\B2B\Common\MvcExtension\Request` as a parameter.
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace My\Namespace;
@@ -49,7 +49,7 @@ To register your own routes, you must add a `RouteProvider` to the routing servi
 First, we create the routing provider containing all routing information.
 Routes themselves are defined as simple arrays, just like this:
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace My\Namespace\DependencyInjection;
@@ -74,12 +74,11 @@ class MyApiRouteProvider implements RouteProvider
 
 Now the route provider and the controller are registered to the DIC.
 
-```xml
-<service id="my.controller" class="My\Namespace\MyApiController"/>
+```PHP
+$services->set('my.controller', My\Namespace\MyApiController::class);
 
-<service id="my.api_route_provider" class="My\Namespace\DependencyInjection\MyApiRouteProvider">
-    <tag name="b2b_common.rest_route_provider"/>
-</service>
+$services->set('my.api_route_provider', My\Namespace\DependencyInjection\MyApiRouteProvider::class)
+    ->tag('b2b_common.rest_route_provider');
 ```
 
 Notice that the route provider is tagged as a `b2b_common.rest_route_provider`.
@@ -92,7 +91,7 @@ Refer to this linked documentation to learn more about placeholders and placehol
 
 If you want to use parameters, you have to define an order in which the parameters should be passed to the action:
 
-```php
+```PHP
 [
     'GET', // the HTTP method
     '/my/hello/{name}', // the sub-route will be concatenated to http://my-shop.de/api/b2b/my/hello/world
@@ -104,7 +103,7 @@ If you want to use parameters, you have to define an order in which the paramete
 
 And now, you can use the placeholders value as a parameter:
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 public function helloAction(string $name, Request $request)
diff --git a/products/extensions/b2b-suite/guides/storefront/how-to-extend-the-storefront.md b/products/extensions/b2b-suite/guides/storefront/how-to-extend-the-storefront.md
index 08cb7fcaa2..35da092254 100644
--- a/products/extensions/b2b-suite/guides/storefront/how-to-extend-the-storefront.md
+++ b/products/extensions/b2b-suite/guides/storefront/how-to-extend-the-storefront.md
@@ -11,19 +11,21 @@ In order to be able to extend the templates of the B2B Suite with another plugin
 
 ## Registering a TemplateNamespaceHierarchyBuilder
 
-Register the `TemplateNamespaceHierarchyBuilder` by tagging it in the `services.xml` file of your plugin.
-
-```xml
-<?xml version="1.0" encoding="UTF-8" ?>
-<container xmlns="http://symfony.com/schema/dic/services"
-           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-           xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
-    <services>
-        <service id="MyPlugin\Framework\Adapter\Twig\NamespaceHierarchy\TemplateNamespaceHierarchyBuilder">
-            <tag name="shopware.twig.hierarchy_builder" priority="750"/>
-        </service>
-    </services>
-</container>
+Register the `TemplateNamespaceHierarchyBuilder` by tagging it in the `services.php` file of your plugin.
+
+```PHP
+// <plugin root>/src/Resources/config/services.php
+<?php declare(strict_types=1);
+
+use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+use MyPlugin\Framework\Adapter\Twig\NamespaceHierarchy\TemplateNamespaceHierarchyBuilder;
+
+return static function (ContainerConfigurator $configurator): void {
+    $services = $configurator->services();
+
+    $services->set(TemplateNamespaceHierarchyBuilder::class)
+        ->tag('shopware.twig.hierarchy_builder', ['priority' => 750]);
+};
 ```
 
 The really important part here is the priority. `750` should work fine for most cases, but if you are having problems here, play around with the priority.
@@ -32,7 +34,7 @@ The really important part here is the priority. `750` should work fine for most
 
 The `TemplateNamespaceHierarchyBuilder` looks like this. Please replace `MyPlugin` with the name of your plugin.
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace MyPlugin\Framework\Adapter\Twig\NamespaceHierarchy;
diff --git a/products/extensions/migration-assistant/guides/creating-a-new-migration-profile.md b/products/extensions/migration-assistant/guides/creating-a-new-migration-profile.md
index fb21732efe..3d5634a935 100644
--- a/products/extensions/migration-assistant/guides/creating-a-new-migration-profile.md
+++ b/products/extensions/migration-assistant/guides/creating-a-new-migration-profile.md
@@ -13,7 +13,7 @@ If you want to migrate your data from a different source system than Shopware, c
 
 First, it is required that you already have installed the [Migration Assistant](https://github.com/shopware/SwagMigrationAssistant) plugin in Shopware 6 and have created a demo source system database with a `product` table. To create the table, use this SQL statement:
 
-```sql
+```SQL
 CREATE TABLE product
 (
   id int PRIMARY KEY NOT NULL AUTO_INCREMENT,
@@ -31,7 +31,7 @@ This table should simulate a simple third-party source system, which should be m
 
 In the first step, you have to create a new profile for your source system:
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace SwagMigrationOwnProfileExample;
@@ -77,19 +77,18 @@ class OwnProfile implements ProfileInterface
 }
 ```
 
-The profile itself does not contain any logic and is used to bundle the executing classes. To use this profile, you have to register and tag it in the `service.xml` with `shopware.migration.profile`:
+The profile itself does not contain any logic and is used to bundle the executing classes. To use this profile, you have to register and tag it in the `services.php` with `shopware.migration.profile`:
 
-```html
-<service id="SwagMigrationOwnProfileExample\Profile\OwnProfile\OwnProfile">
-    <tag name="shopware.migration.profile"/>
-</service>
+```PHP
+$services->set(SwagMigrationOwnProfileExample\Profile\OwnProfile\OwnProfile::class)
+    ->tag('shopware.migration.profile');
 ```
 
 ## Creating a gateway
 
 Next, you have to create a new gateway which supports your profile:
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace SwagMigrationOwnProfileExample\Profile\OwnProfile\Gateway;
@@ -200,21 +199,24 @@ class OwnLocaleGateway implements GatewayInterface
 }
 ```
 
-As you have seen above, the gateway uses the `ConnectionFactory` to test the connection to the source system. You can also implement your own way to check this, but using this factory is the simplest way for a gateway to connect to a local database. Like the profile, you have to register the new gateway in the `service.xml` and tag it with `shopware.migration.gateway`:
+As you have seen above, the gateway uses the `ConnectionFactory` to test the connection to the source system. You can also implement your own way to check this, but using this factory is the simplest way for a gateway to connect to a local database. Like the profile, you have to register the new gateway in the `services.php` and tag it with `shopware.migration.gateway`:
 
-```html
-<service id="SwagMigrationOwnProfileExample\Profile\OwnProfile\Gateway\OwnLocaleGateway">
-    <argument type="service" id="SwagMigrationAssistant\Migration\Gateway\Reader\ReaderRegistry"/>
-    <argument type="service" id="SwagMigrationAssistant\Profile\Shopware\Gateway\Connection\ConnectionFactory"/>
-    <tag name="shopware.migration.gateway"/>
-</service>
+```PHP
+use function Symfony\Component\DependencyInjection\Loader\Configurator\service;
+
+$services->set(SwagMigrationOwnProfileExample\Profile\OwnProfile\Gateway\OwnLocaleGateway::class)
+    ->args([
+        service(SwagMigrationAssistant\Migration\Gateway\Reader\ReaderRegistry::class),
+        service(SwagMigrationAssistant\Profile\Shopware\Gateway\Connection\ConnectionFactory::class),
+    ])
+    ->tag('shopware.migration.gateway');
 ```
 
 ## Creating a credentials page
 
 If you want to try your current progress in the Administration, you can select the profile and gateway in the migration wizard. If you try to go to the next page, there will be an error message because no credentials page was found. To create a new credentials page, you have to add an `index.js` for your new component into `Resources/app/administration/src/own-profile/profile`:
 
-```javascript
+```JAVASCRIPT
 import { Component } from 'src/core/shopware';
 import template from './swag-migration-profile-ownProfile-local-credential-form.html.twig';
 
@@ -296,7 +298,7 @@ Component.register('swag-migration-profile-ownProfile-local-credential-form', {
 
 As you can see above, currently, the template does not exist and you have to create this file: `swag-migration-profile-ownProfile-local-credential-form.html.twig`
 
-```html
+```HTML
 {% block own_profile_page_credentials %}
     <div class="swag-migration-wizard swag-migration-wizard-page-credentials"
          @keypress.enter="onKeyPressEnter">
@@ -374,7 +376,7 @@ Note that the component name isn't random and consists of:
 
 To see your credentials page, you have to register this component in your `main.js`:
 
-```javascript
+```JAVASCRIPT
 import './own-profile/profile';
 ```
 
@@ -382,7 +384,7 @@ import './own-profile/profile';
 
 Now the credential page is loaded in the Administration and the connection check will succeed. But there is no data selection if you open the data selection table. To add an entry to this table, you have to create a `ProductDataSet` first:
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace SwagMigrationOwnProfileExample\Profile\OwnProfile\DataSelection\DataSet;
@@ -413,7 +415,7 @@ class ProductDataSet extends DataSet
 
 Now you have to use this `ProductDataSet` in the new `ProductDataSelection`:
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace SwagMigrationOwnProfileExample\Profile\OwnProfile\DataSelection;
@@ -475,23 +477,21 @@ class ProductDataSelection implements DataSelectionInterface
 The order in the `getDataSets` array is important as it determines the order in which the entities are processed. Because of that, the manufacturers, for example, have to be positioned before the products so that the products can use those later on.
 :::
 
-To see the created `ProductDataSelection` in the Administration, you have to register it both in the `services.xml` and tag them with `shopware.migration.data_selection` and `shopware.migration.data_set`:
+To see the created `ProductDataSelection` in the Administration, you have to register it both in the `services.php` and tag them with `shopware.migration.data_selection` and `shopware.migration.data_set`:
 
-```html
-<service id="SwagMigrationOwnProfileExample\Profile\OwnProfile\DataSelection\ProductDataSelection">
-    <tag name="shopware.migration.data_selection"/>
-</service>
+```PHP
+$services->set(SwagMigrationOwnProfileExample\Profile\OwnProfile\DataSelection\ProductDataSelection::class)
+    ->tag('shopware.migration.data_selection');
 
-<service id="SwagMigrationOwnProfileExample\Profile\OwnProfile\DataSelection\DataSet\ProductDataSet">
-    <tag name="shopware.migration.data_set"/>
-</service>
+$services->set(SwagMigrationOwnProfileExample\Profile\OwnProfile\DataSelection\DataSet\ProductDataSet::class)
+    ->tag('shopware.migration.data_set');
 ```
 
 ## Creating a product gateway reader
 
 Currently, you can see the `DataSelection` in the Administration, but if you select it and start a migration, no product will be migrated. That is because the gateway `read` function isn't implemented yet. But before you can implement this function, you have to create a new `ProductReader` first:
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace SwagMigrationOwnProfileExample\Profile\OwnProfile\Gateway\Reader;
@@ -568,19 +568,20 @@ class ProductReader extends AbstractReader
 }
 ```
 
-Then you have to register this in `services.xml` and tag it with `shopware.migration.reader`:
+Then you have to register this in `services.php` and tag it with `shopware.migration.reader`:
 
-```html
-<service id="SwagMigrationOwnProfileExample\Profile\OwnProfile\Gateway\Reader\ProductReader"
-    parent="SwagMigrationAssistant\Profile\Shopware\Gateway\Local\Reader\AbstractReader">
-    <argument type="service" id="SwagMigrationAssistant\Profile\Shopware\Gateway\Connection\ConnectionFactory"/>
-    <tag name="shopware.migration.reader"/>
-</service>
+```PHP
+$services->set(SwagMigrationOwnProfileExample\Profile\OwnProfile\Gateway\Reader\ProductReader::class)
+    ->parent(SwagMigrationAssistant\Profile\Shopware\Gateway\Local\Reader\AbstractReader::class)
+    ->args([
+        service(SwagMigrationAssistant\Profile\Shopware\Gateway\Connection\ConnectionFactory::class),
+    ])
+    ->tag('shopware.migration.reader');
 ```
 
 Once the `ProductReader` is created and registered, you can use it in the `read` method of the `OwnLocaleGateway`:
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace SwagMigrationOwnProfileExample\Profile\OwnProfile\Gateway;
@@ -693,7 +694,7 @@ class OwnLocaleGateway implements GatewayInterface
 
 By using the gateway reader, you fetch all products but don't use this data yet. In this step, you implement the logic of the converter:
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace SwagMigrationOwnProfileExample\Profile\OwnProfile\Converter;
@@ -838,19 +839,20 @@ class ProductConverter extends ShopwareConverter
 
 If you don't know which properties or requirements your entity has in Shopware 6, you may check the corresponding `EntityDefinition`. For this example, look at the `ProductEntityDefinition` to know how to convert the data exactly.
 
-To use this converter, you must register it in the `services.xml`:
+To use this converter, you must register it in the `services.php`:
 
-```html
-<service id="SwagMigrationOwnProfileExample\Profile\OwnProfile\Converter\ProductConverter">
-    <argument type="service" id="SwagMigrationAssistant\Migration\Mapping\MappingService"/>
-    <argument type="service" id="SwagMigrationAssistant\Migration\Logging\LoggingService"/>
-    <tag name="shopware.migration.converter"/>
-</service>
+```PHP
+$services->set(SwagMigrationOwnProfileExample\Profile\OwnProfile\Converter\ProductConverter::class)
+    ->args([
+        service(SwagMigrationAssistant\Migration\Mapping\MappingService::class),
+        service(SwagMigrationAssistant\Migration\Logging\LoggingService::class),
+    ])
+    ->tag('shopware.migration.converter');
 ```
 
 To write new entities, you have to create a new writer class, but for the product entity, you can use the `ProductWriter`:
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace SwagMigrationAssistant\Migration\Writer;
diff --git a/products/extensions/migration-assistant/guides/decorating-a-shopware-migration-assistant-converter.md b/products/extensions/migration-assistant/guides/decorating-a-shopware-migration-assistant-converter.md
index 93231e85ec..b34b108e21 100644
--- a/products/extensions/migration-assistant/guides/decorating-a-shopware-migration-assistant-converter.md
+++ b/products/extensions/migration-assistant/guides/decorating-a-shopware-migration-assistant-converter.md
@@ -23,7 +23,7 @@ Instead of creating a new plugin for the migration, you might want to add migrat
 
 In this example, the user should be able to map the manufacturer while no new manufacturer will be created. You have to create a new premapping reader to achieve this:
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace SwagMigrationExtendConverterExample\Profile\Shopware\Premapping;
@@ -182,7 +182,7 @@ The created premapping reader fetches all manufacturers of the source system, ge
 
 Currently, the premapping card has no snippets at all, so you have to create a new snippet file for the title:
 
-```json
+```JSON
 {
      "swag-migration": {
          "index": {
@@ -198,7 +198,7 @@ Currently, the premapping card has no snippets at all, so you have to create a n
 
 This file has to be located in `Resources\administration\snippet` and registered in `Resources\administration\main.js` of the plugin like this:
 
-```javascript
+```JAVASCRIPT
 import enGBSnippets from './snippet/en-GB.json';
 
 const { Application } = Shopware;
@@ -216,7 +216,7 @@ Now your new premapping card has a correct title.
 
 After creating your premapping reader, you have a new premapping card, but this premapping is currently not in use. To map the product manufacturers of the source system to your premapping values, you have to decorate one of the Shopware product migration converters. In this example, only the `Shopware55ProductConverter` is decorated, but if you want to decorate all Shopware migration converters, you have to do the same:
 
-```php
+```PHP
  <?php declare(strict_types=1);
 
  namespace SwagMigrationExtendConverterExample\Profile\Shopware\Converter;
@@ -301,16 +301,17 @@ After creating your premapping reader, you have a new premapping card, but this
 
 Your new decorated product migration converter checks if a manufacturer is set and searches for the premapping via the `MappingService`. If a premapping is found, the migration converter uses the converted value of the original converter, adds the manufacturer uuid, and returns the new `ConvertStruct`.
 
-In the end, you have to register your decorated converter in your `services.xml`:
-
-```html
-<service id="SwagMigrationExtendConverterExample\Profile\Shopware\Converter\Shopware55DecoratedProductConverter"
-          decorates="SwagMigrationAssistant\Profile\Shopware55\Converter\Shopware55ProductConverter">
-    <argument type="service" id="SwagMigrationExtendConverterExample\Profile\Shopware\Converter\Shopware55DecoratedProductConverter.inner"/>
-    <argument type="service" id="SwagMigrationAssistant\Migration\Mapping\MappingService"/>
-    <argument type="service" id="SwagMigrationAssistant\Migration\Logging\LoggingService"/>
-    <argument type="service" id="SwagMigrationAssistant\Migration\Media\MediaFileService"/>
-</service>
+In the end, you have to register your decorated converter in your `services.php`:
+
+```PHP
+$services->set(SwagMigrationExtendConverterExample\Profile\Shopware\Converter\Shopware55DecoratedProductConverter::class)
+    ->decorate(SwagMigrationAssistant\Profile\Shopware55\Converter\Shopware55ProductConverter::class)
+    ->args([
+        service('.inner'),
+        service(SwagMigrationAssistant\Migration\Mapping\MappingService::class),
+        service(SwagMigrationAssistant\Migration\Logging\LoggingService::class),
+        service(SwagMigrationAssistant\Migration\Media\MediaFileService::class),
+    ]);
 ```
 
 With this, you have decorated your first Shopware migration converter.
diff --git a/products/extensions/migration-assistant/guides/extending-the-migration-connector.md b/products/extensions/migration-assistant/guides/extending-the-migration-connector.md
index 82b058b40f..1aa283fbc3 100644
--- a/products/extensions/migration-assistant/guides/extending-the-migration-connector.md
+++ b/products/extensions/migration-assistant/guides/extending-the-migration-connector.md
@@ -19,7 +19,7 @@ With this setup, you have the bundle plugin in Shopware 5 and also the bundle pl
 
 To fetch your data via the Shopware 5 API, you have to create a bundle repository first:
 
-```php
+```PHP
 <?php
 
 namespace SwagMigrationBundleApiExample\Repository;
@@ -78,20 +78,18 @@ class BundleRepository extends AbstractRepository
 
 The repository has to inherit from the `AbstractRepository` of the Migration Connector. This provides helper functions like `addTableSelection`, which sets a prefix to all table columns and adds these to the query builder.
 
-You have to register the repository in your `service.xml` with the parent property like this:
+You have to register the repository in your `services.php` with the parent property like this:
 
-```html
-<service id="swag_migration_bundle_api_example.bundle_repository"
-         class="SwagMigrationBundleApiExample\Repository\BundleRepository"
-         parent="SwagMigrationConnector\Repository\AbstractRepository"
-         />
+```PHP
+$services->set('swag_migration_bundle_api_example.bundle_repository', SwagMigrationBundleApiExample\Repository\BundleRepository::class)
+    ->parent(SwagMigrationConnector\Repository\AbstractRepository::class);
 ```
 
 ## Creating bundle service
 
 In the next step, you create a new `BundleService`, which uses your new `BundleRepository` to fetch all bundles and products to map them to one result array:
 
-```php
+```PHP
 <?php
 /**
  * (c) shopware AG <info@shopware.com>
@@ -143,19 +141,20 @@ class BundleService extends AbstractApiService
 }
 ```
 
-You have to register the `BundleService` in your `service.xml`:
+You have to register the `BundleService` in your `services.php`:
 
-```html
-<service class="SwagMigrationBundleApiExample\Service\BundleService" id="swag_migration_bundle_api_example.bundle_service">
-    <argument type="service" id="swag_migration_bundle_api_example.bundle_repository"/>
-</service>
+```PHP
+$services->set('swag_migration_bundle_api_example.bundle_service', SwagMigrationBundleApiExample\Service\BundleService::class)
+    ->args([
+        service('swag_migration_bundle_api_example.bundle_repository'),
+    ]);
 ```
 
 ## Create a new API controller
 
 At last, you have to create a new API controller, which uses the `BundleService` to get your bundle data:
 
-```php
+```PHP
 <?php
 /**
  * (c) shopware AG <info@shopware.com>
@@ -186,7 +185,7 @@ class Shopware_Controllers_Api_SwagMigrationBundles extends Shopware_Controllers
 
 Now you have to create the `BundleReader` in the [SwagMigrationBundleExample](extending-a-shopware-migration-profile) plugin, which only contains the Shopware 5 API route:
 
-```php
+```PHP
 <?php declare(strict_types=1);
 
 namespace SwagMigrationBundleExample\Profile\Shopware\Gateway\Api\Reader;
@@ -215,11 +214,10 @@ class BundleReader extends ApiReader
 
 After this, you have to register the reader in the Symfony container:
 
-```html
-<service id="SwagMigrationBundleExample\Profile\Shopware\Gateway\Api\BundleReader"
-         parent="SwagMigrationAssistant\Profile\Shopware\Gateway\Api\Reader\ApiReader">
-    <tag name="shopware.migration.reader"/>
-</service>
+```PHP
+$services->set(SwagMigrationBundleExample\Profile\Shopware\Gateway\Api\BundleReader::class)
+    ->parent(SwagMigrationAssistant\Profile\Shopware\Gateway\Api\Reader\ApiReader::class)
+    ->tag('shopware.migration.reader');
 ```
 
 With that, you have implemented your first plugin migration via API.