diff --git a/docs/hypernode-deploy/applications/config-for-magento-2.md b/docs/hypernode-deploy/applications/config-for-magento-2.md
index 52d7419c..495e1369 100644
--- a/docs/hypernode-deploy/applications/config-for-magento-2.md
+++ b/docs/hypernode-deploy/applications/config-for-magento-2.md
@@ -17,8 +17,6 @@ return $configuration;
 
 By using the Magento2 ApplicationTemplate, a bunch of default configuration gets set in Hypernode Deploy, and should work out-of-the-box for most magento 2 stores.
 
-These are the steps that will be executed by running your deployment:
-
 ## Advanced
 
 However, for advanced configurations you can override most steps and variables set my Hypernode Deploy:
diff --git a/docs/hypernode-deploy/applications/config-for-shopware-6.md b/docs/hypernode-deploy/applications/config-for-shopware-6.md
index 56eb206b..bc9c1ae5 100644
--- a/docs/hypernode-deploy/applications/config-for-shopware-6.md
+++ b/docs/hypernode-deploy/applications/config-for-shopware-6.md
@@ -1 +1,18 @@
 # Config for Shopware 6
+
+This is a sample configuration that suffices for most Shopware 6 installations:
+
+```php
+<?php
+
+namespace Hypernode\DeployConfiguration;
+
+$configuration = new ApplicationTemplate\Shopware6();
+
+$productionStage = $configuration->addStage('production', 'shopware6.komkommer.store');
+$productionStage->addServer('appname.hypernode.io');
+
+return $configuration;
+```
+
+By using the Shopware6 ApplicationTemplate, a bunch of default configuration gets set in Hypernode Deploy, and should work out-of-the-box for most shopware 6 stores.