(outline of what newly recruited waze editor should read before beginning. very simple language with very little jargon. lots of easy links to the information they will need to digest. what NOT to do.) |
No edit summary |
||
| Line 1: | Line 1: | ||
This is a work in progress, obviously. | |||
Please feel free to discuss at: https://www.waze.com/forum/viewtopic.php?f=276&t=108515 | |||
or to type the right stuff right here. | |||
Opening paragraph. Welcome. Purpose and guidelines. What the waze map is designed for. What it is not designed for. Usability. Simplicity. Retention. | Opening paragraph. Welcome. Purpose and guidelines. What the waze map is designed for. What it is not designed for. Usability. Simplicity. Retention. | ||
Revision as of 19:09, 10 September 2014
This is a work in progress, obviously. Please feel free to discuss at: https://www.waze.com/forum/viewtopic.php?f=276&t=108515 or to type the right stuff right here.
Opening paragraph. Welcome. Purpose and guidelines. What the waze map is designed for. What it is not designed for. Usability. Simplicity. Retention.
Your first editing session
- That silly, out-of-date video
- What not to do (delete roads. Create area places. Create parking lots. Add lots of roads or lanes in parking lots)
- Learn to work the chat -- introduce yourself as a first-time editor
- Using the practice editor
- What to edit your first time out
- Get your area manager to check your work.
- How to find your area manager.
After your first editing session
- Ask lots of questions
- Check your work
- Good tools for checking your own work
- WME validator
- The letter Z
- Color Highlighter
- Good tools for checking your own work
- Start reading the wiki
- Using the forums