View source for Contributing Content

[[Category:Support]]
[[Category:Wiki_Development]]
[[File:Self parking ale-inn.jpeg|thumb|right|420px|<small><small>A sign in the car park outside the 'Little A'Le'Inn' (ale inn) in Rachel, Nevada, USA.</small></small>]][[File:Forestrycommision england rendlesham suffolk UFO trail.jpeg|thumb|right|420px|<small><small>A sign on the 'UFO trail', Rendlesham Forest, Suffolk, England.</small></small>]]
__TOC__
<br clear=all>
== Introduction ==
We could really use all the help we can get. Thank you for taking an interest in helping us present the Billy Meier and FIGU information in English.

This Wiki uses technology that allows anyone to add or edit content, we work together, and you don't need to be a computer programmer to learn how it is done. The technology is called [http://www.mediawiki.org/wiki/MediaWiki MediaWiki].

We collectively, you and readers like you all appreciate having good access to this information in English and it all being presented well. We appreciate that such voluntary (self parking) helpers, assistants and contributors are going to be rare, even when the will and motivation is there, because it is requiring long term dedication to learning how it all works. We recommend starting with simple things at first and to build a knowledge of it all. If you would like to get involved and work out how it all works, we would be delighted to have you onboard. Introduce yourself to the website owner using the contact details on the main page.

'''Before beginning'''<br>
Please have a read through the [[FIGU]] page, https://www.figu.org/ (German language isn't necessarily a requirement, but please be aware of it) and relevant FIGU documents, to appreciate their advice, position and understand the temperament that has been adopted. Future Of Mankind is ''somewhat'' and generally aligned with FIGU and its values, we think they are good values, but be aware this isn't an official FIGU website, even though we make every effort to meet their standards. FIGU's textbooks are for one's own education, we're not therefore trying to convince anyone, nor are we propagandizing or missionising the information and we therefore prefer individuals not 'believe' the story. What e.g. [[Michael Horn]] and others -[[External Links]] are doing is their thing, fundamentally Future Of Mankind is a wiki and encyclopedia. Your role as editor of the website may take many forms depending on what area you've decided to lend a helping hand, mind with and may evolve, but bear that most of all we're presenting the original information as best we can and as neutrally as we can present it, also aesthetically pleasant.

The trust that our audience has in all our content underpins everything that we do. We are independent, impartial and honest. We are committed to achieving the highest standards of accuracy and impartiality and strive to avoid knowingly or materially misleading our audiences.

Our commitment to impartiality is at the heart of that relationship of trust. In all our output we will treat every subject with an impartiality that reflects the full range of views. We will consider all the relevant facts fairly and with an open mind.

Please keep it light, friendly and welcoming for everyone.


See [[Contributing_Content#List_of_things_you_could_help_with|List of things you could help with]]



As a volunteer you do not have a contract of employment, we're never going to expect or demand anything of you. This page here constitutes the guidance being offered and communication is by email. Volunteering is a selfless act of goodwill. Individuals are responsible for themselves. All contributions that are made, fall under the Future Of Mankind copyright if it doesn't already fall under FIGU copyright, which is designed to protect the integrity of the information in the perilous environment of the internet from distortions and falsifications (Something like CC BY 4.0). The website owner reserves the right to rollback a contribution and even to terminate your user account if necessary at any time in the event of misconduct.

==Setting up an account==
# In order to make a contribution to this Wiki you must first create an account and then login with that account. Click on ''Log in / create account'' in the top right-hand corner of the page then enter the requested information.
# Then send an e-mail to [contact details on main page] requesting you be made an "editor". Please state your Wiki username, full name  and home address and describe the changes or additions you intend to make to the Wiki once you are given access. This extra step is required to further reduce spam and vandalism.
# You can now create and edit pages (unprotected ones only).
# (Optional) Add your personal details to your user page (click on your username at the top of the page).
# (Recommended) I recommend you refer to the [http://meta.wikimedia.org/wiki/Help:Contents MediaWiki Handbook] to learn how to edit a page.
# (Recommended) Contributors should sign in and contribute to the .co.uk domain not the .info domain. The .info domain is a mirror / copy, and the .co.uk is the master, the .co.uk overwrites / syncs to the .info domain every night. However the .info is on a faster server, so as editor it's recommended to promote the use of it on social media if you do that.

== Wiki Rules ==

When submitting new articles you '''must''' try your best to ensure that:

* you include one of the following tags at the top of the article to include the relevant notice template:
** &#123;&#123;Officialauthorised&#125;&#125;
** &#123;&#123;Unofficialauthorised&#125;&#125;
** &#123;&#123;Unofficialunauthorised&#125;&#125;
** These get displayed as the following notices when the article is saved:
{{Officialauthorised}}<br />{{Unofficialauthorised}}<br />{{Unofficialunauthorised}}
* if appropriate, also include the following tag
** &#123;&#123;Nonfigupublication&#125;&#125;
** This displays the following notice:{{nonfigupublication}}
* if appropriate, also include the following tag
** &#123;&#123;Necessaryprerequisitetoundestandingthisdocument&#125;&#125;
** This displays the following notice:{{Necessaryprerequisitetoundestandingthisdocument}}
* the translation includes the original German text, if available, which must be exact to the character.
* the line numbering should also be included in the article if it existed in the original text and if available.
* you include the translator's name, if available, at the top of each page
* you include references at the bottom of the page using the &lt;ref&gt;...&lt;/ref%gt; tag within the body of the text and &lt;references /&gt; tag at the bottom.
* you include the source (URL or book title and ISBN) of the article

Once an article is submitted, a Wiki admin will check and verify and improve the article for presentation quality purposes only, not translation quality.

'''Note: Vandalism will not be tolerated. IP addresses of offending users will be blocked permanently. It is also pointless since any changes petty or otherwise can easily be rolled back.'''

If in doubt or need help email the owner of the website: [[Main Page#Webmaster Contact Details]], who can also put you in contact with other helpers too.

We are ''generally'' following the https://en.wikipedia.org/wiki/Wikipedia:List_of_policies_and_guidelines#List and the [[FIGU]] policies and agreements as well as a variety of internal rules and policies which are website specific, all have built over time.

Please ensure that content either originates from FIGU, or is relevant to FIGU, see [https://en.m.wikipedia.org/wiki/False_memory False memory (Wikipedia)].

== Editing Tips ==

# The easiest way to create a new page is to create a link to a new page then click on that link<ref>Make sure that the link does not contain quotation marks, because otherwise you will run into problems.</ref>.
# You can now use [http://www.futureofmankind.co.uk/w/convertgaiaguys.php the new gaiaguys-article-to-Wiki-table convertor] - it is not perfect but helps save some editing time. It is useful for creating a MediaWiki table from a combined German-English translation whereby the lines are alternatively in English, German, English, German.
# There is now also [http://www.futureofmankind.co.uk/w/convertben.php another tool for merging separate German and English articles into the same Contact Report].
# Similar to the above two converter examples. Libreoffice calc (similar to MS excel) has an extension which allows incredibly large quantities of data to be saved incredibly equitably as text with the cells converted to mediawiki table format; which means one might place a great quantity of English in row 1 and German in row 2 and the script which saves the file will add the wiki markup for a table keeping all lines separate and just as a contact report is presented but automatically and then in libreoffice writer the ctrl+h find and replace function has a feature called regular expression, you can find a list of them online, this can then be used to tidy up the document, again semi-automatically, and because mediawiki does the presenting part for you it can all be in text files and in bytes, which means even a very slow computer can handle very large quantities of data providing its first copied from a PDF on a fast computer.
# Unfortunately there is not many ways around the translation problem where a website has to be used for small quantities at a time. There are a few software script chaining methods available, some pretty good allowing the database from dict.figu.org to be entered in, but/however because of the fine quality and specificity of the information, every line would have to be checked manually anyway, having said all that, by combining these various processes together we could theoretically find a way of populating the website in a much less laborious fashion, it would just take a great deal of calibration work to begin with, and after to be fair. If a translation is not good it is not worth reading and therefore not worth bothering to do, so you see now why this process has been taking such a long time despite all these technologies, we’ve been deliberately going this slowly.

== Racist and religious hate crime ==
(and any other breach in the law for that matter)<br>
Future Of Mankind hosts English translation documents of FIGU publications. There are thousands of documents and they cover a very broad subject base, including the subjects of race and religion. We havn’t necessarily checked meticulously all the contents of all the text which has been submitted to the website, because they’re very large documents and as the website is meant to be a repository of FIGU documents, they’re unconditionally accepted if they originate from FIGU - because FIGU has been deemed a responsible publisher for decades.

If you see anything on the website that borders being considered racist or religiously hateful and/or in anyway eligible as hate crime language, or for that matter any sort of crime, then please bring this text to the attention of the website owner, who’s contact details are on the main page. The website will bring it to the attention of the originating source FIGU, including any other website on [[External Links]] which hosts the document and remove it from the website without hesitation if it is in breach of any criminal law. The website is all about the truth, but there are ways in which some things cannot and should not ever be said, and in some nations it is against the law to word something a certain way, might seem harmless but we could get in trouble for it. The website has no interest in hosting anything that breaks the law. FIGU knows all this and is responsible. The website is based in UK and has to abide by UK law and social etiquette. Switzerland is similar to UK and there are readers all over the world - so we have always assumed there would never be a problem, but it would be removed if there ever were.

== Contact Report Layout Template ==
'''Quick introduction guide:'''

There is also something on [[A Note to Editors]] page.

At the top of a contact report page is some information. Copy and paste it into a new page.
:First line sets the category for the page. It makes it listed on a category page like this one [[:Category:Prophecies and Predictions]] or this one [[:Category:Spirit Teaching]] and well of course in this case it will place it here [[:Category:Contact Reports]]. Every page has to have a category assigned to it, please.
:Second line ('''Change this line''') shows what translation type it is, see above section about translation label types.
:Third line is simply a presentation spacer
:Fourth line displays the table of contents at that position.
:Fifth line another line space.
<pre>[[Category:Contact Reports]]
{{Officialauthorised}}
<br>
__TOC__
<br></pre>
Then follows an introduction block with all kinds of data.
Result:
<pre>
==Introduction==
</pre>
<div style="float:left"><small>
* Contact Reports Volume / Issue: 1 (Plejadisch-Plejarische Kontaktberichte Block 1)
: pp. 27-30  <small>[Contact No. [[The_Pleiadian/Plejaren_Contact_Reports#Contact_Reports_1_to_400|1 – 38]] from 28.1.1975 to 13.11.1975] [[Contact_Statistics#Book_Statistics|Stats]] | [http://shop.figu.org/bücher/plejadisch-plejarische-kontaktberichte-block-1 Source]</small>
* Contact Reports Band / Block: 1 (Semjase-Bericht Gespräch Erlebnisse Block 1)
: pp. tbc-tbc  <small>[Contact No. [[The_Pleiadian/Plejaren_Contact_Reports#Contact_Reports_1_to_400|1 – 23]] from 28.1.1975 to date] [[Contact_Statistics#Book_Statistics|Stats]] | [https://shop.figu.org/bücher/semjase-bericht-band-1 Source]</small>
* Date/time of contact: Tuesday, 28<sup>th</sup> January, 1975 – 14:34 (Erster Kontakt)
* Translator(s): Unknown <span class="mw-customtoggle-translshow">[show info]</span>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-translshow">
: <small>Date of original translation: Unknown</small>
: <small>Corrections and improvements made: N/A</small>
</div>
* Contact person(s): [[Semjase]]
</small>
</div>
<div align="right"><div><ul><li style="display: inline-block;">
[[File:PLJARISCHE_BLK_1.jpg|frameless|130px|right|alt=Plejadisch-Plejarische Kontaktberichte]]</li><li style="display: inline-block;">[[File:SEMJASE_BLCK_1.jpg|frameless|130px|right|alt=Semjase-Bericht]]</li></ul></div>
</div>
<br clear="all" />
It look complicated because it's lots of necessary information condensed into a small space. It's relatively self explanatory, and after making a few of them a process emerges. It's condensed into a small space because most readers don't care about it, but it is necessary information about origination.<br>
:Some of the contact reports have images like this one and others have links to an image URL on the actual FIGU website. These links have to be changed to internal FOM image links like the one above because they are gradually being changed on the FIGU.org website, and in a few years we may end up with hundreds of deadlinks.
:In many case the information numbers and values can simply be changed without having to check if everything is linked properly as it's sequentially sourced in sequence.
:(Erster Kontakt) represents the original German word value given to the contact in the actual book and is very useful for using the find function on the book.
:The data can be found in the German books which are either in the [[Downloads]] section or upload log.
:If there has been a translator please include the information given at source, this helps other translators.
<pre>
==Introduction==
<div style="float:left"><small>
* Contact Reports Volume / Issue: 1 (Plejadisch-Plejarische Kontaktberichte Block 1)
: pp. 27-30  <small>[Contact No. [[The_Pleiadian/Plejaren_Contact_Reports#Contact_Reports_1_to_400|1 – 38]] from 28.1.1975 to 13.11.1975] [[Contact_Statistics#Book_Statistics|Stats]] | [http://shop.figu.org/bücher/plejadisch-plejarische-kontaktberichte-block-1 Source]</small>
* Contact Reports Band / Block: 1 (Semjase-Bericht Gespräch Erlebnisse Block 1)
: pp. tbc-tbc  <small>[Contact No. [[The_Pleiadian/Plejaren_Contact_Reports#Contact_Reports_1_to_400|1 – 23]] from 28.1.1975 to date] [[Contact_Statistics#Book_Statistics|Stats]] | [https://shop.figu.org/bücher/semjase-bericht-band-1 Source]</small>
* Date/time of contact: Tuesday, 28<sup>th</sup> January, 1975 – 14:34 (Erster Kontakt)
* Translator(s): Unknown <span class="mw-customtoggle-translshow">[show info]</span>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-translshow">
: <small>Date of original translation: Unknown</small>
: <small>Corrections and improvements made: N/A</small>
</div>
* Contact person(s): [[Semjase]]
</small>
</div>
<div align="right"><div><ul><li style="display: inline-block;">
[[File:PLJARISCHE_BLK_1.jpg|frameless|130px|right|alt=Plejadisch-Plejarische Kontaktberichte]]</li><li style="display: inline-block;">[[File:SEMJASE_BLCK_1.jpg|frameless|130px|right|alt=Semjase-Bericht]]</li></ul></div>
</div>
<br clear="all" />
</pre>

Then comes the synopsis. You can write your own synopsis. Some have bullet points which is achieved by adding a * before the line. Or they tend to be three or four pertinent points of interest, worked into a short paragraph, or both a short paragraph and a couple/few bullet points.
<pre>
=== Synopsis ===
</pre>
Followed by a space and then a short what it is.

'''This is an excerpt of the contact.'''

:The variations are 'full' (if the German side is complete or English side or both sides), 'preliminary' (if its an amateur translation which has not been thoroughly checked yet), 'extract' (for a very short section), 'excerpt' if its a longer but not complete, or 'partial'. They can also be combined if its preliminary and an excerpt.

:Some may also include a reiteration of the information at the top of the page. This is not necessary because of the information at the top of the page, like this.

'''This is a partial and preliminary translation of the contact. It is an unauthorised and unofficial translation and may contain errors.'''

Then the contact report begins
<pre>
== Contact Report 000 Translation ==
{|
|+
|-
| style="width:50%; background:LightSkyBlue; color:Black" | English || style="width:50%; background:LightSkyBlue; color:Black" | German 
|-
| '''Excerpt from the 000th official Contact report conversation of Wednesday the 1st of January 2018'''
| '''Auszug aus dem 000. offiziellen Gesprächsbericht vom Mittwoch, den 1. Januar 2018'''
|-
| '''Billy:'''
| '''Billy:'''
|-
| I'm English text and on the left
| I'm German text and on the right
|-
|}
<br>
</pre>
Result:
<pre>
== Contact Report 000 Translation ==
</pre>
{|
|+
|-
| style="width:50%; background:LightSkyBlue; color:Black" | English || style="width:50%; background:LightSkyBlue; color:Black" | German 
|-
| '''Excerpt from the 000th official Contact report conversation of Wednesday the 1st of January 2018'''
| '''Auszug aus dem 000. offiziellen Gesprächsbericht vom Mittwoch, den 1. Januar 2018'''
|-
| '''Billy:'''
| '''Billy:'''
|-
| I'm English text and on the left
| I'm German text and on the right
|-
| I'm a new line aligned with the other side in English text and on the left
| I'm a new line aligned with the other side in German text and on the right
|-
|}
<br>

<pre>
==Further reading==
</pre>
Add links to pages which are relevant to what was talked about in the contact here, so that readers can just click away and move onto a new page without having to type anything or do anything.

* Whatever the next contact report is in the sequence
* [[Planets]]
* [[Semjase]]
* [[Atlantis]]
* [[MIB]] 

etc.,

Then theres the source and references section, and in some cases the copyright section which can be added now and again if say its the first contact in a new contact report book, see [[Contact Report 001]] to see how copyright section is done. And there is sometimes a translators note included here too, it was traditionally placed at the top of the contact but slowly these notes are being moved to the bottom because they are in some cases too long to introduce the contact. They are often very useful notes because as the translator translates he/she makes various observations, often deep observations which the reader probably won't notice and may help them quickly assess what was what. At any rate these notes correct position is after the experience not before, giving the reader the opportunity to make their own judgment. Included in between the source and references section if the case.
<pre>
==Source==
<br>
==References==
<references />
<br>
</pre>
Which you add the source where it was found, or if it was sent to you by email from a translator, or another website such as au.figu.org or ca.figu.org etc., and the URL

The references section is where everything tagged with a ref tag ends up. The reference tags are in the body of the text and are used to clarify words a show links to external material and various other uses.
<pre>
<ref>I am a reference to this German word at dict.figu.org full URL</ref>
</pre>



Check out a few of the contact reports in edit view before weighing up how these various things are being done.

There is some democracy going on with how things are done on individual pages,

=== Reference Templates ===
Instead of explaining on every page that German words are in the English translation because there are not suitable English synonyms for that word, you can use a template.

ausartung{{Ref:ausartung}}
gemüt{{Ref:gemüt}}
gewalt{{Ref:gewalt}}
wesen{{Ref:wesen}}

It creates a reference at the bottom of the page. The code looks like this, it can be just entered as is into the body of the text.
<pre>
ausartung{{Ref:ausartung}}
gemüt{{Ref:gemüt}}
gewalt{{Ref:gewalt}}
wesen{{Ref:wesen}}
</pre>
In many ways we would prefer folks to use these templates for references because it makes it easier to edit a reference site-wide if it needs refining.

The next question is how to edit or create a new template - well look at the mediawiki documentation before creating, and look at the templates we have on the wiki to see how it is by selecting [[:Special:AllPages]] or the ''Site Index'' link in the navigation, then select ''templates'' from the drop down box list, which should list all the templates on the wiki. Templates are basically just normal pages, but are of course called upon by using the brackets. This is how we place the advice box about translation at the top of each contact report, they are essentially externally called upon pages - templates.

You are welcome to go to dict.figu.org, select words that occur a lot and become tedious to include references and create a template which creates a reference for that word [as above] and put it into the contact reports where appropriate, if you would like to.

=== Newspaper Clippings ===
In the printed books there are quite often clippings/cuttings from newspapers, which includes a caption followed by a publisher and date. This can be included in a contact report if you want to.

There have been 3 templates made to help deal with newspaper clippings included in the original contact report books.
:[[:Template:PPKBnewsclip]] - Includes a centered label explaining it's from a newspaper and included in the book.
:[[:Template:PPKBnewsclipb]] - No center label - for chaining multiple articles, as seen in book.
:[[:Template:PPKBnewsclipc]] - An image of the newspaper clipping itself instead, if want to upload.

We can make templates for a whole raft of different purposes if it speeds up the process and makes it easier for us to skip repetitive tasks.
----
'''How to use them'''
----
Use the trunking divider | to separate arguments.

Like this 
<pre>
{{PPKBnewsclip|1=English language newspaper article title|2=Date it was published in English|3=German language newspaper article title|4=Date it was published in German}}</pre>

1= will display text in the title area on the english side

2= will display text in the date area on the english side

3= will display text in the title area on the german side

4= will display text in the date area on the german side

5= (For Template:PPKBnewsclipc only) will display the image put in there.<br>
<small>
''Images''<br>
Please try to keep the image uploads, including naming, how they are named, consistent if you're uploading many of them from the printed books. Name them in a sequence with a reference e.g. PPKB_newsclip_001_CR004_1987.jpg - as an example, you choose. For a printed newspaper article we've found that about 850px width or so (with whatever proportional height that makes it) is best, with about a 70% jpeg compression, but a 30% compression may be ok if the text remains clearly readable, use the jpg. file format for images, please compress them so readers can see it without having to use lots of data. You may also put the text from the article itself inside the description, so it can be copied and pasted.</small>


Use the trunking divider | to separate arguments.

The order doesn't particularly matter providing the number is followed by an equals sign 

E.g.
<pre>
{{PPKBnewsclip|2=Date it was published in English|3=German language newspaper article title|1=English language newspaper article title|4=Date it was published in German}}</pre>
{{PPKBnewsclip|2=Date it was published in English|3=German language newspaper article title|1=English language newspaper article title|4=Date it was published in German}}
But it's probably best to do it 1 2 3 4 5 so as not to confuse everyone.
----
<big>
: 1: About [[:Template:PPKBnewsclip]]</big>

Newsclip is with the centre text explaining it's from a newspaper clipping in the printed book.
<pre>
{{PPKBnewsclip|1=English language newspaper article title|2=Date it was published in English|3=German language newspaper article title|4=Date it was published in German}}</pre>
Result:
{{PPKBnewsclip|1=English language newspaper article title|2=Date it was published in English|3=German language newspaper article title|4=Date it was published in German}}

----
<big>
: 2: About [[:Template:PPKBnewsclipb]]</big>

Newsclipb is without the centre text for chaining newspaper clippings.
<pre>
{{PPKBnewsclipb|1=English language newspaper article title|2=Date it was published in English|3=German language newspaper article title|4=Date it was published in German}}</pre>
Result:
{{PPKBnewsclipb|1=English language newspaper article title|2=Date it was published in English|3=German language newspaper article title|4=Date it was published in German}}

----
<big>
: 3: About [[:Template:PPKBnewsclipc]]</big>

Newsclipc is with centre image for newspaper clippings instead. The first line of the image description displays the name of the page itself - which should be Contact Report number.
<pre>
{{PPKBnewsclipc|1=English language newspaper article title|2=Date it was published in English|3=German language newspaper article title|4=Date it was published in German|5=File:A guessing game lasting 23 years came to an end.jpg}}</pre>
Result:
{{PPKBnewsclipc|1=English language newspaper article title|2=Date it was published in English|3=German language newspaper article title|4=Date it was published in German|5=File:A guessing game lasting 23 years came to an end.jpg}}

'''Code quick'''<br>
To slice the contact report open, slip it in and shut, cut and shut - copy and paste this in - use the |} to close the table then use the br space divider then insert the template then open the table back up again with a 100% width and 50% designation with another | divider; followed by the continued conversation text.

Like this, copy and paste it:
<pre>
|}
<br>
{{PPKBnewsclip|1=English Title|2=English Date|3=German Title|4=German Date}}
{| style="width: 100%;"
|+
|-
| style="width:50%;" | English contact report conversation continued
| style="width:50%;" | German contact report conversation continued
</pre>

If you're chaining them i.e. putting many one after another; if there are two put the {{PPKBnewsclip| first followed by the {{PPKBnewsclip'''b'''| - if there are more than 2 in succession put the {{PPKBnewsclip| in the second position. Adding a '''b''' removes the text in the middle.

When you're copying and pasting the lines in, it goes '''1 3 2 4''' because that is how they're translated first - copy the English Title into position, then the German Title into position then the English Date, and finally the German Date.

For more help see https://www.mediawiki.org/wiki/Help:Templates<br>
One example of this in practice and as the final result is in [[Contact Report 230]] ''newspaper clippings through out'', and another example is in [[Contact Report 003]] ''newspaper clipping image at the bottom''.

=== Condensed navigation listing ===
When using a touch-screen device such as an iPad, the sidebar disappears to fit more onto the screen -which is good. However it's sometimes tricky to scroll the drop down menu to find the link the reader wants. 

A template has been created which can be added to any ''Further Reading'' section of any page after the relevant links for that page; displaying a condensed navigation listing.

Just add:
<pre>
{{LINKNAVS}}
</pre>
Result:<br>
{{LINKNAVS}}
----
It's here if you need to edit it; any edit is site wide change:
: [[:Template:LINKNAVS]]

=== Copyright ===
To be used conservatively, because readers know after seeing it a few times. Use on the first contact report of a block, see [[Contact Statistics]] scroll down to book statistics to know which contact reports are first in a PPKB block.

The way to use it is after the source section at the bottom of the page (not near the top, not in the middle etc.), as a subheading to the source section. [[Contact Report 001]] and [[Contact Report 230]] have presentation examples.

Like this:
<pre>
==Source==
* ['example source URL' space 'name']
<br>
=== Impressum / Copyright / Disclaimer ===
{{Copyright}}
</pre>

Using the template results in this:<br>
{{Copyright}}

There are however copyright information(s) for specific documents, those should be included for the specific documents, above the template, like this:<br>
<pre>
=== Impressum / Copyright / Disclaimer ===
All extra document specific information here. Document, publication, book, specific information here, what is necessary and identifies the specific book, ['example source URL' space 'name'] etc.
{{Copyright}}
</pre>
As always, by using a template it allows us to manage the information across the whole website at one time. If for whatever reason you need to amend the copyright template, it's here:<br>
[[:Template:Copyright]]

=== Letters / Special box ===
Occasionally a letter i.e. a written, typed, or printed communication, sent in an envelope by post or messenger, by someone else - is included in the printed book. A presentation example is in [[Contact Report 230]], CTRL+F / Find "by Silvano Lehmann". You can use this to present such letters if you would like to include them in the translation.

=== Pleasant spacing ===
Doing the name tag for the person speaking like this:
<pre>
| <br>'''Billy:'''
| <br>'''Billy:'''
|- style="vertical-align:top;"
</pre>
Adds a welcomed space between the last person talking and this, and aligns the talk of the next person to the top which looks nicer. Aligning to the top is also useful on any paragraph if the German text is longer than the English or vice versa. There is an example in [[Contact Report 002]].

=== Linking ===
The link is the word after the forward slash / after Billy_Meier/ 
<pre>
http://www.futureofmankind.co.uk/Billy_Meier/FIGU_Bulletin_008
</pre>
So the link is the FIGU_Bulletin_008 part. It can have the underscores taken out like this, and put into brackets.
<pre>
[[FIGU Bulletin 008]]
</pre>
Result is [[FIGU Bulletin 008]], which can now be clicked on.

You can also change what is written to that link like this

<pre>
[[FIGU Bulletin 008|Bulletin by FIGU, number eight]]
</pre>
Which then looks like this [[FIGU Bulletin 008|Bulletin by FIGU, number eight]] but links to that page.

Some links need to have a colon in for them to work. This is rare but incase you needed to know, it's needed for things like linking to a category instead of making the page that category, or linking to an image instead of the image being shown.
<pre>
[[:File:UFO_India.jpg]]
</pre>
Result:<br>
[[:File:UFO_India.jpg]]<br>
without the colon it would do this, and show it:<br>
[[File:UFO_India.jpg|100px|left]]
<br clear="all" />
=== Quick sequence access ===
All Contact Reports, Special Bulletins, Bulletins have URLs and link methods which are similar across the database. Just change the number at the end.<br>
'''Internal Links''' Just change number at end.
<pre>
[[Contact Report 001]]
[[Contact Report 256]]
[[Contact Report 512]]
</pre>

'''URL Links''' Just change number at end.
<pre>
http://www.futureofmankind.co.uk/Billy_Meier/FIGU_Bulletin_008
http://www.futureofmankind.co.uk/Billy_Meier/FIGU_Bulletin_016
http://www.futureofmankind.co.uk/Billy_Meier/FIGU_Bulletin_027
</pre>
Etc.

=== Redirects ===
Create a new page with;
<pre>
#REDIRECT [[Atlantis]]
</pre>
Save it, and it should now redirect the reader to the page within the brackets. If it doesn’t work it may be an invalid link.

----

Another way is to add an anchor into the body of the text so that the redirect goes to the correct position on the page, which we have been doing for the [[Index]] for some of the longer indexes. But this is not to be done by persons who are newer to the information because it should be done only for rare topic instances and one off subjects. Instead for broader subjects it is better to create a new [[Meier Encyclopedia]] page, assuming a page is not already suitable, usually instead just adding info to an existing page. We have to be careful not to have duplicate pages for the same information, so be careful to check the allpages special page to see what exists already.

=== TOC Headings ===
Table of contents headings links are useful, not so trivial after all and they carve up the page too. Putting two or more == equals signs either end of the heading makes it a heading. The more equals signs there are the deeper and less significant the sub heading max 6 levels, e.g.
<pre>
==Lethargic Perspectives==
===In the time its taken a Plejaren===
====to live and to die====
=====the Earth human globalised an entire world=====
==Second Title header==
===Subsection===
</pre>
Etc., So you get the idea. These will now show because of the inclusion of equals signs, at the start of a sentence, in the TOC and also it’s important that they’re neat and simple because they can also now be linked to from other pages. It’s important to know that because if you change a heading all the links which have been connected to it now will just stop at the top of the page or be redirected to where in the page it used to be, depending on how it’s been setup. Use the [[Test]] page to see that if you really need to. You can also edit a header TOC independently of the rest of the page while signed in and clicking the edit button. Which makes editing quicker.


----
The same principles apply to any Meier Encyclopedia page and any pages. See the other pages in the category for how to solve presentation challenges.

=== Dictionary definition box ===
{| class="wikitable" style="float:right; margin-left: 20px;"
|-
| <small>''Cambridge Dictionary; British English: '''Recommendation'''</small><br>
:<small><small>a '''suggestion''' that something is '''good''' or '''suitable''' for a particular purpose or job.</small></small>
:<small><small>'''advice''' telling someone what the '''best''' thing to do is.</small></small>
:<small><small>the person or thing that has been '''suggested''' as the '''best choice'''.</small></small>
|}
On some pages, rarely, the inclusion of a dictionary definition, from a regular over the counter dictionary, may be appropriate. Usually it is appropriate because we have learnt somehow or another that a most general misunderstanding is occuring.

''Any'' dictionary can be used, actually we prefer using the better known dictionaries, but you can use other dictionaries from say Europe, North America, Oceania - even dictionaries from other languages e.g Swiss dictionary, Japan dictionary. Using dictionaries from other languages, sort of reinforces the fact that the general definition is pretty well univeral, it is fortifying and we like demonstrating that we are dealing with information normally. However it is only acceptable providing there is a high quality translation in English included of course and the dictionary name is followed by the language/English. Default is use of the Cambridge or Oxford dictionary.

There are three lines included in this box, which sort of says the same thing but three ways. The definition should be shortened to its simplistic components and made reader friendly for a quick easy glance, this may mean taking words out and putting words in to simplify, and require some light research into how best to present it. Bold the key words is good for a quick look of the reader.

To do this include the code below before the text; change of course the information.
<br clear=all>
<pre>
{| class="wikitable" style="float:right; margin-left: 20px;"
|-
| <small>''Cambridge Dictionary; British English: '''Recommendation'''</small><br>
:<small><small>a '''suggestion''' that something is '''good''' or '''suitable''' for a particular purpose or job.</small></small>
:<small><small>'''advice''' telling someone what the '''best''' thing to do is.</small></small>
:<small><small>the person or thing that has been '''suggested''' as the '''best choice'''.</small></small>
|}
</pre>


An example is on [[The Twelve Recommendations]] page.

=== Manual:Purge Clear page cache ===

You shouldn't usually need to do this. If you make a substantial change to a page where you add new headers and subheaders (btw don’t change headers without checking first what links to them using the tool 'what links here') and add a lot of new text and make the arrangement and layout better somehow, this applies to any page, it might not link correctly from other pages and link the reader to what appears like a random part of the page, it seems that way but it is where the text used to be before you edited it. 

Then in that case the page cache needs to be purged to reset the page to revert to its original scripts, new layout.

Add this text to the end of the URL and press enter.
<pre>
?action=purge
</pre>
Pressing enter should take you to a confirmation screen, the confirmation screen is only there so that search engine spiders dont trigger it. You can press the confirmation button. Now when you try the links that linked to a random part of the page, instead now they should link to the header where you have placed it.

== Extraneous consistency translator notes ==
<small>Use this area to list off special consistencies that a translator is likely to encounter with the original German presentation and wonder what to do about it.</small>
----
Include the numbers on each line if they can be found elsewhere on an original text.<br>

We don't insert translator notes in the body of the text outside a reference tag. There are however special times when we do annotate the English translation in the body of the text i.e. adding extra words which are not in the original, these occasions are listed below and are relatively rare but when needed for a reader do make sense.<br>

<pre><ref>Translator note: The word was chosen because it holds a meaning for something etc.</ref></pre>

Reference tags come after punctuation.<ref>illustration</ref> - not before<ref>illustration</ref>.<br>

If it's CAPITALISED i.e. all caps, in the Swiss German text, capitalise it in the English translation, but don't if not.<br>

If it's ‹enclosed› or «enclosed» or <<enclosed>> in these types of symbols in the Swiss German text, the options are "quotation marks" or a link to a [[Meier Encyclopedia]] page or other applicable page, if available.

<pre>[[Spirit]]</pre>

Include the original glyphs e.g. Präsidenten, März, «Totale Vernichtung der Aufständischen.» and special characters in the Swiss German text and transfer them over to the translation where possible.<br>

There are several specially invented words in the texts which have a corresponding invented word to be aware of. See dict.figu.org and translator notes from those who have come before you on various different texts.<br>

There are words which have to be used the same way as before despite the words being reviewed/judged as being better translated another way e.g. Pleiades. Take a look at how they've been translated on other contact reports.<br>

Date format is DD/MM/YYYY Day then month then year. Long format if it's written that way in German e.g. "On the 23rd of February in 1976, I went to the town." etc. There are however rare occasions in the original text which defy the law to be aware of, where it's been worded by the speaker as month followed by day, it depends on that sequencing if it's part of a delivered sentence, to maintain the vibe of the original spoken delivery.<br>

Long count numbers: Milliarden in German is a thousand million in English, see [[Billion]].<br>

British-English is used on the Future Of Mankind website over American-English.<br>

Don't bold a word in the body of the text. We '''bold''' the person speaking e.g. '''Billy:'''.<br>

You are not allowed to emphasise a word outside the way we have been doing it.<br>

Speaker must be on a different line to what they have said.<br>

'''Ptaah:'''<br>
That is right,<br>

We don't write '''Billy says:''', or '''Semjase says:''' etc.<br>

Brackets in the Swiss German text should be included in the English translation e.g zwei (2), two (2).<br>

Don't bracket an alternative word choice e.g. Spirit (Ghost). See dict.figu.org and translator notes from those who have come before you and navigated the translation process before you, from their various different translations.<br>

If units of measurements are included e.g 500 metres, it is acceptable to create a reference tag containing the equivalent in other units of measurement for the benefit of international readers, e.g kg to lbs, m to ft, km to miles and yards etc.<br>

Where an exotic word, new word, is used which features in no dictionary or doesn't translate to English, then consult dict.figu.org, see if the word has already been translated in another contact report or other text. We try to use the same words as consistently as possible so as not to confuse readers.<br>

A translator notes section may be added after the translation not before, some older translations still have them presented before but this is not the right way to introduce. You may add a section at the end before the further reading section, like this.
<pre>==Translator Notes==</pre>
Then list your notes with or present them as a paragraph that is up to you. Please keep the notes a reasonable length, longer if necessary but not if unnecessary. The reference section will then include references from in the body of the text. You can link to outside source there, [[Contact Report 544]] has an example.<br>

Avoid too many he/she's. If it's ok to write they, them, we, individual, person, folk etc., if it's contextually appropriate then do that instead. It's not always pleasant to read too many 'he/she' commentaries.<br>

Don't use words more than is necessary, we aim for diversity and keeping the reader as refreshed as possible where the original allows, e.g Creation, more than is necessary, if the translation allows a different word or word-combination etc., then try that. We don't want to bore the reader and we want the reader to continue reading, so if it's possible in the original text to use a better more so delightful arrangement of words in the translation which differs from the way it was said the last time it was said which corresponds more to how they are communicating rather than how the autotranslator is saying it should be, then go for that option. There are several ways of saying the same thing, it's often reinforcing of an explanation to use those different ways. The best translators are carefully selecting a presentation way which keeps it flowing like a real conversation; it was a real conversation.<br> 

Autotranslator softwares strip out much of the soul, rhythm, emotion, flow etc., of the text.<br>

There is all sorts of other things which can be checked by looking at other completed translations to see how it has been done before.

== Translation Tools ==

If you want to translate some German text for '''personal use''', it is advisable to use the online translators provided by Google and Altavista which are some of the best ones available.

* [https://www.deepl.com/translator DeepL Translator]

* [http://www.google.com/translate_t Google Translator]

* Bing Translate

* [http://world.altavista.com/ Altavista Translator] - {Broken link 16aug18}

== Other Tools ==

There is a tool menu at the bottom of the links on the left bar when your signed in.

The [[FIGU News]] I suppose you could call a 'tool', it's linked to an RSS feed of selected sites. And [[Site News]] is a 'tool'. [[:Special:AllPages]] is probably a tool too.

Tools for translators.
* http://www.futureofmankind.co.uk/w/convertgaiaguys.php - created to deal with line after line translations
* http://www.futureofmankind.co.uk/w/convertben.php - created to deal with english and german separately

Here are some other tools provided by Google.

:[https://www.google.com/search?q=%22figu.org%22+-site:figu.org%22+-site:theyflyblog.com%22+-site:futureofmankind.co.uk&tbs=qdr:w View what people said about www.figu.org last week (Google search)]
:[https://www.google.com/search?q=%22futureofmankind.co.uk%22+-site:futureofmankind.co.uk&tbs=qdr:d View what people said about www.futureofmankind.co.uk in the last 24 hours (Google search)]
:[https://www.google.com/search?q=%22futureofmankind.co.uk%22+-site:futureofmankind.co.uk&tbs=qdr:w View what people said about www.futureofmankind.co.uk last week (Google search)]
:[https://www.google.com/search?q=%22futureofmankind.co.uk%22+-site:futureofmankind.co.uk&tbs=qdr:m View what people said about www.futureofmankind.co.uk last month (Google search)]
:[https://www.google.com/search?q=%22futureofmankind.co.uk%22+-site:futureofmankind.co.uk&tbs=qdr:y View what people said about www.futureofmankind.co.uk last year (Google search)]
:[https://www.google.com/search?q=site%3Afutureofmankind.co.uk View how many www.futureofmankind.co.uk links are indexed by Google (Google search)]

:[https://www.google.com/search?q=%22Billy%20Meier%22+-site:figu.org%22+-site:theyflyblog.com%22+-TheyFly%22+-site:futureofmankind.co.uk&tbs=qdr:d View what the world said about ‘the Billy Meier case’ in the last 24 hours (Google search)]
:[https://www.google.com/search?q=%22Billy%20Meier%22+-site:figu.org%22+-site:theyflyblog.com%22+-site:futureofmankind.co.uk&tbs=qdr:m View what the world said about ‘the Billy Meier case’ last month (Google search)]
:[https://www.google.com/search?q=%22Plejaren%22+-site:figu.org%22+-site:theyflyblog.com%22+-site:futureofmankind.co.uk&tbs=qdr:m View what people said about ‘Plejaren’ last month (Google search)]
:[https://www.google.com/search?q=%22Semjase%22+-site:figu.org%22+-site:theyflyblog.com%22+-site:futureofmankind.co.uk&tbs=qdr:m View what people said about ‘Semjase’ last month (Google search)]
:[https://www.google.com/search?q=%22Beamship%22+-site:figu.org%22+-site:theyflyblog.com%22+-site:futureofmankind.co.uk&tbs=qdr:m View what people said about ‘Beamship’ last month (Google search)]

=== New recently added content ===
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2; -webkit-column-rule: 14px solid white; -moz-column-rule: 14px solid white; column-rule: 14px solid white;">
<small><div style="font-size:96%; line-height: 1.2;">'''New pages:'''<br><small>see [[:Special:Newpages]]</small><br>{{Special:Newpages/4}} '''New files:'''<br><small>see [[:Special:Newfiles]]</small><br>{{Special:Newfiles/2}}</div></small>
</div>

== MediaWiki Resources ==

This Wiki uses the MediaWiki server software as used by [http://www.wikipedia.org Wikipedia.org]. It is advised that you refer to the [http://meta.wikimedia.org/wiki/Help:Contents MediaWiki Handbook] for assistance when unsure of how to implement a required change.

* [http://meta.wikimedia.org/wiki/Help:Contents MediaWiki Handbook]
* [http://www.mediawiki.org/wiki/Help:FAQ MediaWiki FAQ]

Note that [http://www.wikipedia.org Wikipedia.org] ''itself'' help pages, may contain help specifically for wikipedia itself e.g. contain templates and use of extentions etc., that Future Of Mankind doesn't have and won't ever have. When using your search engine, search "Mediawiki" followed by the question e.g. "Mediawiki tables", or "Mediawiki images" etc., to get help about mediawiki itself, then it's guaranteed to be relevant to the Future of Mankind website. Having said all that, wikipedia itself does have some very helpful thorough pages which could theoretically be helpful too, - they're both fundamentally using the same technology anyway.

==List of things you could help with==
[[File:Forestrycommision england rendlesham suffolk UFO trail.jpeg|thumb|right|<small>The so-called “UFO trail”, Rendlesham Forest, Suffolk, England</small>]]
This isn't all of the ways; its suggestions from other editors. There is plenty here on the website which reasonable, responsible individuals can help with by improving selflessly for the benefit of other readers.

* Proof read the German and correct any mistakes (if you have the original documents and from the original documents only). Email FIGU if you spot a big mistake in the original documents, dont email FIGU if its an error only on this website and not in the original documents, change a mistake if its wrong on this website compared to the original documents.
: Proof read the English and correct any mistakes. (proper, thorough, complete, grammar, spelling, punctuation, british english spelling, long scale -see [[Billion]], formatting/presentation errors/mistakes/improvements etc.)<br><small>However if the contact is marked as authorised and approved, only very minor corrections can be made to the English only, in this case the website and FIGU should be contacted, but for a contact to be authorised and approved it goes through a reading, checking process so should be very rare. Sometimes something that looks like an error is not, should be careful with official authorised approved because it has been checked by FIGU. You can change American English spellings to British English spellings and some small corrections. Futureofmankind doesn't operate a so called sacred scripture or revered texts, type of policy, we operate a responsible, reasonable, self reasoning and intelligence policy, if something is clearly not right, you are encouraged to research why it's that way, track down the original German and original translation etc., peruse the guidance dict.figu.org and the other pages on the website including the history of previous revisions tab of the page to see how it was done before by others, and to correct it if necessary, within the prudence, circumspection and discretion that we have built. A note can be written into the summary: of the revision and the minor edit button can be highlighted. Explain briefly in the summary box the reasoning behind an edit if it's an abnormal change for a special reason e.g. based on research or if the German word meaning is different etc., be responsible, thank you.</small>
: Compare the English with the German sentence by sentence to make it a better more professional translation; if it doesn't make sense or could be better, if you speak, read and write German and English. Compare word choices with dict.figu.org if you would like to.
: If you have one of the books; input word for word onto the German side of a contact report or document which hasn't been translated yet so that others can translate. We can host German only content, until sometime later, it makes it easier for translators to work on it later.
: If there is no English only German text; you're welcome to translate the German into English if you can do that to a good and reasonable standard, providing the page has the correct header unofficial/unauthorized.
* Spelling and grammar mistakes generally (but the German has to be exactly the same as the original)
: page formatting mistakes, and improved layout of information, functionality and aesthetically.
* Add references (citations and references are the same on this website) to German words included in the English from dict.figu.org so readers know why an English word has not been used, because English doesn't have an appropriate word for it.
: Further reading sections can be expanded with useful relevant information urls from inside the website followed by from wikipedia and other carefully selected websites, regarding specifics written in the contact report - especially if the reader is likely to go looking for it afterwards anyway. Always only the best, clean and direct links, no redirects, no adverts or annoying things, discriminate in favour of long serving websites and FIGU websites.
* Move subject based information to the [[Meier Encyclopedia]].
: If there is already a page for it in the [[Meier Encyclopedia]] don't create another page, instead make the existing page better. You can add a new header to a page which contains an extracts/excerpts if you are able to reference where it came from and of course if it is relevant and matches the sequencing of the existing page presentation.
: List information and extracts/excerpts from the contacts on the [[Meier Encyclopedia]] pages so that each page encompasses everything there is to know about the subject from all of the contacts and document sources combined. Example [[Planets]], [[Event Timeline]], [[Beamship]]s, [[Atlantis]] etc., but the larger the page the greater need to shorten extracts/excerpts into shorter descriptions and brief summary with URL link or page numbers, instead.
: add questions answered from forum.figu.org to the [[Meier Encyclopedia]] and present it like its presented on the other pages, example [[Beamship]]s. There have been thousands of questions answered by FIGU already over many years, many of which answer most of the questions persons have ever had, the most useful and interesting of these questions answered can be included.
* Ensure all the contact reports/articles/documents are consistently presented, unless there are special reasons why a contact reports/articles/documents have been presented differently on certain pages.
: In the introduction section there ideally would be the pages, book, dates etc., all available to the reader e.g. [[Contact Report 001]] which is not always included on all the [[Contact Reports]] but could be taken from shop.figu.org [[Contact Statistics]] and the [[Gaiaguys_Web]] summary pages.
* Help complete lists and statistics;
:[[The_Pleiadian/Plejaren_Contact_Reports]]
:[[Contact Reports]]
:[[Contact Statistics]] - e.g. add last page of the block to the table so readers know all the page numbers etc.
:[[Index]]
* Adding books to the [[Books]] or [[Booklets]] section. Add FIGU documents, complete and improve descriptions, presentations and translations.
: make sure it's all there and makes sense to any reader from anywhere in the world.
: completing information which has not been completed about the books, e.g. description, captions etc.
* Tidy up pages in the [[Articles by others]] section, e.g. make sure links work, that it's presented in a way which works on different browsers tables are included etc., etc.
* Include information and headings not present on pages and articles. See how that has been done in the past to keep the website consistent.
: Translator notes
: Further reading
: Sources
: References 
* Adding letters to [[Letters from Billy]].
* Adding pages which include prophecies or predictions to [[Prophecies and Predictions]] page.
* Updating the [[Interviews with Billy]] section. Linking to interviews e.g. writing out word for word verbatim the contents of an interview and presenting it under a tab.
* Adding images to the [[Photo Gallery]] from the photobooks.
: or adding photos for other pages such as articles and meier encylopedia pages from the SSSC grounds, or Switzerland area, or perhaps you've taken a photo of a UFO or something interesting and already shown Billy and he's identified it; upload it and write a description if its part of the evidence because he identified it.
: Add higher resolution images (if they are genuinely higher resolution) by clicking on the 'newer version' upload button on the media page. The maximum resolution is about 2900 x 2900 or else there are problems creating thumbnails.
: adding images to the TOC area of contact reports and other pages in the way its been done on other pages.
: adding your art to the [[Art_Gallery]], and to some of the other pages.
: add a small selection of carefully selected photos of flowers from around the world, all the climates and biome types, as it's been done on [[External Links]] with a high quality relaxing description, introducing latin, taxomony, evolutionary characteristics, nations and geography. File name 'flowers_[flowername].jpg' has to be a creative commons image, try flickr, and add them to some of the pages that need to be cheered up in a neutral way, neutralising, calming, focusing, promoting concentration, filling large white spaces and are mildly educational for some reason. Only add one if it's going to be done nicely and presented neatly. 
:[[Plejaren_Federation]] page needs a flower on the right of the TOC, a carefully selected special flower which is colourful, orange would work best for that location.
* Add articles that you see or historical found article from the newspapers, magazines, television, films, books, etc., where it's an article about Billy Meier, at any age of his life, or about his information specifically, or one of his images were used, or a review or investigation or commentary and then add it to the [[Downloads]] or just add it by the uploads tab or create a new page for it if you have the text etc., see how other have added those things in the past. If it's anything by Michael Horn add it instead to the listing on the [[Michael Horn]] page, because of the shear nebulous quantity of things by him, it's easier just to redirect the reader to his own website and it's already all very well linked - same for other similar persons e.g. the original investigators. We are, and the Billy Meier audience are, mostly looking for rare media's from individuals we haven't heard from yet. Adding one or two from any good author or person is enough for readers to investigate it for themselves. If it's in another language place under the other languages section or link to the website on [[External Links]] instead, assuming it's not already a known website.
* Add PDF's to [[Downloads]] and present it the same way, with the front cover on right and descriptions in the media as you upload, collect the right and useful information about it, such as full name and full author and dates and ISBN and versions, revisions, publishing house etc.
* Add entries to the [[Site_News]], as it was done before.
* Adding [[FIGU_Bulletins]], [[FIGU_Open_Letters]], [[FIGU_Special_Bulletins]]
: indexing the information in them; but don't use [[Index]] that is for contact reports only, consider creating a new index for just the bulletins and other articles.
: ensuring they're all presented consistently
: adding other documents from FIGU
* Taking existing translations from other websites and importing them into this website using the existing framework
:Taking from translation websites and crediting the author and linking to it in the source section.
:Taking from forums and crediting the author and linking to it in the source section
:Adding a translation key for preliminary translation if its not a professional translation to the [[The_Pleiadian/Plejaren_Contact_Reports]] listing.
:Adding professionally translated documents and checking they are all listed properly on the various pages.
* Adding [[External_Links]]
* Adding [[FIGU_-_related_terms]]
* Updating [[FIGU]] page with content on the figu.org website
* Write a synopsis for a contact report (similar to the others) [[Contact Reports]].
* Add a new contact report, page or significant change to [[Site News]] with a description like the others there.
* Using the tools [[Special:SpecialPages]]
:check for broken links
:dead end pages
:broken redirects
:uncategorised pages
:forgotten pages on the 'all pages' that maybe should be linked better.
:link up pages that should be linked, which are causing readers to go looking for something, add explanations where necessary.
:make it user friendly and easy to find. 
:TOC Place the headings of information on a [[Meier Encyclopedia]] article at the right place in a pleasant sequencing.
:Look at how wikipedia itself handles large amounts of data and large audiences, at how they present it all, they work in big teams and are democratic therefore find good solutions, use those good solutions.

==References==
<small>
<references/>
</small>