On this site I'll give you a short introduction of editing and the codes you might stumble upon.

First of, there are different kinds of editors for the wikia. I'll be focusing on the source editor since you have the most control over your edits.

I'll recommend everybody to change it in your preferences:

Pref source

That way several issues with the visual editor will be bypassed (e. g. adding blank lines in some cases).

You still have the basic formatting buttons available in source mode, but it isn't that hard to use the codes for them either.

This is an example of the source editor:

Source editor

On the right you still have help to add media to the page. But instead of showing a picture in a preview, you've got the wikia code for it. That way you have more control on where you want to place it. Hit the preview button on the top right to see how it looks like when published.

Important: Regardless of which editor you are using, hit preview before publishing anything, look for quirks resulting from your edit. If there are none => publish it. If there are some => back to the editor and correct them.

Now that we've covered the basics of the basics, let's delve into some easy "coding".

The most basic form of coding is used to format text. Let's use some examples:

''Text'' will result in a italic text.
Text will result in a italic text.
'''Text''' will result in a bold one.
Text will result in a bold one.
Combining both is easy, '''''text''''' uses both.
Combining both is easy, text uses both.

Setting up headers is just as easy. Just enclose your desired headline in =. == for a Top level headline === for a sublevel 1 headline ==== for sublevel 2 up to ====== for sublevel 4



Sublevel 1

Sublevel 2

Sublevel 3
Sublevel 4

Headlines up to sublevel 2 automatically add an edit button next to them.

The last one you need to set up a basic layout for a site concerns spacing and readability.

There are basically two snips of code you need to know for that.

The first being a horizontal line. You can use it to close a section of your article. Just add


where you want the line. You see one above. The next one uses a template. Templates are preformatted tables, boxes and so on. The navbox at the bottom of each major page is an example of this. In this case it's just a way to use

<div style="clear:both;"></div>

. To use it type



While it isn't needed if you just write some text, it comes in handy if you have a short text with a picture and another text.

The following example is without the use of the template.

"Those awful, ravenous, rainbows."

Slimepedia Entry


Veggies, fruit and slimes, but not Gold Slimes



Next section

This doesn't have to do anything with the infobox of the tarr.


This example (and this text as well) is with the use of the template, added just before the 'Next section' header.

"Those awful, ravenous, rainbows."

Slimepedia Entry


Veggies, fruit and slimes, but not Gold Slimes



Next section

This doesn't have to do anything with the infobox of the tarr.

As you can see, the text begins after the infobox ends. This way you can make sure that your text fits with the images provided and doesn't cause confusion.

Another important note: when working with any code whatsoever, you've to remember that code doesn't take up blank lines in the published article. To make controlling contributions and code easier, write each part of the code in a different line

A bad example of code used is the following use of the Slimes infobox

{{Infobox_slimes|title = The Tarr|image = The Tarr SP.png|imagecaption = The Tarr on Slimepedia|occ = When a largo eats a plort that it has not yet eaten|vop = None|diet = Slimes, but not Gold Slimes|fav = Ranchers!|harm = Yes}}

As you can see, it's very confusing to look at and getting information out of it is almost impossible. A good version of the very same code would be this

|title        = The Tarr
|image        = The Tarr SP.png
|imagecaption = The Tarr on Slimepedia
|occ          = When a largo eats a plort that it has not yet eaten
|vop          = None
|diet         = Slimes, but not Gold Slimes
|fav          = Ranchers!
|harm         = Yes

This way it's way easier to make changes and, to look for errors. So remember to not only make your visible text neat, but also your code :)

The easiest way to create an infobox is, to copy one from another page, which preferably looks similar to what you want to create. In order to fill the infoboxes with the correct information, you have to first switch into source mode. For the next step EmeraldPlay has contributed a tutorial, which can be found in the comments under the Warp Tech article:

"When you use the infobox, that's what you will see in the source code:


|title =

|image =

|imagecaption =

|res1 =

|res2 =

|res3 =

|blueprint =

In the "|title" option goes the title, but you already know that.

In the "|image" option you put an image of the gadget, which has to be it's slimepedia icon.

The "|imagecaption" option should say "X Icon" where X is replaced by the gadget's name.

Now all of the "|res[number]" options should be used to tell about the resources needed to build the gadget. You have five different "|res" parts that you can use, but most of the gadgets don't use five resources, so some of the |res options will be useless.

If you want to write plorts in here, use this:

Pref source
 16 Pink Plorts

If you want to write slime science resources in here, use this:

Pref source
 8 Buzz Wax

Now the last part "|blueprint" should have the information about how you obtain the gadget, like through buying it, or through getting it from a Treasure Pod.

That's all you need to know!"

Community content is available under CC-BY-SA unless otherwise noted.