Revision [30278]

This is an old revision of WikiStyleGuide made by Rattlehead on 2014-08-03 11:04:08.



HomePage > Wiki Index

Wiki Style Guide


Every wiki page must start with a title, which will surely be the same name you gave to the page when you created it. To designate a text as title, you must format it as header. You can do so in 2 ways: a) selecting the text and pressing the H1-H5 buttons in the text editor. b) Surrounding the text with equal signs (=), from 6 to 2, depending on the size you want. The page title's header should have the biggest size of all the headers in the page, for obvious reasons.
======Really big header======

Really big header

(or: select the text and press H1 in the editor)

=====Rather big header=====

Rather big header

(or: select the text and press H2 in the editor)

====Medium header====

Medium header

(or: select the text and press H3 in the editor)

===Not-so-big header===

Not-so-big header

(or: select the text and press H4 in the editor)

==Smallish header==
Smallish header
(or: select the text and press H5 in the editor)

You can also use bold to designate article sub-section

(or: select the text you want in bold and press the B in the editor)
Headers can be directly link to, by writing between double brackets the url of our current wiki page, followed by the #hn_ termination and then the name of the title we want to be directed to. For example:

Breadcrumbs are used at the top of the articles. They point to index pages and help give the wiki structure. If a page has no other pages linking to it and no category, then a user might not find it. Think about which index the page belongs to. For example, media player software would go on the Multimedia software index, code:
HomePage > Software Index > Multimedia
[[HomePage]] > [[SoftwareIndex Software Index]] > [[SoftwareMultimedia Multimedia]]

Articles should include a Category footer, for example
(line return here)
(line return here)

Paragraph Indents
Paragraphs should come immediately under the title and be indented using a tab, use tab key or ~ character. An exception is categories (and tables while the Wikka bug persists).

Try to link internal to the Wiki where possible. This reduces jumping back and forth between websites. At the end of a pages relevant internal links are often listed under Also on the Wiki and relevant external links Related Websites.

If it isn't obvious from the url where a link goes please provide this information. An example is forum links, as they only show a number and not the thread's or post's title. Example:
Help needed writing the Wiki thread
[[ Help needed writing the Wiki thread]]

Provide a direct link or link to where it can be downloaded. It is help to provide the version in the link, and comment who the packager is. Software icons go above the title and may point to an external link, for example:
qtractor icon


{{image url="" link="" title="qtractor icon" alt="qtractor icon"}}

Used for data or to create columns. There is currently an error in Wikka that breaks the formatting if a table in indented. Here an example of table code:
Header 1Header 2
Cell 1Cell 2

|=|Header 1|=|Header 2||
||Cell 1||Cell 2||

Red text
Should be used for warnings and alerts and not in titles either.
{{color text="Warning:" c="red"}}

Use underline to call attention to text within the article (not in titles).

Bullet Points
Use a list to place bullets on special points within articles.
	- This is a bulleted point

CamelCase is used by Wikka to denote an internal link. Pages that don't have CamelCase style names need the double square bracket, for example:

Sometimes you don't want to link to a page, use the double quotes

If a page doesn't exist but would be useful in the future - leave the link in place, this will remind people that the page is desired.

Avoid HTML in articles, not all editors are proficient with it. Most things can be done in wiki code and the Wikka software is under active development. The double quotes is used to denote html, double quotes are also used to prevent unwanted linking, see above.

Pictures and graphics
Use a title text and alt text. This enables people who use screen readers to better understand articles.
filetype icon
{{image url="" title="filetype icon" alt="filetype icon"}}

Text and graphics are preferred for articles
Many people either do not have access to broadband or can’t afford it. Video is of no use to people using Screen Readers.

Vertically tall graphics should be placed on the right
So text may flow up and left of them. Vertically short graphics may simply be placed normally and thus appear on the left. The code below is taken from the article article
{{image class="right" url="" title="Dpup screenshot" alt="Dpup screenshot"}}{{image url="" title=" logo" alt=" logo"}}

Alternatively, the graphic can be sized using height and width attributes.

Example, coming: soon
{{color text="color" c="teal"}} {{color text="color text" c="fuchsia"}}

Page development and Discussion
If you are making a major/controversial change to a page please comment below the page first. This allows other users to give feedback. The comment button is equivalent to wikipedia's talk area on pages. The RecentlyCommented pages show the most recent discussion.

If there are two or more different pages names that could apply then 'redirect' may be useful. For example there is a page for Orange, Oranges can redirect to that page using this code,
{{redirect target="Oranges"}}

Also on the Wiki
LanguageBars - the bar at the top of many pages allowing access different translations

There are 2 comments on this page. [Show comments]
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki