Glossary
Here you will find a glossary with short explanations of the most important terms in imperia and this documentation.
To search for a specific term in the glossary, we recommend using the search field at the top right.
Add-on#
With add-ons imperia can be extended by certain functionalities. A list of available add-ons can be found in the title bar of imperia CMS at . An overview can be found on our Marketplace website.
Archive#
Used to save all changes made by a user to a document. In this way, any editing status of a document can be restored.
Asset#
Any digital content in content management, in particular media files such as graphics, videos, music files and texts.
Asset Management#
In Asset Management, unstructured asset data is enriched with structured data. Assets are uploaded and stored in directories. In addition, Asset Management can track the documents in which assets are used.
Category#
Thematic rubrics in which new documents are created on the development system. Categories are used to give a project a content structure.
Content#
General term for all the contents that are created and maintained in imperia CMS.
DAM#
Desktop#
Central operating element of imperia. The desktop lists the pending tasks and offers the functions required for them.
Digital Asset Management#
The storage and management of digital content such as media files (images, videos, music) and text components.
Dashboard#
The home page of imperia CMS, which can be configured according to the needs of the user by using functional widgets.
Document#
In imperia CMS, documents function as a collection of content in which each individual piece of information (for example, a text or an image) belongs as a value to a specific key and is stored accordingly. Thus, this content can be published in many possible ways: as an HTML page, as an XML document, in a database, on several target systems and in different formats.
Develop-system#
In a "Staging" architecture, the content is created on the development system and then published on various target systems. This process is usually done by the editors.
Favorite#
Frequently used functions can be stored as bookmarks in imperia CMS.
Flex module#
HTML components that a user can use when creating content. Flex modules can be combined any number of times and in any order.
Form#
HTML form that can be created in imperia CMS with the desired form elements using Drag & Drop.
FTS#
Full Text Search. In imperia context, the search engine that supports full text search and other user-defined search queries.
Group#
The group gives a user access rights to categories, documents and functions. In order to have a certain scope of action in the system, a user must adopt the group required for this.
Live server#
Synonym to target system.
Live system#
Synonym to target system.
Meta data#
Special type of template used to collect information about a document (for example, the template on which the document is based).
One-Click-Edit#
Possibility to edit, delete or republish an imperia document directly in the browser.
Preset#
A recurring task when creating web pages is building a layout consisting of modular elements. Since the structure of web pages of the same type is always the same, you don't want to do this over and over again. If, for example, a news article always consists of a header image, a headline, a teaser module and several paragraph modules, you can add these modules all at once using a document preset. Presets can be imagined as an imperia document prefilled with modules and content. Users can select a preset in a preceding workflow step and then start entering content directly.
SEO#
Search engine optimization. SEO comprises measures that serve to optimize websites for search engines such as Google or Startpage. In imperia CMS, pages are validated using a checklist and suggestions for improvement are offered.
Staging#
Allows the creation of content at different steps in content management.
In imperia content is usually ...
- edited
- approved and
- reviewed on the staging server
... before it is published to one or more live servers.
imperia can also operate without "staging". In that case only the staging system exists without target system.
Staging server#
In a "Staging" environment, content is created and edited on the staging server. After the content has been reviewed and approved, it is published to one or more target systems.
System variable#
Global configuration variable in imperia. System variables are defined in the system.conf file in the imperia site directory. See also description in the Admin manual.
Tagging#
With the help of tags assigned to documents, pages can be categorized thematically. Subsequently, thematic overview pages can be generated in a website, from which website visitors can jump to related pages.
Target System#
In a "Staging" environment, the server intended for the target users and thus the counterpart to the staging server. See also descrition in the Admin manual. Synonym: Live system, Live server.
Template#
Input masks for the content created by programmers . The template defines the layout of the website, which is maintained independently of the content.
Unix time stamp#
Number of seconds since January 1st, 1970 GMT, also known as seconds since the epoch. Such timestamps have several advantages over broken-down date and time specifications, and are therefore in widespread use in programming languages.
-
Time calculations between two time stamps are easier to handle than with data such as "February 1st" and "April 1st" (due to the different number of days of the month, leap days and seconds, and summer/winter time).
-
Time zones can be ignored.
-
Timestamps increase steadily, whereas broken-down date and time specifications have gaps and ambiguities. For example the wall-clock time 2:30 typically exists twice on the day, if summertime is set.
Widget#
Functional component of the dashboard.
Workflow#
Sequence of editing steps that a document must pass through before it can leave the development system and be transferred to a target system.