×
Create a new article
Write your page title here:
We currently have 276 articles on Waste Of Space Wiki. Type your article name above or create one of the articles listed here!



    Waste Of Space Wiki

    Improving the wiki: Difference between revisions

    Content added Content deleted
    m (signed myself)
    m (improved descriptions, made examples better)
    Line 8: Line 8:




    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.
    Checklists are a non-linear set of unorganised 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 17: Line 17:


    [ ] Clean the desk ~Username
    [ ] Clean the desk ~Username

    [ x ] Water the plants


    ...
    ...
    Line 22: Line 24:




    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.
    Roadmaps are a sequentially organised, 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;

    Revision as of 23:25, 22 June 2023

    This article serves to catalogue currently ongoing improvements to the wiki. It is meant for situations in which articles are being refactored and a roadmap/checklist is required to organise editorial efforts, and for organisation of wiki-wide projects.

    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.

    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.


    Checklists are a non-linear set of unorganised 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;

    Organising my room

    [ x ] Sort pencils by colour

    [ ] Clean the desk ~Username

    [ x ] Water the plants

    ...


    Roadmaps are a sequentially organised, 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;

    Go shopping

    | Obtain foodstuffs (Due: 01/12/1984)

    |-> Purchase eggs (DONE)

    |--> Check if they are cracked or not (DONE)

    |-> Buy milk ~Username

    ...

    List

    Polishing the starter guides ~Axenori

    [ ] Enforce a uniform linking style across all starter guide articles; links to relevant wiki articles should be formatted as such only the first time they appear in a paragraph.

    [ ] Split large articles into many smaller ones for quicker load times and SEO.

    [ ] Enable search engine indexing for relevant pages.

    Cookies help us deliver our services. By using our services, you agree to our use of cookies.

    Recent changes

  • Axenori • 3 days ago
  • Voivsone • 4 days ago
  • Axenori • 4 days ago
  • Axenori • 5 days ago
  • Cookies help us deliver our services. By using our services, you agree to our use of cookies.