What this is
A bunch of miscellaneous CSS 'improvements' that I,
Croquembouche, 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.
.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; }
Ever wanted to run a contest? Now, you can. Well, you could before, too. Anyone can post a contest hub at any time. There is no rule explicitly preventing this. There is no written policy page for rules regarding contest hubs, as far as I can tell. I didn't have a ton of time to research.
HOWEVER: I am legally obligated to inform you that you should not attempt to run any sort of unofficial contest without speaking to the Community Outreach Team first. They would really prefer you didn't attempt to run a contest without their approval. I don't think they'd stop you, but many of the things you'd want to do in order to run a serious, quality contest cannot be done without their assistance and oversight.
Anyway. Point is, you could have run a contest before and you didn't. But now, some funny man whose name is literally placeholder is saying you can do it competitively. And there's no way you're turning that down. I mean, you've participated in worse contests.
Come on, don't lie to me, I know you have. I'm scrubbing through your wikidot user history right now. Memecon? Really? Like anything good was going to come out of that.
How to Enter CONTEST CONTEST
1. Within the duration from 12:01 AM EST 6 January 2023 to 11:59 PM EST 12 January 2023, post a page to the SCP Wiki which
- successfully qualifies for the contest tag, and
- still exists at 12:01 AM EST 20 January 2023.
2. Due to the nature of the CONTEST CONTEST, we will unfortunately not be allowing art entries. Like, not just visual art — no art, at all. Your entry must not include anything artistic. Your entry can be an Art Contest, though, that's fine! Oh yeah, and, no theme or component pages as entries either. Apologies for the confusion.
IMPORTANT DATES
POSTING BEGINS: 12:01 AM EST 6 January 2023
POSTING CLOSES: 11:59 PM EST 12 January 2023
RESULTS DECIDED: 12:01 AM EST 20 January 2023
ACTUAL BIRTH DATE OF JESUS CHRIST: 1:00 AM IST 6 April 6 Anno Domini, probably.
ENTRIES
(in random order)
RULES
1. Highest-rated CONTEST CONTEST entry at RESULTS DECIDED time wins. (Visual) Art Contest entries are a separate category with a separate winner because purely visual art is fundamentally different from all other artforms and cannot be compared with them. All non-Art Contests are in the same category, though.
2. The following statement must appear at the top of your entry, right below your rating module:
I, <user not logged in>, fully recognize that CONTEST CONTEST by Placeholder McD is a joke page, and was created without intent to hurt, harm, cause problems, or be unsportsmanlike. I acknowledge that Placeholder McD has discouraged me from posting a Contest Hub without consulting the Community Outreach Team. I understand that the content of CONTEST CONTEST is purely satirical and should not be taken personally. In copying this statement to the top of my page, I admit that what will follow is entirely my fault, and Placeholder McD is in no way responsible for my actions.
Neololfoundation. Cheese Grater. Bottom Text.
Oh, hey, dude, you're currently logged out of your wikidot account. Yeah, it does that sometimes. Site's falling apart.
3. You are permitted to edit your CONTEST CONTEST entry, but not wholly replace it. Although you are allowed to add and remove sections to your CONTEST CONTEST entry, ultimately the central idea of your CONTEST CONTEST entry should remain the same. This also means that any edits that would comprehensively replace or overwrite your original CONTEST CONTEST entry will be prohibited. In the case of having a CONTEST CONTEST entry with planned updates or something similar that we have seen in prior contests, a full and thorough outline of said updates must be presented to a CONTEST CONTEST marshal before the end of the posting period. This is to help ensure that CONTEST CONTEST contestants are given the freedom to be creative with their CONTEST CONTEST entries while at the same time preventing the possibility of some CONTEST CONTEST contestants being able to obtain "additional time" to work on their CONTEST CONTEST entry after the end of the posting period. If unsure over whether an edit would violate these terms, please consult the following flowchart.
4. Any contestant who takes unusual and/or negative actions to increase their vote total, or decrease that of their competitors, will be awarded bonus points.
5. If you have any questions about CONTEST CONTEST, feel free to message one of my agents,
HarryBlank,
Liryn, or
Ralliston. They're the CONTEST CONTEST Marshalls.
6. If you have any questions about being a Contest Marshall, feel free to message the Community Outreach Team. They're the CONTEST CONTEST Marshall Marshalls.
7. If you're a contestant looking to contest the opinions of the CONTEST CONTEST Marshall Marshalls, please feel free to contact the Contest Marshmallow.
TAGGING
Since this page is my ColdpostCon Entry, I was unable to have it reviewed by Community Outreach and, as such, could not arrange creation of the contestcontest tag prior to CONTEST CONTEST. So just do whatever's required to obtain the regular ol' contest tag on your entry.
Since I can't use Listpages to target only contest pages created between certain dates, they won't be listed here unless I edit the page, which I'm not allowed to do until ColdpostCon has concluded. So, on 12 January, between the end of ColdpostCon's Voting Period and the end of CONTEST CONTEST's Posting Period, I'll update this page to reflect all the CONTEST CONTEST entries! The entries currently on this page are placeholders to entertain you until then.
Special thanks to
Placeholder McD for making the CONTEST CONTEST Hub Banner image in preparation for wasting everyone's time with this page. Special apologies to
stormbreath,
Modulum,
Naepic,
WhiteGuard, and several members of the SCP Official Staff Server Discord for badgering you with whether or not I could genuinely make this a contest. I am so, so sorry. This is a joke tale page. This is a joke tale page. Please, I am begging you, do not blemish my perfect record with a Disc thread based on the contents of this page. Thank you and good night.
SOLO WORKS
Author Page |
PLACEHOLDER STAFF DOCUMENT |
+110 |
edited 28 Dec 2022 15:17
commented 03 Feb 2023 01:59 |
SCP Articles |
SCP-INTEGER |
+543 |
edited 25 Dec 2022 05:16
commented 28 Feb 2023 01:58 |
SCP-7579 |
+216 |
edited 25 Dec 2022 03:27
commented 02 Jan 2023 18:23 |
McDoctorate's Proposal |
+214 |
edited 25 Dec 2022 03:21
commented 22 May 2023 04:29 |
SCP-5241 |
+199 |
edited 20 Jan 2023 18:44
commented 14 Feb 2023 09:27 |
SCP-2011-EX |
+169 |
edited 29 Jan 2023 05:44
commented 14 Dec 2022 14:18 |
SCP-5756 |
+127 |
edited 25 Dec 2022 03:34
commented 25 Dec 2022 17:17 |
SCP-6416 |
+119 |
edited 23 Mar 2023 13:48
commented 23 Mar 2023 13:45 |
SCP-5485 |
+98 |
edited 03 Jan 2023 15:59
commented 13 Sep 2021 05:59 |
SCP-6276 |
+122 |
edited 26 Apr 2023 08:04
commented 07 Oct 2022 23:05 |
Tales |
CONTEST CONTEST |
+135 |
edited 06 Jan 2023 03:59
commented 08 Feb 2023 06:58 |
PLACEHOLDER |
+134 |
edited 25 Dec 2022 04:02
commented 04 Feb 2022 22:41 |
AI Classification Guide |
+118 |
edited 25 Dec 2022 04:05
commented 30 Jan 2022 20:07 |
BLANK |
+95 |
edited 25 Dec 2022 04:09
commented 03 Feb 2023 01:34 |
CAST |
+76 |
edited 25 Dec 2022 04:12
commented 04 Apr 2023 19:18 |
Supplements |
Abridged Retirement Proposals |
+57 |
edited 07 Jun 2023 14:07
commented 13 Apr 2023 13:18 |
Themes |
BLANKSTYLE CSS |
+59 |
edited 17 May 2023 21:24
commented 12 Dec 2021 10:16 |
PLACESTYLE CSS |
+38 |
edited 17 May 2023 21:25
commented 10 Mar 2021 00:14 |
Retro AIAD Theme |
+37 |
edited 11 Mar 2021 08:50
commented 04 May 2021 12:53 |
COLLAB WORKS
SCP-6820 |
+755 |
edited 26 May 2023 14:11
commented 28 Mar 2023 00:07 |
SCP-6500 |
+714 |
edited 03 Jan 2023 10:08
commented 09 May 2023 20:56 |
SCP-6747 |
+324 |
edited 26 May 2023 14:09
commented 03 May 2023 23:22 |
SCP-6659 |
+281 |
edited 26 May 2023 14:09
commented 02 Jun 2023 18:49 |
SCP-6488 |
+275 |
edited 23 May 2023 09:54
commented 20 Jan 2023 04:54 |
FRAGMENTED / COMPILED |
+64 |
edited 20 Jan 2023 18:50
commented 10 Nov 2021 00:26 |
Ihp/Locke Proposal |
+442 |
edited 03 May 2023 15:17
commented 29 Apr 2023 17:59 |
SCP-5956 |
+330 |
edited 20 Jan 2023 17:58
commented 25 Dec 2022 17:14 |
SCP-7555 |
+137 |
edited 30 Jan 2023 11:53
commented 09 Mar 2023 13:37 |
ADMONITION |
+293 |
edited 02 Jun 2023 06:20
commented 26 Jan 2023 23:07 |
Site-17 Deepwell Catalog |
+209 |
edited 13 Apr 2023 18:05
commented 01 May 2023 16:41 |
No Return Hub |
+165 |
edited 04 Jun 2023 06:34
commented 24 Apr 2022 15:02 |
Project Isorropía |
+164 |
edited 08 Jun 2023 18:07
commented 08 Jun 2023 19:47 |
SCP-5841 |
+102 |
edited 09 Dec 2022 23:01
commented 19 Oct 2020 20:50 |
I, Hub (April Fools) |
+88 |
edited 25 Feb 2023 19:08
commented 06 Feb 2022 12:10 |
SCP-5243 Video Transcripts |
+85 |
edited 26 Jan 2023 10:34
commented 03 Mar 2023 17:35 |
A little goes a long way. If you've enjoyed my work, you're not a student, and are otherwise financially stable, please consider donating.
More-by page code borrowed in part from
Lt Flops. Thank you, Flops!
Cite this page as:
For more information, see Licensing Guide.
Licensing Disclosures
Title: CONTEST CONTEST BANNER
Filename: TlyH5oe.png
Author:
Placeholder McD
License: CC BY-SA 3.0
Source Link: Imgur
Notes: Derivative of the following works:
Filename: Confetti600x269.png
Author: Agency "Mann beißt Hund" for WMDE
License: CC BY-SA 4.0
Source Link: Wikimedia Commons
Filename: Dept of Homeland Security Distinguished Service Medal.png
Author: U. S. Army
License: Public Domain
Source Link: Wikimedia Commons
Filename: Partyhat_icone.png
Author: Polylerus
License: CC BY-SA 3.0
Source Link: Wikimedia Commons
Title: CONTEST CONTEST FLOWCHART
Filename: ToPVbk6.png
Author:
Placeholder McD
License: CC BY-SA 3.0
Source Link: Imgur
Notes: Derivative of the following works:
Title: Editing Flowchart
Filename: flowchart.png
Author:
WhiteGuard
License: CC BY-SA 3.0
Source Link: SCP-7000 Contest Hub
Significant portions of textual, structural and formatting elements are derived from the ColdpostCon hub, the SCP-7000 Contest hub, and various other SCP Wiki Contest hubs.
For more information about on-wiki content, visit the Licensing Master List.