Editing t20150211

• For the basics about MediaWiki please read MediaWiki FAQ
• In the beginning, the Cheatsheat is very useful

Basic structuring

For the general structuring of an article, please refer to the following reference articles:

Articles

• Data- and Object Model
• Class Browser

How-To's

• Create a new MetaClass
• Create a new MetaProperty
• Create a new MetaClassScope

System Objects

• MetaClasses: METACLASSSCOPE, QUERYSCOPE
• Classifications: SYSCLS TASK, SYSCLS THUMBNAILEDFILE (with properties)

Headlines

Use the general headline formatting, type in regular case.

Infoboxes

Infoboxes should be used as an introduction for articles that have a useful common denominator. They will appear at the top right ans summarize the article in Keywords and/or pictures. Currently there is a template for a Control Infobox implemented that should be used for all articles about UBIK^® controls.

See also the list of available Infoboxes templates.

Categories

Each article must be assigned to at least one category and a maximum of 3 categories.

• If you feel an article fits into more than 3 categories, consider splitting it into multiple articles
• If you feel an article fits into no category, consider merging it into another article
• Do not create new categories every time - check if an existing fits to your needs.

Sub Categories

A new sub category can be created by pasting a category within the source of another category page.

Sort Key

Use sort keys for certain articles, e.g. objects of category System Classifications, so that the article is sorted by a propery sort key instead of S always. Example: [[Category:System Classifications|T]]

Category Tree

The articles and categories are evaluated by the Category Tree extension and used on the SiteMap page.

• Extension:Category Tree
• Help:Extension:CategoryTree

Special articles

HowTos

Create a How-To to describe HOW to solve a certain issue. The given instructions should be clear and easy to follow, therefore use screenshots (server and client side) to document your explanations. Use a descriptive name for the How-To article, such that already describes the content.

Consider the KISS principle - Keep It Short and Simple

In the How-To articles place images within the items of the numbered list (its width should remain 220 pixels width in landscape or 170 pixels height in portrait orientation).

FAQ entry

Create a FAQ entry to provide answers to questions or issues the reader would ask using WHY, WHO, WHEN, etc. Provide a short answer, which probably also includes a few instructions.

If the issue requires more detailed explanations refer to an existing wiki article or create a new one.

Descriptive text

Descriptive text should be left aligned and in the standard font, without any additional formatting.

If you want to emphasize something, use bold style.

If you want to refer to the exact name of something in the UI of UBIK, use italic style.

Links

Internal linking is a good thing, but it must not be used too extensively. Link to the articles that make sense in context of the manual, especially when they are about fundamental principles of UBIK^®, like for example the MetaClass article. Link to each keyword only once in an article, at first appearance of the keyword.

External links only make sense if the target article supports in comprehending an article, for example a certain standard or norm that is used by or in UBIK^®, i.e. ISO15926.

Lists

There are two types of lists that can be used:

Bullets

Use a bullets if you want to list several (short) statements of the same area, which are not chronologically connected. Do not use punctuation for bulleted items.

• Statement
• Another Statement

In addition, if you want to list certain tasks that do not follow a particular order you can use right arrows:

→ Task a

→ Task b

Numbered list

Use numbered list if the items are chronologically connected and have to be executed one after the other. Do not use punctuation for bulleted items.

1. Do this first
2. then do this
3. end finally, do this

Tables

Use the WikiTable like in the following example:

{| class="wikitable" | width = "50%"

|- ! Columns 1!! Column 2

|- | Row 1.1|| Row 1.2

|- | Row 2.1|| Row 2.2

|- | Row 3.1|| Row 3.2

|- |}

will result in

For larger data, the sortable table might be more useful:

{| class="wikitable sortable" | width = "50%"

|- ! Columns 1!! Column 2

|- | Row 1.1|| Row 1.2

|- | Row 2.1|| Row 2.2

|- | Row 3.1|| Row 3.2

|- |}

will result in

Code

Use either a leading blank to format text as source code, or the <code>-Tag for regular code highlighting.

For highlighting a syntax of a specific programming language, use the source-Tag as follows:

<source lang="csharp">
// Hello World in Microsoft C#.

using System;

class HelloWorld
{
    public static int Main(String[] args)
    {
        Console.WriteLine("Hello, World!");
        return 0;
    }
}
</source>

which will result in

Tips and hints

Attention

Use the Attention template to draw attention to a certain sentence:

{{Attention|Please don't miss this sentence!}}

will result in

Please don't miss this sentence!

Hints

Use the Hint template to outline useful tips and hints:

{{Hint|You should read this, it will simplify your work!}}

will result in

You should read this, it will simplify your work!

Colors

Colors should be used very sparingly and only if they really contribute to the better understanding of a text.

Other useful templates

• The KeyPress template allows you to display keyboard commands, so {{key press|Ctrl|W}} will result in Ctrl+W
• Use the UBIK MetaModel template to refer to the data model:

Template list

A list of available templates can be found here UBIK Templates

Naming conventions

To obtain some kind of categorization the name of new images must start with one a prefix. Choose the most appropriate one from the below list:

Formats

Supporting images

Example Supporting images

Supporting images must be formatted as thumb to make them appear on the right side, with the following dimensions:

• Images in portrait format with 170 pixels width
• Images in landscape format with 220 pixels width

Example: [[File:Example.jpg|220px|thumb|border|alt=Example|Example]] {Clear}

Descriptive images

Images as part of the descriptive article text can be placed inline, like for emphasizing a certain manual visually, with the following dimensions:

• Images in landscape should not exceed 700 pixels width
• Images in portrait should not exceed 700 pixels height

Example: [[File:Example.jpg|700px|border|alt=Example|Example]]

Borders

Use the border parameter in the tag for the embedded image, for example [[File:Example.jpg|border]] results in

Image captions

Use image captions if appropriate to describe the image and to create a relation to the text.

Gallery style

If there is the need to place a series of images within the text use the gallery tag with an appropriate width and height

<gallery widths="200" heights="200">
File:Example.jpg|1 - Example
File:Example.jpg|2 - Example
File:Example.jpg|3 - Example
</gallery>

which results in

• 

  1 - Example

• 

  2 - Example

• 

  3 - Example

UBIK Templates