Content deleted Content added
mNo edit summary |
|||
Line 2: | Line 2: | ||
==Organisational standards== |
==Organisational standards== |
||
'''To keep things ordered, you must pick one of the standards listed below to style your improvement set in before you add it to the list.''' |
'''To keep things ordered, you must pick one of the standards listed below to style your improvement set in before you add it to the list.''' |
||
''<small>If you believe your specific set of improvements does not fit within one of these frameworks, please suggest it as a standard in the discussion for this article.</small>'' |
''<small>If you believe your specific set of improvements does not fit within one of these frameworks, please suggest it as a standard in the discussion for this article.</small>'' |
||
Checklists are a non-linear, arbitrarily organised set of tasks. Checklists should be created by placing [ ] in each row except the one occupied by the checklist's name, once a task is completed an x should be placed in the middle. A progress indicator at the top or bottom is optional. |
Checklists are a non-linear, arbitrarily organised set of tasks. Checklists should be created by placing [ ] in each row except the one occupied by the checklist's name, once a task is completed an x should be placed in the middle. A progress indicator at the top or bottom is optional. To volunteer yourself for a task, sign with your username right of it as you see fit. |
||
If you find this unclear or require a visual illustration, an example of how a checklist should be styled is given below; |
If you find this unclear or require a visual illustration, an example of how a checklist should be styled is given below; |
||
Line 15: | Line 16: | ||
[ x ] Sort pencils by colour |
[ x ] Sort pencils by colour |
||
[ ] Clean the desk |
[ ] Clean the desk ~Username |
||
... |
... |
||
Roadmaps are a linear, optionally time constrained set of tasks. As with checklists, a progress indicator is optional. Roadmaps should be created by placing a vertical line in each row. To mark the name of an improvement set, separate its name from the vertical line by one space. To create a task, add a dash (-) followed by a rightward-facing arrow (>) to form an arrow symbol (->); if a task is itself a sub-task of another task, you should style the arrow such that the number of dashes is equal to the depth of the task-tree at that point. |
Roadmaps are a linear, optionally time constrained set of tasks. As with checklists, a progress indicator is optional. Roadmaps should be created by placing a vertical line in each row. To mark the name of an improvement set, separate its name from the vertical line by one space. To create a task, add a dash (-) followed by a rightward-facing arrow (>) to form an arrow symbol (->); if a task is itself a sub-task of another task, you should style the arrow such that the number of dashes is equal to the depth of the task-tree at that point. To volunteer yourself for a task, sign with your username right of it as you see fit. If a task is complete, indicate this by writing this left of it; alternatively if it was time constrained, replace the due date. |
||
If you find this unclear or require a visual illustration, an example of how a roadmap should be styled is given below; |
If you find this unclear or require a visual illustration, an example of how a roadmap should be styled is given below; |
||
Line 28: | Line 30: | ||
| '''Obtain foodstuffs (Due: 01/12/1984)''' |
| '''Obtain foodstuffs (Due: 01/12/1984)''' |
||
|-> Purchase eggs |
|-> Purchase eggs '''(DONE)''' |
||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
... |
... |
||