Skip to content

Child Theme

The Guppy Theme Builder is a browser-based configurator that produces an install-ready Shopware 6 plugin as a ZIP file. No local setup, no PHP knowledge, no build pipeline required.

Why a child theme?

Custom adjustments never belong directly in DmfGuppyTheme. A child theme inherits Guppy's full configuration and overrides it with your own values, parent updates remain safe to apply.

The Theme Builder automates this pattern: fill in a form, the builder produces a plugin with the correct inheritance layout. Done.

What the builder generates

ComponentDescription
Plugin skeletonComposer package, PSR-4 autoload, plugin bootstrap class, depends on dmf/sw6-guppy-theme
theme.jsonwith the correct style/script/asset/configInheritance paths to @Storefront, @DmfGuppyTheme
~250 theme variablesbrand, typography, UI, layout, detail page, product cards…
80+ Bootstrap overridesbuttons, inputs, spacing, borders, shadows, container…
Assetslogo, favicon, plugin icon, theme preview, share image
Fonts@font-face generation from uploaded .woff/.woff2 files
Custom SCSS variablesas name+value pairs in custom.scss with !default
Snippetsde-DE and en-GB translation keys
Icon mappingsShopware icon name ↔ Phosphor icon
.guppy-builder.jsonsnapshot for re-import into the builder

Local vs. builder

Theme BuilderManual child theme
Setupnothing localPHP project, Composer, Node
Dev modelre-import snapshotgit workflow
Best forbrand themes, fast iterationcomplex changes, custom Twig overrides, custom JS
Outputinstall-ready plugin ZIPcustom/plugins/<Name> in your repo
More underGetting StartedManual Child Theme Development

Privacy

Nothing leaves your browser

All input stays in browser localStorage. ZIP generation runs client-side via JSZip. No inputs are sent to a server.

Suggested path

  1. Getting Started: UI walkthrough, first theme generation.
  2. Configuration: full field reference.
  3. Workflow: installation, iteration, snapshot re-import.