Please follow the guidelines set out below whenever creating a new page. If in doubt, please ask on the Community Portal first.
Bugs and Glitches
Only create pages about bugs and glitches if they are extremely prominent (e.g. the Disappearing Text Bug) or have otherwise played an important role in Scratch culture (e.g. the Semicolon Glitch). If a glitch is fairly minor but is still well-known, include it as a section in the article about the relevant feature (e.g. a bug in the paint editor would be included in the Paint Editor article).
New collaboration pages are not allowed. Only a few existing pages have been allowed to remain as notable examples.
Duplicate pages are not allowed. They will be merged, redirected to the original article, or deleted.
Parody, hoax, joke, intentionally misleading, or otherwise fake articles are not allowed.
In general, articles should be written about features in the Scratch editor and website. However, if they are very small or subsets of another feature (e.g. individual tools in the Paint Editor), they should be included as sections in the article of the parent feature.
Only create pages for Scratch modifications that would widely be considered extremely notable.
Pages that can be split into more than one article will be split into multiple articles. If one of the new articles does not qualify, do not create a page for that subject.
Pages about subjects not related to Scratch are not allowed. They will be deleted, sometimes without notice. Gibberish and blank pages are considered not related to Scratch.
Scratchers and Projects
Pages about Scratchers and projects are not allowed except for ones that are extremely important to Scratch history (e.g. Kaj, Removed Pac-Man Project, etc). Within an article, you may link to a project as long as it provides a relevant example. However, it must only be linked in the context of an article and not in a fashion that could be seen as advertising.
Pages about trends through Scratch history are generally only allowed if they have been deemed extremely notable by a wide number of people.
Tutorials should be applicable to a broad range of projects, rather than just a small subset of projects. For example, explaining how to use arrow keys to make a sprite move would be acceptable while explaining how to write a specific kind of game using the arrow keys would not.