The following is a simple list of the current status of specific policies regarding CSS, and other related elements across the several branches of the SCP Foundation:
This list was last updated on 08/01/2023 at 06:20 (UTC+0).
1. Is there a specific page outlining CSS/tech policies?
1.1. Is there a specific team (e.g Tech Team) responsible for CSS/tech policies?
1.2. Are users allowed to create their own themes, or other custom CSS elements? Does it need approval from a specific party?
2. What is considered the "standard theme" (e.g. EN's Sigma-9, PT's Green BHL, etc.) for the branch?
3. Are there any special modifications (e.g. a different default font, a different side-menu style, etc.) in the standard theme of the branch?
4. Are users allowed to use custom/non-standard themes?
5. Are users allowed to use custom/non-standard logos?
6. Are users allowed to use custom CSS components (e.g. ACS, Info-Ayers, etc.)?
7. Are there any specific rules (e.g. adapting a custom theme to a Sigma-9 version, removing certain types of content such as images, or logos, etc.) for translated pages?
EN
1. Is there a specific page outlining CSS/tech policies?
Yes. Click here to access the technical content policy, and click here to access the CSS policy.
1.1. Is there a specific team (e.g Tech Team) responsible for CSS/tech policies?
Yes. Click here for more information about the Tech Team.
1.2. Are users allowed to create their own themes, or other custom CSS elements? Does it need approval from a specific party?
Yes.
It requires approval from the Tech Team.
2. What is considered the "standard theme" (e.g. EN's Sigma-9, PT's Green BHL, etc.) for the branch?
Sigma-9.
3. Are there any special modifications (e.g. a different default font, a different side-menu style, etc.) in the standard theme of the branch?
EN's Sigma-9 is considered the "de facto" default theme for the SCP-Wiki.
4. Are users allowed to use custom/non-standard themes?
Yes.
5. Are users allowed to use custom/non-standard logos?
Yes.
6. Are users allowed to use custom CSS components (e.g. ACS, Info-Ayers, etc.)?
Yes.
7. Are there any specific rules (e.g. adapting a custom theme to a Sigma-9 version, removing certain types of content such as images, or logos, etc.) for translated pages?
All pages must comply with EN's Tech Policy.
ZH-TR
1. Is there a specific page outlining CSS/tech policies?
Currently under development.
1.1. Is there a specific team (e.g Tech Team) responsible for CSS/tech policies?
No.
The existing "Maintenance Team" does not deal with policy-making, only with side-wide maintenance. Click here to access the page.
1.2. Are users allowed to create their own themes, or other custom CSS elements? Does it need approval from a specific party?
Yes.
Only translated themes need to be approved by the administrative team.
2. What is considered the "standard theme" (e.g. EN's Sigma-9, PT's Green BHL, etc.) for the branch?
Sigma-9.
3. Are there any special modifications (e.g. a different default font, a different side-menu style, etc.) in the standard theme of the branch?
Yes. A number of components have been added directly to the theme.
4. Are users allowed to use custom/non-standard themes?
Yes.
5. Are users allowed to use custom/non-standard logos?
Yes.
6. Are users allowed to use custom CSS components (e.g. ACS, Info-Ayers, etc.)?
Yes.
7. Are there any specific rules (e.g. adapting a custom theme to a Sigma-9 version, removing certain types of content such as images, or logos, etc.) for translated pages?
Translated pages have to maintain the appearance, and design of the source page.
The "Maintenance Team" is responsible for ensuring the quality of translated articles.
FR
1. Is there a specific page outlining CSS/tech policies?
Currently under development.
Diegesis and layout consistency throughout the site are considered the major criteria to allow or disallow visual changes as part of the interface.
1.1. Is there a specific team (e.g Tech Team) responsible for CSS/tech policies?
Yes, a Tech Team.
1.2. Are users allowed to create their own themes, or other custom CSS elements? Does it need approval from a specific party?
Yes, it must be approved by the Tech Team.
2. What is considered the "standard theme" (e.g. EN's Sigma-9, PT's Green BHL, etc.) for the branch?
Sigma-9.
FR hosts its own version of the theme on the branch's GitHub.
3. Are there any special modifications (e.g. a different default font, a different side-menu style, etc.) in the standard theme of the branch?
A different body font and several minor UI choices that were made by staff and/or the community.
4. Are users allowed to use custom/non-standard themes?
Only derivatives of Sigma-9 AND only if the theme fits the diegesis and layout consistency criteria.
5. Are users allowed to use custom/non-standard logos?
Logos are considered like all other CSS changes and fall under the same conditions as point 4.
6. Are users allowed to use custom CSS components (e.g. ACS, Info-Ayers, etc.)?
Nature dependent.
ACS and other components intended on replacing "default" or "standard" components/formats are disallowed.
Custom CSS boxes and other elements that do not replace "default" or "standard" components/formats are allowed.
7. Are there any specific rules (e.g. adapting a custom theme to a Sigma-9 version, removing certain types of content such as images, or logos, etc.) for translated pages?
All pages are subjected to the same rules regardless of whether they are original articles or translated articles.
Click here to access the policies.
VN
1. Is there a specific page outlining CSS/tech policies?
Yes. Click here to access the page.
1.1. Is there a specific team (e.g Tech Team) responsible for CSS/tech policies?
Yes. The Tech Team. Click here to access the page.
1.2. Are users allowed to create their own themes, or other custom CSS elements? Does it need approval from a specific party?
Yes. It needs to be approved by the Tech Team.
2. What is considered the "standard theme" (e.g. EN's Sigma-9, PT's Green BHL, etc.) for the branch?
Sigma-9.
3. Are there any special modifications (e.g. a different default font, a different side-menu style, etc.) in the standard theme of the branch?
VN's official logo replaces the "default" SCP Foundation logo.
VN's theme is ported directly from EN.
4. Are users allowed to use custom/non-standard themes?
Yes.
5. Are users allowed to use custom/non-standard logos?
Yes.
6. Are users allowed to use custom CSS components (e.g. ACS, Info-Ayers, etc.)?
Yes.
7. Are there any specific rules (e.g. adapting a custom theme to a Sigma-9 version, removing certain types of content such as images, or logos, etc.) for translated pages?
No.
IT
1. Is there a specific page outlining CSS/tech policies?
No.
1.1. Is there a specific team (e.g Tech Team) responsible for CSS/tech policies?
Yes. The Tech Team.
1.2. Are users allowed to create their own themes, or other custom CSS elements? Does it need approval from a specific party?
Yes. It needs to be approved by the Tech Team.
2. What is considered the "standard theme" (e.g. EN's Sigma-9, PT's Green BHL, etc.) for the branch?
Sigma-9.
A branch-specific version is currently under development.
3. Are there any special modifications (e.g. a different default font, a different side-menu style, etc.) in the standard theme of the branch?
Minor adjustments to UI elements.
4. Are users allowed to use custom/non-standard themes?
Yes.
5. Are users allowed to use custom/non-standard logos?
Yes.
6. Are users allowed to use custom CSS components (e.g. ACS, Info-Ayers, etc.)?
Yes.
7. Are there any specific rules (e.g. adapting a custom theme to a Sigma-9 version, removing certain types of content such as images, or logos, etc.) for translated pages?
Translated pages have to maintain the appearance, and design of the source page.
Click here to access the policy.
KO
1. Is there a specific page outlining CSS/tech policies?
Yes. Click here to access the policy.
1.1. Is there a specific team (e.g Tech Team) responsible for CSS/tech policies?
Yes. The Tech Team.
1.2. Are users allowed to create their own themes, or other custom CSS elements? Does it need approval from a specific party?
Yes. Approval by the Tech Team is only required if the theme, or other custom CSS element does not follow the standards outlined in the CSS/tech policy.
2. What is considered the "standard theme" (e.g. EN's Sigma-9, PT's Green BHL, etc.) for the branch?
Sigma-9.
3. Are there any special modifications (e.g. a different default font, a different side-menu style, etc.) in the standard theme of the branch?
Added support for Korean fonts.
Minor UI modifications.
4. Are users allowed to use custom/non-standard themes?
Yes.
5. Are users allowed to use custom/non-standard logos?
Yes.
6. Are users allowed to use custom CSS components (e.g. ACS, Info-Ayers, etc.)?
Yes.
7. Are there any specific rules (e.g. adapting a custom theme to a Sigma-9 version, removing certain types of content such as images, or logos, etc.) for translated pages?
No.
DE
1. Is there a specific page outlining CSS/tech policies?
Yes. Click here to access the policy (Coderegeln).
1.1. Is there a specific team (e.g Tech Team) responsible for CSS/tech policies?
No.
1.2. Are users allowed to create their own themes, or other custom CSS elements? Does it need approval from a specific party?
Yes, provided it makes "narrative sense" for the article it is used for.
Author pages are exempt from this rule.
No approval beyond "draft approval" as part of DE's special "critique process".
2. What is considered the "standard theme" (e.g. EN's Sigma-9, PT's Green BHL, etc.) for the branch?
Sigma-9.
3. Are there any special modifications (e.g. a different default font, a different side-menu style, etc.) in the standard theme of the branch?
Several components were added directly to the theme.
4. Are users allowed to use custom/non-standard themes?
Yes, provided it makes "narrative sense" for the article it is used for.
5. Are users allowed to use custom/non-standard logos?
Yes, provided it makes "narrative sense" for the article it is used for.
6. Are users allowed to use custom CSS components (e.g. ACS, Info-Ayers, etc.)?
Requires approval during the "draft approval" as part of DE's special "critique process".
7. Are there any specific rules (e.g. adapting a custom theme to a Sigma-9 version, removing certain types of content such as images, or logos, etc.) for translated pages?
CSS components, and themes which are not compliant with DE's CSS/tech policy are removed.
Non-compliant CSS components, and themes are added if the author of the source material provides a reasonable explanation that goes beyond "personal preference" for the addition of the CSS component/theme.
The author of the source material may also be requested to, or willingly provide a policy-compatible version of the non-compliant CSS components, and theme if necessary.
JP
1. Is there a specific page outlining CSS/tech policies?
Yes. Click here to access the policy.
1.1. Is there a specific team (e.g Tech Team) responsible for CSS/tech policies?
Yes. The Tech Team.
1.2. Are users allowed to create their own themes, or other custom CSS elements? Does it need approval from a specific party?
Yes. It requires approval from the Tech Team.
2. What is considered the "standard theme" (e.g. EN's Sigma-9, PT's Green BHL, etc.) for the branch?
Sigma-9.
3. Are there any special modifications (e.g. a different default font, a different side-menu style, etc.) in the standard theme of the branch?
Sidebar Conveniences;
Colmod: multi-folding syntax;
diff : display diff like github (adapted from CN);
Meta title folding : Collapse long meta titles in SCP list;
Disable copying of user syntax : When user syntax is copied, the user name is not copied more than once.
4. Are users allowed to use custom/non-standard themes?
Yes.
5. Are users allowed to use custom/non-standard logos?
Yes.
6. Are users allowed to use custom CSS components (e.g. ACS, Info-Ayers, etc.)?
Yes.
7. Are there any specific rules (e.g. adapting a custom theme to a Sigma-9 version, removing certain types of content such as images, or logos, etc.) for translated pages?
Yes. Custom themes must be adapted to be compatible with JP's standard theme.
CS
1. Is there a specific page outlining CSS/tech policies?
No.
1.1. Is there a specific team (e.g Tech Team) responsible for CSS/tech policies?
No. It is under the purview of the administrative team.
1.2. Are users allowed to create their own themes, or other custom CSS elements? Does it need approval from a specific party?
Yes. No approval is needed.
2. What is considered the "standard theme" (e.g. EN's Sigma-9, PT's Green BHL, etc.) for the branch?
Sigma-9 - Common Theme version.
3. Are there any special modifications (e.g. a different default font, a different side-menu style, etc.) in the standard theme of the branch?
Minor quality of life modifications.
4. Are users allowed to use custom/non-standard themes?
Yes.
5. Are users allowed to use custom/non-standard logos?
Yes.
6. Are users allowed to use custom CSS components (e.g. ACS, Info-Ayers, etc.)?
Yes.
7. Are there any specific rules (e.g. adapting a custom theme to a Sigma-9 version, removing certain types of content such as images, or logos, etc.) for translated pages?
LGBTQ+ logos are removed from translated pages.
LGBTQ+ logos are added if the author of the source material requests it.
UA
1. Is there a specific page outlining CSS/tech policies?
No.
1.1. Is there a specific team (e.g Tech Team) responsible for CSS/tech policies?
No.
1.2. Are users allowed to create their own themes, or other custom CSS elements? Does it need approval from a specific party?
Yes.
Themes, and other custom CSS elements are approved jointly with the articles they are used in as part of UA's standard "critique procedures".
2. What is considered the "standard theme" (e.g. EN's Sigma-9, PT's Green BHL, etc.) for the branch?
Sigma-9.
3. Are there any special modifications (e.g. a different default font, a different side-menu style, etc.) in the standard theme of the branch?
Unmodified from EN.
4. Are users allowed to use custom/non-standard themes?
Yes. It mustn't violate national legislation involving the depictions of authoritarian symbols (e.g. symbols from Communist, and Nazi regimes, etc.).
5. Are users allowed to use custom/non-standard logos?
Yes. It mustn't violate national legislation involving the depictions of authoritarian symbols (e.g. symbols from Communist, and Nazi regimes, etc.)..
6. Are users allowed to use custom CSS components (e.g. ACS, Info-Ayers, etc.)?
Yes. It mustn't violate national legislation involving the depictions of authoritarian symbols (e.g. symbols from Communist, and Nazi regimes, etc.).
7. Are there any specific rules (e.g. adapting a custom theme to a Sigma-9 version, removing certain types of content such as images, or logos, etc.) for translated pages?
Yes. It mustn't violate national legislation involving the depictions of authoritarian symbols (e.g. symbols from Communist, and Nazi regimes, etc.).
PT
1. Is there a specific page outlining CSS/tech policies?
Yes. Click here to access the policy.
1.1. Is there a specific team (e.g Tech Team) responsible for CSS/tech policies?
Yes. The Curator Team.
1.2. Are users allowed to create their own themes, or other custom CSS elements? Does it need approval from a specific party?
Yes. It requires approval from the Curator Team.
2. What is considered the "standard theme" (e.g. EN's Sigma-9, PT's Green BHL, etc.) for the branch?
BHL.
3. Are there any special modifications (e.g. a different default font, a different side-menu style, etc.) in the standard theme of the branch?
Yes.
The theme has been modified with a custom logo, and header.
Several components have been added directly to the theme.
4. Are users allowed to use custom/non-standard themes?
Yes.
5. Are users allowed to use custom/non-standard logos?
Yes.
6. Are users allowed to use custom CSS components (e.g. ACS, Info-Ayers, etc.)?
Yes.
7. Are there any specific rules (e.g. adapting a custom theme to a Sigma-9 version, removing certain types of content such as images, or logos, etc.) for translated pages?
Translated pages have to maintain the appearance, and design of the source page.
RU
1. Is there a specific page outlining CSS/tech policies?
Yes. Click here to access the page.
1.1. Is there a specific team (e.g Tech Team) responsible for CSS/tech policies?
Yes. The Tech Team.
RU's Tech Team is mostly focused, and responsible for developing, and maintaining the site; CSS solutions are usually developed by the users themselves.
1.2. Are users allowed to create their own themes, or other custom CSS elements? Does it need approval from a specific party?
Yes. It needs to be approved by the administrative team.
2. What is considered the "standard theme" (e.g. EN's Sigma-9, PT's Green BHL, etc.) for the branch?
Sigma-9.
3. Are there any special modifications (e.g. a different default font, a different side-menu style, etc.) in the standard theme of the branch?
The page-width has been increased in order to support the length, and formatting of Russian words.
4. Are users allowed to use custom/non-standard themes?
Yes. It requires approval from the administrative team.
5. Are users allowed to use custom/non-standard logos?
No.
6. Are users allowed to use custom CSS components (e.g. ACS, Info-Ayers, etc.)?
No.
7. Are there any specific rules (e.g. adapting a custom theme to a Sigma-9 version, removing certain types of content such as images, or logos, etc.) for translated pages?
Content (such as logos, images, etc) which violates the laws of the Russian Federation is removed.
TH
1. Is there a specific page outlining CSS/tech policies?
No.
1.1. Is there a specific team (e.g Tech Team) responsible for CSS/tech policies?
No.
1.2. Are users allowed to create their own themes, or other custom CSS elements? Does it need approval from a specific party?
Yes. Users must notify the administrative team before creating their own themes but they do not need approval.
2. What is considered the "standard theme" (e.g. EN's Sigma-9, PT's Green BHL, etc.) for the branch?
Sigma-9.
3. Are there any special modifications (e.g. a different default font, a different side-menu style, etc.) in the standard theme of the branch?
Yes.
The theme has been modified with a custom logo, and an animated header.
4. Are users allowed to use custom/non-standard themes?
Yes.
5. Are users allowed to use custom/non-standard logos?
Yes.
6. Are users allowed to use custom CSS components (e.g. ACS, Info-Ayers, etc.)?
Yes.
7. Are there any specific rules (e.g. adapting a custom theme to a Sigma-9 version, removing certain types of content such as images, or logos, etc.) for translated pages?
No.
ES
1. Is there a specific page outlining CSS/tech policies?
Currently under development.
1.1. Is there a specific team (e.g Tech Team) responsible for CSS/tech policies?
No.
1.2. Are users allowed to create their own themes, or other custom CSS elements? Does it need approval from a specific party?
Yes. No approval is required.
2. What is considered the "standard theme" (e.g. EN's Sigma-9, PT's Green BHL, etc.) for the branch?
Sigma-9.
3. Are there any special modifications (e.g. a different default font, a different side-menu style, etc.) in the standard theme of the branch?
No.
4. Are users allowed to use custom/non-standard themes?
Yes, as long as they make sense in the setting, group or plot of the article, but BHL is disallowed.
5. Are users allowed to use custom/non-standard logos?
Yes, as long as they make sense in the setting, group or plot of the article.
6. Are users allowed to use custom CSS components (e.g. ACS, Info-Ayers, etc.)?
Yes, as long as they make sense in the setting, group or plot of the article, but ACS is disallowed.
7. Are there any specific rules (e.g. adapting a custom theme to a Sigma-9 version, removing certain types of content such as images, or logos, etc.) for translated pages?
BHL themes must be changed to their Sigma-9 variants on translations. If that variant doesn't exist, BHL must be removed. ACS must be removed. AI-generated content must be removed.
The abovementioned rules do not apply to Author Pages or Artist Galleries on ES; authors can do almost whatever they want in their personal spaces as long as they list their contributions or art, respectively, and don't break other site rules.