On this page
Use dbxKi in a controlled manner
dbxKi fully prepares design, content and module orders. An AI delivers a result, but dbxapp checks, shows and adopts changes only after an explicit release.
The three areas
| Area | Typical administrator tasks |
|---|---|
| Design | Develop a new design or change an existing design. |
| Content | Create pages, revise existing pages and prepare translations. |
| Modules | Edit existing modules with a defined scope and complete module context. |
The safe process
- Briefing: Define the objective, scope and behaviour to be maintained.
- Order ZIP: dbxKi exports rules, contract and required context.
- AI processing: The ZIP is transferred unchanged to the selected AI.
- Reply ZIP: Import the finished package back into the appropriate dbxKi area.
- Test: Control new, changed and unchanged files or CMS steps.
- Release: Explicitly apply or completely discard the result.
Create or modify
Select the task clearly in the respective briefing. For designs, Developing a new design and Change existing design separately available. A new design requires a free technical name; an existing target is not overwritten. A change, on the other hand, must point to an already existing design.
Describe the desired result in everyday language: Target group, layout, navigation, branding, mobile behaviour and accessibility. Leave the option to obtain system behavior, modules, Ajax, openWin and rights enabled, unless an explicitly verified system intervention is intended.
Using an AI design as a standard
Applying a dbxKi response activates the tested design files, but does not automatically set the package as a frontend or admin standard. Then open it up. Design StudioCheck the preview and follow the instructions Managing designs. Only after acceptance is the desired standard in the system configuration changed.
Responsibility of the Administrator
- Only the design to be edited, the specific content page or the specific module in the order.
- Response ZIPs do not change manually and import only in the appropriate area.
- Fully read preview and change overview; Do not ignore warnings.
- After design changes, test navigation, rights, forms, Ajax, openWin and mobile view.
- Producively used designs and modules before release.