Security Department declares "Green-D" lockdown of the Light Containment Zone
By Vico Trevisani
27 Sep 2022, 21:12
Light Containment Zone SCP-407 View. Photo: Vico Trevisani
The Security Office declares the Light Containment Zone to be under "Green-D" lockdown after "near-breach" of SCP-407 is discovered.
A security detail was sent out this Monday to inspect the integrity of SCP-407's containment chamber. The team reported two critical issues pertaining to the structural integrity of the containment chamber. After rapid response to the situation, the Security Department officially announced lockdown of the zone the next day.
- SCP-407 is a safe-class song that, when played, causes cellular mutation within nearby organisms. The growth is exponential as it then slows down and everything slowly dies. However, certain unknown conditions have lead to SCP-407's instance to stay alive much longer than estimated. The danger lays within the toxic mold that can be spread. There is, of course, the hostile carnivore entities but they will be quickly subdued. What we should worry about are the long-time effects of spores spreading, says Dr. Negan Morrigon in his comment about the dangers of the containment issues.
Hole in the wall said to be caused by an SCP-407-D instance. Photo: Vico Trevisani
The Security Department ensures that the situation is safe
The Security Department was fast at work after the report was published. Their rapid pace kept the losses small and made the situation manageable.
In an email, the Security & Containment division enlightens us on the current situation of the incident.
- While the situation is certainly not a trivial one, it is under our control and we do not expect any impactful losses. There was a massive risk for a containment breach, however, there have been no reports yet of anything major having breached, it sounds from an email of Security & Containment.
When questioned about the cause of the breach, Security Lieutenant "Raiden" of S&C states that the SCP-407 are "under constant war".
- SCP-407 instances are at constant war, and it simply got out of control. It would appear that the SCP-407-D instances had gotten too aggressive, which resulted in unusual destruction behaviour, Raiden says in an interview.
Shortly after announcing the lockdown, S&C released their plans of dealing with the incident. The document outlines a six-step plan, primarily with intentions of moving out the nearby SCPs and decontaminating the area. The document additionally mentions suspiciouns of other safe-class SCPs being affected by the pollen and spores.
They estimate that the plan will take up to a week or two and advise that people do not panic.
Not the first incident
SCP-407 was first introduced to the facility two years back under the re-construction of the Light Containment Zone. A human error caused the SCP to activate and it rapidly spread throughout the LCZ area under construction. The section has been used as the center for all SCP-407-related research ever since.
The incident this Monday has sparked massive controversy about the classification and containment measures of the SCP.
- We went years without anything significant occurring. An unexpected human error led to the anomaly being contained in a fixed and immovable area with intricate logistical issues, and it was, at the time, the best area to contain it, Site Director Dr. J. Merlin says when questioned about the classification of the anomaly.
Board of Directors meeting about the re-classification of SCP-407
Administrative personnel meeting outside the Administration Offices. Photo: Sarita Tara
In response to the recent controversy, the Board of Directors announced a meeting about the classification and containment methods of SCP-407. The meeting is said to not only include BoD, but also specialists and high-rankings from across the region.
/* 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;
pointer-events: auto;
}
@media not all and (max-width: 767px) {
#top-bar .mobile-top-bar {
display: block;
pointer-events: none;
}
#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;
}
#side-bar:focus-within:not(:target) {
left: 0;
}
#side-bar:target .close-menu {
display: block;
position: fixed;
width: 100%;
height: 100%;
top: 0;
left: 0;
margin-left: 19.75em;
opacity: 0;
z-index: -1;
visibility: visible;
}
#side-bar:not(:target) .close-menu { display: none; }
#top-bar .open-menu a:hover {
text-decoration: none;
}
/* FIREFOX-SPECIFIC COMPATIBILITY METHOD */
@supports (-moz-appearance:none) {
#top-bar .open-menu a {
pointer-events: none;
}
#side-bar:not(:target) .close-menu {
display: block;
pointer-events: none;
user-select: none;
}
/* 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;
}
}
}
What this is
A bunch of miscellaneous CSS 'improvements' that I, 
Croquembouche, 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.
.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; }
