SoSLUG procedures and guides
This section introduces various operating procedures which are intended to create a consistent approach when carrying a process. Irrespective of whether the user is a novice or advanced user, to reduce the possibility of errors being made, the procedures should provide a series of steps for the user and be easy to follow.
As improvements, or changes are made to the site, these procedures may need to be updated accordingly; to communicate the procedural changes to intended users. They would also form the basis for any training, (or aids) that are considered necessary.
What is the difference between a procedure and a guide?
Generally procedures are intended to be mandatory, i.e. you are expected to follow them, whereas the application of guidelines are, by and large, optional. Guidelines are often used as a way to pass on someone's expertise, to a beginner or intermediate user, in a specified topic. It up to user whether they follow that advice or not. How to's are perhaps a good example of a guide. E.g. How to install Linux may offer one approach, and advice concerning pitfalls / potential hazards etc. on how to go about this task.
It may not always be clear whether a document is intended as guide, a procedure, or a mixture of both. For example consider,
- Guide to designing (HTML) templates ,
- Guide to designing company (HTML) templates.
The latter case, is almost certainly intended as a procedure; even though the title says guide, as it may contain some very specific rules about the size and position of a company logo within a template which must be followed. Because such a document cannot possibly legislate for all future templates, other parts of the document however may be written as a guide.
On the SoSLUG website, (and only if you are an account holder), then depending on the role assigned to you, there are some procedures which have been collected together under the section
About SoSLUG > procedures.; to distinguish them from other How's to's etc. on the site. They will describe procedures which should be followed when completing various (Drupal) templates, or when configuring a module. In the former case, most of the rules will be mandated by the Drupal software itself. In the latter case, any rules will depend on the particular way SoSLUG intends the site to operate; and can be traced back to the articles of association.
For example the (SoSLUG) rule "No material may be published anonymously". will influence how particular modules are to be sent up. Whereas, on the other hand, other sites may be happy to allow users to comment anonymously.
All authenticated users are free to comment on any aspect of a procedure that affects them, which may be unclear, obsolete or just plain wrong.