Template:Infobox - Revision history

Coreo: adding links to some sources I'm using to figure this out, and suggestion that my building notes should move to discussion eventually

2024-04-25T23:50:51Z

adding links to some sources I'm using to figure this out, and suggestion that my building notes should move to discussion eventually

← Older revision		Revision as of 23:50, 25 April 2024
Line 2:		Line 2:

	<H1>Building notes</H1>		<H1>Building notes</H1>
	This is our initial practice infobox template. It should take the page title as its title, it has room for an image, etc.		This is our initial practice infobox template. It should take the page title as its title, it has room for an image, etc. I have been looking at this essay for advice on the "classic infobox" kinds of infobox: https://meta.miraheze.org/wiki/Infoboxes

			And also looking at the author's own infobox examples on https://softcell.miraheze.org/wiki/Category:Infobox_templates

			And also the site CSS for that wiki at https://softcell.miraheze.org/wiki/MediaWiki:Common.css

			(BTW, I'm hoping to move these build notes to discussion page eventually; please do that instead of deleting this, when it's time?)

	The template offers the fields infobox-title, infobox-image, name, age, hometown, sign, and blood type as example fields.		The template offers the fields infobox-title, infobox-image, name, age, hometown, sign, and blood type as example fields.
Line 13:		Line 19:

	Infobox-image isn't loading, however. And I am still trying to understand how the infobox-title part and PAGENAME in brackets actually work, as well as the image stuff. That having been said much of this template is working and is modifiable to create other infoboxes! Back to the template syntax mines I go!		Infobox-image isn't loading, however. And I am still trying to understand how the infobox-title part and PAGENAME in brackets actually work, as well as the image stuff. That having been said much of this template is working and is modifiable to create other infoboxes! Back to the template syntax mines I go!

			<H1>How to use this template</H1>

	</noinclude>		</noinclude>

Coreo: adding header to noinclude

2024-04-25T23:10:45Z

adding header to noinclude

← Older revision		Revision as of 23:10, 25 April 2024
Line 1:		Line 1:
	<noinclude>This is our initial practice infobox template. It should take the page title as its title, it has room for an image, etc.		<noinclude>

			<H1>Building notes</H1>
			This is our initial practice infobox template. It should take the page title as its title, it has room for an image, etc.

	The template offers the fields infobox-title, infobox-image, name, age, hometown, sign, and blood type as example fields.		The template offers the fields infobox-title, infobox-image, name, age, hometown, sign, and blood type as example fields.

Coreo: minor editing of my own progress notes

2024-04-25T23:09:26Z

minor editing of my own progress notes

← Older revision		Revision as of 23:09, 25 April 2024
Line 5:		Line 5:
	Infobox code itself starts with the if statement after the table class element, and defines the first parameter to fill out in the infobox, in this case age.		Infobox code itself starts with the if statement after the table class element, and defines the first parameter to fill out in the infobox, in this case age.

	In this code, infobox-title is doing the work of a name field, so I took it out, but we could define a separate name field.		In this code, infobox-title is doing the work of a name field, so I took out an explicit name field, but we could define a separate name field. We could also add logic to make the use of the infobox-title part optional, if we want. Right now it seems to be included automatically, and I think using it will work on all of the infoboxes we want to implement.

	At this point I have all of the parameters, Age, Hometown, Sign, Type loading.		At this point I have all of the parameters, Age, Hometown, Sign, Type loading.

Coreo: Documenting where I have gotten to with this template

2024-04-25T23:07:51Z

Documenting where I have gotten to with this template

← Older revision		Revision as of 23:07, 25 April 2024
Line 3:		Line 3:
	The template offers the fields infobox-title, infobox-image, name, age, hometown, sign, and blood type as example fields.		The template offers the fields infobox-title, infobox-image, name, age, hometown, sign, and blood type as example fields.

	~~I think~~ the if statement ~~looking for a param1 is simple logic saying that if there's another~~ parameter ~~listed at the end it interprets that as~~ the ~~thing coming up next. But I'm not sure~~.		Infobox code itself starts with the if statement after the table class element, and defines the first parameter to fill out in the infobox, in this case age.

	~~The name field is redundant in~~ this ~~infobox~~, ~~because~~ infobox-title is doing ~~that~~ work. so I~~'m taking that~~ out.		In this code, infobox-title is doing the work of a name field, so I took it out, but we could define a separate name field.

	~~Right now~~ the "Age~~" line and "age" info are not~~ loading ~~on this infobox over in the example~~, ~~and~~ I ~~cannot figure out why. neither is~~ the infobox-image ~~part~~. ~~Also I'm confused about why I have such big escapes in some parts~~ of ~~the css,~~ and ~~trying~~ to ~~parse what they really mean.I think I'm using infobox-title wrong but I'm trying~~ to ~~understand what this~~ template ~~form actually Eexpects.~~		At this point I have all of the parameters, Age, Hometown, Sign, Type loading.

			Infobox-image isn't loading, however. And I am still trying to understand how the infobox-title part and PAGENAME in brackets actually work, as well as the image stuff. That having been said much of this template is working and is modifiable to create other infoboxes! Back to the template syntax mines I go!

	</noinclude>		</noinclude>

Coreo: more notes to self about testing this template.

2024-04-25T21:59:17Z

more notes to self about testing this template.

← Older revision		Revision as of 21:59, 25 April 2024
Line 6:		Line 6:

	The name field is redundant in this infobox, because infobox-title is doing that work. so I'm taking that out.		The name field is redundant in this infobox, because infobox-title is doing that work. so I'm taking that out.

			Right now the "Age" line and "age" info are not loading on this infobox over in the example, and I cannot figure out why. neither is the infobox-image part. Also I'm confused about why I have such big escapes in some parts of the css, and trying to parse what they really mean.I think I'm using infobox-title wrong but I'm trying to understand what this template form actually Eexpects.

	</noinclude>		</noinclude>

Coreo: editing first param

2024-04-25T21:50:39Z

editing first param

← Older revision		Revision as of 21:50, 25 April 2024
Line 11:		Line 11:
	<div class="infobox-title">{{{Title\|{{PAGENAME}}}}}</div>{{#if:{{{image\|}}}\|		<div class="infobox-title">{{{Title\|{{PAGENAME}}}}}</div>{{#if:{{{image\|}}}\|
	<div class="infobox-image">[[File:{{PAGENAME:{{{image}}}}}\|300px]]</div>}}		<div class="infobox-image">[[File:{{PAGENAME:{{{image}}}}}\|300px]]</div>}}
	<table class="infobox-table">{{#if:{{{~~Age~~\|}}}\|<tr>		<table class="infobox-table">{{#if:{{{age\|}}}\|<tr>
	<th>Age</th>		<th>Age</th>
	<td>{{{age}}}</td>		<td>{{{age}}}</td>

Coreo: Editing beginning of infobox to point to the next item after the title and image parts correctly

2024-04-25T21:42:12Z

Editing beginning of infobox to point to the next item after the title and image parts correctly

← Older revision		Revision as of 21:42, 25 April 2024
Line 11:		Line 11:
	<div class="infobox-title">{{{Title\|{{PAGENAME}}}}}</div>{{#if:{{{image\|}}}\|		<div class="infobox-title">{{{Title\|{{PAGENAME}}}}}</div>{{#if:{{{image\|}}}\|
	<div class="infobox-image">[[File:{{PAGENAME:{{{image}}}}}\|300px]]</div>}}		<div class="infobox-image">[[File:{{PAGENAME:{{{image}}}}}\|300px]]</div>}}
	<table class="infobox-table">{{#if:{{{~~param1~~\|}}}\|<tr>		<table class="infobox-table">{{#if:{{{Age\|}}}\|<tr>
	<th>Age</th>		<th>Age</th>
	<td>{{{age}}}</td>		<td>{{{age}}}</td>

Coreo: removing redundant name field

2024-04-25T21:39:50Z

removing redundant name field

← Older revision		Revision as of 21:39, 25 April 2024
Line 3:		Line 3:
	The template offers the fields infobox-title, infobox-image, name, age, hometown, sign, and blood type as example fields.		The template offers the fields infobox-title, infobox-image, name, age, hometown, sign, and blood type as example fields.

	I think the if statement looking for a param1 is simple logic saying that if there's another parameter listed at the end it interprets that as the thing coming up next. But I'm not sure. </noinclude>		I think the if statement looking for a param1 is simple logic saying that if there's another parameter listed at the end it interprets that as the thing coming up next. But I'm not sure.

			The name field is redundant in this infobox, because infobox-title is doing that work. so I'm taking that out.

			</noinclude>
	<div class="infobox">		<div class="infobox">
	<div class="infobox-title">{{{Title\|{{PAGENAME}}}}}</div>{{#if:{{{image\|}}}\|		<div class="infobox-title">{{{Title\|{{PAGENAME}}}}}</div>{{#if:{{{image\|}}}\|
	<div class="infobox-image">[[File:{{PAGENAME:{{{image}}}}}\|300px]]</div>}}		<div class="infobox-image">[[File:{{PAGENAME:{{{image}}}}}\|300px]]</div>}}
	<table class="infobox-table">{{#if:{{{param1\|}}}\|<tr>		<table class="infobox-table">{{#if:{{{param1\|}}}\|<tr>
	~~<th>Name</th>~~
	~~<td>{{{name}}}</td>~~
	~~</tr>}}{{#if:{{{age\|}}}\|<tr>~~
	<th>Age</th>		<th>Age</th>
	<td>{{{age}}}</td>		<td>{{{age}}}</td>

Coreo: adding to noinclude about how this works

2024-04-25T21:37:42Z

adding to noinclude about how this works

← Older revision		Revision as of 21:37, 25 April 2024
Line 1:		Line 1:
	<noinclude>This is our initial practice infobox template. It should take the page title as its title, it has room for an image, ~~and there's an if parameter statement I'm still trying to understand (I got it from somewhere else~~.)		<noinclude>This is our initial practice infobox template. It should take the page title as its title, it has room for an image, etc.

	The template offers the fields name, age, hometown, sign, and blood type as example fields. </noinclude>		The template offers the fields infobox-title, infobox-image, name, age, hometown, sign, and blood type as example fields.

			I think the if statement looking for a param1 is simple logic saying that if there's another parameter listed at the end it interprets that as the thing coming up next. But I'm not sure. </noinclude>
	<div class="infobox">		<div class="infobox">
	<div class="infobox-title">{{{Title\|{{PAGENAME}}}}}</div>{{#if:{{{image\|}}}\|		<div class="infobox-title">{{{Title\|{{PAGENAME}}}}}</div>{{#if:{{{image\|}}}\|

Coreo: adding documentation in noinclude

2024-04-25T21:34:19Z

adding documentation in noinclude

← Older revision		Revision as of 21:34, 25 April 2024
Line 1:		Line 1:
	<noinclude>This is our initial practice infobox. </noinclude>		<noinclude>This is our initial practice infobox template. It should take the page title as its title, it has room for an image, and there's an if parameter statement I'm still trying to understand (I got it from somewhere else.)

			The template offers the fields name, age, hometown, sign, and blood type as example fields. </noinclude>
	<div class="infobox">		<div class="infobox">
	<div class="infobox-title">{{{Title\|{{PAGENAME}}}}}</div>{{#if:{{{image\|}}}\|		<div class="infobox-title">{{{Title\|{{PAGENAME}}}}}</div>{{#if:{{{image\|}}}\|