Resource Manager

Resource Manager: centrally manage structured content

With the Resource Manager, you manage recurring, similarly structured content in a central location. Typical use cases include references, team members, locations, services, products, contacts or other directories. Instead of entering each piece of information directly on an individual web page, you first define the common structure and then capture any number of content items based on this schema.

A resource consists of two levels in the Keimeno backend:

  • Resource type: Defines fields, additional data tables, HTML templates, and the available widgets.
  • Resource content: A specific entry of that type, for example a particular branch office or an individual team member.

This separation ensures uniform input forms, consistent output and easy maintenance, even for larger data sets.

Open the Resource Manager

In the backend, open the Resource Manager. The start view shows the configured resource types. Use Show all to return to the full overview. The global search in the backend can find resource types by their name, provided your user account has access to the module.

Which areas and buttons are visible depends on your user role, assigned permissions and system configuration.

Create a new resource type

  1. In the resource overview, click the button with the plus sign.
  2. Enter a unique and understandable title, for example Team, Locations or References.
  3. Save the new resource type.
  4. Then open it for configuration.

When creating a type, Keimeno sets up the technical basic structure. This also includes the link for the detail output and the necessary assignments for user groups. You then define the business fields and the presentation.

Configuration of a resource type

The edit view is divided into the areas Variables, Datasets, HTML Templates and Widgets.

Variables: fields of the main entry

Under Variables, you define the fields that appear for each resource content directly in the Content tab. A field in particular has a visible label, a technically generated field name, a field type, a sort order, and a width for the input form.

The field name is generated automatically from the label when the field is created. Choose the label carefully for this reason. For existing fields, the technical name cannot be freely changed in the editor because output templates and stored content may reference it.

The current editor supports, depending on configuration, among others the following input types:

  • single-line and multi-line text as well as HTML or rich-text content,
  • drop-down lists, checkboxes and toggles,
  • numeric or range fields and date fields,
  • links, images and files,
  • source code and blog content,
  • links to entries of another resource type.

For images and files, the dedicated media functions are available. Link fields require an existing target resource type. If this has since been deleted, the backend will point out the missing link.

With the GUI option, you define how wide a field is displayed in the input form. The sort number determines the order of the fields.

Datasets: repeatable records

Datasets are additional, repeatable records within a resource content item. For example, a location can have multiple opening hours, a product can have several variants, or a contact can have different communication channels.

  1. Open the Datasets section.
  2. Select an existing data table or create a new table using the plus sign.
  3. Assign an understandable table name.
  4. Then create the required dataset variables.

Dataset fields also have a label, technical name, field type, order and display options. Without dataset variables, no records can be captured in the relevant table.

When later editing a resource content item, datasets can be added, edited, deleted and sorted via drag and drop. Some text values can be edited directly in the table view. A CSV import is also available for data tables. The uploaded CSV file must be semicolon-separated; before importing, you map the CSV columns to the existing dataset fields.

When multiple languages are enabled, dataset data can be copied from another language. Afterwards, review the imported data in the target language.

HTML Templates: frontend presentation

Under HTML Templates you define how resource content is output in the frontend. You can create multiple templates, mark one of them as the default and assign a detail page to each template.

The integrated template editor provides variable help, a Template Builder and template backups. The template can access the fields of the resource content, the associated datasets and the compiled resource widgets. For images, additional values for alternative text and dimensions are available. Linked resources can be processed in the output with their own data.

Important: Changes to an HTML template can affect all content items that use this template. Before making major adjustments, create a backup and first check the result in the preview.

Assign widgets to a resource type

In the Widgets section, you define which widgets already available in the system may be used within the content items of this resource type.

  1. Select an available widget.
  2. Click Assign.
  3. Repeat this for all required widgets.

The selection list only shows widgets that have not yet been assigned to the resource type. An assignment can be removed again. If a linked widget is no longer available in the system, Keimeno displays a corresponding notice.

Create and maintain resource content

Open a resource type and switch to its content. The overview shows, among other things, the label, ID, responsible person, publication status, visibility period, creation and modification date, frontend preview and available data tables.

Using the filter bar you can:

  • search by title or label,
  • filter by the assigned person,
  • choose the number of displayed entries,
  • sort ascending or descending,
  • order by manual order, label, creation date or last modification.

If the result list only spans a single page, entries can be manually sorted via drag and drop using the handle at the beginning of the row.

Create new content

  1. Click New content.
  2. Enter the required Backend label. It is used for internal identification and appears in the management overview.
  3. Fill in the fields previously defined under Variables.
  4. Save the content.

In addition to normal saving, outside of a modal view you also have Save and new and Save and close available. After the first save, the additional tabs for Datasets, Meta, Settings, Widgets and Permissions become fully usable.

Tabs of a resource content item

Content

Here you edit the backend label and all main fields of the entry. The specific input form is entirely based on the definition of the resource type. Depending on the configured AI functions, an AI menu may additionally be offered in the editor.

Widgets

This tab appears for saved content items. Here you can add any number of instances of the widgets that were previously assigned to the resource type. Activate the desired widgets and select Add selected.

Each instance can be edited in a full-screen dialog and removed again. If the corresponding database extension is active, widget instances can be sorted via drag and drop. The Update description function synchronizes the displayed widget descriptions with the current widget data.

Datasets

Here you maintain the repeatable records of the entry. If there are multiple data tables, first select the desired table. You can then create, edit, import, delete and sort records. The heading of each data table can be customized for the respective content item in the Settings tab.

Meta

The Meta tab contains language-dependent fields for meta title, meta keywords and meta description. Formulate a precise title and a clear description of the specific entry. Avoid using identical meta information for many different content items.

Settings

Under Settings you manage the technical and editorial settings:

  • Permalink: The unique URL segment of the entry; the output uses the .html extension.
  • Visible from / to: Optional period during which the content should be available in the frontend.
  • Creator: Assignment to a person or employee available in the system.
  • Template: Selection of the HTML template for the output.
  • Database headings: Individual labels for the embedded data tables.

Choose a short, unique permalink without unnecessary special characters. Before changing existing URLs, check whether they are already linked externally or indexed by search engines.

SEO

The SEO area provides an analysis via the SEO/AI function integrated into the system. Availability depends on the Keimeno configuration and the services that have been set up. An analysis does not replace editorial review of content, page title, description and frontend output.

Permissions

Users with administrative permissions can assign roles to groups. The selected role determines whether a group may read, edit or administer the content. The administrator group remains set as administrator.

Check permissions immediately after creating a resource type and before handing it over to additional editors. Grant only those permissions that are actually required for the respective task.

Publish, deactivate and preview

The content overview marks each entry as Published or Deactivated. The available action icons depend on your permissions. A deactivated content item can be reviewed via a protected preview link, provided a frontend link is available.

An entry only has a usable frontend link if the detail page and output template are correctly configured. The message No permalink indicates an incomplete frontend configuration.

Multilingual content and translation

Resource content items are stored per language. When editing, explicitly switch to the desired language and check the main fields, meta information, datasets and widgets.

Using Translate, content from a resource type can be transferred from a source language to another enabled language. The source and target languages must be different. The function uses the translation or AI service configured in the system and is therefore only available if that service is set up.

Always review automatically generated translations for accuracy. Proper names, links, units of measurement, structured values and HTML content require particular attention.

CSV import of resource content

Via Import you can upload a semicolon-separated CSV file. After upload, you map one CSV column to the backend label and the remaining columns to the existing resource fields. Columns that are not needed can be excluded from the import. An option for UTF-8 processing is available.

Recommended process:

  1. First test the import with a few rows.
  2. Check delimiter, character encoding and column headers.
  3. Carefully map each column to the correct field.
  4. Review the imported content, media, links and permalinks.
  5. Only then import the complete data set.

Copy resource type

In the overview, a resource type can be cloned. Its structure, including variables, data tables and other configurations, is used as the basis for a new type. Assign a new, unique title and then carefully review especially fields, templates, detail page, widgets and permissions.

Cloning a resource type is not the same as copying all content items maintained within it. Therefore, check the new type before using it editorially.

Link resource in the page tree

In the website manager, the Resource link type is available in the Link tab. This allows an entry in the page tree to point to resource content.

  1. Open the desired page in the website manager.
  2. Switch to the Link tab.
  3. Select Resource as the link type.
  4. Select the resource type.
  5. Then select either a specific resource content item or the option for all content items.
  6. Save the link.

Additionally, link attributes and CSS classes can be stored. Only use values that are intended for the frontend template in use.

Detail pages and frontend output

For the single view, Keimeno uses the Resource Detail Page content plugin. Exactly one resource type is assigned to a detail page. The selected HTML template renders the current entry, its datasets and, if applicable, its widgets.

If a resource does not have a functioning detail view, check:

  • whether the correct resource type is assigned to the detail page,
  • whether an HTML template has been selected as the default,
  • whether a suitable detail page has been assigned to the template,
  • whether the content item has a unique permalink,
  • whether the content item is published and within its visibility period,
  • whether the user or group has the necessary permissions.

Secure editorial workflow

  1. First plan which information is required as main fields and which as repeatable datasets.
  2. Create the resource type, its variables and, if necessary, data tables.
  3. Create and test the HTML template and the detail page.
  4. Assign only the widgets that are actually needed.
  5. Check roles and group permissions.
  6. Capture a complete test content item, including Meta, Settings, Datasets and Widgets.
  7. Use the preview to review desktop and mobile view.
  8. Publish the test content and only then create further entries or perform a larger import.

Typical errors and solutions

The entry has no frontend link

Check the permalink, the selected HTML template and the assigned detail page. Without a complete detail page configuration, Keimeno cannot generate a frontend link.

The content does not appear in the frontend

Check publication status, visible-from/to date, language, permissions and the assignment of the resource type to the detail page.

A dataset cannot be filled

The selected data table requires at least one dataset variable. First define the required columns in the structure of the resource type.

A widget is missing or cannot be added

The widget must exist in the system and be assigned to the resource type. A red error message with a widget ID indicates an outdated link.

A resource link is invalid

Check whether the linked resource type and the selected content item still exist. After deleting a target type, the corresponding link field must be reconfigured.

The CSV import produces incorrect content

Check the semicolon as the delimiter, the character encoding and the mapping of the CSV columns. Do not repeat an import without verification, as this can otherwise lead to duplicate content.

Notes on deletion

Deleting an individual content item can affect associated datasets, files, images, widget instances and frontend links. Deleting an entire resource type has significantly greater impact on templates, detail pages, link fields and all associated content items.

The function for deleting all resources including their content is intended exclusively for special administrative cases. Before any extensive deletion, carefully check the exact selection and ensure that a current data backup is available.

 

  1. Startseite