19,585
edits
OniGalore:Dos and don'ts: Difference between revisions
m
updated page names
m (added advice on using test pages; updated editing help page name) |
m (updated page names) |
||
| Line 3: | Line 3: | ||
==Rules to follow when editing OniGalore== | ==Rules to follow when editing OniGalore== | ||
# If you are new to editing wikis, you should turn to the infobox on the right and read the "About" and "Editing | # If you are new to editing wikis, you should turn to the infobox on the right and read the "About Us" and "Editing Help" pages, and take a look at "Copyrights" if you're legally-minded. | ||
# Use the "Show preview" and "Show changes" buttons to carefully check over your edit so that you don't have to make a lot of follow-up edits. While even experienced and careful users have to make corrective edits sometimes, newcomers to wikis are notorious for making numerous edits to a page in order to fix their mistakes. This clutters the history of the page and makes it harder to follow the changes. You can also use one of [[:Category:Test pages|our test pages]] as a sandbox to try out something that you'll need to save for a while, or an interaction between two pages. | # Use the "Show preview" and "Show changes" buttons to carefully check over your edit so that you don't have to make a lot of follow-up edits. While even experienced and careful users have to make corrective edits sometimes, newcomers to wikis are notorious for making numerous edits to a page in order to fix their mistakes. This clutters the history of the page and makes it harder to follow the changes. You can also use one of [[:Category:Test pages|our test pages]] as a sandbox to try out something that you'll need to save for a while, or an interaction between two pages. | ||
# Always explain what you are changing in the Summary field when making an edit (this is not necessary on a talk page). Exceptions can be made when you are adjusting pages in your personal userspace or making rapid iterations while testing changes to a code page, though "cap" summaries (summary text for the first and last edits of your rapid editing session) which explain what you were starting to do, and ended up doing, would be nice. | # Always explain what you are changing in the Summary field when making an edit (this is not necessary on a talk page). Exceptions can be made when you are adjusting pages in your personal userspace or making rapid iterations while testing changes to a code page, though "cap" summaries (summary text for the first and last edits of your rapid editing session) which explain what you were starting to do, and ended up doing, would be nice. | ||