Roblox Wiki Editing Policy: Difference between revisions
>NXTBoy Heading level fix |
>DBugSlayer →Age related: - Fix minor typo |
||
| Line 40: | Line 40: | ||
===Age related=== | ===Age related=== | ||
Though Roblox has a wide age group to appeal to, most tutorials and pages should be written in such a way that | Though Roblox has a wide age group to appeal to, most tutorials and pages should be written in such a way that users 8-12 would be able to understand. It's fine to have 'advanced' pages that go into more detail or more complex descriptions on how something works or otherwise. | ||
===Writing Style=== | ===Writing Style=== | ||
Revision as of 22:57, 3 August 2011
Revision as of 3/25/10
This is subject to change without notice.
We encourage people to edit and contribute their knowledge to the Wiki, however there are a number of guidelines we ask you to follow while you add to our Wiki.
Editing Levels
Writers
- Are able to upload images
- Are able to edit pages, NOT protected pages
- Are able to discuss on talk pages.
Editors
- Are able to do all that of Writers.
- Are able to edit protected pages
- Are able to review revisions from Writers, approve or disapprove submissions
- Able to give 1 day bans to writers who are spamming or otherwise, pending review from Sysops.
System Operators
- All powers of Editors
- Have command over new accounts
- Ability to ban accounts
Administrators
- All powerful.
General Guidelines
What the Wiki is
The Roblox wiki is meant to be information on how to build, script and play in Roblox. This means information on how to accomplish general tasks, such as putting bricks together in different patterns, or small 2-3 lines of code on how to use an Object. Small things that simply explain what something does or how to use it.
What the Wiki is not
The wiki is not an instruction site. We are here for tutorials on general ideas, NOT to create specific instructions on creating specific items.
There should not be a guide on how to make a plane. There should be a guide on how to aim a brick using BodyGyro, and there should be a guide on how to make a brick fly using BodyVelocity. Users should create their own ideas on how to make a plane or be guided towards a tutorial on how to use Free Models.
Though Roblox has a wide age group to appeal to, most tutorials and pages should be written in such a way that users 8-12 would be able to understand. It's fine to have 'advanced' pages that go into more detail or more complex descriptions on how something works or otherwise.
Writing Style
Direct writing (not referring to 'you' or 'I', non-personalized) was attempted and found to be more confusing. Treat written pages as though you are explaining something to a friend sitting next to you. Don't go overboard with it, just refer to "Lets do this" or "Take a look here", as the second person.
Graphics and Pretty
Yes, the Wiki should be pretty. Examine pages such as Main Page, Rixty, Studio are very 'pretty', they have a layout and plenty of graphical examples to make the information easier to understand. Where possible, set up guides in the format of the Coinstar Tutorial or Flowcharts. You can copy the source tables from those pages to set it up properly, or ask someone who knows how to use it.
ImageMap
We have installed the ImageMap plugin. For an example of this in use, check out the Studio page. ImageMaps are excellent for explaining graphical elements. Let me say that again. Image maps are excellent for explaining graphical elements. They are so excellent that you should use them where you can find a use for them.
That said they have a learning curve. Unless you find counting pixels fun, I would suggest bookmarking this page. It's invaluable.
Templates
There are a whole batch of different templates that you can play with. Take a look at the list of stable templates. Those are the ones you should use on pages where applicable. One above all else is the Template:CatUp template. This should be used often, it gives a clean system for navigating about the Wiki.
Each page should make use of the CatUp template, as well as many links as are appropriate. This should be the first time a term comes up, such as Variables, Studio, etc. Additionally, make use of piped links to make links more clear (links with alternate text).
Off-site links should be kept to a minimum. Wikipedia and Lua.org are fine. Any other links should be checked through MrDoom first.
Protected Pages
Protected pages are usually protected for a good reason. Be that they're needed over a wide range of pages in the case of templates, or because they're key to the navigation of the site, such as the Main Page. If you wish to edit protected pages make it clear on the talk page or in the edit comment what you did and why.
Revisions
We have installed the FlaggedRevisions extension. What this does is hold back changes to pages until they are reviewed by an Editor or higher. This allows edits while still maintaining a level of appropriateness on the Wiki.
When you are promoted to Editor you should be given a guide on it's use by MrDoom. Editors should scan the Recent Changes and browse through the latest revisions.
File Uploads
In a statement: Keep them small and to the theme. Don't upload crazy amounts of files and try to use slightly lossy formats. JPG is fine for thumbnails or small images. PNG is a good format when a picture needs to stay clear and crisp.
Account Actions
If you go against these guidelines without good reason often, there's a good chance you'll lose your ability to edit pages. The idea is that everyone is here working together to better the wiki, because no single person knows everything, myself included. Editors are there to make sure Writers have the right idea on how to write for the Wiki. Editors are there to make the wiki flow coherently. I'm here to help tie things together and as a general Wiki formatting guru. Ask questions. Questions are good. If you're not sure, double check.
If you make more work for Editors, other writers, other Editors or MrDoom you start to run the risk of having your account demoted. If this is the case take a little time off and just browse the wiki, get an idea for how it works and the direction it's taking. In this case it pays to be able to fit in.
