https://en.wiki.ryzom.com/w/api.php?action=feedcontributions&user=Maupas&feedformat=atomRyzom Wiki - User contributions [en]2020-06-07T10:09:56ZUser contributionsMediaWiki 1.29.1https://en.wiki.ryzom.com/w/index.php?title=User_Manual/Common_Acronyms_and_Abbreviations&diff=31299User Manual/Common Acronyms and Abbreviations2019-08-08T10:25:07Z<p>Maupas: </p>
<hr />
<div>{{Trad<br />
|DE=Benutzerhandbuch/Gemeinsame Akronyme and Abkürzungen<br />
|EN=User Manual/Common Acronyms and Abbreviations<br />
|ES=<br />
|FR=Manuel de l'utilisateur/Acronymes usuels et abréviations<br />
|RU=<br />
|H=<br />
|palette=HRP<br />
}}<br />
{|cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;text-align:left;&quot; class=&quot;sortable&quot;<br />
|-bgcolor=&quot;#eee&quot; style=&quot;color:black;&quot;<br />
!Short<br />
!Signification<br />
|-<br />
|:) || happy <br />
|-<br />
|:( || sad <br />
|-<br />
|1h || 1-handed weapon <br />
|-<br />
|2h|| 2-handed weapon <br />
|-<br />
|afaik|| as far as I know <br />
|-<br />
|amp || Magic Amplifier <br />
|-<br />
|AoI || Abyss of Ichor (PR) <br />
|-<br />
|aggro || aggressive monsters or beasts<br />
|-<br />
|apt|| apartment <br />
|-<br />
|brain|| psykopia <br />
|-<br />
|brb || be right back <br />
|-<br />
|cat || experience catalyzer <br />
|-<br />
|ch ||choice <br />
|-<br />
|con ||constitution <br />
|-<br />
|cp|| care planning <br />
|-<br />
|CSR|| Customer Support Rep (GM) <br />
|-<br />
|cya || see you later <br />
|-<br />
|dp || death penalty <br />
|-<br />
|EF ||Elusive Forest (PR) <br />
|-<br />
|ele|| elemental magic level <br />
|-<br />
|ex || excellent <br />
|-<br />
|FH || Fairhaven <br />
|-<br />
|GH || Guild Hall <br />
|-<br />
|GL || Guild Leader <br />
|-<br />
|GM || Game Master (Support) <br />
|-<br />
|GoO ||Gate of Obscurity (PR) <br />
|-<br />
|gtg|| I've got to go now <br />
|-<br />
|gz || gratz, Congratulations <br />
|-<br />
|ha || heavy armor <br />
|-<br />
|HO || High Officer (of a guild) <br />
|-<br />
|hp || hit points <br />
|-<br />
|hq ||high quality <br />
|-<br />
|kk|| okie dokie , OK <br />
|-<br />
|ka || kick-ass <br />
|-<br />
| la || light armor<br />
|-<br />
| LoC || Lands of Continuity (PR)<br />
|-<br />
| lol || laugh out loud<br />
|-<br />
| LoU || Lands of Umbra (PR)<br />
|-<br />
| lvl || skill level<br />
|-<br />
| ma || medium armor<br />
|-<br />
| mat || material<br />
|-<br />
| ML || Mainland, used mostly on Silan<br />
|-<br />
| mob || monster or beast<br />
|-<br />
| NH ||Transporters to New Horizons<br />
|-<br />
| noob || new player, clueless<br />
|-<br />
| NM || Nexus Minor<br />
|-<br />
| np || no problem<br />
|-<br />
| NPC || Nonplayer (game) Character<br />
|-<br />
| nvm ||never mind<br />
|-<br />
| OO || Oflovaks Oasis<br />
|-<br />
| omw || on my way<br />
|-<br />
| op || outpost<br />
|-<br />
| plods ||ploderos<br />
|-<br />
| plz || please<br />
|-<br />
| PR || Prime Roots<br />
|-<br />
| q || quality as in q50 or q200<br />
|-<br />
| rez || resurrect<br />
|-<br />
| stam || stamina<br />
|-<br />
| SN || SuperNodes (for dig)<br />
|-<br />
| sup || supreme<br />
|-<br />
| tank ||fighter that confronts the MOB<br />
|-<br />
| ToT || Trench of Trials (PR)<br />
|-<br />
| tp || teleport<br />
|-<br />
| trek || run around Atys to purchase teleport pacts<br />
|-<br />
| US|| Underspring (PR)<br />
|-<br />
| WL || Wastelands (PR)<br />
|-<br />
| xD || Laugh out Loud<br />
|-<br />
| xp || experience points<br />
|-<br />
| Yrk || Yrkranis<br />
|-<br />
| Zzzz || sleeping<br />
|-<br />
|}<br />
<br />
[[Category:Glossary]][[Category:Gameplay]]</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=User_Manual/Common_Acronyms_and_Abbreviations&diff=31296User Manual/Common Acronyms and Abbreviations2019-08-08T10:23:15Z<p>Maupas: </p>
<hr />
<div>&lt;!-- {{Trad|DE=Benutzerhandbuch/Common Acronyms and Abbreviations|EN=User Manual/Common Acronyms and Abbreviations|FR=Manuel de l'utilisateur/Acronymes usuels et abréviations}} ---&gt;<br />
{{Trad<br />
|DE=Benutzerhandbuch/Gemeinsame Akronyme and Abkürzungen<br />
|EN=User Manual/Common Acronyms and Abbreviations<br />
|ES=<br />
|FR=Manuel de l'utilisateur/Acronymes usuels et abréviations<br />
|RU=<br />
|H=<br />
|palette=HRP<br />
}}<br />
{|cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;text-align:left;&quot; class=&quot;sortable&quot;<br />
|-bgcolor=&quot;#eee&quot; style=&quot;color:black;&quot;<br />
!Short<br />
!Signification<br />
|-<br />
|:) || happy <br />
|-<br />
|:( || sad <br />
|-<br />
|1h || 1-handed weapon <br />
|-<br />
|2h|| 2-handed weapon <br />
|-<br />
|afaik|| as far as I know <br />
|-<br />
|amp || Magic Amplifier <br />
|-<br />
|AoI || Abyss of Ichor (PR) <br />
|-<br />
|aggro || aggressive monsters or beasts<br />
|-<br />
|apt|| apartment <br />
|-<br />
|brain|| psykopia <br />
|-<br />
|brb || be right back <br />
|-<br />
|cat || experience catalyzer <br />
|-<br />
|ch ||choice <br />
|-<br />
|con ||constitution <br />
|-<br />
|cp|| care planning <br />
|-<br />
|CSR|| Customer Support Rep (GM) <br />
|-<br />
|cya || see you later <br />
|-<br />
|dp || death penalty <br />
|-<br />
|EF ||Elusive Forest (PR) <br />
|-<br />
|ele|| elemental magic level <br />
|-<br />
|ex || excellent <br />
|-<br />
|FH || Fairhaven <br />
|-<br />
|GH || Guild Hall <br />
|-<br />
|GL || Guild Leader <br />
|-<br />
|GM || Game Master (Support) <br />
|-<br />
|GoO ||Gate of Obscurity (PR) <br />
|-<br />
|gtg|| I've got to go now <br />
|-<br />
|gz || gratz, Congratulations <br />
|-<br />
|ha || heavy armor <br />
|-<br />
|HO || High Officer (of a guild) <br />
|-<br />
|hp || hit points <br />
|-<br />
|hq ||high quality <br />
|-<br />
|kk|| okie dokie , OK <br />
|-<br />
|ka || kick-ass <br />
|-<br />
| la || light armor<br />
|-<br />
| LoC || Lands of Continuity (PR)<br />
|-<br />
| lol || laugh out loud<br />
|-<br />
| LoU || Lands of Umbra (PR)<br />
|-<br />
| lvl || skill level<br />
|-<br />
| ma || medium armor<br />
|-<br />
| mat || material<br />
|-<br />
| ML || Mainland, used mostly on Silan<br />
|-<br />
| mob || monster or beast<br />
|-<br />
| NH ||Transporters to New Horizons<br />
|-<br />
| noob || new player, clueless<br />
|-<br />
| NM || Nexus Minor<br />
|-<br />
| np || no problem<br />
|-<br />
| NPC || Nonplayer (game) Character<br />
|-<br />
| nvm ||never mind<br />
|-<br />
| OO || Oflovaks Oasis<br />
|-<br />
| omw || on my way<br />
|-<br />
| op || outpost<br />
|-<br />
| plods ||ploderos<br />
|-<br />
| plz || please<br />
|-<br />
| PR || Prime Roots<br />
|-<br />
| q || quality as in q50 or q200<br />
|-<br />
| rez || resurrect<br />
|-<br />
| stam || stamina<br />
|-<br />
| SN || SuperNodes (for dig)<br />
|-<br />
| sup || supreme<br />
|-<br />
| tank ||fighter that confronts the MOB<br />
|-<br />
| ToT || Trench of Trials (PR)<br />
|-<br />
| tp || teleport<br />
|-<br />
| trek || run around Atys to purchase teleport pacts<br />
|-<br />
| US|| Underspring (PR)<br />
|-<br />
| WL || Wastelands (PR)<br />
|-<br />
| xD || Laugh out Loud<br />
|-<br />
| xp || experience points<br />
|-<br />
| Yrk || Yrkranis<br />
|-<br />
| Zzzz || sleeping<br />
|-<br />
|}<br />
<br />
[[Category:Glossary]][[Category:Gameplay]]</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Portal:Fyros&diff=31295Portal:Fyros2019-08-07T22:07:35Z<p>Maupas: </p>
<hr />
<div>{{Tabs<br />
|Tab-1={{3DText|group=fyros|text='''&lt;big&gt;Fyros&lt;/big&gt;'''}}<br />
|URL-1=Portal:Fyros<br />
|bg_Tab-1=#{{ColorAtys|group=fyros|type=light}}<br />
<br />
|Tab-2={{3DText|group=fyros|text='''History'''}}<br />
|URL-2=Portal:Fyros/History<br />
|bg_Tab-2=#{{ColorAtys|group=fyros|type=light}}<br />
<br />
|Tab-3={{3DText|group=fyros|text='''Protagonists'''}}<br />
|URL-3=Portal:Fyros/Protagonists<br />
|bg_Tab-3=#{{ColorAtys|group=fyros|type=light}}<br />
<br />
|Tab-4={{3DText|group=fyros|text='''Politics'''}}<br />
|URL-4=Portal:Fyros/Relations<br />
|bg_Tab-4=#{{ColorAtys|group=fyros|type=light}}<br />
<br />
|Tab-5={{3DText|group=fyros|text='''Culture'''}}<br />
|URL-5=Portal:Fyros/Culture<br />
|bg_Tab-5=#{{ColorAtys|group=fyros|type=light}}<br />
<br />
|Tab-6={{3DText|group=fyros|text='''Roleplay'''}}<br />
|URL-6=Portal:Fyros/Roleplay<br />
|bg_Tab-6=#{{ColorAtys|group=fyros|type=light}}<br />
<br />
|Tab-7={{3DText|group=fyros|text='''fyrk'''}}<br />
|URL-7=Portal:Fyros/fyrk<br />
|bg_Tab-7=#{{ColorAtys|group=fyros|type=light}}<br />
<br />
|bord=2px solid #{{ColorAtys|type=dark|group=fyros}}<br />
|bg_frame=#{{ColorAtys|type=bg|group=fyros}}<br />
|round=5em<br />
|align_tab=center<br />
}}<br />
{{Trad<br />
|DE=Portal:Fyros<br />
|EN=Portal:Fyros<br />
|ES=Portal:Fyros<br />
|FR=Portail:Fyros<br />
|RU=Portal:Fyros<br />
|H=<br />
|palette=fyros<br />
}}<br />
[[Image:Portail fyros princ.png|center]]<br />
&lt;div style=&quot;text-align:center;&quot;&gt;<br />
{{3DText|group=fyros|3D=outset|text=&lt;span style=&quot;font-size:large;font-variant: small-caps;font-weight: bold;&quot;&gt;'''''The portal of the Fyros'''''&lt;/span&gt;}}<br />
<br />
{{3DText|group=fyros|3D=outset|text='''There are currently {{Number of pages}} on [[:category:Fyros|Fyros]].'''}}<br />
&lt;/div&gt;<br />
&lt;!-- TOP --&gt;<br />
{| style=&quot;margin-top:10px; background:none;width:100%;&quot;<br />
| style=&quot;width:100%; border:medium outset #{{ColorAtys|type=dark|group=fyros}}; vertical-align:top; padding: 0px 10px 10px 0px; -moz-border-radius: 10px; -webkit-border-radius: 10px; border-radius:10px;background:#{{ColorAtys|type=bg|group=fyros}};color:#{{ColorAtys|type=fg|group=fyros}}&quot; |<br />
{| cellpadding=&quot;2&quot; cellspacing=&quot;5&quot; style=&quot;width:100%; vertical-align:top; background:transparent; font-weight:bold; text-align: NOcenter;&quot;<br />
!{{ContentBox<br />
|title = {{3DText|group=fyros|text = Abstract}}<br />
|palette=fyros<br />
|image= R2_scenario_admin.png<br />
|content =<br />
}}<br />
|}<br />
|}<br />
&lt;!-- LEFT --&gt;<br />
{| style=&quot;margin-top:10px; background:none;&quot;<br />
| style=&quot;width:65%; border:medium outset #{{ColorAtys|type=dark|group=fyros}}; vertical-align:top; padding: 0px 10px 10px 0px; -moz-border-radius: 10px; -webkit-border-radius: 10px; border-radius:10px;background:#{{ColorAtys|type=bg|group=fyros}};color:#{{ColorAtys|type=fg|group=fyros}}&quot; |<br />
{| cellpadding=&quot;2&quot; cellspacing=&quot;5&quot; style=&quot;width:100%; vertical-align:top; background:transparent;&quot;<br />
&lt;!-- ==============LIGHT ON ================ --&gt;<br />
!{{ContentBox<br />
|title= {{3DText|group=fyros|3D=inset|text=General presentation}}&lt;!-- default=Spotlight on}}--&gt;<br />
|palette=fyros<br />
|image= Fyros emblem.png&lt;!-- default=Zor emblem.png--&gt;<br />
|content=<br />
&lt;!--{{:Featured article/Fyros}}<br />
ou {{:Lumière sur/Fyros/Semaine/{{CURRENTDOW}}}} <br />
ou {{:Lumière sur/Fyros/Mois/{{CURRENTDAY2}}}}<br />
Templates and pages to choose and display are in Category:Portals⇒Category:Template:Portal⇒Category:Featured article⇒Lumière sur/Fyros<br />
--&gt; &lt;!--{{:Featured article/Fyros}} <br />
or {{:Featured article/Fyros/Week/{{CURRENTDOW}}}}<br />
or {{:Featured article/Fyros/Month/{{CURRENTDAY2}}}}<br />
Templates and pages to choose and display are in Category:Portals⇒Category:Template:Portal⇒Category:Featured article⇒Featured article/Fyros<br />
--&gt;<br />
|link = [[Special:RandomInCategory/{{NAMESPACE}}_{{PAGENAME}}/Articles liés|Une page au hasard dans ''' ''{{PAGENAME}}'' ''']]<br />
}}<br />
|}<br />
|&lt;!-- SPACE --&gt; style=&quot;border:5px solid transparent;&quot; |<br />
&lt;!-- RIGHT --&gt;<br />
| style=&quot;width:35%; border:medium outset #{{ColorAtys|type=dark|group=fyros}}; vertical-align:top; padding: 0px; -moz-border-radius: 10px; -webkit-border-radius: 10px; border-radius:10px;background:#{{ColorAtys|type=light|group=fyros}};color:#{{ColorAtys|type=fg|group=fyros}}&quot; |<br />
{| id=&quot;mp-right&quot; cellpadding=&quot;2&quot; cellspacing=&quot;5&quot; style=&quot;width:100%; vertical-align:top; background:transparent;&quot;<br />
!{{ContentBox<br />
|title= {{3DText|group=fyros|3D=inset|text=More about}}<br />
|palette=fyros<br />
|image= Stub.png<br />
|content= {{:Portal_Fyros/More about}} <br />
}}<br />
<br />
!{{ContentBox<br />
|title= {{3DText|group=fyros|3D=inset|text=Plan}}<br />
|palette=fyros<br />
|image= Ico task rite.png<br />
|content= {{:Portal_Fyros/Plan}} <br />
}}<br />
<br />
!{{ContentBox<br />
|title= {{3DText|group=fyros|3D=inset|text=Archives}}<br />
|palette=fyros<br />
|image= Spe inventory.png<br />
|content = {{:Portal_Fyros/Archives}} <br />
}}<br />
<br />
! {{ContentBox<br />
|title= {{3DText|group=fyros|3D=inset|text=To do}}<br />
|palette=fyros<br />
|image = Script_edit.png <br />
|content = {{:Portail_Fyros/2do}}<br />
}}<br />
<br />
|}<br />
|}<br />
<br />
&lt;!-- BOTTOM --&gt;<br />
{{Portal bottom|fyros}}<br />
<br />
__NOTOC__<br />
__NOEDITSECTION__<br />
<br />
[[category: Portals]] [[category: Fyros]]</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Talk:Wiki_Technical_Guide&diff=30546Talk:Wiki Technical Guide2019-06-30T18:03:27Z<p>Maupas: /* Easy to discriminate? */</p>
<hr />
<div>==New(?) templates {{OK}}==<br />
I created [[Template:OK]] ({{OK}}) and [[Template:KO]] ({{KO}}), but I am wondering if those don't already exist with an other name. If they do, please let me know. [[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 00:33, 9 June 2019 (CEST)<br />
:I did so in FR. I think I had not yet time to export in other languages. So, thx to had done it here :) -- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 18:29, 30 June 2019 (CEST)<br />
<br />
== Easy to discriminate? ==<br />
<br />
{{quotation||This facilitates discriminated responses in their consideration, implementation, etc.}}<br />
Really? It sounds like: &quot;This (Writing 50 titles instead of 1 title for 50 topics) make it easy to discriminate responses in consideration, implementation, etc.&quot;&lt;br&gt;Better: &quot;This prevent discriminated responses in their consideration, implementation, etc.&quot; Or what should there be said?&lt;br&gt;--[[:de:User:Heernis|Heernis]] ([[:de:Benutzer_Diskussion:Heernis|talks]]) 30. June 2019 - 14:22<br />
:Of the french text written by Zorroagh I understood that the one who want to modify, (or ask/answer questions about, or translate) some topic will find and work on this topic more easily if it is a short one. Hence my &quot;faithful&quot; translation of ''&quot;Cela facilite les réponses discriminées dans leur prise en compte, leur réalisation, etc.&quot;''<br />
:But I agree that this point of view is questionable (after all, sections are not so difficult to reach and work on) and I suspect the main reason for such a recommendation (systematical splitting of articles) is the difficulties encountered in implementation of wikis in WebIG.<br />
:More, your question raise the point of translation. In fact, as I'am not a native EN speaker, the present EN Wiki Technical Guide need to be checked by somebody who is AND understands FR enough (you know that's how we work in Translation Team). I don't know if we have among ourselves wikis contributors such a person but I think we could at least add a status reading &quot;Proofreading requested&quot; in the TIP template. What do you think?--[[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 17:16, 30 June 2019 (CEST)<br />
::Not sure I understand.<br />
::Reading you, I have the impression that we mix up two subjecs.<br />
::;First one: In my mind I wrote &quot;Cela facilite les réponses discriminées dans leur prise en compte, leur réalisation, etc.&quot; in some context as forum or chat in where it's more a long marathon of interrupted and intertwine interventions not very easy to use as a problem statement. So I probably, because I have no time to find where I said this, I suggested to write a single problem to solve, for instance here. In my mind it would not be so hard to do titles end subtitles in discussion pages? I'm very puzzled and ask myself if I understand you.<br />
::;Second one: Amosys has seen that long text couldn't be well displayed in game with the IG web tool. So he suggested to split long page in some other. For me it's not a problem at all and I can give you thousand of solution already used bay contributors: one of my preferred is: [[Primes_Raider]].<br />
::We have so many solutions in the wiki :) -- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 18:57, 30 June 2019 (CEST)<br />
:::Ooops... sorry for the involuntary illustration of the very (first) point your &quot;Cela facilite les réponses discriminées dans leur prise en compte, leur réalisation, etc.&quot; was raising.<br />
:::;First point: I realize that, in my answer to Heernis, I just forgot the context (which is not of '''all''' pages but only of '''talk''' pages). So, I think '''your''' answer will be more understandable by Heernis than mine. Grytt :-).<br />
:::;Second point: This one came to my mind precisely because of my misunderstanding of the context, and, though I totally agree with you as for solutions of the WebIG issue, it have not to be raised here. Sorry again :-(<br />
:::--[[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 20:03, 30 June 2019 (CEST)<br />
<br />
== Preventing discussion by indicating the link? ==<br />
<br />
{{Quotation||Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion.}} This sound weird. Should be rewritten. (Think more simple ;-) )&lt;br&gt;--[[:de:User:Heernis|Heernis]] ([[:de:Benutzer_Diskussion:Heernis|talks]]) 30. June 2019 - 14:35<br />
:I replaced the &quot;weird&quot; sentence ('''prevent''' is NOT the right verb, no :-)) as follows:<br />
:“''So, please notify the ones you think concerned about the talk by adding the link to it in their own user talk page.''” Feel free to improve it, tough!--[[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 17:33, 30 June 2019 (CEST)<br />
::And it's so true, that I answered here as soon as I could!!! ;)<br />
::Have a look in my [[fr:Discussion_utilisateur:Zorroargh#Wiki_Technical_Guide_.E2.9C.93|discussion page]], Heernis, to see hwo Mapas did -- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 19:07, 30 June 2019 (CEST)</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Talk:Wiki_Technical_Guide&diff=30543Talk:Wiki Technical Guide2019-06-30T17:01:50Z<p>Maupas: /* Easy to discriminate? */</p>
<hr />
<div>==New(?) templates {{OK}}==<br />
I created [[Template:OK]] ({{OK}}) and [[Template:KO]] ({{KO}}), but I am wondering if those don't already exist with an other name. If they do, please let me know. [[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 00:33, 9 June 2019 (CEST)<br />
:I did so in FR. I think I had not yet time to export in other languages. So, thx to had done it here :) -- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 18:29, 30 June 2019 (CEST)<br />
<br />
== Easy to discriminate? ==<br />
<br />
{{quotation||This facilitates discriminated responses in their consideration, implementation, etc.}}<br />
Really? It sounds like: &quot;This (Writing 50 titles instead of 1 title for 50 topics) make it easy to discriminate responses in consideration, implementation, etc.&quot;&lt;br&gt;Better: &quot;This prevent discriminated responses in their consideration, implementation, etc.&quot; Or what should there be said?&lt;br&gt;--[[:de:User:Heernis|Heernis]] ([[:de:Benutzer_Diskussion:Heernis|talks]]) 30. June 2019 - 14:22<br />
:Of the french text written by Zorroagh I understood that the one who want to modify, (or ask/answer questions about, or translate) some topic will find and work on this topic more easily if it is a short one. Hence my &quot;faithful&quot; translation of ''&quot;Cela facilite les réponses discriminées dans leur prise en compte, leur réalisation, etc.&quot;''<br />
:But I agree that this point of view is questionable (after all, sections are not so difficult to reach and work on) and I suspect the main reason for such a recommendation (systematical splitting of articles) is the difficulties encountered in implementation of wikis in WebIG.<br />
:More, your question raise the point of translation. In fact, as I'am not a native EN speaker, the present EN Wiki Technical Guide need to be checked by somebody who is AND understands FR enough (you know that's how we work in Translation Team). I don't know if we have among ourselves wikis contributors such a person but I think we could at least add a status reading &quot;Proofreading requested&quot; in the TIP template. What do you think?--[[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 17:16, 30 June 2019 (CEST)<br />
::Not sure I understand.<br />
::Reading you, I have the impression that we mix up two subjecs.<br />
::;First one: In my mind I wrote &quot;Cela facilite les réponses discriminées dans leur prise en compte, leur réalisation, etc.&quot; in some context as forum or chat in where it's more a long marathon of interrupted and intertwine interventions not very easy to use as a problem statement. So I probably, because I have no time to find where I said this, I suggested to write a single problem to solve, for instance here. In my mind it would not be so hard to do titles end subtitles in discussion pages? I'm very puzzled and ask myself if I understand you.<br />
::;Second one: Amosys has seen that long text couldn't be well displayed in game with the IG web tool. So he suggested to split long page in some other. For me it's not a problem at all and I can give you thousand of solution already used bay contributors: one of my preferred is: [[Primes_Raider]].<br />
::We have so many solutions in the wiki :) -- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 18:57, 30 June 2019 (CEST)<br />
<br />
== Preventing discussion by indicating the link? ==<br />
<br />
{{Quotation||Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion.}} This sound weird. Should be rewritten. (Think more simple ;-) )&lt;br&gt;--[[:de:User:Heernis|Heernis]] ([[:de:Benutzer_Diskussion:Heernis|talks]]) 30. June 2019 - 14:35<br />
:I replaced the &quot;weird&quot; sentence ('''prevent''' is NOT the right verb, no :-)) as follows:<br />
:“''So, please notify the ones you think concerned about the talk by adding the link to it in their own user talk page.''” Feel free to improve it, tough!--[[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 17:33, 30 June 2019 (CEST)</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Talk:Wiki_Technical_Guide&diff=30542Talk:Wiki Technical Guide2019-06-30T16:58:20Z<p>Maupas: /* Preventing discussion by indicating the link? */</p>
<hr />
<div>==New(?) templates {{OK}}==<br />
I created [[Template:OK]] ({{OK}}) and [[Template:KO]] ({{KO}}), but I am wondering if those don't already exist with an other name. If they do, please let me know. [[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 00:33, 9 June 2019 (CEST)<br />
:I did so in FR. I think I had not yet time to export in other languages. So, thx to had done it here :) -- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 18:29, 30 June 2019 (CEST)<br />
<br />
== Easy to discriminate? ==<br />
<br />
{{quotation||This facilitates discriminated responses in their consideration, implementation, etc.}}<br />
Really? It sounds like: &quot;This (Writing 50 titles instead of 1 title for 50 topics) make it easy to discriminate responses in consideration, implementation, etc.&quot;&lt;br&gt;Better: &quot;This prevent discriminated responses in their consideration, implementation, etc.&quot; Or what should there be said?&lt;br&gt;--[[:de:User:Heernis|Heernis]] ([[:de:Benutzer_Diskussion:Heernis|talks]]) 30. June 2019 - 14:22<br />
:Of the french text written by Zorroagh I understood that the one who want to modify, (or ask/answer questions about, or translate) some topic will find and work on this topic more easily if it is a short one. Hence my &quot;faithful&quot; translation of ''&quot;Cela facilite les réponses discriminées dans leur prise en compte, leur réalisation, etc.&quot;''<br />
:But I agree that this point of view is questionable (after all, sections are not so difficult to reach and work on) and I suspect the main reason for such a recommendation (systematical splitting of articles) is the difficulties encountered in implementation of wikis in WebIG.<br />
:More, your question raise the point of translation. In fact, as I'am not a native EN speaker, the present EN Wiki Technical Guide need to be checked by somebody who is AND understands FR enough (you know that's how we work in Translation Team). I don't know if we have among ourselves wikis contributors such a person but I think we could at least add a status reading &quot;Proofreading requested&quot; in the TIP template. What do you think?--[[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 17:16, 30 June 2019 (CEST)<br />
:Not sure I understand.<br />
:Reading you, I have the impression that we mix up two subjecs.<br />
:;First one: In my mind I wrote &quot;Cela facilite les réponses discriminées dans leur prise en compte, leur réalisation, etc.&quot; in some context as forum or chat in where it's more a long marathon of interrupted and intertwine interventions not very easy to use as a problem statement. So I probably, because I have no time to find where I said this, I suggested to write a single problem to solve, for instance here. In my mind it would not be so hard to do titles end subtitles in discussion pages? I'm very puzzled and ask myself if I understand you.<br />
:;Second one: Amosys has seen that long text couldn't be well displayed in game with the IG web tool. So he suggested to split long page in some other. For me it's not a problem at all and I can give you thousand of solution already used bay contributors: one of my preferred is: [[Primes_Raider]].<br />
:We have so many solutions in the wiki :) -- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 18:57, 30 June 2019 (CEST)<br />
<br />
== Preventing discussion by indicating the link? ==<br />
<br />
{{Quotation||Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion.}} This sound weird. Should be rewritten. (Think more simple ;-) )&lt;br&gt;--[[:de:User:Heernis|Heernis]] ([[:de:Benutzer_Diskussion:Heernis|talks]]) 30. June 2019 - 14:35<br />
:I replaced the &quot;weird&quot; sentence ('''prevent''' is NOT the right verb, no :-)) as follows:<br />
:“''So, please notify the ones you think concerned about the talk by adding the link to it in their own user talk page.''” Feel free to improve it, tough!--[[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 17:33, 30 June 2019 (CEST)</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Talk:Wiki_Technical_Guide&diff=30541Talk:Wiki Technical Guide2019-06-30T16:57:53Z<p>Maupas: /* Preventing discussion by indicating the link? */</p>
<hr />
<div>==New(?) templates {{OK}}==<br />
I created [[Template:OK]] ({{OK}}) and [[Template:KO]] ({{KO}}), but I am wondering if those don't already exist with an other name. If they do, please let me know. [[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 00:33, 9 June 2019 (CEST)<br />
:I did so in FR. I think I had not yet time to export in other languages. So, thx to had done it here :) -- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 18:29, 30 June 2019 (CEST)<br />
<br />
== Easy to discriminate? ==<br />
<br />
{{quotation||This facilitates discriminated responses in their consideration, implementation, etc.}}<br />
Really? It sounds like: &quot;This (Writing 50 titles instead of 1 title for 50 topics) make it easy to discriminate responses in consideration, implementation, etc.&quot;&lt;br&gt;Better: &quot;This prevent discriminated responses in their consideration, implementation, etc.&quot; Or what should there be said?&lt;br&gt;--[[:de:User:Heernis|Heernis]] ([[:de:Benutzer_Diskussion:Heernis|talks]]) 30. June 2019 - 14:22<br />
:Of the french text written by Zorroagh I understood that the one who want to modify, (or ask/answer questions about, or translate) some topic will find and work on this topic more easily if it is a short one. Hence my &quot;faithful&quot; translation of ''&quot;Cela facilite les réponses discriminées dans leur prise en compte, leur réalisation, etc.&quot;''<br />
:But I agree that this point of view is questionable (after all, sections are not so difficult to reach and work on) and I suspect the main reason for such a recommendation (systematical splitting of articles) is the difficulties encountered in implementation of wikis in WebIG.<br />
:More, your question raise the point of translation. In fact, as I'am not a native EN speaker, the present EN Wiki Technical Guide need to be checked by somebody who is AND understands FR enough (you know that's how we work in Translation Team). I don't know if we have among ourselves wikis contributors such a person but I think we could at least add a status reading &quot;Proofreading requested&quot; in the TIP template. What do you think?--[[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 17:16, 30 June 2019 (CEST)<br />
:Not sure I understand.<br />
:Reading you, I have the impression that we mix up two subjecs.<br />
:;First one: In my mind I wrote &quot;Cela facilite les réponses discriminées dans leur prise en compte, leur réalisation, etc.&quot; in some context as forum or chat in where it's more a long marathon of interrupted and intertwine interventions not very easy to use as a problem statement. So I probably, because I have no time to find where I said this, I suggested to write a single problem to solve, for instance here. In my mind it would not be so hard to do titles end subtitles in discussion pages? I'm very puzzled and ask myself if I understand you.<br />
:;Second one: Amosys has seen that long text couldn't be well displayed in game with the IG web tool. So he suggested to split long page in some other. For me it's not a problem at all and I can give you thousand of solution already used bay contributors: one of my preferred is: [[Primes_Raider]].<br />
:We have so many solutions in the wiki :) -- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 18:57, 30 June 2019 (CEST)<br />
<br />
== Preventing discussion by indicating the link? ==<br />
<br />
{{Quotation||Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion.}} This sound weird. Should be rewritten. (Think more simple ;-) )&lt;br&gt;--[[:de:User:Heernis|Heernis]] ([[:de:Benutzer_Diskussion:Heernis|talks]]) 30. June 2019 - 14:35<br />
:I replaced the &quot;weird&quot; sentence (prevent is NOT the right verb, no :-)) as follows:<br />
:“''So, please notify the ones you think concerned about the talk by adding the link to it in their own user talk page.''” Feel free to improve it, tough!--[[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 17:33, 30 June 2019 (CEST)</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Talk:Wiki_Technical_Guide&diff=30537Talk:Wiki Technical Guide2019-06-30T15:54:01Z<p>Maupas: /* Easy to discriminate? */</p>
<hr />
<div>==New(?) templates==<br />
I created [[Template:OK]] ({{OK}}) and [[Template:KO]] ({{KO}}), but I am wondering if those don't already exist with an other name. If they do, please let me know. [[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 00:33, 9 June 2019 (CEST)<br />
<br />
== Easy to discriminate? ==<br />
<br />
{{quotation||This facilitates discriminated responses in their consideration, implementation, etc.}}<br />
Really? It sounds like: &quot;This (Writing 50 titles instead of 1 title for 50 topics) make it easy to discriminate responses in consideration, implementation, etc.&quot;&lt;br&gt;Better: &quot;This prevent discriminated responses in their consideration, implementation, etc.&quot; Or what should there be said?&lt;br&gt;--[[:de:User:Heernis|Heernis]] ([[:de:Benutzer_Diskussion:Heernis|talks]]) 30. June 2019 - 14:22<br />
:Of the french text written by Zorroagh I understood that the one who want to modify, (or ask/answer questions about, or translate) some topic will find and work on this topic more easily if it is a short one. Hence my &quot;faithful&quot; translation of &quot;''Cela facilite les réponses discriminées dans leur prise en compte, leur réalisation, etc.''&quot;<br />
:But I agree that this point of view is questionable (after all, sections are not so difficult to reach and work on) and I suspect the main reason for such a recommendation (systematical splitting of articles) is the difficulties encountered in implementation of wikis in WebIG.<br />
:More, your question raise the point of translation. In fact, as I'am not a native EN speaker, the present EN Wiki Technical Guide need to be checked by somebody who is AND understands FR enough (you know that's how we work in Translation Team). I don't know if we have among ourselves wikis contributors such a person but I think we could at least add a status reading &quot;Proofreading requested&quot; in the TIP template. What do you think?--[[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 17:16, 30 June 2019 (CEST)<br />
<br />
== Preventing discussion by indicating the link? ==<br />
<br />
{{Quotation||Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion.}} This sound weird. Should be rewritten. (Think more simple ;-) )&lt;br&gt;--[[:de:User:Heernis|Heernis]] ([[:de:Benutzer_Diskussion:Heernis|talks]]) 30. June 2019 - 14:35<br />
:I replaced the &quot;weird&quot; sentence as follows:<br />
:“''So, please notify the ones you think concerned about the talk by adding the link to it in their own user talk page.''” Feel free to improve it, tough!--[[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 17:33, 30 June 2019 (CEST)</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Talk:Wiki_Technical_Guide&diff=30536Talk:Wiki Technical Guide2019-06-30T15:41:44Z<p>Maupas: /* Preventing discussion by indicating the link? */</p>
<hr />
<div>==New(?) templates==<br />
I created [[Template:OK]] ({{OK}}) and [[Template:KO]] ({{KO}}), but I am wondering if those don't already exist with an other name. If they do, please let me know. [[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 00:33, 9 June 2019 (CEST)<br />
<br />
== Easy to discriminate? ==<br />
<br />
{{quotation||This facilitates discriminated responses in their consideration, implementation, etc.}}<br />
Really? It sounds like: &quot;This (Writing 50 titles instead of 1 title for 50 topics) make it easy to discriminate responses in consideration, implementation, etc.&quot;&lt;br&gt;Better: &quot;This prevent discriminated responses in their consideration, implementation, etc.&quot; Or what should there be said?&lt;br&gt;--[[:de:User:Heernis|Heernis]] ([[:de:Benutzer_Diskussion:Heernis|talks]]) 30. June 2019 - 14:22<br />
:Of the french text written by Zorroagh I understood that the one who want to modify, (or ask/answer questions about, or translate) some topic will find and work on this topic more easily if it is a short one. Hence my &quot;faithful&quot; translation of &quot;''Cela facilite les réponses discriminées dans leur prise en compte, leur réalisation, etc.''&quot;<br />
:But I agree that this point of view is questionable (after all, sections are not so difficult to reach and work on) and suspects the main reason for such a recommendation (systematical splitting of articles) is the difficulties encountered in implementation of wikis in WebIG.<br />
:More, your question raise the point of translation. In fact, as I'am not a native EN speaker, the present EN Wiki Technical Guide need to be checked by somebody who is AND understands FR enough (you know that's how we work in Translation Team). I don't know if we have among ourselves wikis contributors such a person but I think we could at least add a status reading &quot;Proofreading requested&quot; in the TIP template. What do you think?--[[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 17:16, 30 June 2019 (CEST)<br />
<br />
== Preventing discussion by indicating the link? ==<br />
<br />
{{Quotation||Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion.}} This sound weird. Should be rewritten. (Think more simple ;-) )&lt;br&gt;--[[:de:User:Heernis|Heernis]] ([[:de:Benutzer_Diskussion:Heernis|talks]]) 30. June 2019 - 14:35<br />
:I replaced the &quot;weird&quot; sentence as follows:<br />
:“''So, please notify the ones you think concerned about the talk by adding the link to it in their own user talk page.''” Feel free to improve it, tough!--[[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 17:33, 30 June 2019 (CEST)</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=30535Wiki Technical Guide2019-06-30T15:41:21Z<p>Maupas: </p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=4<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.''''' See [[Writing Guide]] for basic wiki knowledge.<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). So, please notify the ones you think concerned about the talk by adding the link to it in their own user talk page. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Lore Validation Request}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''&lt;big&gt;Categories&lt;/big&gt;'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
&lt;div style=&quot;text-align:center;&quot;&gt;<br />
{{3DText|3D=outset|group=ranger|text=&lt;span style=&quot;font-size:large;font-variant: small-caps;font-weight: bold;&quot;&gt;'''''Portal …'''''&lt;/span&gt;}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''&lt;code&gt;&lt;nowiki&gt;There are for now {{Number of pages}} pages on …&lt;/nowiki&gt;&lt;/code&gt;'''<br />
&lt;/div&gt;<br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use &lt;code&gt;&lt;nowiki&gt;{{Number of pages}}&lt;/nowiki&gt;&lt;/code&gt; that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article &lt;big&gt;'''''[[Categorization]]'''''&lt;/big&gt;. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
<br />
[[File:Mindmap 6 wikis and image categories 2019-06-14.png|center|800px|alt=6 wikis, 6 category systems, all images in common|Six wikis, six category systems, all images in common]]<br />
&lt;div style=&quot;text-align:center;&quot;&gt;'''—• Six wikis, six category systems, all images in common •—'''&lt;/div&gt;<br />
<br />
=='''&lt;big&gt;Template&lt;/big&gt;'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
<br />
===Naming your Template===<br />
Some rules for naming templates.<br />
<br />
===All templates===<br />
&lt;big&gt;'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.&lt;/big&gt;<br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''&lt;big&gt;Portal&lt;/big&gt;'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|Associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''&lt;code&gt;&lt;nowiki&gt;{{:DOCNAME}}&lt;/nowiki&gt;&lt;/code&gt;''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class=&quot;wikitable centre&quot;<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || &lt;nowiki&gt;{{:Featured article/...}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/...}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the week || &lt;nowiki&gt;{{:Featured article/GBA/Week/{{CURRENTDOW}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the month || &lt;nowiki&gt;{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}&lt;/nowiki&gt;<br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Associated categories===<br />
====All relevant pages====<br />
To associate an article to a portal, just add at the bottom of the text of the said article a block of instructions of the following type:<br />
'''&lt;pre&gt;&lt;nowiki&gt;{{clear}}{{Last version link}}<br />
&lt;noinclude&gt;{{Portal|xxx}}<br />
[[Category:yyyy]]&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/pre&gt;'''<br />
where:<br />
*the “clear” ensures that the navigation bar to the portal is well above the last image;<br />
*the “last version link” allows you to time stamp the page and adds a discreet tab to find the origin of an inclusion;<br />
*the “noinclude” can be put in so as not to pollute the inclusion.<br />
====On the front page====<br />
Adding the navigation banner to the portal also places the article in “hidden” categories, categories that would not be shown to the reader because they are not relevant, but are indicated by a '''[+]''' located after the last displayed category. The random choice technique has been rejected by Mediawiki as too expensive. Currently, it is preferred a restricted choice (day of the week or month). This requires you to create one redirection at a time to the page you want to highlight. Thus, for example, the “Featured article/GBA/Day/3” page (3rd of the month or Wednesday) is redirected to “Primes Raider”.<br />
<br />
What if the article is too long to be included, or if only some of its sections are worthwhile?<br />
<br />
The wisest way is to signal the sections to be displayed or hidden in the future inclusion by marking them up in the source article.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/noinclude&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to exclude the parts they frame from the future inclusion.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to include only the parts they frame in the future inclusion.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to include only the parts they frame in the future inclusion, while masking them in the original article (to be handled carefully in a template).<br />
<br />
This latter markup is used, for example, to hide in the original article the “To be continued…” ('''&lt;code&gt;&lt;nowiki&gt;{{read more|&lt;&lt;the original article&gt;}}&lt;/nowiki&gt;&lt;/code&gt;''' displayed below) but displays it in the inclusion. {{read more|{{FULLPAGENAME}}}}<br />
<br />
=='''&lt;big&gt;Home page&lt;/big&gt;'''==<br />
Home pages are “specific” because they are those that appear by default when you log in to the wiki. These pages are not editable and can contain many HTML (and Java) tricks. This implies that only seasoned contributors can modify them on community consensus or communication imperatives.<br />
<br />
<br />
== Other advanced stuffs ==<br />
API, tips on Special commands...<br />
<br />
[[Wiki Technical Guide/Comparaison of lists ns and other]]<br />
=== namespaces ===<br />
Code used: &lt;nowiki&gt;{{Special:AllPages|namespace=1}}&lt;/nowiki&gt;<br />
<br />
Usually, the talk has ns+1. To be bief, no talk here (see more detailled pages) BUT un-usual.<br />
<br />
Commons to all:<br />
<br />
*Namespace 1 - Talk (in fr Discussion)<br />
*Namespace 2 - User (in fr, or Utilisateur or Utilisatrices)<br />
* Namespace 6 - File - Fichier <br />
*Namespace 8 - MediaWiki <br />
*Namespace 10 - Modèle - Template <br />
*Namespace 12 - Aide - Help<br />
*Namespace 14 - Category - Catégorie<br />
<br />
==== FR ns ====<br />
see [[:fr:Guide Technique du wiki/FR ns liste]] (commands are KO in here)<br />
<br />
*Namespace 4 - '''EncyclopAtys'''<br />
*Namespace 100 - Guilde<br />
*Namespace 106 - '''Portail - Portal'''<br />
<br />
==== EN ns ====<br />
see [[Wiki Technical Guide/EN ns list]]<br />
<br />
But:<br />
*Namespace '''4 - Ryzom Wiki''' and 5 Namespace 5 - Ryzom Wiki talk<br />
*Namespace '''104 - Event'''<br />
<br />
==== DE ns ====<br />
[[:de:Technischer Wiki-Leitfaden/DE ns list]]<br />
<br />
Looks like the EN, but no Event namespace, less pages and talk<br />
<br />
==== Atys Common ns ====<br />
See [https://atys.wiki.ryzom.com/wiki/User:Heernis/Common_ns_list Common ns list on atys common]<br />
<br />
As the DE/EN wikis: User (ns 2), File (ns 6), Template 10, Help (ns 12) 3p, Category (ns 14)<br />
<br />
* Namespace 4 - '''Ryzom Commons (ns 4)'''<br />
<br />
=== Wiki codes about categories ===<br />
* on common, Heernis used &lt;nowiki&gt;&lt;categorytree mode=&quot;all&quot; depth=&quot;20&quot; showcount&quot;on&quot; hideprefix=&quot;never&quot;&gt;Wikipatys&lt;/categorytree&gt;&lt;/nowiki&gt; to get result: Wikipatys, Deutsch, English, Graphic Charter, Hidden categories<br />
* The code &lt;nowiki&gt;&lt;categorytree&gt;Foo&lt;/categorytree&gt;&lt;/nowiki&gt; on a wiki page, will show the contents of '''category Foo''' as a dynamic tree on that page.<br />
<br />
<br />
From https://www.mediawiki.org/wiki/Extension:CategoryTree#Usage :<br />
* let's try a all mode on Encyclopatys &lt;nowiki&gt;&lt;categorytree mode=&quot;all&quot; depth=&quot;20&quot; showcount&quot;on&quot; hideprefix=&quot;never&quot;&gt;Encyclopatys&lt;/categorytree&gt;&lt;/nowiki&gt;:<br />
&lt;categorytree style=&quot;margin-left: 30px;&quot; mode=&quot;all&quot; depth=&quot;20&quot; showcount&quot;on&quot; hideprefix=&quot;never&quot;&gt;Encyclopatys&lt;/categorytree&gt;<br />
* a parent mode &lt;nowiki&gt;&lt;categorytree mode=&quot;parents&quot; depth=&quot;20&quot; showcount&quot;on&quot; hideprefix=&quot;never&quot;&gt;Mysteries&lt;/categorytree&gt;&lt;/nowiki&gt;:<br />
&lt;categorytree style=&quot;margin-left: 30px;&quot; mode=&quot;parents&quot; depth=&quot;20&quot; showcount&quot;on&quot; hideprefix=&quot;never&quot;&gt;Mysteries&lt;/categorytree&gt;<br />
* let's try an other &lt;nowiki&gt;&lt;categorytree namespaces=&quot;talk&quot; style=&quot;margin-left: 30px;&quot; mode=&quot;pages&quot; depth=&quot;20&quot; &gt;Encyclopatys&lt;/categorytree&gt;&lt;/nowiki&gt; plus categories:<br />
&lt;categorytree style=&quot;margin-left: 30px;&quot; mode=&quot;pages&quot; depth=&quot;20&quot; namespaces=&quot;talk<br />
Category&quot;&gt;Encyclopatys&lt;/categorytree&gt;<br />
<br />
<br />
* With mode=parents we can see all parents of a category :) But how from EN wiki get the FR/EN values ? (tried fr:CategoryName and :fr:CategoryName)<br />
* depth default is 1. 0 will give roots categories<br />
* hideroot: set this to &quot;on&quot; to hide the &quot;root&quot; node of the tree (ex: &lt;nowiki&gt;hideroot=on&lt;/nowiki&gt;)<br />
* The &lt;nowiki&gt;{{#categorytree:Foo|hideroot|mode=pages}}&lt;/nowiki&gt; parser function, same but with other syntax. Using the parser function syntax has the advantage that it allows you to use [https://www.mediawiki.org/wiki/Help:Magic_words magic words] (such &lt;nowiki&gt;{{#categorytree:{{PAGENAME}}}}&lt;/nowiki&gt;), templates (&lt;nowiki&gt;{{#categorytree:{{root category}}}}&lt;/nowiki&gt;) and template parameters when specifying the category to show.<br />
<br />
=== Other links ===<br />
*[[Wiki Technical Guide/Special Pages]]<br />
* [[Wiki Technical Guide/API]]<br />
<br />
Other usefull links<br />
* https://regex101.com/<br />
* https://www.mediawiki.org/wiki/Manual%3APywikibot and [[User:Amosys/Pywiki]] (for tests)<br />
<br />
<br />
<br />
-----------------------------------------------------------------------------------------------<br />
&lt;references/&gt;<br />
{{clear}}{{Last version link}}<br />
&lt;noinclude&gt;{{Portal|Wikipatys|}}&lt;/noinclude&gt;<br />
[[Category:Wikipatys]][[Category:Encyclopatys]][[Category:Help]]</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Talk:Wiki_Technical_Guide&diff=30534Talk:Wiki Technical Guide2019-06-30T15:36:01Z<p>Maupas: /* Preventing discussion by indicating the link? */</p>
<hr />
<div>==New(?) templates==<br />
I created [[Template:OK]] ({{OK}}) and [[Template:KO]] ({{KO}}), but I am wondering if those don't already exist with an other name. If they do, please let me know. [[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 00:33, 9 June 2019 (CEST)<br />
<br />
== Easy to discriminate? ==<br />
<br />
{{quotation||This facilitates discriminated responses in their consideration, implementation, etc.}}<br />
Really? It sounds like: &quot;This (Writing 50 titles instead of 1 title for 50 topics) make it easy to discriminate responses in consideration, implementation, etc.&quot;&lt;br&gt;Better: &quot;This prevent discriminated responses in their consideration, implementation, etc.&quot; Or what should there be said?&lt;br&gt;--[[:de:User:Heernis|Heernis]] ([[:de:Benutzer_Diskussion:Heernis|talks]]) 30. June 2019 - 14:22<br />
:Of the french text written by Zorroagh I understood that the one who want to modify, (or ask/answer questions about, or translate) some topic will find and work on this topic more easily if it is a short one. Hence my &quot;faithful&quot; translation of &quot;''Cela facilite les réponses discriminées dans leur prise en compte, leur réalisation, etc.''&quot;<br />
:But I agree that this point of view is questionable (after all, sections are not so difficult to reach and work on) and suspects the main reason for such a recommendation (systematical splitting of articles) is the difficulties encountered in implementation of wikis in WebIG.<br />
:More, your question raise the point of translation. In fact, as I'am not a native EN speaker, the present EN Wiki Technical Guide need to be checked by somebody who is AND understands FR enough (you know that's how we work in Translation Team). I don't know if we have among ourselves wikis contributors such a person but I think we could at least add a status reading &quot;Proofreading requested&quot; in the TIP template. What do you think?--[[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 17:16, 30 June 2019 (CEST)<br />
<br />
== Preventing discussion by indicating the link? ==<br />
<br />
{{Quotation||Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion.}} This sound weird. Should be rewritten. (Think more simple ;-) )&lt;br&gt;--[[:de:User:Heernis|Heernis]] ([[:de:Benutzer_Diskussion:Heernis|talks]]) 30. June 2019 - 14:35<br />
:I replaced the &quot;weird&quot; sentence as follows:<br />
:“''So, please warn the ones you think concerned by the discussion by adding the link to the discussion in their own discussion user page.''” Feel free to improve it, tough!--[[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 17:33, 30 June 2019 (CEST)</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Talk:Wiki_Technical_Guide&diff=30533Talk:Wiki Technical Guide2019-06-30T15:34:33Z<p>Maupas: /* Easy to discriminate? */</p>
<hr />
<div>==New(?) templates==<br />
I created [[Template:OK]] ({{OK}}) and [[Template:KO]] ({{KO}}), but I am wondering if those don't already exist with an other name. If they do, please let me know. [[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 00:33, 9 June 2019 (CEST)<br />
<br />
== Easy to discriminate? ==<br />
<br />
{{quotation||This facilitates discriminated responses in their consideration, implementation, etc.}}<br />
Really? It sounds like: &quot;This (Writing 50 titles instead of 1 title for 50 topics) make it easy to discriminate responses in consideration, implementation, etc.&quot;&lt;br&gt;Better: &quot;This prevent discriminated responses in their consideration, implementation, etc.&quot; Or what should there be said?&lt;br&gt;--[[:de:User:Heernis|Heernis]] ([[:de:Benutzer_Diskussion:Heernis|talks]]) 30. June 2019 - 14:22<br />
:Of the french text written by Zorroagh I understood that the one who want to modify, (or ask/answer questions about, or translate) some topic will find and work on this topic more easily if it is a short one. Hence my &quot;faithful&quot; translation of &quot;''Cela facilite les réponses discriminées dans leur prise en compte, leur réalisation, etc.''&quot;<br />
:But I agree that this point of view is questionable (after all, sections are not so difficult to reach and work on) and suspects the main reason for such a recommendation (systematical splitting of articles) is the difficulties encountered in implementation of wikis in WebIG.<br />
:More, your question raise the point of translation. In fact, as I'am not a native EN speaker, the present EN Wiki Technical Guide need to be checked by somebody who is AND understands FR enough (you know that's how we work in Translation Team). I don't know if we have among ourselves wikis contributors such a person but I think we could at least add a status reading &quot;Proofreading requested&quot; in the TIP template. What do you think?--[[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 17:16, 30 June 2019 (CEST)<br />
<br />
== Preventing discussion by indicating the link? ==<br />
<br />
{{Quotation||Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion.}} This sound weird. Should be rewritten. (Think more simple ;-) )&lt;br&gt;--[[:de:User:Heernis|Heernis]] ([[:de:Benutzer_Diskussion:Heernis|talks]]) 30. June 2019 - 14:35<br />
:I replaced the &quot;weird&quot; sentence as follows:<br />
:“''So, please warn the ones you think concerned by the discussion by adding the link to the discussion in their own discussion user page.''”<br />
:Feel free to improve it, tough!<br />
:[[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 17:33, 30 June 2019 (CEST)</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Talk:Wiki_Technical_Guide&diff=30532Talk:Wiki Technical Guide2019-06-30T15:33:28Z<p>Maupas: </p>
<hr />
<div>==New(?) templates==<br />
I created [[Template:OK]] ({{OK}}) and [[Template:KO]] ({{KO}}), but I am wondering if those don't already exist with an other name. If they do, please let me know. [[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 00:33, 9 June 2019 (CEST)<br />
<br />
== Easy to discriminate? ==<br />
<br />
{{quotation||This facilitates discriminated responses in their consideration, implementation, etc.}}<br />
Really? It sounds like: &quot;This (Writing 50 titles instead of 1 title for 50 topics) make it easy to discriminate responses in consideration, implementation, etc.&quot;&lt;br&gt;Better: &quot;This prevent discriminated responses in their consideration, implementation, etc.&quot; Or what should there be said?&lt;br&gt;--[[:de:User:Heernis|Heernis]] ([[:de:Benutzer_Diskussion:Heernis|talks]]) 30. June 2019 - 14:22<br />
:Of the french text written by Zorroagh I understood that the one who want to modify, (or ask/answer questions about, or translate) some topic will find and work on this topic more easily if it is a short one. Hence my &quot;faithful&quot; translation of &quot;''Cela facilite les réponses discriminées dans leur prise en compte, leur réalisation, etc.''&quot;<br />
:But I agree that this point of view is questionable (after all, sections are not so difficult to reach and work on) and suspects the main reason for such a recommendation (systematical splitting of articles) is the difficulties encountered in implementation of wikis in WebIG.<br />
:More, your question raise the point of translation. In fact, as I'am not a native EN speaker, the present EN Wiki Technical Guide need to be checked by somebody who is AND understands FR enough (you know that's how we work in Translation Team). I don't know if we have among ourselves wikis contributors such a person but I think we could at least add a status reading &quot;Proofreading requested&quot; in the TIP template. What do you think?<br />
:[[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 17:16, 30 June 2019 (CEST)<br />
<br />
== Preventing discussion by indicating the link? ==<br />
<br />
{{Quotation||Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion.}} This sound weird. Should be rewritten. (Think more simple ;-) )&lt;br&gt;--[[:de:User:Heernis|Heernis]] ([[:de:Benutzer_Diskussion:Heernis|talks]]) 30. June 2019 - 14:35<br />
:I replaced the &quot;weird&quot; sentence as follows:<br />
:“''So, please warn the ones you think concerned by the discussion by adding the link to the discussion in their own discussion user page.''”<br />
:Feel free to improve it, tough!<br />
:[[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 17:33, 30 June 2019 (CEST)</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=30531Wiki Technical Guide2019-06-30T15:26:02Z<p>Maupas: </p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=4<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.''''' See [[Writing Guide]] for basic wiki knowledge.<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). So, please warn the ones you think concerned by the discussion by adding the link to the discussion in their own discussion user page. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Lore Validation Request}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''&lt;big&gt;Categories&lt;/big&gt;'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
&lt;div style=&quot;text-align:center;&quot;&gt;<br />
{{3DText|3D=outset|group=ranger|text=&lt;span style=&quot;font-size:large;font-variant: small-caps;font-weight: bold;&quot;&gt;'''''Portal …'''''&lt;/span&gt;}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''&lt;code&gt;&lt;nowiki&gt;There are for now {{Number of pages}} pages on …&lt;/nowiki&gt;&lt;/code&gt;'''<br />
&lt;/div&gt;<br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use &lt;code&gt;&lt;nowiki&gt;{{Number of pages}}&lt;/nowiki&gt;&lt;/code&gt; that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article &lt;big&gt;'''''[[Categorization]]'''''&lt;/big&gt;. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
<br />
[[File:Mindmap 6 wikis and image categories 2019-06-14.png|center|800px|alt=6 wikis, 6 category systems, all images in common|Six wikis, six category systems, all images in common]]<br />
&lt;div style=&quot;text-align:center;&quot;&gt;'''—• Six wikis, six category systems, all images in common •—'''&lt;/div&gt;<br />
<br />
=='''&lt;big&gt;Template&lt;/big&gt;'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
<br />
===Naming your Template===<br />
Some rules for naming templates.<br />
<br />
===All templates===<br />
&lt;big&gt;'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.&lt;/big&gt;<br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''&lt;big&gt;Portal&lt;/big&gt;'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|Associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''&lt;code&gt;&lt;nowiki&gt;{{:DOCNAME}}&lt;/nowiki&gt;&lt;/code&gt;''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class=&quot;wikitable centre&quot;<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || &lt;nowiki&gt;{{:Featured article/...}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/...}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the week || &lt;nowiki&gt;{{:Featured article/GBA/Week/{{CURRENTDOW}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the month || &lt;nowiki&gt;{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}&lt;/nowiki&gt;<br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Associated categories===<br />
====All relevant pages====<br />
To associate an article to a portal, just add at the bottom of the text of the said article a block of instructions of the following type:<br />
'''&lt;pre&gt;&lt;nowiki&gt;{{clear}}{{Last version link}}<br />
&lt;noinclude&gt;{{Portal|xxx}}<br />
[[Category:yyyy]]&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/pre&gt;'''<br />
where:<br />
*the “clear” ensures that the navigation bar to the portal is well above the last image;<br />
*the “last version link” allows you to time stamp the page and adds a discreet tab to find the origin of an inclusion;<br />
*the “noinclude” can be put in so as not to pollute the inclusion.<br />
====On the front page====<br />
Adding the navigation banner to the portal also places the article in “hidden” categories, categories that would not be shown to the reader because they are not relevant, but are indicated by a '''[+]''' located after the last displayed category. The random choice technique has been rejected by Mediawiki as too expensive. Currently, it is preferred a restricted choice (day of the week or month). This requires you to create one redirection at a time to the page you want to highlight. Thus, for example, the “Featured article/GBA/Day/3” page (3rd of the month or Wednesday) is redirected to “Primes Raider”.<br />
<br />
What if the article is too long to be included, or if only some of its sections are worthwhile?<br />
<br />
The wisest way is to signal the sections to be displayed or hidden in the future inclusion by marking them up in the source article.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/noinclude&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to exclude the parts they frame from the future inclusion.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to include only the parts they frame in the future inclusion.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to include only the parts they frame in the future inclusion, while masking them in the original article (to be handled carefully in a template).<br />
<br />
This latter markup is used, for example, to hide in the original article the “To be continued…” ('''&lt;code&gt;&lt;nowiki&gt;{{read more|&lt;&lt;the original article&gt;}}&lt;/nowiki&gt;&lt;/code&gt;''' displayed below) but displays it in the inclusion. {{read more|{{FULLPAGENAME}}}}<br />
<br />
=='''&lt;big&gt;Home page&lt;/big&gt;'''==<br />
Home pages are “specific” because they are those that appear by default when you log in to the wiki. These pages are not editable and can contain many HTML (and Java) tricks. This implies that only seasoned contributors can modify them on community consensus or communication imperatives.<br />
<br />
<br />
== Other advanced stuffs ==<br />
API, tips on Special commands...<br />
<br />
[[Wiki Technical Guide/Comparaison of lists ns and other]]<br />
=== namespaces ===<br />
Code used: &lt;nowiki&gt;{{Special:AllPages|namespace=1}}&lt;/nowiki&gt;<br />
<br />
Usually, the talk has ns+1. To be bief, no talk here (see more detailled pages) BUT un-usual.<br />
<br />
Commons to all:<br />
<br />
*Namespace 1 - Talk (in fr Discussion)<br />
*Namespace 2 - User (in fr, or Utilisateur or Utilisatrices)<br />
* Namespace 6 - File - Fichier <br />
*Namespace 8 - MediaWiki <br />
*Namespace 10 - Modèle - Template <br />
*Namespace 12 - Aide - Help<br />
*Namespace 14 - Category - Catégorie<br />
<br />
==== FR ns ====<br />
see [[:fr:Guide Technique du wiki/FR ns liste]] (commands are KO in here)<br />
<br />
*Namespace 4 - '''EncyclopAtys'''<br />
*Namespace 100 - Guilde<br />
*Namespace 106 - '''Portail - Portal'''<br />
<br />
==== EN ns ====<br />
see [[Wiki Technical Guide/EN ns list]]<br />
<br />
But:<br />
*Namespace '''4 - Ryzom Wiki''' and 5 Namespace 5 - Ryzom Wiki talk<br />
*Namespace '''104 - Event'''<br />
<br />
==== DE ns ====<br />
[[:de:Technischer Wiki-Leitfaden/DE ns list]]<br />
<br />
Looks like the EN, but no Event namespace, less pages and talk<br />
<br />
==== Atys Common ns ====<br />
See [https://atys.wiki.ryzom.com/wiki/User:Heernis/Common_ns_list Common ns list on atys common]<br />
<br />
As the DE/EN wikis: User (ns 2), File (ns 6), Template 10, Help (ns 12) 3p, Category (ns 14)<br />
<br />
* Namespace 4 - '''Ryzom Commons (ns 4)'''<br />
<br />
=== Wiki codes about categories ===<br />
* on common, Heernis used &lt;nowiki&gt;&lt;categorytree mode=&quot;all&quot; depth=&quot;20&quot; showcount&quot;on&quot; hideprefix=&quot;never&quot;&gt;Wikipatys&lt;/categorytree&gt;&lt;/nowiki&gt; to get result: Wikipatys, Deutsch, English, Graphic Charter, Hidden categories<br />
* The code &lt;nowiki&gt;&lt;categorytree&gt;Foo&lt;/categorytree&gt;&lt;/nowiki&gt; on a wiki page, will show the contents of '''category Foo''' as a dynamic tree on that page.<br />
<br />
<br />
From https://www.mediawiki.org/wiki/Extension:CategoryTree#Usage :<br />
* let's try a all mode on Encyclopatys &lt;nowiki&gt;&lt;categorytree mode=&quot;all&quot; depth=&quot;20&quot; showcount&quot;on&quot; hideprefix=&quot;never&quot;&gt;Encyclopatys&lt;/categorytree&gt;&lt;/nowiki&gt;:<br />
&lt;categorytree style=&quot;margin-left: 30px;&quot; mode=&quot;all&quot; depth=&quot;20&quot; showcount&quot;on&quot; hideprefix=&quot;never&quot;&gt;Encyclopatys&lt;/categorytree&gt;<br />
* a parent mode &lt;nowiki&gt;&lt;categorytree mode=&quot;parents&quot; depth=&quot;20&quot; showcount&quot;on&quot; hideprefix=&quot;never&quot;&gt;Mysteries&lt;/categorytree&gt;&lt;/nowiki&gt;:<br />
&lt;categorytree style=&quot;margin-left: 30px;&quot; mode=&quot;parents&quot; depth=&quot;20&quot; showcount&quot;on&quot; hideprefix=&quot;never&quot;&gt;Mysteries&lt;/categorytree&gt;<br />
* let's try an other &lt;nowiki&gt;&lt;categorytree namespaces=&quot;talk&quot; style=&quot;margin-left: 30px;&quot; mode=&quot;pages&quot; depth=&quot;20&quot; &gt;Encyclopatys&lt;/categorytree&gt;&lt;/nowiki&gt; plus categories:<br />
&lt;categorytree style=&quot;margin-left: 30px;&quot; mode=&quot;pages&quot; depth=&quot;20&quot; namespaces=&quot;talk<br />
Category&quot;&gt;Encyclopatys&lt;/categorytree&gt;<br />
<br />
<br />
* With mode=parents we can see all parents of a category :) But how from EN wiki get the FR/EN values ? (tried fr:CategoryName and :fr:CategoryName)<br />
* depth default is 1. 0 will give roots categories<br />
* hideroot: set this to &quot;on&quot; to hide the &quot;root&quot; node of the tree (ex: &lt;nowiki&gt;hideroot=on&lt;/nowiki&gt;)<br />
* The &lt;nowiki&gt;{{#categorytree:Foo|hideroot|mode=pages}}&lt;/nowiki&gt; parser function, same but with other syntax. Using the parser function syntax has the advantage that it allows you to use [https://www.mediawiki.org/wiki/Help:Magic_words magic words] (such &lt;nowiki&gt;{{#categorytree:{{PAGENAME}}}}&lt;/nowiki&gt;), templates (&lt;nowiki&gt;{{#categorytree:{{root category}}}}&lt;/nowiki&gt;) and template parameters when specifying the category to show.<br />
<br />
=== Other links ===<br />
*[[Wiki Technical Guide/Special Pages]]<br />
* [[Wiki Technical Guide/API]]<br />
<br />
Other usefull links<br />
* https://regex101.com/<br />
* https://www.mediawiki.org/wiki/Manual%3APywikibot and [[User:Amosys/Pywiki]] (for tests)<br />
<br />
<br />
<br />
-----------------------------------------------------------------------------------------------<br />
&lt;references/&gt;<br />
{{clear}}{{Last version link}}<br />
&lt;noinclude&gt;{{Portal|Wikipatys|}}&lt;/noinclude&gt;<br />
[[Category:Wikipatys]][[Category:Encyclopatys]][[Category:Help]]</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Talk:Wiki_Technical_Guide&diff=30530Talk:Wiki Technical Guide2019-06-30T15:16:36Z<p>Maupas: /* Easy to discriminate? */</p>
<hr />
<div>EN translation in progress.<br />
<br />
==New(?) templates==<br />
I created [[Template:OK]] ({{OK}}) and [[Template:KO]] ({{KO}}), but I am wondering if those don't already exist with an other name. If they do, please let me know. [[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 00:33, 9 June 2019 (CEST)<br />
<br />
== Easy to discriminate? ==<br />
<br />
{{quotation||This facilitates discriminated responses in their consideration, implementation, etc.}}<br />
Really? It sounds like: &quot;This (Writing 50 titles instead of 1 title for 50 topics) make it easy to discriminate responses in consideration, implementation, etc.&quot;&lt;br&gt;Better: &quot;This prevent discriminated responses in their consideration, implementation, etc.&quot; Or what should there be said?&lt;br&gt;--[[:de:User:Heernis|Heernis]] ([[:de:Benutzer_Diskussion:Heernis|talks]]) 30. June 2019 - 14:22<br />
:Of the french text written by Zorroagh I understood that the one who want to modify, (or ask/answer questions about, or translate) some topic will find and work on this topic more easily if it is a short one. Hence my &quot;faithful&quot; translation of &quot;''Cela facilite les réponses discriminées dans leur prise en compte, leur réalisation, etc.''&quot;<br />
:But I agree that this point of view is questionable (after all, sections are not so difficult to reach and work on) and suspects the main reason for such a recommendation (systematical splitting of articles) is the difficulties encountered in implementation of wikis in WebIG.<br />
:More, your question raise the point of translation. In fact, as I'am not a native EN speaker, the present EN Wiki Technical Guide need to be checked by somebody who is AND understands FR enough (you know that's how we work in Translation Team). I don't know if we have among ourselves wikis contributors such a person but I think we could at least add a status reading &quot;Proofreading requested&quot; in the TIP template. What do you think?<br />
:[[User:Maupas|Maupas]] ([[User talk:Maupas|talk]]) 17:16, 30 June 2019 (CEST)<br />
<br />
== Preventing discussion by indicating the link? ==<br />
<br />
{{Quotation||Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion.}} This sound weird. Should be rewritten. (Think more simple ;-) )&lt;br&gt;--[[:de:User:Heernis|Heernis]] ([[:de:Benutzer_Diskussion:Heernis|talks]]) 30. June 2019 - 14:35</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29693Wiki Technical Guide2019-06-14T21:10:11Z<p>Maupas: </p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=4<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Lore Validation Request}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''&lt;big&gt;Categories&lt;/big&gt;'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
&lt;div style=&quot;text-align:center;&quot;&gt;<br />
{{3DText|3D=outset|group=ranger|text=&lt;span style=&quot;font-size:large;font-variant: small-caps;font-weight: bold;&quot;&gt;'''''Portal …'''''&lt;/span&gt;}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''&lt;code&gt;&lt;nowiki&gt;There are for now {{Number of pages}} pages on …&lt;/nowiki&gt;&lt;/code&gt;'''<br />
&lt;/div&gt;<br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use &lt;code&gt;&lt;nowiki&gt;{{Number of pages}}&lt;/nowiki&gt;&lt;/code&gt; that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article &lt;big&gt;'''''[[Categorization]]'''''&lt;/big&gt;. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
<br />
[[File:Mindmap 6 wikis and image categories 2019-06-14.png|center|800px|alt=6 wikis, 6 category systems, all images in common|Six wikis, six category systems, all images in common]]<br />
&lt;div style=&quot;text-align:center;&quot;&gt;'''—• Six wikis, six category systems, all images in common •—'''&lt;/div&gt;<br />
<br />
=='''&lt;big&gt;Template&lt;/big&gt;'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
===All templates===<br />
&lt;big&gt;'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.&lt;/big&gt;<br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''&lt;big&gt;Portal&lt;/big&gt;'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|Associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''&lt;code&gt;&lt;nowiki&gt;{{:DOCNAME}}&lt;/nowiki&gt;&lt;/code&gt;''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class=&quot;wikitable centre&quot;<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || &lt;nowiki&gt;{{:Featured article/...}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/...}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the week || &lt;nowiki&gt;{{:Featured article/GBA/Week/{{CURRENTDOW}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the month || &lt;nowiki&gt;{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}&lt;/nowiki&gt;<br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Associated categories===<br />
====All relevant pages====<br />
To associate an article to a portal, just add at the bottom of the text of the said article a block of instructions of the following type:<br />
'''&lt;pre&gt;&lt;nowiki&gt;{{clear}}{{Last version link}}<br />
&lt;noinclude&gt;{{Portal|xxx}}<br />
[[Category:yyyy]]&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/pre&gt;'''<br />
where:<br />
*the “clear” ensures that the navigation bar to the portal is well above the last image;<br />
*the “last version link” allows you to time stamp the page and adds a discreet tab to find the origin of an inclusion;<br />
*the “noinclude” can be put in so as not to pollute the inclusion.<br />
====On the front page====<br />
Adding the navigation banner to the portal also places the article in “hidden” categories, categories that would not be shown to the reader because they are not relevant, but are indicated by a '''[+]''' located after the last displayed category. The random choice technique has been rejected by Mediawiki as too expensive. Currently, it is preferred a restricted choice (day of the week or month). This requires you to create one redirection at a time to the page you want to highlight. Thus, for example, the “Featured article/GBA/Day/3” page (3rd of the month or Wednesday) is redirected to “Primes Raider”.<br />
<br />
What if the article is too long to be included, or if only some of its sections are worthwhile?<br />
<br />
The wisest way is to signal the sections to be displayed or hidden in the future inclusion by marking them up in the source article.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/noinclude&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to exclude the parts they frame from the future inclusion.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to include only the parts they frame in the future inclusion.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to include only the parts they frame in the future inclusion, while masking them in the original article (to be handled carefully in a template).<br />
<br />
This latter markup is used, for example, to hide in the original article the “To be continued…” ('''&lt;code&gt;&lt;nowiki&gt;{{read more|&lt;&lt;the original article&gt;}}&lt;/nowiki&gt;&lt;/code&gt;''' displayed below) but displays it in the inclusion. {{read more|{{FULLPAGENAME}}}}<br />
<br />
=='''&lt;big&gt;Home page&lt;/big&gt;'''==<br />
Home pages are “specific” because they are those that appear by default when you log in to the wiki. These pages are not editable and can contain many HTML (and Java) tricks. This implies that only seasoned contributors can modify them on community consensus or communication imperatives.<br />
<br />
&lt;references/&gt;<br />
{{clear}}{{Last version link}}<br />
&lt;noinclude&gt;{{Portal|Wikipatys|}}&lt;/noinclude&gt;<br />
[[Category:Wikipatys]][[Category:Encyclopatys]][[Category:Help]]</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29691Wiki Technical Guide2019-06-14T20:38:32Z<p>Maupas: /* The main categories of this wiki */</p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Lore Validation Request}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''&lt;big&gt;Categories&lt;/big&gt;'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
&lt;div style=&quot;text-align:center;&quot;&gt;<br />
{{3DText|3D=outset|group=ranger|text=&lt;span style=&quot;font-size:large;font-variant: small-caps;font-weight: bold;&quot;&gt;'''''Portal …'''''&lt;/span&gt;}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''&lt;code&gt;&lt;nowiki&gt;There are for now {{Number of pages}} pages on …&lt;/nowiki&gt;&lt;/code&gt;'''<br />
&lt;/div&gt;<br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use &lt;code&gt;&lt;nowiki&gt;{{Number of pages}}&lt;/nowiki&gt;&lt;/code&gt; that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article &lt;big&gt;'''''[[Categorization]]'''''&lt;/big&gt;. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
<br />
[[File:Mindmap 6 wikis and image categories 2019-06-14.png|center|800px|alt=6 wikis, 6 category systems, all images in common|Six wikis, six category systems, all images in common]]<br />
&lt;div style=&quot;text-align:center;&quot;&gt;'''—• Six wikis, six category systems, all images in common •—'''&lt;/div&gt;<br />
<br />
=='''&lt;big&gt;Template&lt;/big&gt;'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
===All templates===<br />
&lt;big&gt;'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.&lt;/big&gt;<br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''&lt;big&gt;Portal&lt;/big&gt;'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|Associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''&lt;code&gt;&lt;nowiki&gt;{{:DOCNAME}}&lt;/nowiki&gt;&lt;/code&gt;''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class=&quot;wikitable centre&quot;<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || &lt;nowiki&gt;{{:Featured article/...}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/...}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the week || &lt;nowiki&gt;{{:Featured article/GBA/Week/{{CURRENTDOW}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the month || &lt;nowiki&gt;{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}&lt;/nowiki&gt;<br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Associated categories===<br />
====All relevant pages====<br />
To associate an article to a portal, just add at the bottom of the text of the said article a block of instructions of the following type:<br />
'''&lt;pre&gt;&lt;nowiki&gt;{{clear}}{{Last version link}}<br />
&lt;noinclude&gt;{{Portal|xxx}}<br />
[[Category:yyyy]]&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/pre&gt;'''<br />
where:<br />
*the “clear” ensures that the navigation bar to the portal is well above the last image;<br />
*the “last version link” allows you to time stamp the page and adds a discreet tab to find the origin of an inclusion;<br />
*the “noinclude” can be put in so as not to pollute the inclusion.<br />
====On the front page====<br />
Adding the navigation banner to the portal also places the article in “hidden” categories, categories that would not be shown to the reader because they are not relevant, but are indicated by a '''[+]''' located after the last displayed category. The random choice technique has been rejected by Mediawiki as too expensive. Currently, it is preferred a restricted choice (day of the week or month). This requires you to create one redirection at a time to the page you want to highlight. Thus, for example, the “Featured article/GBA/Day/3” page (3rd of the month or Wednesday) is redirected to “Primes Raider”.<br />
<br />
What if the article is too long to be included, or if only some of its sections are worthwhile?<br />
<br />
The wisest way is to signal the sections to be displayed or hidden in the future inclusion by marking them up in the source article.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/noinclude&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to exclude the parts they frame from the future inclusion.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to include only the parts they frame in the future inclusion.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to include only the parts they frame in the future inclusion, while masking them in the original article (to be handled carefully in a template).<br />
<br />
This latter markup is used, for example, to hide in the original article the “To be continued…” ('''&lt;code&gt;&lt;nowiki&gt;{{read more|&lt;&lt;the original article&gt;}}&lt;/nowiki&gt;&lt;/code&gt;''' displayed below) but displays it in the inclusion. {{read more|{{FULLPAGENAME}}}}<br />
<br />
=='''&lt;big&gt;Home page&lt;/big&gt;'''==<br />
Home pages are “specific” because they are those that appear by default when you log in to the wiki. These pages are not editable and can contain many HTML (and Java) tricks. This implies that only seasoned contributors can modify them on community consensus or communication imperatives.<br />
<br />
&lt;references/&gt;<br />
{{clear}}{{Last version link}}<br />
&lt;noinclude&gt;{{Portal|Wikipatys|}}&lt;/noinclude&gt;<br />
[[Category:Wikipatys]][[Category:Encyclopatys]][[Category:Help]]</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29690Wiki Technical Guide2019-06-14T20:37:47Z<p>Maupas: /* The main categories of this wiki */</p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Lore Validation Request}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''&lt;big&gt;Categories&lt;/big&gt;'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
&lt;div style=&quot;text-align:center;&quot;&gt;<br />
{{3DText|3D=outset|group=ranger|text=&lt;span style=&quot;font-size:large;font-variant: small-caps;font-weight: bold;&quot;&gt;'''''Portal …'''''&lt;/span&gt;}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''&lt;code&gt;&lt;nowiki&gt;There are for now {{Number of pages}} pages on …&lt;/nowiki&gt;&lt;/code&gt;'''<br />
&lt;/div&gt;<br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use &lt;code&gt;&lt;nowiki&gt;{{Number of pages}}&lt;/nowiki&gt;&lt;/code&gt; that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article &lt;big&gt;'''''[[Categorization]]'''''&lt;/big&gt;. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
[[File:Mindmap 6 wikis and image categories 2019-06-14.png|center|800px|alt=6 wikis, 6 category systems, all images in common|Six wikis, six category systems, all images in common]]<br />
&lt;div style=&quot;text-align:center;&quot;&gt;'''—• Six wikis, six category systems, all images in common •—'''&lt;/div&gt;<br />
<br />
=='''&lt;big&gt;Template&lt;/big&gt;'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
===All templates===<br />
&lt;big&gt;'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.&lt;/big&gt;<br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''&lt;big&gt;Portal&lt;/big&gt;'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|Associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''&lt;code&gt;&lt;nowiki&gt;{{:DOCNAME}}&lt;/nowiki&gt;&lt;/code&gt;''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class=&quot;wikitable centre&quot;<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || &lt;nowiki&gt;{{:Featured article/...}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/...}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the week || &lt;nowiki&gt;{{:Featured article/GBA/Week/{{CURRENTDOW}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the month || &lt;nowiki&gt;{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}&lt;/nowiki&gt;<br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Associated categories===<br />
====All relevant pages====<br />
To associate an article to a portal, just add at the bottom of the text of the said article a block of instructions of the following type:<br />
'''&lt;pre&gt;&lt;nowiki&gt;{{clear}}{{Last version link}}<br />
&lt;noinclude&gt;{{Portal|xxx}}<br />
[[Category:yyyy]]&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/pre&gt;'''<br />
where:<br />
*the “clear” ensures that the navigation bar to the portal is well above the last image;<br />
*the “last version link” allows you to time stamp the page and adds a discreet tab to find the origin of an inclusion;<br />
*the “noinclude” can be put in so as not to pollute the inclusion.<br />
====On the front page====<br />
Adding the navigation banner to the portal also places the article in “hidden” categories, categories that would not be shown to the reader because they are not relevant, but are indicated by a '''[+]''' located after the last displayed category. The random choice technique has been rejected by Mediawiki as too expensive. Currently, it is preferred a restricted choice (day of the week or month). This requires you to create one redirection at a time to the page you want to highlight. Thus, for example, the “Featured article/GBA/Day/3” page (3rd of the month or Wednesday) is redirected to “Primes Raider”.<br />
<br />
What if the article is too long to be included, or if only some of its sections are worthwhile?<br />
<br />
The wisest way is to signal the sections to be displayed or hidden in the future inclusion by marking them up in the source article.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/noinclude&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to exclude the parts they frame from the future inclusion.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to include only the parts they frame in the future inclusion.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to include only the parts they frame in the future inclusion, while masking them in the original article (to be handled carefully in a template).<br />
<br />
This latter markup is used, for example, to hide in the original article the “To be continued…” ('''&lt;code&gt;&lt;nowiki&gt;{{read more|&lt;&lt;the original article&gt;}}&lt;/nowiki&gt;&lt;/code&gt;''' displayed below) but displays it in the inclusion. {{read more|{{FULLPAGENAME}}}}<br />
<br />
=='''&lt;big&gt;Home page&lt;/big&gt;'''==<br />
Home pages are “specific” because they are those that appear by default when you log in to the wiki. These pages are not editable and can contain many HTML (and Java) tricks. This implies that only seasoned contributors can modify them on community consensus or communication imperatives.<br />
<br />
&lt;references/&gt;<br />
{{clear}}{{Last version link}}<br />
&lt;noinclude&gt;{{Portal|Wikipatys|}}&lt;/noinclude&gt;<br />
[[Category:Wikipatys]][[Category:Encyclopatys]][[Category:Help]]</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29689Wiki Technical Guide2019-06-14T20:36:26Z<p>Maupas: /* The main categories of this wiki */</p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Lore Validation Request}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''&lt;big&gt;Categories&lt;/big&gt;'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
&lt;div style=&quot;text-align:center;&quot;&gt;<br />
{{3DText|3D=outset|group=ranger|text=&lt;span style=&quot;font-size:large;font-variant: small-caps;font-weight: bold;&quot;&gt;'''''Portal …'''''&lt;/span&gt;}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''&lt;code&gt;&lt;nowiki&gt;There are for now {{Number of pages}} pages on …&lt;/nowiki&gt;&lt;/code&gt;'''<br />
&lt;/div&gt;<br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use &lt;code&gt;&lt;nowiki&gt;{{Number of pages}}&lt;/nowiki&gt;&lt;/code&gt; that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article &lt;big&gt;'''''[[Categorization]]'''''&lt;/big&gt;. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
[[File:Mindmap 6 wikis and image categories 2019-06-14.png|center|800px|alt=6 wikis, 6 category systems, all images in common|Six wikis, six category systems, all images in common]]<br />
&lt;div style=&quot;text-align:center;&quot;&gt;'''Six wikis, six category systems, all images in common'''&lt;/div&gt;<br />
<br />
=='''&lt;big&gt;Template&lt;/big&gt;'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
===All templates===<br />
&lt;big&gt;'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.&lt;/big&gt;<br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''&lt;big&gt;Portal&lt;/big&gt;'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|Associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''&lt;code&gt;&lt;nowiki&gt;{{:DOCNAME}}&lt;/nowiki&gt;&lt;/code&gt;''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class=&quot;wikitable centre&quot;<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || &lt;nowiki&gt;{{:Featured article/...}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/...}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the week || &lt;nowiki&gt;{{:Featured article/GBA/Week/{{CURRENTDOW}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the month || &lt;nowiki&gt;{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}&lt;/nowiki&gt;<br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Associated categories===<br />
====All relevant pages====<br />
To associate an article to a portal, just add at the bottom of the text of the said article a block of instructions of the following type:<br />
'''&lt;pre&gt;&lt;nowiki&gt;{{clear}}{{Last version link}}<br />
&lt;noinclude&gt;{{Portal|xxx}}<br />
[[Category:yyyy]]&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/pre&gt;'''<br />
where:<br />
*the “clear” ensures that the navigation bar to the portal is well above the last image;<br />
*the “last version link” allows you to time stamp the page and adds a discreet tab to find the origin of an inclusion;<br />
*the “noinclude” can be put in so as not to pollute the inclusion.<br />
====On the front page====<br />
Adding the navigation banner to the portal also places the article in “hidden” categories, categories that would not be shown to the reader because they are not relevant, but are indicated by a '''[+]''' located after the last displayed category. The random choice technique has been rejected by Mediawiki as too expensive. Currently, it is preferred a restricted choice (day of the week or month). This requires you to create one redirection at a time to the page you want to highlight. Thus, for example, the “Featured article/GBA/Day/3” page (3rd of the month or Wednesday) is redirected to “Primes Raider”.<br />
<br />
What if the article is too long to be included, or if only some of its sections are worthwhile?<br />
<br />
The wisest way is to signal the sections to be displayed or hidden in the future inclusion by marking them up in the source article.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/noinclude&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to exclude the parts they frame from the future inclusion.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to include only the parts they frame in the future inclusion.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to include only the parts they frame in the future inclusion, while masking them in the original article (to be handled carefully in a template).<br />
<br />
This latter markup is used, for example, to hide in the original article the “To be continued…” ('''&lt;code&gt;&lt;nowiki&gt;{{read more|&lt;&lt;the original article&gt;}}&lt;/nowiki&gt;&lt;/code&gt;''' displayed below) but displays it in the inclusion. {{read more|{{FULLPAGENAME}}}}<br />
<br />
=='''&lt;big&gt;Home page&lt;/big&gt;'''==<br />
Home pages are “specific” because they are those that appear by default when you log in to the wiki. These pages are not editable and can contain many HTML (and Java) tricks. This implies that only seasoned contributors can modify them on community consensus or communication imperatives.<br />
<br />
&lt;references/&gt;<br />
{{clear}}{{Last version link}}<br />
&lt;noinclude&gt;{{Portal|Wikipatys|}}&lt;/noinclude&gt;<br />
[[Category:Wikipatys]][[Category:Encyclopatys]][[Category:Help]]</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29688Wiki Technical Guide2019-06-14T20:15:18Z<p>Maupas: </p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Lore Validation Request}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''&lt;big&gt;Categories&lt;/big&gt;'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
&lt;div style=&quot;text-align:center;&quot;&gt;<br />
{{3DText|3D=outset|group=ranger|text=&lt;span style=&quot;font-size:large;font-variant: small-caps;font-weight: bold;&quot;&gt;'''''Portal …'''''&lt;/span&gt;}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''&lt;code&gt;&lt;nowiki&gt;There are for now {{Number of pages}} pages on …&lt;/nowiki&gt;&lt;/code&gt;'''<br />
&lt;/div&gt;<br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use &lt;code&gt;&lt;nowiki&gt;{{Number of pages}}&lt;/nowiki&gt;&lt;/code&gt; that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article &lt;big&gt;'''''[[Categorization]]'''''&lt;/big&gt;. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
[[File:Mindmap 6 wikis and image categories 2019-06-14.png|thumb|center|6 wikis, 6 category systems, all images in common]]<br />
<br />
=='''&lt;big&gt;Template&lt;/big&gt;'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
===All templates===<br />
&lt;big&gt;'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.&lt;/big&gt;<br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''&lt;big&gt;Portal&lt;/big&gt;'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|Associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''&lt;code&gt;&lt;nowiki&gt;{{:DOCNAME}}&lt;/nowiki&gt;&lt;/code&gt;''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class=&quot;wikitable centre&quot;<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || &lt;nowiki&gt;{{:Featured article/...}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/...}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the week || &lt;nowiki&gt;{{:Featured article/GBA/Week/{{CURRENTDOW}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the month || &lt;nowiki&gt;{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}&lt;/nowiki&gt;<br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Associated categories===<br />
====All relevant pages====<br />
To associate an article to a portal, just add at the bottom of the text of the said article a block of instructions of the following type:<br />
'''&lt;pre&gt;&lt;nowiki&gt;{{clear}}{{Last version link}}<br />
&lt;noinclude&gt;{{Portal|xxx}}<br />
[[Category:yyyy]]&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/pre&gt;'''<br />
where:<br />
*the “clear” ensures that the navigation bar to the portal is well above the last image;<br />
*the “last version link” allows you to time stamp the page and adds a discreet tab to find the origin of an inclusion;<br />
*the “noinclude” can be put in so as not to pollute the inclusion.<br />
====On the front page====<br />
Adding the navigation banner to the portal also places the article in “hidden” categories, categories that would not be shown to the reader because they are not relevant, but are indicated by a '''[+]''' located after the last displayed category. The random choice technique has been rejected by Mediawiki as too expensive. Currently, it is preferred a restricted choice (day of the week or month). This requires you to create one redirection at a time to the page you want to highlight. Thus, for example, the “Featured article/GBA/Day/3” page (3rd of the month or Wednesday) is redirected to “Primes Raider”.<br />
<br />
What if the article is too long to be included, or if only some of its sections are worthwhile?<br />
<br />
The wisest way is to signal the sections to be displayed or hidden in the future inclusion by marking them up in the source article.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/noinclude&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to exclude the parts they frame from the future inclusion.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to include only the parts they frame in the future inclusion.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to include only the parts they frame in the future inclusion, while masking them in the original article (to be handled carefully in a template).<br />
<br />
This latter markup is used, for example, to hide in the original article the “To be continued…” ('''&lt;code&gt;&lt;nowiki&gt;{{read more|&lt;&lt;the original article&gt;}}&lt;/nowiki&gt;&lt;/code&gt;''' displayed below) but displays it in the inclusion. {{read more|{{FULLPAGENAME}}}}<br />
<br />
=='''&lt;big&gt;Home page&lt;/big&gt;'''==<br />
Home pages are “specific” because they are those that appear by default when you log in to the wiki. These pages are not editable and can contain many HTML (and Java) tricks. This implies that only seasoned contributors can modify them on community consensus or communication imperatives.<br />
<br />
&lt;references/&gt;<br />
{{clear}}{{Last version link}}<br />
&lt;noinclude&gt;{{Portal|Wikipatys|}}&lt;/noinclude&gt;<br />
[[Category:Wikipatys]][[Category:Encyclopatys]][[Category:Help]]</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29687Wiki Technical Guide2019-06-14T20:01:54Z<p>Maupas: </p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Lore Validation Request}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''&lt;big&gt;Categories&lt;/big&gt;'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
&lt;div style=&quot;text-align:center;&quot;&gt;<br />
{{3DText|3D=outset|group=ranger|text=&lt;span style=&quot;font-size:large;font-variant: small-caps;font-weight: bold;&quot;&gt;'''''Portal …'''''&lt;/span&gt;}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''&lt;code&gt;&lt;nowiki&gt;There are for now {{Number of pages}} pages on …&lt;/nowiki&gt;&lt;/code&gt;'''<br />
&lt;/div&gt;<br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use &lt;code&gt;&lt;nowiki&gt;{{Number of pages}}&lt;/nowiki&gt;&lt;/code&gt; that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article &lt;big&gt;'''''[[Categorization]]'''''&lt;/big&gt;. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
[[File:Mindmap 6 wikis and image categories 2019-06-14.png|thumb|center|6 wikis, 6 category systems, all images in common]]<br />
<br />
=='''&lt;big&gt;Template&lt;/big&gt;'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
===All templates===<br />
&lt;big&gt;'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.&lt;/big&gt;<br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''&lt;big&gt;Portal&lt;/big&gt;'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|Associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''&lt;code&gt;&lt;nowiki&gt;{{:DOCNAME}}&lt;/nowiki&gt;&lt;/code&gt;''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class=&quot;wikitable centre&quot;<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || &lt;nowiki&gt;{{:Featured article/...}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/...}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the week || &lt;nowiki&gt;{{:Featured article/GBA/Week/{{CURRENTDOW}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the month || &lt;nowiki&gt;{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}&lt;/nowiki&gt;<br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Associated categories===<br />
====All relevant pages====<br />
To associate an article to a portal, just add at the bottom of the text of the said article a block of instructions of the following type:<br />
'''&lt;pre&gt;&lt;nowiki&gt;{{clear}}{{Last version link}}<br />
&lt;noinclude&gt;{{Portal|xxx}}<br />
[[Category:yyyy]]&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/pre&gt;'''<br />
where:<br />
*the “clear” ensures that the navigation bar to the portal is well above the last image;<br />
*the “last version link” allows you to time stamp the page and adds a discreet tab to find the origin of an inclusion;<br />
*the “noinclude” can be put in so as not to pollute the inclusion.<br />
====On the front page====<br />
Adding the navigation banner to the portal also places the article in “hidden” categories, categories that would not be shown to the reader because they are not relevant, but are indicated by a '''[+]''' located after the last displayed category. The random choice technique has been rejected by Mediawiki as too expensive. Currently, it is preferred a restricted choice (day of the week or month). This requires you to create one redirection at a time to the page you want to highlight. Thus, for example, the “Featured article/GBA/Day/3” page (3rd of the month or Wednesday) is redirected to “Primes Raider”.<br />
<br />
What if the article is too long to be included, or if only some of its sections are worthwhile?<br />
<br />
The wisest way is to signal the sections to be displayed or hidden in the future inclusion by marking them up in the source article.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/noinclude&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to exclude the parts they frame from the future inclusion.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to include only the parts they frame in the future inclusion.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to include only the parts they frame in the future inclusion, while masking them in the original article (to be handled carefully in a template).<br />
<br />
This latter markup is used, for example, to hide in the original article the “To be continued…” ('''&lt;code&gt;&lt;nowiki&gt;{{read more|&lt;&lt;the original article&gt;}}&lt;/nowiki&gt;&lt;/code&gt;''' displayed below) but displays it in the inclusion. {{read more|{{FULLPAGENAME}}}}<br />
<br />
=='''&lt;big&gt;Home page&lt;/big&gt;'''==<br />
Les pages d’accueil sont « spécifiques » car ce sont celles qui s'affichent par défaut lorsque l'on se connecte sur le wiki. Ces pages ne sont pas modifiables et peuvent contenir de nombreux artifices en HTML (et java). Cela implique que seuls des contributeurs avertis peuvent les modifier sur consensus de la communauté ou impératifs de communication.<br />
<br />
&lt;references/&gt;<br />
{{clear}}{{Last version link}}<br />
&lt;noinclude&gt;{{Portail|Wikipatys|}}&lt;/noinclude&gt;<br />
[[Catégorie:Wikipatys]][[Catégorie:Encyclopatys]][[Catégorie:Aide]]</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29686Wiki Technical Guide2019-06-14T19:59:57Z<p>Maupas: /* On the front page */</p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Lore Validation Request}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''&lt;big&gt;Categories&lt;/big&gt;'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
&lt;div style=&quot;text-align:center;&quot;&gt;<br />
{{3DText|3D=outset|group=ranger|text=&lt;span style=&quot;font-size:large;font-variant: small-caps;font-weight: bold;&quot;&gt;'''''Portal …'''''&lt;/span&gt;}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''&lt;code&gt;&lt;nowiki&gt;There are for now {{Number of pages}} pages on …&lt;/nowiki&gt;&lt;/code&gt;'''<br />
&lt;/div&gt;<br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use &lt;code&gt;&lt;nowiki&gt;{{Number of pages}}&lt;/nowiki&gt;&lt;/code&gt; that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article &lt;big&gt;'''''[[Categorization]]'''''&lt;/big&gt;. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
[[File:Mindmap 6 wikis and image categories 2019-06-14.png|thumb|center|6 wikis, 6 category systems, all images in common]]<br />
<br />
=='''&lt;big&gt;Template&lt;/big&gt;'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
===All templates===<br />
&lt;big&gt;'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.&lt;/big&gt;<br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''&lt;big&gt;Portal&lt;/big&gt;'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|Associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''&lt;code&gt;&lt;nowiki&gt;{{:DOCNAME}}&lt;/nowiki&gt;&lt;/code&gt;''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class=&quot;wikitable centre&quot;<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || &lt;nowiki&gt;{{:Featured article/...}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/...}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the week || &lt;nowiki&gt;{{:Featured article/GBA/Week/{{CURRENTDOW}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the month || &lt;nowiki&gt;{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}&lt;/nowiki&gt;<br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Associated categories===<br />
====All relevant pages====<br />
To associate an article to a portal, just add at the bottom of the text of the said article a block of instructions of the following type:<br />
'''&lt;pre&gt;&lt;nowiki&gt;{{clear}}{{Last version link}}<br />
&lt;noinclude&gt;{{Portal|xxx}}<br />
[[Category:yyyy]]&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/pre&gt;'''<br />
where:<br />
*the “clear” ensures that the navigation bar to the portal is well above the last image;<br />
*the “last version link” allows you to time stamp the page and adds a discreet tab to find the origin of an inclusion;<br />
*the “noinclude” can be put in so as not to pollute the inclusion.<br />
====On the front page====<br />
Adding the navigation banner to the portal also places the article in “hidden” categories, categories that would not be shown to the reader because they are not relevant, but are indicated by a '''[+]''' located after the last displayed category. The random choice technique has been rejected by Mediawiki as too expensive. Currently, it is preferred a restricted choice (day of the week or month). This requires you to create one redirection at a time to the page you want to highlight. Thus, for example, the “Featured article/GBA/Day/3” page (3rd of the month or Wednesday) is redirected to “Primes Raider”.<br />
<br />
What if the article is too long to be included, or if only some of its sections are worthwhile?<br />
<br />
The wisest way is to signal the sections to be displayed or hidden in the future inclusion by marking them up in the source article.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/noinclude&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to exclude the parts they frame from the future inclusion.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to include only the parts they frame in the future inclusion.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to include only the parts they frame in the future inclusion, while masking them in the original article (to be handled carefully in a template).<br />
<br />
This latter markup is used, for example, to hide in the original article the “To be continued…” ('''&lt;code&gt;&lt;nowiki&gt;{{read more|&lt;&lt;the original article&gt;}}&lt;/nowiki&gt;&lt;/code&gt;''' displayed below) but displays it in the inclusion. {{read more|{{FULLPAGENAME}}}}</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29684Wiki Technical Guide2019-06-14T19:55:10Z<p>Maupas: /* On the front page */</p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Lore Validation Request}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''&lt;big&gt;Categories&lt;/big&gt;'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
&lt;div style=&quot;text-align:center;&quot;&gt;<br />
{{3DText|3D=outset|group=ranger|text=&lt;span style=&quot;font-size:large;font-variant: small-caps;font-weight: bold;&quot;&gt;'''''Portal …'''''&lt;/span&gt;}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''&lt;code&gt;&lt;nowiki&gt;There are for now {{Number of pages}} pages on …&lt;/nowiki&gt;&lt;/code&gt;'''<br />
&lt;/div&gt;<br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use &lt;code&gt;&lt;nowiki&gt;{{Number of pages}}&lt;/nowiki&gt;&lt;/code&gt; that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article &lt;big&gt;'''''[[Categorization]]'''''&lt;/big&gt;. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
[[File:Mindmap 6 wikis and image categories 2019-06-14.png|thumb|center|6 wikis, 6 category systems, all images in common]]<br />
<br />
=='''&lt;big&gt;Template&lt;/big&gt;'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
===All templates===<br />
&lt;big&gt;'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.&lt;/big&gt;<br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''&lt;big&gt;Portal&lt;/big&gt;'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|Associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''&lt;code&gt;&lt;nowiki&gt;{{:DOCNAME}}&lt;/nowiki&gt;&lt;/code&gt;''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class=&quot;wikitable centre&quot;<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || &lt;nowiki&gt;{{:Featured article/...}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/...}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the week || &lt;nowiki&gt;{{:Featured article/GBA/Week/{{CURRENTDOW}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the month || &lt;nowiki&gt;{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}&lt;/nowiki&gt;<br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Associated categories===<br />
====All relevant pages====<br />
To associate an article to a portal, just add at the bottom of the text of the said article a block of instructions of the following type:<br />
'''&lt;pre&gt;&lt;nowiki&gt;{{clear}}{{Last version link}}<br />
&lt;noinclude&gt;{{Portal|xxx}}<br />
[[Category:yyyy]]&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/pre&gt;'''<br />
where:<br />
*the “clear” ensures that the navigation bar to the portal is well above the last image;<br />
*the “last version link” allows you to time stamp the page and adds a discreet tab to find the origin of an inclusion;<br />
*the “noinclude” can be put in so as not to pollute the inclusion.<br />
====On the front page====<br />
Adding the navigation banner to the portal also places the article in “hidden” categories, categories that would not be shown to the reader because they are not relevant, but are indicated by a '''[+]''' located after the last displayed category. The random choice technique has been rejected by Mediawiki as too expensive. Currently, it is preferred a restricted choice (day of the week or month). This requires you to create one redirection at a time to the page you want to highlight. Thus, for example, the “Featured article/GBA/Day/3” page (3rd of the month or Wednesday) is redirected to “Primes Raider”.<br />
<br />
What if the article is too long to be included, or if only some of its sections are worthwhile?<br />
<br />
The wisest way is to signal the sections to be displayed or hidden in the future inclusion by marking them up in the source article.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/noinclude&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to exclude the parts they frame from the future inclusion.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to include only the parts they frame in the future inclusion.<br />
*'''&lt;code&gt;&lt;nowiki&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' tags allow to include only the parts they frame in the future inclusion, while masking them in the original article (to be handled carefully in a template).<br />
<br />
This latter markup is used, for example, to hide in the original article the &quot;To be continued…&quot; ({{read more|&lt;&lt;the original article&gt;}} displayed below) but displays it in the inclusion. {{read more|{{FULLPAGENAME}}}}</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29645Wiki Technical Guide2019-06-13T21:57:18Z<p>Maupas: /* Portal */</p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Lore Validation Request}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''&lt;big&gt;Categories&lt;/big&gt;'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
&lt;div style=&quot;text-align:center;&quot;&gt;<br />
{{3DText|3D=outset|group=ranger|text=&lt;span style=&quot;font-size:large;font-variant: small-caps;font-weight: bold;&quot;&gt;'''''Portal …'''''&lt;/span&gt;}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''&lt;code&gt;&lt;nowiki&gt;There are for now {{Number of pages}} pages on …&lt;/nowiki&gt;&lt;/code&gt;'''<br />
&lt;/div&gt;<br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use &lt;code&gt;&lt;nowiki&gt;{{Number of pages}}&lt;/nowiki&gt;&lt;/code&gt; that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article &lt;big&gt;'''''[[Categorization]]'''''&lt;/big&gt;. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
=='''&lt;big&gt;Template&lt;/big&gt;'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
===All templates===<br />
&lt;big&gt;'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.&lt;/big&gt;<br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''&lt;big&gt;Portal&lt;/big&gt;'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|Associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''&lt;code&gt;&lt;nowiki&gt;{{:DOCNAME}}&lt;/nowiki&gt;&lt;/code&gt;''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class=&quot;wikitable centre&quot;<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || &lt;nowiki&gt;{{:Featured article/...}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/...}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the week || &lt;nowiki&gt;{{:Featured article/GBA/Week/{{CURRENTDOW}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the month || &lt;nowiki&gt;{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}&lt;/nowiki&gt;<br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Associated categories===<br />
====All relevant pages====<br />
To associate an article to a portal, just add at the bottom of the text of the said article a block of instructions of the following type:<br />
'''&lt;pre&gt;&lt;nowiki&gt;{{clear}}{{Last version link}}<br />
&lt;noinclude&gt;{{Portal|xxx}}<br />
[[Category:yyyy]]&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/pre&gt;'''<br />
where:<br />
*the “clear” ensures that the navigation bar to the portal is well above the last image;<br />
*the “last version link” allows you to time stamp the page and adds a discreet tab to find the origin of an inclusion;<br />
*the “noinclude” can be put in so as not to pollute the inclusion.<br />
====On the front page====<br />
Adding the navigation banner to the portal also places the article in “hidden” categories, categories that would not be shown to the reader because they are not relevant, but are indicated by a '''[+]''' located after the last displayed category. The random choice technique has been rejected by Mediawiki as too expensive. Currently, it is preferred a restricted choice (day of the week or month). This requires you to create one redirection at a time to the page you want to highlight. Thus, for example, the “Featured article/GBA/Day/3” page (3rd of the month or Wednesday) is redirected to “Primes Raider”.<br />
<br />
Que faire si l'article est trop long à inclure, ou si seulement certaines de ses parties sont intéressantes ?<br />
<br />
Le plus sage est d'indiquer les parties à afficher ou occulter dans la future inclusion en les balisant dans larticle original.<br />
*Les balises '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' et '''&lt;code&gt;&lt;nowiki&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' permettent d'exclure les parties qu'elles encadrent de la future inclusion.<br />
*Les balises '''&lt;code&gt;&lt;nowiki&gt;&lt;onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' et '''&lt;code&gt;&lt;nowiki&gt;&lt;/onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' permettent d'inclure les seules parties qu'elles encadrent dans la future inclusion.<br />
*Les balises '''&lt;code&gt;&lt;nowiki&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' et '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' permettent d'inclure les seules parties qu'elles encadrent dans la future inclusion, tout en les masquant dans l'article original (à manipuler prudemment dans un modèle).<br />
<br />
Ce dernier balisage est par exemple utilisé pour cacher dans l'article original le « À suivre… » ('''&lt;code&gt;&lt;nowiki&gt;{{read more|&lt;l'article original&gt;}}&lt;/nowiki&gt;&lt;/code&gt;''' affiché ci-dessous) mais l'affiche dans l'inclusion. {{read more|{{FULLPAGENAME}}}}</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29644Wiki Technical Guide2019-06-13T21:31:19Z<p>Maupas: /* Portal */</p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Lore Validation Request}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''&lt;big&gt;Categories&lt;/big&gt;'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
&lt;div style=&quot;text-align:center;&quot;&gt;<br />
{{3DText|3D=outset|group=ranger|text=&lt;span style=&quot;font-size:large;font-variant: small-caps;font-weight: bold;&quot;&gt;'''''Portal …'''''&lt;/span&gt;}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''&lt;code&gt;&lt;nowiki&gt;There are for now {{Number of pages}} pages on …&lt;/nowiki&gt;&lt;/code&gt;'''<br />
&lt;/div&gt;<br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use &lt;code&gt;&lt;nowiki&gt;{{Number of pages}}&lt;/nowiki&gt;&lt;/code&gt; that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article &lt;big&gt;'''''[[Categorization]]'''''&lt;/big&gt;. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
=='''&lt;big&gt;Template&lt;/big&gt;'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
===All templates===<br />
&lt;big&gt;'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.&lt;/big&gt;<br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''&lt;big&gt;Portal&lt;/big&gt;'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''&lt;code&gt;&lt;nowiki&gt;{{:DOCNAME}}&lt;/nowiki&gt;&lt;/code&gt;''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class=&quot;wikitable centre&quot;<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || &lt;nowiki&gt;{{:Featured article/...}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/...}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the week || &lt;nowiki&gt;{{:Featured article/GBA/Week/{{CURRENTDOW}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the month || &lt;nowiki&gt;{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}&lt;/nowiki&gt;<br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Les catégories associées===<br />
====Toutes les pages concernées====<br />
Pour associer un article à un portail, il suffit d'ajouter en bas du texte de l'article en question un bloc d'instructions du type suivant :<br />
'''&lt;pre&gt;&lt;nowiki&gt;{{clear}}{{Last version link}}<br />
&lt;noinclude&gt;{{Portal|xxx}}<br />
[[Category:yyy]]&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/pre&gt;'''<br />
où:<br />
*le « ''clear'' » permet d'assurer que la barre de navigation vers le portail est bien en-dessus de la dernière image ;<br />
*le « ''last version link'' » permet d'horodater la page et ajoute un onglet discret permettant de retrouver l'original d'une inclusion ;<br />
*le « ''noinclude'' » peut être mis pour ne pas polluer l'inclusion.<br />
====À la une====<br />
L'ajout de la bannière de navigation vers le portail range en outre l'article dans des catégories « cachées », catégories qui ne seront pas affichées pour le lecteur, car inopportunes, mais qui sont signalées par un '''[+]''' placé après la dernière catégorie affichée.<br />
La technique de choix au hasard a été condamnée par Mediawiki, car trop coûteuse. Actuellement, on lui préfère un choix bridé (jour de la semaine ou du mois). Cela impose de créer une à une les redirections vers les pages qu'on souhaite mettre en lumière. Ainsi, par exemple, la page &quot;Lumière sur/GBA/Jour/3&quot; (3 du mois ou le mercredi) est redirigée vers &quot;Primes Raider&quot;.<br />
<br />
Que faire si l'article est trop long à inclure, ou si seulement certaines de ses parties sont intéressantes ?<br />
<br />
Le plus sage est d'indiquer les parties à afficher ou occulter dans la future inclusion en les balisant dans larticle original.<br />
*Les balises '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' et '''&lt;code&gt;&lt;nowiki&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' permettent d'exclure les parties qu'elles encadrent de la future inclusion.<br />
*Les balises '''&lt;code&gt;&lt;nowiki&gt;&lt;onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' et '''&lt;code&gt;&lt;nowiki&gt;&lt;/onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' permettent d'inclure les seules parties qu'elles encadrent dans la future inclusion.<br />
*Les balises '''&lt;code&gt;&lt;nowiki&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' et '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' permettent d'inclure les seules parties qu'elles encadrent dans la future inclusion, tout en les masquant dans l'article original (à manipuler prudemment dans un modèle).<br />
<br />
Ce dernier balisage est par exemple utilisé pour cacher dans l'article original le « À suivre… » ('''&lt;code&gt;&lt;nowiki&gt;{{read more|&lt;l'article original&gt;}}&lt;/nowiki&gt;&lt;/code&gt;''' affiché ci-dessous) mais l'affiche dans l'inclusion. {{read more|{{FULLPAGENAME}}}}</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29643Wiki Technical Guide2019-06-13T21:30:33Z<p>Maupas: /* Bulletin board */</p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Lore Validation Request}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''&lt;big&gt;Categories&lt;/big&gt;'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
&lt;div style=&quot;text-align:center;&quot;&gt;<br />
{{3DText|3D=outset|group=ranger|text=&lt;span style=&quot;font-size:large;font-variant: small-caps;font-weight: bold;&quot;&gt;'''''Portal …'''''&lt;/span&gt;}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''&lt;code&gt;&lt;nowiki&gt;There are for now {{Number of pages}} pages on …&lt;/nowiki&gt;&lt;/code&gt;'''<br />
&lt;/div&gt;<br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use &lt;code&gt;&lt;nowiki&gt;{{Number of pages}}&lt;/nowiki&gt;&lt;/code&gt; that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article &lt;big&gt;'''''[[Categorization]]'''''&lt;/big&gt;. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
=='''&lt;big&gt;Template&lt;/big&gt;'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
===All templates===<br />
&lt;big&gt;'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.&lt;/big&gt;<br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''&lt;big&gt;Portal&lt;/big&gt;'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Showboard|Showboard]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''&lt;code&gt;&lt;nowiki&gt;{{:DOCNAME}}&lt;/nowiki&gt;&lt;/code&gt;''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class=&quot;wikitable centre&quot;<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || &lt;nowiki&gt;{{:Featured article/...}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/...}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the week || &lt;nowiki&gt;{{:Featured article/GBA/Week/{{CURRENTDOW}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the month || &lt;nowiki&gt;{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}&lt;/nowiki&gt;<br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Les catégories associées===<br />
====Toutes les pages concernées====<br />
Pour associer un article à un portail, il suffit d'ajouter en bas du texte de l'article en question un bloc d'instructions du type suivant :<br />
'''&lt;pre&gt;&lt;nowiki&gt;{{clear}}{{Last version link}}<br />
&lt;noinclude&gt;{{Portal|xxx}}<br />
[[Category:yyy]]&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/pre&gt;'''<br />
où:<br />
*le « ''clear'' » permet d'assurer que la barre de navigation vers le portail est bien en-dessus de la dernière image ;<br />
*le « ''last version link'' » permet d'horodater la page et ajoute un onglet discret permettant de retrouver l'original d'une inclusion ;<br />
*le « ''noinclude'' » peut être mis pour ne pas polluer l'inclusion.<br />
====À la une====<br />
L'ajout de la bannière de navigation vers le portail range en outre l'article dans des catégories « cachées », catégories qui ne seront pas affichées pour le lecteur, car inopportunes, mais qui sont signalées par un '''[+]''' placé après la dernière catégorie affichée.<br />
La technique de choix au hasard a été condamnée par Mediawiki, car trop coûteuse. Actuellement, on lui préfère un choix bridé (jour de la semaine ou du mois). Cela impose de créer une à une les redirections vers les pages qu'on souhaite mettre en lumière. Ainsi, par exemple, la page &quot;Lumière sur/GBA/Jour/3&quot; (3 du mois ou le mercredi) est redirigée vers &quot;Primes Raider&quot;.<br />
<br />
Que faire si l'article est trop long à inclure, ou si seulement certaines de ses parties sont intéressantes ?<br />
<br />
Le plus sage est d'indiquer les parties à afficher ou occulter dans la future inclusion en les balisant dans larticle original.<br />
*Les balises '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' et '''&lt;code&gt;&lt;nowiki&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' permettent d'exclure les parties qu'elles encadrent de la future inclusion.<br />
*Les balises '''&lt;code&gt;&lt;nowiki&gt;&lt;onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' et '''&lt;code&gt;&lt;nowiki&gt;&lt;/onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' permettent d'inclure les seules parties qu'elles encadrent dans la future inclusion.<br />
*Les balises '''&lt;code&gt;&lt;nowiki&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' et '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' permettent d'inclure les seules parties qu'elles encadrent dans la future inclusion, tout en les masquant dans l'article original (à manipuler prudemment dans un modèle).<br />
<br />
Ce dernier balisage est par exemple utilisé pour cacher dans l'article original le « À suivre… » ('''&lt;code&gt;&lt;nowiki&gt;{{read more|&lt;l'article original&gt;}}&lt;/nowiki&gt;&lt;/code&gt;''' affiché ci-dessous) mais l'affiche dans l'inclusion. {{read more|{{FULLPAGENAME}}}}</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29642Wiki Technical Guide2019-06-13T21:26:43Z<p>Maupas: /* Doc of the day */</p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Lore Validation Request}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''&lt;big&gt;Categories&lt;/big&gt;'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
&lt;div style=&quot;text-align:center;&quot;&gt;<br />
{{3DText|3D=outset|group=ranger|text=&lt;span style=&quot;font-size:large;font-variant: small-caps;font-weight: bold;&quot;&gt;'''''Portal …'''''&lt;/span&gt;}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''&lt;code&gt;&lt;nowiki&gt;There are for now {{Number of pages}} pages on …&lt;/nowiki&gt;&lt;/code&gt;'''<br />
&lt;/div&gt;<br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use &lt;code&gt;&lt;nowiki&gt;{{Number of pages}}&lt;/nowiki&gt;&lt;/code&gt; that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article &lt;big&gt;'''''[[Categorization]]'''''&lt;/big&gt;. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
=='''&lt;big&gt;Template&lt;/big&gt;'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
===All templates===<br />
&lt;big&gt;'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.&lt;/big&gt;<br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''&lt;big&gt;Portal&lt;/big&gt;'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Showboard|Showboard]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''&lt;code&gt;&lt;nowiki&gt;{{:DOCNAME}}&lt;/nowiki&gt;&lt;/code&gt;''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class=&quot;wikitable centre&quot;<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || &lt;nowiki&gt;{{:Featured article/...}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/...}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the week || &lt;nowiki&gt;{{:Featured article/GBA/Week/{{CURRENTDOW}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the month || &lt;nowiki&gt;{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}&lt;/nowiki&gt;<br />
|}<br />
<br />
===Panneau d'affichage===<br />
Les panneaux d'affichage contiennent des informations concernant aussi bien les lecteurs que le contributeur. Cela peut aller de la simple information aux urgences en passant par les « &quot;To do lists&quot; et les « Trucs et astuces ».<br />
<br />
===Les catégories associées===<br />
====Toutes les pages concernées====<br />
Pour associer un article à un portail, il suffit d'ajouter en bas du texte de l'article en question un bloc d'instructions du type suivant :<br />
'''&lt;pre&gt;&lt;nowiki&gt;{{clear}}{{Last version link}}<br />
&lt;noinclude&gt;{{Portal|xxx}}<br />
[[Category:yyy]]&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/pre&gt;'''<br />
où:<br />
*le « ''clear'' » permet d'assurer que la barre de navigation vers le portail est bien en-dessus de la dernière image ;<br />
*le « ''last version link'' » permet d'horodater la page et ajoute un onglet discret permettant de retrouver l'original d'une inclusion ;<br />
*le « ''noinclude'' » peut être mis pour ne pas polluer l'inclusion.<br />
====À la une====<br />
L'ajout de la bannière de navigation vers le portail range en outre l'article dans des catégories « cachées », catégories qui ne seront pas affichées pour le lecteur, car inopportunes, mais qui sont signalées par un '''[+]''' placé après la dernière catégorie affichée.<br />
La technique de choix au hasard a été condamnée par Mediawiki, car trop coûteuse. Actuellement, on lui préfère un choix bridé (jour de la semaine ou du mois). Cela impose de créer une à une les redirections vers les pages qu'on souhaite mettre en lumière. Ainsi, par exemple, la page &quot;Lumière sur/GBA/Jour/3&quot; (3 du mois ou le mercredi) est redirigée vers &quot;Primes Raider&quot;.<br />
<br />
Que faire si l'article est trop long à inclure, ou si seulement certaines de ses parties sont intéressantes ?<br />
<br />
Le plus sage est d'indiquer les parties à afficher ou occulter dans la future inclusion en les balisant dans larticle original.<br />
*Les balises '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' et '''&lt;code&gt;&lt;nowiki&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' permettent d'exclure les parties qu'elles encadrent de la future inclusion.<br />
*Les balises '''&lt;code&gt;&lt;nowiki&gt;&lt;onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' et '''&lt;code&gt;&lt;nowiki&gt;&lt;/onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' permettent d'inclure les seules parties qu'elles encadrent dans la future inclusion.<br />
*Les balises '''&lt;code&gt;&lt;nowiki&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' et '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' permettent d'inclure les seules parties qu'elles encadrent dans la future inclusion, tout en les masquant dans l'article original (à manipuler prudemment dans un modèle).<br />
<br />
Ce dernier balisage est par exemple utilisé pour cacher dans l'article original le « À suivre… » ('''&lt;code&gt;&lt;nowiki&gt;{{read more|&lt;l'article original&gt;}}&lt;/nowiki&gt;&lt;/code&gt;''' affiché ci-dessous) mais l'affiche dans l'inclusion. {{read more|{{FULLPAGENAME}}}}</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29641Wiki Technical Guide2019-06-13T21:23:34Z<p>Maupas: /* Doc of the day */</p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Lore Validation Request}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''&lt;big&gt;Categories&lt;/big&gt;'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
&lt;div style=&quot;text-align:center;&quot;&gt;<br />
{{3DText|3D=outset|group=ranger|text=&lt;span style=&quot;font-size:large;font-variant: small-caps;font-weight: bold;&quot;&gt;'''''Portal …'''''&lt;/span&gt;}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''&lt;code&gt;&lt;nowiki&gt;There are for now {{Number of pages}} pages on …&lt;/nowiki&gt;&lt;/code&gt;'''<br />
&lt;/div&gt;<br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use &lt;code&gt;&lt;nowiki&gt;{{Number of pages}}&lt;/nowiki&gt;&lt;/code&gt; that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article &lt;big&gt;'''''[[Categorization]]'''''&lt;/big&gt;. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
=='''&lt;big&gt;Template&lt;/big&gt;'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
===All templates===<br />
&lt;big&gt;'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.&lt;/big&gt;<br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''&lt;big&gt;Portal&lt;/big&gt;'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Showboard|Showboard]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''&lt;code&gt;&lt;nowiki&gt;{{:DOCNAME}}&lt;/nowiki&gt;&lt;/code&gt;''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class=&quot;wikitable centre&quot;<br />
! A different document included || ENGLISH || FRANÇAIS <br />
|-<br />
| When necessary || &lt;nowiki&gt;{{:Featured article/...}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Spotlight on/...}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the week || &lt;nowiki&gt;{{:Featured article/GBA/Week/{{CURRENTDOW}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Spotlight on/.../Jour/{{CURRENTDOW}}}}&lt;/nowiki&gt;<br />
|-<br />
| Every day of the month || &lt;nowiki&gt;{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Spotlight on/.../Mois/{{CURRENTDAY2}}}}&lt;/nowiki&gt;<br />
|}<br />
<br />
===Panneau d'affichage===<br />
Les panneaux d'affichage contiennent des informations concernant aussi bien les lecteurs que le contributeur. Cela peut aller de la simple information aux urgences en passant par les « &quot;To do lists&quot; et les « Trucs et astuces ».<br />
<br />
===Les catégories associées===<br />
====Toutes les pages concernées====<br />
Pour associer un article à un portail, il suffit d'ajouter en bas du texte de l'article en question un bloc d'instructions du type suivant :<br />
'''&lt;pre&gt;&lt;nowiki&gt;{{clear}}{{Last version link}}<br />
&lt;noinclude&gt;{{Portal|xxx}}<br />
[[Category:yyy]]&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/pre&gt;'''<br />
où:<br />
*le « ''clear'' » permet d'assurer que la barre de navigation vers le portail est bien en-dessus de la dernière image ;<br />
*le « ''last version link'' » permet d'horodater la page et ajoute un onglet discret permettant de retrouver l'original d'une inclusion ;<br />
*le « ''noinclude'' » peut être mis pour ne pas polluer l'inclusion.<br />
====À la une====<br />
L'ajout de la bannière de navigation vers le portail range en outre l'article dans des catégories « cachées », catégories qui ne seront pas affichées pour le lecteur, car inopportunes, mais qui sont signalées par un '''[+]''' placé après la dernière catégorie affichée.<br />
La technique de choix au hasard a été condamnée par Mediawiki, car trop coûteuse. Actuellement, on lui préfère un choix bridé (jour de la semaine ou du mois). Cela impose de créer une à une les redirections vers les pages qu'on souhaite mettre en lumière. Ainsi, par exemple, la page &quot;Lumière sur/GBA/Jour/3&quot; (3 du mois ou le mercredi) est redirigée vers &quot;Primes Raider&quot;.<br />
<br />
Que faire si l'article est trop long à inclure, ou si seulement certaines de ses parties sont intéressantes ?<br />
<br />
Le plus sage est d'indiquer les parties à afficher ou occulter dans la future inclusion en les balisant dans larticle original.<br />
*Les balises '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' et '''&lt;code&gt;&lt;nowiki&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' permettent d'exclure les parties qu'elles encadrent de la future inclusion.<br />
*Les balises '''&lt;code&gt;&lt;nowiki&gt;&lt;onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' et '''&lt;code&gt;&lt;nowiki&gt;&lt;/onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' permettent d'inclure les seules parties qu'elles encadrent dans la future inclusion.<br />
*Les balises '''&lt;code&gt;&lt;nowiki&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' et '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' permettent d'inclure les seules parties qu'elles encadrent dans la future inclusion, tout en les masquant dans l'article original (à manipuler prudemment dans un modèle).<br />
<br />
Ce dernier balisage est par exemple utilisé pour cacher dans l'article original le « À suivre… » ('''&lt;code&gt;&lt;nowiki&gt;{{read more|&lt;l'article original&gt;}}&lt;/nowiki&gt;&lt;/code&gt;''' affiché ci-dessous) mais l'affiche dans l'inclusion. {{read more|{{FULLPAGENAME}}}}</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29640Wiki Technical Guide2019-06-13T21:17:00Z<p>Maupas: /* Portal */</p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Lore Validation Request}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''&lt;big&gt;Categories&lt;/big&gt;'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
&lt;div style=&quot;text-align:center;&quot;&gt;<br />
{{3DText|3D=outset|group=ranger|text=&lt;span style=&quot;font-size:large;font-variant: small-caps;font-weight: bold;&quot;&gt;'''''Portal …'''''&lt;/span&gt;}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''&lt;code&gt;&lt;nowiki&gt;There are for now {{Number of pages}} pages on …&lt;/nowiki&gt;&lt;/code&gt;'''<br />
&lt;/div&gt;<br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use &lt;code&gt;&lt;nowiki&gt;{{Number of pages}}&lt;/nowiki&gt;&lt;/code&gt; that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article &lt;big&gt;'''''[[Categorization]]'''''&lt;/big&gt;. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
=='''&lt;big&gt;Template&lt;/big&gt;'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
===All templates===<br />
&lt;big&gt;'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.&lt;/big&gt;<br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''&lt;big&gt;Portal&lt;/big&gt;'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Showboard|Showboard]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''&lt;code&gt;&lt;nowiki&gt;{{:DOCNAME}}&lt;/nowiki&gt;&lt;/code&gt;''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
Il est parfois agréable d'avoir une documentation qui donne un aperçu des thèmes présentés réunis sous le portail.<br />
Cela peut se faire comme suit : <br />
{| class=&quot;wikitable centre&quot;<br />
! Un document différent inclus || ENGLISH || FRANÇAIS <br />
|-<br />
| Quand nécessaire || &lt;nowiki&gt;{{:Featured article/...}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/...}}&lt;/nowiki&gt;<br />
|-<br />
| Chaque jour de la semaine || &lt;nowiki&gt;{{:Featured article/GBA/Week/{{CURRENTDOW}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}&lt;/nowiki&gt;<br />
|-<br />
| Chaque jour du mois || &lt;nowiki&gt;{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}&lt;/nowiki&gt;<br />
|}<br />
<br />
===Panneau d'affichage===<br />
Les panneaux d'affichage contiennent des informations concernant aussi bien les lecteurs que le contributeur. Cela peut aller de la simple information aux urgences en passant par les « &quot;To do lists&quot; et les « Trucs et astuces ».<br />
<br />
===Les catégories associées===<br />
====Toutes les pages concernées====<br />
Pour associer un article à un portail, il suffit d'ajouter en bas du texte de l'article en question un bloc d'instructions du type suivant :<br />
'''&lt;pre&gt;&lt;nowiki&gt;{{clear}}{{Last version link}}<br />
&lt;noinclude&gt;{{Portal|xxx}}<br />
[[Category:yyy]]&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/pre&gt;'''<br />
où:<br />
*le « ''clear'' » permet d'assurer que la barre de navigation vers le portail est bien en-dessus de la dernière image ;<br />
*le « ''last version link'' » permet d'horodater la page et ajoute un onglet discret permettant de retrouver l'original d'une inclusion ;<br />
*le « ''noinclude'' » peut être mis pour ne pas polluer l'inclusion.<br />
====À la une====<br />
L'ajout de la bannière de navigation vers le portail range en outre l'article dans des catégories « cachées », catégories qui ne seront pas affichées pour le lecteur, car inopportunes, mais qui sont signalées par un '''[+]''' placé après la dernière catégorie affichée.<br />
La technique de choix au hasard a été condamnée par Mediawiki, car trop coûteuse. Actuellement, on lui préfère un choix bridé (jour de la semaine ou du mois). Cela impose de créer une à une les redirections vers les pages qu'on souhaite mettre en lumière. Ainsi, par exemple, la page &quot;Lumière sur/GBA/Jour/3&quot; (3 du mois ou le mercredi) est redirigée vers &quot;Primes Raider&quot;.<br />
<br />
Que faire si l'article est trop long à inclure, ou si seulement certaines de ses parties sont intéressantes ?<br />
<br />
Le plus sage est d'indiquer les parties à afficher ou occulter dans la future inclusion en les balisant dans larticle original.<br />
*Les balises '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' et '''&lt;code&gt;&lt;nowiki&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' permettent d'exclure les parties qu'elles encadrent de la future inclusion.<br />
*Les balises '''&lt;code&gt;&lt;nowiki&gt;&lt;onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' et '''&lt;code&gt;&lt;nowiki&gt;&lt;/onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' permettent d'inclure les seules parties qu'elles encadrent dans la future inclusion.<br />
*Les balises '''&lt;code&gt;&lt;nowiki&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' et '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' permettent d'inclure les seules parties qu'elles encadrent dans la future inclusion, tout en les masquant dans l'article original (à manipuler prudemment dans un modèle).<br />
<br />
Ce dernier balisage est par exemple utilisé pour cacher dans l'article original le « À suivre… » ('''&lt;code&gt;&lt;nowiki&gt;{{read more|&lt;l'article original&gt;}}&lt;/nowiki&gt;&lt;/code&gt;''' affiché ci-dessous) mais l'affiche dans l'inclusion. {{read more|{{FULLPAGENAME}}}}</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29639Wiki Technical Guide2019-06-13T21:15:16Z<p>Maupas: /* Portal */</p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Lore Validation Request}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''&lt;big&gt;Categories&lt;/big&gt;'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
&lt;div style=&quot;text-align:center;&quot;&gt;<br />
{{3DText|3D=outset|group=ranger|text=&lt;span style=&quot;font-size:large;font-variant: small-caps;font-weight: bold;&quot;&gt;'''''Portal …'''''&lt;/span&gt;}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''&lt;code&gt;&lt;nowiki&gt;There are for now {{Number of pages}} pages on …&lt;/nowiki&gt;&lt;/code&gt;'''<br />
&lt;/div&gt;<br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use &lt;code&gt;&lt;nowiki&gt;{{Number of pages}}&lt;/nowiki&gt;&lt;/code&gt; that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article &lt;big&gt;'''''[[Categorization]]'''''&lt;/big&gt;. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
=='''&lt;big&gt;Template&lt;/big&gt;'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
===All templates===<br />
&lt;big&gt;'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.&lt;/big&gt;<br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''&lt;big&gt;Portal&lt;/big&gt;'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Showboard|Showboard]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''&lt;code&gt;&lt;nowiki&gt;{{:NOMDOC}}&lt;/nowiki&gt;&lt;/code&gt;''' where NOMDOC=Name of the document to include.<br />
===Doc of the day===<br />
Il est parfois agréable d'avoir une documentation qui donne un aperçu des thèmes présentés réunis sous le portail.<br />
Cela peut se faire comme suit : <br />
{| class=&quot;wikitable centre&quot;<br />
! Un document différent inclus || ENGLISH || FRANÇAIS <br />
|-<br />
| Quand nécessaire || &lt;nowiki&gt;{{:Featured article/...}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/...}}&lt;/nowiki&gt;<br />
|-<br />
| Chaque jour de la semaine || &lt;nowiki&gt;{{:Featured article/GBA/Week/{{CURRENTDOW}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}&lt;/nowiki&gt;<br />
|-<br />
| Chaque jour du mois || &lt;nowiki&gt;{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}&lt;/nowiki&gt;<br />
|}<br />
<br />
===Panneau d'affichage===<br />
Les panneaux d'affichage contiennent des informations concernant aussi bien les lecteurs que le contributeur. Cela peut aller de la simple information aux urgences en passant par les « &quot;To do lists&quot; et les « Trucs et astuces ».<br />
<br />
===Les catégories associées===<br />
====Toutes les pages concernées====<br />
Pour associer un article à un portail, il suffit d'ajouter en bas du texte de l'article en question un bloc d'instructions du type suivant :<br />
'''&lt;pre&gt;&lt;nowiki&gt;{{clear}}{{Last version link}}<br />
&lt;noinclude&gt;{{Portal|xxx}}<br />
[[Category:yyy]]&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/pre&gt;'''<br />
où:<br />
*le « ''clear'' » permet d'assurer que la barre de navigation vers le portail est bien en-dessus de la dernière image ;<br />
*le « ''last version link'' » permet d'horodater la page et ajoute un onglet discret permettant de retrouver l'original d'une inclusion ;<br />
*le « ''noinclude'' » peut être mis pour ne pas polluer l'inclusion.<br />
====À la une====<br />
L'ajout de la bannière de navigation vers le portail range en outre l'article dans des catégories « cachées », catégories qui ne seront pas affichées pour le lecteur, car inopportunes, mais qui sont signalées par un '''[+]''' placé après la dernière catégorie affichée.<br />
La technique de choix au hasard a été condamnée par Mediawiki, car trop coûteuse. Actuellement, on lui préfère un choix bridé (jour de la semaine ou du mois). Cela impose de créer une à une les redirections vers les pages qu'on souhaite mettre en lumière. Ainsi, par exemple, la page &quot;Lumière sur/GBA/Jour/3&quot; (3 du mois ou le mercredi) est redirigée vers &quot;Primes Raider&quot;.<br />
<br />
Que faire si l'article est trop long à inclure, ou si seulement certaines de ses parties sont intéressantes ?<br />
<br />
Le plus sage est d'indiquer les parties à afficher ou occulter dans la future inclusion en les balisant dans larticle original.<br />
*Les balises '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' et '''&lt;code&gt;&lt;nowiki&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' permettent d'exclure les parties qu'elles encadrent de la future inclusion.<br />
*Les balises '''&lt;code&gt;&lt;nowiki&gt;&lt;onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' et '''&lt;code&gt;&lt;nowiki&gt;&lt;/onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' permettent d'inclure les seules parties qu'elles encadrent dans la future inclusion.<br />
*Les balises '''&lt;code&gt;&lt;nowiki&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' et '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' permettent d'inclure les seules parties qu'elles encadrent dans la future inclusion, tout en les masquant dans l'article original (à manipuler prudemment dans un modèle).<br />
<br />
Ce dernier balisage est par exemple utilisé pour cacher dans l'article original le « À suivre… » ('''&lt;code&gt;&lt;nowiki&gt;{{read more|&lt;l'article original&gt;}}&lt;/nowiki&gt;&lt;/code&gt;''' affiché ci-dessous) mais l'affiche dans l'inclusion. {{read more|{{FULLPAGENAME}}}}</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Template:Portal_bottom&diff=29638Template:Portal bottom2019-06-13T20:53:30Z<p>Maupas: </p>
<hr />
<div>{| style=&quot;margin-top:10px; background:none;width:100%;&quot;<br />
| style=&quot;width:100%; border:medium outset #{{ColorAtys|type=dark|group={{{1}}}}}; vertical-align:top; padding: 0px 10px 10px 0px; -moz-border-radius: 10px; -webkit-border-radius: 10px; border-radius:10px;background:#{{ColorAtys|type=light|group={{{1}}}}};color:#{{ColorAtys||type=fg|group={{{1}}}}}&quot; |<br />
{| cellpadding=&quot;2&quot; cellspacing=&quot;5&quot; style=&quot;width:100%; vertical-align:top; background:transparent;&quot;<br />
! {{ContentBox<br />
|title = {{3DText|group={{{1}}}|text=Main portals of the Ryzom Wiki}}<br />
|palette={{{1}}}<br />
|image = Spe labs.png<br />
|content = {{Ryzom portals}}<br />
}}<br />
|}<br />
|}</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29637Wiki Technical Guide2019-06-13T20:14:37Z<p>Maupas: </p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Lore Validation Request}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''&lt;big&gt;Categories&lt;/big&gt;'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
&lt;div style=&quot;text-align:center;&quot;&gt;<br />
{{3DText|3D=outset|group=ranger|text=&lt;span style=&quot;font-size:large;font-variant: small-caps;font-weight: bold;&quot;&gt;'''''Portal …'''''&lt;/span&gt;}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''&lt;code&gt;&lt;nowiki&gt;There are for now {{Number of pages}} pages on …&lt;/nowiki&gt;&lt;/code&gt;'''<br />
&lt;/div&gt;<br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use &lt;code&gt;&lt;nowiki&gt;{{Number of pages}}&lt;/nowiki&gt;&lt;/code&gt; that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article &lt;big&gt;'''''[[Categorization]]'''''&lt;/big&gt;. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
=='''&lt;big&gt;Template&lt;/big&gt;'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
===All templates===<br />
&lt;big&gt;'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.&lt;/big&gt;<br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''&lt;big&gt;Portal&lt;/big&gt;'''==<br />
Les portails dans notre wiki servent de pages d’accueil des différents grands centres d'intérêt du jeu. Ils sont répertoriés dans le cartouche '''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom}}&lt;/nowiki&gt;&lt;/code&gt;'''<br />
{{Portal bottom}}<br />
<br />
Tous les portails ont une structure similaire, mais leur apparence varie selon la complexité des données qu'ils présentent. En général un portail comporte, de haut en bas :<br />
*plusieurs onglets de sous-thèmes, l'accueil général positionnant la lecture le premier onglet ; dans certains cas, il peut y avoir une seconde rangée d'onglets ;<br />
*le nombre d'articles concernés et catégorisés (voir les [[#Les catégories associées|catégories associées]]) ;<br />
*un résumé ;<br />
*des informations (à gauche la [[#Doc du jour|« Doc du jour »]], à droite un [[#Panneau d'affichage|panneau d'affichage]]) ;<br />
*le cartouche récapitulant les principaux portails du Wiki de Ryzom ('''&lt;code&gt;&lt;nowiki&gt;{{Portal bottom|}}&lt;/nowiki&gt;&lt;/code&gt;''').<br />
<br />
Les portails n'ont pas été fabriqués en un jour et donc leur modèle s'est affiné au cours du temps. En général on essaye d'y inclure des documents en utilisant le modèle '''&lt;code&gt;&lt;nowiki&gt;{{:NOMDOC}}&lt;/nowiki&gt;&lt;/code&gt;''' où NOMDOC=Nom du document à inclure.<br />
===Doc du jour===<br />
Il est parfois agréable d'avoir une documentation qui donne un aperçu des thèmes présentés réunis sous le portail.<br />
Cela peut se faire comme suit : <br />
{| class=&quot;wikitable centre&quot;<br />
! Un document différent inclus || ENGLISH || FRANÇAIS <br />
|-<br />
| Quand nécessaire || &lt;nowiki&gt;{{:Featured article/...}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/...}}&lt;/nowiki&gt;<br />
|-<br />
| Chaque jour de la semaine || &lt;nowiki&gt;{{:Featured article/GBA/Week/{{CURRENTDOW}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}&lt;/nowiki&gt;<br />
|-<br />
| Chaque jour du mois || &lt;nowiki&gt;{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}&lt;/nowiki&gt; || &lt;nowiki&gt;{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}&lt;/nowiki&gt;<br />
|}<br />
<br />
===Panneau d'affichage===<br />
Les panneaux d'affichage contiennent des informations concernant aussi bien les lecteurs que le contributeur. Cela peut aller de la simple information aux urgences en passant par les « &quot;To do lists&quot; et les « Trucs et astuces ».<br />
<br />
===Les catégories associées===<br />
====Toutes les pages concernées====<br />
Pour associer un article à un portail, il suffit d'ajouter en bas du texte de l'article en question un bloc d'instructions du type suivant :<br />
'''&lt;pre&gt;&lt;nowiki&gt;{{clear}}{{Last version link}}<br />
&lt;noinclude&gt;{{Portal|xxx}}<br />
[[Category:yyy]]&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/pre&gt;'''<br />
où:<br />
*le « ''clear'' » permet d'assurer que la barre de navigation vers le portail est bien en-dessus de la dernière image ;<br />
*le « ''last version link'' » permet d'horodater la page et ajoute un onglet discret permettant de retrouver l'original d'une inclusion ;<br />
*le « ''noinclude'' » peut être mis pour ne pas polluer l'inclusion.<br />
====À la une====<br />
L'ajout de la bannière de navigation vers le portail range en outre l'article dans des catégories « cachées », catégories qui ne seront pas affichées pour le lecteur, car inopportunes, mais qui sont signalées par un '''[+]''' placé après la dernière catégorie affichée.<br />
La technique de choix au hasard a été condamnée par Mediawiki, car trop coûteuse. Actuellement, on lui préfère un choix bridé (jour de la semaine ou du mois). Cela impose de créer une à une les redirections vers les pages qu'on souhaite mettre en lumière. Ainsi, par exemple, la page &quot;Lumière sur/GBA/Jour/3&quot; (3 du mois ou le mercredi) est redirigée vers &quot;Primes Raider&quot;.<br />
<br />
Que faire si l'article est trop long à inclure, ou si seulement certaines de ses parties sont intéressantes ?<br />
<br />
Le plus sage est d'indiquer les parties à afficher ou occulter dans la future inclusion en les balisant dans larticle original.<br />
*Les balises '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' et '''&lt;code&gt;&lt;nowiki&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' permettent d'exclure les parties qu'elles encadrent de la future inclusion.<br />
*Les balises '''&lt;code&gt;&lt;nowiki&gt;&lt;onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' et '''&lt;code&gt;&lt;nowiki&gt;&lt;/onlyinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;''' permettent d'inclure les seules parties qu'elles encadrent dans la future inclusion.<br />
*Les balises '''&lt;code&gt;&lt;nowiki&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' et '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' permettent d'inclure les seules parties qu'elles encadrent dans la future inclusion, tout en les masquant dans l'article original (à manipuler prudemment dans un modèle).<br />
<br />
Ce dernier balisage est par exemple utilisé pour cacher dans l'article original le « À suivre… » ('''&lt;code&gt;&lt;nowiki&gt;{{read more|&lt;l'article original&gt;}}&lt;/nowiki&gt;&lt;/code&gt;''' affiché ci-dessous) mais l'affiche dans l'inclusion. {{read more|{{FULLPAGENAME}}}}</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29636Wiki Technical Guide2019-06-13T20:11:03Z<p>Maupas: /* All templates */</p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Lore Validation Request}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''&lt;big&gt;Categories&lt;/big&gt;'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
&lt;div style=&quot;text-align:center;&quot;&gt;<br />
{{3DText|3D=outset|group=ranger|text=&lt;span style=&quot;font-size:large;font-variant: small-caps;font-weight: bold;&quot;&gt;'''''Portal …'''''&lt;/span&gt;}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''&lt;code&gt;&lt;nowiki&gt;There are for now {{Number of pages}} pages on …&lt;/nowiki&gt;&lt;/code&gt;'''<br />
&lt;/div&gt;<br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use &lt;code&gt;&lt;nowiki&gt;{{Number of pages}}&lt;/nowiki&gt;&lt;/code&gt; that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article &lt;big&gt;'''''[[Categorization]]'''''&lt;/big&gt;. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
=='''&lt;big&gt;Template&lt;/big&gt;'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
===All templates===<br />
&lt;big&gt;'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.&lt;/big&gt;<br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Categorization&diff=29635Categorization2019-06-13T20:10:33Z<p>Maupas: /* Le Wikipatys */</p>
<hr />
<div>{{Trad<br />
|DE=Kategorisierung<br />
|EN=Categorization<br />
|ES=Categorización<br />
|FR=Catégorisation/Synoptique<br />
|RU=Категоризация<br />
}}<br />
<br />
Implemention of a [[Categorization/how to|categorisation that suits the 6 wikis]], knowing that &quot;Forge&quot; and &quot;Lore&quot; are integrated in the 5 &quot;linguistical&quot; wikis (and the &quot;common&quot; images as far as possible).<br />
There are for each wiki (DE, EN, ES, FR, RU) the same roots. These are:<br />
; Encyclopatys: the actual encyclopedic wiki, powered by all the players<br />
; Wikipatys: the wiki maintenance tools (template, technical doc, archive...), powered by all players with some advanced experience of Mediawiki and Wikipedia.<br />
; Forge: all the documentary and technical content enabling the development of Ryzom<br />
; Lore: all the Lore officially transmitted or approved by the Ryzom Lore Team<br />
<br />
[[File:RClogo211905.png|center|#pj-ryzom_wiki is the RC to talk about wiki|link=https://chat.ryzom.com/channel/pj-ryzom_wiki]]<br />
<br />
__TOC__<br />
<br />
==The basic principle == <br />
The main categories are associated with portals themselves pointed by navigation templates thru Portals, and answer questions:<br />
About the game:<br />
* '''What is the game Ryzom?''': the universe of Ryzom (&quot;'THE Lore&quot;'), and how to play it<br />
* '''What is the world I am in?''': Atys, the planet, its fauna, its flora...<br />
* '''Which races will I be able to embody?''': Fyros, Matis, Tryker or Zoraï.<br />
* '''What are the divine or assimilated powers of the planet, as well as the major groups that will direct my actions?''': Kamis, Karavan, Rangers, Marauders, Trytonists.<br />
Then comes the &quot;Encyclopedia&quot; co-managed by the '''players and animators''':<br />
* '''The Chronicles of Atys''' are the official texts used as reference to describe the past<br />
* '''The Great Library''', contains all the players' experience that does not necessarily fit into any of the previous subjects<br />
* '''The arcane''' contains the &quot;behind the scenes&quot; of the wiki.<br />
<br />
==Encyclopatys==<br />
With the exception of the &quot;Forge&quot; items, the goal is to attempt to categorize all items directly or indirectly into at least one category in the following table. It is not useful, and even harmful, to define and freeze all the categories of levels lower than those in the tables. Players and writers can create and manage the categories they want, as long as they link them to those written in the current tables and above all avoid creating &quot;root&quot; categories, otherwise the Sysop will integrate them where it suits best, the aim being to have some harmonization between the 5 language wikis.<br />
<br />
All missing bricks (&quot;category&quot; and &quot;template&quot;) must be written in English by default. This does not apply to old bricks already made. When two bricks co-exist, one in English the other in local, the wisest, in general, is to redirect the English brick on the local. The reason is that developers( including Sysop) are comfortable in English, but not necessarily the players / contributors.<br />
<br />
{|class=&quot;wikitable alternance sortable&quot; <br />
! DE !! EN !! ES !! FR !! RU !! Level<br />
|-<br />
! colspan=&quot;5&quot;|[[:Category:Encyclopatys]] || 1<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(180, 100%, 95%); background-image: linear-gradient(to left,white,hsl(180, 100%, 95%) 75%);&quot;<br />
| [[:Category:Hilfe]] || [[:Category:Help]] || [[:Category:Ayuda]] || [[:Category:Aide‎]] || [[:Category:Справка]] ||style=&quot;background-color:hsl(180, 100%, 90%); background-image: linear-gradient(to right,white,hsl(180, 100%, 90%));&quot; | 2<br />
|--style=&quot;background-color:#eef;&quot;<br />
| colspan=&quot;5&quot;| ||<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| colspan=&quot;5&quot;| ||<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(180, 100%, 95%); background-image: linear-gradient(to left,white,hsl(180, 100%, 95%) 75%);&quot;<br />
| [[:Category:Kategorisierung]] || [[:Category:Categorization]] || [[:Category:Categorización]] || [[:Category:Catégorisation]] || [[:Category:Категоризация]] ||style=&quot;background-color:hsl(180, 100%, 90%); background-image: linear-gradient(to right,white,hsl(180, 100%, 90%));&quot; | 2<br />
|--style=&quot;background-color:#eef;&quot;<br />
| colspan=&quot;5&quot;| ||<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| colspan=&quot;5&quot;| ||<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(180, 100%, 95%); background-image: linear-gradient(to left,white,hsl(180, 100%, 95%) 75%);&quot;<br />
| [[:Category:Portal]] || [[:Category:Portals]] || [[:Category:Portales]] || [[:Category:Portails‎]] || [[:Category:Портал]] ||style=&quot;background-color:hsl(180, 100%, 90%); background-image: linear-gradient(to right,white,hsl(180, 100%, 90%));&quot; | 2<br />
|--style=&quot;background-color:#eef;&quot;<br />
| colspan=&quot;5&quot;| ||<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| colspan=&quot;5&quot;| ||<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(180, 100%, 95%); background-image: linear-gradient(to left,white,hsl(180, 100%, 95%) 75%);&quot;<br />
| [[:Category:Ryzom, the game]] || [[:Category:Ryzom, the game]] || [[:Category:Ryzom, el juego]] || [[:Category:Ryzom, le jeu]] || [[:Category:Ryzom, the game]] ||style=&quot;background-color:hsl(180, 100%, 90%); background-image: linear-gradient(to right,white,hsl(180, 100%, 90%));&quot; | 2<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Ryzom]] || [[Template:Portal Ryzom]] || [[Template:Portal Ryzom]] || [[Template:Portail Ryzom]] || [[Template:Portal Ryzom]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Spiel]] || [[Portal:Game]] || [[Portal:Juego]] || [[Portail:Jeu]] || [[Portal:Гейм]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(120, 100%, 95%); background-image: linear-gradient(to left,hsl(180, 100%, 95%),hsl(120, 100%, 95%) 75%);&quot;<br />
| [[:Category:Gameplay]] || [[:Category:Gameplay]] || [[:Category:Gameplay]] || [[:Category:Gameplay]] || [[:Category:Gameplay]] ||style=&quot;background-color:hsl(120, 100%, 90%); background-image: linear-gradient(to right,hsl(180, 100%, 90%),hsl(120, 100%, 90%));&quot; | 3<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Gameplay]] || [[Template:Portal Gameplay]] || [[Template:Portal Gameplay]] || [[Template:Portail Gameplay]] || [[Template:Portal Gameplay]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Spiel/Gameplay]] || [[Portal:Game/Gameplay]] || [[Portal:Juego/Gameplay]] || [[Portail:Jeu/Gameplay]] || [[Portal:Гейм/Gameplay]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(60, 100%, 95%); background-image: linear-gradient(to left,hsl(120, 100%, 95%),hsl(60, 100%, 95%));&quot;<br />
| [[:Category:Kampf]] || [[:Category:Fight]] || [[:Category:Combate]] || [[:Category:Combat]] || [[:Category:Бороться]] ||style=&quot;background-color:hsl(60, 100%, 90%); background-image: linear-gradient(to right,hsl(120, 100%, 90%),hsl(60, 100%, 90%));&quot; | 4<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Kampf]] || [[Template:Portal Fight]] || [[Template:Portal Combate]] || [[Template:Portail Combat]] || [[Template:Portal Бороться]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Kampf]] || [[Portal:Fight]] || [[Portal:Combate]] || [[Portail:Combat]] || [[Portal:Бороться]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(60, 100%, 95%); background-image: linear-gradient(to left,hsl(120, 100%, 95%),hsl(60, 100%, 95%));&quot;<br />
| [[:Category:Magie]] || [[:Category:Magic]] || [[:Category:Magia]] || [[:Category:Magie]] || [[:Category:Мэги]] ||style=&quot;background-color:hsl(60, 100%, 90%); background-image: linear-gradient(to right,hsl(120, 100%, 90%),hsl(60, 100%, 90%));&quot; | 4<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Magie]] || [[Template:Portal Magic]] || [[Template:Portal Magia]] || [[Template:Portail Magie]] || [[Template:Portal Мэги]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Magie]] || [[Portal:Magic]] || [[Portal:Magia]] || [[Portail:Magie]] || [[Portal:Мэги]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(60, 100%, 95%); background-image: linear-gradient(to left,hsl(120, 100%, 95%),hsl(60, 100%, 95%));&quot;<br />
| [[:Category:Handwerks]] || [[:Category:Craft]] || [[:Category:Craft]] || [[:Category:Craft]] || [[:Category:Pемесленничество]] ||style=&quot;background-color:hsl(60, 100%, 90%); background-image: linear-gradient(to right,hsl(120, 100%, 90%),hsl(60, 100%, 90%));&quot; | 4<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Handwerks]] || [[Template:Portal Craft]] || [[Template:Portal Craft]] || [[Template:Portail Craft]] || [[Template:Portal Pемесленничество]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Handwerks]] || [[Portal:Craft]] || [[Portal:Craft]] || [[Portail:Craft]] || [[Portal:Pемесленничество]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(60, 100%, 95%); background-image: linear-gradient(to left,hsl(120, 100%, 95%),hsl(60, 100%, 95%));&quot;<br />
| [[:Category:Ernte]] || [[:Category:Harvest]] || [[:Category:Perforación]] || [[:Category:Forage]] || [[:Category:Бурение]] ||style=&quot;background-color:hsl(60, 100%, 90%); background-image: linear-gradient(to right,hsl(120, 100%, 90%),hsl(60, 100%, 90%));&quot; | 4<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Ernte]] || [[Template:Portal Harvest]] || [[Template:Portal Perforación]] || [[Template:Portail Forage]] || [[Template:Portal Бурение]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Ernte]] || [[Portal:Harvest]] || [[Portal:Cosecha]] || [[Portail:Forage]] || [[Portal:Бурение]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(120, 100%, 95%); background-image: linear-gradient(to left,hsl(180, 100%, 95%),hsl(120, 100%, 95%) 75%);&quot;<br />
| [[:Category:Roleplay]] || [[:Category:Roleplay]] || [[:Category:Roleplay]] || [[:Category:Roleplay]] || [[:Category:Roleplay]] ||style=&quot;background-color:hsl(120, 100%, 90%); background-image: linear-gradient(to right,hsl(180, 100%, 90%),hsl(120, 100%, 90%));&quot; | 3<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Roleplay]] || [[Template:Portal Roleplay]] || [[Template:Portal Roleplay]] || [[Template:Portail Roleplay]] || [[Template:Portal Roleplay]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Spiel/Roleplay]] || [[Portal:Game/Roleplay]] || [[Portal:Juego/Roleplay]] || [[Portail:Jeu/Roleplay]] || [[Portal:Гейм/Roleplay]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(120, 100%, 95%); background-image: linear-gradient(to left,hsl(180, 100%, 95%),hsl(120, 100%, 95%) 75%);&quot;<br />
| [[:Category:Community]] || [[:Category:Community]] || [[:Category:Comunidad]] || [[:Category:Communauté]] || [[:Category:Сообщество]] ||style=&quot;background-color:hsl(120, 100%, 90%); background-image: linear-gradient(to right,hsl(180, 100%, 90%),hsl(120, 100%, 90%));&quot; | 3<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Community]] || [[Template:Portal Community]] || [[Template:Portal Community]] || [[Template:Portail Community]] || [[Template:Portal Community]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Spiel/Community]] || [[Portal:Game/Community]] || [[Portal:Juego/Comunidad]] || [[Portail:Jeu/Communauté]] || [[Portal:Гейм/Сообщество]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(120, 100%, 95%); background-image: linear-gradient(to left,hsl(180, 100%, 95%),hsl(120, 100%, 95%) 75%);&quot;<br />
| [[:Category:Animation]] || [[:Category:Animation]] || [[:Category:Animación]] || [[:Category:Animation]] || [[:Category:Oдушевление]] ||style=&quot;background-color:hsl(120, 100%, 90%); background-image: linear-gradient(to right,hsl(180, 100%, 90%),hsl(120, 100%, 90%));&quot; | 3<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Animation]] || [[Template:Portal Animation]] || [[Template:Portal Animation]] || [[:fr:Template:Portail Animation]] || [[Template:Portal Animation]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Spiel/Animation]] || [[Portal:Game/Animation]] || [[Portal:Juego/Animación]] || [[:fr:Portail:Jeu/Animation]] || [[Portal:Гейм/Oдушевление]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(180, 100%, 95%); background-image: linear-gradient(to left,white,hsl(180, 100%, 95%) 75%);&quot;<br />
| [[:Category:Atys‎]] || [[:Category:Atys‎]] || [[:Category:Atys‎]] || [[:Category:Atys‎]] || [[:Category:Atys‎]] ||style=&quot;background-color:hsl(180, 100%, 90%); background-image: linear-gradient(to right,white,hsl(180, 100%, 90%));&quot; | 2<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Atys‎]] || [[Template:Portal Atys‎]] || [[Template:Portal Atys‎]] || [[Template:Portail Atys‎]] || [[Template:Portal Atys‎]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Atys‎]] || [[Portal:Atys‎]] || [[Portal:Atys‎]] || [[Portail:Atys‎]] || [[Portal:Atys‎]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(60, 100%, 95%); background-image: linear-gradient(to left,hsl(120, 100%, 95%),hsl(60, 100%, 95%));&quot;<br />
| [[:Category:Planeten]] || [[:Category:Planet]] || [[:Category:Planeta]] || [[:Category:Planète]] || [[:Category:Планета]] ||style=&quot;background-color:hsl(60, 100%, 90%); background-image: linear-gradient(to right,hsl(120, 100%, 90%),hsl(60, 100%, 90%));&quot; | 4<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Planeten]] || [[Template:Portal Planet]] || [[Template:Portal Planeta]] || [[Template:Portail Planète]] || [[Template:Portal Планета]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Planeten]] || [[Portal:Planet]] || [[Portal:Planeta]] || [[Portail:Planète]] || [[Portal:Планета]] || P<br />
<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(120, 100%, 95%); background-image: linear-gradient(to left,hsl(180, 100%, 95%),hsl(120, 100%, 95%) 75%);&quot;<br />
| [[:Category:Gebietsansässige]] || [[:Category:Inhabitants]] || [[:Category:Habitantes]] || [[:Category:Habitants]] || [[:Category:Inhabitants]] ||style=&quot;background-color:hsl(120, 100%, 90%); background-image: linear-gradient(to right,hsl(180, 100%, 90%),hsl(120, 100%, 90%));&quot; | 3<br />
|--style=&quot;background-color:#eef;&quot;<br />
| •[[Template:Portal Atys‎]]&lt;br/&gt;•[[Template:Portal Die Große Bibliothek‎]] || •[[Template:Portal Atys‎]]&lt;br/&gt;•[[Template:Portal The Great Library‎]] || •[[Template:Portal Atys‎]]&lt;br/&gt;•[[Template:Portal La Gran Biblioteca]] || •[[Template:Portail Atys‎]]&lt;br/&gt;•[[Template:Portail La Grande Bibliothèque]] || •[[Template:Portal Atys‎]]&lt;br/&gt;•[[Template:Portal Великая Библиотека]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| colspan=&quot;5&quot;| ||<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(60, 100%, 95%); background-image: linear-gradient(to left,hsl(120, 100%, 95%),hsl(60, 100%, 95%));&quot;<br />
| [[:Category:Flora]] || [[:Category:Flora]] || [[:Category:Flora]] || [[:Category:Flore]] || [[:Category:Flora]] ||style=&quot;background-color:hsl(60, 100%, 90%); background-image: linear-gradient(to right,hsl(120, 100%, 90%),hsl(60, 100%, 90%));&quot; | 4<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Flora]] || [[Template:Portal Flora]] || [[Template:Portal Flora]] || [[Template:Portail Flore]] || [[Template:Portal Flora]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Flora]] || [[Portal:Flora]] || [[Portal:Flora]] || [[Portail:Flore]] || [[Portal:Flora]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(60, 100%, 95%); background-image: linear-gradient(to left,hsl(120, 100%, 95%),hsl(60, 100%, 95%));&quot;<br />
| [[:Category:Fauna]] || [[:Category:Fauna]] || [[:Category:Fauna]] || [[:Category:Faune]] || [[:Category:Fauna]] ||style=&quot;background-color:hsl(60, 100%, 90%); background-image: linear-gradient(to right,hsl(120, 100%, 90%),hsl(60, 100%, 90%));&quot; | 4<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Fauna]] || [[Template:Portal Fauna]] || [[Template:Portal Fauna]] || [[Template:Portail Faune]] || [[Template:Portal Fauna]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Fauna]] || [[Portal:Fauna]] || [[Portal:Fauna]] || [[Portail:Faune]] || [[Portal:Fauna]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(60, 100%, 95%); background-image: linear-gradient(to left,hsl(120, 100%, 95%),hsl(60, 100%, 95%));&quot;<br />
| '''[[:de:Die Völker von Atys]]''' || '''[[:en:Category:Peoples of Atys]]''' || '''[[:es:Category:Pueblos de Atys]]''' || '''[[:fr:Category:Les Peuples d'Atys]]''' || '''[[:ru:Category:Народы Atys]]''' ||style=&quot;background-color:hsl(60, 100%, 90%); background-image: linear-gradient(to right,hsl(120, 100%, 90%),hsl(60, 100%, 90%));&quot; | 4<br />
|--style=&quot;background-color:#eef;&quot;<br />
| colspan=&quot;5&quot;| ||<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| colspan=&quot;5&quot;| ||<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(30, 100%, 95%); background-image: linear-gradient(to left,hsl(60, 100%, 95%),hsl(30, 100%, 95%));&quot;<br />
| [[:Category:Primitiven]] || [[:Category:Primitives]] || [[:Category:Primitivos]] || [[:Category:Primitifs]] || [[:Category:Primitives]] ||style=&quot;background-color:hsl(30, 100%, 90%); background-image: linear-gradient(to right,hsl(60, 100%, 90%),hsl(30, 100%, 90%));&quot; | 5<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Primitiven]] || [[Template:Portal Primitives]] || [[Template:Portal Primitivos]] || [[Template:Portail Primitif]] || [[Template:Portal Primitives]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Atys/Primitiven]] || [[Portal:Atys/Primitives]] || [[Portal:Atys/Primitivos]] || [[Portail:Atys/Primitifs]] || [[Portal:Atys/Примитивные]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(30, 100%, 95%); background-image: linear-gradient(to left,hsl(60, 100%, 95%),hsl(30, 100%, 95%));&quot;<br />
| [[:Category:Stämme]] || [[:Category:Tribes]] || [[:Category:Tribus]] || [[:Category:Tribus]] || [[:Category:Tribes]] ||style=&quot;background-color:hsl(30, 100%, 90%); background-image: linear-gradient(to right,hsl(60, 100%, 90%),hsl(30, 100%, 90%));&quot; | 5<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Stamm]] || [[Template:Portal Tribe]] || [[Template:Portal Tribu]] || [[Template:Portail Tribu]] || [[Template:Portal Племя‎]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Atys/Stämme]] || [[Portal:Atys/Tribes]] || [[Portal:Atys/Tribus]] || [[Portail:Atys/Tribus]] || [[Portal:Atys/Племен]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(30, 100%, 95%); background-image: linear-gradient(to left,hsl(60, 100%, 95%),hsl(30, 100%, 95%));&quot;<br />
| [[:Category:Zivilisation]] || [[:Category:Civilization]] || [[:Category:Civilizaciones de Atys]] || [[:Category:Civilisations Homines]] || [[:Category:Цивилизация]] ||style=&quot;background-color:hsl(30, 100%, 90%); background-image: linear-gradient(to right,hsl(60, 100%, 90%),hsl(30, 100%, 90%));&quot; | 5<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Zivilisation]] || [[Template:Portal Civilization]] || [[Template:Portal Civilización]] || [[Template:Portail Civilisation]] || [[Template:Portal Civilization]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Atys/Zivilisation]] || [[Portal:Atys/Civilization]] || [[Portal:Atys/Civilización]] || [[Portail:Civilisation]] || [[Portal:Atys/Цивилизация]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(0, 100%, 95%); background-image: linear-gradient(to left,hsl(30, 100%, 95%),hsl(0, 100%, 95%));&quot;<br />
| [[:Category:Fyros]] || [[:Category:Fyros]] || [[:Category:Fyros]] || [[:Category:Fyros]] || [[:Category:Fyros]] ||style=&quot;background-color:hsl(0, 100%, 90%); background-image: linear-gradient(to right,hsl(30, 100%, 90%),hsl(0, 100%, 90%));&quot; | 6<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Fyros]] || [[Template:Portal Fyros]] || [[Template:Portal Fyros]] || [[Template:Portail Fyros]] || [[Template:Portal Fyros]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Fyros]] || [[Portal:Fyros]] || [[Portal:Fyros]] || [[Portail:Fyros]] || [[Portal:Fyros]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(0, 100%, 95%); background-image: linear-gradient(to left,hsl(30, 100%, 95%),hsl(0, 100%, 95%));&quot;<br />
| [[:Category:Matis]] || [[:Category:Matis]] || [[:Category:Matis]] || [[:Category:Matis]] || [[:Category:Matis]] ||style=&quot;background-color:hsl(0, 100%, 90%); background-image: linear-gradient(to right,hsl(30, 100%, 90%),hsl(0, 100%, 90%));&quot; | 6<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Matis]] || [[Template:Portal Matis]] || [[Template:Portal Matis]] || [[Template:Portail Matis]] || [[Template:Portal Matis]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Matis]] || [[Portal:Matis]] || [[Portal:Matis]] || [[Portail:Matis]] || [[Portal:Matis]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(0, 100%, 95%); background-image: linear-gradient(to left,hsl(30, 100%, 95%),hsl(0, 100%, 95%));&quot;<br />
| [[:Category:Tryker]] || [[:Category:Tryker]] || [[:Category:Tryker]] || [[:Category:Tryker]] || [[:Category:Tryker]] ||style=&quot;background-color:hsl(0, 100%, 90%); background-image: linear-gradient(to right,hsl(30, 100%, 90%),hsl(0, 100%, 90%));&quot; | 6<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Tryker]] || [[Template:Portal Tryker]] || [[Template:Portal Tryker]] || [[Template:Portail Tryker]] || [[Template:Portal Tryker]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Tryker]] || [[Portal:Tryker]] || [[Portal:Tryker]] || [[Portail:Tryker]] || [[Portal:Tryker]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(0, 100%, 95%); background-image: linear-gradient(to left,hsl(30, 100%, 95%),hsl(0, 100%, 95%));&quot;<br />
| [[:Category:Zoraï]] || [[:Category:Zoraï]] || [[:Category:Zoraï]] || [[:Category:Zoraï]] || [[:Category:Zoraï]] ||style=&quot;background-color:hsl(0, 100%, 90%); background-image: linear-gradient(to right,hsl(30, 100%, 90%),hsl(0, 100%, 90%));&quot; | 6<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Zoraï]] || [[Template:Portal Zoraï]] || [[Template:Portal Zoraï]] || [[Template:Portail Zoraï]] || [[Template:Portal Zoraï]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Zoraï]] || [[Portal:Zoraï]] || [[Portal:Zoraï]] || [[Portail:Zoraï]] || [[Portal:Zoraï]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(0, 100%, 95%); background-image: linear-gradient(to left,hsl(30, 100%, 95%),hsl(0, 100%, 95%));&quot;<br />
| [[:Category:Rangers]] || [[:Category:Rangers]] || [[:Category:Rangers]] || [[:Category:Rangers]] || [[:Category:Rangers]] ||style=&quot;background-color:hsl(0, 100%, 90%); background-image: linear-gradient(to right,hsl(30, 100%, 90%),hsl(0, 100%, 90%));&quot; | 6<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Rangers]] || [[Template:Portal Rangers]] || [[Template:Portal Rangers]] || [[Template:Portail Rangers]] || [[Template:Portal Rangers]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Rangers]] || [[Portal:Rangers]] || [[Portal:Rangers]] || [[Portail:Rangers]] || [[Portal:Rangers]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(30, 100%, 95%); background-image: linear-gradient(to left,hsl(60, 100%, 95%),hsl(30, 100%, 95%));&quot;<br />
| [[:Category:Fraktionen]] || [[:Category:Factions]] || [[:Category:Factions]] || [[:Category:Factions]] || [[:Category:Factions]] ||style=&quot;background-color:hsl(30, 100%, 90%); background-image: linear-gradient(to right,hsl(60, 100%, 90%),hsl(30, 100%, 90%));&quot; | 5<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Factions]] || [[Template:Portal Factions]] || [[Template:Portal Factions]] || [[Template:Portail Factions]] || [[Template:Portal Factions]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Factions]] || [[Portal:Factions]] || [[Portal:Factions]] || [[Portail:Factions]] || [[Portal:Factions]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(30, 100%, 95%); background-image: linear-gradient(to left,hsl(60, 100%, 95%),hsl(30, 100%, 95%));&quot;<br />
| [[:Category:Religion]] || [[:Category:Religion]] || [[:Category:Religión]] || [[:Category:Religions]] || [[:Category:Религия]] ||style=&quot;background-color:hsl(30, 100%, 90%); background-image: linear-gradient(to right,hsl(60, 100%, 90%),hsl(30, 100%, 90%));&quot; | 5<br />
|--style=&quot;background-color:#eef;&quot;<br />
| •[[Template:Portal Factions]]&lt;br/&gt;•[[Template:Portal Gesellschaft]] || •[[Template:Portal Factions]]&lt;br/&gt;•[[Template:Portal Society]] || •[[Template:Portal Factions]]&lt;br/&gt;•[[Template:Portal Sociedad]] || •[[Template:Portail Factions]]&lt;br/&gt;•[[Template:Portail Société]] || •[[Template:Portal Factions]]&lt;br/&gt;•[[Template:Portal Общество]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| colspan=&quot;5&quot;| ||<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(0, 100%, 95%); background-image: linear-gradient(to left,hsl(30, 100%, 95%),hsl(0, 100%, 95%));&quot;<br />
| [[:Category:Kamis]] || [[:Category:Kamis]] || [[:Category:Kamis]] || [[:Category:Kamis]] || [[:Category:Kamis]] ||style=&quot;background-color:hsl(0, 100%, 90%); background-image: linear-gradient(to right,hsl(30, 100%, 90%),hsl(0, 100%, 90%));&quot; | 6<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Kami]] || [[Template:Portal Kami]] || [[Template:Portal Kami]] || [[Template:Portail Kami]] || [[Template:Portal Kami]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Kami]] || [[Portal:Kami]] || [[Portal:Kami]] || [[Portail:Kami]] || [[Portal:Kami]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(0, 100%, v%); background-image: linear-gradient(to left,hsl(30, 100%, 95%),hsl(0, 100%, 95%));&quot;<br />
| [[:Category:Karavan]] || [[:Category:Karavan]] || [[:Category:Karavan]] || [[:Category:Karavan]] || [[:Category:Karavan]] ||style=&quot;background-color:hsl(0, 100%, 90%); background-image: linear-gradient(to right,hsl(30, 100%, 90%),hsl(0, 100%, 90%));&quot; | 6<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Karavan]] || [[Template:Portal Karavan]] || [[Template:Portal Karavan]] || [[Template:Portail Karavan]] || [[Template:Portal Karavan]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Karavan]] || [[Portal:Karavan]] || [[Portal:Karavan]] || [[Portail:Karavan]] || [[Portal:Karavan]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(0, 100%, 95%); background-image: linear-gradient(to left,hsl(30, 100%, 95%),hsl(0, 100%, 95%));&quot;<br />
| [[:Category:Marodeuren]] || [[:Category:Marauders]] || [[:Category:Merodeadores]] || [[:Category:Maraudeurs]] || [[:Category:Marauders]] ||style=&quot;background-color:hsl(0, 100%, 90%); background-image: linear-gradient(to right,hsl(30, 100%, 90%),hsl(0, 100%, 90%));&quot; | 6<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Marodeuren]] || [[Template:Portal Marauders]] || [[Template:Portal Merodeadores]] || [[Template:Portail Maraudeurs]] || [[Template:Portal Marauder]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Marodeuren]] || [[Portal:Marauders]] || [[Portal:Merodeadores]] || [[Portail:Maraudeurs]] || [[Portal:Marauders]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(0, 100%, 95%); background-image: linear-gradient(to left,hsl(30, 100%, 95%),hsl(0, 100%, 95%));&quot;<br />
| [[:Category:Trytonisten]] || [[:Category:Trytonists]] || [[:Category:Trytonistas]] || [[:Category:Trytonistes]] || [[:Category:Тритонисты]] ||style=&quot;background-color:hsl(0, 100%, 90%); background-image: linear-gradient(to right,hsl(30, 100%, 90%),hsl(0, 100%, 90%));&quot; | 6<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Trytonisten]] || [[Template:Portal Trytonists]] || [[Template:Portal Trytonistas]] || [[Template:Portail Trytonistes]] || [[Template:Portal Тритонисты]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Trytonisten]] || [[Portal:Trytonists]] || [[Portal:Trytonistas]] || [[Portail:Tritonystes]] || [[Portal:Тритонисты]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(180, 100%, 95%); background-image: linear-gradient(to left,white,hsl(180, 100%, 95%) 75%);&quot;<br />
| [[:Category:Die Große Bibliothek]] || [[:Category:The Great Library]] || [[:Category:La Gran Biblioteca]] || [[:Category:La Grande Bibliothèque]] || [[:Category:Великая Библиотека]] ||style=&quot;background-color:hsl(180, 100%, 90%); background-image: linear-gradient(to right,white,hsl(180, 100%, 90%));&quot; | 2<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Die Große Bibliothek]] || [[Template:Portal The Great Library]] || [[Template:Portal La Gran Biblioteca]] || [[Template:Portail La Grande Bibliothèque]] || [[Template:Portal Великая Библиотека]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Die Große Bibliothek]] || [[Portal:The Great Library]] || [[Portal:La Gran Biblioteca]] || [[Portail:La Grande Bibliothèque]] || [[Portal:Великая Библиотека]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(120, 100%, 95%); background-image: linear-gradient(to left,hsl(180, 100%, 95%),hsl(120, 100%, 95%) 75%);&quot;<br />
| [[:Category:Wissenschaft und Technik]] || [[:Category:Science and technology‏‎]] || [[:Category:Ciencia y tecnología]] || [[:Category:Sciences et techniques]] || [[:Category:Наука и техника]] ||style=&quot;background-color:hsl(120, 100%, 90%); background-image: linear-gradient(to right,hsl(180, 100%, 90%),hsl(120, 100%, 90%));&quot; | 3<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Wissenschaften]] || [[Template:Portal Sciences]] || [[Template:Portal Ciencias]] || [[Template:Portail Sciences]] || [[Template:Portal Науки]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Die Große Bibliothek/Wissenschaft]] || [[Portal:The Great Library/Sciences]] || [[Portal:La Gran Biblioteca/Ciencias]] || [[Portail:La Grande Bibliothèque/Sciences]] || [[Portal:Великая Библиотека/Наука]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(120, 100%, 95%); background-image: linear-gradient(to left,hsl(180, 100%, 95%),hsl(120, 100%, 95%) 75%);&quot;<br />
| [[:Category:Literatur]] || [[:Category:Literature]] || [[:Category:Literatura]] || [[:Category:Littérature]] || [[:Category:Литература]] ||style=&quot;background-color:hsl(120, 100%, 90%); background-image: linear-gradient(to right,hsl(180, 100%, 90%),hsl(120, 100%, 90%));&quot; | 3<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Literatur]] || [[Template:Portal Literature]] || [[Template:Portal Literatura]] || [[Template:Portail Littérature]] || [[Template:Portal Литература]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Die Große Bibliothek/Literatur]] || [[Portal:The Great Library/Literature]] || [[Portal:La Gran Biblioteca/Literatura]] || [[Portail:La Grande Bibliothèque/Littérature]] || [[Portal:Великая Библиотека/Литература]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(120, 100%, 95%); background-image: linear-gradient(to left,hsl(180, 100%, 95%),hsl(120, 100%, 95%) 75%);&quot;<br />
| [[:Category:Gesellschaft]] || [[:Category:Society]] || [[:Category:Sociedad]] || [[:Category:Société]] || [[:Category:Общество]] ||style=&quot;background-color:hsl(120, 100%, 90%); background-image: linear-gradient(to right,hsl(180, 100%, 90%),hsl(120, 100%, 90%));&quot; | 3<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Gesellschaft]] || [[Template:Portal Society]] || [[Template:Portal Sociedad]] || [[Template:Portail Société]] || [[Template:Portal Общество]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Die Große Bibliothek/Gesellschaft]] || [[Portal:The Great Library/Society]] || [[Portal:La Gran Biblioteca/Sociedad]] || [[Portail:La Grande Bibliothèque/Société]] || [[Portal:Великая Библиотека/Общество]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(120, 100%, 95%); background-image: linear-gradient(to left,hsl(180, 100%, 95%),hsl(120, 100%, 95%) 75%);&quot;<br />
| [[:Category:Homins‎]] || [[:Category:Homins‎]] || [[:Category:Homins‎]] || [[:Category:Homins‎]] || [[:Category:Homins‎]] ||style=&quot;background-color:hsl(120, 100%, 90%); background-image: linear-gradient(to right,hsl(180, 100%, 90%),hsl(120, 100%, 90%));&quot; | 3<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Homins‎]] || [[Template:Portal Homins‎]] || [[Template:Portal Homins‎]] || [[Template:Portail Homins‎]] || [[Template:Portal Homins‎]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Die Große Bibliothek/Homins‎]] || [[Portal:The Great Library/Homins‎]] || [[Portal:La Gran Biblioteca/Homins‎]] || [[Portail:La Grande Bibliothèque/Homins‎]] || [[Portal:Великая Библиотека/Homins‎]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(120, 100%, 95%); background-image: linear-gradient(to left,hsl(180, 100%, 95%),hsl(120, 100%, 95%) 75%);&quot;<br />
| [[:Category:Geschichte]] || [[:Category:History]] || [[:Category:Historia]] || [[:Category:Histoire‎]] || [[:Category:История]] ||style=&quot;background-color:hsl(120, 100%, 90%); background-image: linear-gradient(to right,hsl(180, 100%, 90%),hsl(120, 100%, 90%));&quot; | 3<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Geschichte]] || [[Template:Portal History]] || [[Template:Portal Historia]] || [[Template:Portail Histoire‎]] || [[Template:Portal История]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Die Große Bibliothek/Geschichte]] || [[Portal:The Great Library/History]] || [[Portal:La Gran Biblioteca/Historia]] || [[Portail:La Grande Bibliothèque/Histoire‎]] || [[Portal:Великая Библиотека/История]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(120, 100%, 95%); background-image: linear-gradient(to left,hsl(180, 100%, 95%),hsl(120, 100%, 95%) 75%);&quot;<br />
| [[:Category:Trödel]] || [[:Category:Bric-a-brac]] || [[:Category:Batiburillo]] || [[:Category:Bric-à-brac]] || [[:Category:Базар]] ||style=&quot;background-color:hsl(120, 100%, 90%); background-image: linear-gradient(to right,hsl(180, 100%, 90%),hsl(120, 100%, 90%));&quot; | 3<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Trödel]] || [[Template:Portal Bric-a-brac]] || [[Template:Portal Batiburillo]] || [[Template:Portail Bric-à-brac]] || [[Template:Portal Базар]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Die Große Bibliothek/Trödel]] || [[Portal:The Great Library/Bric-a-brac]] || [[Portal:La Gran Biblioteca/Batiburillo]] || [[Portail:La Grande Bibliothèque/Bric-à-brac]] || [[Portal:Великая Библиотека/Базар]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(180, 100%, 95%); background-image: linear-gradient(to left,white,hsl(180, 100%, 95%) 75%);&quot;<br />
| [[:Category:Chroniken]] || [[:Category:Chronicles]] || [[:Category:Crónicas]] || [[:Category:Chroniques]] || [[:Category:Хроники]] ||style=&quot;background-color:hsl(180, 100%, 90%); background-image: linear-gradient(to right,white,hsl(180, 100%, 90%));&quot; | 2<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Chroniken]] || [[Template:Portal Chronicles]] || [[Template:Portal Crónicas]] || [[Template:Portail Chroniques]] || [[Template:Portal Хроники]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Chroniken]] || [[Portal:Chronicles]] || [[Portal:Crónicas]] || [[Portail:Chroniques]] || [[Portal:Хроники]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(120, 100%, 95%); background-image: linear-gradient(to left,hsl(180, 100%, 95%),hsl(120, 100%, 95%) 75%);&quot;<br />
| [[:Category:Chroniken Bis 2480]] || [[:Category:Chronicles Before 2480]] || [[:Category:Crónicas Antes de 2480]] || [[:Category:Chroniques Avant 2480]] || [[:Category:Хроники До 2480]] ||style=&quot;background-color:hsl(120, 100%, 90%); background-image: linear-gradient(to right,hsl(180, 100%, 90%),hsl(120, 100%, 90%));&quot; | 3<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Chroniken Bis 2480]] || [[Template:Portal Chronicles Before 2480]] || [[Template:Portal Crónicas Antes de 2480]] || [[Template:Portail Chroniques Avant 2480]] || [[Template:Portal Хроники До 2480]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Chroniken/Bis 2480]] || [[Portal:Chronicles/Before 2480]] || [[Portal:Crónicas/Antes de 2480]] || [[Portail:Chroniques/Avant 2480]] || [[Portal:Хроники/До 2480]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(120, 100%, 95%); background-image: linear-gradient(to left,hsl(180, 100%, 95%),hsl(120, 100%, 95%) 75%);&quot;<br />
| [[:Category:Chroniken 2481 - 2484]] || [[:Category:Chronicles 2481 - 2484]] || [[:Category:Crónicas 2481 - 2484]] || [[:Category:Chroniques 2481 - 2484]] || [[:Category:Хроники 2481 - 2484]] ||style=&quot;background-color:hsl(120, 100%, 90%); background-image: linear-gradient(to right,hsl(180, 100%, 90%),hsl(120, 100%, 90%));&quot; | 3<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Chroniken 2481 - 2484]] || [[Template:Portal Chronicles 2481 - 2484]] || [[Template:Portal Crónicas 2481 - 2484]] || [[Template:Portail Chroniques 2481 - 2484]] || [[Template:Portal Хроники 2481 - 2484]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Chroniken/2481 - 2484]] || [[Portal:Chronicles/2481 - 2484]] || [[Portal:Crónicas/2481 - 2484]] || [[Portail:Chroniques/2481 - 2484]] || [[Portal:Хроники/2481 - 2484]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(120, 100%, 95%); background-image: linear-gradient(to left,hsl(180, 100%, 95%),hsl(120, 100%, 95%) 75%);&quot;<br />
| [[:Category:Chroniken 2485 - 2525]] || [[:Category:Chronicles 2485 - 2525]] || [[:Category:Crónicas 2485 - 2525]] || [[:Category:Chroniques 2485 - 2525]] || [[:Category:Хроники 2485 - 2525]] ||style=&quot;background-color:hsl(120, 100%, 90%); background-image: linear-gradient(to right,hsl(180, 100%, 90%),hsl(120, 100%, 90%));&quot; | 3<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Chroniken 2485 - 2525]] || [[Template:Portal Chronicles 2485 - 2525]] || [[Template:Portal Crónicas 2485 - 2525]] || [[Template:Portail Chroniques 2485 - 2525]] || [[Template:Portal Хроники 2485 - 2525]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Chroniken/2485 - 2525]] || [[Portal:Chronicles/2485 - 2525]] || [[Portal:Crónicas/2485 - 2525]] || [[Portail:Chroniques/2485 - 2525]] || [[Portal:Хроники/2485 - 2525]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(120, 100%, 95%); background-image: linear-gradient(to left,hsl(180, 100%, 95%),hsl(120, 100%, 95%) 75%);&quot;<br />
| [[:Category:Chroniken 2525 - 2562]] || [[:Category:Chronicles 2525 - 2562]] || [[:Category:Crónicas 2525 - 2562]] || [[:Category:Chroniques 2525 - 2562]] || [[:Category:Хроники 2525 - 2562]] ||style=&quot;background-color:hsl(120, 100%, 90%); background-image: linear-gradient(to right,hsl(180, 100%, 90%),hsl(120, 100%, 90%));&quot; | 3<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Chroniken 2525 - 2562]] || [[Template:Portal Chronicles 2525 - 2562]] || [[Template:Portal Crónicas 2525 - 2562]] || [[Template:Portail Chroniques 2525 - 2562]] || [[Template:Portal Хроники 2525 - 2562]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Chroniken/2525 - 2562]] || [[Portal:Chronicles/2525 - 2562]] || [[Portal:Crónicas/2525 - 2562]] || [[Portail:Chroniques/2525 - 2562]] || [[Portal:Хроники/2525 - 2562]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(120, 100%, 95%); background-image: linear-gradient(to left,hsl(180, 100%, 95%),hsl(120, 100%, 95%) 75%);&quot;<br />
| [[:Category:Chroniken Seit 2562]] || [[:Category:Chronicles Since 2562]] || [[:Category:Crónicas Después de 2562]] || [[:Category:Chroniques Depuis 2562]] || [[:Category:Хроники С года 2562]] ||style=&quot;background-color:hsl(120, 100%, 90%); background-image: linear-gradient(to right,hsl(180, 100%, 90%),hsl(120, 100%, 90%));&quot; | 3<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Chroniken Seit 2562]] || [[Template:Portal Chronicles Since 2562]] || [[Template:Portal Crónicas Después de 2562]] || [[Template:Portail Chroniques Depuis 2562]] || [[Template:Portal Хроники С года 2562]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Chroniken/Seit 2562]] || [[Portal:Chronicles/Since 2562]] || [[Portal:Crónicas/Después de 2562]] || [[Portail:Chroniques/Depuis 2562]] || [[Portal:Хроники/С года 2562]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(120, 100%, 95%); background-image: linear-gradient(to left,hsl(180, 100%, 95%),hsl(120, 100%, 95%) 75%);&quot;<br />
| [[:Category:Chroniken OOC]] || [[:Category:Chronicles OOC]] || [[:Category:Crónicas OOC]] || [[:Category:Chroniques HRP]] || [[:Category:Хроники OOC]] ||style=&quot;background-color:hsl(120, 100%, 90%); background-image: linear-gradient(to right,hsl(180, 100%, 90%),hsl(120, 100%, 90%));&quot; | 3<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Chroniken OOC]] || [[Template:Portal Chronicles OOC]] || [[Template:Portal Crónicas OOC]] || [[Template:Portail Chroniques HRP]] || [[Template:Portal Хроники OOC]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Chroniken/OOC]] || [[Portal:Chronicles/OOC]] || [[Portal:Crónicas/OOC]] || [[Portail:Chroniques/HRP]] || [[Portal:Хроники/OOC]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(180, 100%, 95%); background-image: linear-gradient(to left,white,hsl(180, 100%, 95%) 75%);&quot;<br />
| [[:Category:X-files]] || [[:Category:X-files]] || [[:Category:Entresijos]] || [[:Category:Arcanes]] || [[:Category:X-files]] ||style=&quot;background-color:hsl(180, 100%, 90%); background-image: linear-gradient(to right,white,hsl(180, 100%, 90%));&quot; | 2<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal X-files]] || [[Template:Portal X-files]] || [[Template:Portal Entresijos]] || [[Template:Portail Arcanes]] || [[Template:Portal X-files]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:X-files]] || [[Portal:X-files]] || [[Portal:Entresijos]] || [[Portail:Arcanes]] || [[Portal:X-files]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(120, 100%, 95%); background-image: linear-gradient(to left,hsl(180, 100%, 95%),hsl(120, 100%, 95%) 75%);&quot;<br />
| [[:Category:Archives]] || [[:Category:Archives]] || [[:Category:Archivos]] || [[:Category:Archives]] || [[:Category:Archives]] ||style=&quot;background-color:hsl(120, 100%, 90%); background-image: linear-gradient(to right,hsl(180, 100%, 90%),hsl(120, 100%, 90%));&quot; | 3<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Archives]] || [[Template:Portal Archives]] || [[Template:Portal Archivos]] || [[Template:Portail Archives]] || [[Template:Portal Archives]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:X-files/Archives]] || [[Portal:X-files/Archives]] || [[Portal:Entresijos/Archivos]] || [[Portail:Arcanes/Objets perdus]] || [[Portal:X-files/Archives]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(120, 100%, 95%); background-image: linear-gradient(to left,hsl(180, 100%, 95%),hsl(120, 100%, 95%) 75%);&quot;<br />
| [[:Category:Geheimnis]] || [[:Category:Mysteries]] || [[:Category:Misterios]] || [[:Category:OVNI]] || [[:Category:Mysteries]] ||style=&quot;background-color:hsl(120, 100%, 90%); background-image: linear-gradient(to right,hsl(180, 100%, 90%),hsl(120, 100%, 90%));&quot; | 3<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Geheimnis]] || [[Template:Portal Mysteries]] || [[Template:Portal Misterios]] || [[Template:Portail OVNI]] || [[Template:Portal Mysteries]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:X-files/Geheimnis]] || [[Portal:X-files/The_Cave]] || [[Portal:Entresijos/La_Cueva]] || [[Portail:Arcanes/OVNI]] || [[Portal:X-files/Mysteries]] || P<br />
|--------------------------------------------style=&quot;border-top:double;&quot;<br />
! colspan=&quot;5&quot;|[[:Category:Wikipatys]] || 1<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Wikipatys]] || [[Template:Portal Wikipatys]] || [[Template:Portal Wikipatys]] || [[Template:Portail Wikipatys]] || [[Template:Portal Wikipatys]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:X-files/Wikipatys]] || [[Portal:X-files/Wikipatys]] || [[Portal:Entresijos/Wikipatys]] || [[Portail:Arcanes/Coulisses]] || [[Portal:X-files/Wikipatys]] || P<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(180, 100%, 95%); background-image: linear-gradient(to left,white,hsl(180, 100%, 95%) 75%);&quot;<br />
| [[:Category:Graphic Charter]] || [[:Category:Graphic Charter]] || [[:Category:Graphic Charter]] || [[:Category:Charte graphique]] || [[:Category:Graphic Charter]] ||style=&quot;background-color:hsl(180, 100%, 90%); background-image: linear-gradient(to right,white,hsl(180, 100%, 90%));&quot; | 2<br />
|--style=&quot;background-color:#eef;&quot;<br />
| colspan=&quot;5&quot;| ||<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| colspan=&quot;5&quot;| ||<br />
|--------------------------------------------style=&quot;border-top:double;background-color:hsl(180, 100%, 95%); background-image: linear-gradient(to left,white,hsl(180, 100%, 95%) 75%);&quot;<br />
| [[:Category:Portal]] || [[:Category:Portals]] || [[:Category:Portales]] || [[:Category:Portails‎]] || [[:Category:Портал]] ||style=&quot;background-color:hsl(180, 100%, 90%); background-image: linear-gradient(to right,white,hsl(180, 100%, 90%));&quot; | 2<br />
|--style=&quot;background-color:#eef;&quot;<br />
| colspan=&quot;5&quot;| ||<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| colspan=&quot;5&quot;| ||<br />
|--------------------------------------------style=&quot;border-top:double;&quot;<br />
! colspan=&quot;5&quot;|[[:Category:Forge]], managed by development team || 1<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Forge]] || [[Template:Portal Forge]] || [[Template:Portal Forge]] || [[:fr:Template:Portail Forge]] || [[Template:Portal Forge]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Forge]] || [[Portal:Forge]] || [[Portal:Forge]] || [[Portail:Forge]] || [[Portal:Forge]] || P<br />
|--------------------------------------------style=&quot;border-top:double;&quot;<br />
! colspan=&quot;5&quot;|[[:Category:Lore]], managed by Lore team || 1<br />
|--style=&quot;background-color:#eef;&quot;<br />
| [[Template:Portal Lore]] || [[Template:Portal Lore]] || [[Template:Portal Lore]] || [[:fr:Template:Portail Lore]] || [[Template:Portal Lore]] || T<br />
|---style=&quot;background-color:#ddf;&quot;<br />
| [[Portal:Lore]] || [[Portal:Lore]] || [[Portal:Lore]] || [[Portail:Lore]] || [[Portal:Lore]] || P<br />
|}<br />
<br />
==La Lore==<br />
{|class=&quot;wikitable alternance&quot; <br />
! Sous catégorie !! Sous niveau ou portail<br />
|+&lt;big&gt;[[:Category:Lore]]&lt;/big&gt; {{Portal Lore}}<br />
|-<br />
| ► [[:Category:Lore Officielle‎|Lore Officielle‎]]‎ || Toutes les pages validées par les ''' ''[[loristes]]'' '''. Ces pages ne peuvent être modifiées que par des administrateurs.<br />
|-<br />
|<br />
► [[:Category:LoreMigrée|LoreMigrée]]&lt;br/&gt;<br />
► [[:Category:Modèle:Ancienne Lore‎|Modèle:Ancienne Lore‎]]&lt;br/&gt;<br />
► [[:Category:Modèle:Lore‎|Modèle:Lore‎]]&lt;br/&gt;<br />
► [[:Category:ValidationLore‎|ValidationLore‎]]&lt;br/&gt;<br />
► [[:Category:WikiFusionner‎|WikiFusionner‎]]<br />
| Gestion technique de la Lore<br />
|-<br />
|► [[:Category:To be check|To be check]] ||&lt;big&gt;{{3DText|text=Articles devant être validés et protégés en écriture par les [[Loristes]] ou les Sysop (en accord avec les loristes)}}&lt;/big&gt;<br />
|}<br />
<br />
==Ryzom Forge==<br />
{|class=&quot;wikitable alternance&quot; <br />
! Sous catégorie !! Sous niveau ou portail<br />
|+&lt;big&gt;[[:Category:Forge]]&lt;/big&gt; {{Portal Forge}}<br />
|-<br />
|<br />
► 3D‎&lt;br/&gt;<br />
► ARK‎&lt;br/&gt;<br />
► Brainstorming‎&lt;br/&gt;<br />
► Comm Marketing‎&lt;br/&gt;<br />
► Comp Graphic‎&lt;br/&gt;<br />
► Dev‎&lt;br/&gt;<br />
► Forge Dev‎&lt;br/&gt;<br />
► Forge Event‎ &lt;br/&gt;<br />
► Forge Lore‎ &lt;br/&gt;<br />
► Forge Portal‎&lt;br/&gt;<br />
► Graphic‎ &lt;br/&gt;<br />
► Help contents‎ &lt;br/&gt;<br />
► Help-support‎ &lt;br/&gt;<br />
► Ideas‎&lt;br/&gt;<br />
► K dfn sitem‎ &lt;br/&gt;<br />
► K item typ‎ &lt;br/&gt;<br />
► K primitives ryzom core‎ &lt;br/&gt;<br />
► K sitem typ‎&lt;br/&gt;<br />
► Khaganat‎ &lt;br/&gt;<br />
► Level-Design‎ &lt;br/&gt;<br />
► Linux‎&lt;br/&gt;<br />
► News‎ &lt;br/&gt;<br />
► Project&lt;br/&gt;<br />
► Rykea‎&lt;br/&gt;<br />
► Support‎&lt;br/&gt;<br />
► Test‎ &lt;br/&gt;<br />
► Textures‎&lt;br/&gt;<br />
► Translation‎ &lt;br/&gt;<br />
► Tutorials‎&lt;br/&gt;<br />
► Wiki Admin‎ &lt;br/&gt;<br />
| Les sous catégories sont (et doivent être) identiques dans les 5 langues. <br />
|}<br />
Vers [[Categorization/Notes réu category Forge 1]]<br />
<br />
==The Wikipatys==<br />
{{Portal|Wikipatys}} <br />
&quot; The &lt;big&gt;[[:category:Wikipatys|Wikipatys]] &lt;/big&gt; is the dark side of the administration of this wiki ;) &quot;<br />
{{WIP}}<br />
{|class=&quot;wikitable alternance » <br />
! colspan=&quot;3&quot; | Presentation toolkit <br />
|-<br />
|► &lt;big&gt;&lt;big&gt;'''[[:Category:Categorization|Categorization]]'''&lt;/big&gt;&lt;/big&gt; || the '''category ''categorization'' ''' includes shared categorization rules for the 5 wiki languages.<br />
|-<br />
|► &lt;big&gt;&lt;big&gt;'''[[:Category:Charte graphique‎|Charte graphique]]'''&lt;/big&gt;&lt;/big&gt; || La '''catégorie ''Charte graphique''''' comprend la charte graphique de wiki de Ryzom et les modèles associés. Les couleurs sont celles utilisées fréquemment dans le jeu (uniformes, logo...) pour &quot;colorier&quot; les thèmes (trykers, kamis...), dans forge (alerte, commentaires...). Elles sont conjuguées sur plusieurs intensités pour permettre des contrastes suffisant pour une lecture confortable.<br />
|-<br />
| rowspan=&quot;8&quot; | ► &lt;big&gt;&lt;big&gt;'''[[:Category:Template|Template]]'''&lt;/big&gt;&lt;/big&gt; <br />
|► &lt;big&gt;'''[[:category:Template:Bandeau|Template:Bandeau]]'''&lt;/big&gt; || La '''catégorie des ''modèles de bandeaux''''' comprend les modèles que l’on insère en en-tête des articles, ou de certains paragraphes pour avertir le lecteur de la pertinence, de la qualité, etc. de ce qui suit. <br />
|-<br />
| colspan=&quot;2&quot;| • Les '''Modèle de la ''Chartes graphiques‎‎''''' sont dans [[:Category:Charte graphique|‎Charte graphique]]<br />
|-<br />
|► &lt;big&gt;'''[[:Category:Template:Infobox|Template:Infobox]]'''&lt;/big&gt; || La '''catégorie ''Template:Infobox'' ''' contient les infobox du wiki Ryzom.<br />
Une infobox sur [http://fr.wikipedia.org/wiki/Aide:Infobox Wikipedia] est une table préformatée de données dynamiques qui présente sommairement des informations importantes sur un sujet dans une cartouche ou un encadré placé en général à droite de l'article. Les informations contenues dans une infobox ne doivent pas se substituer à l’article ; il convient que le contenu d’une infobox reste très sommaire. <br />
Dans le wiki Ryzom, Ces boîtes ont l'aspect d'une ambre pour tout ce qui concerne le jeu vu par le joueur (RP ou non), et une boîte «fluo» pour ce qui est plus technique (Forge essentiellement).<br />
|-<br />
|► &lt;big&gt;'''[[:Category:Lien portail|‎‎Lien portail]]'''&lt;/big&gt; || La '''catégorie ''Lien portail''''' regroupe tous les liens des articles vers leur(s) portail(s).<br />
Ces liens se trouve tout en bas de la page de l'article.<br />
|-<br />
|► &lt;big&gt;'''[[:Category:Template:Lore‎‎|Template:Lore‎‎]]'''&lt;/big&gt; || La '''catégorie ''Template:Lore'' ''' contient les modèles spécifiques utilisés pour la lorification des articles. <br />
|-<br />
|► &lt;big&gt;'''[[:Category:Template navigation‎‎|Template navigation‎‎]]'''&lt;/big&gt; || La '''catégorie ''Modèle navigation''''' regroupe les palettes de navigation.<br />
Une palette de navigation est un modèle qui permet de naviguer via un regroupement de liens internes dans un groupe restreint d'articles. Elle est généralement située horizontalement au bas des articles ou plus rarement verticalement à droite des articles. Extrait de [http://fr.wikipedia.org/wiki/Aide:Palette_de_navigation Wikipédia]<br />
|-<br />
|► &lt;big&gt;'''[[:Category:Template:Onglet‎‎|Template:Onglet‎‎]]'''&lt;/big&gt; || La '''catégorie ''Template:Onglet''''' regroupe les modèle pour la création d'onglets.<br />
|-<br />
|► &lt;big&gt;'''[[:Category:Templates|‎Templates]]'''&lt;/big&gt; || La '''catégorie ''Template''''' regroupe les modèles identiques pour tous le wiki, en anglais, non traduits, car souvent évidents. <br />
|-<br />
|► &lt;big&gt;&lt;big&gt;'''[[:Category:Portals‎|Portals‎]]'''&lt;/big&gt;&lt;/big&gt;<br />
La '''catégorie ''Portails''''' contient &lt;u&gt;les portails proprement dits et les sous-portails&lt;/u&gt; associés au portail maître (les onglets du portail).<br />
|► &lt;big&gt;'''[[:Category:Template:Portal|Template:Portal]]'''&lt;/big&gt; <br />
La '''catégorie ''Template:Portail''''' réunit toutes les &lt;big&gt;{{3DText|text=''briques''}}&lt;/big&gt; qui constituent un portail. <br />
|► '''[[:Category:Lumière sur|Lumière sur]]'''<br />
'''Lumière sur''' est une astuce pour remplacer l'affichage '''aléatoire''' de &quot;bons&quot; articles. Cette méthode permet d'afficher un article différent par semaine, mois voire année.<br />
Le article référencé sont soit redirigés, soit copiés/collés. Ce dernier est utile pour tronquer le texte à une taille raisonnable pour rentrer élégamment dans la page du portail. Dans ce cas, en bas il faut ajouter un lien '''&quot;à suivre&quot;''' qui pointe vers la page entière.<br />
[[Category:Template:Portal]]<br />
|-<br />
! colspan=&quot;3&quot; | Boîte à outils pour la maintenance et les patrouilles <br />
|-<br />
|► [[:Category:À blanchir‎|À blanchir]] &lt;br/&gt;<br />
► [[:Category:Article à illustrer|Article à illustrer‎]]&lt;br/&gt;<br />
► [[:Category:Ebauche|‎Ebauche]]&lt;br/&gt;<br />
► [[:Category:Pages avec des liens de fichiers brisés|‎Pages avec des liens de fichiers brisés]] &lt;br/&gt;<br />
► [[:Category:WIP|WIP]] ‎&lt;br/&gt;<br />
|-<br />
! colspan=&quot;3&quot; | Catégories techniques <br />
|-<br />
|► [[:Category:Admin|Admin]] &lt;br/&gt;<br />
► [[:Category:Aide|‎Aide]] &lt;br/&gt;<br />
|-<br />
|► [[:category:Babylon|‎Babylon]] || La '''catégorie ''Babylon‎''''' comprend les langues plus ou moins bien connues par les contributeurs qui y sont présents. <br />
|-<br />
|► [[:category:Catégories cachées|‎Catégories cachées]] || La '''catégorie ''Catégories cachées''''' comprend des catégories techniques inutiles pour la classification en soi, mais servant à &quot;ranger&quot; les articles par exemple choisi au hasard ou autre pour la &quot;Une&quot; des portails. <br />
|-<br />
|► [[:Category:Exclure_lors_de_l%27impression|Exclure lors de l’impression]] &lt;br/&gt;<br />
► [[:Category:Homonymie|Homonymie]]‎ &lt;br/&gt;<br />
► [[:Category:Images|‎Images]]‎ &lt;br/&gt;<br />
► [[:Category:Maquettes‎|Maquettes]]&lt;br/&gt;<br />
► [[:Category:Obsolète‎|Obsolète‎]] &lt;br/&gt;<br />
► [[:Category:Policies|Policies]] ‎&lt;br/&gt;<br />
► [[:Category:Wikipatys|etc.]]<br />
|}<br />
[[Category:Categorization]]<br />
&lt;!------------------------------<br />
==Wikipatys == <br />
<br />
|-<br />
/ ► &lt; big &gt; &lt;big &gt; &quot; '[[[: category: chart|chart]]]&quot;'&lt;/big&gt;&lt;/big&gt; || the &quot;' category &quot;chart&quot;&quot; ' includes Ryzom's wiki chart and associated models. The colors are those used frequently in the game (uniforms, logo...) for &quot;coloring&quot; the themes (trykers, kamis...), forge (alert, comments...). They are combined over several intensities to allow sufficient contrasts for a comfortable reading.<br />
|-<br />
/ rowspan= &quot; 8 &quot;/ ► &lt; big &gt; &lt;big &gt; &quot; '[[: Category: models|models]] &quot;' &lt; / big &gt; &lt; / big&gt; <br />
/ ► &lt; big &gt; &quot; '[[: category:pattern:Bandeau|model: Bandeau]]&quot;'&lt;/big&gt; || the &quot;'category of&quot; band patterns &quot;&quot;' includes patterns that are inserted in the letterhead of articles, or of certain paragraphs to alert the reader to the relevance, quality, etc.of the following. <br />
|-<br />
/ colspan= &quot; 2 &quot;/ • The &quot;'chart model &quot;' are in [[: Category: chart / chart]]<br />
|-<br />
/ ► &lt; big &gt; &quot; '[[: Category:Model:Infobox|model: Infobox]]&quot;'&lt;/big&gt; || the &quot;'category &quot;Model: Infobox &quot;&quot;' contains the infobox of the ryzom wiki.<br />
An infobox on [http://fr.wikipedia.org/wiki/Aide:Infobox Wikipedia] is a pre-formatted table of dynamic data that outlines important information about a topic in a cartridge or box usually placed to the right of the article. The information contained in an infobox should not replace the article ; the content of an infobox should remain very brief. <br />
In the ryzom wiki, these boxes have the appearance of an amber for all that concerns the game seen by the player (RP or not), and a &quot;fluo&quot; box for what is more technical (Forge essentially).<br />
|-<br />
/ ► &lt; big &gt; &quot;' [[: category: link portal / link portal]] &quot;'&lt;/big&gt; || the &quot;' category&quot; link portal&quot; &quot;' brings together all the links of the articles to their portal(s).<br />
These links can be found at the bottom of the article page.<br />
|-<br />
/ ► &lt; big &gt; &quot; '[[: Category:Model:Lore|model:Lore]]&quot;'&lt;/big&gt; || the &quot;' category &quot;Model: Lore&quot; &quot;' contains the specific models used for the lorification of articles. <br />
|-<br />
/ ► &lt; big &gt; &quot; '[[: category: navigation model|navigation model]]&quot;'&lt;/big&gt; || the &quot;' category&quot; navigation model&quot; &quot;' includes navigation pallets.<br />
A navigation palette is a template that allows you to browse through a group of internal links in a small group of articles. It is usually located horizontally at the bottom of the articles or more rarely vertically to the right of the articles. Extract from [http://fr.wikipedia.org/wiki/Aide:Palette_de_navigation Wikipedia]<br />
|-<br />
/ ► &lt; big &gt; &quot;'[[: category: template: tab / template: tab]] &quot;'&lt; / big&gt; / / the &quot;'category&quot; template: Tab &quot;&quot;' Groups the templates for creating tabs.<br />
|-<br />
/ ► &lt;big &gt; &quot; '[[: Category: Templates|Templates]]&quot;'&lt;/big&gt; || the &quot;'category &quot;Template&quot;&quot;' brings together identical models for all the wiki, in English, not translated, because often obvious. <br />
|-<br />
/ ► &lt; big &gt; &lt;big &gt; &quot; '[[: Category: portals|portals]] &quot;' &lt; / big &gt; &lt; / big&gt;<br />
The &quot;'category&quot; portals &quot;&quot;' contains &lt; u&gt;the portals themselves and the&lt;/u&gt; sub-portals associated with the master portal (the portal tabs).<br />
/ ► &lt; big &gt; &quot; '[[: Category:Model:portal|model: portal]]&quot; ' &lt;/big&gt; <br />
The &quot;'category&quot; Model:portal &quot;'brings together all the &lt;big &gt; {{3DText/text= &quot;bricks&quot;}} &lt; / big &gt; that constitute a portal. <br />
/ ► &quot;'[[: Category: light on|light on]]&quot;'<br />
&quot;'Light on&quot; ' is a trick to replace the &quot;'random &quot;'display of&quot; good &quot; items. This method allows to display a different article per week, month or even year.<br />
The referenced article is either redirected or copied/pasted. The latter is useful for truncating the text to a reasonable size to fit elegantly into the portal page. In this case, at the bottom you have to add a link &quot;'&quot;to follow&quot;&quot;' which points to the entire page.<br />
[[Category:Model: Portal]]<br />
|-<br />
! colspan= &quot; 3 &quot; / maintenance and patrol toolbox <br />
|-<br />
/ ► [[: category: to be bleached / bleached]] &lt;br / &gt;<br />
► [[: Category: article to illustrate / article to illustrate]]&lt;br / &gt;<br />
► [[:Category:Draft|Draft]]&lt;br/&gt;<br />
► [[: category: Pages with broken file links|Pages with broken file links]] &lt;br / &gt;<br />
► [[: category: WIP / WIP]] &lt;br / &gt;<br />
|-<br />
! colspan = &quot; 3 &quot; / technical categories <br />
|-<br />
|► [[:Category:Admin|Admin]] &lt;br/&gt;<br />
► [[:Category:Help|Help]] &lt;br/&gt;<br />
|-<br />
| ► [[: Category:Babylon | Babylon]] | / the &quot;'category &quot;Babylon &quot;&quot;' includes languages more or less well known by the contributors who are present. <br />
|-<br />
| ► [[: category:hidden categories | hidden categories]] | / the &quot;'category &quot;hidden categories&quot;&quot;' includes technical categories which are not relevant for classification per se, but which are used to &quot;store&quot; items, for example, chosen at random or otherwise for the &quot;one&quot; of portals. <br />
|-<br />
/ ► [[: category: Exclure_ors_of_l % 27impression / exclude when printed]] &lt;br / &gt;<br />
► [[:category:Disambiguation|Disambiguation]] &lt;br/&gt;<br />
► [[:category:Images|Images]] &lt;br/&gt;<br />
► [[: Category: models / models]]&lt;br / &gt;<br />
► [[: Category: obsolete / obsolete]] &lt;br / &gt;<br />
► [[:category:Policies|Policies]] &lt;br/&gt;<br />
► [[: Category: Wikipatys|etc.]]<br />
|}<br />
[[category: categorisation]]<br />
--------------------------------------&gt;<br />
<br />
==Autres portails==<br />
{{Portail Langage}}<br />
<br />
[[category:Categorization]]</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29634Wiki Technical Guide2019-06-13T20:06:15Z<p>Maupas: /* Template */</p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Lore Validation Request}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''&lt;big&gt;Categories&lt;/big&gt;'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
&lt;div style=&quot;text-align:center;&quot;&gt;<br />
{{3DText|3D=outset|group=ranger|text=&lt;span style=&quot;font-size:large;font-variant: small-caps;font-weight: bold;&quot;&gt;'''''Portal …'''''&lt;/span&gt;}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''&lt;code&gt;&lt;nowiki&gt;There are for now {{Number of pages}} pages on …&lt;/nowiki&gt;&lt;/code&gt;'''<br />
&lt;/div&gt;<br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use &lt;code&gt;&lt;nowiki&gt;{{Number of pages}}&lt;/nowiki&gt;&lt;/code&gt; that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article &lt;big&gt;'''''[[Categorization]]'''''&lt;/big&gt;. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
=='''&lt;big&gt;Template&lt;/big&gt;'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
===All templates===<br />
&lt;big&gt;'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.&lt;/big&gt;<br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#Le_Wikipatys]]</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29633Wiki Technical Guide2019-06-13T19:21:34Z<p>Maupas: </p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Lore Validation Request}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''&lt;big&gt;Categories&lt;/big&gt;'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
&lt;div style=&quot;text-align:center;&quot;&gt;<br />
{{3DText|3D=outset|group=ranger|text=&lt;span style=&quot;font-size:large;font-variant: small-caps;font-weight: bold;&quot;&gt;'''''Portal …'''''&lt;/span&gt;}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''&lt;code&gt;&lt;nowiki&gt;There are for now {{Number of pages}} pages on …&lt;/nowiki&gt;&lt;/code&gt;'''<br />
&lt;/div&gt;<br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use &lt;code&gt;&lt;nowiki&gt;{{Number of pages}}&lt;/nowiki&gt;&lt;/code&gt; that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article &lt;big&gt;'''''[[Categorization]]'''''&lt;/big&gt;. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
=='''&lt;big&gt;Template&lt;/big&gt;'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29612Wiki Technical Guide2019-06-10T16:53:44Z<p>Maupas: /* Template */</p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Lore Validation Request}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''&lt;big&gt;Categories&lt;/big&gt;'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
&lt;div style=&quot;text-align:center;&quot;&gt;<br />
{{3DText|3D=outset|group=ranger|text=&lt;span style=&quot;font-size:large;font-variant: small-caps;font-weight: bold;&quot;&gt;'''''Portal …'''''&lt;/span&gt;}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''&lt;code&gt;&lt;nowiki&gt;There are for now {{Number of pages}} pages on …&lt;/nowiki&gt;&lt;/code&gt;'''<br />
&lt;/div&gt;<br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use &lt;code&gt;&lt;nowiki&gt;{{Number of pages}}&lt;/nowiki&gt;&lt;/code&gt; that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article &lt;big&gt;'''''[[Categorization]]'''''&lt;/big&gt;. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
=='''&lt;big&gt;Template&lt;/big&gt;'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29611Wiki Technical Guide2019-06-10T16:52:22Z<p>Maupas: /* The main categories of this wiki */</p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Lore Validation Request}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''&lt;big&gt;Categories&lt;/big&gt;'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
&lt;div style=&quot;text-align:center;&quot;&gt;<br />
{{3DText|3D=outset|group=ranger|text=&lt;span style=&quot;font-size:large;font-variant: small-caps;font-weight: bold;&quot;&gt;'''''Portal …'''''&lt;/span&gt;}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''&lt;code&gt;&lt;nowiki&gt;There are for now {{Number of pages}} pages on …&lt;/nowiki&gt;&lt;/code&gt;'''<br />
&lt;/div&gt;<br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use &lt;code&gt;&lt;nowiki&gt;{{Number of pages}}&lt;/nowiki&gt;&lt;/code&gt; that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article &lt;big&gt;'''''[[Categorization]]'''''&lt;/big&gt;. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
=='''&lt;big&gt;Template&lt;/big&gt;'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29610Wiki Technical Guide2019-06-10T16:35:52Z<p>Maupas: /* On the use of categories */</p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Lore Validation Request}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''&lt;big&gt;Categories&lt;/big&gt;'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
&lt;div style=&quot;text-align:center;&quot;&gt;<br />
{{3DText|3D=outset|group=ranger|text=&lt;span style=&quot;font-size:large;font-variant: small-caps;font-weight: bold;&quot;&gt;'''''Portal …'''''&lt;/span&gt;}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''&lt;code&gt;&lt;nowiki&gt;There are for now {{Number of pages}} pages on …&lt;/nowiki&gt;&lt;/code&gt;'''<br />
&lt;/div&gt;<br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use &lt;code&gt;&lt;nowiki&gt;{{Number of pages}}&lt;/nowiki&gt;&lt;/code&gt; that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article &lt;big&gt;'''''[[Categorization]]'''''&lt;/big&gt;. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29608Wiki Technical Guide2019-06-10T15:43:39Z<p>Maupas: </p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Lore Validation Request}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''&lt;big&gt;Categories&lt;/big&gt;'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29607Wiki Technical Guide2019-06-10T15:26:52Z<p>Maupas: </p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Lore Validation Request}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Template:Lore_Validation_Request&diff=29606Template:Lore Validation Request2019-06-10T15:24:57Z<p>Maupas: Created page with &quot;left&lt;div style=&quot;margin:1em;padding:1em;border: medium outset #ff0;background:#ff9;color:#330;text-align:center;font-weight: bold; font-size:large;fo...&quot;</p>
<hr />
<div>[[File:Dummy.png‎|48px|left]]&lt;div style=&quot;margin:1em;padding:1em;border: medium outset #ff0;background:#ff9;color:#330;text-align:center;font-weight: bold; font-size:large;font-variant:small-caps;text-shadow: white -1px -1px 0.02em, black 1px 1px .05em;&quot;&gt;This page is submitted to the Lore staff for validation. &lt;div style=&quot;text-align:right;font-weight: normal; font-size:small;font-variant:none;font-style:italic&quot;&gt;Editing date:{{{1|...}}}&lt;/div&gt;&lt;/div&gt;<br />
&lt;noinclude&gt;[[Category:Template:Banner]][[Category:Template:Lore]]&lt;/noinclude&gt;</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29604Wiki Technical Guide2019-06-10T14:48:24Z<p>Maupas: </p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;<br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''&lt;code&gt;&lt;nowiki&gt;{{Official Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' wihich will display the picture [[image:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''&lt;code&gt;&lt;nowiki&gt;{{Demande validation Lore}}&lt;/nowiki&gt;&lt;/code&gt;''' which is displayed as follows:<br />
<br />
{{Demande validation Lore}} Request for Lore validation</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29603Wiki Technical Guide2019-06-10T14:33:17Z<p>Maupas: </p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29602Wiki Technical Guide2019-06-10T14:26:03Z<p>Maupas: </p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|models]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
&lt;big&gt;A document validated by the Loristes, the official communications officers or the administrators is protected against any modifications not expressly authorized.&lt;/big&gt;</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29601Wiki Technical Guide2019-06-10T14:11:29Z<p>Maupas: </p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''&lt;code&gt;&lt;nowiki&gt;[[Utilisateur:Zorroargh/Brouillons/...]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
<br />
=='''&lt;big&gt;Validation of content&lt;/big&gt;'''==<br />
Normalement, dans les wikis de Ryzom toutes les pages sont libres de traitement tant qu'il n'y a pas vandalisme. Néanmoins, les joueurs peuvent avoir besoin de documents fiables. Cela concerne essentiellement :<br />
<br />
[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&amp;post187218=en#1 Ryzom code of conduct]</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29600Wiki Technical Guide2019-06-10T13:55:28Z<p>Maupas: </p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP|~~~~}}&lt;/nowiki&gt;&lt;/code&gt;''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&amp;nbsp;&lt;sup&gt;&lt;small&gt;[[User talk:Zorroargh|Woren&amp;nbsp;Siloy]]&lt;/small&gt;&lt;/sup&gt; 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''&lt;code&gt;&lt;nowiki&gt;{{WIP}}&lt;/nowiki&gt;&lt;/code&gt;'''.”</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29599Wiki Technical Guide2019-06-10T13:26:07Z<p>Maupas: </p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29595Wiki Technical Guide2019-06-09T22:33:13Z<p>Maupas: </p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''&lt;code&gt;&lt;nowiki&gt;&lt;!--&lt;/nowiki&gt;&lt;/code&gt;''' and to follow it with '''&lt;code&gt;&lt;nowiki&gt;--&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''&lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;''' and '''&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt;'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of a:</div>Maupashttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=29594Wiki Technical Guide2019-06-09T18:56:22Z<p>Maupas: </p>
<hr />
<div>&lt;noinclude&gt;{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=2<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}&lt;/noinclude&gt;<br />
'''''A short technical guide for experienced contributors and documentation managers.'''''<br />
<br />
=='''&lt;big&gt;Working as a team&lt;/big&gt;'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''&lt;code&gt;&lt;nowiki&gt;[[Talk:{{FULLPAGENAME}}]]&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''&lt;code&gt;&lt;nowiki&gt;===Title of the topic==&lt;/nowiki&gt;&lt;/code&gt;'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''&lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more &lt;code&gt;:&lt;/code&gt; than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''&lt;code&gt;&lt;nowiki&gt;==Title of the topic {{OK}}==&lt;/nowiki&gt;&lt;/code&gt;'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''&lt;code&gt;&lt;nowiki&gt;{{KO}}&lt;/nowiki&gt;&lt;/code&gt;'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''&lt;big&gt;Translations&lt;/big&gt;'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''&lt;big&gt;Edition&lt;/big&gt;'''==</div>Maupas