Put there the Why answer, the justification, the benefits, the limitations (when to use or not to use).
[Optional sub-section] Put there the original reason that has motivated the creation of that metascript.
Put there a short description of D&Do activity as controlled by this metascript, the input data and the results
List of variants and a description of each one (one of which is always there, the Default). Here are 2 examples:
List of tagged drops and description of each one. An example below:
Description of untagged drops. Here is an example:
The untagged drops (identified as Statements) contain not yet validated text fragments that will be used as a name for a new file
Usage of the system clipboard. Here is an example
The clipboard is not used as input for any variant. However, the content of the clipboard is changed once the script activity has started; it contains a file name.
Script-generated error messages. Here is an example:
Example: An explicit Clear List command is required
Here is an example:
Under variant Create, the script actually creates a new file (overwriting a file with the same name) at the destination directory.
See also the Purpose and to the Description sections above
You do not need to explain how to start D&Do, nor on how to load this metascript
Start the user guide as if D&Do has already loaded the metascript and that it is at the default variant.
Assume that the Description section was read. Concentrate on the "How To accomplish specific tasks". Explain a step by step procedure, the possible problem that the user may encounter and how to solve them.
Organize this user-guide either by task (which may imply the usage of many variants) or by variant.
Start by listing the tasks
Please, add authors and owners for each version of the metascript