Difference between revisions of "Help:Add new Honor"
DesignerThan (talk | contribs) |
DesignerThan (talk | contribs) |
||
Line 1: | Line 1: | ||
− | + | ||
<div class="toc toccolours toclimit-3" style="float: left; margin-right: 1em;"> | <div class="toc toccolours toclimit-3" style="float: left; margin-right: 1em;"> | ||
__TOC__ | __TOC__ | ||
</div> | </div> | ||
− | To know which pages are important for an honor, read the section about the [[Pathfinder_Wiki:Structure|Structure of an Honor]]. | + | Here you'll find a guide on how to add a new honor to the wiki. To know which pages are important for an honor, read the section about the [[Pathfinder_Wiki:Structure|Structure of an Honor]]. |
== Create the Honor Landing Page == | == Create the Honor Landing Page == | ||
Line 10: | Line 10: | ||
Source Code wise it has the following structure: Template call of [[Template:HonorLanding|HonorLanding]] followed by the Overview and the Challenging-Part-Section. The content ends with a call of the [[Template:CloseHonorPage|CloseHonorPage-Template]] Use the following code as a starting point and set the needed arguments of the [[Template:HonorLanding|HonorLanding Template]], they are described in the documentation of the template, and write an awesome overview. Then the Landing Page should be finished. | Source Code wise it has the following structure: Template call of [[Template:HonorLanding|HonorLanding]] followed by the Overview and the Challenging-Part-Section. The content ends with a call of the [[Template:CloseHonorPage|CloseHonorPage-Template]] Use the following code as a starting point and set the needed arguments of the [[Template:HonorLanding|HonorLanding Template]], they are described in the documentation of the template, and write an awesome overview. Then the Landing Page should be finished. | ||
− | <syntaxhighlight lang=" | + | <syntaxhighlight lang="html+handlebars" style="overflow:auto"> |
− | + | {{HonorLanding | |
− | |skill=2 | + | |skill=2 |
− | |year=Unknown | + | |year=Unknown |
− | |category=Regional | + | |category=Regional |
− | |authority=Florida Conference | + | |authority=Florida Conference |
− | |insignia=Scrapbooking (FL) AY Honor.png | + | |insignia=Scrapbooking (FL) AY Honor.png |
− | |insignia_source=FL | + | |insignia_source=FL |
− | |primary=AY Honors/Scrapbooking | + | |primary=AY Honors/Scrapbooking |
}} | }} | ||
− | + | == {{Localize|Overview}}== | |
− | < | + | <translate> |
− | WRITE AN AWESOME OVERVIEW HERE :) | + | WRITE AN AWESOME OVERVIEW HERE :) |
− | < | + | </translate> |
− | + | == {{Localize|The Challenging Part}} == | |
− | + | {{Localize|Challenging Part}} | |
− | + | {{#lst:{{#titleparts:{{PAGENAME}}|2|1}}/Requirements{{GetLangSuffix}} |challenge}} | |
− | + | {{CloseHonorPage}} | |
</syntaxhighlight > | </syntaxhighlight > | ||
Line 37: | Line 37: | ||
Use the following code as a template for the requirements page. | Use the following code as a template for the requirements page. | ||
− | <syntaxhighlight lang=" | + | <syntaxhighlight lang="html+handlebars" style="overflow:auto"> |
− | + | {{HonorSubpage}} | |
− | < | + | <section begin=Body /> |
− | < | + | <b>1. <section begin=req1 /><noinclude><translate> |
− | < | + | </noinclude>The first Requirement of this honor. |
− | < | + | <noinclude></translate></noinclude><section end=req1 /></b> |
− | < | + | <section begin=challenge /> |
− | < | + | <b>N. <section begin=reqN /><noinclude><translate> |
− | < | + | </noinclude>The N-th Requirement of this honor |
− | < | + | <noinclude></translate></noinclude><section end=reqN /></b> |
− | < | + | <section end=challenge /> |
− | < | + | <section end=Body /> |
+ | {{CloseHonorPage}} | ||
</syntaxhighlight > | </syntaxhighlight > | ||
+ | |||
+ | The page needs to start with the Template-Call of [[Template:HonorSubpage|HonorSubpage]]. It generates the Honor-Navigation, Language Switcher, the Infobox and the basic page structure. At the end of the page, the Template [[Template:CloseHonorPage|CloseHonorPage]] needs to be called, to close the HTML-Page-Structure. Between the two Templage calls the <code><section begin=Body /></code>-Tag and the <code><section end=Body /></code>-Tag is needed. The section-tags enable the wiki, to include the enclosed content, on other pages, by the name of the section. Each section name, needs to be unique on the page. | ||
+ | |||
+ | The requirements are also enclosed by section-tags. The names of these start with "req", followed by the requirement number. Between the section-tags the translate-tags need to be opened and closed. That they aren't included on other pages they need to be surrounded by noinclude-tags. For the sake of styling the whole requirement is surrounded by the b-tags, those make the text bold. | ||
+ | |||
+ | Next one needs to define the requirement that is the challenging part of the honor. That is again done by using the section-tags using the section name "challenge". In the example that would be the N-th requirement. |
Revision as of 13:43, 3 October 2023
Here you'll find a guide on how to add a new honor to the wiki. To know which pages are important for an honor, read the section about the Structure of an Honor.
Create the Honor Landing Page
That is the first page that need's to be created. It has the following structure: The Honor Navigation, followed by an Overview and the Challenging-Part-Section. On the right side it has the infobox that is displaying the most important information about an honor.
Source Code wise it has the following structure: Template call of HonorLanding followed by the Overview and the Challenging-Part-Section. The content ends with a call of the CloseHonorPage-Template Use the following code as a starting point and set the needed arguments of the HonorLanding Template, they are described in the documentation of the template, and write an awesome overview. Then the Landing Page should be finished.
Create the Requirements Page
To create the requirement page, just use the link to the requirements page on the newly created honor landing page. Use the following code as a template for the requirements page.
The page needs to start with the Template-Call of HonorSubpage. It generates the Honor-Navigation, Language Switcher, the Infobox and the basic page structure. At the end of the page, the Template CloseHonorPage needs to be called, to close the HTML-Page-Structure. Between the two Templage calls the -Tag and the
-Tag is needed. The section-tags enable the wiki, to include the enclosed content, on other pages, by the name of the section. Each section name, needs to be unique on the page.
The requirements are also enclosed by section-tags. The names of these start with "req", followed by the requirement number. Between the section-tags the translate-tags need to be opened and closed. That they aren't included on other pages they need to be surrounded by noinclude-tags. For the sake of styling the whole requirement is surrounded by the b-tags, those make the text bold.
Next one needs to define the requirement that is the challenging part of the honor. That is again done by using the section-tags using the section name "challenge". In the example that would be the N-th requirement.