- - This page is hard to read and/or its content needs to be updated. Please improve this page and remove this box when you are done.
- This page should be merged with TechDocs/Wiki/NewUserGuide
This page is meant to be the first reference for new users in the FSFE, regardless if you're a volunteer or Fellow of the FSFE. Please have a look at it before starting using the wiki or any other services, and you won't regret it!
You are also encouraged to read the wiki FAQ.
Each user automatically has an account on this wiki: just use your usual username and password to login.
Each wiki user has his or her own user page at http://wiki.fsfe.org/Fellows/yourname . You can create this page using this form:
Enter your username here:
The manual approach:
You can create your own user page by logging in and clicking on the yourname link on the first line of the screen.
When creating your page, choose HomepageTemplate to get a page with a basic structure you can improve.
- Alternatively, make sure that your page belongs to !Category/Homepage using the "Add to:" menu in the page editor.
Please note that Fellow usernames (like all names on the wiki) are case-sensitive.
You can add a fancy link to your userpage (like the one at the top of the screen) by writing Fellows:yourname (yes, with a colon instead of a slash).
If you never used a wiki, you are encouraged to have a look at the basic moinmoin syntax, which is explained at length in the HelpOnEditing page (see also the HelpForBeginners and the WikiCourse pages).
Here we just list some suggestions about some of the most useful Moinmoin features:
Templates: when you create a new page, you can choose to start from a template, selecting it from the list in the page creation page (see HelpOnTemplates for information on Moinmoin templates).
Variables: you can use special variables that are automatically expanded, e.g. <<Date(2008-11-25T15:41:37+0100)>>, @USERNAME@, etc. (see HelpOnVariables for further info)
Macros: Moinmoin provides some macros to add extra functionality to your pages; some examples:
The <<TableOfContents>> macro adds a table of contents of the current page.
The MailTo macros provide an antispam feature if you have to include e-mail addresses in the page, to make it more difficult for spam bots to get e-mail addresses from the pages.
Image galleries and attachments: the wiki provides the Arnica Moinmoin extension (formerly known as Gallery2). To create a gallery, just attach images to a page and define their formatting using the syntax described in the Arnica help page. Please avoid attaching image files larger than 200Kb.
You can edit wiki pages with Moinmoin web-based editors: the text-based one and the GUI-based one.
Alternatively, you can use your favourite text editor, using one of the following tools.
cri: the current version of itsalltext seems to have this bug: if you start making some changes with the editor invoked by itsalltext, save the temporary file, click on the moinmoin "Preview" button, and then make other changes, these last changes won't be passed to Moinmoin. To repeat multiple edit-preview cycles, you have to:
Press the Moinmoin Edit link
Press the Moinmoin Preview button
- Click on the itsalltext icon and start the edit-preview cycle
cri: I had a quick look at this but I couldn't figure out easily if it works with our kind of authentication
A wiki gives users a lot of freedom to create and organize information.
To ease collaboration, we try to follow some common rules.
Moinmoin supports both CamelCase syntax for page names and the free link syntax.
One advantage of using short camel-case page names is that CamelCase words are automatically displayed as links by Moinmoin.
One advantage of longer non-camel-case page names is that you can use a more convenient free link syntax in situations like:
"GNU is part of the [[history_of_free_software]]."
"GNU is part of the [[History/FreeSoftware|history of free software]]."
So far the majority of users seems to like the free link solution more than the camel case one; anyway, both are technically acceptable, we recommend choosing one and keeping consistency in all pages that are somehow related.
Pages translated from an original page should append _xx (or replace _en) where xx is the language code for the language of the translation. This should then help the Wiki show available languages for the original page and for all the different translations. Remember to add a language declaration in the page content as described in this help section.
For example, a French translation of the Advocacy page should be called Advocacy_fr, and a French translation of the Advocacy_faq_en page should be called Advocacy_faq_fr. In the content of such pages, a declaration should be provided as follows:
Overriding the page title
Each page has a title which appears in the green box at the top of each page's content, and this title is typically derived from the page name. Thus, the UserGuide page has the title "User Guide". In some circumstances it can be desirable to override this automatically generated title with one of your own choosing. For example, when providing a translated page, it is probably highly desirable to use a title in the language employed by the translation.
To override the page title - for example, for the SupportPrograms_de translated page, where the automatically generated title is "Support Programs (Deutsch)" - add the following style of declaration to the very top of the page content:
#pragma title Unterstützerprogramme
When the page is displayed, the overridden title will appear in the green box at the top of the page's content.
It is also possible to define hierarchical titles. For example:
#pragma title groups #pragma title Rhein/Main
This produces a title of "groups » Rhein/Main", permitting the definition of a hierarchical title and usage of the / character in the title without it being interpreted as a special hierarchical separator. (A page name of groups/Rhein/Main will normally produce the title "groups » Rhein » Main" because / is generally regarded as providing a new level in the page name hierarchy.)
Moinmoin offers the ''subpage'' feature (which is sometimes called namespaces in some other wikis).
Some advantages of using subpages:
- Users can subscribe to all subpages of a given page and receive email notification for changes made to all these pages
- Optionally, different access control lists could be enforced on all subpages of a given page
Here are the subpage-namespaces that we are already using:
/Fellows/ : this is used automatically by moinmoin for user home pages
/FellowshipGroup/ : homepages of local Fellowship groups
/FellowshipProjects/ : projects, campaigns etc run by Fellows and Fellowship groups
/FellowshipHacks/ : projects related to the Fellowship technological infrastructure
Some other subpages that we could consider using:
A little gotcha that might confuse newbies: when you create a link to a subpage, if you start the page name with a slash (/NewPage) the link will point to a subpage of the current page, not of the "root" page (if you want the latter behaviour, just drop the initial slash). Yes, it works just the opposite way of a usual filesystem. Ask Moinmoin why
Moinmoin offers the category feature. To learn how to use it, please read HelpOnCategories.
At the moment we are using the following categories: