This is a guide meant for the moderators of the wiki in the case that they would want some insight into the more complicated functions of the site. For the more simple guide, see Guide for new editors.
This guide also presumes editing in source mode, since most of the more complicated functions cannot be performed in the visual editor. Many of the pages I will be talking about are protected and only mods and admins will be able to edit them.
(May 2020. This guide is a work in progress. Let me know if there is anything I should cover or expand on. For now I plan to work on better examples and explaining tables.)
Some useful code[]
First, will mention a few tricks that were not covered in the guide for new editors. Know that the format for most of these can be found among templates or the wiki css, so this section is more about how to use it.
Make a quote by using {{quotes|(text of the quote)|(who the quote is from)}}, e.g. {{quotes|Just die already|Sagara}} will result in:
| “ | Just die already | ” |
– Sagara
| ||
If you ever want to refer to something indirectly but you do not want to create a link to it linked to, you can use this code, example <abbr title="Asha">black silhouette</abbr> will result in: black silhouette
If you need for a picture from a previous section to not break into the next section, divide the text with {{clr}}
Take note that there are more specific ways to create references. All are explained in the reft template.
To make the contents of a page appear on another page without having to copy paste, use the {{:pagename}} command. The contents will automatically update if the page that is called on gets edited.
<onlyinclude>I want to see this</onlyinclude> - these tags make it so that if you call onto the contents of a page using the {{:pagename}} tag, only the contents inside the onlyinclude tags will get transferred. This is used for example in the chapter pages (the summaries get transferred) and also on the pages of main characters (their infobox gets transferred). An opposite approach to this would be to put anything you do not want included into notinclude tags, like so: <notinclude>I don't want to see this</notinclude>. Then everything outside the tags will get transferred.
<nowiki>don't activate code</nowiki> - any code inside these tags will not be activated and will show up as written on the resulting page. If you check the code of this page, you will see an overuse of this tag.
To hide certain contents of a page use:
<!-- I don't want to see this -->
Any code inside these tags will not be activated and it will not show up on the page, although it stays visible in the source editor mode. This can also be used for plain text which you want to keep hidden on the wiki (for example if some information has yet to be confirmed or is yet to be released on webtoons, you might want to hide related text until it is safe to reveal it.)
To visually divide sections of text, you can use:
<div style="text-align: center">♢ ♢ ♢</div>
The code for the diamonds is ♢ and the result will look like this:
More TBA.
Template[]
This wiki uses templates which allow inserting the same content to different pages and ensure a unified standard. More on this in Kubera Wiki:Templates. I will now cover those that you might need.
Main page templates[]
Main page templates are templates that appear on the main page of the wiki. The main page itself only calls on these templates, it does not explicitly have the content which you can see on it, so if you wish to edit anything on it, you will need to venture to this category.
The most frequently edited template would be Template:Main-Slider which needs to be updated after each new episode release. This template allows switching between up to 4 images and can link to desired pages. These pictures must have a resolution of 670x360 px.
Another popular template is Template:Poll which allows to create a poll which will show on the main page. All it takes is entering a question and possible answers. But be warned, any edit will reset the poll.
Template:Wiki News might come in handy when we wish to inform the community about what is going on with the wiki while Template:Latest News is where we write about what is up with Kubera.
Template:Right column includes the wiki news and latest news templates. Moreover, it includes some general text about welcoming contributors. This is also the page where the meme of the week template was included. It is now, however, disabled.
Template:Main-Welcome includes the welcome message at the top of the main page.
Template:Main-Links includes links to useful sites such as reddit, discord, the blog.
Template:Main-Info has some general information about Kubera for those who are new to this page.
Template:Main-Contents-Table is where you can find the directory to all the pages of the wiki, such as characters, magic, universe, community.
Template:Main-Contents includes several of the above-mentioned templates (slider, main contents) and it also includes the list of main characters.
Template:Main-Bottom merely includes a list of affiliated wikis.
Infobox templates[]
Infobox templates are used for infoboxes in articles. There are several general wiki templates, but the ones we use are mostly customized templates for our wiki.
These are: Template:Character, Template:Clan, Template:Episode, Template:Event, Template:Location, Template:Transcendental.
Only the fields that are present in the code of the template will show in the infobox. Therefore, if you need an extra field in the infobox, you will need to edit the related template.
If you open the editing box in any template, you will see that the top part of the page contains the important code.
At the top is the "theme" which draws on information from the wiki CSS about what the template should look like. I'll get to that later. e.g. <infobox theme="transcendental">
Then follow lines that ask where to take the source from. The word in the quotation marks is the word that will have to be used when utilizing the template. The word inbetween the tags is what will show up in the infobox. E.g.
<data source="name-alt"><label>Alternate name</label></data>
this tells the template to take information from whatever you input for "name-alt", e.g.:
|name-alt = babo
If I were to use an infobox with this code, it would say: Alternate name babo
In the template documentation section, you can see the description for the template followed by a box that shows how to use the template. It includes all fields that are in the template and if you want to use the template when in source mode, you only need to copy this part.
If you add a line to the template's code, don't forget to also add it to the template documentation.
The infoboxes use MediaWiki:Custom-infobox.css, which is where you could edit the color of the infobox as well as other parameters. If you were to create a new infobox template, you would also need to add it here. Best be careful here, though.
The episode template is slightly different from the others in that it draws on modules and automatically generates quite some information. It is inadvisable to tamper with it with one exception. Whenever there is a special episode, the code here needs to be edited. More on that later.
Other templates[]
Other templates you might find yourself using would be in the General wiki templates.
Template:Currybox is the basis for several tables on the main page of the wiki and thus might need to be edited if you want to change the format on the main page.
Template:Reft and Template:Reftf are used for making references.
Template:Eindex is used for linking to episodes in character plot summaries.
You can also find templates determining the format of headers. And spoiler warning boxes. etc.
Modules[]
Modules make it possible for certain links, titles, and information to get automatically generated. Many infoboxes draw on this. The list of modules can be found in Lua modules.
Episode modules[]
There are three important episode modules and the episode template draws on all of them for information.
Module:EpisodeLink automatically generates the link to the episode on naver and webtoons. It must be updated weekly to include the number of the latest naver and webtoons release. In the case of a special episode that does not get released on webtoons, it is also necessary to edit the counter for the webtoons linknumber.
Module:EpisodeNav generates a link to the previous and next release inside the episode infobox. It must be updated weekly to contain the number of the latest naver release. It is necessary to edit it in the case of special episodes, which must be added separately.
Module:EpisodeTitle includes titles of the chapters in Kubera. Whenever a new chapter begins, it is necessary to add it to the list and then the episode infobox will automatically generate its header from this module.
Character modules[]
Alike the episode template, the character template also draws on some information from modules.
Module:CharInfo draws information from Module:CharInfo/chardat and automatically counts the age of characters inside their infoboxes. It also contains their race and magic ranking (if given). This information must first be entered into the chardat module.
Module:CharApp draws information from Module:CharApp/charappdat and adds the characters which appeared in an episode into the episode infobox for that episode. The appearances must first be input into the charappdat module.
What to do when an episode updates[]
There are several things which must be updated whenever a new episode gets released. This task is usually assigned to a specific person, but if you would ever like to try adding the new page yourself, inform one of the mods and you will get your chance.
A new episode[]
For every new episode, first, create a page using the naming format of "Episode season-number" (for example "Episode 3-125").
You can copy this code into the new page then. This is an example from Episode 3-160.
{{episode
|image =
|caption =
|season = 3
|ep = 160
|release = 452
}}
==Summary==
<onlyinclude>TBA</onlyinclude>
<gallery></gallery>
===Currygom's comment===
TBA
{{clr}}
==Afterword==
{{blogdata|url=222755402392|date=2022.06.02 23:30|cat=Episodes|translator=Tierra}}
TBA
==Notes==
==References==
<references />
The first part is the episode template. This must contain the correct season, episode, and release number (this is based on naver releases) so do not forget to edit it. The page must further include a summary, author's comment, afterword, notes, and references. For the box for the afterword, you must also manually enter the url and date (these do not get automatically generated).
When writing the summary, be careful with the <onlyinclude> tags. These must be on both sides of the text so that only the summary gets transferred when this page gets called onto from the chapter page. The gallery tags serve for entering pictures. And notes and references are a standard part of every page.
The release number in Module:EpisodeLink and Module:EpisodeNav must be raised to match the new episode. It is this part of the code:
local LATEST_NAVER = 454
Template:Main-Slider should then be updated to link to the newest episode. This is the code:
<gallery type="slider" orientation=left>
Slider-naver.png|Latest on Naver|linktext=Special Episode 1: Gaze|link=Extra: Special Episode 1 - Gaze
Slider-webtoons.png|Latest on Webtoon|linktext=S.3 Ep.160: The Golden Knight 2 (10)|link=Episode 3-160
Slider-AK.png|What's ''Kubera''?|linktext=Learn more about this webtoon!|link=About Kubera
N23 slider v2.png |The battle of N23|linktext=Learn more about this massive conflict|link=The battle of N23
</gallery>
Edit the "link" to match the wiki name of the page of the new episode and the "linktext" to contain the name that you want the slider to show. Do not edit the name of the picture, instead upload a new picture with a matching name onto the wiki, "Slider-naver.png" or "Slider-webtoons.png". The picture must have a resolution of 670x360.
Furthermore, the episode should be written into the page for the relevant chapter and it must be entered into the Episode Guide using the format of {{ttl|season|number|}}, e.g. {{ttl|3|160|}} for episode 160 of season 3.
That's it.
A new chapter[]
Whenever there is a new chapter, on top of everything that must be done for a new episode, it is also necessary to create a page for the new chapter keeping the format of "Chapter number: name" (e.g. "Chapter 12: Lies for You"). You can copy this code in the new page, this is an example from Chapter 48: Separation
{{infobox chapter
|title = Separation
|title-k = 별리
|image =
|season = 3
|chapter = 48
|range = 3-121 to 3-150 (30 total)
|prev = [[Chapter 47: Words That Never Reached You]]
|next = [[Chapter 49: The Golden Knight 2]]
}}
==Episode 3-121==
'''[[Episode 3-121|Season 3 Episode 121: Separation (1)]]'''
{{:Episode 3-121}}
==References==
<references />
The first part of the page is the the chapter infobox where you must correctly input the title, the season and chapter number, as well as the number of episodes. The previous and next chapter must also be input manually.
The page further includes links to all episodes of that chapter (these should be added gradually as they get released) as well as a command to take the contents from the episode page, which ensures that the summaries get transferred to the chapter page. An example of what this would look like is:
==Episode 3-90==
'''[[Episode 3-90|Season 3 Episode 90: Soul (1)]]'''
{{:Episode 3-90}}
The first line is the header, the second line is a link to the episode (in bold), and the third line is a command that calls on the text from the episode page. if the episode summary is in <onlyinclude tags>, only the summary will get transferred.
The chapter must naturally be added to the Chapter Guide and Episode Guide.
And to make things more fun, you must also edit Module:EpisodeTitle where you input the new title and set the counter. This will ensure that the episodes of that chapter get named correctly. This part:
<title source="season">
<format>{{#switch: {{{release|}}} | 34 = Gu Bera No. 1 | 53 = Gu Bera No. 2 | 72 = Gu Bera No. 3 | 105 = Season 1 Epilogue | 157 = Q&A Special No. 1 | 208 = Q&A Special No. 2 | 273 = Punishment | 290 = Season 2 Epilogue | 392 = 9-Year Summary | 453 = Q&A session | 454 = Gaze | 455 = Terms of affection | 456 = I Iove you, I love you not (1) | 457 = I love you, I love you not (2) | 458 = Watershadow | 459 = News | 460 = More | 461 = The South Pole Expedition (1) | 462 = The South Pole Expedition (2) | 463 = Hide and Seek | 464 = Wish (1) | 465 = Wish (2) | 466 = Wish (3) | {{title|{{{season}}}|{{{ep}}}}}<!-- end title -->}}<!-- end switch --></format>
</title>
and then this part under the getTitle function:
elseif (episode <= 500) then title = 'The Weight of Time' ftitle = 'Chapter 50: The Weight of Time' index = episode - 160
A special episode[]
These are a pain.
Firstly, when creating a page for a special episode, it must always start with "Extra:", since the code in the template expects this wording for creating the infobox. Other than that, create the page the same way as you would for an episode, except don't input the episode number into the episode infobox. Write in only the season and release number.
Template:Episode needs to be updated in the case of special episodes. It is necessary to input the title into the code as an exception because the template does not know how to deal with episodes without episode numbers.
Module:EpisodeLink and Module:EpisodeNav must be raised to match the latest release number, but on top of that, the name of the episode must explicitly be added into the code of EpisodeNav, because otherwise the navigation would lead to the next full episode and skip the special. It is this part:
elseif (LinkNumber == 453) then LinkTxt = "[[Extra: Q&A session]]"
The linknumber must match the release number of the episode, then add the correct title of the special. You must also edit the counter at the bottom, otherwise the next normal episode would get numbered incorrectly. This part:
elseif (LinkNumber < 453) then LinkNumber = LinkNumber - 292
More edits to EpisodeLink must be done only in the case that the episode does not get translated on webtoons. Then it is necessary to raise the counter that generates a link to webtoons. This part:
elseif (LinkNumber <= 452) then
LinkNumber = LinkNumber - 7
The slider can be edited same as for ordinary episodes. Don't forget to add it to the Chapter Guide and Episode Guide.
Tables[]
Several complex pages with protected view include tables, so it might be wise to briefly explain how they work. Simple tables can be created through visual editor, but as they get more complex, source editor becomes necessary.
The most simple example would be something like this
{| class="article-table" style="margin-left:auto;
margin-right:auto; font-size: 90%; line-height: auto;"
! column 1
! column 2
|-
| answer 1
| answer 2
|-
| answer 1
| answer 2
|}
{| signifies the beginning of the table. The first line gives the style of the table. This example mostly left things to auto.
Lines with ! then determine the headers of the column. |- signifies that a new column begins. The contents of the cells must be written behind | and if a cell is to be left empty, then write a | without anything. Do not skip the line. The table gets closed with |}
This is what my example would look like:
| column 1 | column 2 |
|---|---|
| answer 1 | answer 2 |
| answer 1 | answer 2 |
Another example of the opening line would be from the Chapter Guide.
{| class="article-table" style="width:80%;" cellspacing="1"
cellpadding="1" border="1" align="center"
! scope="col" width="80%" valign="top" | Title
! scope="col" | Image Gallery
Unlike the previous example, it determined the structure of the table to specific values. For setting the headers of columns, the style of the columns first got determined and the text itself is after the | line. The "col" makes it so that there is a visible line dividing the columns in the table and the valign aligns the text. I will now use this heading instead of the previous one, otherwise keep the previous table:
| Title | Image Gallery |
|---|---|
| answer 1 | answer 2 |
| answer 1 | answer 2 |
If you want to make a table with multiple tabbers, you will need to use a slightly different style. A simple example is from the Magicians ranking page. I've simplified it a bit to fit it here:
<div class="regtab"><tabber>
N16= {| class="wikitableplus wikitable" style="margin-left:auto; margin-right:auto; font-size: 90%; line-height: auto;"
!Ranking<br/>(N7)
!Name
|-
|1
|style="text-align: left;" | Teo Rakan
|-
|2
|style="text-align: left;" | Lutz Sairofe
|-|
|N11= <!-- ==================================================== ==================================== -->
{| class="wikitableplus wikitable" style="margin-left:auto; margin-right:auto; font-size: 90%; line-height: auto;" ! Ranking<br/> (N11)
!Name
|-
|1
|style="text-align: left;" | Airi Yui
|-
|2
|style="text-align: left;" | Teo Rakan
|} </tabber>
As can be seen, the whole table is inside code that enables multiple tabs. Each tabber should have the table information input again. The name of the tabber preceeds the table and is followed by a = sign. The tabbers need to be divided by |-| and if they are complicated, then by a line of ===. The tabber must be closed at the end.
Probably the most complicated table on this wiki is in the List of characters since it has a tabber inside a tabber. This is a simplified version of what you will see nested inside the table which is in itself given the same way as in the previous example:
Supporting Characters=
{{#tag:tabber|Pure-blood humans=
{{{!}} align="center" border="1" cellpadding="0" cellspacing="0"
class="article-table" style="width:100%;"
{{!}}-
! scope="col" style="width:25%; background-color:#c14e4e;" {{!}} '''English Name'''
! scope="col" style="width:35%; background-color:#c14e4e;" {{!}} '''Race'''
{{!}}-
{{!}} Jibril Ajes {{!!}} pure-blood human
{{!}}-
{{!}} colspan="4" {{!}} lots of text
{{!}}-
{{!}} colspan="4" style="padding:2px; background-color:#c14e4e;" {{!}}
{{!}}-
{{!}} Enan {{!!}} pure-blood human
{{!}}-
{{!}} colspan="4" {{!}} lots of text
{{!}}}
<!-- =====================================================
=================================== --> <br>
{{!}}-{{!}}Quarters=
{{{!}} align="center" border="1" cellpadding="0" cellspacing="0"
class="article-table" style="width:100%;"
{{!}}-
! scope="col" style="width:25%; background-color:DarkOrange;" {{!}} '''English Name'''
! scope="col" style="width:35%; background-color:DarkOrange;" {{!}} '''Race'''
{{!}}-
{{!}} Kanna Ajes {{!!}} quarter {{!!}}
{{!}}-
{{!}} colspan="4" {{!}} lots of text
{{!}}-
{{!}} colspan="4" style="padding:2px; background-color:DarkOrange;" {{!}}
{{!}}-
{{!}} Leto Ajes {{!!}}quarter {{!!}}
{{!}}-
{{!}} colspan="4" {{!}} lots of text
}}
Now what you can see here. Instead of the determination of the table immediately following the supporting characters, there is a command to create a tabber "<nowiki>{{#tag:tabber|" and only after that, the table determination follows.
All | have been replaced with {{!}} and if there were two || then they are replaced with {{!!}}. The two lines make it so that the next text gets written next to the previous one, not under. Other than that, the nested tabbers work much like in the previous example.
There is a colspan command between every line which makes it so that a colored line is between the cells. The nested tabber gets ended by a double }}