User:Delib/Sandbox

---

From EditorGuide "DebianWiki/EditorGuide"

---

1. language en
   1. 2. NOTE TO WIKI EDITORS :
      3. ----------------------
      5. Don't edit this page directly.
      6. Use debian-www mailing list to propose new policy or modify existing ones
      8. Only validate contents can be inserted here. (see "Wiki Policy Approbation" below)

||<tablestyle="width: 100%; border: 0px hidden">~-Translation(s): English - Español - Français - Indonesia - Português (Portugal) - Русский - 简体中文-~||<style="text-align: right; border: 0px hidden"> (!) Discussion||

---

This page provides instructions for people wanting to edit the content of wiki.debian.org.

There's a QuickStart for new editors.

(!) See also: HelpOnSmileys :-) HelpOnMacros and HelpOnLinking and short HelpOnEditing

For generic help on formatting under moinmoin wiki, read moinmoin's HelpContents pages (in the sidebar). Syntax reference is handy. You can experiment in WikiSandBox.

If you disagree with any statement below, comment it out, then start a new discussion thread in the discussion page.

<<TableOfContents(2)>>

<<Anchor(account)>>

Your Account

* Your wiki username should be in the format "!FirstnameLastname" ("!IrcNickname" or your Debian Developer login are fine too).
* Adjust the timezone in your <<Action(userprefs,sub=prefs)>> page.

Your WikiHomePage

You can use the HomepageTemplate when you create your homepage. Here are ideas for content, grabbed from various existing homepages.

* Your full name.
* Your main homepage outside this wiki.
* Your email address.
* Your location (city and country) ~-useful for timezone considerations and more-~.
* If you use IRC, your usual server, channel and nickname.
* If you are a Debian Developer (DD), your login name (with a link to http://qa.debian.org/developer.php?login=foobar@debian.org).
* Non-DDs can link to [[1]].
* Your subjects of interest (not limited to Debian).
* Your !ToDo/Done list.
* (Some of) Your contributions to open source (bug reporting; writing/translating; developing/maintaining...)

1. 1. HintsnTips is merged in existing Portals
   2. * Some cool hints about Debian + put a copy on HintsnTips.

Make sure you keep the !CategoryHomepage tag at the bottom of your homepage (present by default in the !HomepageTemplate).

Subscribe to pages

* You could subscribe to the pages relevant to your subjects of interest.

<<Anchor(lost-password)>>

Lost Password

If you lose your wiki.debian.org password, go to the page <<Action(recoverpass)>>, then follow the instructions there (type your email address, then click on "Mail me my account data").

<<Anchor(writing-style)>>

Writing Style / WikiEtiquette

There are at least five major styles of Wiki page

* TreeMode
* DocumentMode
* ThreadMode
* NewsMode
* CategoryHomepage

Elements of good style for each type are explained further on their individual pages.

Try to maintain balance when writing. This includes visual balance, but also an attempt to avoid bias. If you find that your comments are controversial, sign them, so that others will feel more free to disagree publicly.

* Don't make !EveryThing into a !UselessWikiName.  Knowing when to make a new page is one of the hardest parts of !WikiStyle.

* !RefactorMercilessly  There is no page in the !WikiUniverse that is finished.  All content can be refined.  See Wiki:RefactoringWikiPages for many useful thoughts.

* If the wiki topic is fairly long, then it would be good style to give a quick overview of what has been discussed in the topic as a sort of concluding paragraph. If a concluding paragraph cannot be easily written then perhaps the scoping of the topic was not right, and it should either be separated into subtopics or merged with others into one larger topic.  This is common when !ThreadMode meanders off topic.

See also this Wiki:GoodStyle page.

<<Anchor(links)>>

Links

Don't overuse linking. If there are too many, the reader won't know which links are useful. You can move some of the links to a "See also" section at the bottom of your page (but again, not too many).

Where links point to a page in another language, append "(in $language)", thus: Something (in French)

See also moinmoin's HelpOnLinking

<<Anchor(internal-links)>>

Internal Links

Internal Links (within this wiki)

1. {{{FooPage}}} is usually the preferred syntax.
2. {{{FooPage}}} is frequently used to shorten subpages.
3. {{{editor guide}}} can be used to help fit the link name into a sentence as normal lower-case words.
4. Don't "rename" the link by using {{{Another title}}} (if you have to do this, it implies the page is misnamed).

In all cases, make sure that the link label is meaningful to visitors, and that the link doesn't lead somewhere unexpected (preferably, the link label should be the same as the page title).

To link within a page, you should define the target anchor using {{{<<Anchor(bar)>>}}} (see HelpOnMacros), then use {{{Bar Chapter}}} or {{{Bar Chapter}}} (where Bar Chapter is the actual paragraph title).

<<Anchor(links-to-www)>>

Links to external sites

The preferred way to link to external resources is:

* [[2]] - Debian Official documentation repository.

(Avoid the notation {{{ [label] }}}, which hides the target URL, unless the context makes it clear, as in "John Doe provides a script named [[3]].")

* Group external links in the last section of the page.
* Call this section External links.
* Any "project homepage" link can go in this section, or (if there are no other external links) a See also section.

Use InterWiki format to link to Debian packages, bugs, RFCs and Wikipedia articles.

<<Anchor(links-from-www)>>

Links from external sites

If an (important) page is linked from outside Debian, it's a good idea to tag it with {{{CategoryPermalink}}}, so that nobody removes it inadvertently.

<<Anchor(formatting)>>

Formatting

<<Anchor(article-header)>>

Header sections

Material that naturally belongs in an (optional) "header" area at the top of the page includes:

* Links to translated versions (make sure they really exist!):
{{{Translation(s): Deutsch - Français}}}
* A Discussion link, for controversial material: {{{(!) Discussion}}}
* Compare DefaultTemplate
* Don't use {{{<<Include()>>}}} macro for translations. Why? Because could overload this Wiki server if it's used on every page. Frontpage is the only exception.

<<Anchor(disambiguation)>>

Disambiguation banner

Sometimes, a page's name can be ambiguous. If this can't be avoided, you can insert something like this at the top of the page: ||<tablestyle="width:65%;margin-left:35%;padding-left:30pt" style="border:1pt solid #b48;border-left:5pt solid #d4a">Disambiguation : This page is about Debian Conferences.<
> For Debian configuration management system, see debconf.||

~-Sample: -~ 

<<Anchor(official)>>

Debian "official material" banner

Often, the content of a Debian wiki page is also covered by some piece of "official" Debian Documentation (or in some other "reference" location). The wiki page can still be useful for collaboration. It's a good idea to add a link to the reference location at the top of the page.

Sample link presentation to some official page, related to the current subject.

1. 1. OLD##||<tablestyle="width:100%;" style="width:32px;border-color:#ff9ec2" >Template:Attachment:Portal/IDB/official-doc.png||<style="border-color:#ff9ec2;background-color:#ffe4f1" >http://www.debian.org/somewhere - Sample topic||

{{{#!wiki debian

http://www.debian.org/somewhere - Sample topic }}}

~-Sample: -~ {{{{

{{{#!wiki debian http://www.debian.org/somewhere - Sample topic }}}

}}}}

The logo's license is Portal/IDB#debian-official-doc-modif-fpiat.

Table of Contents sections

If a page gets long, you might want to add a Table of Contents. See the example at the top of this page!

~-Sample (note how the table is indented with one space): -~ {{{
<<TableOfContents(2)>>

}}}

FAQ sections

A typical FAQ section could be formatted like this:

Q. How do I do XXXX? :: A1) You can do XXXX by doing X.
:: A2) You can do XXXX by doing Y.
~-Sample (notice the space at the beginning of the lines): -~ {{{
Q. How do I do XXXX? :: A1) You can do XXXX by doing X.
:: A2) You can do XXXX by doing Y.

}}}

<<Anchor(footer)>>

Footer sections

Material that naturally belongs in an (optional) "footer" area at the end of the page includes:

* "See also" sections
* Link to "Parent Page : ParentPageName" (if the page is a !SubPage).
* Categories to mark connections with other pages
* Credits for attachements
* Work Needed tags
* Compare DefaultTemplate

Page Fragments

Not only code can be be reused - page content can too! If you notice that a given paragraph has to be repeated on many pages, you can reuse ("include") a page fragment each time. (Do not abuse this to duplicate content everywhere!)

* A page meant to be included in another should be named */!PageFragment/*
* Add a hidden comment ({{{##}}}) at the top of the page so people understand why it's "incomplete" (a fragment!)
* See the {{{<<Include()>>}}} macro in HelpOnMacros

A sample is available at InstallingDebianOn and InstallingDebianOn/PageFragments/Philosophy. Also note how the page is included inside a table (but don't use this hack to bypass moinmoin formatting limitations: see Complex Formatting).

<<Anchor(complex-formatting)>>

Advanced Formatting/Complex Formatting

``Avoid`` using "advanced" formatting (using tables, include, etc.)

* It's difficult to understand and maintain for you and other wiki editors.
* It's difficult to read the {{{diff}}} of complex formatting.
* The GUI editor may break your layout.

<<Anchor(images)>>

Images, media and attachments

See also: moinmoin's HelpOnLinking.

<<Anchor(attachments-credits)>>

Credits and copyright

Add credits and copyright information at the bottom of the page where you attach an image, typically: {{{

1. 1. attachments:
   2. openlogo-100.jpg Copyright 1999 "Software in the Public Interest" from http://www.debian.org/logos/openlogo-100.jpg

}}}

<<Anchor(attachments-location)>>

Attachment location

It's often a good idea to attach the image to the parent page (in case the image is reused in other subpages).

For translated pages, attach the image to the English version (internationalized/localized images should be attached to the internationalized/localized pages).

<<Anchor(screenshots)>>

Screenshots

If you want to include a screenshot, you might want to store it on [[4]], then use :

{{{
[Template:Http://screenshots.debian.net/thumbnail/amide] 

}}}

* Note the package name appears __twice__ in  this block.

Example:

[Template:Http://screenshots.debian.net/thumbnail/amide] 

Image position

||<tablestyle="float:right; width:100px; background:transparent; margin: 0 0 1em 1em;" style="padding:0.5em; border-style:none;"> Template:Http://www.debian.org/logos/openlogo-nd-75.jpg ||

It is possible to shift the images to right of the page, thanks to CSS' {{{float:right}}}:

* Note: adjust {{{width:100px}}} to fit your need.

<<Anchor(tags)>>

"Work needed" tags

<<Include(WikiTag)>>

Note: do not use the [[5]] processing instruction, as it prevents further editing of the page (e.g. to fix broken links). If you need to mark a page as needing to be improved/removed, use an appropriate WikiTag instead.

These tags are meant for wiki editors, not for visitors, so don't make them too intrusive; instead of putting a warning tag at the top of the page, insert it in the page's footer.

<<Anchor(pages)>>

Pages

<<Anchor(pages-name)>>

URL/page naming conventions

* Use only MoinMoin:CamelCase formatting (as opposed to Underscore_Separated).
* The first letter of the first word should be upper case.
* Special characters should be avoided in page names.
* Slashes function to create (directory-style) groups of related subpages. If your page clearly belongs to a collection, you might consider creating it as a subpage - see for example the Moinmoin documentation SubPages.
* For translated pages, see Translation section.
* Picking an appropriate name is important. It should clearly state what the page is about and should contain the word visitors will search for.
* Avoid ambiguous names - don't use, for instance:
 * "About"... about what?  About the Debian OS, community, wiki...?
 * "Release"... does it mean previous releases, the current stable release, the release life-cycle, future release status, release process, release team, etc... 

<<Anchor(create)>>

Creating a page

Before you create a page, ask yourself some questions:

* Is a new page really needed? Might it already exist under a different name? Could the content be added to an existing page?
* Does it comply with the wiki.debian.org Content guidelines?

link If you decide to proceed:

* Choose a unique name for the page - see URL/page naming conventions.
* Search the CategoryPortal page for an appropriate portal page (you may find more than one - choose the best) and click on it
* Once on the portal page, click on the Edit link and add the name of the new page you want to create (with "link" formatting) to the existing list of page links
* Save the edited portal page and then click on the "?" link in front of the new page that is to be created; this will take you to a page where you have the option to create the new page
* You can then either create a blank page, but the recommended option is to pick the appropriate template - !DefaultTemplate is the recommended one
* If your page relates to a subject already covered by some official Debian documentation, link to it at the top (see Debian official material)
* Once the page is complete, make links to it from relevant pages (one link is often enough).
* More hints:
 * Re-read it two days later (does it still look good?)
 * Subscribe to that page.
 * This page isn't "yours", so don't be offended when other people "improve" it.

See also: moinmoin's HelpOnPageCreation.

<<Anchor(rename)>>

Renaming a page

Cool URIs don't change ([[6]]). Still, sometime it's a good idea to rename a page when its name don't accurately describe the page content.

__Before you rename a page: __

* Verify that this page isn't tagged with CategoryPermalink.
* Use Google (or equivalent) to check whether the page is linked from outside this wiki. Search {{{link:wiki.debian.org/FooBar}}}. If it is referenced, think twice before renaming the page. If you rename the page, consider creating a redirect page and contacting the owner of the referring page to get the links updated.
* Check if this page is linked from inside this wiki (open the page and click on the title to get the list of back links).

If you decide to actually rename the page:

* Choose a name for a page. see URL/page naming conventions.
* Make sure you update all the pages that used to point to the old name (type the previous page name into the search bar, then click "Text"!).
* Also take care of translated versions of the page.

Note: If the page-rename seems to require a "redirect" page, that might mean that the page shouldn't be renamed!

<<Anchor(delete)>>

Deleting a page

Read the Renaming a page hints, since they apply here too.

If you think a page should be removed, you can either:

* Delete the page yourself (writing your rationale in the comment field).
* or Tag the page with "!CategoryProposedDeletion" so other editors can react (i.e. put the tag and explanation at the bottom of the page). 

Don't be rude: do not copy-paste the content of an existing page into a new one, and delete the old page - this loses page history. Instead see Merging and splitting pages.

Again, if there are translated versions, deal with them too!

<<Anchor(merge-and-split)>>

Merging and splitting pages

Reorganizing pages is a good idea. You are encouraged to:

* Merge "duplicate" pages covering the same subject.
* Merge similar page, if both are "too short".
* Split long pages that cover more than one topic (but consider adding a {{{<<TableOfContents>>}}} instead.).

Try to preserve page history:

* Use the Comment field to record the "before" and "after" page-names in splits or mergers.
* Merge pages into one of the existing pages, not into a newly created page.

For translations: if you can't merge/split translated pages, add directions (comments) in the translated version so translators can keep up!

<<Anchor(redirect-page)>>

Redirect pages

On some occasions, you might want to create a "redirect" page (which automatically redirects the browser to the proper page).

Don't over-use this tool.

sample : {{{

1. redirect DestinationPage

go to DestinationPage }}}

Note that {{{#refresh}}} isn't enabled on this wiki.

1. 1. If the page was moved you can use :
   2. {{{
      1. refresh 5 DestinationPage
   3. This page moved. update your bookmark : DestinationPage
   4. }}}

See also: moinmoin's HelpOnProcessingInstructions.

<<Anchor(categories)>>

Categories

moinmoin wiki's help: using categories.

The list of categories used on this wiki: CategoryCategory.

<<Anchor(portal)>>

Portals

Portals are hub pages containing links to articles. They complement the relational structure offered by CategoryCategory, and the integrated search engine.

Portal pages should be based on PortalTemplate.

1. 1. GUI EDITOR IS DISABLED in moinmoin 1.7 ## Do not use Edit(GUI) since it will break some wiki contents ([editing to text breaks contents], and some wiki link formats).

<<Anchor(portal-howto)>>

Turning pages into portals

To make your article into a portal page, add the tag !CategoryPortal to its footer and find an appropriate portal to attach it to.

Don't create portals full of dead links.

<<Anchor(portal-idb)>>

Image Data Base

Commonly-used icons and portal logos can be centralized to Portal/IDB. This is useful for translated portals and for making artwork consistent.

<<Anchor(translation)>>

Translations

<<Anchor(link-to-translations)>> The top of each page shows links to the same page in other languages - see Headers, and DefaultTemplate as an example.

<<Anchor(translation-page-name)>> The principles:

* Any topic given a wiki page may have many translations, but there is always one "base" page.
* Since this master copy has to be in some language, we standardize on using the US English version.
* Translated pages use the naming scheme "[[7]]" + "/" + "!EnglishName" - for example:
 * Base version: Hardware
 * French translation: fr/Hardware
* When you modify a translated page, update or notify the English version too.
* Try to keep the layout the same in every language, since it simplifies synchronization (especially, editors who aren't fluent in your language will still have some chance of finding and updating the right element).
* If the page doesn't exist in English, create that too. If you don't feel comfortable writing in English, just create a page with the usual headers and link to your translated page, making sure you tag your page with Update``English.
* If the page doesn't exist in your language, start by copy/pasting it from the English version and updating the page header to match the page name, then see below.

<<Anchor(translation-synchronize)>>

Synchronizing translations

When you're updating a page to match one in another language (i.e. "synchronizing" the versions),

* All versions of a page should keep the same layout (formatting, paragraph order, etc.).
* Keep the revision status of the page clear:
 * (either) update the whole page at once, and then change the matching "revision" number in the header
 * (or) add a comment like {{{## TRANSLATION UPDATE STOPPED here}}} where you stop.
* If the translated page is newer than the English one:
 * (either) update the English version yourself if you can (don't worry about minor language errors - someone will correct them)
 * (or) append an "!UpdateEnglish" tag at the bottom of the page, and add "+ IMPROVEMENTS" to the English revision comment.

<<Anchor(translators)>>

Wiki translators

People involved in translating Debian Wiki pages should add the tag !CategoryWikiTranslator on their homepage.

<<Anchor(helping)>>

Helping with wiki.debian.org

Anybody can help to improve wiki.debian.org:

1. 1. * Delete Spam : ["DealingWithSpam"]

* Improve the content of any page, where you can.
* Add your remarks and questions at the bottom of the wiki pages you visit.
* Spellcheck pages (many contributions are made by non-native English speakers).
* Translate pages.
* Search for backlinks to HelpWanted, FixMe and ToDo.
* ReFactor anything you can.
* Cleanup (see ThreadMode)
* Pass on your knowledge on how to install or use Debian
* If you don't work in IT, you can create a page to explain how you use computers in your day-to-day work. Explain your problems and needs.

Debian also needs non-IT skills (legal; marketing; organizing events; fund-raising; public relations; and much more). See also [[8]].

<<Anchor(promote)>>

Promoting wiki.debian.org

The best and easiest ways to promote this wiki are to use it yourself and to make it useful to others by contributing useful material (bear in mind the content guidelines).

When you are asked a question in a mailing list, forum, or irc channel,

* the first and best option is to point inquiries towards the official Debian documentation (www.debian.org/* , man page, README, etc.), suggesting improvements to the author or maintainer if necessary;
* the second best is to update the appropriate wiki page to make sure it answers the question, and point towards that.

<<Anchor(faq)>>

Frequently Asked Questions

Q) Can I get a list of all the pages on this wiki? :: A) Yes, see TitleIndex

Q) Wouldn't the wiki be more useful if it was better organized? :: A) Possibly, but a structured wiki is largely a contradiction in terms.  It's more important to give it good content.

1. 1. As an argument, http://c2.com/cgi/wiki?LimitsOfHierarchies is irrelevant (structure != rigid hierarchy)
   2. but it does raise incoherent unhelpfulness to the level of an art form.

Q) Is there a way to show just the orphan articles? :: A) No (OrphanedPages is broken; links in the form {{{Link Label}}} aren't counted). But being an orphan is only a problem if there are pages that should link to it and don't (so fix those), or if the page fails to show up in searches (so make sure it includes the appropriate keywords).

<<Anchor(pages-changes)>>

1. 1. fouled anchor; what happened here?

<<Anchor(track-changes)>>

Q) How do I keep track of changes? :: A) By using two features accessible via the sidebar menu:
 * the link to the Recent``Changes page (limited to a week for visitors, 90 days for logged-in users);
 * the Subscribe option, which requests e-mail notification when the page is modified.

1. 1. NB: these next two are nowhere to be found. Pre-moinmoin relics?
   2. * the History of a page Page (the list is limited in number of entries, usually enough for normal pages.)
   3. * the list of User contributions (AFAIK, moinmoin offers no way to summarize someone's contributions).

<<Anchor(technical)>>

Technical Information

This Wiki is running [[9]] software, version 1.9 (wiki configuration information). It currently runs on a machine sponsored by [Goo Informatik GmbH & Co KG] (both hardware, housing and bandwidth).

---

Moin Syntax, copied from https://wiki.debian.org/HelpOnMoinWikiSyntax

1. 1. page was renamed from SyntaxReference
   2. master-page:Unknown-Page
   3. master-date:Unknown-Date
2. acl -All:write Default
3. format wiki
4. language en

Moin Wiki Syntax

<<TableOfContents()>> This page aims to introduce the most important elements of MoinMoin``'s syntax at a glance, showing first the markup verbatim and then how it is rendered by the wiki engine. Additionally, you'll find links to the relative help pages. Please note that some of the features depend on your configuration.

Headings and table of contents

see: HelpOnHeadlines {{{ Table of contents: <<TableOfContents()>>

Table of contents (up to 2nd level headings only): <<TableOfContents(2)>>

heading 1st level

heading 2nd level

heading 3rd level

heading 4th level

no heading 6th level

}}} {{{#!wiki dashed Table of contents: <<TableOfContents()>>

Table of contents (up to 2nd level headings only): <<TableOfContents(2)>>

heading 1st level

heading 2nd level

heading 3rd level

heading 4th level

no heading 6th level

}}}

Text Formatting

see: HelpOnFormatting ||<rowbgcolor="#ffffcc" width="50%"> Markup || Result || || `italic` || italic || || `bold` || bold || || {{{`monospace`}}} || `monospace` || || `{{{code}}}` || {{{code}}} || || `__underline__` || __underline__ || || `^super^script` || ^super^script || || `,,sub,,script` || ,,sub,,script || || `~-smaller-~` || ~-smaller-~ || || `~+larger+~` || ~+larger+~ || || `--(stroke)--` || --(stroke)-- ||

Hyperlinks

see: HelpOnLinking

Internal Links

||<rowbgcolor="#ffffcc" width="50%"> Markup || Result || || `FrontPage` || FrontPage || || `FrontPage` || FrontPage || || `HelpOnEditing/SubPages` || HelpOnEditing/SubPages || || `/SubPage` || /SubPage || || `../SiblingPage` || ../SiblingPage || || `named link` || named link || || `#anchorname` || #anchorname || || `description` || description || || `PageName#anchorname` || PageName#anchorname || || `description` || description || || `attachment:filename.txt` || attachment:filename.txt ||

External Links

||<rowbgcolor="#ffffcc" width="50%"> Markup || Result || || `http://moinmo.in/` || http://moinmo.in/ || || `[[10]]` || [[11]] || || `[Wiki]` || [Wiki] || || `[[12]]` || [[13]] || || `Template:Http://static.moinmo.in/logos/moinmoin.png` || Template:Http://static.moinmo.in/logos/moinmoin.png || || `[[14]]` || [[15]] || || `MeatBall:InterWiki` || MeatBall:InterWiki || || `[MeatBall:InterWiki|InterWiki page on MeatBall]]` || InterWiki page on MeatBall || || `link to filename.txt` || link to filename.txt || || `user@example.com` || user@example.com ||

Avoid or Limit Automatic Linking

||<rowbgcolor="#ffffcc" width="50%"> Markup || Result || || `Wiki'Name` || Wiki'Name || || {{{Wiki``Name}}} || Wiki``Name || || `!WikiName` || !WikiName || || `WikiName's` || WikiName's || || {{{WikiName``s}}} || WikiName``s || || {{{`http://www.example.com`}}} || `http://www.example.com` || || `[[16]]notlinked` || [[17]]notlinked ||

Drawings

see: HelpOnDrawings

TWikiDraw

Template:Drawing:myexample

AnyWikiDraw

Template:Drawing:myexample.adraw

Blockquotes and Indentations

{{{

indented text
 text indented to the 2nd level

}}} {{{#!wiki dashed

indented text
 text indented to the 2nd level

}}}

Lists

see: HelpOnLists

Unordered Lists

{{{

* item 1

* item 2 (preceding white space)
 * item 2.1
  * item 2.1.1
* item 3
 . item 3.1 (bulletless)
. item 4 (bulletless)
 * item 4.1
  . item 4.1.1 (bulletless)

}}} {{{#!wiki dashed

* item 1

* item 2 (preceding white space)
 * item 2.1
  * item 2.1.1
* item 3
 . item 3.1 (bulletless)
. item 4 (bulletless)
 * item 4.1
  . item 4.1.1 (bulletless)

}}}

Ordered Lists

with Numbers

{{{

1. item 1
  1. item 1.1
  1. item 1.2
1. item 2

}}} {{{#!wiki dashed

1. item 1
  1. item 1.1
  1. item 1.2
1. item 2

}}}

with Roman Numbers

{{{

I. item 1
  i. item 1.1
  i. item 1.2
I. item 2

}}} {{{#!wiki dashed

I. item 1
  i. item 1.1
  i. item 1.2
I. item 2

}}}

with Letters

{{{

A. item A
  a. item A. a)
  a. item A. b)
A. item B

}}} {{{#!wiki dashed

A. item A
  a. item A. a)
  a. item A. b)
A. item B

}}}

Definition Lists

{{{

term:: definition
object::
:: description 1
:: description 2

}}} {{{#!wiki dashed

term:: definition
object::
:: description 1
:: description 2

}}}

Horizontal Rules

see: HelpOnRules {{{

---

---

---

---

---

---

---

}}} {{{#!wiki dashed

---

---

---

---

---

---

---

}}}

Tables

see: HelpOnTables

Macros and Variables

Macros

see: HelpOnMacros

* <<Anchor(anchorname)>>`<<Anchor(anchorname)>>` inserts a link anchor `anchorname`
* `<
>` inserts a hard line break
* `<<FootNote(Note)>>` inserts a footnote saying `Note`
* `<<Include(HelpOnMacros/Include)>>` inserts the contents of the page `HelpOnMacros/Include` inline
* `<<MailTo(user AT example DOT com)>>` obfuscates the email address `user@example.com` to users not logged in

Variables

see: HelpOnVariables

* `@``SIG``@` inserts your login name and timestamp of modification
* `@``TIME``@` inserts date and time of modification

Smileys and Icons

see: HelpOnSmileys <<ShowSmileys>>

Parsers

see: HelpOnParsers

Verbatim Display

{{{{ {{{ def hello():

   print "Hello World!"

}}} }}}}

{{{ def hello():

   print "Hello World!"

}}}

Syntax Highlighting

{{{{ {{{#!highlight python def hello():

   print "Hello World!"

}}} }}}}

{{{#!highlight python def hello():

   print "Hello World!"

}}}

Using the wiki parser with css classes

{{{{ {{{#!wiki red/solid This is wiki markup in a div with __css__ `class="red solid"`. }}} }}}}

{{{#!wiki red/solid This is wiki markup in a div with __css__ `class="red solid"`. }}}

Admonitions

see: HelpOnAdmonitions

{{{{ {{{#!wiki caution Don't overuse admonitions

Admonitions should be used with care. A page riddled with admonitions will look restless and will be harder to follow than a page where admonitions are used sparingly. }}} }}}}

{{{#!wiki caution Don't overuse admonitions

Admonitions should be used with care. A page riddled with admonitions will look restless and will be harder to follow than a page where admonitions are used sparingly. }}}

Comments

see: HelpOnComments

{{{ Click on "Comments" in edit bar to toggle the /* comments */ visibility. }}} {{{#!wiki dashed Click on "Comments" in edit bar to toggle the /* comments */ visibility. }}}

{{{{ {{{#!wiki comment/dashed This is a wiki parser section with class "comment dashed" (see HelpOnParsers).

Its visibility gets toggled the same way. }}} }}}}

{{{#!wiki comment/dashed This is a wiki parser section with class "comment dashed" (see HelpOnParsers).

Its visibility gets toggled the same way. }}}