Backrooms Wiki
Advertisement

Introduction

Wikitext is incredibly important for spicing up wiki pages, and it is often underused despite its usefulness. This guide aims to make Wikitext more widely used by the general population of editors. Not everything is achievable with Wikitext alone; however, many features to a page that expand past simple text can be used fairly easily. If something is not on this list, first try to figure out a Wikitext solution and put it on this page, or contact Egglord1 on adding HTML code to your page. HTML code is much more expansive in use than Wikitext, however it can be more complicated.

Wikitext can only be used in the Source Editor, so all Wikitext here (except in examples) will be written in the visual editor.

Basic Page Composition

Headings

Headings are meant as titles for major page sections, such as a level description, or a section listing colonies. Think of these as chapter titles for a book. For example, the "Basic Page Composition" header directly above is a Heading. Surrounding text with two equal signs on both sides makes it a heading, which will display larger than other text and add it to the table of contents for the page. These are formatted in the Source Editor as:

=Example Heading=

Sub-Headings

Sub-Headings are meant to further organize pages, as a sub-category under Headings. For example, the text above reading "Headings" and "Sub-Headings" are both formatted as Sub-Headings, under the main Heading of "Basic Page Composition". These are formed with three equal signs on both sides of text, formatted as:

===Example Sub-Heading===

Sub-Heading 2

Sub-Heading 2 is meant for very finely organizing a page; it is basically the same concept as a Sub-Heading being a sub-category to a Heading, but instead it is a sub-category to a Sub-Heading. It is less common to reach this level of organization in most pages, but if it is warranted, it can prove to be a useful tool. Sub-Heading 2 is formatted as:

====Example Sub-Heading 2====

Page Titles

You may be wondering; if headings are two equal signs and sub-headings are three equal signs and so on, what does one equal sign result in? Well, surrounding text with one equal sign results in a Page Title, which makes the text massive and distracting. These should be avoided in pages, as contrary to their name, they don't change the actual title of the page, they just make very large text which shouldn't be used. For organization's sake, a Page Title will not be used here, but an example of it can be found at the top of the page; text surrounded by one equal sign on both sides will look the way "Backrooms Wikitext Guide" does.

Basic Text Editing

Surrounding text with 3 apostrophes will bold text, and 2 apostrophes will italicize the text (or do both if there are 5 apostrophes, but this will almost never be used). This is incredibly simple and the most basic part of text editing. Using apostrophes in the Source Editor isn't even required for this; one can just bold and italicize text through the top formatting options in the Visual Editor.

Bold Text

Bold text in articles is primarily used to bold the name of a specific level or Entity whenever it is mentioned in its article. For example, in Level 0's article, every time "Level 0" is said, it is bolded. This allows for better organization and gives a cleaner feel to the page.

Bold text in Source Editor: '''Text'''

Result: Text

Italicized Text

Italicized text is less commonly used in pages, but it still has its uses. Stressing a point in an article is better achieved with italicized text because fully capitalizing it like "Do NOT, by any means, enter this level" looks unfitting in articles. If something is that important to stress, it is recommended to italicize it.

Italicized text in Source Editor: ''Text''

Result: Text

Intermediate Text Editing

Text can be further edited in many interesting and useful ways, such as underlining, strikethrough, or code. These are less commonly used in articles, but can still serve a purpose every once in a while (avoid overusing them).

Underlining

While being one of the three simple formatting options listed at the top of the Visual Editor, underlined text is written in the Source Editor by surrounding text with <u> and </u>, rather than with a number of apostrophes.

Underlined text in Source Editor: <u>Text</u>

Result: Text

Strikethrough

If you want text that has been crossed out, surround it with <s> and </s>. This can be used for information that has, in-lore, been changed following a new discovery.

Strikethrough text in Source Editor: <s>Text</s>

Result: Text

Code Text

Surrounding text with <code> and </code> will change its font to a more computer/code looking style. This can be used for many different things, or in rare circumstances, even change the font of the entire page if one wants.

Code text in Source Editor: <code>Text</code>

Result: Text

Advanced Page Composition

Tabbers

Simply using headers and normal text may not always cut it in longer pages. Tabbers are very powerful tools meant to nicely shrink down information into sleek and readable chunks. We will get to how and when to use them after this demonstration.

Tabbers in Source Editor:

<tabber>

|-| Tabbers=

Word

|-| Look=

Word2

|-| Like=

Word3

|-| This=

Word4

</tabber>

This text in the Source Editor would yield the following format:

Word1

Word2

Word3

Word4

Anything can be put inside tabbers, including other tabbers. However, they should be used with a bit of caution. First of all, if a page is built for a header system, it may be meant to be read from top to bottom. However, tabbers have the reader read laterally between tabs, and that style may clash. In addition, tabbers take some of the "meat" from your page, meaning that it substantially decreases the length of it. If your page is extremely long and hard to read top to bottom, this is a benefit, but if your page is under 6,000 characters you might not have enough text to warrant tabbers. Say you have 1,000 characters each for the intro and ending (we'll get into that later), and you have 5 tabs. That's 800 characters per tab. This can be extremely underwhelming, as somebody clicks on a tab expecting an in-depth look at the subject matter, and would instead see only a single paragraph. This makes it seem like your page has little content, even if it has a decent amount, and overall makes it feel half-baked.

If tabbers would still benefit your page, keep in mind that the actual first section of your article has to have meat to it as well; if all of your content is crammed into a single set of tabbers, it will feel a little off. A page should have a cohesive intro, content, and some sort of text to conclude it. A conclusion can be content that is associated with finality, such as an "Entrances and Exits" section, or something else to ease the reader into the end of the page.

Here is an example page utilizing tabbers:

[Introductory text and content][Introductory text and content][Introductory text and content][Introductory text and content][Introductory text and content][Introductory text and content][Introductory text and content][Introductory text and content][Introductory text and content][Introductory text and content][Introductory text and content][Introductory text and content][Introductory text and content][Introductory text and content]

[Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview] [Overview]

[c̵̨̲̀̋r̵̠̗̔͗͘͘e̴͖̔é̷̲͇p̸̫͖̪͇̂̂̚ͅy̴͚̞̎̊̋ ̴̧̼̘̚w̷̻̳̏͂̂h̵̯̀o̶̗͋̅̌͌a̷̬̘̻͒a̸̦̻̪̱̎̈́͊͋̔a̴̤͈̿͑͂̅͝ ̸̛̙̬̞̝͊̒̄ş̷̞̗̞̜̽p̷̡̹̼̰͈͒̚o̴̰͐̈o̴̯͚̮̔͐̅k̷̼̝͇̯̯͊̃̿͝y̵̧̜̻͇̌̐̈́͘͝] [c̵̨̲̀̋r̵̠̗̔͗͘͘e̴͖̔é̷̲͇p̸̫͖̪͇̂̂̚ͅy̴͚̞̎̊̋ ̴̧̼̘̚w̷̻̳̏͂̂h̵̯̀o̶̗͋̅̌͌a̷̬̘̻͒a̸̦̻̪̱̎̈́͊͋̔a̴̤͈̿͑͂̅͝ ̸̛̙̬̞̝͊̒̄ş̷̞̗̞̜̽p̷̡̹̼̰͈͒̚o̴̰͐̈o̴̯͚̮̔͐̅k̷̼̝͇̯̯͊̃̿͝y̵̧̜̻͇̌̐̈́͘͝] [c̵̨̲̀̋r̵̠̗̔͗͘͘e̴͖̔é̷̲͇p̸̫͖̪͇̂̂̚ͅy̴͚̞̎̊̋ ̴̧̼̘̚w̷̻̳̏͂̂h̵̯̀o̶̗͋̅̌͌a̷̬̘̻͒a̸̦̻̪̱̎̈́͊͋̔a̴̤͈̿͑͂̅͝ ̸̛̙̬̞̝͊̒̄ş̷̞̗̞̜̽p̷̡̹̼̰͈͒̚o̴̰͐̈o̴̯͚̮̔͐̅k̷̼̝͇̯̯͊̃̿͝y̵̧̜̻͇̌̐̈́͘͝] [c̵̨̲̀̋r̵̠̗̔͗͘͘e̴͖̔é̷̲͇p̸̫͖̪͇̂̂̚ͅy̴͚̞̎̊̋ ̴̧̼̘̚w̷̻̳̏͂̂h̵̯̀o̶̗͋̅̌͌a̷̬̘̻͒a̸̦̻̪̱̎̈́͊͋̔a̴̤͈̿͑͂̅͝ ̸̛̙̬̞̝͊̒̄ş̷̞̗̞̜̽p̷̡̹̼̰͈͒̚o̴̰͐̈o̴̯͚̮̔͐̅k̷̼̝͇̯̯͊̃̿͝y̵̧̜̻͇̌̐̈́͘͝] [c̵̨̲̀̋r̵̠̗̔͗͘͘e̴͖̔é̷̲͇p̸̫͖̪͇̂̂̚ͅy̴͚̞̎̊̋ ̴̧̼̘̚w̷̻̳̏͂̂h̵̯̀o̶̗͋̅̌͌a̷̬̘̻͒a̸̦̻̪̱̎̈́͊͋̔a̴̤͈̿͑͂̅͝ ̸̛̙̬̞̝͊̒̄ş̷̞̗̞̜̽p̷̡̹̼̰͈͒̚o̴̰͐̈o̴̯͚̮̔͐̅k̷̼̝͇̯̯͊̃̿͝y̵̧̜̻͇̌̐̈́͘͝] [c̵̨̲̀̋r̵̠̗̔͗͘͘e̴͖̔é̷̲͇p̸̫͖̪͇̂̂̚ͅy̴͚̞̎̊̋ ̴̧̼̘̚w̷̻̳̏͂̂h̵̯̀o̶̗͋̅̌͌a̷̬̘̻͒a̸̦̻̪̱̎̈́͊͋̔a̴̤͈̿͑͂̅͝ ̸̛̙̬̞̝͊̒̄ş̷̞̗̞̜̽p̷̡̹̼̰͈͒̚o̴̰͐̈o̴̯͚̮̔͐̅k̷̼̝͇̯̯͊̃̿͝y̵̧̜̻͇̌̐̈́͘͝] [c̵̨̲̀̋r̵̠̗̔͗͘͘e̴͖̔é̷̲͇p̸̫͖̪͇̂̂̚ͅy̴͚̞̎̊̋ ̴̧̼̘̚w̷̻̳̏͂̂h̵̯̀o̶̗͋̅̌͌a̷̬̘̻͒a̸̦̻̪̱̎̈́͊͋̔a̴̤͈̿͑͂̅͝ ̸̛̙̬̞̝͊̒̄ş̷̞̗̞̜̽p̷̡̹̼̰͈͒̚o̴̰͐̈o̴̯͚̮̔͐̅k̷̼̝͇̯̯͊̃̿͝y̵̧̜̻͇̌̐̈́͘͝] [c̵̨̲̀̋r̵̠̗̔͗͘͘e̴͖̔é̷̲͇p̸̫͖̪͇̂̂̚ͅy̴͚̞̎̊̋ ̴̧̼̘̚w̷̻̳̏͂̂h̵̯̀o̶̗͋̅̌͌a̷̬̘̻͒a̸̦̻̪̱̎̈́͊͋̔a̴̤͈̿͑͂̅͝ ̸̛̙̬̞̝͊̒̄ş̷̞̗̞̜̽p̷̡̹̼̰͈͒̚o̴̰͐̈o̴̯͚̮̔͐̅k̷̼̝͇̯̯͊̃̿͝y̵̧̜̻͇̌̐̈́͘͝] [c̵̨̲̀̋r̵̠̗̔͗͘͘e̴͖̔é̷̲͇p̸̫͖̪͇̂̂̚ͅy̴͚̞̎̊̋ ̴̧̼̘̚w̷̻̳̏͂̂h̵̯̀o̶̗͋̅̌͌a̷̬̘̻͒a̸̦̻̪̱̎̈́͊͋̔a̴̤͈̿͑͂̅͝ ̸̛̙̬̞̝͊̒̄ş̷̞̗̞̜̽p̷̡̹̼̰͈͒̚o̴̰͐̈o̴̯͚̮̔͐̅k̷̼̝͇̯̯͊̃̿͝y̵̧̜̻͇̌̐̈́͘͝] [c̵̨̲̀̋r̵̠̗̔͗͘͘e̴͖̔é̷̲͇p̸̫͖̪͇̂̂̚ͅy̴͚̞̎̊̋ ̴̧̼̘̚w̷̻̳̏͂̂h̵̯̀o̶̗͋̅̌͌a̷̬̘̻͒a̸̦̻̪̱̎̈́͊͋̔a̴̤͈̿͑͂̅͝ ̸̛̙̬̞̝͊̒̄ş̷̞̗̞̜̽p̷̡̹̼̰͈͒̚o̴̰͐̈o̴̯͚̮̔͐̅k̷̼̝͇̯̯͊̃̿͝y̵̧̜̻͇̌̐̈́͘͝] [c̵̨̲̀̋r̵̠̗̔͗͘͘e̴͖̔é̷̲͇p̸̫͖̪͇̂̂̚ͅy̴͚̞̎̊̋ ̴̧̼̘̚w̷̻̳̏͂̂h̵̯̀o̶̗͋̅̌͌a̷̬̘̻͒a̸̦̻̪̱̎̈́͊͋̔a̴̤͈̿͑͂̅͝ ̸̛̙̬̞̝͊̒̄ş̷̞̗̞̜̽p̷̡̹̼̰͈͒̚o̴̰͐̈o̴̯͚̮̔͐̅k̷̼̝͇̯̯͊̃̿͝y̵̧̜̻͇̌̐̈́͘͝] [c̵̨̲̀̋r̵̠̗̔͗͘͘e̴͖̔é̷̲͇p̸̫͖̪͇̂̂̚ͅy̴͚̞̎̊̋ ̴̧̼̘̚w̷̻̳̏͂̂h̵̯̀o̶̗͋̅̌͌a̷̬̘̻͒a̸̦̻̪̱̎̈́͊͋̔a̴̤͈̿͑͂̅͝ ̸̛̙̬̞̝͊̒̄ş̷̞̗̞̜̽p̷̡̹̼̰͈͒̚o̴̰͐̈o̴̯͚̮̔͐̅k̷̼̝͇̯̯͊̃̿͝y̵̧̜̻͇̌̐̈́͘͝] [c̵̨̲̀̋r̵̠̗̔͗͘͘e̴͖̔é̷̲͇p̸̫͖̪͇̂̂̚ͅy̴͚̞̎̊̋ ̴̧̼̘̚w̷̻̳̏͂̂h̵̯̀o̶̗͋̅̌͌a̷̬̘̻͒a̸̦̻̪̱̎̈́͊͋̔a̴̤͈̿͑͂̅͝ ̸̛̙̬̞̝͊̒̄ş̷̞̗̞̜̽p̷̡̹̼̰͈͒̚o̴̰͐̈o̴̯͚̮̔͐̅k̷̼̝͇̯̯͊̃̿͝y̵̧̜̻͇̌̐̈́͘͝] [c̵̨̲̀̋r̵̠̗̔͗͘͘e̴͖̔é̷̲͇p̸̫͖̪͇̂̂̚ͅy̴͚̞̎̊̋ ̴̧̼̘̚w̷̻̳̏͂̂h̵̯̀o̶̗͋̅̌͌a̷̬̘̻͒a̸̦̻̪̱̎̈́͊͋̔a̴̤͈̿͑͂̅͝ ̸̛̙̬̞̝͊̒̄ş̷̞̗̞̜̽p̷̡̹̼̰͈͒̚o̴̰͐̈o̴̯͚̮̔͐̅k̷̼̝͇̯̯͊̃̿͝y̵̧̜̻͇̌̐̈́͘͝] [c̵̨̲̀̋r̵̠̗̔͗͘͘e̴͖̔é̷̲͇p̸̫͖̪͇̂̂̚ͅy̴͚̞̎̊̋ ̴̧̼̘̚w̷̻̳̏͂̂h̵̯̀o̶̗͋̅̌͌a̷̬̘̻͒a̸̦̻̪̱̎̈́͊͋̔a̴̤͈̿͑͂̅͝ ̸̛̙̬̞̝͊̒̄ş̷̞̗̞̜̽p̷̡̹̼̰͈͒̚o̴̰͐̈o̴̯͚̮̔͐̅k̷̼̝͇̯̯͊̃̿͝y̵̧̜̻͇̌̐̈́͘͝] [c̵̨̲̀̋r̵̠̗̔͗͘͘e̴͖̔é̷̲͇p̸̫͖̪͇̂̂̚ͅy̴͚̞̎̊̋ ̴̧̼̘̚w̷̻̳̏͂̂h̵̯̀o̶̗͋̅̌͌a̷̬̘̻͒a̸̦̻̪̱̎̈́͊͋̔a̴̤͈̿͑͂̅͝ ̸̛̙̬̞̝͊̒̄ş̷̞̗̞̜̽p̷̡̹̼̰͈͒̚o̴̰͐̈o̴̯͚̮̔͐̅k̷̼̝͇̯̯͊̃̿͝y̵̧̜̻͇̌̐̈́͘͝] [c̵̨̲̀̋r̵̠̗̔͗͘͘e̴͖̔é̷̲͇p̸̫͖̪͇̂̂̚ͅy̴͚̞̎̊̋ ̴̧̼̘̚w̷̻̳̏͂̂h̵̯̀o̶̗͋̅̌͌a̷̬̘̻͒a̸̦̻̪̱̎̈́͊͋̔a̴̤͈̿͑͂̅͝ ̸̛̙̬̞̝͊̒̄ş̷̞̗̞̜̽p̷̡̹̼̰͈͒̚o̴̰͐̈o̴̯͚̮̔͐̅k̷̼̝͇̯̯͊̃̿͝y̵̧̜̻͇̌̐̈́͘͝] [c̵̨̲̀̋r̵̠̗̔͗͘͘e̴͖̔é̷̲͇p̸̫͖̪͇̂̂̚ͅy̴͚̞̎̊̋ ̴̧̼̘̚w̷̻̳̏͂̂h̵̯̀o̶̗͋̅̌͌a̷̬̘̻͒a̸̦̻̪̱̎̈́͊͋̔a̴̤͈̿͑͂̅͝ ̸̛̙̬̞̝͊̒̄ş̷̞̗̞̜̽p̷̡̹̼̰͈͒̚o̴̰͐̈o̴̯͚̮̔͐̅k̷̼̝͇̯̯͊̃̿͝y̵̧̜̻͇̌̐̈́͘͝]

[Logs] [Logs] [Logs][Logs] [Logs] [Logs] [Logs] [Logs][Logs] [Logs] [Logs][Logs] [Logs] [Logs] [Logs] [Logs][Logs] [Logs] [Logs] [Logs] [Logs] [Logs] [Logs] [Logs] [Logs] [Logs]

[Outsider POV / Log Context] [Outsider POV / Log Context] [Outsider POV / Log Context] [Outsider POV / Log Context][Outsider POV / Log Context] [Outsider POV / Log Context] [Outsider POV / Log Context] [Outsider POV / Log Context] [Outsider POV / Log Context] [Outsider POV / Log Context] [Outsider POV / Log Context] [Outsider POV / Log Context] [Outsider POV / Log Context][Outsider POV / Log Context] [Outsider POV / Log Context]

[Conclusive text] [Conclusive text] [Conclusive text] [Conclusive text] [Conclusive text] [Conclusive text] [Conclusive text] [Conclusive text] [Conclusive text] [Conclusive text] [Conclusive text] [Conclusive text] [Conclusive text] [Conclusive text] [Conclusive text] [Conclusive text] [Conclusive text] [Conclusive text]

Collapsible Text

Collapsible text is a very useful tool in articles. It can be used for things such as recovered documents and files, where the reader has to click on something like "OPEN FILE: RECOVERED DOCUMENT" to access its content. This can be very finnicky and Wikitext likes to mess it up often. It is dictated by the use of <div> and </div> with classes indicating collapsibility. Here is an example of collapsible text (bolded so it is obvious one can interact with it):

<div class="mw-customtoggle-first">'''OPEN ADDENDUM'''<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-first">

EXAMPLE TEXT

</div></div>

This will make the text "OPEN ADDENDUM" interactable, and once clicked, it will reveal any text following the code. For example, "Upon further investigation, this level... etc." Once the text inside the collapsible is done, end it with </div>. This will allow you to continue the page text after it, without it being included in the collapsible. Here is how the text would work in Source Editing:

OPEN ADDENDUM

EXAMPLE TEXT


To include multiple collapsibles in one document, just do the same thing again, but replace the "first" in "mw-customtoggle-first" and "mw-customcollapsible-first" with "second," and so on. You can get fancy with collapsibles, such as layering them within one another, and add underlined or even colored text. An example of this would be:

<div class="mw-customtoggle-first"><span style="color:green;">'''<u>OPEN ADDENDUM</u>'''</span><div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-first">

EXAMPLE TEXT

</div>

The text "OPEN ADDENDUM" is collapsible, bold, underlined, and colored green. When clicked, it reveals "EXAMPLE TEXT". Here is how the text would work in an actual page (the instances of "first" here are replaced with "second" as we have a previous collapsible above):

OPEN ADDENDUM

EXAMPLE TEXT


In some instances, the page can sometimes mess up collapsible text when saving it, such as adding an [Expand] button next to it, which looks messy. If this occurs, just replace the <div> text around it again with the code provided in this page. Collapsible text has many possibilities and its usefulness cannot be understated.

Timers & Simple Time-Based Events

While functions like these and the following are interesting to mess around with, they are very rare in most pages. Here is how one can describe the time and date in an article:

It is currently {{#time: g}}:{{#time: i}}:{{#time:s}} {{#time: A}} {{#time: e}} on {{#time: l}}, {{#time: F}}, {{#time: j}} .

This creates the following text: It is currently 10:00:02 AM UTC on Thursday, April, 28. If you want to add the year, add {{#time: Y}}.

Time-based events on Wikitext are incredibly flawed, and Javascript is required to create anything more than a rudimentary system. If we wanted to make a page that changes on a 30 minute basis, we'd use this system:

{{#ifexpr {{#time: i}} > 30 | page content 1 | page content 2}}

We'll get into #ifexpr later, but for now, let's get into the issues of this method: the first and most glaring flaw is that this isn't executed every time a page is loaded, but instead when a page is parsed. This means it would realistically take about 2 days to change to the second version of the page content if the page isn't edited. The other issue is that custom time periods are hard to make. Overall, Javascript does the job much better. However, in a pinch, this function can work.

Functions

There are many basic tools that you can use to build your page. The first of these is {{#expr}}. This executes a basic logic or math command and prints the answer. The data printed from this command cannot be used in another function, and only shows up when viewing a page.

{{#ifexpr}} is a simple true/false function, printing something based on whether an {{#expr}} command is true or false. It is formatted {{#ifexpr (Insert logic/math here to get a result) | True text | False text}}. For instance, if you did {{#ifexpr 40 = 50 | True Text | False Text}}, you would get False Text (Don't quote me I might be off). This text can be replaced with anything, up to an entire level. {{#ifeq}} Compares whether two things are equal. It is formatted as {{#ifeq input1 | input2 |output1 |output2}}, and can be used for both text and numbers. There is apparently {{#switch}} but it confuses me so I will not put it in this guide, if anyone knows how to use it please add it.

Randomization

If you want to use a random text or number, use <choose> <option> Option1 </option> <option> Option2 </option> <option> Option3</option> <option> Option4 </option> <option> Option5 </option> </choose>

This is the <choose> function, and it is used to randomly generate from a list of defined options. Using that in wikitext would yield the following:

Option2 

This gives you 1 possible option every time the page is refreshed, and could be used to make a "Roulette" type of level, where it dynamically changes and the page changes with it. An example is this page, a rudimentary level of this type.

CSS and Page Design

Before we start, I'd like to give an example of meticulous and good looking page design.

I am not great at CSS, so before writing this section I will practice to get examples


Note: This is a catalog of pure CSS and its applications, however, I haven't tested it yet: here it is

Advertisement