dbxapp Knowledge CMS with dbxKi

CMS with dbxKi

With dbxKi, new CMS pages can be prepared, existing content can be improved and language versions can be created in a structured manner. This tutorial shows the complete sequence from the task description to the verified publication in dbxContent.

Basic principle: dbxKi operates within the CMS sequence. They specify the objective, content and desired change; Before sharing, check the page, media, rights and presentation.

What You Can Do After This Tutorial

Creating new content

Describe destination folder, page title, target group, structure and media so that dbxKi can generate a complete CMS page.

Change existing pages

Only revise the desired fields and get existing links, modules, media and layout markers.

Check results in the CMS

Control content tree, page data, editor, media areas, SEO and active status.

Translation and reworking

Create language versions and formulate small corrections as a clearly limited follow-up order.

Preparation

  1. Sign up with a user who is allowed to edit content.
  2. Open the landing page or remember the destination folder in the Content Tree.
  3. Write down target group, communication target and desired page elements.
  4. Check whether suitable images are already available in the media browser.
  5. Decide whether the page should be created immediately actively or first as a draft.

1. Open dbxKi and select order

Open in the main menu dbxKi. Depending on the task, different entries are available for content: new content, change existing content, translate individual pages or synchronize a complete language structure. Always choose the smallest suitable order.

Rule of thumb: For a new page "New Content", for a technical or editorial correction "Change Content", for a language version use "Translate Page".

2. Formulate a good content order

A robust job answers six questions:

QuestionExample
Where?Under "Performances", as a new subpage
For whom?Decision makers in small businesses
Why?Explain performance clearly and trigger contact request
What?Introduction, three benefits, procedure, FAQ and call to action
How?Clear, factual, short paragraphs, German you-address
What are the limits?Keep existing links and modules; Not initially published
Erstelle im Ordner „Leistungen“ eine neue Seite „CMS-Schulung“.
Zielgruppe: Redakteure ohne technische Vorkenntnisse.
Ziel: Ablauf, Nutzen und Vorbereitung einer Schulung erklären.
Aufbau: kurze Einleitung, 4 Lernziele, Tagesablauf, Voraussetzungen,
FAQ und Button zur Kontaktanfrage.
Ton: freundlich, konkret, Sie-Ansprache. Seite zunächst inaktiv anlegen.
Vorhandene Medien verwenden; keine neuen Produktversprechen ergänzen.

3. Control goal and page settings

Before running, check especially destination folder, page title, permalink, content template and active status. The title is visible to readers; The permalink determines the address. The content template specifies which areas such as header, hero, gallery, body or footer are available.

  • Destination folder: Does the page technically fit into this area?
  • Permalink: Short, clear and without unnecessary special characters?
  • Template: Does it support the planned construction?
  • Active: Only activate when content and media are checked.

4. Find results in the Content Tree

After successful execution, open the CMS. In the left Content Tree you will find folders, pages and language status. Use the search if the tree is extensive. A click on the page loads the edit on the right.

First, check title, permalink, description, content template, and status. After that, read the actual content completely in the editor.

5. Check content in the editor

Go through the text not only linguistically, but also functionally:

  1. Voices Headline Hierarchy and Order?
  2. Are facts, prices, dates and promises technically correct?
  3. Do links lead to the right internal or external goals?
  4. Are module calls, buttons and CMS range markers received?
  5. Is the call for action clear for the target group?
Important: Fluent wording is not yet a editorial approval. Figures, legal statements, availabilities and performance promises must be verified by the responsible person.

6. Assign media and test presentation

In the right CMS area, Hero, Gallery and media “In text” are managed separately. For each image, check title, alternative text, image section and usage. The hero is the large header image; Gallery media form a series of images; Inline media belong directly to the text.

  • Only set Hero if the page template has a Hero area.
  • Check Gallery order and visible number.
  • Alternative texts describe the image content, not just the file name.
  • Check desktop and mobile before sharing the page.

7. Change an existing page specifically

For changes, always choose the existing page as a reference point and describe exactly what needs to remain the same. Small, limited orders are easier to check than a blanket invitation like “Improve page”.

Überarbeite auf der Seite „CMS-Schulung“ nur Einleitung und FAQ.
Behalte Überschriften, Links, Button, Medien und Modulaufrufe unverändert.
Kürze die Einleitung auf höchstens 70 Wörter.
Ergänze im FAQ eine Antwort zur benötigten Vorbereitung.
Keine Änderung an Titel, Permalink, Template oder Aktivstatus.

8. Creating a translation

  1. Select the homepage and target language.
  2. Specify technical terms, product names and desired title.
  3. Generate the translation and open the new language page in the Content Tree.
  4. Check links, media, numbers, proper names and calls to action.
  5. Only then set the active status of the language version.

Final check before publication

  • Correct folder, title and permalink
  • Appropriate content template and complete content
  • Technically tested statements, functioning links and modules
  • Hero, gallery and inline media correctly assigned
  • Alternative texts, description and SEO information maintained
  • Desktop and mobile view tested
  • Active status set only after the final test

Deepening Content TreeDeepening the mediaAll tutorials

Text walkthrough

The slideshow remains the visual tutorial. These steps provide a complete text fallback.

Prerequisite: Sign in with an account that has access to the area shown in the tutorial.
  1. What You Can Do After This Tutorial
  2. Creating new content
    Describe destination folder, page title, target group, structure and media so that dbxKi can generate a complete CMS page.
  3. Change existing pages
    Only revise the desired fields and get existing links, modules, media and layout markers.
  4. Check results in the CMS
    Control content tree, page data, editor, media areas, SEO and active status.
  5. Translation and reworking
    Create language versions and formulate small corrections as a clearly limited follow-up order.
  6. Preparation
  7. Open dbxKi and select order
    Open in the main menu dbxKi. Depending on the task, different entries are available for content: new content, change existing content, translate individual pages or synchronize a complete language structure. Always choose the smallest suitable order.
  8. Formulate a good content order
    A robust job answers six questions:
  9. Control goal and page settings
    Before running, check especially destination folder, page title, permalink, content template and active status. The title is visible to readers; The permalink determines the address. The content template specifies which areas such as header, hero, gallery, body or footer are available.
  10. Find results in the Content Tree
    After successful execution, open the CMS. In the left Content Tree you will find folders, pages and language status. Use the search if the tree is extensive. A click on the page loads the edit on the right.
  11. Check content in the editor
    Go through the text not only linguistically, but also functionally:
  12. Assign media and test presentation
    In the right CMS area, Hero, Gallery and media “In text” are managed separately. For each image, check title, alternative text, image section and usage. The hero is the large header image; Gallery media form a series of images; Inline media belong directly to the text.

Checkpoint: After the final step, reload the target page and confirm that the expected state remains active.

Common errors: If a control or record is missing, first check permissions, the active language, filters and whether the preceding step was saved.