Help:Style guide/Test chambers

Test Chambers are an integral part of each game. Each Test Chamber in Portal and Portal 2 should have a page dedicated to it and those pages should meet the guidelines outlined on this page.

Naming conventions
Test Chambers are identified by numbers, and within each game there are different test chambers that share a name. For that reason, the following conventions are in place to ensure each Test Chamber gets it's own article:

Singleplayer

 * Test Chamber pages are prefixed with the game they are contained within.
 * For example:
 * This would be a redirect to the above example, as in Portal: Still Alive the only difference in test chambers is additional ones at the end.
 * In the case of Portal 2, or any future Portal game that has Acts with test chambers per each Act, there is an suffix appended to the game prefix - noting which Act the test chamber is part of. Refer to the Story article for a definition of each Act.
 * For example:
 * The numerical identifier of the test chamber should always be double-digits, as they are signage of each test chamber.
 * The numerical identifier of the test chamber should always be double-digits, as they are signage of each test chamber.
 * The numerical identifier of the test chamber should always be double-digits, as they are signage of each test chamber.
 * The numerical identifier of the test chamber should always be double-digits, as they are signage of each test chamber.

Co-op
The above singleplayer naming conventions apply to Co-op, with exception to the Act naming.
 * Instead of Act in the above guidelines, the name will contain the game mode Co-op.
 * Following the  identifier will be the numerical identifier of the Chapter in which the test chamber is a part of.
 * For example:

Solutions

 * Solutions will be noted in a dedicated sub-page of each Test Chamber. Append   to a Test Chamber's page to access this sub-page and write or modify the content there.
 * For example:

Coverage
Each Test Chamber page should mention the following things:
 * What Mechanics a user will interact with.
 * What threats a user will interact with.
 * What the Test Chamber intends the player to learn, if anything.
 * Regarding the Story
 * Or the use of Mechanics

Solutions
Solutions will be contained within a dedicated subpage, as mentioned in the above naming conventions. Solution pages should contain the following:
 * A walkthrough of the Test Chamber, accompanied by annotated screenshots.
 * A video walkthrough of the test chamber.