Content types are a very central part of Infoglue. The concept is that you after an information analysis define the information types needed for the site as content types. A content type consists of a name and the attributes it contains. Each attribute can be of different data type and often maps to some sort of data structure.
As we stated before a content type is a definition of an information requirement on the site. Because of this all contents are based on a content type and the content type is also used as the interface description for the input interface for the editor. This means the content editing view is dynamically generated based on the content type definition which saves a lot of development work.
The interface looks like this (the list is most often unique to each customer):
The list view is not very interesting but the detail view looks like this:
As you see the Article content type in this example has a list of attributes. The attributes has a type which can be one of a few predefined. It also has an order and can be moved up or down in the list.
To add a new attribute you choose the type in the list as below and press “Insert Form Element”.
The new field will have gotten a few defaults to it and you should now change the field’s properties at once as well as change it’s ordering if needed.
On a content type definition you can choose to allow content editors to categorize contents based on that content type. To allow categorization you have to add one or more category to the content type definition. You do this by pressing the “Add Category”-link and then clicking on the properties on that property-icon. The view looks like this:
You set the category key (used in searches later by developers). The title is what the user sees when categorizing and you also add which base category should be used. The logic is that all categories below the selected base category will be available to the user.
Continued from the part about Categories I will make it possible to categorize on region.
There is also a way to predefine the asset keys that should be available when uploading files to contents of this content type. This helps the users choose the right key which is important in those cases where templates are dependent on what key the user gave the attached asset.
You can state that you wish an image uploaded with this asset key to be transformed. Read the administration manual for a description on how the transformation XML should look like.
To add a new asset Key just press the link and fills in the information. Existing keys can be edited by clicking on the existing key.
If you click on the property icon on an attribute you will also see this:
In this view you state the name of the attribute which is how you later reach those attributes from templates. You also define the type and some descriptions and css-classes. In this case this type also has properties controlling the width and height of the field as well as which editors should be available in the edit view. There is also a possibility to set what text should be default when it’s empty and the user enters the form.