Papers, Pages and Post-it Notes

NOTICE:

This is a component page used internally by the SCP Wiki. It is intended to be used and included on other pages.

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

What this is

A component that displays your text on separate pages, for example the pages of a book.

Made by CroquemboucheCroquembouche.

Other components that simulate pagination:

Usage

On any wiki:

[[include :scp-wiki:component:pages
| medium=vintage-book
| contents=
<h1>Hello, welcome to my book.</h1>
I hope you <em>really enjoy</em> it so that the pain it took to write it was worth it.

]]

There are two parameters for this component.

medium What medium should your text be presented in? This determines the background image of each page, the font, etc. I'm open to adding more options — please contact me (Croquembouche) if you have an idea.
These are documented in detail at the bottom of this page.
contents The contents of your pages. Can include very simple formatting and images.
style CSS styling to inject into the document.

The contents parameter can spread across as many lines as you want.

The contents may not contain the following characters:

  • | (pipe symbol)
  • ` (backtick), unless it's preceded by a backslash (\‘)
  • ]] (two closing brackets), but only if it’s at the end of a line or followed by whitespace


Text formatting

The contents parameter won't be rendered by Wikidot. It goes straight through to a custom parser that I've written myself that spits out HTML.

All that lovely Wikidot syntax that you're used to goes out of the window. Instead, you'll have to write inline HTML.

For example:

  • To make bold text, instead of **text**, write <b>text</b>.
  • To make an em dash, instead of --, write a literal em dash ().
  • To make a horizontal rule, instead of -----, write <hr>.

Unlike HTML, you do not need to write <p>…</p> around each line.


Images

Include images using standard HTML for an image:

<img src="http://scp-wiki.wdfiles.com/local--files/your-page/your-image.png">

You can fix the image to the top or bottom of a page by adding either position="top" or position="bottom". This will fix the image to either the top or the bottom of whatever page it would appear on. This only works for images that are on a line by themselves, not in the middle of text:

<img position="top" src="URL">

To horizontally centre an image, add this CSS to its style attribute directly:

<img style="display: block; margin-left: auto; margin-right: auto;" src="URL">

If an image is too tall to fit on a single page, the bottom of it will be chopped off.


Page breaks

Sometimes you want to say "okay, stop there. Start the next bit on a new page. The rest of this page can be empty."

To do that, on a line by itself, add a page break:

<br class="page-break">

The thing that comes next after a page break will be on the next page. If there's an image with position="bottom" just before the page break, it will still be at the bottom of that page, as expected.


Advanced usage

You can include CSS via the style parameter, and embedded Javascript in the contents parameter.

Using CSS

Any CSS you include in the style parameter will be injected into the pages. Use this to tweak things, add classes that you can use in your content, and change the font (for example).

For example:

[[include :scp-wiki:component:pages
| medium=vintage-book
| style=
@import url('https://fonts.googleapis.com/css2?family=Architects+Daughter');

.page {
font-family: 'Architects Daughter', cursive;
margin: 2rem;
}

.page .red {
color: red;
}
| contents=
This text will appear <span class="red">handwritten</span>.
]]

You can't style this component with a CSS module elsewhere on your article — this is the only way.

Tip! You can add parameters in any order you like, but it's a good idea to put the style parameter above the contents parameters. Your contents parameter will probably be really, really long — you might find it easier to have all the settings and CSS at the top.

Using Javascript

The contents parameter will be parsed as a Javascript template literal, which is why it can't contain a backtick.

Because of that, you can include arbitrary Javascript in the contents parameter inside an embedded expression (${expression}), which will be executed and substituted back into the string. For example:

[[include :scp-wiki:component:pages
| medium=vintage-book
| contents=
The day today is ${new Date().toLocaleString("default", { weekday: "long" })}.
]]

This book will tell the reader the name of the current day.

Should you do this? Probably not. But you can.

Please note that while you can include arbitrary Javascript, the OR operator (||) is unavailable because it's made of pipe symbols, which are forbidden. However, using AND and NOT, you can create an OR yourself: NOT((NOT x) AND (NOT y)) is equivalent to (x OR y). In Javascript, that's !((!x) && (!y)).


Medium Options

The following are your options for the 'medium' parameter.

I am actively soliciting requests for new medium options. I mean, the title of this component is 'Papers, Pages and Post-it Notes', but right now it can only do a vintage book. This component is designed to be as versatile as possible, but right now, it can only do one thing.

If you have any requests for paginated formats, please let me know (Croquembouche).

Each medium has a fixed aspect ratio that determines its height for any browser width.

Medium Background Font y:x Source
plain (default) plain-preview.png Browser default 4:7
vintage-book book.300px.png Libre Baskerville 10:9 Public Domain


Source code

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