View source for Help:Staff guidebook

{{shortcut|P:STAFFGUIDE}}
The following is a list of information and tips about how staff members can best use the tools at their disposal to help the wiki.

== Patrolling and cleaning up ==
Edit patrolling is a feature that wiki staff have access to. Essentially, it's a way of saying that you've checked the edit out, so other staff members don't need to. Most commonly this happens due to a staff member browsing the [[Special:RecentChanges|recent changes]] and seeing what's new by clicking the "diff" buttons.

[[Pikipedia:Claims]] explains the key notes for accepting (or not accepting) an edit that's making a claim. For edits that aren't claims, you should make changes to the article to correct any policy, guideline, or style mishaps. You could also do stuff like adding {{tem|clean}}.

If you're not sure about an edit, discuss it with other staff or '''leave it unpatrolled''', so it can be looked at by somebody that's more certain. It's preferable to leave an edit unpatrolled than patrolling it when it has a problem. If that happens, the edit will be left on the wiki for years, causing problems throughout.

=== Tricky cases ===
Some edits look harmless on the surface, but if you try your hardest, you can imagine some problems. This doesn't necessarily mean the edit is bad and needs to be undone, but it does mean that it should be improved. Don't mark it as patrolled until it is improved.

* A user changes the name of a section of an article to include the game's name, and they do so without italicizing the name.
*: What you should do seems clear: italicize the game name. But consider this: do other articles have links to this section of the page? If so, then the addition of the game name will have broken all of the links... Should you correct the links, or bring the section name to how it was before?
* A user removes a sentence that explained a specific characteristic about a character. That characteristic was [[debatable canon]], and the user did not agree it should be mentioned alongside canon information.
*: No one fan is the authority on what is canon and what isn't, so we should follow the rules the wiki has for this. In addition, by removing the information, it just means another user in the future will feel the need to mention it again. Ideally, you should adjust the page so that information is not lost, and is still compliant to our policies and guidelines.
* A user removes a {{tem|todo}} that called editors to check if something is true. There is no edit summary.
*: Is this user implying that they have checked that it's true, so the template is no longer necessary? Maybe, but they never explained in the edit summary. And where's the proof? In these cases, you should probably double-check yourself too, or ask the user to elaborate in their talk page.

== Undoing ==
To undo what a user did, you have a few possibilities:

# Pressing the rollback button in a diff's page.
#: The <code>[rollback 1 edit]</code> (or a higher number) button is exclusive to staff, and it instantly patrols and reverts the user's latest edits on that article, by creating a new edit that brings the article back to how it was before. This does not let you adjust the article, write an edit summary, or control which edits to undo, so ''it should only be used in cases where it's an obvious vandal or spam''.
# Pressing the undo button in a diff's page.
#: The <code>(undo)</code> button puts you in the editing form, with the page in the same state as it was before that user's edit (or [[#Tips|edit''s'']]). Here, you can make further adjustments if necessary, as well as to write an edit summary for your undo. ''You should always explain why you are undoing the edit''. Remember to also patrol the undone edit(s).
# Editing from an older revision.
#: When you're in a diff's page or a revision's page, you can hit <code>(edit)</code> or the standard <code>Edit</code> button to edit the article from that version of the page. A warning at the top will let you know you're working with an outdated version. This is useful when you want to undo multiple edits and also do some tweaks all together, and also works well when you can't undo directly because of edit conflicts, though you should be careful that you're not getting rid of some good edits that came later in the timeline. Again, ''you should always explain why you are undoing the edit'', and remember to patrol the edit(s).
# Editing the text by hand.
#: If the edit is too involved, it may not be possible to undo it with either of the previous two methods. In this case you will have to edit the article by hand and undo things manually by writing the old text again. As usual, ''you should always explain why you are undoing the edit'' and patrol the edit(s).

== Tips ==
* If a user's made many edits in a row, and you want to see all of them as one diff, or even undo all of them at once, you can go to the page's history, scroll to the edit before the first, and click the "cur" button. Alternatively, use the radio buttons and click "Compare selected revisions".
* If a page has no problems, it makes sense for all its edits to be patrolled. Instead of doing this manually one-by-one, you can use the "patrol entire page" widget, which can be enabled in your user settings. Note that this might fail when the recent changes are very busy, due to technical limitations.
* Coordinate with other staff members. Maybe you like to keep a lookout on articles of a certain type that another staff member doesn't like.
* Install a spellchecker for your browser. Not only will this help you catch the occasional mistake you might make while typing, but it's also good for when you're just reading a page's source and spot some red underline that escaped unnoticed all this time.

== See also ==
* [[Pikipedia:Staff]]

{{help}}
[[Category:Help]]