Author: Lt FlopsLt Flops
Published on 20 Aug 2018 08:59
/* source: */
#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) {
    .mobile-top-bar {
        display: block;
    .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!important;
        position: fixed;
        top: 0;
        left: -19em;
        width: 17em;
        height: 100%;
        overflow-y: auto;
        z-index: 10;
        padding: 0.3em 0.675em;
        background-color: rgba(0,0,0,0.1);
        transition: left 0.5s ease-in-out;
    #side-bar:target {
        display: block;
        left: 0;
        width: 17em;
        margin: 0;
        z-index: 10;
    #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;
    .close-menu {
        margin-left: 19em;
        opacity: 0;
rating: +219+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.


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(';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.

: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; }
Author: Lt FlopsLt Flops
Published on 20 Aug 2018 08:59
> Audio Version <
rating: +219+x


CONTAINMENT CLASS:euclid restricted

DISRUPTION CLASS: {$disruption}


SCP-4420. Image captured from a 50-metre safe distance.

Special Containment Procedures: SCP-4420 is situated in a secure position in the Site-82 Arboretum. Tentative Containment Module #819 regulates the entrance to an artificial pocket dimension large enough to confine SCP-4420. Containment technicians have installed four synchronized Scranton–Marlowe Topology Stabilizers, which maintain dimensional stability inside the module.

Description: SCP-4420 is a red Idaho potato with a current mass of 400 million kg and external dimensions of 150 metres by 65 metres by 55 metres. SCP-4420 displays the following ectoentropic properties:

  1. SCP-4420 responds to moisture shrinkage (~5% every two weeks) by generating a new amount of moist potato matter. During this event, a random Idaho citizen's drinking water transforms into starch-rich potato-flavoured water, which grants the ability to commune with potatoes for 3 to 10 hr after consumption.
  2. Exposure to electromagnetic radiation in the human visual spectrum (λ = 400 nm to 700 nm) produces potato matter of a randomized form. This matter relates to potatoes at various conceptual levels, be that immediate or vague. The new matter grows alongside SCP-4420 and attaches itself via esoteric means beyond current agricultural understanding. Observed forms include:
    • Any variation of the 5 000 potato varieties grown globally.1
    • Types of cooked potatoes such as mashed potatoes, French fries, and potato chips.
    • 1996 Idaho County Junior League Potato Sack Race champion Michelle Brown, age 6.
    • A species of Jerusalem cricket (colloquially known as the potato bug) composed of sweet potato. These insects have infested ~8% of SCP-4420 to date.
    • Memetic ennui affecting 10% of persons within a 5-km radius.
  3. SCP-4420 displays evident immunity to decay. SCP-4420 consumes most organic irregularities almost immediately after their growth, and produces healthy potato matter in their place.
  4. SCP-4420 consumes food and organic waste within 20 metres of its surface. Any nearby organic material transforms into a potato tuber of equal mass and teleports into SCP-4420. This includes small animals up to 5 kg in mass.

As of current documentation, SCP-4420 has been growing for 22 years.


I. 10 May 2019

Field researchers discovered foreign fluid with trace amounts of thaumic contaminants in the local groundwater. The Site-82 Operations Command Office initiated Mandate 3731-Ov91, which calls for immediate lockdown and destruction of foreign substances. Security staff considered the lockdown successful within the hour.

Because of its containment location, however, SCP-4420 remained unaccounted for.

At 21:51 CDT, SCP-4420 absorbed thaumic fluids and developed sapience lasting for 32 hours. During this time, it displayed the ability to manipulate informational constructs. SCP-4420 then disseminated 362 SMS messages to on-site staff.

A series of received messages is as follows.

can you see me

pls look at me

im big

look at me

do you think im pretty

is that what i rly look like

no way

is that how you see me ☹️

you cant see me like this

im not good enough am i

not for you

how could i be

leave me alone

im a monster

im sorry i look this way

II. 12 May 2019

At 05:51 CDT, SCP-4420 ceased all anomalous growth and displayed signs of accelerated decomposition.

SCP-4420 has been reclassified as NEUTRALIZED.

rating: +219+x
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License