Structuring the content tree #

This page is for website creators who create the folder structure of a site. In Exponential the content tree is more than storage: it decides the menus, the addresses (URL aliases), the breadcrumbs and, through subtree limitations, who may do what.

Contents #

1. The roots of the tree
2. What the tree decides
3. Laying out the top levels
4. Sort order
5. One object, several locations
6. Hiding
7. Several sites in one tree
8. Checklist

The roots of the tree #

settings/content.ini [NodeSettings] names the top nodes:

A site shows the content below its root node. A siteaccess can use another node as its root, which is how several sites share one tree (Several sites in one tree).

What the tree decides #

Laying out the top levels #

• Keep the top level short: it is usually the main menu.
• Name folders as visitors would; the names become addresses.
• Put content that has no place in the navigation (landing pages for campaigns, legal pages) in a folder of its own and link to it from where it is needed.
• Separate content by who edits it: a subtree per team makes roles simple.
• Keep media in the media library, not inside content folders, unless the media belongs to one page only.

Sort order #

Each container has a sort field and direction: by name, published or modified date, priority, class, and others. Set it on the folder (the sub-items list), and choose the class default for new containers (Content classes for websites).

One object, several locations #

An object can be placed in several folders (Locations tab). Each location is a node with its own address; one is the main location. Use it when the same item belongs in two sections of the menu. Use a relation instead when you only want to point to it (Relations and content reuse). Search engines see two addresses for one item; point them to the main one (SEO basics).

Hiding #

Hide takes a node and its subtree off the site for visitors; editors still see it, marked hidden. Hiding is undone with Reveal. Removing a node moves it to the trash (Trash: who and where). Before hiding or removing, the administration warns about content that points to it (Reverse relation check).

Several sites in one tree #

A common shape: one folder per site under the root, each siteaccess using its folder as the root:

# settings/siteaccess/<site_b>/content.ini.append.php
[NodeSettings]
RootNode=<node id of the site B folder>

Root (2)
├── Site A
└── Site B

See Setting up several sites in one installation for the whole setup.

Checklist #

• To do: The top level matches the main menu.
• To do: Every folder has the sort order its content needs.
• To do: Folder names make good addresses.
• To do: Media is in the media library.
• To do: Each editing team has its own subtree, or a section.
• To do: Content with several locations has the right main location.

Related pages #

• Site map and content inventory
• Sections and object states for site builders
• Editing content
• Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.