Sythan: Document linked primary secondary content-type eyebrow resolver

2026-08-24T22:04:03Z

Document linked primary secondary content-type eyebrow resolver

Show changes

Sythan: Document two-dimensional article eyebrow context resolution

2026-08-24T21:43:28Z

Document two-dimensional article eyebrow context resolution

Show changes

Sythan: Document centralized article eyebrow section resolution

2026-08-24T21:31:32Z

Document centralized article eyebrow section resolution

New page

{{Article header|section=Operations|deck=How EDFM resolves article header eyebrows from page context instead of page-title duplication.}}

EDFM article pages use a centralized section resolver so the eyebrow above the page title answers '''where in EDFM the reader is''', while the H1 answers '''what page the reader is reading'''.

Normal output should look like:

<pre>
EDFM // Ships & Equipment
Frame Shift Drive
</pre>

rather than repeating the page title in the eyebrow.

== Normal author workflow ==

Most pages should use:

<pre>
{{Article header|deck=Optional one-line page summary.}}
</pre>

Do not normally set an eyebrow manually. The header calls [[Module:PageContext]], which resolves the section automatically from structured data and central rules.

== Resolution order ==

The resolver checks, in order:

# '''Explicit override''' — <code>{{Article header|section=Combat}}</code>. Use only when the central resolver cannot reasonably infer the section.
# '''Exact central section mappings''' — section and hub pages such as [[Engineering]], [[Mining]], [[Powerplay]], and [[Ships and Equipment]].
# '''Structured page/content type''' — existing canonical data/index pages, including Engineers, ship modules, mining datasets, and field-procedure datasets.
# '''Page-family rules''' — conservative families such as <code>Unlocking ...</code> and <code>How to ...</code>, which resolve to [[Field Procedures]].
# '''Limited topic-family rules''' — documented conservative title-family signals such as Guardian, Thargoid/Xeno, and AX naming.
# '''Fallback''' — unknown pages resolve to <code>Reference</code>.

== Structured type mappings ==

Structured page type mappings live in [[Module:Data/PageSections]]. Current mappings include:

* Engineer pages from <code>Module:Data/Engineers/index</code> → '''Engineering'''
* Ship module pages from <code>Module:Data/ShipModules/index</code> and <code>Module:Data/Modules/index</code> → '''Ships & Equipment'''
* Guardian module pages identified through the module index and Guardian naming → '''Guardian Technology'''
* Thargoid/Xeno/AX module pages identified through the module index and xeno naming → '''Thargoids'''
* Mining method/equipment/location/commodity datasets → '''Mining'''
* Mining procedure dataset pages → '''Field Procedures'''

If EDFM adds a new canonical dataset, add a lightweight detector in [[Module:PageContext]] and map the resulting type in [[Module:Data/PageSections]]. Do not duplicate every individual page into a hand-maintained lookup table.

== Page-family rules ==

Page-family rules are centralized in [[Module:Data/PageSections]]. They are for predictable editorial families that may not have a complete structured dataset yet.

Current examples:

* <code>Unlocking ...</code> → '''Field Procedures'''
* <code>How to ...</code> → '''Field Procedures'''

Keep these conservative. Do not add fuzzy keyword guessing.

== Exceptional overrides ==

Use an article-level override only when a page is intentionally cross-topic or cannot be identified cleanly from data/rules:

<pre>
{{Article header
|section=Operations
|deck=Optional one-line summary.
}}
</pre>

If many pages require overrides, improve the structured data or page-family rules instead.

== Adding a primary section ==

# Add the section name to <code>exactSections</code> in [[Module:Data/PageSections]] for its hub page.
# If the section corresponds to a structured dataset, add/adjust a page type detector in [[Module:PageContext]].
# Map the new page type in <code>typeToSection</code>.
# Test with <code>{{#invoke:PageContext|getSection|page=Example Page}}</code> and a rendered live page.

== Public Lua interface ==

[[Module:PageContext]] exposes:

* <code>getPageType</code> — returns a semantic type such as <code>engineer</code> or <code>ship_module</code> where known.
* <code>getSection</code> — returns a plain section name such as <code>Ships & Equipment</code>.
* <code>eyebrow</code> — returns rendered eyebrow text such as <code>EDFM // Ships & Equipment</code> for [[Template:Article header]].

== Testing ==

Representative parser tests:

<pre>
{{#invoke:PageContext|getSection|page=Frame Shift Drive}}
{{#invoke:PageContext|getSection|page=Felicity Farseer}}
{{#invoke:PageContext|getSection|page=Unlocking Broo Tarquin}}
{{#invoke:PageContext|getSection|page=Resolver Sandbox Unknown}}
{{#invoke:PageContext|getSection|page=Frame Shift Drive|section=Combat}}
</pre>

Then verify rendered pages include exactly one visible eyebrow, retain the semantic H1, and do not show Lua/script errors.

[[Category:EDFM project documentation]]

Elite Dangerous Field Manual:Page section resolution - Revision history

Sythan: Document linked primary secondary content-type eyebrow resolver

Sythan: Document two-dimensional article eyebrow context resolution

Sythan: Document centralized article eyebrow section resolution