WiscWeb CMS - Defining usage of content templates
WiscWeb CMS allows administrators to create Page Definitions and preassigned Content Classes to allow for easier content creation by end-users.
The CMS enables administrators to take a couple of steps to make end-users' creation of pages as easy as possible:
Preset a block's creation upon page creation - using what are called "Page Definitions" the Administrator can specify that some certain block(s) will automatically appear within a newly created Blank Web Page, doing away with the need to manually add in the content block.
Preassign Content Classes - the Administrator decides where certain Content Classes can be used. For example, an Administrator can specify that any of the columns on a page can include the Article Block, but no columns on a page can include the code that would generate a whole new webpage, since that would not make sense.
Preset a Block's Creation Upon Page Creation
For example, it is possiblle to create a Page Definition so that an end-user can create a Blank Web Page with an Article Block in it:
In SmartTree, browse to Administer Content Classes > Foundation > Blank Web Page > Page Definitions:
In the Action Menu, click Create Page Definition.
A dialog box appears that allows you to type in a name and description for the Page Definition.
Enter a name for the Page Definition and press Next.
Another page appears - on the left are the structural elements for the "Blank Web Page" Foundation Content Class, and on the right are the available Content Classes of your project.
On the right, expand the Content Blocks folder, and drag the appropriate Content Class (in this example, "Article Block") to the left's con_Center_Column and release.
By doing so, con_Center_Column is populated with the Content Class.
You will probably want to rename the default name given to the populated Content Class by right-clicking on it and editing the Headline:
The Tree View now displays the Page Definition that was created.
By repeating these steps to create all the appropriate Page Definitions, a user will be able to easily create new pages with the appropriate block already created.
Note: In order to make this Page Definition usable by End-Users, you will need to complete the following How To, to pre-assign the Page Definition as one of the Content Classes that is allowed for users to choose from.
Pre-Assigning Page Definitions to a List
Having created a Page Definition in the previous How To, now we want to make that Page Definition usable by End-Users. To do so, we need to tell the CMS that we want it to be one of the options when someone creates a new item off of the Subpages list in the black Page Info bar.
In SmartTree, browse to Administer Content Classes > Foundation > Blank Web Page > Structural Elements > lst_Navigation.
Note that "lst_Navigation" is the Subpages list; webpages utilizing the Blank Web Page template have their subpages connected to this list.
With lst_Navigation selected, click on "Preassign Content Classes" from the Action Menu.
A dialog box appears that allows you to check off which Content Classes (in this case, which Foundation page Content Classes) you want to allow to be created off of this list.
Check off the Page Definition that we just created: "Web Page with Article."
Nothing visually changes in the Tree View, but the pre-assignments have taken place. Now if a user tries to create a new subpage off of an existing page that uses the Blank Web Page template, they will be given the option to choose Web Page with Article.
Pre-Assigning Blocks to Foundation Page
Because not every Content Class should be allowed within a page, you can specify that only a subset of the Content Classes are usable for some given column(s) on a Foundation page. Here, we will specify that only blocks can be put into the middle column of a Foundation page.
In SmartTree, browse to one of the Foundation pages underneath:
Administer Content Classes > Foundation
With this node expanded, you see the contents of the Foundation Content Class: it contains content elements (a Headline), structural elements (Anchors, Lists, Containers, etc.), and so on. We are going to pre-assign what Content Classes can be used within the body area of a page with the con_Center_Column structural element.
Under the Foundation page, browse to
Structural Elements > con_Center_Column.
With con_Center_Column selected, click on "Preassign Content Classes" from the Action Menu.
A dialog box appears that allows you to check off which Content Classes you want to allow to be used for the body area.
Check off the appropriate Content Classes' boxes within the "Content Blocks" Content Class folder.
Nothing visually changes in the Tree View, but the pre-assignments have taken place. Now if a user tries to create a block within the con_Center_Column Container, they will only be given those options that you checked off in these steps.