Welcome to the Lylat Wiki, all about the Star Fox series! If you'd like to help out, please take a look at our community portal.

Difference between revisions of "Help:Infoboxes"

From Lylat Wiki, your source on Star Fox information. By Fans, for Fans.
Jump to navigationJump to search
No change in size ,  17:43, 30 August 2010
no edit summary
Line 32: Line 32:
| InfoDetails = {{{pie}}}
| InfoDetails = {{{pie}}}
}}
}}
<!-- {{infoboxentry}} -->
<!-- {{InfoBoxEntry}} -->
{{InfoBoxEnd v2.0
{{InfoBoxEnd v2.0
| name = WkiInfoBox v2.0
| name = WkiInfoBox v2.0
Line 64: Line 64:
| InfoDetails = {{{pie}}}
| InfoDetails = {{{pie}}}
}}
}}
<!-- {{infoboxentry}} -->
<!-- {{InfoBoxEntry}} -->
{{InfoBoxEnd v2.0
{{InfoBoxEnd v2.0
| name = WkiInfoBox v2.0
| name = WkiInfoBox v2.0
Line 71: Line 71:




Each row in the table has 2 cells: Info#name and Info#details, where # is the row number. [[Template:InfoBoxBegin v2.0]] has room for 5 rows, and [[Template:infoboxentry v2.0]] can dynamically add a row for each time it's used. [[Template:InfoBoxBegin v2.0]] and [[Template:InfoBoxEnd v2.0]] complete the box with all the needed info.  
Each row in the table has 2 cells: Info#name and Info#details, where # is the row number. [[Template:InfoBoxBegin v2.0]] has room for 5 rows, and [[Template:InfoBoxEntry v2.0]] can dynamically add a row for each time it's used. [[Template:InfoBoxBegin v2.0]] and [[Template:InfoBoxEnd v2.0]] complete the box with all the needed info.  


== Parameters ==
== Parameters ==
when using a infobox within another template, like [[Template:VehicleInfobox v2.0]], you can specify the name of each row to something related to related usage of the template. In our example above, We are expecting this particular infobox to be used on Fruit related pages; therefore we told the template we are inheriting that we want the 5 fields to be called: Colors, Taste, Baked, Salted and "related info".  
when using a infobox within another template, like [[Template:VehicleInfoBox v2.0]], you can specify the name of each row to something related to related usage of the template. In our example above, We are expecting this particular infobox to be used on Fruit related pages; therefore we told the template we are inheriting that we want the 5 fields to be called: Colors, Taste, Baked, Salted and "related info".  


Now, being we are using multiple layers of embedding templates, we want to make sure the end user's information is pass through our template and up to the core infobox template that actaully uses the infomation. This is where the parameters with a varible on the end come in handy. They look like <nowiki>| Info4details = {{{salted|}}}</nowiki> and if the end user specifies a value for "salted", we take it and pass it along as "Info4details". Neat, isn't it?
Now, being we are using multiple layers of embedding templates, we want to make sure the end user's information is pass through our template and up to the core infobox template that actaully uses the infomation. This is where the parameters with a varible on the end come in handy. They look like <nowiki>| Info4details = {{{salted|}}}</nowiki> and if the end user specifies a value for "salted", we take it and pass it along as "Info4details". Neat, isn't it?

Navigation menu