Template:Engineer infobox - Revision history

Sythan: Point documentation links at existing structured-data index module

2026-08-23T18:40:10Z

Point documentation links at existing structured-data index module

← Older revision		Revision as of 18:40, 23 August 2026
Line 4:		Line 4:

	When structured data exists for an Engineer, the template automatically uses		When structured data exists for an Engineer, the template automatically uses
	the canonical values stored in [[Module:Data/Engineers]]. Parameters supplied		the canonical values stored in [[Module:Data/Engineers/index\|Module:Data/Engineers/index]]. Parameters supplied
	directly on the article override those values when needed.		directly on the article override those values when needed.

Sythan at 18:36, 19 August 2026

2026-08-19T18:36:15Z

← Older revision		Revision as of 18:36, 19 August 2026
Line 1:		Line 1:
	{{#invoke:Engineers\|infobox}}<noinclude>		{{#invoke:Engineers\|infobox}}<noinclude>
	== Usage ==		== Usage ==
	~~Drop-in replacement~~ for ~~a bare {{tl\|Infobox}} call on~~ an Engineer ~~article.~~		Infobox for Elite Dangerous Engineer articles.
	~~Reads~~ canonical ~~facts from~~ [[Module:Data/Engineers]] ~~(one JSON page per~~
	~~Engineer) when one exists for this page; otherwise falls back to whatever~~		When structured data exists for an Engineer, the template automatically uses
	~~named parameters are passed~~ directly~~, so this template is safe to use~~ on		the canonical values stored in [[Module:Data/Engineers]]. Parameters supplied
	~~an Engineer with no JSON record yet~~.		directly on the article override those values when needed.

	<pre>		<pre>
	{{Engineer infobox		{{Engineer infobox
	\|name = Broo Tarquin		\|name = Broo Tarquin
	\|image = ~~(optional)~~		\|image =
	\|engineer_type = Ship (weapons)		\|engineer_type = Ship (weapons)
	\|system = Muang		\|system = Muang
	\|body = ~~(optional)~~		\|body =
	\|facility = Broo's Legacy		\|facility = Broo's Legacy
	\|region = ~~(optional)~~		\|region =
	\|allegiance = ~~(optional)~~		\|allegiance =
	\|specialties = Beam, Burst, and Pulse Laser modifications		\|specialties = Beam, Burst, and Pulse Laser modifications
	\|max_grade = ~~(optional)~~		\|max_grade =
	\|prerequisite_engineer = ~~(optional — omit if none)~~		\|prerequisite_engineer =
	\|discovery_requirement = Referral from Hera Tani		\|discovery_requirement = Referral from Hera Tani
	\|invitation_requirement = Combat rank Competent or higher		\|invitation_requirement = Combat rank Competent or higher
Line 26:		Line 26:
	</pre>		</pre>

	Empty~~/omitted fields~~ are hidden automatically~~, same as {{tl\|Infobox}}~~		Empty parameters are hidden automatically.
	~~itself — no manual row numbering needed either way. To add~~ or ~~update the~~
	canonical ~~JSON record for an Engineer instead of passing params by hand~~,		For information about adding or updating canonical structured data, see
	~~see~~ [[Elite Dangerous Field Manual:Adding Structured Data]].		[[Elite Dangerous Field Manual:Adding Structured Data]].

	<templatedata>		<templatedata>
	{		{
	"description": "Engineer infobox for Elite Dangerous Engineer articles. Article parameters override structured Engineer data defaults~~, so these fields can be edited directly from VisualEditor or source edit~~.",		"description": "Engineer infobox for Elite Dangerous Engineer articles. Article parameters override structured Engineer data defaults.",
	"format": "block",		"format": "block",
	"params": {		"params": {
Line 50:		Line 50:
	"engineer_type": {		"engineer_type": {
	"label": "Engineer type",		"label": "Engineer type",
	"description": "Broad type/category of Engineer.",		"description": "Broad type or category of Engineer.",
	"type": "string",		"type": "string",
	"suggested": true		"suggested": true
Line 56:		Line 56:
	"system": {		"system": {
	"label": "System",		"label": "System",
	"description": "System where the Engineer is located~~. Wikitext links are allowed~~.",		"description": "System where the Engineer is located.",
	"type": "wiki-page-name",		"type": "wiki-page-name",
	"suggested": true		"suggested": true
Line 62:		Line 62:
	"body": {		"body": {
	"label": "Body",		"label": "Body",
	"description": "Planet, moon, or body if applicable.",		"description": "Planet, moon, or other body if applicable.",
	"type": "string"		"type": "string"
	},		},
	"facility": {		"facility": {
	"label": "Facility",		"label": "Facility",
	"description": "Engineer base/facility name.",		"description": "Engineer base or facility name.",
	"type": "string",		"type": "string",
	"suggested": true		"suggested": true
Line 78:		Line 78:
	"allegiance": {		"allegiance": {
	"label": "Allegiance",		"label": "Allegiance",
	"description": "Faction/superpower allegiance if applicable.",		"description": "Faction or superpower allegiance if applicable.",
	"type": "string"		"type": "string"
	},		},
Line 89:		Line 89:
	"max_grade": {		"max_grade": {
	"label": "Maximum grade",		"label": "Maximum grade",
	"description": "Highest engineering grade offered, if useful as a ~~single~~ summary ~~field~~.",		"description": "Highest engineering grade offered, when useful as a summary.",
	"type": "string"		"type": "string"
	},		},
	"prerequisite_engineer": {		"prerequisite_engineer": {
	"label": "Prerequisite Engineer",		"label": "Prerequisite Engineer",
	"description": "Engineer referral prerequisite~~, or None~~ if ~~available from the start~~.",		"description": "Engineer referral prerequisite. Omit if no prerequisite Engineer is required.",
	"type": "string",		"type": "string"
	~~"suggested": true~~
	},		},
	"discovery_requirement": {		"discovery_requirement": {
Line 106:		Line 105:
	"invitation_requirement": {		"invitation_requirement": {
	"label": "Invitation requirement",		"label": "Invitation requirement",
	"description": "Requirement for receiving an invitation.",		"description": "Requirement for receiving an invitation from this Engineer.",
	"type": "string",		"type": "string",
	"suggested": true		"suggested": true
Line 112:		Line 111:
	"unlock_requirement": {		"unlock_requirement": {
	"label": "Unlock requirement",		"label": "Unlock requirement",
	"description": "Commodity/task required to unlock workshop access.",		"description": "Commodity, material, or task required to unlock workshop access.",
	"type": "string",		"type": "string",
	"suggested": true		"suggested": true

Sythan: Document Engineer infobox fields for VisualEditor

2026-08-13T03:49:13Z

Document Engineer infobox fields for VisualEditor

@@ Line 30: / Line 30: @@
 canonical JSON record for an Engineer instead of passing params by hand,
 see [[Elite Dangerous Field Manual:Adding Structured Data]].
 [[Category:Templates]]
 </noinclude>

Sythan: New: Lua-backed infobox wrapper for Engineer articles (Shape B)

2026-08-07T22:05:44Z

New: Lua-backed infobox wrapper for Engineer articles (Shape B)

New page

{{#invoke:Engineers|infobox}}<noinclude>
== Usage ==
Drop-in replacement for a bare {{tl|Infobox}} call on an Engineer article.
Reads canonical facts from [[Module:Data/Engineers]] (one JSON page per
Engineer) when one exists for this page; otherwise falls back to whatever
named parameters are passed directly, so this template is safe to use on
an Engineer with no JSON record yet.

<pre>
{{Engineer infobox
|name = Broo Tarquin
|image = (optional)
|engineer_type = Ship (weapons)
|system = Muang
|body = (optional)
|facility = Broo's Legacy
|region = (optional)
|allegiance = (optional)
|specialties = Beam, Burst, and Pulse Laser modifications
|max_grade = (optional)
|prerequisite_engineer = (optional — omit if none)
|discovery_requirement = Referral from Hera Tani
|invitation_requirement = Combat rank Competent or higher
|unlock_requirement = Deliver 50 units of Fujin Tea
}}
</pre>

Empty/omitted fields are hidden automatically, same as {{tl|Infobox}}
itself — no manual row numbering needed either way. To add or update the
canonical JSON record for an Engineer instead of passing params by hand,
see [[Elite Dangerous Field Manual:Adding Structured Data]].
[[Category:Templates]]
</noinclude>