Improving the wiki

This article catalogues 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.

If you are not here to contribute an improvement list, please skip to the List heading by clicking here (or scrolling).

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 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. To create subtasks for a particular task, indent the row so there are 3 dashes (-) for each level of depth in the task tree at that point. 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;

Tidying my room

[ x ] Sort pencils by colour

[ ] Clean the desk ~Username

[ x ] Water the plants

---[ x ] Water the coleus

---[ x ] Water the cactus

...

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 twice the depth of the task tree at that point + one (2 dashes per task tree depth at that point + 1). 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

Wiki-wide

|-> Enforce a uniform linking style; linking a term to an article should be done each time that unique term appears for the first time in a specific (sub)heading.

|---> Enforce a uniform linking style across the starter guides as these have a lot of text and repeated links. ~Axenori

|---> Enforce a uniform linking style across all articles featured on the front page.

|---> Enforce a uniform linking style across all large articles (more text correlates with more links).

|---> Patrol smaller articles and fix their linking style if required.

Polishing the starter guides

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

[ x ] Split large articles into many smaller ones for quicker load times, SEO, and easier discoverability on the wiki.

[ x++ ] Enable search engine indexing for relevant pages. (Completed for all relevant pages, not just the starter guides)

[ ] Polish the text: Correct grammar and spelling where needed, clarify if unclear, shorten it if it is able to be written in a more concise way.

[ ] Add illustrations and or pictures wherever applicable to complement the textual explanation with a visual one. ~Axenori