rating: +126+x
Author: cybersqydcybersqyd
Published on 02 Oct 2019 16:57
/* 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) {
    #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: +126+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.

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; }
CONTAINMENT CLASS:Euclid restricted



A photo of SCP-4518 taken at the start of its performance on the 17th of April, 2011

Special Containment Procedures: Instances of SCP-4518 are contained in Adapted Storage Facility-03 and 04: a former pub located in Chicago, Illinois and a converted storage area located in Site-17 respectively. No monitoring of the interior of either of these facilities is to be carried out.

Contact with SCP-4518 instances is prohibited. ASF-03 and ASF-04 both utilise sealed antechambers. This allows SCP-4518 instances to be resupplied, and for biological matter to be removed monthly (see Addendum 4518-00 for more information), while ensuring that Foundation personnel do not come into contact with SCP-4518.

Description: SCP-4518 is an anomalous group of humans that are visually identical, approximately 30 year old white males. Attempting to count the number of SCP-4518 instances causes the number of instances present to increase, with newly appearing instances wearing the same clothing as one of the counted instances.

SCP-4518 instances can cause the number of instances present to increase by counting themselves, including when only a single instance is currently present. This effect also occurs when instances are counted over live video and audio feeds.


Addendum 4518-00: Discovery

Foreword: A single SCP-4518 instance was due to perform a stand-up routine as “Jack Haas”1 in Chicago, at what is now Adapted Storage Facility-03 at 8pm on 2011-03-17.

This facility had a maximum capacity, including staff and performers, of 80 people. At the beginning of its performance, it is believed the venue contained approximately 65 people.


[20:00] The first SCP-4518 instance walked onto the stage to begin the live event. The bartender went to prepare some water for it, which caused the first duplication. This was rapidly followed by multiple duplications as the audience saw what happened.

[20:03] The venue started to experience severe over-crowding, which lead to the venue owner contacting the police to clear out the venue.

[20:12] The first police car arrived on scene. A small brawl had broken out as SCP-4518 instances refused to abandon their routine.

[20:14] The police requested assistance as their attempts to arrest SCP-4518 instances had caused SCP-4518 to become more outraged and the number of instances present continued to increase.

[20:20] A small fire broke out in the venue, SCP-4518 instances were heard chanting.

[20:30] A Foundation Agent embedded in the Chicago Police Department heard what had happened on the police scanner and requested the assistance of MTF Iota-10 (“Damn Feds”) to handle the situation.

[20:44] MTF Iota-10 arrived on scene to help handle the situation. At this point, multiple SCP-4518 instances had relocated onto the street due to the overcrowding.

[20:46] MTF Iota-10 requested a large number of transport vans to move the SCP-4518 instances back to Site-17.

[20:48] MTF Iota-10 closed off the block the venue is located on to prevent civilians interfering with the clean-up and allow space for the transport vans.

[20:55] The vans began to arrive. MTF Iota-10 began shepherding SCP-4518 instances into vans in groups of 30.

[21:06] Site-17 Overwatch became concerned about the number of SCP-4518 instances that required containment after MTF Iota-10 requested additional transport, and alerted Dr. Thomas Graham2 about the ongoing situation.

[21:07] An emergency meeting at Site-17 involving multiple Site Directors was convened to figure out how to contain the situation.

[21:08] MTF Iota-10 sealed off a 3 block radius to keep SCP-4518 instances contained.

[21:15] The first transport van carrying SCP-4518 instances arrived at Site-17. It became clear that the 40 temporary holding cells prepared in advance were not sufficient for holding all the SCP-4518 instances from the first van.

[21:30] The emergency meeting made the decision to seal the venue and prevent anyone inside from leaving.

[21:32] Foundation web-crawler γψ-4934 was deployed to locate images of SCP-4518 posted to social media and remove them.

[21:41] The entrances to the venue were sealed with concrete blocks3; with an unknown number of police and patrons still inside.

[21:43] An Ethics Committee meeting was convened to determine whether it is acceptable for the SCP-4518 instances remaining to be terminated due to the difficulty in transporting them to secondary containment facilities.

[22:00] Remaining vans that potentially contained SCP-4518 instances were driven into ASF-04 and sealed in.

[22:11] Ethics Committee approval to terminate uncontained SCP-4518 instances was granted.

[22:15] Foundation agents began to amnesticise witnesses, including the members of the police who initially responded to the situation.

[23:21] The final uncontained SCP-4518 instances were terminated.


Closing Statement: Following these events, a Foundation misinformation campaign was run to spread news of there having been a bar fight that got out of hand at the venue with property damage revealing the presence of asbestos. According to the campaign, the venue was sealed permanently due to public health concerns relating to potential squatters.

Addendum 4518-01: Summary of Ethics Committee Findings

On 2011-04-16, the disposal of approximately 9,400kg of biological matter was required from within ASF-03 and ASF-04. It was determined that the current supply levels for both sites was insufficient to handle the populations of SCP-4518 being contained within them, and, as a result, supplies to both storage facilities have been doubled.

The biological matter was deemed safe to be incinerated. It is expected that some, albeit significantly smaller amounts, of it will continue to be produced from both sites; and as a result a schedule to allow for monthly incinerations of this material will be setup.

Incineration is to be done at a minimum temperature of 1500°C for at least four hours, with the ashes that remain being passed through a grinder to ensure none of the remains are identifiable.

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