(Redirected from S:NEWPAGES)
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.
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.
Do not create new pages for Scratch Modifications. Only several such pages have been allowed to remain as notable examples. Scratch Modifications should document themselves on their own websites. However, new modifications can still be listed in the list of modifications if they have been completed.
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 (and any other user-generated content) are generally not allowed. The exceptions are:
- Topics that are confirmed to have involved at least one Scratch Team member. However, they must still be considered otherwise notable; simply having Scratch Team involvement is not sufficient reason to allow such a page. For example, the Scratch Design Studio is documented since it is a major component of the site even though it is a studio, but there are not articles for most other studios that various Scratch Team members curate.
- Topics that have been considered important/notable enough in Scratch's history by a majority of Wiki editors that they deserve an article (e.g. kaj, Removed Pac-Man Project, etc.).
Anything that may fit an exception listed above will be decided on a case-by-case basis.
Additionally, projects may be linked to as examples to get the point of an article across more effectively, such as on Pen Projects. They must, however, be relevant to the topic and work adequately well, and they should only be mentioned in the context of the article. The article should not be or look like an article about that specific project.
Articles on users mostly known for having the most followers or otherwise being popular, such as Griffpatch, will not be allowed, per this Community Portal discussion.
Individual pages about trends through Scratch history are generally only allowed if they have been deemed extremely notable by a wide number of people. For example, Add Everything Studios is allowed to exist as its own page due to the large amount of controversy they generated in the Scratch community.
For moderately notable trends, a section in one of the four lists linked at Scratch Trends may be created and potentially a redirect to that section may be created at the title of that trend. For example, Lyrics Taken Literally is a section in Project Trends and a redirect exists at that title, but it is not its own page. To be included on one of those lists, the trend must still be reasonably widespread or had a significant impact on Scratch culture.
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 whereas explaining how to write a Pac-Man game using the arrow keys would not. There is some gray area in between, which is decided on a case-by-case basis.