Site News Hub

Note: These are different from the main page's news and the Archived News. Those are for live updates on the site's workings, policies, and projects. This is a summary for site articles and fandom creations for the month in whole, posted at the beginning of each month. If you wish to comment on this news series as a whole, or make suggestions, please comment on this hub instead of the individual pages. Please do not add rating modules to any of the individual pages.


rating: +206+x

News for August, 2021

/* source: http://ah-sandbox.wikidot.com/component:collapsible-sidebar-x1 */
 
#top-bar .open-menu a {
        position: fixed;
        top: 0.5em;
        left: 0.5em;
        z-index: 5;
        font-family: 'Nanum Gothic', san-serif;
        font-size: 30px;
        font-weight: 700;
        width: 30px;
        height: 30px;
        line-height: 0.9em;
        text-align: center;
        border: 0.2em solid #888;
        background-color: #fff;
        border-radius: 3em;
        color: #888;
}
 
@media (min-width: 768px) {
 
    #top-bar .mobile-top-bar {
        display: block;
    }
 
    #top-bar .mobile-top-bar li {
        display: none;
    }
 
    #main-content {
        max-width: 708px;
        margin: 0 auto;
        padding: 0;
        transition: max-width 0.2s ease-in-out;
    }
 
    #side-bar {
        display: block;
        position: fixed;
        top: 0;
        left: -20em;
        width: 17.75em;
        height: 100%;
        margin: 0;
        overflow-y: auto;
        z-index: 10;
        padding: 1em 1em 0 1em;
        background-color: rgba(0,0,0,0.1);
        transition: left 0.4s ease-in-out;
 
        scrollbar-width: thin;
    }
 
    #side-bar:target {
        left: 0;
    }
 
     #top-bar .close-menu {
        margin-left: 19.75em;
        opacity: 0;
    }
    #side-bar:target .close-menu {
        display: block;
        position: fixed;
        width: 100%;
        height: 100%;
        top: 0;
        left: 0;
        z-index: -1;
    }
 
    #top-bar .open-menu a:hover {
        text-decoration: none;
    }
}
 
@supports selector(:focus-within) {
 
@media (min-width: 768px) {
    #top-bar .open-menu a {
        pointer-events: none;
    }
    #side-bar:not(:target) .close-menu {
        display: block;
        pointer-events: none;
        user-select: none;
        z-index: -1;
    }
 
    /* This pseudo-element is meant to overlay the regular sidebar button
    so the fixed positioning (top, left, right and/or bottom) has to match */
 
    #side-bar .close-menu::before {
        content: "";
        position: fixed;
        z-index: 5;
        display: block;
 
        top: 0.5em;
        left: 0.5em;
 
        border: 0.2em solid transparent;
        width: 30px;
        height: 30px;
        font-size: 30px;
        line-height: 0.9em;
 
        pointer-events: all;
        cursor: pointer;
    }
    #side-bar:focus-within {
        left: 0;
    }
    #side-bar:focus-within .close-menu::before {
        pointer-events: none;
    }
}
 
}
rating: +206+x

What this is

A bunch of miscellaneous CSS 'improvements' that I, CroquemboucheCroquembouche, use on a bunch of pages because I think it makes them easier to deal with.

The changes this component makes are bunch of really trivial modifications to ease the writing experience and to make documenting components/themes a bit easier (which I do a lot). It doesn't change anything about the page visually for the reader — the changes are for the writer.

I wouldn't expect translations of articles that use this component to also use this component, unless the translator likes it and would want to use it anyway.

This component probably won't conflict with other components or themes, and even if it does, it probably won't matter too much.

Usage

On any wiki:

[[include :scp-wiki:component:croqstyle]]

This component is designed to be used on other components. When using on another component, be sure to add this inside the component's [[iftags]] block, so that users of your component are not forced into also using Croqstyle.

Related components

Other personal styling components (which change just a couple things):

Personal styling themes (which are visual overhauls):

CSS changes

Reasonably-sized footnotes

Stops footnotes from being a million miles wide, so that you can actually read them.

.hovertip { max-width: 400px; }

Monospace edit/code

Makes the edit textbox monospace, and also changes all monospace text to Fira Code, the obviously superior monospace font.

@import url('https://fonts.googleapis.com/css2?family=Fira+Code:wght@400;700&display=swap');
 
:root { --mono-font: "Fira Code", Cousine, monospace; }
#edit-page-textarea, .code pre, .code p, .code, tt, .page-source { font-family: var(--mono-font); }
.code pre * { white-space: pre; }
.code *, .pre * { font-feature-settings: unset; }

Teletype backgrounds

Adds a light grey background to <tt> elements ({{text}}), so code snippets stand out more.

tt {
  background-color: var(--swatch-something-bhl-idk-will-fix-later, #f4f4f4);
  font-size: 85%;
  padding: 0.2em 0.4em;
  margin: 0;
  border-radius: 6px;
}

No more bigfaces

Stops big pictures from appearing when you hover over someone's avatar image, because they're stupid and really annoying and you can just click on them if you want to see the big version.

.avatar-hover { display: none !important; }

Breaky breaky

Any text inside a div with class nobreak has line-wrapping happen between every letter.

.nobreak { word-break: break-all; }

Code colours

Add my terminal's code colours as variables. Maybe I'll change this to a more common terminal theme like Monokai or something at some point, but for now it's just my personal theme, which is derived from Tomorrow Night Eighties.

Also, adding the .terminal class to a fake code block as [[div class="code terminal"]] gives it a sort of pseudo-terminal look with a dark background. Doesn't work with [[code]], because Wikidot inserts a bunch of syntax highlighting that you can't change yourself without a bunch of CSS. Use it for non-[[code]] code snippets only.

Quick tool to colourise a 'standard' Wikidot component usage example with the above vars: link

:root {
  --c-bg: #393939;
  --c-syntax: #e0e0e0;
  --c-comment: #999999;
  --c-error: #f2777a;
  --c-value: #f99157;
  --c-symbol: #ffcc66;
  --c-string: #99cc99;
  --c-operator: #66cccc;
  --c-builtin: #70a7df;
  --c-keyword: #cc99cc;
}
 
.terminal, .terminal > .code {
  color: var(--c-syntax);
  background: var(--c-bg);
  border: 0.4rem solid var(--c-comment);
  border-radius: 1rem;
}

Debug mode

Draw lines around anything inside .debug-mode. The colour of the lines is red but defers to CSS variable --debug-colour.

You can also add div.debug-info.over and div.debug-info.under inside an element to annotate the debug boxes — though you'll need to make sure to leave enough vertical space that the annotation doesn't overlap the thing above or below it.

…like this!

.debug-mode, .debug-mode *, .debug-mode *::before, .debug-mode *::after {
  outline: 1px solid var(--debug-colour, red);
  position: relative;
}
.debug-info {
  position: absolute;
  left: 50%;
  transform: translateX(-50%);
  font-family: 'Fira Code', monospace;
  font-size: 1rem;
  white-space: nowrap;
}
.debug-info.over { top: -2.5rem; }
.debug-info.under { bottom: -2.5rem; }
.debug-info p { margin: 0; }
/*
    Newspaper Theme
    [2021 Wikidot Theme]
    By MalyceGraves and EstrellaYoshte
    Based on:
       Penumbra Theme by EstrellaYoshte
       Paperstack Theme by EstrellaYoshte
       Ad Astra Theme by NatVoltaic and stormbreath
       Inkblot Theme by Croquembouche
       Anderson Robotics Theme by Croquembouche
       BHL Style Collapsible by Monkatraz
       Monotypical Theme by EstrellaYoshte
*/
 
@import url('https://fonts.googleapis.com/css2?family=Kulim+Park&display=swap');
@import url('https://fonts.googleapis.com/css2?family=DM+Serif+Display&display=swap');
 
:root {
    --accentColor: #E5062B;
    --lgurl: url("http://scp-wiki.wdfiles.com/local--files/theme%3Anewspaper/newslogo.png");
    --bgurl: url("http://scp-wiki.wdfiles.com/local--files/theme%3Anewspaper/newshead.png");
 
    --primaryBackgroundColor: #f3f3f3;
    --textColor: #090B0C;
    --headerColor: #161B33;
    --selectionColor: #FFE419;
 
    --header-font: 'DM Serif Display', serif;
    --link-timing: 0.125s ease-out;
}
 
#content-wrap {
    margin: 0.65em auto 0;
    box-sizing: border-box;
}
#page-content { font-size: 1rem; }
 
body {
    font-family: 'Kulim Park', sans-serif;
    color: var(--textColor);
    background-color: #FFF4E9;
    background-image: none;
    background-repeat: no-repeat;
}
tt {
    background-color: var(--primaryBackgroundColor);
}
code {
    font-family: var(--mono-font);
}
#edit-page-textarea, .code pre, .code p, .code, tt, .page-source {
    font-size: 90%;
}
 
a:not(.rate-box-with-credit-button a, .page-rate-widget-box a, yui-nav a) {
    color: var(--accentColor);
}
 
#page-content div {
    clear: unset;
}
 
/* Selection */
::selection {
    background: var(--selectionColor);
    color: var(--textColor);
}
 
/* ---- HEADER ---- */
 
div#container-wrap {
     background-image: none;
}
div#header {
    background-image: none;
    height: 240px;
}
 
div#header-extra-div-1 {
    height: 164px;
    width: 100%;
    top: 0;
    position: absolute;
    background: var(--lgurl);
    background-size: contain;
    background-repeat: no-repeat;
    background-position: 50% 50%;
    opacity: 1;
    z-index: -1;
}
div#extra-div-1 {
    height: 164px;
    width: 100%;
    top: 0;
    position: absolute;
    background: var(--bgurl);
    background-size: cover;
    background-repeat: no-repeat;
    background-position: center 0;
    z-index: -2;
    -webkit-mask-image: linear-gradient(to bottom, rgba(0,0,0,1) 20%, rgba(0,0,0,0.3) 70%, rgba(0,0,0,0) 100%);
    mask-image: linear-gradient(to bottom, rgba(0,0,0,1) 20%, rgba(0,0,0,0.3) 70%, rgba(0,0,0,0) 100%);
}
 
#header h1, #header h2 { margin-left: 0; float: none; text-align: center; }
#header h1 a {
    padding-top: 174px;
    width: -moz-fit-content;
    width: fit-content;
    margin: 0 auto;
 
}
#header h2 { 
margin-top: 6.5rem;
    font-size: 0.75rem;
    font-style: italic;
}
/* Hide the existing text */
#header h1 span, #header h2 span { font-size: 0; display: none; }
/* Style the new text */
#header h1 a::before, #header h2::before {
  color: var(--headerColor);
  font-family: var(--header-font);
  text-shadow: none;
}
#header h2::before { color: var(--textColor); }
/* Set the new text's content from variable */
#header h1 a::before {
  content: var(--header-title, "SCP Foundation News");
  font-weight: 300;
  font-size: 1.3em;
}
#header h2::before {
  content: var(--header-subtitle, "The Official SCPN Monthly");
  font-weight: 600;
  font-size: 1.22em;
}
 
#login-status {
    color: var(--textColor);
    background-color: #FEFBF8;
    padding: 0.3rem 0.25rem 0.4rem 0.5rem;
    border-radius: 0 0 0.5rem 0.5rem;
    box-shadow: 0 0 3px 1px rgba(0,0,0,0.2);
    top: 0;
}
#login-status a {
    color: var(--accentColor);
}
#account-topbutton {
    border: none;
    margin-left: -0.1rem;
}
 
div#account-options {
    background-color: var(--primaryBackgroundColor);
    border: none;
    border-radius: 0.35rem;
    box-shadow: 0 0 4px 1px rgba(0,0,0,0.25);
    top: 1.85rem;
 
    display: block!important;
    opacity: 0;
    pointer-events: none;
    transition: opacity 0.15s;
}
#account-topbutton:focus + #account-options,
#account-topbutton:active + #account-options,
#account-options:focus-within {
    opacity: 1;
    pointer-events: all;
}
/* Without this, touchscreen doesn't work */
@media (pointer: coarse) {
    #account-topbutton:hover + #account-options,
    #account-options:hover {
        opacity: 1;
        pointer-events: all;
    }
}
#account-options li a,
#account-options li a:hover {
    color: var(--accentColor);
}
 
/* ---- SEARCH ---- */
div#search-top-box {
    top: 2.25rem;
    right: 0.5rem;
    width: 1.6rem;
}
 
div#search-top-box::before {
    content: "";
    display: block;
    width: 100%;
    height: 100%;
    position: absolute;
    top: 0; right: 0.05rem;
    background-color: var(--accentColor);
    pointer-events: none;
    z-index: 2;
    -webkit-mask-image: url("data:image/svg+xml,%3Csvg%20xmlns%3D%22http%3A%2F%2Fwww.w3.org%2F2000%2Fsvg%22%20viewBox%3D%220%200%20512%20512%22%3E%3Cpath%20fill%3D%22%23ddd%22%20d%3D%22M505%20442.7L405.3%20343c-4.5-4.5-10.6-7-17-7H372c27.6-35.3%2044-79.7%2044-128C416%2093.1%20322.9%200%20208%200S0%2093.1%200%20208s93.1%20208%20208%20208c48.3%200%2092.7-16.4%20128-44v16.3c0%206.4%202.5%2012.5%207%2017l99.7%2099.7c9.4%209.4%2024.6%209.4%2033.9%200l28.3-28.3c9.4-9.4%209.4-24.6.1-34zM208%20336c-70.7%200-128-57.2-128-128%200-70.7%2057.2-128%20128-128%2070.7%200%20128%2057.2%20128%20128%200%2070.7-57.2%20128-128%20128z%22%2F%3E%3C%2Fsvg%3E");
            mask-image: url("data:image/svg+xml,%3Csvg%20xmlns%3D%22http%3A%2F%2Fwww.w3.org%2F2000%2Fsvg%22%20viewBox%3D%220%200%20512%20512%22%3E%3Cpath%20fill%3D%22%23ddd%22%20d%3D%22M505%20442.7L405.3%20343c-4.5-4.5-10.6-7-17-7H372c27.6-35.3%2044-79.7%2044-128C416%2093.1%20322.9%200%20208%200S0%2093.1%200%20208s93.1%20208%20208%20208c48.3%200%2092.7-16.4%20128-44v16.3c0%206.4%202.5%2012.5%207%2017l99.7%2099.7c9.4%209.4%2024.6%209.4%2033.9%200l28.3-28.3c9.4-9.4%209.4-24.6.1-34zM208%20336c-70.7%200-128-57.2-128-128%200-70.7%2057.2-128%20128-128%2070.7%200%20128%2057.2%20128%20128%200%2070.7-57.2%20128-128%20128z%22%2F%3E%3C%2Fsvg%3E");
    -webkit-mask-size: 1rem;
            mask-size: 1rem;
    -webkit-mask-position: center;
            mask-position: center;
    -webkit-mask-repeat: no-repeat;
            mask-repeat: no-repeat;
    opacity: 1;
    transition: opacity 0.25s ease;
}
div#search-top-box:focus-within::before { opacity: 0; }
 
div#search-top-box form {
    display: flex;
    justify-content: flex-end;
}
 
div#search-top-box form input[type="text"]:not(:focus),
div#search-top-box form input[type="text"]:not(:focus):not(:hover) {
    position: relative;
    color: transparent;
    cursor: pointer;
    display: inline-block;
    font-family: var(--body-font);
    width: 1.6rem;
    height: 1.6rem;
    padding: 0.1em 0.5em;
    box-sizing: border-box;
    border-radius: 0.35rem;
    border: none;
    box-shadow: 0 0 2px 1.5px var(--shadow);
}
 
div#search-top-box form input[type="text"],
div#search-top-box form input[type="text"]:hover,
div#search-top-box form input[type="text"]:focus {
    background-color: var(--primaryBackgroundColor)!important;
    color: var(--textColor);
    display: inline-block;
    border: none;
    height: 1.6rem;
    width: 9rem;
    transition: width .25s;
    outline: none;
}
 
div#search-top-box form input[type="submit"] {
    display: none;
}
 
/* ---- TOP BAR ---- */
 
#top-bar {
     top: 14.6rem;
     display: flex;
     justify-content: center;
     right: 0;
}
@media (max-width: 768px) {
    .mobile-top-bar {
         display: flex;
         justify-content: center;
         max-width: 100%;
         width: 100%;
         left: 0;
    }
}
 
/* div[class*=top-bar] is to select both regular and mobile top bar that exist in #top-bar */
 
#top-bar div[class*=top-bar] > ul > li > a {
    color: var(--textColor);
}
 
#top-bar div[class*=top-bar] ul li ul li a {
    color: var(--accentColor);
}
 
#top-bar div[class*=top-bar] > ul > li > a:hover,
#top-bar div[class*=top-bar] > ul > li.sfhover > a {
    background-color: transparent;
    background: none;
}
 
#top-bar div[class*=top-bar] > ul > li,
#top-bar div[class*=top-bar] > ul > li.sfhover {
    background-color: transparent;
    background-image: linear-gradient(to bottom, var(--linkColor) 0%, var(--linkColor) 100%);
    background-size: 0 100%;
    background-position: 0 100%;
    background-repeat: no-repeat;
    transition: background-size var(--link-timing);
}
#top-bar div[class*=top-bar] > ul > li:hover,
#top-bar div[class*=top-bar] > ul > li:focus-within {
    background-color: transparent;
    background-size: 100% 100%;
}
 
#top-bar div[class*=top-bar] ul li ul {
    background-color: var(--primaryBackgroundColor);
    border: none;
    box-shadow: 0 0 4px rgba(0,0,0,0.3);
    border-radius: 0.5rem;
}
#top-bar div[class*=top-bar] ul li ul li:first-of-type a {
    border-top-left-radius: 0.5rem;
    border-top-right-radius: 0.5rem;
}
#top-bar div[class*=top-bar] ul li ul li:last-of-type a {
    border-bottom-left-radius: 0.5rem;
    border-bottom-right-radius: 0.5rem;
}
 
#top-bar div[class*=top-bar] ul li ul li,
#top-bar div[class*=top-bar] ul li ul li a {
    background: transparent;
    border: none;
}
#top-bar div[class*=top-bar] ul li ul li a:hover,
#top-bar div[class*=top-bar] ul li ul li a:focus {
    background-color: #FEFBF8;
}
 
/* keyboard navigation compatibility */
#top-bar div[class*=top-bar] ul > li > ul > li > a {
    height: auto;
    max-height: none;
    line-height: 1.5!important;
    padding-top: 0.1rem;
    padding-bottom: 0.1rem;
}
#top-bar div[class*=top-bar] > ul > li > ul {
    visibility: visible;
    opacity: 0;
    pointer-events: none;
}
#top-bar div[class*=top-bar] > ul > li:hover > ul,
#top-bar div[class*=top-bar] > ul > li > ul:hover,
#top-bar div[class*=top-bar] > ul > li:focus-within > ul,
#top-bar div[class*=top-bar] > ul > li > ul:focus-within {
    opacity: 1;
    pointer-events: all;
}
 
/* ---- SIDE BAR ---- */
 
div#side-bar{
    background: #FEFBF8;
    clear: both;
    padding: .8em;
    border: none;
    border-radius: 0;
    box-shadow: 0 0 4px rgba(0,0,0,0.3);
    overflow-x: hidden;
}
 
#side-bar .heading{
    color: var(--headerColor);
    font-family: var(--header-font);
    font-size: 0.94rem;
    border-bottom: solid 1px var(--headerColor);
    border-top: solid 1px var(--headerColor);
    margin-top: 1.35rem;
    padding-left: 0;
    text-align: center;
}
#side-bar .side-block {
    border: transparent;
    border-radius: 0;
    box-shadow: none;
    background-color: #FEFBF8;
}
#side-bar .side-block.media {
    background-color:#FEFBF8;
}
#side-bar .side-block.media > * {
    display: flex;
    justify-content: space-evenly;
}
#side-bar .side-block.resources {
    background-color:#FEFBF8;
}
.side-block .menu-item > .image {
    display: none;
}
 
#side-bar div.menu-item a {
    color: var(--accentColor);
}
 
#top-bar div.open-menu a {
    border-radius: 0.35rem;
    box-shadow: 0 0 4px rgba(0,0,0,0.3);
    color: var(--accentColor);
    background-color: #FEFBF8;
    border: none;
    padding: 0.15rem;
    user-select: none;
}
 
/* ---- MAIN CONTENT ---- */
#main-content {
    background-color: #FEFBF8;
    padding: 0.5em 2em 0.75em;
    box-shadow: 0 0 4px rgba(0,0,0,0.3);
    width: 100%;
    max-width: 880px;
    margin: -0.4rem auto 0;
    border-radius: 0;
    box-sizing: border-box;
}
 
/* ---- PAGE TITLE ---- */
#page-title, .meta-title {
    color: var(--headerColor);
    font-family: var(--header-font);
    font-size: 3em;
    text-align: center;
    display: flex;
    align-items: center;
    text-align: center;
    border-bottom: none;
    margin: 0.25rem 0;
    padding-bottom: 0;
}
#page-title::before,
#page-title::after,
.meta-title::before,
.meta-title::after {
    content: "";
    flex-grow: 1;
    height: 0.25rem;
    margin: auto auto auto 0.65rem;
    background-color: transparent;
    border-top: solid 0.125rem var(--headerColor);
    border-bottom: solid 0.125rem var(--headerColor);
}
#page-title::before,
.meta-title::before {
    margin: auto 0.65rem auto auto;
}
 
/* ---- BREADCRUMBS ---- */
 
#breadcrumbs, #page-content .pseudocrumbs {
    font-size: 0.85rem;
    font-family: var(--header-font);
    margin-top: -1.05em;
}
#page-content .pseudocrumbs * { text-decoration-color: var(--accentColor)!important; }
 
/* ---- TABS ---- */
 
/* ---- YUI TAB BASE ---- */
.yui-navset .yui-nav a,.yui-navset .yui-navset-top .yui-nav a{background-color:inherit;background-image:inherit}.yui-navset .yui-nav a:hover,.yui-navset .yui-nav a:focus{background:inherit;text-decoration:inherit}.yui-navset .yui-nav .selected a,.yui-navset .yui-nav .selected a:focus,.yui-navset .yui-nav .selected a:hover{color:inherit;background:inherit}.yui-navset .yui-nav,.yui-navset .yui-navset-top .yui-nav{border-color:inherit}.yui-navset li{line-height:inherit}
 
/* ---- YUI TAB CUSTOMIZATION ----*/
 
 .yui-navset .yui-nav,
 .yui-navset .yui-navset-top .yui-nav{
     display: flex;
     flex-wrap: wrap;
     width: calc(100% - .125rem);
     margin: 0 auto;
     border-width: 0;
     box-shadow: none;
}
 .yui-navset .yui-nav a, /* ---- Link Modifier ---- */
 .yui-navset .yui-navset-top .yui-nav a{
     color: var(--textColor);
     font-weight: bold;
    /* ---- Tab Background Colour | [UNSELECTED] ---- */
     background-color: transparent;
     border: unset;
     box-shadow: none;
 
     background-image: linear-gradient(to bottom, var(--linkColor) 0%, var(--linkColor) 100%);
     background-size: 0 100% ;
     background-position: 0 100%;
     background-repeat: no-repeat;
     transition: background-size var(--link-timing);
}
 .yui-navset .yui-nav a:hover,
 .yui-navset .yui-nav a:focus{
    /* ---- Tab Background Colour | [HOVER] ---- */
     background-color: transparent;
     background-image: linear-gradient(to bottom, var(--linkColor) 0%, var(--linkColor) 100%);
     background-size: 100% 100% ;
     background-position: 0 100%;
     background-repeat: no-repeat;
     transition: background-size var(--link-timing);
}
 .yui-navset .yui-nav li, /* ---- Listitem Modifier ---- */
 .yui-navset .yui-navset-top .yui-nav li{
     position: relative;
     display: flex;
     flex-grow: 2;
     max-width: 100%;
     margin: 0.25rem;
     padding: 0;
     color: #d6d6d6;
     background-color: var(--primaryBackgroundColor);
     border-color: transparent;
     border-radius: 0.35rem;
     box-shadow: none;
}
 .yui-navset .yui-nav li a,
 .yui-navset-top .yui-nav li a,
 .yui-navset-bottom .yui-nav li a{
     display: flex;
     align-items: center;
     justify-content: center;
     width: 100%;
     border-radius: 0.35rem;
}
 .yui-navset .yui-nav li em{
     border: unset;
}
 .yui-navset .yui-nav a em,
 .yui-navset .yui-navset-top .yui-nav a em{
     padding: .35em .75em;
 
     text-overflow: ellipsis;
     overflow: hidden;
     white-space: nowrap;
}
 .yui-navset .yui-nav .selected, /* ---- Selection Modifier ---- */
 .yui-navset .yui-navset-top .yui-nav .selected{
     flex-grow: 2;
     margin: 0;
     padding: 0;
     border-radius: 0.35rem;
    /* ---- Tab Background Colour | [SELECTED] ---- */
     background-color: var(--accentColor);
     color: var(--primaryBackgroundColor);
}
 .yui-navset .yui-nav .selected a,
 .yui-navset .yui-nav .selected a em{
     border: none;
}
 .yui-navset .yui-nav .selected a{
     width: 100%;
     color: #ffffff;
     font-weight: bold;
}
 .yui-navset .yui-nav .selected a:focus,
 .yui-navset .yui-nav .selected a:active{
     color: #ffffff;
     background-color: var(--accentColor);
}
 .yui-navset .yui-content {
    border: none;
    background-color: transparent;
    box-shadow: none;
    margin-top: 0.25rem;
    box-sizing: border-box;
    border-radius: 1rem;
    padding: 0.35rem 0;
    border-top: solid 0.2rem var(--accentColor);
    border-bottom: solid 0.2rem var(--accentColor);
}
 
/* ---- INFO PANE ---- */
 
:root {
    --linkColor: var(--selectionColor);
    --radius-adjust: 0.325rem;
    --shadow: rgba(0,0,0,0.2);
}
 
#page-content .creditRate{
    margin: unset;
    margin-bottom: 1rem;
}
#page-content .rate-box-with-credit-button {
    background-color: var(--primaryBackgroundColor);
    border: none;
    box-shadow: 0 0 3px 1px var(--shadow);
    border-radius: var(--radius-adjust);
    padding: 0.275rem;
}
#page-content .rate-box-with-credit-button .page-rate-widget-box { border: none; }
 
#page-content a.fa {
    transform: none;
}
#page-content .rate-box-with-credit-button .fa-info {
    border: none;
    color: var(--textColor);
 
    padding-top: 0.25rem;
    padding-bottom: 0.0725rem;
    width: 0.9rem;
    margin-left: -0.1rem;
    margin-right: 0.1rem;
 
    background-image: linear-gradient(to bottom, var(--linkColor) 0%, var(--linkColor) 100%);
    background-size: 0 100% ;
    background-position: 0 100%;
    background-repeat: no-repeat;
    transition: background-size var(--link-timing);
}
 
#page-content .rate-box-with-credit-button .fa-info:hover,
#page-content .rate-box-with-credit-button .fa-info:focus {
    background-size: 100% 100%;
}
 
.rate-box-with-credit-button .cancel {
    border: solid 1px var(--primaryBackgroundColor);
}
 
#page-content .creditButtonStandalone {
    margin: 0.125rem 0;
}
#page-content .creditButtonStandalone p a {
    border-radius: 1rem;
    color: var(--textColor);
    text-align: center;
    background: initial;
    box-shadow: 0 0 2px 1px var(--shadow);
    padding: 0.24rem;
 
    background: none;
    background-image: linear-gradient(to bottom, var(--linkColor) 0%, var(--linkColor) 100%);
    background-position: 0 100%;
    background-repeat: no-repeat;
    background-size: 0 100%;
    transition: background-size var(--link-timing);
}
#page-content .creditButtonStandalone p a:hover,
#page-content .creditButtonStandalone p a:focus {
    text-decoration: none;
    background: none;
    background-image: linear-gradient(to bottom, var(--linkColor) 0%, var(--linkColor) 100%);
    background-position: 0 100%;
    background-repeat: no-repeat;
    background-size: 100% 100%;
}
 
/* ---- PAGE RATING ---- */
 
.page-rate-widget-box {
    box-shadow: none;
    margin: unset;
    margin-bottom: 1rem;
    background-color: var(--primaryBackgroundColor);
    border-radius: var(--radius-adjust);
    box-shadow: 0 0 3px 1px var(--shadow);
    padding: 0.275rem;
}
 
.page-rate-widget-box .rateup a:hover, .page-rate-widget-box .rateup a:focus,
.page-rate-widget-box .ratedown a:hover, .page-rate-widget-box .ratedown a:focus,
.page-rate-widget-box .cancel a:hover, .page-rate-widget-box .cancel a:focus {
    color: var(--textColor);
    background: unset;
    background-image: linear-gradient(to bottom, var(--linkColor) 0%, var(--linkColor) 100%);
    background-size: 100% 100%;
    background-position: 0 100%;
    background-repeat: no-repeat;
    border-radius: 0;
}
 
.page-rate-widget-box .rate-points {
    background-color: var(--primaryBackgroundColor) !important;
    color: var(--textColor) !important;
    border: solid 1px var(--primaryBackgroundColor);
    border-radius: 0;
}
.page-rate-widget-box .rateup,
.page-rate-widget-box .ratedown {
    background-color: var(--primaryBackgroundColor);
    border-top: solid 1px var(--primaryBackgroundColor);
    border-bottom: solid 1px var(--primaryBackgroundColor);
}
 
.page-rate-widget-box .rateup a,
.page-rate-widget-box .ratedown a {
    color: var(--textColor);
    background-image: linear-gradient(to bottom, var(--linkColor) 0%, var(--linkColor) 100%);
    background-size: 0 100%;
    background-position: 0 100%;
    background-repeat: no-repeat;
    transition: background-size var(--link-timing);
}
 
.page-rate-widget-box .cancel {
    background-color: var(--primaryBackgroundColor);
    border: solid 1px var(--primaryBackgroundColor);
    border-radius: 0;
}
 
.page-rate-widget-box .cancel a {
    color: var(--textColor);
    background-image: linear-gradient(to bottom, var(--linkColor) 0%, var(--linkColor) 100%);
    background-size: 0 100%;
    background-position: 0 100%;
    background-repeat: no-repeat;
    transition: background-size var(--link-timing);
}
 
/* ---- PAGE ELEMENTS ---- */
 
h1,
h2,
h3,
h4,
h5,
h6 {
    color: var(--headerColor);
    font-family: var(--header-font);
    font-weight: normal;
    margin: 0.45em 0;
}
h1 { font-size: 2em; }
h2 { font-size: 1.7em; }
h3 { font-size: 1.45em; }
h4 { font-size: 1.25em; }
h5 { font-size: 1.1em; }
h6 { font-size: 1em; }
 
hr {
    height: 0.25rem;
    margin: 1.75rem 0;
    background-color: transparent;
    border-top: solid 0.125rem var(--headerColor);
    border-bottom: solid 0.125rem var(--headerColor);
    clear: both;
}
 
blockquote,
div.blockquote {
    background-color: var(--primaryBackgroundColor);
    border: none;
    border-left: solid 0.2rem var(--headerColor);
    padding: 0.1rem 1rem;
    box-shadow: 0 0 3px rgba(0,0,0,0.25);
    position: relative;
}
blockquote::before, blockquote::after,
div.blockquote::before, div.blockquote::after {
    content: "";
    display: block;
    height: 0.5rem; width: 0.5rem;
    position: absolute;
    left: 0;
    background-color: var(--headerColor);
}
blockquote::before, div.blockquote::before {
    top: 0;
    transform: translate(calc(-50% - 0.1rem),-50%) rotate(45deg);
}
blockquote::after, div.blockquote::after {
    bottom: 0;
    transform: translate(calc(-50% - 0.1rem),50%) rotate(45deg);
}
 
#toc {
    display: block;
    background-color: #FEFBF8;
    border: none;
    padding: 0.1rem 1rem;
    box-shadow: 0 0 4px rgba(0,0,0,0.3);
    border-right: solid 0.2rem var(--headerColor);
    padding: 0.75em;
    position: relative;
}
#toc::before, #toc::after {
    content: "";
    display: block;
    height: 0.5rem; width: 0.5rem;
    position: absolute;
    right: 0;
    background-color: var(--headerColor);
}
#toc::before {
    top: 0;
    transform: translate(calc(0.1rem + 50%),-50%) rotate(45deg);
}
#toc::after {
    bottom: 0;
    transform: translate(calc(0.1rem + 50%),50%) rotate(45deg);
}
#toc-list {
    font-family: var(--header-font);
}
#toc-list > div[style*="margin-left: 1em;"] { margin-left: 0.5em!important; }
#toc-list > div:not([style*="margin-left: 1em;"]) { display: none; }
 
.scp-image-block {
    border: solid 8px var(--primaryBackgroundColor);
    box-shadow: 0px 0px 4px rgba(0,0,0,0.3);
    box-sizing: border-box;
    position: relative;
    z-index: 0;
}
.scp-image-block::before, .scp-image-block::after {
    content:'';
    position: absolute;
    pointer-events: none;
    border: solid 0.25rem var(--headerColor);
    transform: rotate(25deg);
}
.scp-image-block::before {
    right: -0.135rem;
    height: 36px;
    width: 9px;
    top: -14.25px;
    border-radius: 0 0 2rem 2rem;
    border-top: none;
}
.scp-image-block::after {
    top: -25px;
    right: -0.94rem;
    height: 16px;
    width: 14px;
    border-radius: 2rem 2rem 0 0;
    border-bottom: solid 0.55rem transparent;
    z-index: -1;
}
 
.scp-image-block .scp-image-caption {
    background-color: var(--primaryBackgroundColor);
    border-top: solid 4px var(--primaryBackgroundColor);
    color: var(--textColor);
}
.scp-image-block.block-left,
.scp-image-block.block-right {
    margin: 0.25rem 2rem 0.625rem;
}
.scp-image-block.block-left { margin-left: 0.5rem; }
.scp-image-block.block-right { margin-right: 0.5rem; }
@media (max-width: 640px) {
  .scp-image-block.block-left, .scp-image-block.block-right {
    float: none; clear: both; margin-left: auto; margin-right: auto;
  }
}
 
#page-content .wiki-content-table tr th {
    border: solid 1px var(--headerColor);
    color: var(--headerColor);
    background-color: var(--primaryBackgroundColor);
    /* set border for table title */
}
#page-content .wiki-content-table tr td {
    border: solid 1px var(--headerColor);
    /* set border for table content */
}
 
/* fancy collapsible */
#page-content .collapsible-block-folded, #page-content .collapsible-block-unfolded-link {
    background-color: var(--primaryBackgroundColor);
    border-radius: 0.35rem;
    width: min-content;
    white-space: nowrap;
    overflow: hidden;
    margin: auto;
}
 
#page-content .collapsible-block-folded {
    background-image: linear-gradient(to bottom, var(--linkColor) 0%, var(--linkColor) 100%);
    background-size: 0 100% ;
    background-position: 0 100%;
    background-repeat: no-repeat;
    transition: background-size var(--link-timing);
}
#page-content .collapsible-block-folded:hover,
#page-content .collapsible-block-folded:focus-within {
    background-size: 100% 100% ;
    transition: background-size var(--link-timing);
}
#page-content .collapsible-block-unfolded-link {
    background-color: var(--accentColor);
    box-shadow: 0 0 0 0.2rem var(--accentColor);
}
#page-content .collapsible-block-folded, #page-content .collapsible-block-unfolded-link {
    margin-top: 10px;
    margin-bottom: 10px;
}
#page-content .collapsible-block-link {
    display: inline-flex;
    padding: 0.5rem 1rem;
    text-decoration: none;
    color: var(--textColor);
    font-weight: bold;
}
#page-content .collapsible-block-unfolded-link .collapsible-block-link {
    color: var(--primaryBackgroundColor);
}
 
/* Footnotes */
a.footnoteref {
    padding: 0 0.25em 1px;
    margin-left: -0.15em;
}
 
.hovertip {
    font-size: 1.25em;
    background-color: #FEFBF8 !important;
    border: none !important;
    border-left: solid 0.2rem var(--accentColor)!important;
    color: var(--textColor) !important;
    border-radius: 0 1rem;
    box-shadow: 0 0 4px rgba(0,0,0,0.3);
    padding: 0.35rem;
    box-sizing: border-box;
    width: min(24rem, 60vw)!important;
 
    top: initial!important;
    left: initial!important;
    position: fixed! important;
 
    display: block!important;
    bottom: 2rem;
    right: -25rem;
 
    transition: right 0.45s cubic-bezier(.6,.18,.27,.88);
    transition-delay: 0.455s;
    z-index: 29;
}
.hovertip::before {
    content: "";
    display: block;
    height: 0.5rem;
    width: 0.5rem;
    position: absolute;
    left: 0;
    top: 0;
    background-color: var(--accentColor);
    transform: translate(calc(-50% - 0.1rem),-50%) rotate(45deg);
}
div[id$="button-hovertip"] { transition-delay: 0s; }
 
.hovertip[style*="display: block"],
.hovertip:hover {
    z-index: 30;
    right: 1rem;
    transition-delay: 0s;
}
 
.footnote .f-heading {
    font-family: var(--header-font);
}
.footnote .f-footer, .equation .e-footer, .reference .r-footer {
    display: none;
}
 
.footnotes-footer {
    border: none;
    border-left: solid 0.2rem var(--accentColor);
    padding: 0.1rem 1rem 1rem 1.25rem;
    position: relative;
    border-radius: 0 1.25rem;
}
.footnotes-footer::before {
    content: "";
    display: block;
    height: 0.5rem; width: 0.5rem;
    position: absolute;
    left: 0; top: 0;
    background-color: var(--accentColor);
    transform: translate(calc(-50% - 0.1rem),-50%) rotate(45deg);
}
 
.footnotes-footer .title {
    color: var(--textColor);
    font-family: var(--header-font);
    margin: 0 0 0.625rem 0;
}
 
/*-- tags --*/
 
#main-content .page-tags a {
    height: 0.8125rem;
    font-size: 0.6875rem;
    background-color: var(--primaryBackgroundColor);
    color: var(--textColor);
    border-radius: 0.35rem;
    margin: .25rem .2rem;
    padding: 0.21rem 0.35rem 0.22rem 0.3rem;
    box-shadow: 0 0 3px rgba(0,0,0,0.25);
    display: inline-flex;
    align-items: center;
    flex-wrap: nowrap;
 
    background-image: linear-gradient(to bottom, var(--linkColor) 0%, var(--linkColor) 100%);
    background-size: 0 100%;
    background-position: 0 100%;
    background-repeat: no-repeat;
    transition: background-size var(--link-timing);
}
 
#main-content .page-tags a:hover,
#main-content .page-tags a:focus {
    background-size: 100% 100%;
    text-decoration: none;
}
#main-content .page-tags a:before {
    content: "⬤";
    font-size: 4px;
    padding-right: 0.2rem;
    display: inline-block;
}
 
.page-tags span {
    border-top: solid 0.125rem var(--primaryBackgroundColor);
}
 
/* Pop-Up Windows */
.owindow {
    background-color: var(--primaryBackgroundColor);
    border: none;
}
 
.owindow .modal-header {
    background-color: transparent;
}
 
.owindow .modal-body img {
    background-color: transparent !important;
}
 
.owindow .title {
    background-color: transparent;
    color: var(--headerColor);
    border-bottom: 1px solid var(--headerColor);
}
 
.owindow .button-bar a {
    background-color: var(--primaryBackgroundColor);
    border-color: var(--accentColor);
    color: var(--accentColor);
}
.owindow .button-bar a:hover {
    background-color: var(--accentColor);
    color: var(--primaryBackgroundColor);
}
 
#page-content .modalbox {
    background: #FEFBF8;
    border: none;
    border-radius: 0;
    box-shadow: 0 0 10px rgba(0,0,0,0.35);
}
#page-content .modalbox hr { margin: 0.75rem 1rem; }
 
/* Edit Buttons */
.buttons .btn {
    background-color: var(--primaryBackgroundColor);
    border-color: var(--accentColor);
    color: var(--accentColor);
    padding: 3px 5px;
}
.buttons .btn:hover {
    background-color: var(--accentColor);
    color: var(--primaryBackgroundColor);
}
 
/* Close Button for Page Source, Rating, Etc */
a.action-area-close:hover {
    background-color: var(--accentColor);
    color: var(--primaryBackgroundColor);
}
 
/* Page-History Current */
.pager .current {
    background-color: var(--accentColor);
    border-color: var(--primaryBackgroundColor);
}
 
/* ---- CUSTOM SYNTAX ----*/
 
#page-content .section-header {
    display: flex;
    align-items: center;
    text-align: center;
    margin-top: 3.5rem;
    margin-bottom: 0.75rem;
    clear: both;
}
#page-content .breaker + .section-header {
    margin-top: 1.5rem;
}
.section-header::before, .section-header::after {
    content: "";
    flex-grow: 1;
    height: 0.175rem;
    margin: auto -0.625rem auto auto;
    background-color: var(--primaryBackgroundColor);
}
.section-header::after {
    margin: auto auto auto -0.625rem;
}
 
.section-header h1 {
    width: max-content;
    margin: 0 auto;
    text-align: center;
    padding: 0.05rem 1.5rem;
    border-radius: 0rem 0.875rem;
    border-bottom: solid 0.2rem var(--accentColor);
    border-top: solid 0.2rem var(--accentColor);
    position: relative;
}
.section-header h1::before {
    content: "";
    background-color: var(--accentColor);
    display: block;
    width: 0.6rem; height: 0.6rem;
    position: absolute;
    top: 0;
    left: 0;
    transform: translate(-0.3rem, -0.4rem) rotate(45deg);
}
.section-header h1::after {
    content: "";
    background-color: var(--accentColor);
    display: block;
    width: 0.6rem; height: 0.6rem;
    position: absolute;
    bottom: 0;
    right: 0;
    transform: translate(0.3rem, 0.4rem) rotate(45deg) ;
}
.section-header h1 span {
    width: max-content;
    margin: auto;
}
 
/*-----------------*/
 
.s-title {
    font-size: 110%;
    font-weight: bold;
    display: inline;
    padding: 0 0.15em;
    padding-bottom: 0.1em;
    border-bottom: solid 0.1rem currentColor;
    border-top: solid 0.1rem currentColor;
}
 
.gallery-frame {
    box-sizing: border-box;
    background-color: #FFF4E9;
    padding: 0.75rem;
    border: inset 0.325rem var(--headerColor);
    box-shadow: inset 0 0 5px rgba(0,0,0,0.4);
    margin: auto;
}
.gallery-frame > img { box-shadow: 0 0 3px 1px rgba(0,0,0,0.3); }
 
.hover:hover {
    text-decoration: none;
}
.hover span { display: none; }
.hover:hover span {
    position: absolute;
    display: inline;
    height: auto;
    max-width: 25%;
    background-color: var(--headerColor);
    color: #FEFBF8;
    font-weight: bold;
    padding: 0.5em 1.5em;
    border-bottom-right-radius: 1rem;
}
 
.f-flex {
    display: flex;
    flex-wrap: wrap;
    justify-content: space-evenly;
}
.f-flex > div {
    flex-basis: 18rem;
    flex-grow: 1;
}
.f-flex.three > div {
    flex-basis: 13rem;
    flex-grow: 1;
}
.f-flex.data > div {
    padding: 0.65rem 0.375rem;
}
.f-flex.data > div:hover {
    z-index: 9;
}
 
.f-con {
    border: none;
    padding: 0.15rem 0.75rem;
    margin: 0.85rem;
    position: relative;
    border-radius: 0 1.25rem;
    background-color: #FFF4E9;
    box-shadow: 0 0 4px rgba(0,0,0,0.3);
}
#page-content .f-flex .f-con { max-width: 25rem; }
.f-con h4 {
    background-color: var(--headerColor);
    color: #FEFBF8;
    padding: 0.1rem 0;
    border-radius: 0 0.625rem;
}
 
.placard {
    display: inline-block;
    position: relative;
    padding: 0.45rem 0.65rem;
    margin: -1.05rem -0.5rem -1.3rem;
    border: solid 1em transparent;
    background: var(--primaryBackgroundColor) padding-box;
    clip-path: polygon(0 3em, 3em 0, 100%  0, 100% calc(100% - 3em), calc(100% - 3em) 100%, 0 100%);
    filter: drop-shadow(0 1px 2px rgba(0,0,0,0.25));
}
.placard::before, .placard::after {
    position: absolute;
    width: 3em;
    height: .35em;
    background: radial-gradient(at 50% 0, rgba(0,0,0,0.17), rgba(0,0,0,0) 65%);
    content: "";
}
.placard::before {
    top: 0.45em;
    left: -0.95em;
    transform: rotate(-45deg);
}
.placard::after {
    bottom: 0.45em;
    right: -0.95em;
    transform: rotate(135deg);
}
 
/*---- Side ToC setup ----*/
 
.anchor {
    position: sticky;
    height:0;
    top: 0.5rem;
    z-index: 4;
}
.tocbox {
    margin-top: 0;
    position: absolute;
    top: 0;
    right: max(-18.75rem, -17vw);
    z-index: 4;
    box-sizing: border-box;
    width: max-content;
    pointer-events: none;
}
 
#page-content .tocbox .toc-u {
    padding: 0.5rem;
    background-color: #FEFBF8;
    box-shadow: 0 0 4px rgba(0,0,0,0.3);
    border-right: solid 0.2rem var(--headerColor);
    position: relative;
    width: 15rem;
    max-height: calc(98vh - 2rem);
    max-width: calc((30vw - 50% - 6rem)/1.2);
    margin-right: 0; margin-left: auto;
    pointer-events: all;
}
.toc-u #toc::before, .toc-u #toc::after { display: none; }
.toc-u::before, .toc-u::after {
    content: "";
    display: block;
    height: 0.5rem; width: 0.5rem;
    position: absolute;
    right: 0;
    background-color: var(--headerColor);
}
.toc-u::before {
    top: 0;
    transform: translate(calc(0.1rem + 50%),-50%) rotate(45deg);
}
.toc-u::after {
    bottom: 0;
    transform: translate(calc(0.1rem + 50%),50%) rotate(45deg);
}
 
#page-content .tocbox .toc-u #toc-list {
    overflow-y: auto;
    overflow-x: hidden;
    max-height: 84vh;
    padding: 0 0.5em 1em;
    scrollbar-width: thin;
}
#page-content .tocbox .toc-u #toc-list::-webkit-scrollbar {
    width: 6px;
}
 
.tocbox table,
.tocbox tbody,
.tocbox tr,
.tocbox td,
.tocbox #toc {
    display: contents;
}
 
#toc-list > div { position: relative; }
#toc-list > div[style*="1em"]::before {
    content: "•";
    display: inline-block;
    position: absolute;
    left: -0.75em;
    color: var(--accentColor);
}
 
@media (max-width: 1340px) {
    .anchor {
        filter: none;
        transition: filter 0.2s ease-out;
     }
    .tocbox {
        right: -1rem;
        width: unset;
    }
    .tocbox::before {
        content: "";
        display: block;
        position: absolute;
        background-color: transparent;
        width: 1.5rem; height: 100%;
        top: 0; right: -0.25rem;
        pointer-events: all;
}
    .tocbox::after {
        content: "";
        display: block;
        position: absolute;
        background-color: transparent;
 
        width: 0; height: 0;
        border: solid 1rem transparent;
        border-left-width: 0.5rem;
        border-right-color: var(--headerColor);
 
        top: calc(50% - 1rem); right: 0;
        pointer-events: all;
        transition: border-right-width 0.15s ease-out;
    }
    #page-content .tocbox .toc-u {
        width: -moz-fit-content;
        width: fit-content;
        max-width: 60vw;
        box-shadow: none;
        clip-path: inset(-0.5rem -0.5rem -0.5rem calc(100% - 0.65rem));
        transition: clip-path 0.2s ease-out;
        pointer-events: none;
    }
 
    .anchor:hover { filter: drop-shadow(0px 0px 3px rgba(0,0,0,0.2)); }
    .tocbox:hover {
        pointer-events: all;
    }
    .tocbox:hover::after {
        border-right-width: 0;
    }
    #page-content .tocbox:hover .toc-u {
        pointer-events: all;
        clip-path: inset(-0.5rem -0.5rem -0.5rem -0.35rem);
    }
}
 
/* ---- FOOTER & LICENSE AREA ---- */
 
#footer, #license-area {
    background-color: #FFF4E9;
    color: var(--textColor);
}
#footer a { color: var(--accentColor); }
 
#footer {
    padding-top: 1rem;
}
#license-area {
    padding-top: 0;
}
 
/* ---- INTERWIKI ---- */
 
.scpnet-interwiki-frame{
    filter: invert(100%) grayscale(100%) contrast(75%);
}
 
/* ---- MOBiLE QUERY ---- */
@media (max-width: 767px) {
 
    div#header, div#top-bar {
        width: 100%;
        max-width: 100%;
    }
 
    #login-status {
        padding-top: 0rem;
        padding-left: 0.3rem;
    }
    #login-status span.printuser  {
        font-size: 0;
    }
    #login-status span.printuser img {
        font-size: 0;
        transform: translate(6px, 5px);
    }
    #login-status a#my-account {
        display: none;
    }
 
    #main-content {
        padding: 0.5em 1.75em 0.75em;
    }
    #side-bar .close-menu {
        opacity: 0;
        margin-left: 18.75em;
    }
    #side-bar:target .close-menu:hover {
        background: unset;
    }
 
    :root {
        --header-title: "SCPF News";
    }
 
    #page-title, .meta-title { font-size: 2.4em; }
    h1 { font-size: 1.8em; }
    h2 { font-size: 1.5em; }
    h3 { font-size: 1.25em; }
    h4 { font-size: 1.05em; }
    h5 { font-size: 0.9em; }
    h6 { font-size: 0.8em; }
}

DISCLAIMER: This is the Site News for the English Branch of the SCP Wiki. The opinions of the individual members of the Site News team that are presented in each edition of the Site News are their own thoughts and are not meant to be representative of the Site News team as a whole nor are they representative of the staff body as a whole. If you take issue with any of the contents, then feel free to reach out to the editor(s) and they will review the contents to see if there are any edits that need to be made. We intend to always deliver interesting content to you, and we understand that there may be times where controversial or unpopular opinions will be presented whether by our writers or our editor(s). Thank you for your understanding!

Table of Contents

Editorial

Upon reading the August edition of the Site News, you will catch onto a trend that has been occurring throughout the month. This trend is an uptick in short articles. Is this a sign of a Series I renaissance? Is it a rebellion from the status quo of longer articles that has developed over the years? Is this the future direction of the SCP Wiki?

The early days of the SCP project witnessed a vast majority of shorter articles over longer ones. Part of it was due to being modeled after the original SCP-173, part of it was simply the culture of the time believing that an SCP had to be short, and part of it was simply a lack of connectivity and world-building that would not be established for years to come. As the SCP project found its footing, more and more themes and narratives found their place and began to flourish within an increasing number of articles. With the addition of these new stories and tools to work with, writers went on to incorporate this "lore" into their own articles and further fuel their own narratives. Does this mean that SCP was on a collision course for a unified canon? I wouldn't go that far. We have always established a clear sentiment that there is no canon, but that doesn't mean that stories and this universe we have created do not end up intersecting in interesting and unique ways. Regardless of the way you see it, this movement of bringing narratives together has in general increased the average length of works on the site. There have always been new short articles, however, but over the years we have seen a number of long articles with fascinating stories that would not typically be accepted if we were still in the days of Series I. It is certainly for the better that we now have this diversity in methods of story-telling and word count. The possibilities nowadays are almost endless.

So, is this some grand movement to return to the old days? Nah, that would be a travesty. But while we have this little reminiscent burst of this style of articles, treat yourself to a nice short read and cup of tea on me.

- By WhiteGuard

SCP News

Artwork by Seraphannim

Site News

Daveyoufool Opens Up

In the newest edition of the Interviewing Icons series, WhiteGuard and Elenee Fishtruck interview the man who could easily be called the SCP Wiki's Comedy King - daveyoufool. In the interview, dave goes over many different subjects, from his first outings as an author, The Three Moons Initiative, how the wiki helped shape his writing, and most importantly his new book which has been in the works for nearly 5 years now!

The Shorter, The Sweeter

Early in August, one Yossipossi sat and wondered, "we have all of these new users coming into the site and saying that everything we have in the new series is long and convoluted when that really isn't the case. What can we do to help show them short, sweet stuff?" A new page was made, the shortest pages this month, and hopefully this will help show people that short stuff is constantly being made. Whether intentionally, by accident, or just as sheer coincidence, the amount of shorter articles in the past month has significantly grown. Having so much more short reads and having them all organized neatly on one page has certainly helped the "pick up and read" experience many people needed right now.

Offsite News

Wanderer's Library: Wandercon 2021

The Wanderer's Library is hosting it's first team contest! Participants have organized themselves into teams and been tasked with writing the collected stories of one of the countless authors whose tomes are enshrined in the Library. Teams came up with patafictional authors, monster hunters, and gonzo journalists to characterize through their writing.

Mass Recognition of the Bodies in the Water

At the start of the month, Markiplier uploaded a short video to his Tik-Tok account referencing djKaktus's SCP-2316. The skit was probably just meant to be a quick, funny reference, but ended up garnering over 25 million views in a few days and inadvertently launched an avalanche of online publicity for the article. Thousands of videos and dozens of news articles were made in response to the trend, most of which unfortunately failed to name anyone involved in the article's creative process. Fortunately, some publishings retroactively added names into their articles, and many authors started adding info modules to their articles to help combat this problem in the future.

International News


Italian Branch's Summer 2021 Contest!

From Siddartha Alonne over at -IT: "Sun, mountains, beaches and containment cells". In this contest, participants had to choose a summer location and write a work having that place as a protagonist. Mountains, beaches, even other countries! The contest ended, here is the Top 3:

🥇 First Place: SCP-121-IT "Anomalous Turin" by Lo_Dev — The old capital holds a great secret about its own spirit.

🥈 Second Place: Summer Flowers by QuantumCryptographer — Sequel tale of SCP-101-IT "Imaginary Friend" by the same author, starring the happy ending of a neutralized anomaly.

🥉 Third Place: SCP-069-IT "The Exodus" by Dr Placido and Siddartha Alonne — Reality-bending axolotls seeking their God, hunted by an old and known enemy of the deity.

Czech Branch's First 001 Proposal!

From Kubik over at -CS: Two years passed since the Czech Branch became an official branch of the SCP Foundation, and just recently the user Steven Choros wrote the first SCP-001-CS "A Gift for Maria", set in the early days of the Foundation.

Czech Branch's First Crackfiction Contest!

News from -CS doesn't end here this month! The theme is, well… MMP-Class "Woofing Of The Worlds" Scenario. Yeah, they get serious when it gets to shitposting. More info here!

Featured Content

Top Articles of the Month

Ratings of course do not mean everything, but they are representative of what people happened to like seeing at the time. With this in mind, the following are the top-rated works of the month, so if by some chance you haven't encountered them yet, be sure to check them out!

Top-Rated SCP

SCP-6336: Seeing Myself Blink — by Lamentte.

  • SCP-6336 is the reflection of Researcher Jackson Colroy.

Top-Rated Non-SCP

👉👉👉eddybird art page or sth👉👉 — by eddybird.

  • 👉👉👉👉👉.

Front Page Features

Every month, an article is selected from each of the three common article types: SCP, Tale, and Group of Interest Format. These three articles are displayed on the front page for the month to bring further recognition to them.

If you would like to view the previous front page features, you can view the archive for the SCPs here, the archive for the Tales here, and the archive for the GoI Formats here!

SCP Article

SCP-5170: Pattern Screamer, Esq. 💼⚖️— by Amytato [featured by DianaBerry and Fireknight].

  • "UNITED STATES OF AMERICA v. Certain Electronic Documents Relating to 'SCP-5170', And All Iterations and Derivations Thereof"

Tale

Tales From Asheville Vol.1 - Camille & Hershey — by Marcelles_Raynes [featured by Zyn and Phantom8].

  • "Hershey sighed as he tripped over another charred skeleton."

GoI-Format

LaRue Post - Willie's shine — by Vivarium [featured by DianaBerry and Fireknight].

  • Come and get it y'all, its the best shine in La Rue!

Underread & Underrated

Underread and Underrated is a project intended to shine a spotlight on, well, underread and underrated pages! As part of the associated UaU initiative, each month an element of SCP lore will be picked that people outside the general gestalt might not know about. Additionally, writing challenges will be hosted involving said lore!

For more information including the topic and prompt for each month, check out the actual Underread and Underrated page here!

Featured SCP

SCP-5332: Remains of the Elder — by Dr Moned.

  • Storage: The cargo to be stowed in the hold, in a large standard crate with a sheepskin padded interior, and secured to the floor hull by rope.

Featured Non-SCP

The Definition of Madness — by ROUNDERHOUSE.

  • He was cracking open the second beer when he heard the voice.

Reviewers' Spotlights

Works are featured on the site’s front page as part of the Reviewers’ Spotlight, which acknowledges the time and effort spent by forum reviewers helping other authors develop and edit and their works for the mainsite. Each month, community members are encouraged to nominate forum reviewers who have been both particularly helpful and active. Members of the Forum Criticism Team will then discuss the nominations, and select four prominent reviewers to choose the month’s Reviewers’ Spotlight front-page features.

If you would like to view previous spotlights, you can view the archive for them here!

1st of July

SCP-726-EX - The Dowsing Rod — by Uncle Nicolini [featured by Uncle Nicolini].

  • The object was allegedly capable of detecting anomalies, but has since been labelled non-anomalous and reclassified as Explained.

9th of July

SCP-5484 - Hellevator — by Ralliston and BlazingPie [featured by fabledtiefling].

  • SCP-5484 is to be sealed off from the remainder of Site-120's building..

17th of July

SCP-5117 - Alex? I'm Lonely — by Greyve [featured by Jack Waltz].

  • SCP-5117 is a pair of matching rose gold wedding bands.

25th of July

SCP-6044 - A ‘Helpful’ Forest, A Giant Sponge and A Lot of Axolotls — by OzzyLizard [featured by FireKnight].

  • These objects nearly always correlate with a recent, heavily radio broadcast tragedy or major world event.

Writer's Column

The Riemann Conjecture

//Olber’s Paradox //

There are a couple of immutable truths in the universe. That it’s static, infinitely old, and that the night sky is full of so many stars that’s infinitely bright and it fucking burns my retinas. Stars everywhere. An incredibly dense wall of light with endless rays subtended by endless angles. You open your mouth to scream but it’s also full of stars.

This is known as Olber’s Paradox, and was one of the first hints that the universe was more complicated than we gave it credit for. With the dawn of the Copernican model1 and Newtonian gravity, we found ourselves dealing with two fundamental questions.

The first was that if the earth was not the center of the universe, what was? Was there even a center? And more pressingly, Newtonian mechanics required an infinite and homogenous universe so as not to collapse under its own weight. So how many stars were there? And how bright should the night sky be? Let’s consider a spherical shell of thickness dr, homogenous star number density n, and radius r. For simplicity, we’re going to assume all stars have the same radius as our sun - $r^{2}_{\odot}~=~7~\times~10^8~m~$.

This would give us $4 \pi r^{2} dr n~$ stars in this shell, where each would cover fraction $\pi r^{2}_{\odot} dr n~$ of the night sky. So! For a section of the sky roughly the size of the sun (from our point of view!), we can look at $\pi r^{2}_{\odot} R n~$ and find R such that this fraction is equal to 1.

Now, you may notice that this fraction goes linearly with R. And that R, the radius that we’re integrating out to, is infinity.

Obviously that’s kind of a problem. Stars will definitely occlude other stars, so a cylindrical cross section would be a more accurate integral, but this is a writing website and not a maths class. So I think it’s suffice to say that any nonzero stellar density will result in this section of the sky being entirely full of stars from our eyes. The entirety of the night sky is about 180,000 times larger than that singular patch, so naturally the night sky is 180,000 times more intense than sunlight.

Wait. Shit.

Ok, ok. What if the stars are just arranged in a pattern where they’re all hiding behind the ones we can see? What, that’s weird and disquieting? Uh, ok, ok. What if there was some interstellar medium that was absorbing the light? Yeah! Yeah, ok. Ok. So there’s some interstellar medium, let’s say dust2. And it’s absorbing 180,000 times the energy of the sun at any given moment. Hold on, I’m getting a call from my thermodynamicist.

Ok - she’s telling me that there’s no material that can infinitely absorb energy and that it would start diffusing energy once it’s reached thermal equilibrium.

So… Where do we go from here? We all live in an era where things like the Big Bang (thanks Penzias and Wilson!) and the accelerating expansion of the universe (thanks Riess and Perlmutter!) are commonplace and widely accepted. But this wasn’t always the case, and I think the fact that it took us till the early 20th century to properly dissuade ourselves of the notion speaks to how deep the belief in a static and infinite universe ran. But thanks to the efforts of cosmologists and astronomers like Einstein, Friedmann, Walker, Robertson, Lemaitre, Hubble, and others, we now know the resolution to Olber’s Paradox. The night sky is not infinitely bright because the universe is young. Modern stars and galaxies formed 1-10 Gigayears after the Big Bang3. And the universe is not endlessly irradiated because of its expansion - leftover radiation from the Big Bang has been redshifted into the microwave band.

Until relatively recently, cosmology has relied on four key assumptions:

1. The laws of physics apply at all points.
2. The universe is homogenous.
3. The universe is static.
4. The universe is infinite.

Olber's paradox is only resolved because we now know that the last two assumptions are not true. And that's what makes Olber's so interesting. The universe is so much smaller but so much more interesting than we had ever thought it would be, and if it wasn't, well, I wouldn't have banged my dang knee the other night cause it was so dark. Because, as we all know, the night sky is full of stars.

Next month: Riemann gives uncontroversial takes on Author Avatars

- By Riemann


Captain's Log: Date 002

Comedy 101: A Probability and Statistics Course

In theme with my fellow columnist completely disregarding our target demographic to write about cosmology, I decided I'd one up him: I'll write about something nobody cares about on a writing site (math) and also something I have no qualification for (being funny). I do feel like I have to take this approach though, since humor is generally considered such a flippant and nebulous genre to write. The rules of comedy has always been:

1. If they laugh, you've done it right
2. There is no second rule

So, instead of talking about what goes into making an individual joke land, I want to take a look at how jokes and comedy manifest in SCP articles specifically. Be it a -J or a funny mainlister, SCP humor has to find a way to make a reader laugh (or at least smirk) within the confines of the format.4 Approaches to the "funny SCP" challenge are incredibly diverse, so it's difficult to make broad sweeping remarks, or try to categorize them all. So, instead of using hand-wavey, poorly defined terms like "stinger" and "tone", how about we talk about comedy in certain terms. Let's use some math.

I want to start by defining some measurements you can make in a comedic article:

  1. Length (L): It's literally just word count. It's always some non-negative integer.
  2. Joke Count (Jc): The number of moments in the article where the reader is supposed to laugh. Also always a non-negative integer.
  3. Joke Intensity (Ji): How funny any individual "Joke Moment" is supposed to be5. If you're an economist you can quantify this as utility? I think?
  4. Joke Success Rate (P(J)): How likely any single joke is to land. It's just a probability so it'll always be some number between zero and one.

Now that we've defined these terms, we can use them to calculate things!6 We'll start with something that I think can be used to characterize comedic articles, and might even be a useful measure meant for your own joke articles! It's called Joke Density (Jd).

(1)
\begin{align} J_d = \frac{J_c}{L} \end{align}

It's the frequency of jokes in an article. Knowing that an article has only 1 joke or 10 jokes means something, but that changes if there's 1 joke in a 100 word article or 10 jokes in a 5000 word article.

Which now brings me to a joke-to-joke value we can calculate: Expected Joke Intensity (E[Ji]). On its face, any individual joke for any single reader has one of two values: its joke intensity, or zero. It either lands, or it doesn't7. However, we can use the expected value of a joke's intensity to estimate, on average, how funny it will be for any given reader. Luckily, expected value is pretty easy to calculate here:

(2)
\begin{align} E[J_i] = J_i\times P(J) \end{align}

Now, preferably we want to maximize $E[J_i]$ for every joke in our article, but that's rarely the case. However, given that we can't necessarily always do this, we can see that different types of jokes can have similar $E[J_i]$. For example, a joke that requires some obscure knowledge, but lands hard for its target audience could score the same as a more accessible joke that causes an exhale rather than a guffaw.

$E[J_i]$ is a useful value for talking about individual jokes, but how do we turn this into a measurement of an entire article? We would want to combine all of these values together. Now, the solution here seems obvious… you just add them together. Usually in probability, you don't just get to add probabilities together, but expected values abide by Linearity of Expectation8. So, if we defined all of the jokes in an article $A$ as the set $A_J$, then we can define Expected Article Humor (E[A]) as:

(3)
\begin{align} E[A] = \sum_{J \in A_J} E[J_i] \end{align}

This tells us now how funny our article is in its entirety (in expectation)! Its a way to homogenize how articles with high quantities of jokes can sometimes equal a single high quality joke. But instead of looking at articles in some sort of monolithic categories, we now have a continuous measurement of how effective a comedy article is! We can compare rapid fire and shaggy dog, anecdote with knock knock. All humor bows before our numbers!

Except, we are still missing one last aspect, which we briefly mentioned before: time. See, people want to feel rewarded for their time investment in reading your article. So let's round this off with one final value: Expected Laughter Frequency Per Article (E[L_t]):

(4)
\begin{equation} E[L_t] = E[A]/L \end{equation}

And now, we have done it. A measurement to unify all humor articles. How much laughter you will get out of how much time investment. We can optimize all of our comedy, apply a minimum expected laughter frequency threshold, GATE KEEP HARDER.

Except well, there's the obvious issue that everyone probably pointed out at the very beginning: you can't really put numbers to like, most of this.

Yeah, humor is subjective. But making sure you as a writer know what makes this worth reading to you is important. Do I have a high joke density with medium payoffs? Or am I promising my reader the funniest punchline they've ever seen after 2000 words? Or maybe I just want to have the whole essence of the article be funny without any big set up, and let little consistent moments of humor bring the reader along? If you follow the steps above, and believe you're executing on these all correctly, they should come out to a similar $E[L_t]$.

Which brings me back to the first rule of comedy. "iI they laugh, you've done it right". If you go through these steps, and end up with a high enough value that you're happy with, that means at least one person should probably be laughing at your article. It's not like there's a correct way to go about writing humor, in the first place. All the different methods you'll see on the site have a chance at scoring highly on our silly little scale. But when you're writing, you only have your guts to go off. This brings me to my proposed amendment to the first rule of comedy. Captain Kirby's new decree from on high. All writers who break this rule shall be stripped of their comedy license:

1. If you laugh, you've done it right
2. There is no second rule

- By CaptainKirby

Rounder Table


Prompts from your favorite house, thoughts from your favorite authors - all about the genre of SCP writing!

Prompt: What makes an effective critique comment?

Doing critique on the SCP wiki is unlike most other forms of feedback, and each form of critique on the wiki is unlike the others. When doing critique on ideas or drafts, you are helping the author form and build their concept into something that could be posted publicly and, as a result, you are sharing your own techniques or ideas for them to consider and build on their own. However, when doing critique in a comment on a posted work, the skillset is very different. Instead of giving advice on how to build the article from the ground up, you are looking at the work set in front of you and figuring out where it works for you and what the author could do to specifically earn your vote.

To do this, it is important to keep two things in mind: 1) is this a flaw or is it just not written by me and 2) what would I like to have seen in this article? The first one is an important thing to consider because many commenters can confuse articles that do something different than a typical article with being a bad article, and recognizing this can turn complaining about the article into constructive critique. For example, saying “This format is garbage” helps nobody while “the formatting of this article makes it annoying to read or difficult to understand” is a flaw that the author could choose to address. And the second is important for framing a critique as an actual critique. Instead of just listing things you don’t like, it is more helpful to list what you would have specifically liked to see. Listing only problems often leads to solutions you don’t want and don’t help anyone.

- By Pedagon

Critique on posted works is fundamentally different from critique on drafts - in the drafting stage you're giving live input onto the draft as it forms and takes shape and grows. A draft is a sketch; a posted article is the painting hanging in the gallery. The way you approach critiquing a sketch and a portrait is the gulf of difference we're talking about here.

In the draft stage, radically reworking an entire premise is a practical, if oft-unwanted solution to outstanding issues. When dealing with an article completed and posted to the mainlist, suggesting that people write an entirely different article isn't practical at all. Critique on posted works needs to be practically actionable. You can suggest changes in structure and style but the key thing to keep in mind is that your suggestions - and you should make suggestions, because critique without suggestions to go on isn't very helpful at all - should be addressing and amending the issues with pacing/characterization/whatever, not attempting to fundamentally change the basis of the story.

Obviously there are exceptions to this, no one critique fits all, but it's a good thing to keep in mind. That you need to provide suggestions and a direction for the critique to be applied in. Pointing out flaws in articles is incredibly easy - presenting how to shift those issues and fix them is the mark of good critique.

- By Alan Smithee

When it comes to "good critique" there's no one size fits all answer, as it's so heavily dependent on what you're critiquing. That said, there are some things that I've seen in my experience that stand out as the most effective. One of the main things I try to do where possible is find something that I like about the author's idea/work or point out what they do right. Letting them know "hey, this part is good and I want to see more of that" is fundamental to letting them know what to build off of.

The second thing is to just explain yourself. If you don't like something, explain why that is. Was the story too slow? Were the characters not well constructed? Let the author know these things, because simply saying "I didn't like this" or "This sucked" doesn't actually tell the author where to improve. When in doubt, over explain yourself a bit.

- By fabledtiefling

Artist's Shoutout

~ Wendipeligo ~

Twitter
Instagram
Amino
SCP-173 - The Sculpture - The Original173_wendipeligo.jpg

Wendipeligo, also known as Clay, is an American artist who started on Amino. They take great joy in drawing the Foundation's creepy creatures (but mostly the cats). They also tend to take a lot of creative liberties with SCP designs, leading to some interesting products.

Now, you started drawing SCP work on Amino, and have since branched out to platforms like Twitter. How did you start drawing in general and for the SCP Wiki?

Art has been something I've had great interest in since before I can even remember. I grew up with a family that highly encouraged my art, and always supported it, no matter what I drew. I had a lot of great role models and friends within the artist community that inspired me greatly to draw and improve my artwork, and it lead to me exploring different aspects and styles of artwork; especially when it came to more taboo/horror themes. SCP came into my life at a super crucial turning point for my art, and has been such a big factor in a lot of what I create to this day. My SCP artworks are some of the most consistently up-kept themes, to the point that I now use certain pieces to gauge how far my skills as an artist have evolved by redrawing recurring pieces almost yearly :)

That's awesome you have such support, and your progress certainly shows. If I may cite a specific piece, your SCP-173 redesign artwork, what inspired you to work on this piece and what was your process making it/your artistic process in general?

My SCP-173 work is definitely one of my most out there designs, especially when it comes to SCPs that have an already generally agreed upon appearance. It's actually one I tend to avoid due to its popularity, as most designs follow the original article image pretty faithfully. However, I drew some inspiration from the sculptor Bruno Catalano, who's sculptures tend to be missing substantial parts, and yet can still stand freely. I wanted to implement a bit of their work, as well as that classic marble sculptor feel, just with a bit of modern day elements mixed in, thus the rebar that now runs its course through the entirety of SCP-173. The piece itself actually took several months to be finished, as while I enjoyed the original sketch and was happy with the design, I hit a bit of an art rut where I wasn't entirely happy with what I was producing. And so, SCP-173 became a highly experimental piece, simply finished in a way that brought me joy, leaving lots of room for error and improvement, and, of course, some fun colors.

My general artistic process is total chaos, start to finish. The moment I have an idea in my head for a piece, I usually try to take my time to get down a sketch of it before I forget; however, when it comes to works that I'm genuinely excited to work on, I do tend to be a bit impatient and skip the planning process entirely, going straight in for lineart/colors. It definitely plays a big factor in how long it can take to finish, as some works can be anywhere between 2-3 hours all the way up to 10+ hours, excluding any breaks I may take in between. I've got a couple sitting around that higher marker that still aren't even a quarter of the way finished. Typically I can get a few pieces down in a day if I sit down with some music on, but my art styles are all so varied that each piece is a bit difficult to prepare for, but definitely keeps me entertained as I never know what might inspire my work that day.

I can sympathize with that notion of chaos. With that in mind, how has your style (or styles) developed into its current form, and how do you think it'll develop moving forward?

My style used to be very… nit-picky, I suppose I would describe it? I would spend a LOT of time striving for perfection, searching for ways to make sure it looked as clean as humanely possible, and as pleasing to the eye as can be. However, over the years, I've learned to loosen up on my art a ton, and it has definitely changed my artwork for the better by making things far less stressful and focusing on what I love doing, versus striving for a perfection that will only turn art into a chore. I hope to continue to improve, while still teaching myself to let go of perfection, and implement more of what I personally enjoy as an artist :)

With the styles you've developed, which artists inspire you, both off and potentially on the wiki?

So many! I definitely find a lot of inspiration in the artwork of my acquaintances, both on and off the wiki. UncertaintyCrossing and Sebarus are always super inspiring, whether they realize it or not. I also find a lot of inspiration in artists like xianta, who I don't believe to be on the wiki, but they share a lot of wonderful art on their tiktok and their tutorials are honestly a godsend in learning grayscale painting. There are so many wonderful, talented artists out there that I honestly wish I could list them all, as even in passing glances, I learn new techniques and different little art quirks from artists that might never know the type of impact they have on the art of others.

SCP-049 - Plague Doctor049_wendipeligo.jpgSCP-860 - Blue Key860_wendipeligo.jpg

SCP-939 - With Many Voices
939_wendipeligo.jpg

Onsite Art this Month

Interview of the Month

July spotlight: SCP-6336 - Seeing Myself Blink

Featuring: Lamentte
Interviewer: Elenee FishTruck

Interview

Heya, Lamentte! I want to discuss your most recent article, SCP-6336, currently your highest rated article and one of the few SCPs on the entire wiki to reach +100 within 24 hours. A major achievement! But first, some background: You posted your first article nearly three years ago, but you've made no small impact since then, your highest-rated skip before SCP-6336 reaching +255. How have you developed as a writer on the SCP Wiki from your beginnings up to now?

I feel generally my experience on the SCP Wiki has really helped me grasp a lot of writing concepts over the years, even if that growth is somewhat subconscious. I feel looking back that I have most grown my ability to see each individual element of a story/writing and be able to figure out what's working and what's not working to forward the narrative, which is something that's even more important on a site that's whole deal most of the time is a concise tone.

Concise is correct! Now, while you posted SCP-6336 recently, you've worked on this idea for a while, to my understanding. Where did the concept for SCP-6336 originate, and how did it develop from conception to completion?

I'm not entirely sure where the concept originated, actually, but I know that the base idea was in my head for a long while (that being like, "reflection does a bad job and then gets arrested") before I wrote the initial draft of it. The first draft was meant to be the shorted non-format screw scp, which I succeed in at the time, but I quickly realized that it may be too short in that state. So I did what any normal person would do: left in my sandbox untouched for 5 months! After that, I abandoned the restriction of "THE shortest" and beefed it up a little and polished it around the edges. I showed people it, people liked it, then I posted it and people REALLY liked it. I very much regret letting it sit in my sandbox for almost half a year now, haha.

Well, at least people have taken to it now. When you posted it, an August wave of popular short SCPs (ex. SCP-6101, SCP-6799, and SCP-6150) had started to sweep the site, and would continue afterward largely due to your article! What, to you, is the general appeal of short articles compared to meatier narratives (ex. several of the 6kcon entries which dominated May and June)? How does this apply to SCP-6336?

I guess I didn't really realize there was a wave of short SCPs before I posted 6336. I can get why people are fond of short articles though. There's a pretty common criticism that I see a handful of people make when talking about SCP, essentially that it's "too complicated" or "too long", which in some cases can be true, and it can be kinda harrowing for a new user to read a really lore-dense SCP oftentimes. However, short-form articles avoid both of those critiques just by nature of their construction. While some can still have complexity, the length of them is more inviting for people who browse casually, while still being enjoyable by hardcore fans if the writing's good enough. This applies to 6336 specifically because it's particularly very far from both those aforementioned complaints, it's the shortest SCP in the last 30 days, and the concept and narrative aren't super complicated for most to understand. Instead, the minimalist implications leave people space to mentally write their own continuation of the broader idea of what's going on.

Certainly all these attributes contributed to its success, especially after the many several-thousand-word epics released just a month or two prior. How do you imagine SCP-6336's reception given you posted it at another time?

I don't think it would really be all that different if I had posted it earlier in the year, I've seen a lot of short-form SCPs do well over the years, it's just now that they've built more momentum in their broader popularity. I do wonder how it would do if I were to have posted it later though, I'm not sure if people would dismiss it as riding The Shortwagon because of its simplicity, but at the same time, it would've still been the same words and everything, so it might have done just fine and I may just be paranoid.

Makes enough sense. Given the existence of this "Shortwagon" as of late, how do you believe trends of this nature develop, and do you think they will emerge in the future?

I think they develop from writers seeing other writers do something that readers like and wanting to do something to capture a similar essence to that initial thing. This can be writing less, writing more, writing about a new GoI, writing about a gang of vampirous alpaca bikers (this is my idea now, nobody's allowed to steal it), or just whatever else seems to catch people's interest at the time. The site's not just collaborative in the realm of lore and setting, but also in the way each author builds off of each other, sometimes not even from criticism, but from seeing other authors do something and then being inspired to try something in the same vein.

Well, thank you for serving as that inspiration with your wonderful article, and thank you for partaking in this interview!

No problem! And remember to always watch your reflection closely 👁️

SCP Data & Trends

All the goings-on of the site condensed into bite-sized takeaways! Is there a statistic or figure you would be interested in knowing? Let us know and we can feature it next time!

AARP.png
AAPTM.png
AT.png
AA.png

Eddybird's art page was the highest-rated page with no downvotes, with a huge +118! The highest-rated article with no downvotes was On The Internet, Nobody Knows You're A Kaiju by stormbreath with +50. This makes it the second month running an article by stormbreath has achieved this!

If you haven't heard about SCP-6542 yet, where have you been? It's quickly proved to be one of the most polarising articles on the site — after 204 votes it's currently sat at +14. Similarly, after 57 votes SCP-5741 resides at +3.

The huge ≈250% increase in the top-rated GoI format from July to August is due to Fish^12's WWS article Critter Profile: Big Blue! hitting the upper echelons of the voting ranks.

In a complete opposite to July, through August TUESDAY was the most popular day to post (total of 29 articles) and SATURDAY was the least popular, with only 14!

What happened with the tags this month? Same as July, sentient, sapient, and humanoid were the top 3 tags, with 30, 24, and 22 tags respectively.

When you compare July to August though:

  • online dropped from 6 tags in July to 0 this month. (Did we all go outside and touch grass during the last of the Summer sun?)
  • alive jumped by 600% from 3 tagged article in July to 18 in August! The highest-rated of which was SCP-6101 by PeppersGhost.
  • We also had acoustic go from no tagged articles to 6 in August. The highest-rated of this bunch was SCP-6150 by Elenee FishTruck and TheYeIIowDucK. (That Elenee sure does write good sound-related articles).

Figures correct as of 2nd September.

Word from Staff


Word from Staff of the Month: Gloaming
Def: The period of time which the Sun is setting.

After the craziness throughout the month of July, things are starting to calm down and staff activity is starting to balance out. With that said, this not without saying that — although this month is less notable compared to the last — there have still been great strides in rolling out new policy, improving site infrastructure, and bettering the general user experience. With that said, firstly: I would like to give a warm welcome to the newest additions to the staff body:

  • Elunerazim, MAST
  • Siddartha Alonne, Community Outreach/MAST
  • Rounderhouse, Community Outreach/Technical
  • PlaguePJP, Recap
  • Pedagon, Recap/Site Crit/Community Outreach
  • J Dune, Recap
  • Jack Waltz, MAST
  • GremlinGroup, Recap
  • Dysadron, Community Outreach
  • Assistant Null, Internet Outreach

We're elated to have them aboard, and look forward to seeing their contributions to staff.

Updates from 05 Command

Although not on par with the cyclone of new policy that was July, August has seen quite a bit of proposals being pushed through in its own right; along with seeing follow ups on stuff previously discussed and voted on (e.g. Recaps). For convenience and brevity, the following consists of summaries for each policy discussion, vote, and other general notable events occurring on the staff site of for the SCP Wiki and general staff activities. Along with this, if you so desire, direct links to the relevant threads will be included if you wish to read the details in full: http://05command.wikidot.com/forum/t-14192777/august-2021-recap

Right out of the gate — on the first of the month, staff members OptimisticLucio and UncertaintyCrossing posted the Art Restructuring Proposal discussion to O5 (main site mirror thread can be found here). The aim of the proposal is to make artists and their work on the site more visible, in an effort to resolves concerns brought up by community members consulted by the relevant staffers. The bulk of the proposal denotes that — to increase visibility and traffic to the work of on-site artists, they would be allowed to create separate pages under a new page category. This would consist of one or more stand-alone galleries outside of an artist's artwork page.

On the 10th of August, staff member gee0765 forwarded an 'Unarchival' policy to both O5 Command and the main site for discussion (main site mirror can be found here). The new policy was drafted following talk in staff chat; noting that there is no formal process by which an -ARC article can be unarchived and/or deleted. To resolve this, the proposed solution would establish that any OS+ staff member would be allowed to put up a vote for the unarchival of a designated page. Said votes would have a duration of one week, and a simple majority vote is necessary.

OS user OCuin, on the 20th, — posted the 'What is vice-captaincy?' discussion thread on O5. The goal of the thread was to determine key features regarding the roles of Vice-Captains among staff teams. Among the topics of the conversation: main points included determining powers and purposes of the the VC position.

The next day, Limeyy posted a follow-up discussion thread regarding the previously proposed PWRD team — to functionally replace the now-defunct Site Crit team. Essentially, as noted just before, with Site Crit being dead, a new team would be established to take on and reimagine the initial tasks delegated to the former group. Moreover, they would also serve to revive the rapidly deteriorating #thecritters channel on SkipIRC. The generality of the thread revolved around a sandbox draft of the in-depth responsibilities that would be held by the hypothetical team.

Woedenaz notes that the interwiki portion of the side bar is incompatible with a number of CSS themes. They post a discussion thread on O5 regarding a fix. Some modifications to Tech and CSS Policy would be needed for this change.

On the 31st, Rounderhouse opens up a thread about changing the minimum requirements for some classes of tags. It would change the number of articles/authors required to have a tag implemented for attribute/character/GoI/canon tags.

Staff Spotlight: Technical Team

Featuring: stormbreath
Interviewer: WhiteGuard

Interview

Alright, stormbreath. Why don't we start out by talking a little about what the Technical team actually does and what you personally do as a Captain of it?

So the Technical Team is responsible for managing Technical assets on the wiki — anything involving the infastructure of the site or needing some outside coding knowledge to handle. Our primary duties under that label are handling CSS and managing tags on the wiki. These aren't all we do, but they're the most common things that we handle. Another critical duty is handling javascript and html, as Wikidot allows users to add their own html to articles through [[html]] blocks. Sometimes, this html has problems, and needs attention. A recent duty we've been dealing with is the switch from http to https, which we were recently able to get configured for the wiki. We also work with the Wikijump Team (although many of us are on it) to help Project Foundation along.

Some common tasks that we handle on the Tech Team are looking over tag requests and determing if we should meet them, taking themes and approving them for posting, doing the same sort of thing for components or answering questions users have about formatting and Wikidot syntax in #site11. Alongside these, we tend to have a lot of unique, one-off projects to help try and improve site function. For instance, a few months ago we worked on html meta tags to better improve what the site looks to when you drop a link to it on Twitter, Discord or many other platforms.

Would you care to share a little about your journey from regular Tech member to Captain? Did you have a lot of experience with Wikidot code and such before joining or was it a "learn on the fly" kind of thing?

I was recruited as a Tech Staff in May 2018. At that time, I already had a decent amount of experience with Wikidot code and CSS — in fact, the initial circumstances of my recruitment was fixing up a CSS theme really quick while hanging out in #site11 and getting asked to join Tech by Magnus as a result. Since then, I was on the team for about a year and half, doing work for the team on a regular and consistent basis. Although I went in to the team with a pretty good handle on Wikidot formatting and other Technical elements, my time on the team resulted in me sharpening those skills and getting a lot more experience, so it's a bit of a mixture of prior experience and learning as I went. Getting Captain happened earlier this year, when Magnus offered me the position. At that point, aismallard and I were doing a lot of the work for the team, so the Captaincy seemed to make sense on that basis.

Speaking of elevating position, you were part of the recent batch of candidates to be elevated to the position of administrator. How does it feel to be an admin for the SCP Wiki? Has anything changed for you yet?

It definitely feels weird being an admin, I have to say. For the most part, the day-to-day of staff operations haven't changed. It certainly makes a lot of Tech Captain duties easier - not needing to get ahold of an admin in order to check something out in the admin panel makes it a lot easier to do Tech work for the site. From a policy level, it's honestly less of a change than I had been expecting, although there is still something of a difference, with more work and needing to keep more of an eye on what's going on in general.

Sounds good. To wrap things up, I just wanted to ask a little about your somewhat recent 6000 contest entry that you worked on with your fellow Tech team Co-captain, aismallard. It ended up in third place overall, which is quite the accomplishment. What are your general sentiments about how SCP-6140 turned out and how was working with your Co-captain on something not staff-work-related?

I'm very happy with how 6140 turned out and how it ended up placing. It's definitely one of my favorite articles I've written, and it was really surprising to me that it managed to do quite as well as it did. I was certainly hoping that we would do well in the contest, but top three well out did my expectations. Working with ais was a lot of fun - we've been friends for a while even before we became Tech Captains, so working together on this was nice to finally write something together. It was somewhat funny, however, for the two Tech Captains to write an article that ultimately had nothing to do with anything related to Tech. I feel like that's kinda playing against expectations.

Well, I believe that will do it. Once again, congratulations on that entry and thanks again for agreeing to this interview!

No problem!

New Content this Month

There is a multitude of wonderful works that are posted to the Wiki every month whether they be SCP articles, Tales, GoI Formats, Art pages, Author Pages, Essays, and more! Below, we have all of the creations for this month listed out by week and type (except for art pages, we did that earlier!) We have added little emojis next to articles that qualify to add some additional content. Below we have listed out the emojis we use and what they mean. Be sure to give them a look!

🐣 = An author's first article - This is their first one! Check them out and be sure to leave comments!
🤝 = Co-authored works - It is always interesting to see the dynamics of how people work together!
💯 = Articles rated at +100 and higher - These are articles that have seen success and should be celebrated for it!
📈 = SCP articles rated under +30 and Tales and GoI Formats rated under +20 - Let's show these a little love!


Week of August 1st


SCP Articles

  • SCP-6062 ("King Ratthew Splondis XVIII, Bearer of Pestilence and Lord of All Rodents") - Written by J Dune.
  • SCP-6161 ("The Confectionary Knife") - Written by Aroncrime, rewritten by Uncle Nicolini.
  • 💯 SCP-6101 ("The Most Powerful SCP") - Written by PeppersGhost.
  • SCP-6069 ("Cupid's Angel") - Written by Nickthebrick1.
  • SCP-6076 ("A Hero, Complete") - Written by Tanhony.
  • SCP-5847 ("The Food's Court") - Written by Tstaffor.
  • SCP-6332 ("Saldemander") - Written by RoninTortoise.
  • SCP-6524 ("A God-Awful Small Affair") - Written by BlueJones.

Tales

GoI Formats

Miscellaneous Pages

Ozzylizard’s Corner of The Wiki It's OzzyLizard's Author Page!


Week of August 8th


SCP Articles

  • SCP-6068 ("Site-█▓░▒") - Written by TL333s.
  • 📈 SCP-6018 ("The Beforelife") - Written by Flopmind.
  • 🤝 💯 SCP-6150 ("Voskhod 3") - Written TheYeIIowDucK, rewritten by Elenee FishTruck.
  • 📈 SCP-6688 ("[ACCESS DENIED]") - Written by Impperatrix.
  • SCP-6799 ("Shards of Glass") - Written by Tufto.
  • SCP-6970 ("foundation that tortures you") - Written by Fish^12.

Tales

GoI Formats

Miscellaneous Pages


Week of August 15th


SCP Articles

  • SCP-6168 ("The Puzzle Pieces of Adolescence") - Written by Irina Bougainvillea.
  • 💯 SCP-6336 ("Seeing Myself Blink") - Written by Lamentte.
  • 📈 SCP-6241 ("A Dead God's Remains") - Written by NebulousStar.
  • 📈 SCP-6095 ("I Want to Go Back") - Written by drop therapy.
  • 📈 SCP-5736 ("Breakdown, Reform, Lost Along the Way") - Written by Azmoeth Jikandia.
  • SCP-3837 ("Corn Goblin") - Written by Tstaffor.
  • 📈 SCP-6828 ("<span style="font-family: Book Antiqua,Palatino,serif;font-style:italic;font-weight: bold;">The Extent of The Words, Sayings, Quotes, Parables and Many Pieces of Wisdom Related to The Glorious and Necessary Ted</span>") - Written by MrRonin.
  • 📈 SCP-6262 ("A Friendly Bus") - Written by Waspus.
  • SCP-6299 ("A Power Cut") - Written by OhSirWaffle.
  • 🤝 SCP-6555 ("What Moved the Tides") - Written by JakdragonX and Ralliston.
  • 📈 SCP-6440 ("Theatre of the Living Dead") - Written by fairydoctor.
  • SCP-6888 ("Extratemporal Funeral Home") - Written by stoner99.
  • SCP-6404 ("My Name is Your Name and Your Name is My Name") - Written by fabledtiefling.
  • SCP-6089 ("Black Sabbath") - Written by MrRonin.
  • 📈 SCP-6635 ("Not so Useless") - Written by Undercover Fly.
  • SCP-6250 ("Keystone Flats") - Written by bigslothonmyface.
  • SCP-6343 (""The Amazing Non-Existing Beast!"") - Written by Duke-Crusty.
  • 🤝 💯 SCP-6598 ("Flippant") - Written by Cremo, rewritten by PlaguePJP, J Dune, and HarryBlank.
  • 📈 SCP-5584 ("Griefing") - Written by IronShears.

Tales

GoI Formats

No GoI formats this week!

Miscellaneous Pages


Week of August 22nd


SCP Articles

  • 💯 SCP-6815 ("To Fly Lanterns Under the Rising Sun") - Written by Veralta.
  • SCP-6902 ("Lost Luggage") - Written by LizardWizard.
  • SCP-6899 ("A Little Piece Of Me") - Written by ManyMeats.
  • 📈 SCP-6642 ("You hate me, too?") - Written by NebulousStar.
  • 📈 SCP-6338 ("The Rubicon Rope") - Written by RYLIRK.
  • SCP-6223 ("Burn With Me") - Written by LordStonefish.
  • SCP-6072 ("Wherever Death Goes") - Written by Ralliston.
  • 📈 SCP-5273 ("Pasta, lightly seasoned with [COGNITOHAZARD EXPUNGED]") - Written by hungrypossum.
  • SCP-1444 ("Hunger.") - Written by stormbreath.
  • SCP-6724 ("I'd rather be someplace else.") - Written by Fishish.
  • 📈 SCP-6340 ("Closing Act") - Written by RogueNite.
  • SCP-5846 ("The One-Stop Shop") - Written by Tstaffor.
  • SCP-6360 ("The Basilisk") - Written by Dr Lerche.
  • 📈 SCP-6244 ("Scot Pilgrims Vs. The Worlds") - Written by Rhineriver.

Tales

GoI Formats

Miscellaneous Pages


Week of August 29th


SCP Articles

  • 📈 SCP-5429 ("arm back you") - Written by SketchyTh0ughts.
  • 📈 SCP-6701 ("Shooting Star Swallow") - Written by Sirslash47.
  • 📈 SCP-6542 ("The Virgin Dairy") - Written by DarnellJermaine.
  • SCP-6990 ("The Truth about Ancient Aliens") - Written by Dr Golden.
  • 📈 SCP-6391 ("Of spiders and nostalgia") - Written by Tiamat Elsen.
  • SCP-6767 ("The Bronze Lizard") - Written by Sidewindered.
  • 📈 SCP-6181 ("The Opposite of Progress") - Written by TL333s.
  • SCP-6049 ("Viral Marketing") - Written by Fishish.
  • SCP-6791 ("The Protagonist") - Written by LittleFieryOne.

Tales

GoI Formats

Miscellaneous Pages

The Site News Team

Editor

WhiteGuard

Editor, Interviewer

Hey there! I am the editor of the SCP Wiki -EN branch's Site News as well as a Moderator for the site. If you have any questions, issues, suggestions, concerns, and so on about the Site News, feel free to contact me! My predominant goal when taking over was to deliver a product each month to our wonderful community that would be interesting and enjoyable to read. Have a wonderful day and stay tuned for the next one!

Reporters

CaptainKirby

Columnist

Well written, quick as a whip, and able to pilot any seafaring vessel9. Clever robot creator and shaped like a friend.

DrAkimoto

Art Team

Consider this a placeholder as Aki is busy right now. :P

Dysadron

Data Reporter

Former reporter for [EXPUNGED]. Likes writing, horror movies, and puppies. If you know of me, it's likely due to SCP-5733. Don't ask me how to pronounce my username.

Elenee FishTruck

Art Team, Interviewer

Former President. Image connoisseur. Reportedly good at asking questions (unsubstantiated).

EstrellaYoshte

Art Team, Formatting Team

Site News' most sleepless artist and visual technician. Can be found haunting your CSS at the dead of night.

Hexick

Staff News Reporter

Hexick is scared of people, and happy to be here! They much enjoy recording data, reading, writing, existential dread, computers, the outdoors, robotics, and a slew of other totally normal things. Likes helping out both on-site and in IRC, and tries to be very thorough; nothing gets past them. [Placeholder; staff summary goes here. Remember to remove this during finalization.]

Limeyy

Staff News Reporter

Unhealth addiction to refreshing 05command, thought they might as well tell someone about it. Number one writer on the site named after a citrus fruit, because that's the bar we're setting.

Naepic

Art Team

Very old for a guy beginning his 20s. Remembers when Site News was sigma and bland-pilled and was hired out of the blue by a guy who wrote about racecar witches.

OptimisticLucio

SCP News Reporter

Falls backward into positions that he's absolutely not qualified for. Deer College Enthusiast.

Riemann

Columnist

Riemann is a cosmologist10 who should be spending their time writing papers rather than writing columns. No one believes that they ride a motorcycle.

ROUNDERHOUSE

Features Reporter, Formatting Team, Op-ed Reporter

Bigger, better, rounder than you are. Wanderer's Library admin. Former editor of [EXPUNGED]. Likes doing author features and writing spotlights when he isn't stacking racks. Delightfully devilish.

Siddartha Alonne

SCP News Reporter

International reporter! Knows everything about every branch of the Foundation. When he's not searching for nitpicks, he's reporting international news to our magazine. Don't make him notice that the correct spelling is "Siddhartha". The world is not ready for it.

UncertaintyCrossing

Art Team

This incorporeal entity can be found traveling the Seven Seas in search of artistic treasure to share here with the community. Feel free to give it a poke if you have a bounty to contribute.


Thank you so much for reading the SCP Wiki's Site News!




News Archive

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License