Your own Converia website

CMS

The Content Management System (CMS) can be used to create your own event website in Converia. Even if an external website already exists, it is recommended to use the Converia CMS to provide important content such as terms and conditions, privacy policy and imprint for participants.

The following chapters explain the structure, basic functions and display options of the CMS so that the desired content can be displayed even without much prior knowledge.

The central header graphic is not stored in the CMS, but in the basic settings. You can find more detailed information on this in the Header, logo and visibility chapter.

Functional areas of the CMS

Articles - Articles refer to page content that is usually created using a text editor. For example, texts and images can be inserted, linked to each other and documents can be made available for download.
Page structure - Menu navigation, start pages and visibility are defined in the page structure. In addition, previously created article content is linked here.
Structured data - Structured data can be used to display similar information, such as a list of sponsors or speakers, in a clear form without having to resort to tables.
Media - Files such as images and documents that are to be available on the website can be uploaded and managed in the media browser.

Structure and principle of the CMS

As is common in other content management systems, the structure is separated from the content in Converia CMS. This means that content (articles) can only be accessed in the frontend once they have been linked in the page structure.

The different levels from the subportal to the article build on each other, as the following diagram shows:

Subportal level: The number of subportals corresponds to the number of active languages in a conference. A separate menu navigation can be created for each subportal.
Folder level: The folder structure determines the menu in the frontend. Folders - and therefore menu items - can be shown and hidden. A hierarchy of top-level and subfolders can also be created. Sub-menu items that are created as folders are also visible if the associated main menu item has not been selected. In Fig. 2, the “News” subfolder is not visible.
Page level: Each folder must contain at least one page in which content modules such as text articles are linked. Pages can have different properties, e.g. be folder or subportal start pages or also be displayed as menu items in the frontend. The pages "Imprint" and " Privacy policy" in Fig. 2 are displayed as submenu items as soon as someone selects the menu item Contact.
Page content level: So that the menu items do not remain empty in terms of content, an article that was previously created is linked as page content. In addition to simple text articles, other module types can also be linked for various actions and the access options can be configured for each module.

PreviousAdd and link imprint NextArticle

Last updated 21 days ago

Functional areas of the CMS

Articles - Articles refer to page content that is usually created using a text editor. For example, texts and images can be inserted, linked to each other and documents can be made available for download.

Page structure - Menu navigation, start pages and visibility are defined in the page structure. In addition, previously created article content is linked here.

Structured data - Structured data can be used to display similar information, such as a list of sponsors or speakers, in a clear form without having to resort to tables.

Media - Files such as images and documents that are to be available on the website can be uploaded and managed in the media browser.

Structure and principle of the CMS

The different levels from the subportal to the article build on each other, as the following diagram shows:

Subportal level: The number of subportals corresponds to the number of active languages in a conference. A separate menu navigation can be created for each subportal.

Folder level: The folder structure determines the menu in the frontend. Folders - and therefore menu items - can be shown and hidden. A hierarchy of top-level and subfolders can also be created. Sub-menu items that are created as folders are also visible if the associated main menu item has not been selected. In Fig. 2, the “News” subfolder is not visible.

Page level: Each folder must contain at least one page in which content modules such as text articles are linked. Pages can have different properties, e.g. be folder or subportal start pages or also be displayed as menu items in the frontend. The pages "Imprint" and " Privacy policy" in Fig. 2 are displayed as submenu items as soon as someone selects the menu item Contact.

Page content level: So that the menu items do not remain empty in terms of content, an article that was previously created is linked as page content. In addition to simple text articles, other module types can also be linked for various actions and the access options can be configured for each module.