Composr Tutorial: Coordination between staff and staff/members
Written by Chris Graham (ocProducts)When you run a Composr site, you do not merely create a website for people to visit. As an interactive, dynamic, system, Composr can provide different features for different users, and in particular, different features for staff than are available to ordinary members or visitors. Some of these features are specifically written to be for staff, some of these are a result of the privileges system, and some are the combination between the ability to create new categories/forums and control access to these using permissions. The term 'staff' is used loosely in this tutorial, to mean anyone with the necessary permission: by default, it is staff who have the mentioned permissions, but this may be altered.
Staff can use these features to distinguish themselves from ordinary users, and to collaborate together towards the operation of the website. This tutorial will cover a number of these features and how you might use them; some of these referenced features will be presented according to the Conversr system but are also likely to be included in third-party forum solutions in some form.
Table of contents
- Composr Tutorial: Coordination between staff and staff/members
Staff and the staff module
In a few places, being 'staff' gives certain hard-coded permissions: these are rare, however as usually permissions are given purely on the basis of usergroup membership. The main usefulness of the staff concept is simply presentational - staff are listed on the site staff page along with their details.
Staff are listed/viewed from the staff module (site:staff page-link, About > Staff on the default menus).
You can configure staff from the staff administration page. This is available from:
Admin Zone > Security > Staff
The staff administration page allows you to choose staff (if the staff filter is on) as well as configure their listed details. You may also configure their details by editing the corresponding custom profile fields from your forums profile editing screen.
By default, Conversr is installed with a single staff member, 'admin'. It is recommended that this member be left as a general purpose 'site representative', not used solely by any single staff member. It is also useful as a fail-safe account, because as a super-administrator, 'admin' can access any part of your Composr-based site.
Coordinating with other staff
Conversr creates a default staff forum for you on installation.
Conflict detectionIf more than one user is editing the same thing at the same time, Composr will put out a notice informing you. You can then coordinate with the other user so that you don't overwrite each other's changes.
Staff checklistOn the Admin Zone front page is a checklist of tasks to be performed. This combines tasks that are auto-detected with a set of shared manually added tasks.
You can also share links and notes on the Admin Zone front page.
More can be read on the Admin Zone in the Admin Zone overview tutorial.
Staff notifications, and the messaging systemStaff have access to a wide variety of notifications, to be informed on what is happening on the site.
In particular, if the main_contact_us (staff messaging system) is being used for user contact messages, messages will be directed to a shared location in the Admin Zone (and notifications sent out), and staff will be able to take responsibility for handling the contents of the message.
Notes within contentYou may wish to use the Comcode staff_note tag to embed comments within resource Comcode. For example, adding a comment to a news post.
Additionally, most content has an explicit 'staff notes' field for you to share notes within.
Validation and workflowsYou may wish to intentionally not validate content, even when a staff member adds it. This provides an opportunity for another member of staff (perhaps monitoring the needs-validation notification type) to check the content is ready for publishing.
Larger enterprises may require a more sophisticated workflow system. Composr has a non-bundled workflows addon, which provides a fully-managed process of multiple configurable approval steps for content (to different staff usergroups), before it goes live. The workflow system can be implemented for different content types, and is currently implemented for galleries out-of-the-box. Enterprise customers will want the system tuning for individual needs. If you require an advanced enterprise workflow system, you should enquire with ocProducts (or other third-party developers) with your specific needs, and whatever system you require can be set up for you.
ReviewsYou can set the "Comcode page review frequency" option so that Comcode pages are automatically flagged for regular review, to make sure they stay updated.
Notifications will be sent out automatically, or you can browse content needing reviewing from:
Admin Zone > Audit > Periodic content reviews
Staging sitesFor large sites, particularly tightly-run operations, you will want to test stuff on a staging site before making it live. Because of the constant flow of community content into the live database, it is not usually viable to just replace the whole live site with the staging site. You'll therefore need a more sophisticated process.
Novice users may simply copy & paste stuff from a test/staging site, to a live site. This works reasonably for most cases of new content, but not when more wide-spread changes are required, such as changes in menu layout or whole new categories.
Advanced users who are mainly aiming to stage content changes can use the Composr repository WebDAV feature to mass-copy data between sites.
Programmers managing site deployment also have a number of options, as Composr includes a number of APIs for import/export of content types (for example, menus). These are handy when used in coordination with the popular git tool (i.e. hosting site code in git, and writing deployment scripts to deploy things such as menu changes).
There's no magic-bullet when it comes to staging site changes in any software because of all the different change factors that could be involved (e.g. interconnected structural changes between two diverged versions of a website). However a skilled team has many options available to them, so can always come up with a workable deployment plan for both small and major site updates.
Version controlThere are a few angles to version control on a Composr site:
- Composr automatically does version control for Comcode pages and theme CSS/templates (i.e. the main parts of Composr websites)
- You should always have a good backup automated backup plan in place
- You can make use of the popular git tool (useful for enterprise users)
On point '3':
git is a standard tool to use when making code changes, but not for database changes. However it is possible to use WebDAV in coordination with git to manually do formal "commits" when changes are made to a website. If you are an enterprise interested in this functionality, you'll likely want to take on a developer (such as ocProducts) as a consultant to test/tune this functionality to your particular content needs, or set up an automated system if appropriate.
Once a post is reported, the report is actually created as a topic in the default 'Reported posts' forum. This method is, at the time of writing, unique to Composr, and allows staff to collaborate together to decide how to deal with the problem, as well as allowing clarity so that all staff know how the issue was reported and dealt with.
We have found it often to be the case that staff will report posts themselves, so that they can easily bring them (and possibly their related action) to the attention of other staff.
Warning membersConversr provides a facility for warning members. This is just one example of a punitive measure that may be taken out against a member. For full details, see the 'Tools for punishment' section of the Policing a community site tutorial.
WhisperingWhen members use the Conversr whisper feature to make inline-personal-posts, they are visible to moderators (which by default, equates to the same as staff, dependant on specific forum permissions). This has two consequences:
- moderators can tell when members abuse the feature
- moderators can use the feature to write in-topic messages to each other (and hence, all other moderators too, due to the ability for all the moderators to see them all). It may be necessary to reign back your staff if they use this feature too much and make sarcastic remarks: the unforeseen may become reality, with the target of the sarcasm becoming staff at a later date, and seeing such remarks.
- Admin Zone overview
- Policing a community site
- People in their roles
- Using IP addresses to trace users
- Correspondence between users
- Legal and social responsibilities
- Advice for choosing and managing staff
- Access control and privileges
- Advanced techniques for multi-site-networks
- The Composr Enterprise Repository
Please rate this tutorial:
Have a suggestion? Report an issue on the tracker.