On this page
Create, modify and set designs as standard
The Design Studio manages independent design packages. Preview, personalization and AI processing remain separate work steps so that a production design is not unintentionally overwritten.
Open Design Studio
The overview shows each recognized design with technical name, layout and status. The markings Front-end standard and Admin standard Show which packages are currently used automatically.
| Action | Effects |
|---|---|
| Personalisation | Opens the Wizard based on the chosen design and creates a new, separate design. |
| AI | Opens a dbxKi job to create or specifically change a design. |
| Preview | Shows the design temporarily in a new tab. This does not change a standard. |
| ZIP backup | Download the full design package as a backup. |
Creating a new design
- In the Design Studio Design wizard Select.
- Determine an initial design and assign a free technical name.
- Set distribution, menu shape, content width, footer, branding, colors and typography.
- Optional Set as frontend standard after creation Activate.
- Create and then check the preview on desktop and mobile.
dbx/design and does not overwrite a design of the same name.Change existing design
For a safe variant, choose Personalisation. A new design is created from the existing package. If the same design is to be further developed specifically, use the action AI and choose on behalf of Change existing design.
For dbxKi: Create briefing, have order ZIP edited by the AI, import response ZIP, check file list and only then explicitly apply. In the event of a change, a fuse is applied before the replacement.
Define frontend and admin standards
dbxapp distinguishes two requirements:
- Design (user) applies to public pages and the normal frontend area.
- Design (Admin) This applies to administrative modules.
A new wizard design can become the front-end standard right when you create it. Existing requirements are set under System configuration · dbx in the fields: Design (user) and Design (Admin) selected and with Store Configuration taken over.
dbx_design and applying a dbxKi result does not automatically change the default. If an individual design is not offered in the system configuration, set it as a frontend standard when you create it or have it technically released before a manual configuration change.Recommended order
- Download ZIP backup of the initial design.
- Implement change as a new design or via the tested dbxKi sequence.
- Preview, navigation, forms, openWin, mobile view and check rights.
- Only then change the appropriate standard.
- Keep the previous design until successful acceptance.