Content Configuration

This describes internal configuration of the selected content type. Setting different options will alter the fields viewed in the list

This information is associated with all content items of the selected type and is accessed by selecting a type under

Consider the different parts associated with Content. Generally, the List View consists of some number of items on the left part of the window, and a set of Selector links on the right. Example item list

Overall Configuration

The first few items for configuration affect the overall configuration of the class.

Singular and Plural Name
The name fields allow you to set or change the words or phrases used by the platform when referring to one item versus a set of items. Sometimes just adding the letter 's' to the end just doesn't work. Some examples:
TeamTeam Building
Blog PostBlog
We use the plural form in the navigation menu, and in the heading of the list and individual page. The singular form is used when you're editing a particular entry.
Resources: Add link?
If checked, a menu item for this class will be added under the Resources navigation menu. Most commonly, this is the best and easiest way to make information available to others. Removing the link won't delete any data: items will still be visible, but the URL for items will not be easily found by others. Items will still be visible / editable to the individuals who created the item (via "My Content"). If you want to hide everywhere, you need to Archive.

Forms cannot be listed in the Resources navigation menu. Instead, you should publish the URL for users to fill out the form. (Similar to<name>/new.)
View: Require login to view?
Though most item classes should be restricted from general view, you can make classes visible without login. Blogs or upcoming announcement which don't include sensitive information are possible examples for this feature. Note this overrides the global per-site setting. Setting this to False, will allow non-logged-in users to view items even though the site requires login otherwise. Initially, all content classes will required login to view.
View: Allow Comments?
Comment lines For some content classes, it may be useful to permit logged-in users to add comments to individual entries. Comments are viewable to all. Blogs are a great content class for comments. User can delete their own comments, and Administrators can delete any comment. If enabled, Comments appear at the below the content of each entry. (User must be logged in to post.)
View: Allow messaging Author?
Message button If enabled, this will display a small button, allowing the reader to directly send a message to the author of this item. (User must be logged in to post.)
View: This ia s Form / Application?
Forms have special behavior.
  • They'll always include a "Submit" button
  • They are editable based on settings, but they are viewable only by administrators and anyone listed as a review for the form. (There's a link to all submitted forms to the right of the grid.)
  • Forms can be filled in by people who are not logged in (i.e., not even current users): Set the View: Non-users can fill out this Form option. Users may also fill out the form (of course) and this form will be associated with them, so they can re-edit it. Non-users do not get that option.
  • Forms can be anonymous (View: This is an Anonymous Form). When anonymous, we do not associate the form with any user: If you're logged in, we don't record that you are editing the form, this means you need to fill out the form all at one time -- we don't save it for you to allow you to edit it later.
Note: It's okay to have a form which is Anonymous and only filled out by logged in users -- perhaps it's an anonymous user survey.

It's okay to have a form which is not Anonymous and can be filled out by non-users. Clearly, we'll not know who the non-logged in users are (so it's anonymous for them), but if the form is filled out by someone who is logged in, we'll store it with their account and they'll be able to edit and resubmit the form at a later time.

Forms which may be filled out by non-logged in users cannot have teams or fields which select from exisiting Peers (because a non-logged in user cannot gain access to list of Peers.) You should use a simple text field instead.

List View Configuration

List: Maximum viewable items
Maximum number of items shown in the list view. This number excludes sticky items. Note: 0 indicates no list, -1 indicates show all.
List: Use Author for Title?
Sometimes the Author is the title. For example, a content class intended to list people with available skills doesn't need anything more than the individual's name as the title. This feature allows you to simplify this: We'll ignore any other title and just show the name of the author.
List: Sorted?
If selected, the resulting list will be sorted alphabetically by the title (which may be the author's name, if the User Author for Title item is also selected). If not selected, we display items based on their published date, most recent items first.
List: Truncate item?
When viewing items on the listing page, show a truncated version of the item or show the full item. If truncated, we'll show the first few lines and then fade out the entry. To view the full text, the user need to click through to the single item view.
List: Use Teaser when truncated?
If we're truncating items on a listing page (the previous option), and a particular item has a teaser, display the full teaser instead of the truncated original text. This gives you more control over what is shown in the list view. If you use a teaser, keep it short! That allows the reader to scan the list quickly.
List: Show Author Photo, Published Date, Byline, Tags

Extra item fields

You can choose to display or hide any of these fields. Some configurations make more sense that others. For example, if you've set Use Author for Title, it make sense to not display the byline: you can still include Allow Messaging Author as that's not part of the byline.

If you keep tags, we'll include a Tag selector on the right side of the page.

List Selector Configuration

On the right side of the list window, we show a set of filter selectors, allowing the user to view a subset of the full list. From this page, you can show/hide some of the more generic selectors. Other selectors are configured through the Field Editor.

View: Show Archive Selector
Include time-based Archive List to be displayed with these items. This is a way to show only a few items on the list, but still permit access to older items.

If the feature Enable Publish Date (below) is selected, only published item will be displayed, and the Archive will reflect months where there was one or more items published. If the Enable Publish Date is not selected, then the date entered with the item will be used: it may be in the future (say, if you're listing up-coming events.)
View: Show Titles Selector
Include an alphabetized list of all item titles to be displayed with these items. This is a way to show only a few items on the list, but still permit access to other items. Similarly, because the items are displayed based on published date, this list provides a sort of index to all items.

If you've set Use Author for Title, then this titles list will be a list of authors(!)
View: Show Authors Selector
Include an alphabetized list of all authors. This may be useful as a simple way to find an author of a post.

Note: If you've set Use Authors as Title, we'll ignore this value and never display this selector. Instead, you should enable Show Titles Selector.


This set of features guide how items are created and published.

Edit: Anyone can create?
Can anyone create a new item, or are items created only by administrators? Administrators can always create a new item and then set the Author field to another user, if this field is False. When True, all users will be able to create new items from their My Content dashboard.
Edit: Author can edit
In addition to administrators, can the author of a post edit their own post? This allows you to disable Anyone Can Create, yet, create an item, assign it to another person and have them do the editing for that item.
Edit: Author can publish
In addition to administrators, can the author of a post publish their own post? Turning this off is one way to allow Authors to write and review posts, but still require an administrator to make the post visible.
Edit: Enable publish date?
If publish dates are enabled, then an item is not made visible to the community until the item's publish date has arrived. If this option is disabled, posts are immediately visible. Post-dating posts is convenient for Blogs, but for most other content classes, this feature should be disabled.
Edit: Allow attachments
If enabled, this allows administrators, and the item author to add attachments to the post. Attachments may be downloaded by any user. Other user cannot upload attachments
Edit: Has Team?
Does this (should this) item have a team associated with it? If enabled, the author becomes the Team Leader, and is able to add other (existing) users as members of the team. Administrator can create an item, assign the Author and add a team. (Note the order of actions: if you create an item, and add a team as the second step, you're the team leader. Be sure to set the Team Leader / Author before attempting to create a team.


As a final item, you can Archive all items of this type. This does not delete any data, but will make it inaccessible to everyone except administrators using the Admin Content page. Users will not be able to view / edit their own content of this type, nor will they be able to create new items of this type. This action can be undone.

See also:


Was this information helpful?
Suggestions for improvement?

Still need help?