Help:Tips and tricks

The official GemStone IV encyclopedia.
Revision as of 19:51, 30 May 2018 by ZHOUY1 (talk | contribs) (horizontally aligning elements)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
This article is a work in progress!

This will detail some of the advanced editing techniques you can use to make articles appear a little nicer.

Linking

The linking system is very flexible and allows for you to link so that the text flows naturally in articles regardless of what their names are. Here are a few ways to make links fit into the text better.

Singular article, plural text

If the article you're linking to (such as Rogue) is singular, but the sentence you're linking within (such as "Rogues are great.") uses the word in a plural form, simply place an s at the end of the link, as in [[Rogue]]s, which will produce Rogues.

Capitalized article names

The names of all articles are forced to start with a capital letter as a result of how the software works. However, because of that, the case of the first letter in a link doesn't matter for the link target. Thus, [[rogue]] will produce rogue, which properly links to the Rogue article. Therefore, you should use the proper capitalization for the sentence, such as "The spell's success rate is based on the player's casting strength" rather than "The spell's success rate is based on the player's Casting strength", which looks weird.

Arbitrary link names

In some cases, you may way to label a link as something that is completely different than the name of the article, for instance, in the sentence "Warriors have cheaper costs for some physical skills than the other square profession." you might want "other square profession" to be a link to the Rogue article. To achieve this, you would do [[rogue|other square profession]], which would produce a link to the other square profession.

Linking to a subsection

To link to a subsection of an article: [[Page name#Section name|displayed text]]. The section name is case-sensitive (including the first letter).

This will not work if there are multiple subsections with the same name, or if the target page is renamed. To work around this, you can insert the HTML code <span id="anchor_name"></span> at the start of the target section then link to [[Page name#anchor_name]].

Redirects

In some cases, an article may have more than one reasonable name, for instance, "CS" and "Casting strength". In this case, you can use redirect pages to make both names go to the same article. To do this, pick the most canonical name ("Casting strength") and create the article there. Then create an article under the other name(s) ("CS") with the only text being "#REDIRECT [[Real article name]]". Then, if someone visits the other names, they'll automatically be sent to the canonical name.

Don't abuse this to make only vaguely related things go to the same article, though. Redirecting "Lock Mastery" to "Pick locks" or "Pickpocketing" to "Justice" would be a bad idea, but redirecting "Lockpicking" to "Pick locks" or "Combat maneuver list" to "Combat maneuvers" probably wouldn't be.

Log formatting

Logs of in-game messages are usually presented with the <pre{{log2}}> tag. However, this may sometimes cause the text to overlap with right-aligned tables. Possible workarounds:

  • Use <pre{{log2|margin-right=...}}> and set margin-right to a higher value than the default 20%. Drawback: a very high fixed value for margin-right can cause the log to be unreadable on narrow screens (for example handheld devices).
  • Put the log inside its own table, which should auto-resize to avoid overlap:
{| class="wikitable"
|<pre{{log-inline}}>
...
</pre>
|}

Horizontally aligning elements

<div>
<div style="display: table-cell; padding: 10px;">
*Element 1.1
*Element 1.2
</div>
<div style="display: table-cell; padding: 10px;">
*Element 2.1
*Element 2.2
</div>
  • Element 1.1
  • Element 1.2
  • Element 2.1
  • Element 2.2

(This will probably not work for IE 7 and older browsers.)

Templates inside <pre> tag

Templates are normally not parsed inside preformatted text. This can be worked around using:

  • {{#tag:pre|text {{template}} more text}}
  • {{#tag:pre|text {{template}} more text|style=custom_css}}

For more details, see MediaWiki documentation on Magic words.

Hovering tooltips

  • {{#info: More information}} - More information - tooltip persists
  • {{#info: More information | note}} - More information - tooltip only appears when cursor is hovering

This can be used to mark up table entries where it would otherwise be inconvenient to display detailed information.

For technical documentation, see https://www.semantic-mediawiki.org/wiki/Help:Tooltip