Form tab

The way the page looks in the Page Store is defined on the “Form” tab.

Input components are defined in the <CMS_MODULE> tags and allow editors to subsequently add the actual editorial content to the page.

Line numbering can be shown or hidden using the icon in the top right-hand corner of the workspace for templates.

Edit default values: This icon is used to open the dialog for editing default values.

Search in templates

The following icons are used to run searches in templates:

Find (Ctrl+F): Opens a window in which the user can search for text.

Replace (Ctrl+R): Opens a window in which the user can search for and replace text.

Next occurrence (F3): Jumps to the next search result.

Previous occurrence (Shift+F3): Jumps to the last search result.

Undo (Ctrl+Z): Undoes the last change.

Redo (Ctrl+Y): Restores changes that have been undone.

Form

The input components defined here correspond to the GUI available to the editor on every page in the Page Store. The form is like a type of framework that can be filled with individual content for any individual page in the Page Store.

Since a page template is only used to hold the static content of a page, only those inputs are defined that:

• are needed only once on each page, such as a page title.
• are always to look the same way on all pages (such as navigation elements and logos)

Components for entering text or images, on the other hand, are found in the section templates.

DTD validation is carried out when saving GUI.XML. Incorrect formatting would be disastrous here; GUI.XML cannot be saved in that case. Other errors are just displayed.

If a preview for GUI.XML is requested in the locked state then the changes are saved automatically beforehand. (A new version is not created – that only occurs when unlocking!)

Code completion makes it easy to insert all available input components along with the corresponding parameters.