The content is the information for the page. We have already mentioned that for each page on your site you choose what template to use. When you add content to a page, it is automatically placed in the placeholders of the template you are using.
A page can have one or several content areas, or content blocks The first must be {content}. To add more content blocks to your template, use {content block='block name'}. These blocks will then appear as textareas when you edit a page.
You can make a content block use only one line, instead of a full textarea, by using the parameter oneline=true. That is, the full tag being: {content block='block name' oneline=true}. Read about more parameters in the help for the Content tag in the CMSMS Admin Panel, under Extensions -> Tags.
Content Types
There are currently 4 main content types in version 1.3.1 "Havana". These content types determine the type of content for each menu item.
- Content
- Link
- Separator
- Section Header
The content type is simply a regular page. Normally this is the only one you will use. That is what this page you are reading is. Here you can put any content that you would put on a regular page. The layout of these types of pages are controlled by the templates. For each content page you create you must choose a template for it. If you login as admin and change the template of this page, you will see exactly how it works.
The separator type is just what it sounds like, a separator that appears on the menus. This type follows the hierarchy set in content management pages.
The link type is just what it sounds like, a link to another page, either internal or external. This Link type also shows up in the menu following the same hierarchy rules as the content type.
The section header type is used to break up menus into groupings. This is unrelated to the hierarchy, as the section headers have no associated pages with them. They are just a little bit of text to say what the next few links are in reference to.
There is also the News content type. But use the News module call in the template instead, it works better. :)