Template:Article header: Difference between revisions

Current answers. Practical procedures. Reliable reference.
Jump to navigation Jump to search
No edit summary
Render linked contextual article eyebrow segments
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
<p class="edfm-eyebrow noexcerpt">{{{eyebrow|{{{1|}}}}}}</p>{{#if:{{{deck|}}}|<p class="edfm-deck">{{{deck|}}}</p>}}<noinclude>
<p class="edfm-eyebrow noexcerpt">EDFM // {{#invoke:PageContext|renderEyebrowBody|page={{{page|}}}|section={{{section|}}}|topic={{{topic|}}}|context={{{context|}}}|secondaryContext={{{secondaryContext|}}}|type={{{type|}}}|contentType={{{contentType|}}}}}</p>{{#if:{{{deck|}}}|<p class="edfm-deck">{{{deck|}}}</p>}}<noinclude>
== Usage ==
== Usage ==
Optional. Adds a small category "eyebrow" label above the page's real
Adds the EDFM context eyebrow and/or a muted one-line description ("deck") near the article title.
title, and/or a muted one-line description ("deck") directly under it —
see the redesign brief's Article header mockup:


<pre>
Normal pages should not provide an eyebrow manually. [[Module:PageContext]] resolves three separate semantic dimensions:
EDFM // COMMANDER REFERENCE
 
* primary topic/section, such as <code>Engineering</code>, <code>Mining</code>, or <code>Ships & Equipment</code>;
* optional secondary context, such as <code>Ships</code>, <code>Modules</code>, <code>Weapons</code>, or <code>Engineers</code>;
* optional content type, currently used for meaningful types such as <code>Field Procedures</code>.


TOOLS & RESOURCES
The visible eyebrow intentionally stays compact: <code>EDFM //</code> plain text followed by a linked primary section and, at most, one second segment. Content type takes display priority over ordinary secondary context.


Community tools, applications and services commonly used by commanders.
<pre>
{{Article header
|deck=Optional one-line description shown under the title.
}}
</pre>
</pre>


Placement in the wikitext doesn't matter (top of the article is
Use <code>section=</code>, <code>context=</code>, and/or <code>type=</code> only for genuine exceptions that cannot be resolved from structured data or central rules:
conventional) — a small script in [[MediaWiki:Common.js]] moves the
eyebrow line to sit visually above [[MediaWiki:Common.css|#firstHeading]]
on page load. The real page title stays the genuine, semantic H1 the whole
time; this only adds text before/after it, it never replaces it. If a
reader has JavaScript disabled, the eyebrow still renders — directly under
the title instead of above it — so nothing is lost, only the exact
placement changes.


<pre>
<pre>
{{Article header
{{Article header
  |eyebrow=EDFM // Commander Reference
  |section=Engineering
|context=Engineers
|type=Field Procedures
  |deck=Optional one-line description shown under the title.
  |deck=Optional one-line description shown under the title.
}}
}}
</pre>
</pre>


Both parameters are optional; using just <code>eyebrow=</code> or just
The rendered eyebrow is presentation text such as <code>EDFM // [[Engineering]] / [[Field Procedures]]</code>. The real page title remains the semantic H1. [[MediaWiki:Common.js]] moves the eyebrow above the H1 visually when JavaScript is available; without JavaScript it remains in article content below the H1.
<code>deck=</code> is fine.


[[Category:Templates]]
[[Category:Templates]]
</noinclude>
</noinclude>

Latest revision as of 21:58, 24 August 2026

EDFM // Reference

Usage

Adds the EDFM context eyebrow and/or a muted one-line description ("deck") near the article title.

Normal pages should not provide an eyebrow manually. Module:PageContext resolves three separate semantic dimensions:

  • primary topic/section, such as Engineering, Mining, or Ships & Equipment;
  • optional secondary context, such as Ships, Modules, Weapons, or Engineers;
  • optional content type, currently used for meaningful types such as Field Procedures.

The visible eyebrow intentionally stays compact: EDFM // plain text followed by a linked primary section and, at most, one second segment. Content type takes display priority over ordinary secondary context.

{{Article header
 |deck=Optional one-line description shown under the title.
}}

Use section=, context=, and/or type= only for genuine exceptions that cannot be resolved from structured data or central rules:

{{Article header
 |section=Engineering
 |context=Engineers
 |type=Field Procedures
 |deck=Optional one-line description shown under the title.
}}

The rendered eyebrow is presentation text such as EDFM // Engineering / Field Procedures. The real page title remains the semantic H1. MediaWiki:Common.js moves the eyebrow above the H1 visually when JavaScript is available; without JavaScript it remains in article content below the H1.