Add content pages to content areas

You can start your content area definition with the definition of a content repository, adding all content items including the content items that shall be directly visible in the default configuration of the content area. You can then use the functionality for designing the layout of the content area in the web-based content area designer to define all content pages directly in the web-based content area designer.

You must at least add one content page to the content area.

  1. Right-click the content area node in the explorer and select Create New Content Page.
  2. Click the new content page in the explorer and define the following:
    • Caption: Enter the text displayed in the tab for the content page.
    • Description: Enter a description that will be displayed as a tooltip on the Alfabet user interface in the selector to hide and show content pages in a content area.
    • Name: Change the name to a meaningful name that helps you to identify the content page in the explorer.
    • Allow Moving Content Page Items: Set this attribute to False if users should not be able to re-size and move the content items on the content page.
    • Sort Content Page Buttons: You can use this attribute to sort custom button after you have added them to the content page.
    • Sort Content Page Items: You can use this attribute to sort content items on the page after having added content items.
    • Default Visibility:Set the attribute to Hidden if the content item shall not be visible directly in the content page but only available via the content repository.

      For customers migrating from Alfabet 11.8 to Alfabet 11.9 the attribute will be set to Hidden for content pages which were in Alfabet 11.8 available in the configuration in Alfabet Expand but hidden in the default configuration.

    • Visibility Conditions: If you want the content page to be only visible under specific circumstances, you can define a condition element testing whether the specific circumstances apply. You can then select the condition element in this attribute. The content page will be visible if the condition applies. For example, a condition specifies that the content page shall only be visible for users in user group B. The condition checks the user group configuration for the current user at runtime and hides the content page if the user is not a member of user group B.