The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.
Help:Funtoo Editing Guidelines
This guide is meant to serve as a reference for those who are interested in helping improve the Funtoo Wiki.
First, to perform edits on the wiki, you must Create a Funtoo account and log in.
You can create a new page by navigating to http://www.funtoo.org/New_Page_Name. Underscores are the equivalent of spaces. Then click the "Create" button in the upper right.
Whether creating a new page or editing an existing page by clicking "Edit", you will be presented with Web-based text editor that allows you to modify the wikitext of the page. The wikitext is rendered to produce the document you see when you view the page normally.
This wiki uses the ApprovedRevs Extension, which means that any changes you make to a page will need to be approved by an Editor before they are displayed. Editors can visit the Special:ApprovedRevs page to approve edits made on pages (click "Pages whose approved revision is not their latest" or "Unapproved pages".)
Until your edits are approved, you can continue to edit the page and your changes will be displayed in the page's History -- click "View History" in the upper right to view the page's history. You will see that the approved version of a page has a star next to it.
Another fun thing you can do is click on your name in the upper right once you have logged in. This will bring you to your "User" page. Then click "Create with Form" and enter your geographic and other information. This will allow you to be displayed on our Usermap and will also allow your full name to be displayed on Ebuild pages for which you are an author. It's generally a good idea to do this.
The following sections document how to use wikitext and Funtoo templates on the Funtoo wiki.
Paragraphs
To create a new paragraph, insert a blank line between two lines of text. If a blank line doesn't exist between two lines of wikitext, they will be combined into a single flowing paragraph.
Page and Section Capitalization
In general, capitalize all words in page names and section heading except:
- Articles: a, an, the
- Coordinating Conjunctions: and, but, or, for, nor, etc.
- Prepositions (fewer than five letters): on, at, to, from, by, etc.
Document Heirarchy
Use section headings to create a document heirarchy for your page. These will define the table of contents that appears at the top of the wiki page.
The above top-level section was inserted using:
= document hierarchy structure =
document hierarchy sub structure
Sub-sections can be created as follows, or use these as your main sections:
== document hierarchy sub structure ==
this is the primary structure most pages, talk pages will use instead of main heading example above. some pages will call for main heading.
document hierarchy sub sub structure
Now, we can create third-level sections:
=== document hierarchy sub sub structure ===
document hierarchy sub sub sub structure
==== document hierarchy sub structure ====
Console
To display console output, use the <console> tag:
For a root console:
<console> ###i## run a command as root </console>
Produces:
root # run a command as root
The ##i## text tags the rest of the line as being user input ("i" is for "input"). It is then highlighted in a noticeable color so it stands out from text that is not typed in by the user.
Examples of usage:
For a non-root console:
<console> $ ##i##run a command as user </console>
Produces:
user $ run a command as user
Note that we use a # prompt for root and a $ prompt to denote a non-root user.
Examples of usage:
or a more concise syntax
Fancy Notes
notes, warnings, tips, and important templates will help bring emphasis to articles drawn up.
{{fancynote|this is a fancy note}}
this is a fancy note
{{fancyimportant|this is a fancy important}}
this is a fancy important
{{fancywarning|this is a fancy warning}}
this is a fancy warning
{{fancytip|this is a fancy tip}}
this is a fancy tip
Kernelop
To display kernel configuration options, we encourage you to use the kernelop template. To use the kernelop template, create an entry similar to the following example:
{{kernelop|title=foo,bar|desc=
kernel options pasted from "make menuconfig"
}}
Kernelop is colored blue to slightly resemble the blueish background from make menuconfig.
Adding this entry will give you the following output:
Under foo-->bar:
kernel options
Here's a more concrete example:
Under File systems:
<M> Second extended fs support [ ] Ext2 extended attributes [ ] Ext2 execute in place support <M> Ext3 journalling file system support
Examples of usage:
links
Internal links to other wiki pages can be specified as [[pagename]]. To specify an alternate name for the link, use [[pagename|my link name]].
For external links, use [http://funtoo.org my link] to specify a URL. If you want the URL to appear in the wikitext, you can specify it without brackets: http://forums.funtoo.org.
Displaying Source Code
To display source code, use the <syntaxhighlight> tag, which has the ability to perform syntax highlighting on the source code for easier reading:
<syntaxhighlight lang="python"> import system </syntaxhighlight>
This will produce the following output:
import system
Alternatively, if you need a caption, use can use the file template, specifying a lang= parameter:
{{file|name=foobar|lang=python|desc=foobarosity|body=
import system
}}
This will produce:
foobar (python source code) - foobarosityimport system
Note that the language should be specified in the lang attribute. For a list of supported languages, see this list.
Displaying Text File Contents
For displaying the contents of non-programming language text files (like config files), you have two options. You can enclose your lines within <pre> tags, or use the new file template. The file template is used like so:
{{file|name=/etc/foo.conf|desc=My foo.conf file|body=
# /etc/host.conf:
# $Header: /var/cvsroot/gentoo/src/patchsets/glibc/extra/etc/host.conf,v 1.1 2006/09/29
}}
This will produce:
/etc/foo.conf - My foo.conf file# /etc/host.conf:
# $Header: /var/cvsroot/gentoo/src/patchsets/glibc/extra/etc/host.conf,v 1.1 2006/09/29
Marking Pages as Needing Updates
If you find outdated wiki content, but you don't have the time or ability to update it, add one of the following templates to the wikitext of the page. This will add the page to the Needs Updates Category so we can identify pages that need updating:
{{PageNeedsUpdates}}
{{SectionNeedsUpdates}}
Displaying Files
To display the contents of a file that is not source code, use the </pre> tag. The </pre> tag preserves formatting. Example file contents:
foo bar oni
Examples of usage:
<tt> and <code>
To emphasize filenames, commands, and other technical jargon when they appear inline in a paragraph, use the <tt> or <code> option. To use these, follow the example below:
The <tt>/etc/fstab</tt> file is an important one. Another important file is <code>/boot/grub/grub.cfg</code>.
This example produces the following output (notice the difference between the fonts?):
The /etc/fstab file is an important one. Another important file is /boot/grub/grub.cfg.
Collapsible text
<div class="toccolours mw-collapsible"> some text you might want to fold away because its a huge explanation.</div>
<div class="toccolours mw-collapsible mw-collapsed">pre collapsed text because it is a huge explanation.</div>
Screencasting
screencasting is an easy method to explain complex tasks. take for instance youtu.be/5KDei5mBfSg we chop off the id and insert it into the following syntax to produce a video example.
tiny:
{{#widget:YouTube|id=5KDei5mBfSg|width=320|height=180}}
standard:
{{#widget:YouTube|id=5KDei5mBfSg|width=700|height=420}}