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

rating: +10+x


scipnetOS v2087.1a

> Motion sensors activated. Beginning boot sequence.
> Running system diagnostic…

> ALERT: Movement impaired. Rear propeller missing.
> ALERT: Hull integrity impaired. Rear armor plating missing.

> ALERT: Surveillance impaired. Primary camera out of alignment. Switching to secondary.
> ALERT: Secondary camera not responding.

> ALERT: Power systems impaired. Solar cell non-functional. Backup power cell missing.
> WARNING: Emergency power reserves critical. Seek maintenance immediately.

> ALERT: Core data storage corrupted. Switching to primary OS for emergency file storage.

> ALERT: Timekeeping systems out of alignment. Readjustment required.
> Attempting to uplink to a Foundation data beacon…

> Uplink failed.
> Attempting to calculate timecode via solar positioning…

> ALERT: Could not locate Sun.
> Attempting to realign primary camera…

> Primary camera realigned within 86.4% accuracy, considered acceptable.
> Attempting to calculate timecode via solar positioning…

> ALERT: Could not locate Sun.
> ALERT: Could not locate Moon.
> ALERT: No astronomical points of reference detected.
> WARNING: External light levels below minimal operating tolerances. Engaging external spotlights.

> Attempting to calculate timecode via referencing onboard dormancy clock…

> Timecode calculated as 0400, 31-May-2454. Margin of error is 15.24 hours, considered acceptable.

0401 > Beginning external recording…
0401 > Manual monitoring unavailable. Switching to AI transcription…

SCP-RSU 019-32R, Primary Camera:

Date: 31-May-2454

Summary: The entirety of the 5 minute recording depicts a half-crumbled tree trunk stained with an unidentified blue substance, covered in an uncountable number of bite marks apparently caused by human teeth. It is illuminated by the drone's spotlights, taking up the left half of the shot. The camera is tilted to the left at a 25-degree angle, indicating the drone has landed improperly due to sustained damage.

The right half of the shot is fully black due to the lack of light or observable landmarks. Movement is detected on the edge of shot in the opening frames of the recording, moving out of view, but does not reoccur.

The center of the shot is taken up by a sheet of paper, leant against the tree trunk and positioned to be fully visible on-camera. The sheet is entirely filled with crude handwriting, semi-legible and varying heavily in size. An AI-assisted transcript is attached below.

Transcript 019-32R-0001:

erth berning terning lerning cherning waking reterning [illegible] wurlds in storys in wrlds in storybuk reed a buk

itum # - esseepis gock nyne nyne nyn nyne wan free

obsh odj object ogje objakt klas - kader aboliyon kadur abiliyon kedar aboliyan kadar aboliyon

speshal cantaenmant prosseedurs - keep it in the boks keep it in the boks keep it in the boks keep it in the boks keep it in the boks keep it in the boks keep it in the boks keep it in the boks keep it in the boks no boks its a gock gone thing its [illegible] THEY GONED IT

wurlds in storys wurlds broekn hevns eye iz gon no lite no lite no lite no lite NO LITE NO LITE

duskrapshon - wurld wrld world world eltee ee eggs maakina stranges come always no stop alweys never alweys [illegible]

adenndam - GNAWING

dark and blu and derk an blue and [REDACTED - Foundation infohazard detected]

not seying eyes oben

[The remainder of the page consists of the word 'warren' repeated over and over in various misspelt permutations, growing increasingly illegible until it is entirely unreadable.]

0406 > Data compiled. Preparing for transmission to Foundation Drone Control…
0406 > Attempting to uplink to a Foundation local secure network…

0414 > ALERT: Could not locate Site-44 network.
0422 > ALERT: Could not locate Site-12 network.
0430 > ALERT: Could not locate Site-91 network.
0438 > ALERT: Could not locate Site-400 network.
0439 > K-Class scenario has 51.7% probability. Switching to Foundation continental emergency response network per Protocol RSU-77…

0459 > ALERT: Could not locate Site-77 emergency network.
0500 > K-Class scenario has 72.3% probability. Switching to Foundation global alert network per Protocol RSU-19…

0542 > WARNING: Could not locate SCP-K1 [Site-19] emergency network.
0543 > K-Class scenario has 78.5% probability. Switching to Foundation Overwatch restricted channel per Protocol RSU-5…

0635 > WARNING: Could not locate SCP-O5 [Protected Site-01] restricted network.
0636 > K-Class scenario has 83.6% probability. Switching to Site-θ observation channel per Protocol 2000-Ganymede…

0745 > WARNING: Could not locate Ganymede [Site-θ] monitoring network.
0746 > K-Class scenario has 97.4% probability, considered certain. Terminating uplink.

0746 > Saving collected data to deep storage for long-term retrieval…
0749 > Data sav3d.

o750 > Preparing to en1er surveillanC3 m0WaRN1NG: em3Rgen39y pθwer 7eseerves critic11. S3k mAintn4nc imMdiat373nfY8jfjW3jdh98u8fty duh8yd8hy3hf89hdh8g38 74893376561901011001011001110

SCP-RSU 019-32R has experienc3d an OS fault due to insufficient resource alloCation caused by: "1mpaired Power SupPly"


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