How Imperia works


An Imperia document manages the content captured by an editor for publication on a web page. From them, Imperia generates the finished web pages based on templates and other layout specifications.


Documents are managed in rubrics. The headings thus form the structure tree of a web offer. Access rights, navigation and administrative parameters (e.g. for document layout, multilingual appearances, etc.) are controlled via these rubrics. For each web presence, the structure must first be defined via rubrics before web pages can be created.

Areas of an Imperia system:

  1. Document area on the development system
    Each document is assigned to a rubric when it is first created. While it is being edited, it is in a workflow. One of the most common steps in this workflow is the Edit step. The Imperia Desktop shows all documents that are currently in the workflow.
  2. Web page area on the development system
    Only in the approval step of a document in the document workflow are the associated web pages simultaneously generated on the development system. The development system can be reached via the address and is only visible within the university. Here, the appearance and linking of new web pages can be checked before they are transferred to the target system and thus made available to the public.
  3. Web page area on the target system
    When publishing, the generated web pages are finally transferred to the so-called target system - mostly the central web server of the WWU.


Here is an example of how the URLs differ between the development and target systems:
URL on the target system:
URL on the development system:

© Uni MS IT