Technical Content Policy
The following will be added to the Technical Content Policy:
SCP Titles
Not to be confused with Page Titles, SCP titles are the text that follows its associated link on the SCP Series pages with the following format:
[[[SCP-XXXX]]] - Title of SCP
The link part ([[[SCP-XXXX]]]) represents the Page Title of the article; which should not be used to substitute the metadata title (Title of SCP).
To ensure technical and parsing compatibility, there are limitations to ensure standardization and avoid issues with site technical policy.
Titles must be primarily composed of plain text, and are reasonably accessible to screen readers. For example, "zalgo text", misusing mathematical characters as alternate "fonts", and use of the Private Use Area (PUA) would be prohibited, as well as excessive usage of emoji. However, this does not preclude the use of non-Latin characters when appropriate.
- Example of appropriate usage of non-Basic Latin and Latin-1 Supplement Unicode characters: SCP-5040 - 血の涙 ("Tears of Blood")
- Example of inappropriate usage: SCP-XXXX - 𝐃𝐄𝐀𝐃 𝐁𝐎𝐃𝐘 (Mathematical Bold Capital letters used for stylistic purposes rather than mathematical notation.)
Limited formatting for accurate representation of text may be permitted with Technical Team approval. For instance, use of superscript or subscript for strictly technical information (e.g. "H2O" or "21024 bytes"), or use of the "ruby text" CSS class for CJK-compatible text displays. Use of these features for "stylistic" reasons is not permitted.
In addition:
- Use of CSS modules and/or external stylesheets to supplement titles are prohibited.
- Use of inline formatting are restricted to the following:
- bold (**bold**)
- italic (//italic//)
- underline (__underline__)
- strikethrough (--strikethrough--)
- teletype ({{teletype}})
- Escaping with @@
- color (##blue|color##)
- Use of color syntax to render text invisible, obscure or otherwise difficult to read is prohibited.
- [[span]] with inline CSS (no class). Only the following properties are allowed:
- All font properties
- All background properties (excluding use of external or encoded images)
- padding properties
- All border properties
- color
- All text-decoration properties, text-shadow, letter-spacing, word-spacing
- box-shadow
The Tech Team reserves the right to edit titles and alter formatting if deemed too disruptive or deleterious to accessibility and legibility. Determination of violation is subject to Technical Team's discretion.
Additionally, the Preview Content Policy will be updated to reflect more accurate technical language and rigorous definitions:
Preview Content Policy
The Preview component can be added to the top of the page to expose a hidden but query-able blurb for an article. This may be any text which accurately or usefully describes an article at a glance or in summary. However, there are limitations to ensure standardization and avoid issues with site technical policy.
Blurbs must be primarily composed of plain text, as defined in the SCP Titles section.
- Syntax blocks (e.g. [[div]]), custom CSS (inline or through modules), and use of components are prohibited.
- Use of inline formatting are restricted to the following:
- bold (**bold**)
- italic (//italic//)
- underline (__underline__)
- strikethrough (--strikethrough--)
- teletype ({{teletype}})
- Escaping with @@
- Inline center text (= at the start of a new line.)
- Use of the component is limited to pages in the default category.
- Blurbs must be at least one sentence or equivalent in length.
- Blurbs should describe, summarize, or provide a hook for the article they reference. Off-topic or inappropriate blurbs may be subject to edits at the discretion of the Curation Team.
- Blurbs should not be disruptive, such as containing excessively many paragraphs. This is determined at staff discretion.
- Blurbs may contain links when appropriate, e.g. to a series it's a part of, or to a sequel/prequel article.
The Tech Team reserves the right to edit blurbs as necessary if deemed too disruptive or deleterious to accessibility and legibility. Determination of violation is subject to Technical Team's discretion.
Any titles and blurbs found to be in violation of these are eligible for retroactive edits, rather than being grandfathered in.
Tales Hub
Tales Hub will be updated for better sorting and presented information:
Mockup: https://scp-wiki.wikidot.com/workbench:estrellayoshte
Changes
- Use ListPages-based URL passthrough parameters for sorting by tale tags.
- Display Preview Content, if used.
- Show meta information, being tags, upvotes and numbers of comments.
- Individual pages for each tale categories will be retired.
Additional thoughts
The tales hub update will arrive in two stages, of which this is the first. The filter sorting functionality as seen in the mockup is a minimum viable product, useful for sorting tales by single category.
Future plans will try to allow for more comprehensive, customizable filters (see AO3 or MangaDex, which allows you to choose multiple tags, as well as sorting options, among other things).
This will take some more time, so the primary update will be delivered first, so as to be more useful than the current Tales Hub regardless.
The discussion will last for 7 days, after which the described items will be implemented unless serious concerns are raised. In the event of negative or split opinions on a proposed items, it will not be implemented.
Mainsite Mirror: https://scp-wiki.wikidot.com/forum/t-16739308/