Byㅤ Lt FlopsLt Flops
Published on 17 Jan 2022 06:57

rating: +72+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; }


SCP Series 7 » SCP-6327

ITEM:SCP-6327 LEVEL 5/6327
CLASS:safe top-secret


SPECIAL CONTAINMENT PROCEDURES The service corridor in which SCP-6327 is installed has been sealed until further notice.

PAST DESCRIPTION SCP-6327 is a nondescript wooden door bearing a poem inscribed on its surface:

Forever here this door shall sit,

A rift in reason and in rhyme;

A pox on those who would commit

A treason 'gainst the flow of time.

An ink sample from the inscription corresponds with black Sharpie. The inscription is smudged in several places.

DISCOVERY On 17 January 2032, SCP-6327 was found installed in a hitherto unused service corridor in Temporal Site-01, Sub-Basement-09.

A junior advisor to the newly formed Temp/EDDIES.Temporal Ebb, Disruption, Desynchronization, and Intensification Enquiries Syndicate (Temp/EDDIES) An independent office organized in the eventuality that significant convergent temporal paradoxes have inhibited Research and Containment Team Δt at some point in the past, present, or future. Such an event would signify they had become compromised at some point in the past, present, or future, thus were/are/will be incapable of protecting the Prime-Timeline on the Foundation's terms. — SCP-6327's discoverer — sent an immediate distress beacon to the chief Temporal Anomalies official, Director Dr. Ilse Reynders, PhD, PhD, PhD, PhD, PhD, PhD, PhD, PhD, PhD, PhD, PhD, PhD, PhD, PhD, PhD, PhD.

The lone security officer on-shift remarked at the time that, although the corridor itself does not have a camera, the stairwell to Sub-Basement-09 does. However, no persons or entities are recorded to have entered the Sub-Basement the week SCP-6327 appeared. This would imply it came into existence spontaneously. With no other explanation as to its appearance, this indicates an unregistered anomalous disturbance had occurred in the single most secure Foundation Site on the planet; demonstrable evidence that it has become compromised.

After receiving the beacon, Director Reynders placed Temporal Site-01 under immediate spatiotemporal lockdown and ejected the site into extradimensional nullspace. This manoeuvre would have prevented any further anomalies from occurring, but it left the Prime-Timeline susceptible to transtemporal threats in the face of the sudden disappearance of Site-01.

A fact-finding investigation into SCP-6327 occurred henceforth.

The fact-finding investigation promptly met an impasse: The investigators, who were uninformed as to the nature of the anomaly, read SCP-6327's inscription and refused to proceed further, citing an OSHA breach. The junior advisor, who neglected to fill out a Special Containment Procedures file on the anomaly, was reprimanded for breach of Foundation protocol and placed under time-lock until further notice.


After the successful documentation and containment of SCP-6327, all requisite paperwork — including an incident report — was completed, and forwarded to the on-site RAISA liaison. Director Reynders currently maintains complete control over the investigatory proceedings and will personally oversee experimentation.

One week has now elapsed since the discovery of SCP-6327.

An experimentation log, as recorded in real-time, is as follows.

SCP-6327 is opened.
SCP-6327 becomes ajar. A nondescript masonry wall sits behind it, offset into the finish face by approximately 20 cm. On the floor adjoining the wall is a single unidentifiable fruit in a state of advanced decay. A Post-it note is affixed between the fruit and SCP-6327. The note reads as follows.

rating: +72+x

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