Difference between revisions of "Template:Ansreq"

From Pathfinder Wiki
 
(59 intermediate revisions by 4 users not shown)
Line 1: Line 1:
<!--close the collapsible box from previous requirement-->
+
<noinclude>
{{#ifeq:{{{num}}}|1
+
This template is used to create the header and the answerbox of a requirement. The answerbox needs to be closed by using the [[Template:CloseReq|CloseReq]]-Template.<br>
|<!--first requirement doesn't close previous box-->
+
For example like that:<br>
|</div></div><!--if this is not the first requirement, close the previous box-->}}
+
<div class="toccolours">
 +
:<nowiki>{{Ansreq|num=1|page={{PAGENAME}}}}<nowiki /></nowiki><br>
 +
:<nowiki>Here you can write your answer. Any MediaWiki-Content is possible.</nowiki><br>
 +
:<nowiki>{{CloseReq}}</nowiki>
 +
</div>
 +
The <nowiki><nowiki /></nowiki> tag is needed so there is no unnecessary line break at the begining of the answer.
 +
For the Example the <nowiki>{{PAGENAME}}</nowiki> was replaced with a fixed name, but at an honor page the template will get the needed information out of the pagename.
  
<!-- Add empty header to make the section editable.-->
+
If the page argument contains the word "Requirement" then the requirements are fetched directly from that page.  If it doesn't, then we construct the requirements page by extracting the first two elements of the page (assumed to be "AY Honors/''honor''") and appending "/Requirements" to it. We need this to support variant requirements, as it allows us to specify
=={{{num}}}==
+
<pre>page=AY Honors/''honor''/Requirements_2</pre>
 +
in the honor landing template.
  
<!--render requirements box-->
+
{{Ansreq|num=1|page=AY Honors/Aboriginal Lore}}<nowiki />
<table width="100%" cellspacing=0>
+
This is the example answer. Any MediaWiki-Content is possible (Tables, Templates, ...).
<tr>
+
{{CloseReq}}
<td bgcolor=#8080e0>
+
</noinclude><includeonly><div class="req-container"><div class="req-head"><p class="req-num">
<font size=3 color=#202020>
+
{{#if:{{#pos:{{{page|}}}
'''''{{#switch:{{SUBPAGENAME}}
+
            |Requirements}}
|es=Requisito
+
    |{{#vardefine:reqpage|{{{page}}}}}
|fr=Exigence
+
    |{{#vardefine:reqpage|{{#titleparts:{{{page}}}|2|1}}/Requirements}}
|Requirement}} {{{num}}}'''''</font>
+
}}{{{dispreq|{{{num}}}}}}</p><div class="req-text">{{#lst:{{#var:reqpage}}{{GetLangSuffix}}|req{{{num}}} }}</div></div></div><div class="req-answer"></includeonly>
</td>
+
<noinclude>[[Category:Requirements Template]]</noinclude>
</tr>
 
<tr>
 
<td bgcolor=#c0c0ff>
 
<b><font size=3 color=#202020>{{:{{#titleparts:{{{page}}}|3|1}}/Requirement/{{{num}}}{{#switch:{{SUBPAGENAME}}|es=/es|fr=/fr}}}}</font></b>
 
</td></tr>
 
</table>
 
<!--create collapsible box for the answers-->
 
<!--div class="toccolours mw-collapsible mw-collapsed" style="width:100%"-->
 
<div class="toccolours mw-collapsible" style="width:100%">
 
Answers
 
<div class="mw-collapsible-content">
 

Latest revision as of 03:48, 15 July 2021

This template is used to create the header and the answerbox of a requirement. The answerbox needs to be closed by using the CloseReq-Template.
For example like that:

{{Ansreq|num=1|page={{PAGENAME}}}}<nowiki />
Here you can write your answer. Any MediaWiki-Content is possible.
{{CloseReq}}

The <nowiki /> tag is needed so there is no unnecessary line break at the begining of the answer. For the Example the {{PAGENAME}} was replaced with a fixed name, but at an honor page the template will get the needed information out of the pagename.

If the page argument contains the word "Requirement" then the requirements are fetched directly from that page. If it doesn't, then we construct the requirements page by extracting the first two elements of the page (assumed to be "AY Honors/honor") and appending "/Requirements" to it. We need this to support variant requirements, as it allows us to specify

page=AY Honors/''honor''/Requirements_2

in the honor landing template.

1

Who are the Aborigines and where did they come from? How many tribes were there when European colonization commenced?

This is the example answer. Any MediaWiki-Content is possible (Tables, Templates, ...).