SmashWiki:Read This First, Man

NOTE: This is incomplete. Feel free to comment and improve but do not treat this as an active proposal.

[insert cheesy introduction here]

Step 1: Get the point

While you should know this by now, we are a wiki. We're not a forum, or a personal webspace provider, or a social site, or a strategy guide. We are an organized encyclopedic collection of information that depends on its userbase to provide correct and up-to-date content. To that end, we expect all users to have a reasonable work-to-fun ratio - you are allowed a certain amount of freedom on user pages and forums, but at some point you will be expected to contribute positively to the wiki's goal.

Step 2: Get the rules

As a new user, you are not required to know the full technical ins-and-outs of every policy and guideline; other users will generally assume good faith should you break rules, and administrators will almost never issue blocks without outlining what you have done wrong. Regardless, it is your job to be aware of the rules and how they apply to you; ignorance of rules is essentially never accepted as a valid excuse.

Step 3: Get the activity

You may already know this, but all wikis have a special page called Recent Changes used to keep track of all edits made to the wiki. We recommend that users spend most of their idle time on this page in order to watch for proposal discussions, major article revisions, and unconstructive edits that need to be undone. This includes new users, who would do well to get a feel for how the wiki works by watching others edit before making any serious changes themselves.

Step 4: Get the interface

Beyond simple text, wikicode can be confusing to new users. Before fumbling around in articles trying to get things to work, use the sandbox to make test edits. It can also be helpful to click the edit button of a page but not change anything, instead simply reading the code to see how it compares to the page's result. Finally, one can use their userpage as a testing ground if you don't want other people in the Sandbox messing up your tests; do note step 1 above however. In any case, the most important rule is to use the preview button before saving edits, as nobody likes it when Recent Changes lists five edits that together only did one thing.

Step 5: Get the ???

Now armed with knowledge of how to edit, many new users' first question is what to edit. In many cases, the usage of Special:Random can help find errors or problems that no one else has seen in years. [needs more work]