-
Notifications
You must be signed in to change notification settings - Fork 51
Admin menu guide
Back to Glossary
Here you can tell Bricolage to send you messages, or Alerts, when certain actions are carried out. For example, if you have submitted a new Story to be published next Tuesday, you can have Bricolage send you an Alert as soon as it goes up to let you know that the action has been executed.
The permissions of a Group determine the privileges of its members. From this section you can create new Groups and edit the permissions of existing ones. Group types include users, elements, sites, categories, and more.
Here you can adjust settings and change the way certain information is displayed. Search for the Preference you want to edit, or do a blank search to view all Preferences. To change a preference, click Edit to get to the Preference Profile page, edit the preference, and click Save. You can also denote whether users can over ride them.
Add and manage sites. Sites are a fundamental way of separating content in Bricolage. For example, if you set “Filter by Site Context” to “On” in the Preferences screen, you will only see search results from the site you are currently on. The site selection dropdown is in the top right corner.
This is where you create user accounts and establish access levels. A user’s access is determined by his or her membership in user groups. For example, if you want user Mary Jones to be allowed to edit stories, you’ll go to her user profile and enter her into a user group that has story editing permissions. Study Bric::Security for details on permissions management.
With Bulk Publish, a permitted administrator can publish all stories or media in selected categories.
A Category is the place on your site where content items are published. On first use, the only Category in Bricolage is the Root Category, but you can create and edit new Categories in this area. Publishing content items in multiple Categories can help to organize your site’s components.
Contributor Types are used to classify Contributors by role, such as “Writer” and “Photographer.” Once a Contributor Type has been created, a user can select it in the Contributor Profile page.
The people who produce content items, Contributors are important to note for the purposes of both attribution and organization. By adding Contributors in this area and later attaching them to content items, not only can you keep tabs on who did what, but you can also tie together stories created by the same writer or allow visitors to search illustrations by an artist.
This is where you create and edit Element Types. Element Types are instances of Element Type Sets, and are the building blocks of story and media documents. You should first read Bric::ElementAdmin in order to understand how to plan your element hierarchy.
Add, edit, or delete Keywords.
Add and edit Media Types, also known as MIME types.
Output Channels dictate the file extension and URI convention for your files. When you create templates, they will be associated with an output channel. Output channels in turn are associated with destinations for your files to be published to. The default Output Channel is the World Wide Web.
A Source is the party responsible for providing a certain content item. Partner sites, your own site, freelancer, news services, or different offices or departments are just a few examples of potential Sources. On first use, you will find only one Source in the system. This one, temporarily entitled “Internal Source,” will be used to attribute content items to your site. You are encouraged to rename this Source with your company’s name and to add any Sources from which you will receive content. Once you have created a Source, you can give it credit by selecting it from a content item’s Profile page.
Here is where you create and edit Workflows, the management areas for content items. The default Workflows are Media, Story and Template, but you can add new Workflows or change the existing ones to fit your site’s needs.
Workflows organize the Content creation and editing process among a series of Desks. Every Workflow has one start Desk where all Content enters the Workflow. A Workflow also has one or more Publish Desks, from where Content can be sent to the Web Server. Content can be moved back and forth between Desks, the Shelf, and the Web Server. Workflows have two sections – Actions and Desks. Workflows are the drop down boxes on the left side of the screen.
Here is where you create and edit Destinations, which are the servers you want your content distributed to when it is published or previewed. Note that publishing and moving (or in general, Actions) are done in separate phases. Publishing runs the content of elements through templates (this is called “burning”), storing the resulting files (usually HTML) to a local staging directory. Then later the “distribution monitor”, bric_dist_mon, causes the burned files to be moved from the staging directory to destination servers.
This is where you look at pending Jobs. Jobs, such as publish, are put into a queue and wait for bric_dist_mon to trigger their execution, at which point they disappear from the job queue.