<plugin root>/src/Resourcesfolder. Open up the
<plugin root>/src/Resources/theme.jsonfile with your favorite code-editor. The configuration looks like this.
nameof your theme and the
descriptionsection is optional and as you notice it is also translatable.
stylesection determines the order of the CSS compilation. In the
<plugin root>/app/storefront/src/scss/base.scssfile you can apply your changes you want to make to the
@Storefrontstandard styles or add other styles you need. The
<plugin root>/app/storefront/src/scss/overrides.scssfile is used for a special case. Maybe you need to override some defined
functionsdefined by Shopware or Boostrap, you can implement your changes here. Checkout the Override bootstrap variables in a theme guide for further information.
assetoption you can configure your paths to your assets like images, fonts, etc. The standard location to put your assets to is the
<plugin root>/app/storefront/src/assetsfolder. Checkout the Add assets to theme guide for further information.
@Storefrontas asset path
configproperty which contains a list of tabs, blocks, sections and fields.
configentries will show up in the administration and can be customized by the end user (if
editableis set to
true, see table below).
configInheritanceoption lets you configure additional themes from which your theme will inherit its fields configuration. Every theme will always inherit the fields from the
Storefrontstandard theme. With this option you can add additional other themes. For example, you can have a basic theme for your corporate design and special themes for different sales channels with specific changes only needed for a single sales channel.
BasicThemeis a theme that adds all the configurations you need for your corporate design. This configurations will be inherited in your new theme which can add or change some configurations only needed in a special sales channel or for a special time. See Theme inheritance for a more detailed example.
configInheritanceare available inside the current theme, unless they are explicitly overwritten. This way custom themes can be extended without copying their configuration inside the theme.json.