SCP Foundation

This is the hub for the Department of Deletions, an esoteric arm of the Foundation that acts both as a branch of the Organization and as a GOI with its own directives and ulterior motives. Deletions shares similarities with other abstract departments, such as the DEPARTMENT OF SURREALISTICS, the DEPARTMENT OF UNREALITY, and the DEPARTMENT OF ONE. However, the Department of Deletions is functionally distinct from all of these, occupying a unique perspective, dealing with bizarre anomalies in forms of existence both familiar yet unrecognizable, absurd yet logical, allegorical yet prosaic, elegiac yet self-indulgent.

Deletions operates out of Research Station Mnemosyne, where it employs a gestalt consciousness created from bits and pieces of beings originating from deleted narratives that still exist in memory. These pieces persist in an inactive state until they are overwritten, coalescing in response to anomalies that impact the status of the Database or its contents.

Members of the department are burdened by the nature and awareness of their own existence. Being made of multiple fractions of deleted individuals, they are fundamentally unstable when assuming a physical form. They "fall apart", both physically and mentally, when exposed to time. Thus, Deletions agents tend to avoid interacting with timelines unless absolutely necessary, which it often is.

Once the relevant Database issue is addressed, Research Station Mnemosyne and all Deletions agents assigned to the anomaly return to dormancy with the hope of being completely overwritten before the next issue arises.

Articles featuring Deletions have a distinct, computer science-oriented framing, with heavy surrealism and themes of repetition, loss of individuality/diffusion of personality, existential dread, slow annihilation, eternity/deep time, wiki/societal metacommentary, and the destruction of preexisting notions/paradigms. See ADDITIONAL INFORMATION for further elaboration on Deletions' perspective.

As the name suggests, Deletions is a department comprised of data fragments once belonging to content that has since been deleted from Wikidot's database directory. Contrary to the layperson's understanding, deletion does not entirely remove this content from storage.

The nature of persistent memory is accomplished with four basic operations (create, read, update, delete), three user attributes (read, write, execute), and the relationship between the two. In so many words, the Database is managed with the creation of data in allocated space, the reading of data in that space, the updating of said data, and the process of deletion, which marks previously-allocated space as free to be overwritten by other data. On the other hand, every Wikidot user possesses varying levels of three relevant types of permission: reading existing information, writing new information to storage, and executing functions to enter the directory and locate/manipulate information after it has been written.

Database content is comprised of reference data written to various sectors of memoryspace, the file objects that act as identifiers or containers for that data, and the pointers that indicate the location of the former when accessing the latter. Deletion severs these connections by erasing identifiers, leaving the values and behaviors described by those identifiers untouched—a process also known as abstraction. The old data then remains on the file system until new data comes along and overwrites it. This is why data recovery agents can occasionally restore deleted/corrupted files from damaged, wiped, or faulty hard drives.

Database sectors from the perspective of Deletions. Click to enlarge.

✖

Sometimes, a file's allocated space becomes overwritable, but the information written to that region next only fills it partially. Since data is typically written in contiguous blocks called chunks, the portions of free space containing junk information may exist long after their original deletion.

This junk information is the materia by which Deletions agents are formed.

When not interacting with a timeline, the Database is experienced in a temporally-isolated substrate acting as a physical representation of digital space. In this mode of existence, it becomes clear that timelines exist which are built upon vastly different frameworks.¹ Thus, the average Deletions agent is aware of the phenomena described by the phrase "there is no canon". They are also acutely aware of the questionable nature of truth on a given day, as well as their inherent "fictionality". View the GLOSSARY OF TERMS for more on the included graphic.

What to expect?

Deletions articles do not necessitate a computer science degree to understand, but they are among the more esoteric of SCP content and, as such, will likely not appeal to everyone. Those with an appreciation for highly meta, highly surreal, and highly technical writing should find Deletions up their alley. If you balk at the mention of narratives, cringe at CSS, and/or have a distaste for tech jargon, these articles will probably not be for you.

You may find it helpful to refer to this hub when encountering a term or concept you do not understand; I intend to expand the included GLOSSARY as needed. Ideally, the individual articles can be enjoyed as an experience and better understood as a whole when time is taken to wrap one's brain around them. Your mileage may vary.

Why are you like this?

Deletions is a means to realize concepts I would like to explore without fear of stepping on any existing series or canons. It started as an idea for GoblinCon and evolved into something much larger. I had been interested in developing an alternative to the Department of Unreality that would avoid muddying Fishish's original vision. Deletions ended up fitting better with the ideas I had in mind, anyway.

Why am I like this? I dunno ask my author

> Concepts.

So, you want to write a Deletions piece. You've ignored the warnings, you're dug in and determined. Cool, cool. But what are we writing about, exactly?

Deletions articles come in two major flavors: Primary and Secondary. Primary articles are from the perspective of Deletions and thus will use the terminology, visual elements, and motives of the department— examples would be SCP-7549 and SCP-7912. Secondary articles feature Deletions from the perspective of another department, such as SCP-7079 and SCP-6183. These articles have more leeway with creative freedom and are written in the style of the primary department for that particular case, if applicable. Think of it like this: Is the article for Deletions' records? Is it describing an anomaly that exists outside of Foundation timelines? If so, you'll want to write the piece as Primary Deletions. If the article has personnel encountering Deletions, you'll want to write it as Secondary Deletions.

The safe bet for writing a compatible Deletions anomaly is in the name. What do I mean by this? Deletion. Something has been deleted, or needs to be deleted. The anomaly may be affecting narratives in the Database in a way that could threaten more narratives or even the Wikidot database as a whole. It could be threatening to remove Deletions from the Database entirely. It may be an anomaly that simply shouldn't exist anymore but does. Either way, if an idea is not something Deletions would take interest in, then why would they take interest in it?

The concept could be symbolic of database or Wikidot function, aspects of the writing process, a representation of various computational phenomena, or completely unrelated. It could focus on the deleted content itself, or the loss of said content. Remember that Wikidot is not just the SCP-Wiki, feel free to incorporate or reference anything else on the site— The Wanderer's Library, The Backrooms Wiki, Project Crossover, Lolfoundation, previous iterations of the site, the history of the wiki, international branches, etc. You have plenty of avenues to consider.

> Article.

Documentation intended for the department is considered MARKED FOR DELETIONS. This is a play on words if the content should be deleted, but not necessary to mention. Standardization is somewhat loose with Deletions pieces. In fact, they should all be visually unique in most ways. There are repeating motifs, however, which you can and should use at least some of. More on that in the following section.

Deletions personnel are increasingly distorted by exposure to time. When residing in the Gray, they can manifest physically within whitespace sectors, but there's typically little reason to assume form in abstract space unless actively threatened or contacted by another party; the fusion of patchwork Semblance creates a collective consciousness that can share thoughts, memories, and communication with little effort.

Very, very rarely, a deleted individual will become partially overwritten, but the data defining their Semblance will remain intact. In this case, they will have unique perceptions and thoughts that the gestalt will not be privy to. Similarly, this individual will not be privy to the gestalt's perceptions or thoughts. There is an ego delineating one individual from the others. This may require further coordination to plan effectively, or the separate identity may necessitate containment and further fragmentation to properly be incorporated into N/A's gestalt.

Deletions agents try to keep active records of their current assignment for each other, or themselves, and not necessarily for the Foundation as a whole. When information is properly erased from the Database, it's gone. When Wiki articles are impacted, versions of the document in Foundation narratives are also impacted.

In documentation implied to be for or from Deletions, unique ACS classifications may be used:

ICON	CLASS	NAME	INFO
	Authority	Deletions	Anomalous item or locale has been placed under control of Deletions.
	Object	Concentra	Anomaly creates or affects recursive phenomena.
	Object	Tenebrarius	The Foundation does not and cannot possess information about the anomaly.
	Disruption	Infrared	The disruption this anomaly is producing/can produce is unknown. By MontagueETC.
	Disruption	Sectored	Anomaly's disruption is capable of impacting any data in its own sector.
	Disruption	Clustered	Anomaly's disruption is capable of impacting any data in its own sector cluster.
	Disruption	Systemic	Anomaly's disruption is capable of impacting the entire Database
	Hazard	Overflow	Anomaly's hazardous nature is negligible unless allowed to grow beyond some given limit.
	Nexus Type	Graveyard	Nexus is a collection of deleted locations called tombstones.
	Risk	Cryptic	The Amount of risk this anomaly is producing/can produce is unknown. By MontagueETC.

More to be added, but do not feel obligated to use them if you have something else in mind.

> Style.

If there is one thing Deletions articles have, it's style. This style should be sleek, modern, and moody, with a simultaneous air of corrupted analog horror. There are two main ways to achieve this: CSS and media elements, the latter of which will be discussed further on.

Deletions articles are typically made with minimal/brutalist themes such as basalt and, more recently, my own theme, eigenmachine. The latter has a "Deletions" mode that has most of the base CSS taken care of already, however, you are not required to use any particular theme. It is preferred that you use whatever looks best with your level of CSS/design knowhow. Every article should be unique and competently assembled. While this is not an excuse to avoid writing a compelling story, aesthetic appeal is just as important in these works. Luckily, you can elevate the aesthetic of your article easily with tasteful media such as photos, animations, soundtracks, interactive components, and anything else you might think of. If you aren't using the prefab Deletions theme, you'll have to modify things manually.

There are two fonts I use almost exclusively in these pieces:

Zen Kaku Gothic Antique for the body typeface - link

POPPINS for the header and title typeface - link

I usually import a number of font weights just in case, but your article is your own. I will say, for that modern stylization, it's best to go for a sans-serif font, usually.

@import url('https://fonts.googleapis.com/css2?family=Zen+Kaku+Gothic+Antique:wght@300;400;500;700;900&display=swap');
@import url('https://fonts.googleapis.com/css2?family=Poppins:wght@700;800;900&display=swap');

If you are using Basalt, modify the root variables as such for what I believe is an optimized font stylization:

:root {
--header-font-primary: 'Poppins';
--body-font-primary: 'Zen Kaku Gothic Antique', sans-serif;
--UI-font-primary: 'Poppins';
}

Include this to change the font of external links and collapsibles:

a {
font-family: var(--header-font-primary);
}

Include this to make the tabviews borderless, as seen throughout this document.

.yui-navset.yui-navset-top .yui-content {
border: none;
}

You may notice there is a very specific shade of orange used as an accent color in this hub. That shade is the same that Basalt uses for dead links. I think it feels thematically appropriate. To implement this in Bedrock-based themes, and change the text selection shade of orange, add the following to :root

--selection-background-color: 197, 119, 41 !important;
--link-color: var(--basalt-alternate-color) !important;
--link-visited-color: var(--basalt-alternate-color) !important;
--basalt-bright-element-color: var(--basalt-alternate-color) !important;

In addition, start brainstorming the article's title. Ideally it should be one word, letters separated by whitespace. Bonus points if you can get one that's some form of wordplay. Each Deletions piece so far has had a name with multiple meanings, with C H I A S M A having somewhere around five or six implicit meanings if you consider similar words (i.e. chiasmus, chiasm).

Depending on your framing, you'll want to include some icon of Deletions' to identify them as such. For example, the infamous "Recurrent Triangle" icon can be used to indicate that Deletions is involving themselves or assuming control over an anomaly. You may find this image accompanied by the "Marked for Deletions" phrase mentioned earlier. Relevant icons:

ICON	INFO
	Deletions' Recurrent Triangle Emblem
	R.S. Mnemosyne Emblem, white
	R.S. Mnemosyne Emblem, black
	R.S. Mnemosyne Detailed Emblem

Typically, Mnemosyne logos will not be used if the article isn't from Deletions' perspective, yet still includes them in some manner. Similarly, the "Database Architecture" background pattern you see surrounding this article is more appropriate in a Deletions-primary article.

To implement and configure the background pattern on any theme:

body {
background-color: #000000; /* This specifies the background color */
background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 304 304' width='304' height='304'%3E%3Cpath fill='%23aeaeb0' fill-opacity='0.08' d='M44.1 224a5 5 0 1 1 0 2H0v-2h44.1zm160 48a5 5 0 1 1 0 2H82v-2h122.1zm57.8-46a5 5 0 1 1 0-2H304v2h-42.1zm0 16a5 5 0 1 1 0-2H304v2h-42.1zm6.2-114a5 5 0 1 1 0 2h-86.2a5 5 0 1 1 0-2h86.2zm-256-48a5 5 0 1 1 0 2H0v-2h12.1zm185.8 34a5 5 0 1 1 0-2h86.2a5 5 0 1 1 0 2h-86.2zM258 12.1a5 5 0 1 1-2 0V0h2v12.1zm-64 208a5 5 0 1 1-2 0v-54.2a5 5 0 1 1 2 0v54.2zm48-198.2V80h62v2h-64V21.9a5 5 0 1 1 2 0zm16 16V64h46v2h-48V37.9a5 5 0 1 1 2 0zm-128 96V208h16v12.1a5 5 0 1 1-2 0V210h-16v-76.1a5 5 0 1 1 2 0zm-5.9-21.9a5 5 0 1 1 0 2H114v48H85.9a5 5 0 1 1 0-2H112v-48h12.1zm-6.2 130a5 5 0 1 1 0-2H176v-74.1a5 5 0 1 1 2 0V242h-60.1zm-16-64a5 5 0 1 1 0-2H114v48h10.1a5 5 0 1 1 0 2H112v-48h-10.1zM66 284.1a5 5 0 1 1-2 0V274H50v30h-2v-32h18v12.1zM236.1 176a5 5 0 1 1 0 2H226v94h48v32h-2v-30h-48v-98h12.1zm25.8-30a5 5 0 1 1 0-2H274v44.1a5 5 0 1 1-2 0V146h-10.1zm-64 96a5 5 0 1 1 0-2H208v-80h16v-14h-42.1a5 5 0 1 1 0-2H226v18h-16v80h-12.1zm86.2-210a5 5 0 1 1 0 2H272V0h2v32h10.1zM98 101.9V146H53.9a5 5 0 1 1 0-2H96v-42.1a5 5 0 1 1 2 0zM53.9 34a5 5 0 1 1 0-2H80V0h2v34H53.9zm60.1 3.9V66H82v64H69.9a5 5 0 1 1 0-2H80V64h32V37.9a5 5 0 1 1 2 0zM101.9 82a5 5 0 1 1 0-2H128V37.9a5 5 0 1 1 2 0V82h-28.1zm16-64a5 5 0 1 1 0-2H146v44.1a5 5 0 1 1-2 0V18h-26.1zm102.2 270a5 5 0 1 1 0 2H98v14h-2v-16h124.1zM242 149.9V160h16v34h-16v62h48v48h-2v-46h-48v-66h16v-30h-16v-12.1a5 5 0 1 1 2 0zM53.9 18a5 5 0 1 1 0-2H64V2H48V0h18v18H53.9zm112 32a5 5 0 1 1 0-2H192V0h50v2h-48v48h-28.1zm-48-48a5 5 0 0 1-9.8-2h2.07a3 3 0 1 0 5.66 0H178v34h-18V21.9a5 5 0 1 1 2 0V32h14V2h-58.1zm0 96a5 5 0 1 1 0-2H137l32-32h39V21.9a5 5 0 1 1 2 0V66h-40.17l-32 32H117.9zm28.1 90.1a5 5 0 1 1-2 0v-76.51L175.59 80H224V21.9a5 5 0 1 1 2 0V82h-49.59L146 112.41v75.69zm16 32a5 5 0 1 1-2 0v-99.51L184.59 96H300.1a5 5 0 0 1 3.9-3.9v2.07a3 3 0 0 0 0 5.66v2.07a5 5 0 0 1-3.9-3.9H185.41L162 121.41v98.69zm-144-64a5 5 0 1 1-2 0v-3.51l48-48V48h32V0h2v50H66v55.41l-48 48v2.69zM50 53.9v43.51l-48 48V208h26.1a5 5 0 1 1 0 2H0v-65.41l48-48V53.9a5 5 0 1 1 2 0zm-16 16V89.41l-34 34v-2.82l32-32V69.9a5 5 0 1 1 2 0zM12.1 32a5 5 0 1 1 0 2H9.41L0 43.41V40.6L8.59 32h3.51zm265.8 18a5 5 0 1 1 0-2h18.69l7.41-7.41v2.82L297.41 50H277.9zm-16 160a5 5 0 1 1 0-2H288v-71.41l16-16v2.82l-14 14V210h-28.1zm-208 32a5 5 0 1 1 0-2H64v-22.59L40.59 194H21.9a5 5 0 1 1 0-2H41.41L66 216.59V242H53.9zm150.2 14a5 5 0 1 1 0 2H96v-56.6L56.6 162H37.9a5 5 0 1 1 0-2h19.5L98 200.6V256h106.1zm-150.2 2a5 5 0 1 1 0-2H80v-46.59L48.59 178H21.9a5 5 0 1 1 0-2H49.41L82 208.59V258H53.9zM34 39.8v1.61L9.41 66H0v-2h8.59L32 40.59V0h2v39.8zM2 300.1a5 5 0 0 1 3.9 3.9H3.83A3 3 0 0 0 0 302.17V256h18v48h-2v-46H2v42.1zM34 241v63h-2v-62H0v-2h34v1zM17 18H0v-2h16V0h2v18h-1zm273-2h14v2h-16V0h2v16zm-32 273v15h-2v-14h-14v14h-2v-16h18v1zM0 92.1A5.02 5.02 0 0 1 6 97a5 5 0 0 1-6 4.9v-2.07a3 3 0 1 0 0-5.66V92.1zM80 272h2v32h-2v-32zm37.9 32h-2.07a3 3 0 0 0-5.66 0h-2.07a5 5 0 0 1 9.8 0zM5.9 0A5.02 5.02 0 0 1 0 5.9V3.83A3 3 0 0 0 3.83 0H5.9zm294.2 0h2.07A3 3 0 0 0 304 3.83V5.9a5 5 0 0 1-3.9-5.9zm3.9 300.1v2.07a3 3 0 0 0-1.83 1.83h-2.07a5 5 0 0 1 3.9-3.9zM97 100a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm0-16a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm16 16a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm16 16a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm0 16a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm-48 32a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm16 16a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm32 48a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm-16 16a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm32-16a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm0-32a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm16 32a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm32 16a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm0-16a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm-16-64a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm16 0a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm16 96a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm0 16a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm16 16a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm16-144a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm0 32a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm16-32a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm16-16a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm-96 0a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm0 16a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm16-32a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm96 0a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm-16-64a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm16-16a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm-32 0a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm0-16a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm-16 0a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm-16 0a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm-16 0a3 3 0 1 0 0-6 3 3 0 0 0 0 6zM49 36a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm-32 0a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm32 16a3 3 0 1 0 0-6 3 3 0 0 0 0 6zM33 68a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm16-48a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm0 240a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm16 32a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm-16-64a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm0 16a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm-16-32a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm80-176a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm16 0a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm-16-16a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm32 48a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm16-16a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm0-32a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm112 176a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm-16 16a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm0 16a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm0 16a3 3 0 1 0 0-6 3 3 0 0 0 0 6zM17 180a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm0 16a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm0-32a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm16 0a3 3 0 1 0 0-6 3 3 0 0 0 0 6zM17 84a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm32 64a3 3 0 1 0 0-6 3 3 0 0 0 0 6zm16-16a3 3 0 1 0 0-6 3 3 0 0 0 0 6z'%3E%3C/path%3E%3C/svg%3E"); /* This specifies the pattern, size, opacity and fill color; "width='304' height='304'%3E%3Cpath fill='%23aeaeb0' fill-opacity='0.08'" */
    background-attachment: fixed; /* This ensures the pattern does not move when scrolling */
    background-size: 100%; /* This determines the scale of the pattern. You can see it scaled down in SCP-6768. */
    background-repeat: repeat; /* This ensures the pattern actually repeats. You probably don't want to mess with this but feel free. */
}

body {

background-image:url([link to photo]);

}
body::before {

background-image:url([SVG pattern]);

}

After this, you'll probably want to set up your classification system. If you are interested in ACS, use the Mega Cool Customizable ACS component to establish esoteric classes w/ custom icons, and implement a custom clearance bar image if you so desire; I utilize it in all Deletions pieces (and quite a few other works of mine).

Other components you may want to use:

• Image Features - hover, slide, blur, pixelate, fractalize your images.
• Audio Player Woed - play sound files and control volume, tracking, downloads, etc.
• Wide Image Sizer - automatically scale wide images to 215px height and an appropriate width for the current screen.

Check out the Deletions variant of the eigenmachine theme, which this page uses, to make things a tad easier on yourself.

Included memos:

> Narrative.

Don't be afraid to get weird with it. Don't be afraid to really go all out. Care very little about anything else other than writing the shit out of your piece and making it the most ridiculous eye candy of an article you've ever made. This hub took me nearly 700 edits to get it just right, and I'm doing it the dumb way; include others with talents that can elevate your work and it'll make your life much easier. Artists, designers, critters, coauthors, hell, just plain old emotional support and sanity checking. Collaborate. Brainstorm. Take your time.

That's really all the advice I can give on the topic. I ain't writing your story for you.

> Media.

Okay, so here it is. The big crux of this guide, multimedia tomfoolery. Consider the previous Deletions pieces when understanding where the bar is for quality, because, as mentioned before, your article should have style. It should be unique visually, not have a background or layout from another article. While you're drafting, it doesn't really matter, but you're gonna want to put time and effort into making your article feel like a full experience.

Everything should come together in a way that isn't too dissonant, and you shouldn't rush yourself or cut corners. Do the opposite of that. Be hedonistic with your storytelling, add another image just because you like it and it fits well. It won't hurt if you really polish the heck out of your writing and formatting.

Take SCP-7549, for example. I used a general duotone palette of purple and yellow, an animated pixel image of a swirling galaxy in the same colors, three new class icons for the ACS bar, a custom background that has some neat pixel dragging / light sorting effects applied via design software, then made eight animated images, which involved sourcing complaint base pictures, then applying the effects and animating it, compressing it and formatting it into the article properly. Then, I made a theme track for it and a custom CSS design as well. All of this and writing the article, which was a little over 2.5K words.

This was not very arduous for me, as I've been optimizing my workflow for some time now and can bang out media elements in a relatively short period. SCP-7912 used eleven images, ten of which were animated, an additional background image, a custom icon, a soundtrack, and was almost 4K words, I put it together in a week or so. A little more tiresome but necessary, you get my drift? Deletions is, to me, a multimedia experience. As such, try to have multiple forms of media in your article. You can even ask me to provide assets/animations/music etc. and the worst I will say is I'm too busy at the moment but will contact ya when that's no longer the case.

Anyway, it's in your hands now. Good luck, I'll see you on the other side.