Expansion
Expansion
By: TopDownUnderTopDownUnder
Published on 17 Oct 2021 20:38
rating: +1+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.

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.

…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; }
/* 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;
}
 
@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;
    }
    #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;
    }
    }
}

Expansion
Author: TopDownUnderTopDownUnder
Published on 17 Oct 2021 20:38
Reclamation
Expansion
Liberation

rating: +1+x


Terminal #6576


------
Welcome, Dr. Akabi Hayk
------




Good morning Hayk! You have (4) unread messages! What would you like to do today?


> open messages

Opening SCiPNet Messenger…

You have (4) unread messages:

(1). Monthly Site Memo - Site Director Everest
(2). SCP-6876 - O5-3
(3). sorry about yesterday - J. Researcher Daya
(4). New Revisions on SCP-6776 - Automated Alert System

Which one would you like to open? Enter (E) to go back to start menu.


> ????

Sorry, I didn't understand that. Please reenter your input.


> 2

Opening SCP-6876 from O5-3

NOTICE: Confidential data detected. Please re-input credientials to confirm identity.


> u: ahayka34@scip.net
> p: alldogsgotoheaven

Identity confirmed. Opening message…








Intiating Secured Terminal Protocol


Success. Opening 6876.scp file. Happy Reading, Hayk.




house.jpg
house.jpg
SCP-6876.

Item #: SCP-6876

Object Class: Safe

Special Containment Procedures: Site-76 has been christened for the sole purpose of overseeing containment of SCP-6876. Site Director Ed Hatley has been cleared for requesting direct funding from O5 Command for containment of SCP-6876.

All residential buildings near SCP-6876 have been purchased by a Foundation front company. Foundation personnel have been stationed in these houses, and are tasked with monitoring SCP-6876 for any activity or trespassers.

SCP-6876-2 is currently contained in an Incorporeal Entity Vacuum Chamber located within Site-76's Administrative Wing. Testing on SCP-6876-2 is strictly forbidden, and any requests for interviews are to be sent to Dir. Hatley.

Under no circumstances should STF Epsilon-55, Dr. Akabi Hayk, Dr. Frederick Heiden O5-31 or any other individuals associated with the Site-19 Recuperation Committee be made aware of SCP-6876. MTF Beta-5 ("Hunting Mothers") has been assigned the task of surveying the North American continent for more phenomena resembling SCP-6876.

Archived Containment Procedures from before July 12th, 2024 are available upon request.

Description: SCP-6876 is an abandoned, 2-story, wooden house located in Lincolnton, North Carolina.

Prior to July 12th, 2024, SCP-6876 served as the location of a series of spectral phenomena which began in 1950. SCP-6876 was home to two Class III Spectral Entities (classified as SCP-6876-1 and -2) which, once every six months, would clean and repair the house as needed. In the timespan between their manifestations, various Class I and Class II Spectral Entities would be seen entering and exiting SCP-6876, never staying for more than two days. None of these entities have been seen since July 12th, 2024.

On that date the Pueraria Montana.Kudzu. surrounding SCP-6876 rapidly grew over the house, covering any entrances into it and obscuring most of its windows. SCP-6876-1 was inside the house when this occurred, while SCP-6876-2 was outside tending to a small garden. SCP-6876-2 was able to avoid the expansion of the Pueraria Montona, but -1 was left inside. SCP-6876-2 tracked down the local task force, who were currently at a local restaurant, alerted them to the event, and brought them to SCP-6876. The task force contacted the closest Foundation Site, which at that point was Area-34 in Boone, North Carolina, and requested a containment team be sent to the location.

Further investigation of the event revealed it to have occurred at the same time as an expedition into SCP-6776 entered the facility. It is currently unknown if these two events are related, but is considered to be highly likely.




Incoming transmission from O5-3. View feed? (Y/N)


> y

Affirmitive. Connecting to live feed.


ERROR: No video detected. Playing audio.




Live Audio Recording


[Ruffling can be heard as O5-3 Heiden puts the recorder into his coat pocket. A toilet can be heard flushing, followed by running water. ]

Heiden: Alright, Frederick. First O5 meeting. You- sorry, we got this. Couldn't forget about you, Akky.

[A noise can be heard as Hayk pats the recorder.]

Heiden: [Deep sigh] Alright, let's go.

[A door creaks open, letting in the noise of Site-01. A nonstop stream of chatter comes through the recorder, as Department Heads and other high-ranking individuals walk through the facility's halls. Behind all the talking, the low hum of the Site's power generators can be heard.]

Unknown Voice: Hey, F- Sorry, Overseer.

O5-3: Cole, hey. How, uh, how's it going?

Dr. Cole Thereven: Good, good. Say, have you talked to the Council yet about bumping up funding for my Department? We really need those extra zeros.

O5-3: Oh, shit, yeah. I forgot about that. I'll try and find a way to bring it up during the Summit today, but no promises.

Dr. Thereven: Sweet, thanks. Just let me know, alright?

O5-3: Yeah…

[O5-3 continues walking towards the Summit room, occasionally stopping for small conversations with other Department Heads. Most of them ask for extra funding or similar requests.]

[As O5-3 gets closer to the Summit room, another, higher-pitched hum joins the generator in the background. The sounds of chatter slowly dissipate until, finally, all that is left is the hum.]

O5-3: Alright.. Let's do this.

[O5-3 zips up the pocket the recorder is in, slightly muffling the noise. After a moment, a beep can be heard, followed by a door opening.]

Unknown Voice: Greetings, Three. May I take your coat?

O5-3: No, thank you. It's rather cold today.

Factotum: As you wish, my Overseer. Follow me.

[O5-3's shoes can be heard clicking against the wooden floor.]

O5-3: Am I the last to arrive?

Factotum: No. We're still awaiting the arrival of a couple of our Overseers. At the moment, only O5-4, O5-9, and O5-12 have arrived. I would recommend taking this time to read over the topics you will be discussing today and preparing anything you would wish to present. I am correct in assuming this is your first interaction with the rest of the O5?

O5-3: Uh, yeah. I was only inaugurated last week.

Factotum: I would also recommend taking this time to acquaint yourself with the other Overseers then. They will be your colleagues for the rest of your tenure at our Foundation, after all.

O5-3: I'll see what I can do then. Thank you.

Factotum: It is my pleasure, Overseer.

[O5-3 stops walking as the Factotum can be heard opening another door.]

Factotum: [Shouting] Annoucing O5-3!

[O5-3 walks into the chamber as the doors shut behind him. The three present Overseers can be heard talking casually.]

O5-5: The new recruit! Come, come, take a seat.

[A seat scrapes against the floor.]

O5-5: Welcome to the Council. I'm Five.

O5-8: Eight.

O5-12: And Twelve. Pleasure to make your acquaintance, Three.

O5-3: Thank you. Where are the others?

O5-8: One and Two always arrive late together, you know how it is.

O5-12: Thirteen will be here when everyone else is.

O5-5: And everyone else'll be here sooner or later. We three are usually the early birds.

O5-8: Hard to be late when you live in this room, huh Twelve?

O5-12: Hah, funny.

O5-5: Have you looked over the topics for today?

O5-3: I skimmed through it while I was getting ready, but I didn't really look into it.

[Sounds of papers shuffling.]

O5-5: Here, take one. Twelve always prepares these little playbills for us.

O5-12: They're not playbills, Four, they're s-

O5-5: Playbills.

O5-3: Thank you.

[O5-3 takes the paper.]

O5-8: We'll leave you to that. Don't be afraid to ask any questions, either. Best you be informed for when we have to vote.

[The three Overseers continually talking amongst themselves, occasionally breaking out into fits of laughter.]

O5-3: [Whispering] Reallocation of Site-43's funding, expansion of Nexus definition, funding for extrastellar expeditions, potential hephaesium stores in Germany… SCP-6876.

O5-3: [Whispering] I'm gonna turn off the recorder until we get to 6876. See you in a bit, Akky.



End of transmission.


> access messages

Opening SCiPNet Messenger…

You have (3) unread messages:

(1). Monthly Site Memo - Site Director Everest
(2). sorry about yesterday - J. Researcher Daya
(3). New Revisions on SCP-6776 - Automated Alert System

Which one would you like to open? Enter (E) to go back to start menu.


> 3

Opening New Revisions on SCP-6776 from Automated Alert System

Redirect detected. Opening link…




Item#: 6776
Level4
Containment Class:
esoteric
Secondary Class:
thaumiel
Disruption Class:
keneq
Risk Class:
caution

reclaimed.jpg
Photograph of Site-19's Tertiary Evacuation Point.

Special Containment Procedures: No changes detected.

Description: No changes detected.

Addendum.6776.1: Abandonment of SCP-6776

No changes detected.

Addendum.6776.2: Site-19 Recuperation Committee

No changes detected.

Addendum.6776.3: 2024 Survey

No changes detected.

Addendum.6776.4: Proliferation MARKED FOR DELETION, DATA BEING TRANSFERED TO RAISA ARCHIVE

SCP-6776 came under the investigation of the Department of Essophysics following the events of Addendum.6776.3, as existing data indicated the presence of an essophysical entity. Multiple essophysical researchers were sent from Site-17 to test for the presence of one. Through observing the local conceptual space of SCP-6776 and deploying irritants known to affect essophysical entities, the existence of an essophysical entity within SCP-6776 was confirmed.

Further investigation pending O5 approval.



Incoming transmission from O5-3. Play audio? (Y/N)


> y

Affirmitive. Connecting to live feed.




Live Audio Recording


O5-1: …ad we could come to a decision on that. What's next on the plate?

O5-2: SCP-6876 and 6776, mx.

O5-1: Right, thank you. O5-8, you got something to say about these two SCPs?

O5-8: Yes. As you may know, the Department of Essophysics recently conducted a test on SCP-6776 to see if there were any essophysical entities present - the contents of the 2024 Survey indicated that there may be. The research team from 17 found evidence of an essophysical entity in 6776. The issue, however, was that they found evidence of a fragment of an essophysical entity, not the whole being itself.

O5-6: So where's the rest of this thing, then?

O5-8: I'm getting there, Six, hold your horses. The team accessed the data that E-55's gear picked up during their survey, specifically the readings for this one type of energy exclusively produced by essophysical entities, and compared it with readings they took when they first got there.

O5-8: They found that the energy level was high when E-55 had first arrived at 6776, indicative of an essophysical presence, but it had suddenly dropped when they opened the facility's main gates. Meaning that, whatever essophysical entity was in there, was free.

O5-10: So we have an essophysical entity just, out there? On the loose?

O5-8: Not ex-

O5-3: Why would it leave at that point, and not when Psi-7 blew a hole in the facility's West Wing?

O5-8: We're still not su-

O5-12: What does 6876 have to do with any of this?

O5-8: If you'd just let me ex-

[The Council devolves into the Overseers talking over each other and asking questions at O5-8. After several minutes of this, a loud buzzer noise can be heard and the Council falls silent.]

O5-13: Silence.

O5-1: Eight, please, continue.

O5-8: Thank you. As I was trying to say, they managed to find trace amounts of this energy leading out of 6776. As we speak, we have a team of essophysical researchers following the path.

O5-2: …And?

O5-8: It seems to be heading to 6876.



> access scp db

Accessing SCiPNet Database

Search via (T)ags, or (N)umber? Choose (T/N)


> n

Please input Search Inquiry:


> 6876

Sorry, this slot appears to be beyond your current clearance level. Would you like to send a request to RAISA to view this slot? (Y/N)


> n
> access info db

Accessing Information Database

Search via (T)itle, (A)author, (S)ite of Origin, or (P)ublication Date? Choose (T/A/S/P)


> T

Please input Search Inquiry:


> Essophysics

Generating Search Results…

(1). List of Known Essophysical Entities - Department of Essophysics, et al.
(2). Essophysics For Beginners - Department of Essophysics
(3). Practical Uses of Essophysics (Or; How Can We Manipulate Essophysics?) - Anonymous

Related SCPs:

(S1). SCP-4260
(S2). SCP-4936
(S3). SCP-6820
(S4). SCP-6996

Which one would you like to access? Enter (E) to go back to start menu.


> 2

Opening essay…

Excerpt opened in side window.

hetgs

Essophysics.png
Essophysics refers to the study of embodiments of universal concepts. These embodiments are akin to gods as they're capable of affecting the concepts they embody, but changes in that concept can also affect them.
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License