Template:Character infobox2/doc

From Herocopia
Jump to: navigation, search

Description[edit]

  • This template produces a character infobox in the upper right hand corner of character pages.
  • When editing a character page for the first time, copy and paste the base text from the syntax box directly below.
  • Then fill in the parameters with data and information as best you can for the character you are working on.
  • Existing pages should already have a call to this template installed. If not, please add one and work from it going forward.
  • A sample of a typical character page, with most of the parameters filled in is shown below. You can also open up a current page for editing and examine its usage of this character infobox2 template.

Syntax[edit]

{{character infobox2
|image        = Image:NIA3.gif
|imagewidth   = 300px
|status       = Active || Inactive || Deceased || Retired
|realname     = 
|debut        = <issue>
|earliest     = <in world date>
|origin       = <issue>
|affiliation  =
|baseops      =
|rangeops     =

|relatives    =
|aliases      =
|occupation   =
|birthdate    =
|maritalstatus =
|height       =
|weight       =
|eyes         = 
|hair         = 

|headlines    = <in world date and Headline>
|appearances  = <issue list>
}}

Notes[edit]

  • There is a logic glitch in this template that needs fixing. For now don't use the Box Title Parameter unless you intend to override it. In general, it is best to not to use it.
  • There is another logic glitch in this template for images. Please, if you don't have an image to reference, just keep the Image parameter reference pointing to Sample320.gif. Thanks.
  • There are three sections to a Character Infobox. They are AstroFacts, Personal Data and InfoDump. Each section has predefined statistic(stat) fields. All are shown above. The flexibility of the template determines where the stat field will be placed inside the overall infobox section.
  • Keeping a stat (any stat) empty will result in displaying no information and usually no title either.
  • There is also the capability of doing roll-your-own stats, with roll-your-own-titles. See the next section for more information on that.

Sample output[edit]

Sample.gif
Character infobox2/doc
RexZorus.jpg
© Juke Box Productions


AstroFacts


Status: Active
Real Name: Rex Zorus
Origin: March 1972 as shown in Astro City: The Dark Age Book One #2
Affiliation: First Family
Base of Operations: Currently: First Family's Headquarters

Prior to joining First Family: Monstro City(assumed)

Range of Operations: International, interplanetary, intergalactic and inter-dimensional


Personal Data


Relatives: <add list>
Aliases: Tyranos Rex, Rex Majestros
Date of Birth: Based on commentary from Royal Williams in Book One of the Dark Age Series, his estimated birth-year would be somewhere in the late 1950s, assuming his race ages at the same rate as surface dwelling humans. It is further assumed that his birthplace and childhood residency is Monstro City.
Civil Status: married
Height: (estimated): 6' 3"
Weight: (estimated): 500 lbs


InfoDump


Headlines: June 8 (or 9), 1986: Rex and Natalie: It's A Girl!
Appearances (in Publication Order): Kurt Busiek's Astro City Vol. 1 #4, 6

Wizard Presents: Kurt Busiek's Astro City Vol. 2 #1/2

Kurt Busiek's Astro City Vol. 2 #1, 2, 3, 4, 6, 8, 20

Astro City: The Dark Age Book One #2, 3, 4

Astro City Special: Samaritan

Astro City: The Dark Age Book Two #1, 3, 4

Astro City: The Dark Age Book Three #1, 3, 4

Astro City Special: Astra #1, 2

Astro City: The Dark Age Book Four #3


Event Timeline

Sample.gif



Typical Character infobox2:
{{Character infobox2
|Box title =
|image = Image:RexZorus.jpg
|status = Active
|realname = Rex Zorus
|debut = Kurt Busiek's Astro City Vol. 1 #4
|origin = March 1972 as shown in Astro City: The Dark Age Book One #2
|affiliation = First Family
|baseops = Currently: First Family's Headquarters
Prior to joining First Family: Monstro City(assumed)
|rangeops = International, interplanetary, intergalactic and inter-dimensional

|relatives = <add list>
|aliases = Tyranos Rex, Rex Majestros
|occupation =
|birthdate =
Based on commentary from Royal Williams in Book One of the Dark Age Series, his estimated birth-year would be somewhere in the late 1950s, assuming his race ages at the same rate as surface dwelling humans. It is further assumed that his birthplace and childhood residency is Monstro City.
|maritalstatus = married
|height = (estimated): 6' 3"
|weight = (estimated): 500 lbs
|eyes = test
|hair =

|headlines = June 8 (or 9), 1986: Rex and Natalie: It's A Girl!
|appearances = Kurt Busiek's Astro City Vol. 1 #4, 6
Wizard Presents: Kurt Busiek's Astro City Vol. 2 #1/2
Kurt Busiek's Astro City Vol. 2 #1, 2, 3, 4, 6, 8, 20
Astro City: The Dark Age Book One #2, 3, 4
Astro City Special: Samaritan
Astro City: The Dark Age Book Two #1, 3, 4
}}



Roll-Your-Own Stats For Character infobox2[edit]

... with Roll-Your-Own Titles.

Think of these as Totally Optional Template Options that provide additional flexibility to this template for building infoboxes for things other than characters. In constructing this template, I made it lean heavily to the needs of an individual character for content and topics, yet it is also very flexible, and yes you can indeed add a option for team members.

Here's a current example for Apollo11.

|PD1title      = Members:
|PD1info       = Garrison, Carruthers, McCaleb, eight others so far unnamed

Each section of the infobox (AstroFacts, PersonalData, and InfoDump) have three of these title-info pairs. We can add more if needed. We can also promote an Optional-option to permanent-option if we find the particular topic keeps cropping up. The difference between these is you must provide a title (which can be anything you want it to be) to go along with the info, and you must pair the names correctly


PD1title
PD1info

PD2title
PD2info

PD3title
PD3info

AF1title
AF1info

AF2title
AF2info

AF3title
AF3info

ID1title
ID1info

ID2title
ID2info

ID3title
ID3info


If it warrants it, I can see a Team Template as something that will probably be built in the future. I am OK with using this one template for now. Let's try it for awhile, and see if the need is strong enough for doing a team one. Or maybe, given its dynamics and flexibility, this template needs a different name.