Content hierarchy

Knarly page content is derived by a hierarchy. Which helps to make certain parts of the page consistant throughout the whole or perhaps part of the site.

This includes the headers and the footers of a page and other features such as tabs and breadcrumbs. To illustrate this here is a display of the page layout.

HTML Page Layout

 ---------------------------------------------
 |#container                                 |
 | ----------------------------------------- |
 | |#header                                | |
 | ----------------------------------------- |
 | |#Tabs                                  | |
 | ----------------------------------------- |
 | |#Crumbs                                | |
 | ----------------------------------------- |
 | |#Main Content                          | |
 | | ------------------------------------- | |
 | | | #heading                          | | |
 | | ------------------------------------- | |
 | | |                    |       |      | | |
 | | |   Main Content     | Col 1 | Col2 | | |
 | | |                    |       |      | | |
 | | |                    |       |      | | |
 | | |                    |       |      | | |
 | | |                    |       |      | | |
 | | |                    |       |      | | |
 | | |--------------------|-------|------| | |
 | ----------------------------------------- |
 | ----------------------------------------- |
 | |#Footer                                | |
 | ----------------------------------------- |
 ---------------------------------------------

Layout content and Scope

Each of the above sections in the HTML layout can be defined in the kedit form. Under the label "Structure" it requires specification of the scope, section and the content definition.

Scope

If the scope is defined as Current then for the section within the current page display the defined content.

Likewise if the scope is for Children then the defined content will be displayed for just the children of the current page. For Category then only children which are of type category. If Datasets then only children of type dataset. If all then apply the definition to the current and all the children (regardless of their type).

For a site with many branches. The decision to display a particular defintion into a section of our html page layout shown has the following precedence.

1. Definitions that belong to the current page
2. Definitions that belong to a parent (closest relative first)
3. Else default definition defined by knarly

Its important that this is understood before playing around with the "Structure" section of the Kedit form.