Elite Dangerous Field Manual - User contributions [en]

MediaWiki:Common.css

2026-08-11T03:16:34Z

EDFM Maintenance: Constrain sidebar logo to fit raster artwork

/* ==========================================================================
EDFM site-wide styling -- "Elite Dangerous technical field manual" theme.
Original CSS written for this project -- no code or assets copied from
runescape.wiki, Elite Dangerous, or any other site/game, and no Frontier
logo/branding/proprietary fonts/copied HUD elements. Restrained visual
influence only: dark industrial surfaces, subtle angular geometry,
orange/cyan accents used sparingly, information hierarchy first. This is
a reference site, not a HUD -- no glow, no neon, no glassmorphism, no
constant animation.

SKIN NOTE: the site uses Vector "legacy" (2011), not Vector 2022 -- see
the "Why Vector legacy" note in docs/content-style-guide.md (Vector 2022
hard-restricts its pinned sidebar to logged-in users; legacy has no such
restriction). Several rules below exist specifically to beat core Vector
legacy/mediawiki.skinning selectors that are *more specific* than a naive
override would be (documented inline at each occurrence) -- this isn't
guesswork, each one was found by reading the actual core .less source and
confirmed with a real rendered screenshot, not just computed-style checks
(:visited colours in particular are invisible to getComputedStyle by
design -- see the tab-bar note below).

2026-08-07 SECOND PASS: the first redesign pass was judged too close to
stock MediaWiki with a colour change -- this pass changes the actual
visual composition (centred workspace instead of a huge dead gutter,
a two-tier header, a real masthead, a tile-grid TOC, a restructured
status module, larger deliberate type scale, depth via surface
elevation instead of borders-around-everything) while reusing every
working mechanism from the first pass rather than throwing it away --
the tab/:visited fix, the external-link specificity fix, the mobile
reorder fix, and focus-visible/reduced-motion are all still here,
unchanged in mechanism.
========================================================================== */

/* ==========================================================================
1. DESIGN TOKENS
========================================================================== */
:root {
/* Depth system: site (outermost, visible in the sidebar/header/gutters)
-> article surface -> component surfaces, each a deliberate step
brighter so the page reads as having actual depth rather than "one
background colour with slightly lighter boxes everywhere". */
--edfm-bg-deep: #07090b;
--edfm-bg-page: #0a0e11;
--edfm-surface-1: #10171b;
--edfm-surface-2: #161f24;
--edfm-surface-3: #1c272d;
--edfm-surface-4: #233037;

--edfm-border: #26333b;
--edfm-border-soft: rgba( 255, 255, 255, 0.06 );

--edfm-text: #edf0f2;
--edfm-text-muted: #98a5ad;
--edfm-text-dim: #6c7a82;

/* Accents -- orange is reserved for navigation/selection/emphasis/
section numbering; cyan/blue are for links, verification info, and
secondary interface elements. See "Links" and "Colour system" in
docs/content-style-guide.md for the reasoning. */
--edfm-orange: #ff8a00;
--edfm-orange-bright: #ffa21a;
--edfm-cyan: #42c7d9;
--edfm-blue: #4f9fe8;

/* Derived link colours */
--edfm-link: var( --edfm-blue );
--edfm-link-visited: #3f7bb3;
--edfm-link-hover: #8cc4f7;
--edfm-link-external: var( --edfm-cyan );
--edfm-link-external-visited: #2f8f9c;
--edfm-link-external-hover: #7fe0ec;
--edfm-link-new: #e07a7a;

/* Status semantics (article metadata module) -- text label always
present too, never colour-only. */
--edfm-status-positive: var( --edfm-cyan );
--edfm-status-attention: var( --edfm-orange );
--edfm-status-neutral: var( --edfm-text-dim );
--edfm-status-positive-bg: rgba( 66, 199, 217, 0.12 );
--edfm-status-attention-bg: rgba( 255, 138, 0, 0.12 );
--edfm-status-neutral-bg: rgba( 108, 122, 130, 0.12 );

/* Typography -- explicit desktop scale (2026-08-07 pass 2). Sized in
rem against the root's real 16px (Vector legacy's own
@font-size-root is 100%, i.e. browser default -- confirmed by
reading skins.vector.styles.legacy/variables.less, not assumed)
rather than nested em, specifically so component sizes can't
compound smaller than intended inside whatever ambient size an
ancestor happens to set. */
--edfm-fs-title: clamp( 1.9rem, 1.4rem + 2vw, 2.25rem ); /* ~30-36px */
--edfm-fs-h2: 1.35rem; /* ~21.6px */
--edfm-fs-h3: 1.15rem; /* ~18.4px */
--edfm-fs-body: 1rem; /* 16px */
--edfm-fs-resource-name: 1.1rem; /* ~17.6px */
--edfm-fs-meta: 0.8rem; /* ~12.8px */
--edfm-fs-sidebar: 0.9375rem; /* 15px -- polish pass: +1px for readability */
--edfm-fs-utility: 0.72rem; /* ~11.5px */

--edfm-mono: 'JetBrains Mono', 'Fira Code', Consolas, 'SF Mono', Menlo, 'Courier New', monospace;
--edfm-sans: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Helvetica, Arial, sans-serif;

/* Legacy aliases: earlier revisions of this stylesheet used these names
directly and some inline template output/older docs may still refer
to them; keep pointing at the current tokens rather than duplicate
values that could drift out of sync. */
--edfm-orange-hover: var( --edfm-orange-bright );
--edfm-orange-active: var( --edfm-orange-bright );
--color-progressive: var( --edfm-orange );
--color-progressive--hover: var( --edfm-orange-bright );
--color-progressive--active: var( --edfm-orange-bright );
--color-progressive--focus: var( --edfm-orange );
--background-color-progressive: var( --edfm-orange );
--background-color-progressive--hover: var( --edfm-orange-bright );
--background-color-progressive--active: var( --edfm-orange-bright );
--border-color-progressive: var( --edfm-orange );
--border-color-progressive--hover: var( --edfm-orange-bright );
--border-color-progressive--active: var( --edfm-orange-bright );

/* Geometry / layout */
--edfm-corner: 10px;
/* Full-width article workspace: keep the fixed Vector sidebar clear,
but let the article surface use the entire remaining viewport. */
--edfm-sidebar-width: 12.75rem;
--edfm-sidebar-clear: 12.75rem;
--edfm-content-max: calc( 100vw - var( --edfm-sidebar-clear ) );
--edfm-gutter: 0px;
}

/* ==========================================================================
2. BASE / RESET-ADJACENT
========================================================================== */
html, body {
background-color: var( --edfm-bg-page );
color: var( --edfm-text );
}
body.mediawiki {
color: var( --edfm-text );
font-family: var( --edfm-sans );
font-size: var( --edfm-fs-body );
}
/* Background treatment: a faint technical grid plus a very soft radial
glow centred behind the (now centred) content column, so the composition
still has quiet visual interest in the gutters on ultrawide screens
instead of just flat colour -- both stay under ~3% opacity, this is
texture, not a HUD. Not image assets; pure CSS gradients. */
body {
background-image:
radial-gradient( ellipse 1400px 900px at 50% 0%, rgba( 66, 199, 217, 0.05 ), transparent 60% ),
linear-gradient( rgba( 255, 255, 255, 0.025 ) 1px, transparent 1px ),
linear-gradient( 90deg, rgba( 255, 255, 255, 0.025 ) 1px, transparent 1px );
background-size: auto, 48px 48px, 48px 48px;
background-repeat: no-repeat, repeat, repeat;
background-attachment: fixed, scroll, scroll;
}
/* Full-height sidebar rail: mirrors the RuneScape.wiki behavior where the
left rail has no visible bottom edge. The real #mw-panel only carries the
navigation content; this fixed layer paints the uninterrupted surface,
border, and shadow down the whole viewport. */
body::before {
content: '';
position: fixed;
top: 0;
left: 0;
bottom: 0;
width: var( --edfm-sidebar-width );
background: linear-gradient( 180deg, var( --edfm-surface-1 ) 0%, var( --edfm-bg-deep ) 100% );
border-right: 1px solid var( --edfm-border );
box-shadow: 10px 0 22px rgba( 0, 0, 0, 0.32 );
pointer-events: none;
z-index: 1;
}
@media ( prefers-reduced-motion: reduce ) {
*, *::before, *::after {
animation-duration: 0.001ms !important;
animation-iteration-count: 1 !important;
transition-duration: 0.001ms !important;
scroll-behavior: auto !important;
}
}
/* Focus visibility: applies to every interactive element, not just links. */
a:focus-visible,
button:focus-visible,
input:focus-visible,
textarea:focus-visible,
select:focus-visible,
[tabindex]:focus-visible {
outline: 2px solid var( --edfm-cyan );
outline-offset: 2px;
}

/* Small reusable angular motif: a corner-cut bracket, used sparingly (see
the redesign notes in docs/content-style-guide.md for exactly where) --
deliberately not applied everywhere. */
.edfm-corner-cut {
clip-path: polygon( 0 0, calc( 100% - var( --edfm-corner ) ) 0, 100% var( --edfm-corner ), 100% 100%, 0 100% );
}

/* ==========================================================================
3. TYPOGRAPHY
========================================================================== */
h1, h2, h3, h4, h5, h6 {
color: var( --edfm-text );
border-color: var( --edfm-border );
}
/* !important justified here: MediaWiki core's mediawiki.skinning module
sets heading colour with equal-specificity plain-tag selectors and kept
winning in testing despite this stylesheet loading later -- rather than
keep chasing exact cascade/bundling order, force it. This is a
correctness/contrast fix, not decoration. */
.mw-body h1, .mw-body h2, .mw-body h3, .mw-body h4, .mw-body h5, .mw-body h6,
.mw-heading1, .mw-heading2, .mw-heading3, .mw-heading4, .mw-heading5, .mw-heading6,
h1, h2, h3, h4, h5, h6 {
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
font-family: var( --edfm-mono );
letter-spacing: 0.01em;
line-height: 1.3;
}
#firstHeading {
color: var( --edfm-text ) !important;
font-family: Georgia, 'Times New Roman', Times, serif;
font-size: clamp( 1.75rem, 1.35rem + 1.45vw, 2.15rem );
font-weight: 700;
letter-spacing: 0;
line-height: 1.18;
margin: 0.15em 0 0.25em;
padding-bottom: 0.22em;
border-bottom: 1px solid var( --edfm-border );
}
/* Section headings (h2): "// " prefix in orange, bright heading text, a
short orange accent segment over the dim full-width divider core
already draws. Substantially more vertical space than a wiki section
normally gets, per the "sections feel packed together" fix -- 3.25rem
(~52px) above, ~1.1rem gap to the first content component below. If a
heading opts into explicit numbering via {{Section number}}, the
automatic "// " is suppressed so the two treatments don't double up. */
.mw-body h2 {
position: relative;
padding-bottom: 0.25em;
margin-top: 2rem;
margin-bottom: 0.85rem;
font-family: Georgia, 'Times New Roman', Times, serif;
font-size: clamp( 1.28rem, 1.08rem + 0.65vw, 1.62rem );
font-weight: 500;
letter-spacing: 0;
border-bottom: 1px solid var( --edfm-border ) !important;
}
.mw-body h2::before {
content: none;
}
.mw-body h2:has( .edfm-section-number )::before {
content: none;
}
.mw-body h2::after {
content: '';
position: absolute;
left: 0;
bottom: -1px;
width: 3em;
max-width: 100%;
height: 2px;
background: var( --edfm-orange );
}
.edfm-section-number {
color: var( --edfm-orange );
font-weight: 700;
}
.edfm-section-sep {
color: var( --edfm-orange );
margin-right: 0.15em;
}
h3, h4 {
color: var( --edfm-text );
font-size: var( --edfm-fs-h3 );
}
h3::before {
content: '/ ';
color: var( --edfm-text-dim );
font-weight: 400;
}

/* Body text: readable sans-serif, deliberately NOT monospace -- long-form
reading in monospace hurts readability, which stays a hard requirement
even with a more technical visual language elsewhere. */
.mw-body p,
.mw-body li,
.mw-body dd {
line-height: 1.7;
font-size: var( --edfm-fs-body );
}
.mw-body p {
margin: 0 0 1.1em 0;
max-width: none !important; /* Site-wide full-width pass: article text should use the whole content rail. */
}
.mw-body ul,
.mw-body ol {
line-height: 1.7;
margin-bottom: 1.1em;
}
/* MW 1.46 wraps headings in a `.mw-heading2`/`.mw-heading3` div, so the
sibling that immediately follows is that wrapper, not the `h2`/`h3`
itself -- matching both forms since a page could still have a bare
heading in edge cases (e.g. content generated without the wrapper). */
.mw-heading2 + p, .mw-body h2 + p,
.mw-heading3 + p, .mw-body h3 + p,
.mw-heading2 + div, .mw-body h2 + div,
.mw-heading3 + div, .mw-body h3 + div {
margin-top: 0;
}
hr {
background-color: var( --edfm-border );
border-color: var( --edfm-border );
}

/* Quiet, discoverable section-edit controls (logged-in editors only --
MediaWiki only renders these for users who can edit). Keeping the
functionality/keyboard access intact while making sure they don't
compete visually with the heading they're attached to: low opacity at
rest, full opacity on hover/focus of the heading OR the control itself,
brackets hidden (the opacity+letter-spacing treatment already reads as
a distinct control without them). */
.mw-editsection {
margin-left: 1em;
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-utility ) !important;
font-weight: 700;
letter-spacing: 0.05em;
text-transform: uppercase;
opacity: 0.45;
transition: opacity 0.15s ease;
}
.mw-heading:hover .mw-editsection,
.mw-heading:focus-within .mw-editsection,
.mw-editsection:hover,
.mw-editsection:focus-within {
opacity: 1;
}
.mw-editsection a {
color: var( --edfm-text-dim );
}
.mw-editsection a:hover,
.mw-editsection a:focus-visible {
color: var( --edfm-cyan );
}
.mw-editsection-bracket {
display: none;
}
.mw-editsection-divider {
color: var( --edfm-text-dim );
margin: 0 0.3em;
}

/* ==========================================================================
8. LINKS
========================================================================== */
a { color: var( --edfm-link ); transition: color 0.1s ease; }
a:visited { color: var( --edfm-link-visited ); }
a:hover { color: var( --edfm-link-hover ); }
a.new, .new a { color: var( --edfm-link-new ); }
a.external { color: var( --edfm-link-external ); }
/* Core MediaWiki ships `.mw-parser-output a.external`/`a.extiw` (and their
:visited/:hover states) at higher specificity (two classes + a tag) than
a plain `a.external` rule (one class + a tag), so the line above never
actually wins for real article links on its own -- the same underlying
"core selector outranks a naive theme override" gotcha as the tab
:visited fix further down. Matching the same selector shape here (this
stylesheet loads after core skin styles) is what actually applies our
colour to external links in article content. */
.mw-parser-output a.external,
.mw-parser-output a.extiw {
color: var( --edfm-link-external );
}
.mw-parser-output a.external:visited,
.mw-parser-output a.extiw:visited {
color: var( --edfm-link-external-visited );
}
.mw-parser-output a.external:hover,
.mw-parser-output a.extiw:hover {
color: var( --edfm-link-external-hover );
}
.mw-footer a {
color: var( --edfm-link );
}
.mw-footer a:hover {
color: var( --edfm-link-hover );
}

/* ==========================================================================
1. GLOBAL LAYOUT -- centred workspace
========================================================================== */
/* Full-width article pass: the article now fills the workspace to the right edge.
Historical note: this block originally centred a capped article column.

THE fix for "enormous unused region on the right side of wide displays".
Vector legacy's core layout (skins.vector.styles.legacy/layouts/
screen.less) gives `.mw-body` (#content) a left margin to clear the
fixed-width sidebar and otherwise lets it run edge-to-edge to the
browser's right side with no max-width at all -- the first redesign
pass added a max-width but left the column pinned to the sidebar's left
edge, which is *why* it still read as "a column stuck on the left with
dead space on the right" rather than a composed layout.

Fix: instead of a fixed `margin-left: 11em`, compute how much space is
left over in the workspace (viewport minus the sidebar) once the
content has its max-width, and split that leftover evenly between the
left and right margins (via the --edfm-gutter token above) -- so the
article is centred *within the workspace to the right of the sidebar*,
not centred in the full viewport (which would ignore the sidebar and
look off-centre) and not pinned to its left edge either. On a screen
too narrow for sidebar + max-width content, --edfm-gutter naturally
evaluates to 0 and this degrades to the old "fill the workspace"
behaviour -- no separate narrow-screen override needed.

The header/tab bar's own float/absolute-position box (#mw-head) is left
at its native full width deliberately -- rewriting *that* mechanism is
a different, much higher-risk change (it took several rounds to get
right originally) -- but its *contents* (search box, personal tools,
namespace/view tabs) get their own right/left offsets pulled in by the
same --edfm-gutter below, so they still visually line up with the
centred column beneath them instead of hugging the browser edge. */
.mw-body,
#mw-data-after-content,
.mw-footer {
position: relative;
z-index: 2;
margin-left: var( --edfm-sidebar-clear );
margin-right: var( --edfm-gutter );
max-width: var( --edfm-content-max );
box-sizing: border-box;
}
/* Tables, code blocks, and preformatted content are still allowed to be
wider than a comfortable reading measure (technical data often needs
it) -- they scroll horizontally inside the capped column instead of
being force-shrunk or breaking the layout. Ordinary images/galleries
already respect the column via max-width:100% below. */
.mw-body table,
.mw-body pre,
.mw-body .mw-code {
max-width: 100%;
overflow-x: auto;
}
.mw-body table.wikitable,
.mw-body table.mw-datatable,
.mw-parser-output > table.wikitable,
.mw-parser-output > table.mw-datatable {
/* Keep real table layout so header cells and body cells share one column grid.
The earlier display:block + tbody display:table overflow hack made sortable
headers size independently from body columns, which visibly misaligned the
Engineer directory after portrait chips were added. */
display: table;
width: 100%;
table-layout: auto;
}
.mw-body table.wikitable th,
.mw-body table.wikitable td,
.mw-body table.mw-datatable th,
.mw-body table.mw-datatable td {
vertical-align: middle;
}
.mw-body img {
max-width: 100%;
height: auto;
}

/* ==========================================================================
4. ARTICLE MASTHEAD (eyebrow / title / deck)
========================================================================== */
/* Eyebrow line is authored as ordinary wikitext (see Template:Article
header) and, purely as a placement detail, a small script
(MediaWiki:Common.js) moves it directly above #firstHeading on load --
see the comment there for why that needs JS rather than CSS/a template
(the title is rendered by the skin before the article body in the DOM,
so nothing living inside the article body can appear earlier than it
without either moving it in the DOM or abandoning the real semantic H1).
If JS is unavailable the eyebrow still renders, just directly under the
title instead of above it.

The eyebrow/title/deck aren't wrapped in one literal bounding box (they
live at two different DOM depths -- eyebrow is a sibling of #firstHeading,
deck is inside the article body further down -- wrapping them in one
real container would need heavier JS than is justified here), so the
"designed masthead" read comes from a matching top rule above the
eyebrow and bottom rule below the deck, a small angular marker, and the
larger title/subtitle type scale, rather than one drawn box. */
.edfm-eyebrow {
display: block;
margin: 0.2em 0 0.15em 0;
padding: 0;
border: 0;
font-family: var( --edfm-sans );
font-size: 0.78rem;
font-weight: 600;
letter-spacing: 0.04em;
text-transform: uppercase;
color: var( --edfm-text-dim );
}
.edfm-eyebrow::before {
content: none;
}
.edfm-eyebrow .edfm-orange-mark {
color: var( --edfm-orange );
}
.edfm-deck {
color: var( --edfm-text-muted );
font-family: var( --edfm-sans );
font-size: 0.95rem;
font-style: italic;
line-height: 1.45;
max-width: none;
margin: 0.25em 0 0.85em 1.4em;
padding: 0;
border: 0;
}

/* ==========================================================================
1. SIDEBAR
========================================================================== */
#mw-panel {
background: transparent;
box-sizing: border-box;
width: var( --edfm-sidebar-width );
padding: 0 0.65rem 1.35rem 0.65rem;
border-right: 0;
box-shadow: none;
z-index: 3;
}
/* Logo anchors the sidebar visually. Keep raster logo artwork contained in
Vector legacy's fixed sidebar slot rather than letting the image render at
its intrinsic PNG size and clip against the rail. */
#p-logo {
box-sizing: border-box;
width: auto;
height: 10rem;
margin: 0 -0.65rem 0.65rem -0.65rem;
padding: 0.5rem 0.55rem 0.45rem 0.55rem;
border-bottom: 0 !important;
background: radial-gradient( circle at 50% 25%, rgba( 255, 138, 0, 0.08 ), transparent 58% );
overflow: hidden;
}
#p-logo a.mw-wiki-logo {
box-sizing: border-box;
display: block;
width: 100% !important;
height: 100% !important;
background-position: center center !important;
background-repeat: no-repeat !important;
background-size: contain !important;
}
/* Each nav group gets real breathing room from the one before it instead
of being packed together like a stock wiki sidebar. */

/* Sidebar Discord invite CTA: injected by MediaWiki:Common.js directly below
the logo and above the first generated Vector portlet, matching the compact
community-button placement shown in the reference screenshot. */
.edfm-discord-cta {
display: inline-flex;
align-items: center;
justify-content: center;
gap: 0.42rem;
box-sizing: border-box;
width: calc( 100% - 1.35rem );
min-height: 1.78rem;
margin: 0.35rem 0.675rem 1.05rem 0.675rem;
padding: 0.36rem 0.56rem;
border-radius: 4px;
background: #5865f2;
color: #fff !important;
font-size: 0.76rem;
font-weight: 700;
line-height: 1.1;
text-align: center;
text-decoration: none !important;
box-shadow: 0 2px 5px rgba( 0, 0, 0, 0.35 );
transition: background-color 120ms ease, box-shadow 120ms ease, transform 120ms ease;
}
.edfm-discord-cta:hover,
.edfm-discord-cta:focus {
background: #4752c4;
color: #fff !important;
text-decoration: none !important;
box-shadow: 0 3px 8px rgba( 0, 0, 0, 0.42 );
transform: translateY( -1px );
}
.edfm-discord-cta-icon {
display: inline-flex;
width: 1rem;
height: 1rem;
flex: 0 0 auto;
}
.edfm-discord-cta-icon svg {
display: block;
width: 100%;
height: 100%;
fill: currentColor;
}

#mw-panel .portal,
#mw-panel .vector-menu-portal {
box-sizing: border-box;
width: auto;
max-width: none;
margin-top: 1.45rem;
}
#mw-panel .portal:first-of-type,
#mw-panel .vector-menu-portal:first-of-type {
margin-top: 0;
}
#mw-panel .portal .body,
#mw-panel .portal ul,
#mw-panel .vector-menu-content,
#mw-panel .vector-menu-content-list {
box-sizing: border-box;
width: auto;
max-width: none;
margin-left: 0;
margin-right: 0;
padding-left: 0;
border-color: var( --edfm-border-soft );
}
#mw-panel .portal a {
color: var( --edfm-text-muted );
display: block;
font-size: var( --edfm-fs-sidebar );
line-height: 1.35;
padding: 0.42em 0.55em;
margin: 0.08em -0.35em;
border-left: 2px solid transparent;
border-radius: 2px;
}
#mw-panel .portal a:hover {
color: var( --edfm-cyan );
background: var( --edfm-surface-1 );
}
/* "You are here" -- MediaWiki's sidebar has no built-in current-page
indication; MediaWiki:Common.js adds the .edfm-nav-current class to the
matching list item by comparing hrefs to the current URL. Orange is
reserved for exactly this kind of "important navigation / selected
state" per the colour system, which is why the rest of the sidebar is
deliberately muted rather than orange throughout (an all-orange sidebar
would both fight this indicator and read as visually dominant). */
.edfm-nav-current > a {
color: var( --edfm-orange ) !important;
font-weight: 700;
border-left-color: var( --edfm-orange );
border-left-width: 3px;
background: var( --edfm-surface-2 );
box-shadow: inset 0 0 0 1px rgba( 255, 138, 0, 0.08 );
}
.vector-menu-heading {
color: var( --edfm-text-dim );
font-weight: 700;
font-family: var( --edfm-mono );
letter-spacing: 0.08em;
text-transform: uppercase;
font-size: var( --edfm-fs-utility );
border-left: 2px solid var( --edfm-orange );
padding-left: 0.5em;
margin-left: -0.5em;
margin-bottom: 0.4em;
}

/* ==========================================================================
3. TOP BAR -- two-tier chrome
========================================================================== */
/* Vector legacy's #mw-head naturally has ~2.5em of empty space above the
tabs row (core: `#left-navigation/#right-navigation { margin-top:2.5em }`),
originally reserved just for #p-personal to float in. Painting that same
box with a background gradient that stays transparent for that top
band and then switches to a surface colour for the tabs band creates a
real two-tier read -- "primary chrome" (personal tools/search, over the
page's own background) above "wiki authoring controls" (the tabs, on
their own distinct strip) below -- without touching #mw-head's own
position/width mechanics, which is the same fragile absolute-position
system the very first pass of this project had to debug carefully to
get the persistent sidebar working at all. Not worth re-risking that
for a background change. */
#mw-head {
background-image: linear-gradient(
to bottom,
transparent 0,
transparent 2.35em,
var( --edfm-surface-2 ) 2.35em,
var( --edfm-surface-2 ) 100%
);
border-bottom: 1px solid var( --edfm-border );
}
#mw-page-base {
background-color: var( --edfm-bg-deep );
background-image: none;
}
#mw-head-base {
background-color: var( --edfm-bg-deep );
/* Polish pass: thinned from 2px -- at 2px this competed visually with
the masthead's own orange marker/rule directly below it; a single
thinner accent line still reads as "site identity colour" without
the repetition. */
border-bottom: 1px solid var( --edfm-orange );
}
/* Personal tools (login/logout) and the search box are the "primary
chrome" tier -- pulled in by the same gutter used to centre the article,
so on wide screens they visually line up with the centred column
instead of hugging the browser edge, and given noticeably more visual
weight than the tabs below them. */
#p-personal {
right: calc( 0.75em + var( --edfm-gutter ) );
display: flex;
align-items: center;
gap: 0.75rem;
}
#p-personal ul {
display: flex;
align-items: center;
gap: 0.55rem;
}
#p-personal li {
margin-left: 0;
}
#p-personal a {
color: var( --edfm-text-muted );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-sidebar );
padding: 0.3em 0.2em;
}
#p-personal a:hover {
color: var( --edfm-orange );
}
.edfm-topbar-clocks {
display: inline-flex;
align-items: center;
gap: 0.5rem;
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-sidebar );
line-height: 1;
white-space: nowrap;
}
.edfm-topbar-clock {
display: inline-flex;
align-items: center;
gap: 0.3em;
padding: 0.3em 0.55em;
background: rgba( 66, 199, 217, 0.08 );
border: 1px solid var( --edfm-border-soft );
border-left: 2px solid var( --edfm-cyan );
color: var( --edfm-text );
}
.edfm-topbar-clock-label {
color: var( --edfm-text-dim );
font-size: var( --edfm-fs-utility );
letter-spacing: 0.08em;
text-transform: uppercase;
}
.edfm-topbar-clock time {
color: var( --edfm-cyan );
font-weight: 700;
}
.edfm-topbar-clock-local {
background: rgba( 255, 138, 0, 0.06 );
border-left-color: var( --edfm-orange );
}
.edfm-topbar-clock-local time {
color: var( --edfm-orange-bright );
}
#right-navigation {
margin-right: var( --edfm-gutter );
}
#left-navigation {
margin-left: var( --edfm-sidebar-clear );
}
/* Polish pass: core caps this at `width:20vw; max-width:20em`, which read
as cramped next to the rest of the (now larger-scale) interface --
given more room on desktop, still capped so it can't dominate the bar. */
.vector-search-box-inner {
width: 22vw;
max-width: 24em;
}
.vector-search-box-inner input,
#searchInput {
background-color: var( --edfm-surface-3 );
color: var( --edfm-text );
border: 1px solid var( --edfm-border );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-sidebar );
padding: 0.5em 0.7em;
transition: border-color 0.15s ease, box-shadow 0.15s ease;
}
#searchInput:focus {
border-color: var( --edfm-cyan );
box-shadow: 0 0 0 2px rgba( 66, 199, 217, 0.22 );
outline: none;
}
#searchInput::placeholder {
color: var( --edfm-text-dim );
}
/* Namespace tabs (Main Page / Discussion, left) and view tabs
(Read / Edit / View history, right) both use Vector legacy's
.vector-menu-tabs-legacy markup. Core skin CSS paints every tab `li`
with a gradient fading to white and forces the selected tab to pure
white -- neither is touched by recolouring the link text alone, which is
why these stayed light before this stylesheet covered the `li`
background too. Core also has an `a:visited` rule (higher specificity
than a plain `a` rule, since a pseudo-class counts the same as a class)
that reasserts a near-black "visited" colour meant for a white
background; since these tabs point at pages you've almost always
already visited, without an explicit `:visited` override here the text
goes dark-on-dark. This can't be caught by reading getComputedStyle() in
an automated check -- browsers deliberately report the *unvisited*
colour to JS for privacy reasons, so it only shows up on an actual
screen; verified with real rendered screenshots, including after
genuinely visiting the linked pages first.

These are the "wiki authoring controls" utility tier -- deliberately
smaller (--edfm-fs-utility) and quieter than personal-tools/search
above them, sitting on their own background strip (see #mw-head above).
Selected state stays orange (it's still real navigation, just
secondary); unselected rests dim so the *selected* tab is the one that
reads clearly. */
.vector-menu-tabs-legacy li {
background-image: none;
background-color: transparent;
}
.vector-menu-tabs-legacy li.selected {
background-image: none;
background-color: var( --edfm-surface-1 );
/* Polish pass: a small underline makes the selected tab unambiguous at
a glance instead of relying on the text colour change alone. */
box-shadow: inset 0 -2px 0 var( --edfm-orange );
}
.vector-menu-tabs-legacy li a,
.vector-menu-tabs-legacy li a:visited {
background-color: transparent;
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-utility );
letter-spacing: 0.03em;
text-transform: uppercase;
font-weight: 700;
}
.vector-menu-tabs-legacy li a:hover,
.vector-menu-tabs-legacy li a:visited:hover {
color: var( --edfm-text );
}
.vector-menu-tabs-legacy li.selected a,
.vector-menu-tabs-legacy li.selected a:visited {
color: var( --edfm-orange );
}
.vector-menu-tabs-legacy li.new a,
.vector-menu-tabs-legacy li.new a:visited {
color: var( --edfm-link-new );
}
/* "More" actions dropdown (#p-cactions) sits in the same tab row; same
:visited gotcha applies to its menu items. */
.vector-menu-dropdown .vector-menu-heading {
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
border-left: none;
padding-left: 8px;
margin-left: 0;
margin-bottom: 0;
text-transform: uppercase;
letter-spacing: 0.03em;
font-size: var( --edfm-fs-utility );
font-weight: 700;
}
.vector-menu-dropdown .vector-menu-heading:hover,
.vector-menu-dropdown .vector-menu-heading:focus {
color: var( --edfm-orange );
}
.vector-menu-dropdown .vector-menu-content {
background-color: var( --edfm-surface-3 );
border-color: var( --edfm-border );
}
.vector-menu-dropdown .vector-menu-content a,
.vector-menu-dropdown .vector-menu-content a:visited {
color: var( --edfm-text-muted );
font-size: var( --edfm-fs-sidebar );
}
.vector-menu-dropdown .vector-menu-content li.selected a,
.vector-menu-dropdown .vector-menu-content li.selected a:visited {
color: var( --edfm-orange );
}
.vector-menu-dropdown .vector-menu-content li:hover {
background-color: var( --edfm-surface-4 );
}

/* Front-page chrome: the hero already names the site, so suppress the
generated MediaWiki page title only on the Main Page. Keep the namespace
tab label and all other article titles intact. */
body.page-Main_Page #firstHeading {
display: none;
}
body.page-Main_Page .mw-body-content {
margin-top: 0;
}

/* ==========================================================================
CONTENT / ARTICLE SURFACE
========================================================================== */
.mw-body,
.parsoid-body {
background-color: var( --edfm-surface-1 );
color: var( --edfm-text );
border-color: var( --edfm-border );
font-family: var( --edfm-sans );
}
.mw-body {
border-right: 1px solid var( --edfm-border );
}
#content {
background-color: var( --edfm-surface-1 );
}

/* Site notice chrome. The global disclaimer was moved to its dedicated
legal/disclaimer page, so an empty #siteNotice must not leave behind a
phantom divider at the top of the article surface. */
#siteNotice:empty {
display: none;
}
#siteNotice:not( :empty ) {
font-size: var( --edfm-fs-meta );
line-height: 1.5;
color: var( --edfm-text-dim );
font-style: normal;
padding-bottom: 0.7em;
margin-bottom: 1.4rem;
border-bottom: 1px solid var( --edfm-border-soft );
}
#siteNotice:not( :empty ) em, #siteNotice:not( :empty ) i {
color: var( --edfm-text-muted );
font-style: italic;
}
#siteNotice:not( :empty ) a {
color: var( --edfm-link-external );
}
#siteNotice a:hover {
color: var( --edfm-link-external-hover );
}

/* ==========================================================================
HOME PAGE DASHBOARD
========================================================================== */
.edfm-home-hero {
margin: 0.9rem 0 1.6rem;
padding: 1.35rem 1.55rem;
background:
linear-gradient( 135deg, rgba( 255, 138, 0, 0.16 ), transparent 34% ),
linear-gradient( 315deg, rgba( 66, 199, 217, 0.14 ), transparent 42% ),
var( --edfm-surface-2 );
border: 1px solid var( --edfm-border );
border-left: 4px solid var( --edfm-cyan );
clip-path: polygon( 0 0, calc( 100% - 12px ) 0, 100% 12px, 100% 100%, 0 100% );
}
.edfm-home-hero-kicker,
.edfm-home-card-kicker {
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-meta );
font-weight: 800;
letter-spacing: 0.1em;
text-transform: uppercase;
}
.edfm-home-hero-title {
margin-top: 0.25rem;
color: var( --edfm-text );
font-family: var( --edfm-mono );
font-size: clamp( 1.55rem, 1.1rem + 1.5vw, 2.2rem );
font-weight: 800;
line-height: 1.15;
}
.edfm-home-hero-text {
max-width: none;
margin-top: 0.55rem;
color: var( --edfm-text-muted );
font-size: 1.05rem;
line-height: 1.55;
}
.edfm-home-grid {
display: grid;
gap: 1rem;
margin: 1.2rem 0 2rem;
}
.edfm-home-grid-four {
grid-template-columns: repeat( 4, minmax( 0, 1fr ) );
}
.edfm-home-grid-topics {
grid-template-columns: repeat( 2, minmax( 0, 1fr ) );
}
.edfm-home-grid-two {
grid-template-columns: repeat( 2, minmax( 0, 1fr ) );
}
.edfm-home-card {
background: var( --edfm-surface-2 );
border: 1px solid var( --edfm-border );
border-left: 3px solid var( --edfm-cyan );
padding: 1rem 1.1rem;
box-shadow: 0 12px 24px rgba( 0, 0, 0, 0.2 );
transition: transform 0.15s ease, border-color 0.15s ease, background-color 0.15s ease;
}
.edfm-home-card:hover {
transform: translateY( -2px );
background: var( --edfm-surface-3 );
border-left-color: var( --edfm-orange );
}
.edfm-home-card-primary {
border-left-color: var( --edfm-orange );
}
.edfm-home-card-warning {
border-left-color: var( --edfm-text-dim );
}
.edfm-home-card-title,
.edfm-home-card-title a {
margin-top: 0.35rem;
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
font-size: 1.05rem;
font-weight: 800;
line-height: 1.3;
text-decoration: none;
}
.edfm-home-card-title a:hover {
color: var( --edfm-orange-bright ) !important;
}
.edfm-home-card-text,
.edfm-home-link-list {
margin-top: 0.65rem;
color: var( --edfm-text-muted );
line-height: 1.6;
}
.edfm-home-link-list a {
font-weight: 600;
}
@media ( max-width: 1100px ) {
.edfm-home-grid-four {
grid-template-columns: repeat( 2, minmax( 0, 1fr ) );
}
}
@media ( max-width: 760px ) {
.edfm-home-grid-four,
.edfm-home-grid-topics,
.edfm-home-grid-two {
grid-template-columns: 1fr;
}
}

/* ==========================================================================
HOME PAGE NEWS MODULE
========================================================================== */
.edfm-home-news {
margin: 1.8rem 0 2.2rem;
}
.edfm-news-feature-grid {
display: grid;
grid-template-columns: repeat( 3, minmax( 0, 1fr ) );
gap: 1rem;
margin-bottom: 1rem;
}
.edfm-news-card,
.edfm-news-list {
background: var( --edfm-surface-2 );
border: 1px solid var( --edfm-border );
box-shadow: 0 14px 26px rgba( 0, 0, 0, 0.22 );
overflow: hidden;
}
.edfm-news-card {
display: flex;
flex-direction: column;
min-height: 100%;
transition: transform 0.15s ease, border-color 0.15s ease, background-color 0.15s ease;
}
.edfm-news-card:hover {
transform: translateY( -2px );
border-color: rgba( 255, 138, 0, 0.48 );
background: var( --edfm-surface-3 );
}
.edfm-news-card-art {
display: flex;
align-items: flex-end;
min-height: 7rem;
padding: 0.8rem 1rem;
box-sizing: border-box;
background:
linear-gradient( 135deg, rgba( 255, 138, 0, 0.28 ), transparent 42% ),
linear-gradient( 315deg, rgba( 66, 199, 217, 0.2 ), transparent 48% ),
linear-gradient( 180deg, var( --edfm-surface-4 ), var( --edfm-surface-1 ) );
border-bottom: 1px solid var( --edfm-border );
color: rgba( 237, 240, 242, 0.72 );
font-family: var( --edfm-mono );
font-size: 0.8rem;
font-weight: 800;
letter-spacing: 0.16em;
text-transform: uppercase;
}
.edfm-news-card-primary .edfm-news-card-art {
background:
linear-gradient( 135deg, rgba( 255, 138, 0, 0.38 ), transparent 46% ),
linear-gradient( 315deg, rgba( 79, 159, 232, 0.26 ), transparent 52% ),
var( --edfm-surface-4 );
}
.edfm-news-card-body {
padding: 1rem 1.15rem 1.15rem;
}
.edfm-news-meta {
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-meta );
letter-spacing: 0.04em;
text-transform: uppercase;
margin-bottom: 0.35rem;
}
.edfm-news-title,
.edfm-news-title a {
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
font-size: 1.1rem;
font-weight: 800;
line-height: 1.25;
text-decoration: none;
}
.edfm-news-title a:hover {
color: var( --edfm-orange-bright ) !important;
}
.edfm-news-summary {
color: var( --edfm-text-muted );
line-height: 1.55;
margin-top: 0.65rem;
}
.edfm-news-list {
padding: 1.1rem 1.25rem 1.2rem;
border-left: 4px solid var( --edfm-orange );
}
.edfm-news-list-heading {
color: var( --edfm-text );
font-family: var( --edfm-mono );
font-size: 1.05rem;
font-weight: 800;
letter-spacing: 0.04em;
text-transform: uppercase;
margin-bottom: 0.75rem;
}
.edfm-news-list ul {
margin: 0;
}
.edfm-news-list li {
margin-bottom: 0.55rem;
color: var( --edfm-text-muted );
}
.edfm-news-more {
margin-top: 0.9rem;
padding-top: 0.85rem;
border-top: 1px solid var( --edfm-border-soft );
text-align: right;
font-family: var( --edfm-mono );
font-weight: 800;
letter-spacing: 0.03em;
text-transform: uppercase;
}
@media ( max-width: 900px ) {
.edfm-news-feature-grid {
grid-template-columns: 1fr;
}
}

/* ==========================================================================
10. JUMP NAVIGATION (table of contents)
========================================================================== */
/* A compact navigation strip/tile-grid rather than a traditional TOC box
of small text links -- real MediaWiki anchors/markup untouched, this is
all presentation. "Contents" is kept in the DOM for screen readers/
no-JS/no-CSS fallback (more standard wording there anyway) and visually
replaced with "Jump to" via ::before on the wrapper, with the real
heading text hidden via font-size rather than display:none so it
remains in the accessibility tree. */
#toc, .toc {
display: block;
width: 100%;
box-sizing: border-box;
background: none;
border: none;
color: var( --edfm-text );
padding: 0;
margin: 1.8rem 0;
}
.toctitle {
position: relative;
margin-bottom: 0.7em;
}
.toctitle::before {
content: 'Jump to';
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-meta );
font-weight: 700;
letter-spacing: 0.12em;
text-transform: uppercase;
color: var( --edfm-orange );
}
/* Core ships `.toc h2 { font-size: 100%; ... }` (mediawiki.skinning/toc/
screen.less) at the exact same specificity (one class + one tag) as a
plain `.toctitle h2` rule -- same "tie that doesn't resolve the way
naive source order would suggest" gotcha documented elsewhere in this
file. #toc's own ID makes this one unambiguous instead of relying on
cascade order. */
#toc .toctitle h2,
.toc .toctitle h2 {
font-size: 0 !important;
line-height: 0;
margin: 0;
border: none;
padding: 0;
display: inline;
}
.toctitle h2::before,
.toctitle h2::after {
content: none;
}
.toctogglelabel::before {
color: var( --edfm-text-dim );
}
/* Desktop: a real grid of clickable tiles (3 columns suits this site's
typical 5-8 top-level sections well: commonly 2-3 rows) instead of one
long line of small text. Each tile has its own surface, a visible
boundary via the accent rail (not a full border -- see "stop using a
border around everything"), and an obvious hover state. */
.toc > ul {
display: grid;
grid-template-columns: repeat( 4, 1fr );
gap: 0.45rem;
list-style: none;
margin: 0;
padding: 0;
}
.toc li {
margin: 0;
}
/* 2026-08-08 density pass: reverted to side-by-side number/label (from the
earlier "stacked number-above-label" polish pass) specifically to cut
per-tile height -- with 12 sections on articles like The Dweller, the
stacked layout meant the jump nav alone filled most of the first
viewport. Row layout plus tighter padding/font-size gets noticeably
more sections above the fold without dropping the numbering or shrinking
tap targets below a comfortable size -- see the dedicated mobile padding
bump further down for keeping touch targets safe on small screens
specifically. Whole tile stays one real <a>, so it's still a single
click/focus target and keyboard tab stop either way. */
.toc a {
display: flex;
flex-direction: row;
align-items: center;
gap: 0.5em;
height: 100%;
box-sizing: border-box;
padding: 0.5em 0.75em 0.5em 0.7em;
background: var( --edfm-surface-3 );
/* Left accent rail: matches the orange section numbers and gives each
jump tile a stronger EDFM navigation affordance without boxing the
entire card. */
border-left: 4px solid var( --edfm-orange );
box-shadow: inset 1px 0 0 rgba( 255, 162, 26, 0.35 );
color: var( --edfm-text-muted );
text-decoration: none;
transition: background-color 0.15s ease, border-color 0.15s ease, box-shadow 0.15s ease, color 0.15s ease, transform 0.15s ease;
}
.toc a:hover {
background: var( --edfm-surface-4 );
border-left-color: var( --edfm-cyan );
box-shadow: inset 1px 0 0 rgba( 66, 199, 217, 0.45 );
color: var( --edfm-text );
transform: translateY( -1px );
}
/* Nested sub-levels (rare on this site so far) drop back to a plain
indented block list inside their parent tile's grid cell rather than
trying to stay gridded themselves. */
.toc ul ul {
grid-column: unset;
list-style: none;
margin: 0.3em 0 0 1.2em;
padding: 0;
display: block;
}
.toc ul ul a {
flex-direction: row;
align-items: center;
background: none;
border-left-width: 1px;
padding: 0.3em 0.6em;
}
.toc ul ul .tocnumber {
font-size: 0.85em;
}
.toc ul ul .toctext {
font-size: 0.85em;
}
.tocnumber {
color: var( --edfm-orange );
font-family: var( --edfm-mono );
font-weight: 700;
font-size: 1.05rem;
line-height: 1;
}
.toctext {
color: inherit;
font-size: 0.85rem;
line-height: 1.3;
}
/* 2026-08-08: rebalanced for the 4-column desktop default above -- was
>1150px = 3 cols -> <=1150px = 2 cols -> <=560px = 1 col. A page with
12 sections (e.g. The Dweller) now gets 3 rows at desktop width instead
of 4, so a new <=860px step was added rather than dropping straight
from 3 to 2 columns at 1150px, which left the same "Star systems,
navigation and exploration"-style long labels cramped in the 1024px
range this breakpoint set was originally tuned for. Order stays widest
condition first, narrowest last, so cascade order matches the max-width
overlap correctly at every width. */
@media ( max-width: 1150px ) {
.toc > ul {
grid-template-columns: repeat( 3, 1fr );
}
}
@media ( max-width: 860px ) {
.toc > ul {
grid-template-columns: repeat( 2, 1fr );
}
}
@media ( max-width: 560px ) {
.toc > ul {
grid-template-columns: 1fr;
}
/* Single-column tiles are already full-width here, so there's no
density pressure left -- restore closer to the pre-2026-08-08
padding instead of the tighter desktop value, keeping tap targets
comfortable rather than compacting mobile just because desktop
compacted. */
.toc a {
padding: 0.7em 0.95em;
}
}

/* ==========================================================================
5b. FULL-WIDTH ARTICLE FLOW OVERRIDES
========================================================================== */
/* 2026-08-10 audit: EDFM pages should not leave half the article rail empty.
Earlier readability caps on paragraphs/hero copy made long-form sections
look like narrow blocks while tables, TOCs, and navigation tiles spanned
the page. Keep the main rail full-width everywhere; individual components
may still opt into their own internal grids, but ordinary article copy and
common block containers should stretch to the content edge. */
.mw-parser-output > p,
.mw-parser-output > ul,
.mw-parser-output > ol,
.mw-parser-output > dl,
.mw-parser-output > div:not( .thumb ):not( .tright ):not( .tleft ):not( .floatright ):not( .floatleft ):not( .edfm-status ):not( .edfm-panel ):not( .edfm-box ) {
max-width: none;
box-sizing: border-box;
}
/* Final guard against stale/skin rules recapping article prose while leaving
compact maintenance/status panels free to keep their intentional centred width. */
.mw-body .mw-parser-output > p,
.mw-parser-output > p {
max-width: none !important;
width: 100%;
box-sizing: border-box;
}

/* ==========================================================================
6. PANELS / CALLOUTS, and 11. ARTICLE METADATA / STATUS MODULE
========================================================================== */
/* Deliberately NOT defined here. .edfm-box / .edfm-panel* / .edfm-status* /
.edfm-inline-flag / .edfm-related* are used exclusively by the
editorial templates (see Template:Article status, Template:Draft
warning, Template:Related articles, etc.), which already load
Template:EDFM style/styles.css themselves via <templatestyles>.
Defining the same class names in both this file and that one would
leave their relative precedence dependent on unclear/unstable ordering
between a ResourceLoader "site" stylesheet and a TemplateStyles-injected
<style> tag -- rather than rely on that, there is exactly one definition
of each, living in Template:EDFM style/styles.css. That file freely uses
the --edfm-* custom properties defined above; custom properties resolve
through the DOM regardless of which stylesheet declared vs references
them, so this split costs nothing. */

/* ==========================================================================
7. TABLES (wikitables, and Special: pages' tables)
========================================================================== */
table.wikitable,
table.mw-datatable {
background-color: var( --edfm-surface-2 );
color: var( --edfm-text );
border-color: var( --edfm-border );
font-size: var( --edfm-fs-body );
}
table.wikitable > tr > th,
table.wikitable > * > tr > th {
background-color: var( --edfm-surface-3 );
color: var( --edfm-text );
border-color: var( --edfm-border );
font-family: var( --edfm-mono );
letter-spacing: 0.03em;
text-transform: uppercase;
font-size: var( --edfm-fs-meta );
text-align: left;
padding: 0.6em 0.8em;
}
table.wikitable > tr > td,
table.wikitable > * > tr > td {
border-color: var( --edfm-border-soft );
padding: 0.6em 0.8em;
}
/* Subtle alternating row treatment -- helps scanning wide/dense reference
tables without turning them into cards. */
table.wikitable > tbody > tr:nth-child( even ),
table.wikitable > * > tr:nth-child( even ) {
background-color: var( --edfm-surface-1 );
}

/* ==========================================================================
15. FOOTER
========================================================================== */
/* A real branded footer: a small wordmark line (pure CSS generated
content -- decorative branding only, redundant with the sidebar logo
already visible, so nothing load-bearing depends on it being
selectable), a top rule with more separation from the article above it,
and MediaWiki's real info/places/icon links laid out on a clean grid
with the badges aligned as a group rather than floating alone. */
.mw-footer {
margin-left: var( --edfm-sidebar-clear );
margin-right: var( --edfm-gutter );
margin-top: 2.5rem;
padding-top: 1.6rem;
border-top: 1px solid var( --edfm-border );
display: grid;
grid-template-columns: 1fr auto;
grid-template-areas: "brand brand" "info icons" "places icons";
align-items: center;
column-gap: 2em;
row-gap: 0.4rem;
}
.mw-footer::before {
grid-area: brand;
content: 'EDFM // Elite Dangerous Field Manual';
font-family: var( --edfm-mono );
font-size: 0.85rem;
font-weight: 700;
letter-spacing: 0.06em;
text-transform: uppercase;
color: var( --edfm-text-muted );
margin-bottom: 0.5rem;
}
.mw-footer,
.mw-footer li,
#footer-info,
#footer-info li {
color: var( --edfm-text-dim );
border-color: var( --edfm-border-soft );
font-size: var( --edfm-fs-meta );
}
#footer-info {
grid-area: info;
margin: 0;
line-height: 1.6;
}
#footer-places {
grid-area: places;
margin: 0;
}
/* Same "small uppercase label" treatment used for tags/meta text
elsewhere, so these read as deliberate EDFM navigation rather than
default MediaWiki footer links. */
#footer-places li {
display: inline-block;
margin-right: 1.4em;
}
#footer-places a {
font-family: var( --edfm-mono );
font-weight: 700;
letter-spacing: 0.03em;
text-transform: uppercase;
font-size: 0.78rem;
}
/* A left rule ties the badges to the rest of the footer instead of
letting them read as detached/floating in their own space. */
#footer-icons {
grid-area: icons;
align-self: center;
display: flex;
gap: 0.75em;
margin: 0;
padding-left: 1.6em;
border-left: 1px solid var( --edfm-border-soft );
}
#footer-icons img {
background: var( --edfm-text );
border-radius: 2px;
}
@media ( max-width: 640px ) {
.mw-footer {
grid-template-columns: 1fr;
grid-template-areas: "brand" "info" "places" "icons";
}
#footer-icons {
margin-top: 0.7em;
padding-left: 0;
border-left: none;
border-top: 1px solid var( --edfm-border-soft );
padding-top: 0.7em;
}
}

/* ==========================================================================
MISC MediaWiki UI chrome that ships with light backgrounds by default
========================================================================== */
.catlinks {
background: none !important;
border: none !important;
border-top: 1px solid var( --edfm-border-soft ) !important;
color: var( --edfm-text-dim );
font-size: var( --edfm-fs-meta );
padding: 0.9em 0 0 0 !important;
margin-top: 1.8rem !important;
}
div.thumbinner {
background-color: var( --edfm-surface-2 );
border-color: var( --edfm-border );
}
.thumbimage {
background-color: var( --edfm-surface-1 );
border-color: var( --edfm-border );
}

/* Code / preformatted text (syntaxhighlight uses its own Pygments theme,
set via $wgPygmentsStyle in LocalSettings.php; this covers plain
<pre>/<code> that isn't Pygments-highlighted). */
pre, code, .mw-code {
background-color: var( --edfm-surface-2 );
color: var( --edfm-text );
border-color: var( --edfm-border );
font-family: var( --edfm-mono );
}

/* ==========================================================================
GENERIC INFOBOX -- see Template:Infobox
========================================================================== */
.edfm-infobox {
float: right;
clear: right;
width: 310px;
margin: 0 0 1.2em 1.2em;
border: 1px solid var( --edfm-border );
border-top: 2px solid var( --edfm-orange );
background: var( --edfm-surface-2 );
color: var( --edfm-text );
font-size: 0.92rem;
}
.edfm-infobox-title {
background: var( --edfm-orange );
color: var( --edfm-bg-deep );
font-weight: 700;
font-family: var( --edfm-mono );
letter-spacing: 0.04em;
text-transform: uppercase;
text-align: center;
padding: 0.5em 0.6em;
clip-path: polygon( 0 0, calc( 100% - 14px ) 0, 100% 14px, 100% 100%, 0 100% );
}
.edfm-infobox-image {
text-align: center;
padding: 0.6em;
border-bottom: 1px solid var( --edfm-border );
}
.edfm-infobox-image-placeholder {
display: flex;
align-items: center;
justify-content: center;
height: 160px;
border: 1px dashed var( --edfm-border );
background: var( --edfm-surface-1 );
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-utility );
text-transform: uppercase;
letter-spacing: 0.06em;
text-align: center;
padding: 0.5em;
}
/* Optional section label (Template:Infobox's |groupN=) splitting a long
infobox into scannable groups, e.g. Engineer infoboxes into "ENGINEER"
and "ACCESS" (2026-08-08, part of the Engineer article layout pass). A
shaded band with a bottom rule rather than a full boxed sub-header --
consistent with .edfm-infobox-row's own bottom-rule-only separator, not
a new visual language. */
.edfm-infobox-group {
background: var( --edfm-surface-3 );
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
font-weight: 700;
font-size: var( --edfm-fs-utility );
letter-spacing: 0.08em;
text-transform: uppercase;
padding: 0.35em 0.7em;
border-bottom: 1px solid var( --edfm-border );
}
.edfm-infobox-row {
display: flex;
border-bottom: 1px solid var( --edfm-border-soft );
padding: 0.45em 0.7em;
}
.edfm-infobox-row:last-child {
border-bottom: none;
}
.edfm-infobox-label {
font-weight: 700;
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-meta );
width: 40%;
flex-shrink: 0;
color: var( --edfm-cyan );
}
.edfm-infobox-value {
width: 60%;
}
@media ( max-width: 640px ) {
.edfm-infobox {
float: none;
width: auto;
margin: 1em 0;
}
}

/* ==========================================================================
14. MOBILE
========================================================================== */
/* Vector legacy has NO built-in responsive breakpoint at all (unlike
Vector 2022) -- its entire header region (#mw-head, tabs, search,
personal tools/login) is built with absolute positioning and floats
that all assume a fixed-width sidebar reserving 10-11em on the left,
AND the page's actual DOM order is content-then-navigation-then-footer
(the absolute positioning was doing double duty: both moving the header
visually to the top AND compensating for that DOM order). Simply
removing the positioning stacks things in DOM order, which reads oddly
on a phone (article text, then the nav/sidebar, then the footer).
Confirmed the actual DOM structure directly (not guessed): <body>'s
real children are #mw-page-base, #mw-head-base, #content,
#mw-navigation (which itself contains #mw-head then #mw-panel, already
in the right relative order), #footer. Since all four major regions are
direct children of <body>, flexbox `order` on <body> can reorder them
properly without needing to touch the DOM itself.
Result: header/search/tabs, then sidebar nav, then content, then
footer -- a plain stacked mobile layout, not a collapsible hamburger
menu, but a correct and readable order. */
@media ( max-width: 800px ) {
body::before {
display: none;
}
body {
display: flex;
flex-direction: column;
}
/* #mw-head-base ships with `margin-top: -5em` in Vector legacy's own
CSS -- a trick to sit it behind the absolutely-positioned header.
Now that the header is a normal flex sibling, that negative margin
drags everything after it upward. Neutralize both decorative
strips. */
#mw-page-base,
#mw-head-base {
order: 0;
height: 0;
margin: 0;
min-height: 0;
}
#mw-navigation {
order: 1;
}
#content {
order: 2;
}
.mw-footer {
order: 3;
}

#mw-head {
position: static;
width: auto;
background-image: none;
background-color: var( --edfm-surface-2 );
}
#left-navigation,
#right-navigation {
float: none;
margin: 0 !important;
width: auto;
clear: both;
}
#left-navigation {
margin-top: 0 !important;
}
/* Core Vector legacy floats each tab/dropdown portlet
(.vector-menu-tabs-legacy for Page/Discussion and Read/View
source/View history, .vector-menu-dropdown for the More menu) AND
floats every <li> inside their <ul>, with no wrapping at all -- at
narrow widths the labels just overflow and overlap each other
(confirmed with a real screenshot: "View source" and "More"
overlapped instead of wrapping to a new line). Switching the
portlets to inline-block and their tab lists to flex-wrap lets them
reflow onto as many rows as needed instead. */
#left-navigation .vector-menu-tabs-legacy,
#right-navigation .vector-menu-tabs-legacy,
#right-navigation .vector-menu-dropdown {
float: none;
display: inline-block;
vertical-align: top;
}
.vector-menu-tabs-legacy ul {
float: none;
display: flex;
flex-wrap: wrap;
}
.vector-menu-tabs-legacy li {
float: none;
}
#p-personal {
position: static;
text-align: right;
padding: 0.5em 1em;
margin: 0;
right: auto !important;
top: auto;
}
#p-personal ul {
padding-left: 0;
}
.vector-search-box {
float: none;
margin: 0.5em 1em;
display: block;
}
.vector-search-box-inner {
width: auto;
max-width: none;
}
#mw-panel {
position: static;
width: auto;
padding: 0.5em 1em;
float: none;
background: var( --edfm-bg-deep );
border-top: 1px solid var( --edfm-border );
border-bottom: 1px solid var( --edfm-border );
}
.mw-body,
#mw-data-after-content,
.mw-footer {
margin-left: 0 !important;
margin-right: 0 !important;
max-width: none;
}
.mw-body {
margin-top: 0;
border-width: 0;
padding: 1em;
}
.edfm-status-details {
grid-template-columns: 1fr;
}
/* .toc > ul column count is NOT overridden here -- the dedicated
1150px/560px breakpoints above already cover every width down to
the smallest phones; duplicating a rule here previously fought
those (same specificity, this position in the cascade would have
won and wrongly forced 1 column as low as 561px). */
#firstHeading {
font-size: 1.6rem;
}
.mw-body h2 {
margin-top: 2.25rem;
}
.edfm-eyebrow {
padding-top: 0.9em;
}
}
/* ==========================================================================
16. OOUI DIALOGS -- VisualEditor's save dialog, and any other OOUI
dialog (delete/move/protect confirmations, special-page dialogs).
These render via OOUI's own bundled WikimediaUI theme stylesheet,
entirely outside the .edfm-* component system this file otherwise
covers, so without this they show up starkly white against the rest of
the dark-themed site regardless of any variable/token used elsewhere in
this file. !important is justified the same way as the h1-h6 fix above:
OOUI's own stylesheet loads with equal-or-higher effective specificity,
and this is a correctness/contrast fix, not decoration.
========================================================================== */
.oo-ui-window-frame {
background: var( --edfm-surface-2 ) !important;
color: var( --edfm-text ) !important;
}
.oo-ui-processDialog {
background: rgba( 7, 9, 11, 0.75 ) !important;
}
.oo-ui-processDialog-navigation,
.oo-ui-window-head,
.oo-ui-window-foot {
background: var( --edfm-surface-3 ) !important;
border-color: var( --edfm-border ) !important;
}
.oo-ui-processDialog-title,
.oo-ui-labelElement-label,
.oo-ui-fieldLayout-header,
.oo-ui-fieldLayout .oo-ui-labelElement-label {
color: var( --edfm-text ) !important;
}
.oo-ui-inputWidget-input {
background: var( --edfm-surface-1 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}
.ve-ui-mwSaveDialog-options,
.oo-ui-panelLayout,
.oo-ui-window-body {
background: var( --edfm-surface-2 ) !important;
color: var( --edfm-text ) !important;
}
.oo-ui-popupWidget-popup {
background: var( --edfm-surface-2 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}
.oo-ui-buttonElement:not( .oo-ui-flaggedElement-primary ) > .oo-ui-buttonElement-button {
background: var( --edfm-surface-4 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}
/* ==========================================================================
17. OOUI TOOLBAR -- VisualEditor's persistent editing toolbar and its
dropdown menus (Cite, Insert, paragraph style, etc.), and the equivalent
toolbar/popups used when editing a single section. Same root cause as
16. OOUI DIALOGS above (OOUI's own bundled theme, not touched by
anything else in this file), found separately because it's a different
set of OOUI classes (toolbar chrome, not dialog chrome). Icons are not
overridden here and don't need to be -- they're currentColor-based, so
they pick up the text colour set below automatically.
========================================================================== */
.oo-ui-toolbar-bar,
.oo-ui-toolGroup-tools,
.oo-ui-popupToolGroup-tools {
background: var( --edfm-surface-3 ) !important;
border-color: var( --edfm-border ) !important;
}
.oo-ui-tool-title,
.oo-ui-tool-link,
.oo-ui-toolGroup-tools .oo-ui-optionWidget,
.oo-ui-menuOptionWidget,
.oo-ui-labelElement-label {
color: var( --edfm-text ) !important;
}
.oo-ui-optionWidget.oo-ui-optionWidget-selected,
.oo-ui-optionWidget:hover,
.oo-ui-tool:hover .oo-ui-tool-link {
background: var( --edfm-surface-4 ) !important;
}
/* ==========================================================================
18. OOUI GENERIC MENUS -- .oo-ui-menuSelectWidget is OOUI's general
dropdown/autocomplete menu class (paragraph-style picker, citation-type
picker, link/media search suggestions, etc.) -- a different class from
the toolbar-specific popups in 17. above, confirmed separately via
computed-style inspection to default to the same white OOUI theme
background.
========================================================================== */
.oo-ui-menuSelectWidget {
background: var( --edfm-surface-3 ) !important;
border-color: var( --edfm-border ) !important;
}
.oo-ui-menuOptionWidget {
color: var( --edfm-text ) !important;
}
.oo-ui-menuOptionWidget.oo-ui-optionWidget-highlighted,
.oo-ui-menuOptionWidget:hover {
background: var( --edfm-surface-4 ) !important;
}
/* ==========================================================================
19. OOUI ICONS -- the toolbar/menu icons themselves (Bold, link, list,
Cite, undo/redo, etc.) are rendered as background-image SVGs with a
colour baked into the SVG markup, not currentColor-based masks -- so
16-18 above (which only recolour backgrounds/text) left them dark and
low-contrast against the now-dark surfaces. OOUI ships its own fix for
exactly this, gated behind a narrow accessibility media query
(forced-colors + prefers-color-scheme: dark) that doesn't apply to this
site's own always-on dark theme -- reusing that exact technique
unconditionally rather than inventing a different one. `:not(
.oo-ui-image-invert )` is OOUI's own exclusion for icons already meant
to render light (e.g. on the orange primary-button background) --
inverting those too would flip them back to dark.
========================================================================== */
.oo-ui-iconElement-icon:not( .oo-ui-image-invert ),
.oo-ui-indicatorElement-indicator:not( .oo-ui-image-invert ) {
filter: invert( 1 ) hue-rotate( 180deg );
}
/* ==========================================================================
20. EDIT SOURCE FORM -- MediaWiki core + WikiEditor + CodeMirror

The source editor is not covered by the article/component selectors above:
`action=edit` loads core edit-form CSS, WikiEditor chrome, and sometimes
CodeMirror with their own light neutral surfaces. Force the same EDFM dark
surface stack here so the source page no longer flashes as a white island.
========================================================================== */
.mw-editform,
#editform,
#toolbar,
.editOptions,
.mw-editTools,
.mw-summary-preview,
.mw-datatable,
.wikiEditor-ui,
.wikiEditor-ui-view,
.wikiEditor-ui-text,
.wikiEditor-ui-toolbar,
.wikiEditor-ui-top,
.wikiEditor-ui-controls,
.wikiEditor-ui-tabs,
.wikiEditor-ui-buttons,
.CodeMirror,
.CodeMirror-scroll {
background: var( --edfm-surface-1 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}
.mw-editform textarea,
#wpTextbox1,
#wpSummary,
#wpSummaryWidget input,
#editform input[type='text'],
#editform input[type='search'],
#editform textarea,
.wikiEditor-ui-text textarea,
.CodeMirror-code,
.CodeMirror-lines,
.CodeMirror pre {
background: var( --edfm-bg-deep ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
caret-color: var( --edfm-orange-bright );
}
.wikiEditor-ui-toolbar,
.wikiEditor-ui-toolbar .group,
.wikiEditor-ui-toolbar .tabs,
.wikiEditor-ui-toolbar .page,
.wikiEditor-ui-toolbar .sections,
.wikiEditor-ui-toolbar .section,
.wikiEditor-ui-toolbar .options,
.wikiEditor-ui-toolbar .booklet,
.wikiEditor-ui-toolbar .pages,
.CodeMirror-gutters {
background: var( --edfm-surface-2 ) !important;
color: var( --edfm-text-muted ) !important;
border-color: var( --edfm-border ) !important;
}
.wikiEditor-ui-toolbar a,
.wikiEditor-ui-toolbar .label,
.wikiEditor-ui-toolbar .tab a,
.mw-editTools a,
.editOptions label,
.mw-editform label,
.CodeMirror-linenumber {
color: var( --edfm-text ) !important;
}
.wikiEditor-ui-toolbar .tab a:hover,
.wikiEditor-ui-toolbar .tool-button:hover,
.wikiEditor-ui-toolbar .tool-select:hover,
.wikiEditor-ui-toolbar .page-table th,
.wikiEditor-ui-toolbar .page-table td,
.CodeMirror-activeline-background {
background: var( --edfm-surface-3 ) !important;
color: var( --edfm-text ) !important;
}
.wikiEditor-ui-toolbar .tab.current a,
.wikiEditor-ui-toolbar .section-main,
.CodeMirror-selected {
background: var( --edfm-surface-4 ) !important;
}
.CodeMirror-cursor {
border-left-color: var( --edfm-orange-bright ) !important;
}
.CodeMirror-matchingbracket {
color: var( --edfm-orange-bright ) !important;
}

/* ==========================================================================
21. FILE PAGE CHROME -- #filetoc (the File / File history / File usage /
Metadata nav on File: description pages) is defined in MediaWiki core's
mediawiki.action.view.filepage.less, entirely separate from both the
.edfm-* system and the OOUI fixes in 16-19 above -- a different
subsystem again, only loaded on File: pages, which is why it was never
touched by anything else in this file. Link colour inside it already
correctly inherits the site's normal link blue; only the light neutral
background/border needed overriding.
========================================================================== */
#filetoc {
background: var( --edfm-surface-2 ) !important;
border-color: var( --edfm-border ) !important;
}
/* ==========================================================================
22. FILE PAGE: METADATA TABLE + MEDIA VIEWER BUTTON -- #mw_metadata is
the EXIF-style metadata table (separate from the File history table
above -- that one already carries the .wikitable class and picked up
dark styling from 7. TABLES automatically; this one doesn't have that
class, so it never matched). The "Open in Media Viewer" button is a
Codex component (MultimediaViewer extension) -- a third distinct
styling subsystem from OOUI and MediaWiki core skinning, again never
touched by anything else in this file.
========================================================================== */
#mw_metadata th,
#mw_metadata td {
background: var( --edfm-surface-2 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}
.mw-mmv-view-expanded.cdx-button {
background: var( --edfm-surface-4 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}

/* Core MediaWiki/action buttons: match EDFM dark theme instead of default white/orange controls. */
.mw-ui-button,
.mw-htmlform-submit,
.mw-htmlform-ooui-wrapper button,
#mw-patrol-form button,
#mw-patrol-form input[type="submit"],
form.mw-htmlform button,
form.mw-htmlform input[type="submit"],
input[type="submit"].mw-ui-button,
button.mw-ui-button,
.cdx-button:not( .cdx-button--fake-button--enabled ) {
background: var( --edfm-surface-4 ) !important;
color: var( --edfm-text ) !important;
border: 1px solid var( --edfm-border-strong, var( --edfm-border ) ) !important;
border-radius: 0 !important;
box-shadow: none !important;
font-family: var( --edfm-mono ) !important;
font-weight: 800 !important;
text-shadow: none !important;
}
.mw-ui-button:hover,
.mw-htmlform-submit:hover,
.mw-htmlform-ooui-wrapper button:hover,
#mw-patrol-form button:hover,
#mw-patrol-form input[type="submit"]:hover,
form.mw-htmlform button:hover,
form.mw-htmlform input[type="submit"]:hover,
input[type="submit"].mw-ui-button:hover,
button.mw-ui-button:hover,
.cdx-button:not( .cdx-button--fake-button--enabled ):hover {
background: var( --edfm-surface-3 ) !important;
color: var( --edfm-orange-bright ) !important;
border-color: var( --edfm-orange ) !important;
}
.mw-ui-button:focus,
.mw-htmlform-submit:focus,
.mw-htmlform-ooui-wrapper button:focus,
#mw-patrol-form button:focus,
#mw-patrol-form input[type="submit"]:focus,
form.mw-htmlform button:focus,
form.mw-htmlform input[type="submit"]:focus,
input[type="submit"].mw-ui-button:focus,
button.mw-ui-button:focus,
.cdx-button:not( .cdx-button--fake-button--enabled ):focus {
outline: 2px solid var( --edfm-cyan ) !important;
outline-offset: 2px !important;
}

/* Patrol action: remove the cramped review button from the public article chrome. */
#mw-patrol-form {
display: none !important;
}

/* Frontier news: after removing the repeated dispatch list, keep attribution compact. */
.edfm-news-attribution-compact {
margin-top: 0.35rem;
padding-top: 0.6rem;
}

/* ===========================================================================
23. RUNE-WIKI-INSPIRED MOBILE APP SHELL
=========================================================================== */
/* Inspired by RuneScape.wiki's mobile ergonomics -- persistent top app bar,
large touch targets, off-canvas navigation, search-forward layout, and
single-column readable article flow -- while preserving EDFM's dark field
manual identity and not copying RuneScape.wiki assets/CSS.
The close button is injected into #mw-panel by Common.js, so it must be
explicitly hidden by default; otherwise a tiny native white button appears
in the desktop sidebar's top-left corner. */
.edfm-mobile-appbar,
.edfm-mobile-scrim,
.edfm-mobile-close-button {
display: none;
}
@media ( max-width: 800px ) {
html {
-webkit-text-size-adjust: 100%;
}
body {
background: var( --edfm-bg-page );
overflow-x: hidden;
}
body.edfm-mobile-menu-open {
overflow: hidden;
}
.edfm-mobile-appbar {
display: grid;
grid-template-columns: 48px 1fr 48px;
align-items: center;
position: sticky;
top: 0;
z-index: 1200;
min-height: 56px;
padding: 0 0.35rem;
background:
linear-gradient( 90deg, rgba( 255, 138, 0, 0.18 ), transparent 38% ),
var( --edfm-surface-2 );
border-bottom: 1px solid var( --edfm-border );
box-shadow: 0 10px 24px rgba( 0, 0, 0, 0.35 );
}
.edfm-mobile-brand {
min-width: 0;
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
font-weight: 800;
letter-spacing: 0.05em;
text-transform: uppercase;
text-decoration: none;
white-space: nowrap;
overflow: hidden;
text-overflow: ellipsis;
}
.edfm-mobile-brand::before {
content: 'EDFM // ';
color: var( --edfm-orange );
}
.edfm-mobile-menu-button,
.edfm-mobile-search-button,
.edfm-mobile-close-button {
appearance: none;
-webkit-appearance: none;
display: inline-flex;
align-items: center;
justify-content: center;
min-width: 44px;
min-height: 44px;
margin: 0;
border: 0;
border-radius: 0;
background: transparent;
color: var( --edfm-text );
font: 700 1.5rem/1 var( --edfm-mono );
cursor: pointer;
}
.edfm-mobile-menu-button:focus-visible,
.edfm-mobile-search-button:focus-visible,
.edfm-mobile-close-button:focus-visible {
outline: 2px solid var( --edfm-cyan );
outline-offset: -4px;
}
.edfm-mobile-menu-button::before {
content: '☰';
color: var( --edfm-orange );
}
.edfm-mobile-search-button::before {
content: '⌕';
font-size: 1.85rem;
color: var( --edfm-cyan );
}
.edfm-mobile-close-button::before {
content: '×';
color: var( --edfm-text );
}
.edfm-mobile-scrim {
display: block;
position: fixed;
inset: 0;
z-index: 1000;
background: rgba( 0, 0, 0, 0.58 );
opacity: 0;
pointer-events: none;
transition: opacity 0.18s ease;
}
body.edfm-mobile-menu-open .edfm-mobile-scrim {
opacity: 1;
pointer-events: auto;
}
#mw-navigation {
background: var( --edfm-surface-2 );
box-shadow: none;
}
#mw-head {
position: relative;
z-index: 1100;
border-bottom: 1px solid var( --edfm-border );
}
#mw-head .vector-search-box {
display: none;
margin: 0;
padding: 0.65rem;
background: var( --edfm-surface-2 );
border-top: 1px solid var( --edfm-border-soft );
}
body.edfm-mobile-search-open #mw-head .vector-search-box {
display: block;
}
#mw-head .vector-search-box-inner,
#mw-head #searchform {
width: 100%;
}
#mw-head #searchInput {
min-height: 44px;
box-sizing: border-box;
width: 100%;
font-size: 1rem;
}
#left-navigation,
#right-navigation {
padding: 0 0.45rem 0.35rem;
background: var( --edfm-surface-2 );
overflow-x: auto;
white-space: nowrap;
-webkit-overflow-scrolling: touch;
}
.vector-menu-tabs-legacy ul {
flex-wrap: nowrap;
}
.vector-menu-tabs-legacy li a,
.vector-menu-tabs-legacy li a:visited,
.vector-menu-dropdown .vector-menu-heading {
min-height: 36px;
display: inline-flex;
align-items: center;
}
#p-personal {
display: none;
}
#mw-panel {
position: fixed;
top: 0;
left: 0;
z-index: 1300;
width: min( 82vw, 22rem );
height: 100dvh;
box-sizing: border-box;
padding: 0;
background: var( --edfm-surface-1 );
border: 0;
border-right: 1px solid var( --edfm-border );
box-shadow: 18px 0 36px rgba( 0, 0, 0, 0.45 );
overflow-y: auto;
-webkit-overflow-scrolling: touch;
transform: translateX( -105% );
transition: transform 0.2s ease;
}
body.edfm-mobile-menu-open #mw-panel {
transform: translateX( 0 );
}
#mw-panel::before {
content: 'EDFM Navigation';
display: block;
position: sticky;
top: 0;
z-index: 1;
padding: 1rem 3.4rem 1rem 1rem;
background: var( --edfm-surface-2 );
border-bottom: 1px solid var( --edfm-border );
color: var( --edfm-orange );
font: 800 0.86rem/1.2 var( --edfm-mono );
letter-spacing: 0.08em;
text-transform: uppercase;
}
#mw-panel .edfm-mobile-close-button {
position: absolute;
top: 0.3rem;
right: 0.35rem;
z-index: 2;
}
#mw-panel .portal,
#mw-panel .vector-menu-portal {
margin: 0;
padding: 0.75rem 0;
border-bottom: 1px solid var( --edfm-border-soft );
}
#mw-panel .vector-menu-heading {
margin: 0.25rem 1rem 0.45rem;
}
#mw-panel .vector-menu-content-list li a,
#mw-panel .vector-menu-content-list li a:visited {
display: flex;
align-items: center;
min-height: 46px;
box-sizing: border-box;
padding: 0.55rem 1rem;
border-left: 3px solid transparent;
color: var( --edfm-text-muted );
font-size: 1rem;
text-decoration: none;
}
#mw-panel .vector-menu-content-list li a:hover,
#mw-panel .vector-menu-content-list li a:focus {
background: var( --edfm-surface-3 );
border-left-color: var( --edfm-cyan );
color: var( --edfm-text );
}
#mw-panel .edfm-nav-current > a,
#mw-panel .edfm-nav-current > a:visited {
background: rgba( 255, 138, 0, 0.12 );
border-left-color: var( --edfm-orange );
color: var( --edfm-orange ) !important;
}
.mw-body {
padding: clamp( 1rem, 4vw, 1.35rem );
font-size: 1rem;
line-height: 1.68;
}
#siteNotice {
margin-bottom: 1rem;
padding-bottom: 0.85rem;
}
#firstHeading {
font-size: clamp( 1.65rem, 8vw, 2.25rem );
line-height: 1.1;
letter-spacing: -0.015em;
}
.mw-body h2 {
font-size: 1.18rem;
line-height: 1.25;
}
.mw-body p,
.mw-body li {
max-width: none;
}
.mw-body img,
.mw-body .thumb,
.mw-body .thumbinner,
.mw-body .thumbimage {
max-width: 100% !important;
height: auto !important;
box-sizing: border-box;
}
.mw-body .thumb,
.mw-body .tright,
.mw-body .tleft {
float: none !important;
clear: both;
width: auto !important;
margin: 1rem 0 !important;
}
.mw-parser-output > table.wikitable,
.mw-parser-output > table.mw-datatable {
display: block;
width: 100% !important;
max-width: 100%;
overflow-x: auto;
-webkit-overflow-scrolling: touch;
white-space: nowrap;
}
.mw-parser-output > table.wikitable th,
.mw-parser-output > table.wikitable td,
.mw-parser-output > table.mw-datatable th,
.mw-parser-output > table.mw-datatable td {
white-space: normal;
min-width: 8rem;
}
.edfm-infobox {
font-size: 0.95rem;
}
.edfm-infobox-row {
display: grid;
grid-template-columns: minmax( 7.5rem, 40% ) 1fr;
gap: 0.5rem;
padding: 0.65rem 0.8rem;
}
.edfm-infobox-label,
.edfm-infobox-value {
width: auto;
}
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type,
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type tbody,
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type tr,
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type th,
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type td {
display: block;
width: 100% !important;
box-sizing: border-box;
}
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type {
overflow: visible;
white-space: normal;
background: transparent;
border: 0;
}
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type th {
margin-top: 0.75rem;
border-left: 3px solid var( --edfm-orange );
}
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type td {
margin-bottom: 0.75rem;
background: var( --edfm-surface-2 );
border-left: 3px solid var( --edfm-border );
}
.mw-footer {
padding: 1rem;
margin-top: 1.5rem;
}
}
@media ( max-width: 430px ) {
.edfm-mobile-brand::before {
content: 'EDFM';
margin-right: 0.45rem;
}
.edfm-mobile-brand {
font-size: 0.88rem;
}
.edfm-infobox-row {
grid-template-columns: 1fr;
gap: 0.2rem;
}
}

/* 22a. Mobile action tabs refinement: keep Vector's page/discussion/read/
source/history controls available, but put them on one compact horizontal
action rail so the first phone viewport feels like a real mobile app shell
instead of two stacked desktop tab bars. */
@media ( max-width: 800px ) {
body:not( .edfm-mobile-search-open ) #mw-head {
display: flex;
align-items: stretch;
gap: 0;
overflow-x: auto;
overflow-y: hidden;
-webkit-overflow-scrolling: touch;
scrollbar-width: thin;
}
body:not( .edfm-mobile-search-open ) #left-navigation,
body:not( .edfm-mobile-search-open ) #right-navigation {
flex: 0 0 auto;
clear: none !important;
float: none !important;
width: auto;
padding: 0 0.25rem;
margin: 0 !important;
border-right: 1px solid var( --edfm-border-soft );
}
body:not( .edfm-mobile-search-open ) .vector-menu-tabs-legacy,
body:not( .edfm-mobile-search-open ) .vector-menu-dropdown {
float: none !important;
display: inline-block;
}
body:not( .edfm-mobile-search-open ) .vector-menu-tabs-legacy li a,
body:not( .edfm-mobile-search-open ) .vector-menu-tabs-legacy li a:visited,
body:not( .edfm-mobile-search-open ) .vector-menu-dropdown .vector-menu-heading {
min-height: 40px;
padding-left: 0.55rem;
padding-right: 0.55rem;
font-size: 0.68rem;
}
body.edfm-mobile-search-open #mw-head {
display: block;
}
}

/* ===========================================================================
24. HARD OVERRIDE: JUMP TILE LEFT RAIL

The earlier border-left rail can be swallowed by ResourceLoader/cascade or
visually read as part of the tile edge. Draw the rail as a high-specificity
gradient on the actual top-level TOC anchors so it is unmistakable on the
live jump grid.
=========================================================================== */
#toc.toc > ul > li > a,
.mw-parser-output #toc > ul > li > a,
.mw-parser-output .toc > ul > li > a {
background-image: linear-gradient( 90deg, var( --edfm-orange ) 0, var( --edfm-orange ) 6px, transparent 6px ) !important;
border-left: 0 !important;
padding-left: 1rem !important;
}
#toc.toc > ul > li > a:hover,
#toc.toc > ul > li > a:focus-visible,
.mw-parser-output #toc > ul > li > a:hover,
.mw-parser-output #toc > ul > li > a:focus-visible,
.mw-parser-output .toc > ul > li > a:hover,
.mw-parser-output .toc > ul > li > a:focus-visible {
background-image: linear-gradient( 90deg, var( --edfm-cyan ) 0, var( --edfm-cyan ) 6px, transparent 6px ) !important;
}

/* ===========================================================================
25. SOURCE EDIT CONFLICT / WIKITEXT DIFF THEME

Source-edit conflict review uses MediaWiki's diff table classes, not the
normal edit textarea/WikiEditor chrome. Without this, unchanged rows and
inline change pills fall back to stark white/yellow/blue defaults. Keep the
old/new meaning, but render it in EDFM's dark surfaces with restrained
orange/cyan accents.
=========================================================================== */
.mw-parser-output table.diff,
table.diff,
.diff {
background: var( --edfm-bg-deep ) !important;
color: var( --edfm-text ) !important;
border-collapse: separate !important;
border-spacing: 0 0.12rem !important;
}
.diff-title,
.diff-otitle,
.diff-ntitle,
#mw-diff-otitle1,
#mw-diff-ntitle1 {
background: var( --edfm-bg-deep ) !important;
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
}
td.diff-lineno,
.diff-lineno {
background: transparent !important;
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
font-weight: 700;
border: 0 !important;
padding: 0.35rem 0.5rem !important;
}
td.diff-marker,
.diff-marker {
background: transparent !important;
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
font-weight: 700;
padding: 0.25rem 0.45rem !important;
text-align: center;
}
td.diff-context,
td.diff-addedline,
td.diff-deletedline,
.diff-context,
.diff-addedline,
.diff-deletedline,
.mw-diff-inline-context,
.mw-diff-inline-added,
.mw-diff-inline-deleted,
.mw-diff-inline-changed,
.mw-diff-inline-moved {
background: var( --edfm-surface-1 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
font-family: var( --edfm-mono );
box-shadow: none !important;
}
td.diff-context:empty,
td.diff-addedline:empty,
td.diff-deletedline:empty,
.diff-context:empty,
.diff-addedline:empty,
.diff-deletedline:empty {
/* Empty diff cells are alignment placeholders. Keep their card boundary so
the two-column source-conflict diff does not look broken, but make them
compact and neutral instead of tall blank blocks. */
background: var( --edfm-surface-1 ) !important;
border-color: var( --edfm-border ) !important;
box-shadow: none !important;
min-height: 0;
padding-top: 0.08rem !important;
padding-bottom: 0.08rem !important;
}
td.diff-deletedline,
.diff-deletedline,
.mw-diff-inline-deleted {
background: rgba( 255, 138, 0, 0.08 ) !important;
border-color: rgba( 255, 138, 0, 0.6 ) !important;
border-left-color: var( --edfm-orange ) !important;
}
td.diff-addedline,
.diff-addedline,
.mw-diff-inline-added {
background: rgba( 66, 199, 217, 0.08 ) !important;
border-color: rgba( 66, 199, 217, 0.6 ) !important;
border-left-color: var( --edfm-cyan ) !important;
}
.diffchange,
.diff-addedline .diffchange,
.diff-deletedline .diffchange,
.mw-diff-inline-added ins,
.mw-diff-inline-changed ins,
.mw-diff-inline-moved ins,
.mw-diff-inline-deleted del,
.mw-diff-inline-changed del,
.mw-diff-inline-moved del {
border-radius: 3px !important;
padding: 0.08rem 0.22rem !important;
font-weight: 700;
text-decoration: none !important;
color: var( --edfm-bg-deep ) !important;
}
.diff-deletedline .diffchange,
.mw-diff-inline-deleted del,
.mw-diff-inline-changed del,
.mw-diff-inline-moved del {
background: var( --edfm-orange-bright ) !important;
}
.diff-addedline .diffchange,
.mw-diff-inline-added ins,
.mw-diff-inline-changed ins,
.mw-diff-inline-moved ins {
background: var( --edfm-cyan ) !important;
}
.mw-explainconflict,
#wpTextbox2,
textarea#wpTextbox2,
textarea.mw-textarea-oldrev {
background: var( --edfm-surface-1 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}

/* Engineer directory portrait chips -- intentionally quiet so table rows still
read like data rows, not card/list hybrids. */
.edfm-engineer-entry {
display: inline-flex;
align-items: center;
gap: 0.45rem;
min-width: max-content;
}
.edfm-engineer-entry .mw-file-element {
width: 30px;
height: 30px;
object-fit: cover;
border-radius: 3px;
border: 1px solid var( --edfm-border );
background: var( --edfm-surface-0 );
box-shadow: none;
}
.edfm-engineer-entry__name {
line-height: 1.2;
}

/* Frontier official news feed image treatment */
.edfm-frontier-news .edfm-news-card-art-image {
display: block;
position: relative;
padding: 0;
/* Keep all news thumbnails uniform, including the first/primary story. */
height: 9.5rem;
min-height: 9.5rem;
aspect-ratio: 16 / 9;
background: var( --edfm-surface-4 );
overflow: hidden;
}
.edfm-frontier-news .edfm-news-card-primary .edfm-news-card-art-image {
height: 9.5rem;
min-height: 9.5rem;
}
.edfm-frontier-news .edfm-news-card-art-image > span,
.edfm-frontier-news .edfm-news-card-art-image .mw-default-size,
.edfm-frontier-news .edfm-news-card-art-image .mw-file-description {
display: block !important;
position: absolute;
inset: 0;
width: 100% !important;
height: 100% !important;
max-width: none !important;
margin: 0 !important;
}
.edfm-frontier-news .edfm-news-card-art-image .mw-file-element {
display: block !important;
width: 100% !important;
height: 100% !important;
max-width: none !important;
object-fit: cover;
transition: transform 0.2s ease, filter 0.2s ease;
}
.edfm-frontier-news .edfm-news-card:hover .edfm-news-card-art-image .mw-file-element {
filter: brightness( 1.08 ) contrast( 1.05 );
transform: scale( 1.035 );
}
.edfm-frontier-news .edfm-news-source-badge {
display: inline-flex !important;
align-items: center;
position: absolute !important;
left: 0.8rem !important;
right: auto !important;
bottom: 0.75rem !important;
z-index: 2;
max-width: calc( 100% - 1.6rem );
padding: 0.25rem 0.55rem;
background: rgba( 10, 13, 17, 0.82 );
border: 1px solid rgba( 255, 138, 0, 0.48 );
box-shadow: 0 8px 18px rgba( 0, 0, 0, 0.34 );
color: var( --edfm-text );
font-family: var( --edfm-mono );
font-size: 0.68rem;
font-weight: 800;
letter-spacing: 0.08em;
line-height: 1;
text-transform: uppercase;
white-space: nowrap;
pointer-events: none;
}

.edfm-news-attribution {
margin-top: 0.85rem;
padding-top: 0.75rem;
border-top: 1px solid var( --edfm-border-soft );
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-meta );
line-height: 1.45;
}

/* Patrol action: hide MediaWiki generated patrol footer/link from article chrome. */
.patrollink,
.patrollink[data-mw-interface],
.patrollink .cdx-button,
#mw-content-text + .patrollink,
.mw-parser-output + .patrollink {
display: none !important;
visibility: hidden !important;
height: 0 !important;
min-height: 0 !important;
margin: 0 !important;
padding: 0 !important;
border: 0 !important;
overflow: hidden !important;
}
/* ===========================================================================
2026-08-10 PROSE RAIL SLEDGEHAMMER
=========================================================================== */
/* Plain article prose on EDFM is supposed to occupy the article rail. Keep this
deliberately simple and selector-separated: no comma-list dependency on
advanced :not() parsing, no TemplateStyles scoping, and both physical and
logical width properties so later/readability rules cannot re-cap lines. */
body.mediawiki #content.mw-body #mw-content-text .mw-parser-output > p,
body.mediawiki #content.mw-body #mw-content-text .mw-parser-output > ul,
body.mediawiki #content.mw-body #mw-content-text .mw-parser-output > ol,
body.mediawiki #content.mw-body #mw-content-text .mw-parser-output > dl {
display: block !important;
width: 100% !important;
max-width: none !important;
inline-size: 100% !important;
max-inline-size: none !important;
box-sizing: border-box !important;
}
body.mediawiki #content.mw-body #mw-content-text .mw-parser-output p {
max-width: none !important;
max-inline-size: none !important;
}
body.mediawiki #content.mw-body #mw-content-text .mw-parser-output li,
body.mediawiki #content.mw-body #mw-content-text .mw-parser-output dd {
max-width: none !important;
max-inline-size: none !important;
}
/* Restore the intentional compact maintenance notice after the broad prose
override above. */
body.mediawiki #content.mw-body #mw-content-text .mw-parser-output > .edfm-status,
body.mediawiki #content.mw-body #mw-content-text .mw-parser-output > .edfm-panel-draft,
body.mediawiki #content.mw-body #mw-content-text .mw-parser-output > .edfm-draft {
width: auto !important;
max-width: 44rem !important;
inline-size: auto !important;
max-inline-size: 44rem !important;
margin-left: auto !important;
margin-right: auto !important;
}

File:Heroferrari.png

2026-08-11T03:08:17Z

EDFM Maintenance: Remove redundant Elite Dangerous wording from Engineer image metadata

== Summary ==
{{EDFM image information
|description = In-game portrait of Hero Ferrari, an Odyssey Engineer.
|subject = [[Hero Ferrari]]
|subject_type = Odyssey Engineer
|source = Elite Dangerous
|media_type = Cropped in-game screenshot
|captured_by = Sythan
|modifications = Cropped to portrait framing (dimensions are non-standard for a full-screen capture, consistent with cropping; not confirmed against an uncropped original)
|intended_use = Identification and illustration on the [[Hero Ferrari]] article and related Engineering pages.
|copyright_holder = Frontier Developments plc
}}

[[Category:Engineer images]]
[[Category:Odyssey Engineer images]]
== Licensing ==
{{License-ED screenshot}}

File:Petraolmanova.png

2026-08-11T03:06:47Z

EDFM Maintenance: Restore Ship/Odyssey Engineer image subtype metadata

== Summary ==
{{EDFM image information
|description = In-game portrait of [[Petra Olmanova]], a Ship Engineer.
|subject = [[Petra Olmanova]]
|subject_type = Ship Engineer
|source = Elite Dangerous, captured in-game
|media_type = In-game screenshot
|captured_by = [[User:Sythan|Sythan]]
|intended_use = Identification and illustration on the [[Petra Olmanova]] article and related Engineering pages.
|copyright_holder = Frontier Developments plc
}}

[[Category:Engineer images]]
[[Category:Ship Engineer images]]

== Licensing ==
{{License-ED screenshot}}

File:Melbrandon.png

2026-08-11T03:06:46Z

EDFM Maintenance: Restore Ship/Odyssey Engineer image subtype metadata

== Summary ==
{{EDFM image information
|description = In-game portrait of [[Mel Brandon]], a Ship Engineer.
|subject = [[Mel Brandon]]
|subject_type = Ship Engineer
|source = Elite Dangerous, captured in-game
|media_type = In-game screenshot
|captured_by = [[User:Sythan|Sythan]]
|intended_use = Identification and illustration on the [[Mel Brandon]] article and related Engineering pages.
|copyright_holder = Frontier Developments plc
}}

[[Category:Engineer images]]
[[Category:Ship Engineer images]]

== Licensing ==
{{License-ED screenshot}}

File:Lorijameson.png

2026-08-11T03:06:45Z

EDFM Maintenance: Restore Ship/Odyssey Engineer image subtype metadata

== Summary ==
{{EDFM image information
|description = In-game portrait of [[Lori Jameson]], a Ship Engineer.
|subject = [[Lori Jameson]]
|subject_type = Ship Engineer
|source = Elite Dangerous, captured in-game
|media_type = In-game screenshot
|captured_by = [[User:Sythan|Sythan]]
|intended_use = Identification and illustration on the [[Lori Jameson]] article and related Engineering pages.
|copyright_holder = Frontier Developments plc
}}

[[Category:Engineer images]]
[[Category:Ship Engineer images]]

== Licensing ==
{{License-ED screenshot}}

File:Ramtah.png

2026-08-11T03:06:45Z

EDFM Maintenance: Restore Ship/Odyssey Engineer image subtype metadata

== Summary ==
{{EDFM image information
|description = In-game portrait of [[Ram Tah]], a Ship Engineer.
|subject = [[Ram Tah]]
|subject_type = Ship Engineer
|source = Elite Dangerous, captured in-game
|media_type = In-game screenshot
|captured_by = [[User:Sythan|Sythan]]
|intended_use = Identification and illustration on the [[Ram Tah]] article and related Engineering pages.
|copyright_holder = Frontier Developments plc
}}

[[Category:Engineer images]]
[[Category:Ship Engineer images]]

== Licensing ==
{{License-ED screenshot}}

File:Thesarge.png

2026-08-11T03:06:44Z

EDFM Maintenance: Restore Ship/Odyssey Engineer image subtype metadata

== Summary ==
{{EDFM image information
|description = In-game portrait of [[The Sarge]], a Ship Engineer.
|subject = [[The Sarge]]
|subject_type = Ship Engineer
|source = Elite Dangerous, captured in-game
|media_type = In-game screenshot
|captured_by = [[User:Sythan|Sythan]]
|intended_use = Identification and illustration on the [[The Sarge]] article and related Engineering pages.
|copyright_holder = Frontier Developments plc
}}

[[Category:Engineer images]]
[[Category:Ship Engineer images]]

== Licensing ==
{{License-ED screenshot}}

File:Lizryder.png

2026-08-11T03:06:43Z

EDFM Maintenance: Restore Ship/Odyssey Engineer image subtype metadata

== Summary ==
{{EDFM image information
|description = In-game portrait of [[Liz Ryder]], a Ship Engineer.
|subject = [[Liz Ryder]]
|subject_type = Ship Engineer
|source = Elite Dangerous, captured in-game
|media_type = In-game screenshot
|captured_by = [[User:Sythan|Sythan]]
|intended_use = Identification and illustration on the [[Liz Ryder]] article and related Engineering pages.
|copyright_holder = Frontier Developments plc
}}

[[Category:Engineer images]]
[[Category:Ship Engineer images]]

== Licensing ==
{{License-ED screenshot}}

File:Zachariahnemo.png

2026-08-11T03:06:42Z

EDFM Maintenance: Restore Ship/Odyssey Engineer image subtype metadata

== Summary ==
{{EDFM image information
|description = In-game portrait of [[Zacariah Nemo]], a Ship Engineer.
|subject = [[Zacariah Nemo]]
|subject_type = Ship Engineer
|source = Elite Dangerous, captured in-game
|media_type = In-game screenshot
|captured_by = [[User:Sythan|Sythan]]
|intended_use = Identification and illustration on the [[Zacariah Nemo]] article and related Engineering pages.
|copyright_holder = Frontier Developments plc
}}

[[Category:Engineer images]]
[[Category:Ship Engineer images]]

== Licensing ==
{{License-ED screenshot}}

File:Selenejean.png

2026-08-11T03:06:41Z

EDFM Maintenance: Restore Ship/Odyssey Engineer image subtype metadata

== Summary ==
{{EDFM image information
|description = In-game portrait of [[Selene Jean]], a Ship Engineer.
|subject = [[Selene Jean]]
|subject_type = Ship Engineer
|source = Elite Dangerous, captured in-game
|media_type = In-game screenshot
|captured_by = [[User:Sythan|Sythan]]
|intended_use = Identification and illustration on the [[Selene Jean]] article and related Engineering pages.
|copyright_holder = Frontier Developments plc
}}

[[Category:Engineer images]]
[[Category:Ship Engineer images]]

== Licensing ==
{{License-ED screenshot}}

File:Theblaster.png

2026-08-11T03:06:41Z

EDFM Maintenance: Restore Ship/Odyssey Engineer image subtype metadata

== Summary ==
{{EDFM image information
|description = In-game portrait of [[Tod "The Blaster" McQuinn]], a Ship Engineer.
|subject = [[Tod "The Blaster" McQuinn]]
|subject_type = Ship Engineer
|source = Elite Dangerous, captured in-game
|media_type = In-game screenshot
|captured_by = [[User:Sythan|Sythan]]
|intended_use = Identification and illustration on the [[Tod "The Blaster" McQuinn]] article and related Engineering pages.
|copyright_holder = Frontier Developments plc
}}

[[Category:Engineer images]]
[[Category:Ship Engineer images]]

== Licensing ==
{{License-ED screenshot}}

File:Leicheung.png

2026-08-11T03:06:40Z

EDFM Maintenance: Restore Ship/Odyssey Engineer image subtype metadata

== Summary ==
{{EDFM image information
|description = In-game portrait of [[Lei Cheung]], a Ship Engineer.
|subject = [[Lei Cheung]]
|subject_type = Ship Engineer
|source = Elite Dangerous, captured in-game
|media_type = In-game screenshot
|captured_by = [[User:Sythan|Sythan]]
|intended_use = Identification and illustration on the [[Lei Cheung]] article and related Engineering pages.
|copyright_holder = Frontier Developments plc
}}

[[Category:Engineer images]]
[[Category:Ship Engineer images]]

== Licensing ==
{{License-ED screenshot}}

File:Marcoqwent.png

2026-08-11T03:06:39Z

EDFM Maintenance: Restore Ship/Odyssey Engineer image subtype metadata

== Summary ==
{{EDFM image information
|description = In-game portrait of [[Marco Qwent]], a Ship Engineer.
|subject = [[Marco Qwent]]
|subject_type = Ship Engineer
|source = Elite Dangerous, captured in-game
|media_type = In-game screenshot
|captured_by = [[User:Sythan|Sythan]]
|intended_use = Identification and illustration on the [[Marco Qwent]] article and related Engineering pages.
|copyright_holder = Frontier Developments plc
}}

[[Category:Engineer images]]
[[Category:Ship Engineer images]]

== Licensing ==
{{License-ED screenshot}}

File:Heroferrari.png

2026-08-11T03:06:38Z

EDFM Maintenance: Restore Ship/Odyssey Engineer image subtype metadata

== Summary ==
{{EDFM image information
|description = In-game portrait of Hero Ferrari, an Odyssey Engineer in ''Elite Dangerous''.
|subject = [[Hero Ferrari]]
|subject_type = Odyssey Engineer
|source = Elite Dangerous
|media_type = Cropped in-game screenshot
|captured_by = Sythan
|modifications = Cropped to portrait framing (dimensions are non-standard for a full-screen capture, consistent with cropping; not confirmed against an uncropped original)
|intended_use = Identification and illustration on the [[Hero Ferrari]] article and related Engineering pages.
|copyright_holder = Frontier Developments plc
}}

[[Category:Engineer images]]
[[Category:Odyssey Engineer images]]
== Licensing ==
{{License-ED screenshot}}

Category:Odyssey Engineer images

2026-08-11T03:06:37Z

EDFM Maintenance: Restore Ship/Odyssey Engineer image subtype guidance

Portrait and identification images of Odyssey Engineers.

[[Category:Engineer images]]

Category:Ship Engineer images

2026-08-11T03:06:37Z

EDFM Maintenance: Restore Ship/Odyssey Engineer image subtype guidance

Portrait and identification images of Ship Engineers.

[[Category:Engineer images]]

Category:Engineer images

2026-08-11T03:06:36Z

EDFM Maintenance: Restore Ship/Odyssey Engineer image subtype guidance

Portrait and identification images of Engineers, both Ship and Odyssey. See [[:Category:Ship Engineer images]] and [[:Category:Odyssey Engineer images]] for the two sub-groups.

[[Category:Media]]

Elite Dangerous Field Manual:Adding an Image

2026-08-11T03:06:35Z

EDFM Maintenance: Restore Ship/Odyssey Engineer image subtype guidance

How to add a screenshot or original image to an EDFM article.

== Current access ==
Uploads are technically enabled on EDFM (PNG/JPEG/WebP, up to 30 MB — see [[Elite Dangerous Field Manual:Screenshot Policy]] for the full rules), but the upload right is currently restricted to administrator accounts while public account creation is still closed — see [[Elite Dangerous Field Manual:Current Project Status]]. This is not the same as uploads being switched off; it's a temporary access restriction that will lift alongside public registration. If you have content you'd like added, flag it via the article's talk page for now rather than assuming you can upload it yourself.

== Before uploading ==
Read [[Elite Dangerous Field Manual:Image Use Policy]] in full — in short: only your own original screenshots or diagrams (nothing copied from Fandom, Reddit, Discord, YouTube, other wikis, or "found on Google"), no third-party UI overlays or other players' identifying information without consent, and no AI-generated images presented as real captures.

== Uploading an image ==
Go to <code>Special:Upload</code>. EDFM's upload form asks for what it can't safely work out on its own, and generates the rest of the file page automatically:

# '''Choose the file.'''
# '''Destination filename''' — a clear, descriptive name (it becomes the page title in the File namespace).
# '''Media purpose''' — what kind of image this is: Engineer portrait, character portrait, ship image, module/equipment image, station/settlement/planet/system image, UI screenshot, gameplay screenshot, diagram/infographic, EDFM-created graphic, or other. This drives the description and categories EDFM generates below.
# '''Subject''' — the EDFM article this image is of, typed as plain text (e.g. <code>Hero Ferrari</code>, not <code><nowiki>[[Hero Ferrari]]</nowiki></code>) — start typing and existing page titles will autocomplete. Required for media purposes that have an obvious subject (a portrait, a ship, a specific location); optional for general gameplay screenshots, UI screenshots, and diagrams. If the subject doesn't yet have an EDFM article, it's still recorded, just as plain text rather than a link.
# '''Subject type override''' — optional, and normally not needed. For an Engineer portrait, EDFM automatically works out "Ship Engineer" vs "Odyssey Engineer" from the subject's own article (its Engineering-type category) — only use this field if that inference is wrong or the subject's article doesn't exist yet.
# '''Licensing''' — for an ordinary gameplay screenshot this is almost always "Elite Dangerous in-game screenshot." See the guidance on the upload page itself, or [[Elite Dangerous Field Manual:Image Use Policy]], for the other options. Your choice here also determines the <code>source</code>, <code>media_type</code>, and (where the license makes it clear) <code>copyright_holder</code> fields below — you don't need to re-enter information the license already establishes.
# '''Image modifications''' — optional. Only state something here if you actually know the file has been altered (e.g. "Cropped to portrait framing"); leave it blank rather than guess.
# '''Additional notes''' — optional freeform field for anything else worth recording.

On submission, EDFM builds the file page's <code>== Summary ==</code> section automatically, using {{tl|EDFM image information}}:
* '''description''' — a short factual sentence built from the media purpose and subject (e.g. "In-game portrait of [[Hero Ferrari]], an Odyssey Engineer.").
* '''subject''' / '''subject_type''' — the article you named, linked if it exists, plus its inferred or overridden type.
* '''source''' / '''media_type''' / '''copyright_holder''' — derived from your Licensing choice (e.g. "Elite Dangerous, captured in-game" / "In-game screenshot" / "Frontier Developments plc" for an ordinary screenshot). For original work you made yourself, copyright is attributed to you as the creator, not to EDFM.
* '''captured_by''' — your account name, filled in automatically; you never need to type your own name.
* '''capture_date''' — included '''only''' if the uploaded file's own metadata contains a genuine capture date. EDFM never substitutes the upload date, and never guesses.
* '''modifications''' / '''notes''' — only included if you actually filled those optional fields in.
* '''intended_use''' — a short standard sentence built from the media purpose and subject (e.g. "Identification and illustration on the [[Hero Ferrari]] article and related Engineering pages.").

The relevant categories (for example [[:Category:Engineer images]] and [[:Category:Odyssey Engineer images]]) and the <code>== Licensing ==</code> section (from your Licensing choice, e.g. {{tl|License-ED screenshot}}) are added automatically as well.

You should not need to write or edit <code>{{tl|EDFM image information}}</code> syntax by hand for a normal upload. If something EDFM generated needs correcting, or you want to add detail beyond what the form covers, you can always edit the file page afterwards like any other page on this wiki — see [[#Advanced: editing a file page directly|below]].

'''Uploading a new version of an existing file''' (replacing the image itself) does not regenerate or overwrite the existing file page's description — your original metadata is left exactly as it was.

Once uploaded, reference the image on the article as <code><nowiki>[[File:Name.png|thumb|caption]]</nowiki></code>, or pass it as <code>|image=Name.png</code> to an infobox that supports one (e.g. {{tl|Engineer infobox}}).

== Advanced: editing a file page directly ==
File pages are ordinary wiki pages. An experienced editor can open a file page and edit its {{tl|EDFM image information}} fields directly at any time — for example to add a <code>capture_date</code> EDFM couldn't detect, correct a <code>subject_type</code>, or expand on <code>notes</code>. See {{tl|EDFM image information}}'s own documentation for the full field list.

== Captioning ==
Use {{tl|Screenshot caption}} for the visible caption text under the image on the article page, so credit/context is shown consistently rather than as plain prose. This is separate from {{tl|EDFM image information}} on the file page itself — see [[Elite Dangerous Field Manual:Screenshot Policy]] for the distinction.

{{Related articles|[[Elite Dangerous Field Manual:Image Use Policy]] [[Elite Dangerous Field Manual:Screenshot Policy]] [[Elite Dangerous Field Manual:Contributing]]}}

MediaWiki:Common.css

2026-08-10T04:22:16Z

EDFM Maintenance: Add logo spacing above sidebar Discord invite button

/* ==========================================================================
EDFM site-wide styling -- "Elite Dangerous technical field manual" theme.
Original CSS written for this project -- no code or assets copied from
runescape.wiki, Elite Dangerous, or any other site/game, and no Frontier
logo/branding/proprietary fonts/copied HUD elements. Restrained visual
influence only: dark industrial surfaces, subtle angular geometry,
orange/cyan accents used sparingly, information hierarchy first. This is
a reference site, not a HUD -- no glow, no neon, no glassmorphism, no
constant animation.

SKIN NOTE: the site uses Vector "legacy" (2011), not Vector 2022 -- see
the "Why Vector legacy" note in docs/content-style-guide.md (Vector 2022
hard-restricts its pinned sidebar to logged-in users; legacy has no such
restriction). Several rules below exist specifically to beat core Vector
legacy/mediawiki.skinning selectors that are *more specific* than a naive
override would be (documented inline at each occurrence) -- this isn't
guesswork, each one was found by reading the actual core .less source and
confirmed with a real rendered screenshot, not just computed-style checks
(:visited colours in particular are invisible to getComputedStyle by
design -- see the tab-bar note below).

2026-08-07 SECOND PASS: the first redesign pass was judged too close to
stock MediaWiki with a colour change -- this pass changes the actual
visual composition (centred workspace instead of a huge dead gutter,
a two-tier header, a real masthead, a tile-grid TOC, a restructured
status module, larger deliberate type scale, depth via surface
elevation instead of borders-around-everything) while reusing every
working mechanism from the first pass rather than throwing it away --
the tab/:visited fix, the external-link specificity fix, the mobile
reorder fix, and focus-visible/reduced-motion are all still here,
unchanged in mechanism.
========================================================================== */

/* ==========================================================================
1. DESIGN TOKENS
========================================================================== */
:root {
/* Depth system: site (outermost, visible in the sidebar/header/gutters)
-> article surface -> component surfaces, each a deliberate step
brighter so the page reads as having actual depth rather than "one
background colour with slightly lighter boxes everywhere". */
--edfm-bg-deep: #07090b;
--edfm-bg-page: #0a0e11;
--edfm-surface-1: #10171b;
--edfm-surface-2: #161f24;
--edfm-surface-3: #1c272d;
--edfm-surface-4: #233037;

--edfm-border: #26333b;
--edfm-border-soft: rgba( 255, 255, 255, 0.06 );

--edfm-text: #edf0f2;
--edfm-text-muted: #98a5ad;
--edfm-text-dim: #6c7a82;

/* Accents -- orange is reserved for navigation/selection/emphasis/
section numbering; cyan/blue are for links, verification info, and
secondary interface elements. See "Links" and "Colour system" in
docs/content-style-guide.md for the reasoning. */
--edfm-orange: #ff8a00;
--edfm-orange-bright: #ffa21a;
--edfm-cyan: #42c7d9;
--edfm-blue: #4f9fe8;

/* Derived link colours */
--edfm-link: var( --edfm-blue );
--edfm-link-visited: #3f7bb3;
--edfm-link-hover: #8cc4f7;
--edfm-link-external: var( --edfm-cyan );
--edfm-link-external-visited: #2f8f9c;
--edfm-link-external-hover: #7fe0ec;
--edfm-link-new: #e07a7a;

/* Status semantics (article metadata module) -- text label always
present too, never colour-only. */
--edfm-status-positive: var( --edfm-cyan );
--edfm-status-attention: var( --edfm-orange );
--edfm-status-neutral: var( --edfm-text-dim );
--edfm-status-positive-bg: rgba( 66, 199, 217, 0.12 );
--edfm-status-attention-bg: rgba( 255, 138, 0, 0.12 );
--edfm-status-neutral-bg: rgba( 108, 122, 130, 0.12 );

/* Typography -- explicit desktop scale (2026-08-07 pass 2). Sized in
rem against the root's real 16px (Vector legacy's own
@font-size-root is 100%, i.e. browser default -- confirmed by
reading skins.vector.styles.legacy/variables.less, not assumed)
rather than nested em, specifically so component sizes can't
compound smaller than intended inside whatever ambient size an
ancestor happens to set. */
--edfm-fs-title: clamp( 1.9rem, 1.4rem + 2vw, 2.25rem ); /* ~30-36px */
--edfm-fs-h2: 1.35rem; /* ~21.6px */
--edfm-fs-h3: 1.15rem; /* ~18.4px */
--edfm-fs-body: 1rem; /* 16px */
--edfm-fs-resource-name: 1.1rem; /* ~17.6px */
--edfm-fs-meta: 0.8rem; /* ~12.8px */
--edfm-fs-sidebar: 0.9375rem; /* 15px -- polish pass: +1px for readability */
--edfm-fs-utility: 0.72rem; /* ~11.5px */

--edfm-mono: 'JetBrains Mono', 'Fira Code', Consolas, 'SF Mono', Menlo, 'Courier New', monospace;
--edfm-sans: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Helvetica, Arial, sans-serif;

/* Legacy aliases: earlier revisions of this stylesheet used these names
directly and some inline template output/older docs may still refer
to them; keep pointing at the current tokens rather than duplicate
values that could drift out of sync. */
--edfm-orange-hover: var( --edfm-orange-bright );
--edfm-orange-active: var( --edfm-orange-bright );
--color-progressive: var( --edfm-orange );
--color-progressive--hover: var( --edfm-orange-bright );
--color-progressive--active: var( --edfm-orange-bright );
--color-progressive--focus: var( --edfm-orange );
--background-color-progressive: var( --edfm-orange );
--background-color-progressive--hover: var( --edfm-orange-bright );
--background-color-progressive--active: var( --edfm-orange-bright );
--border-color-progressive: var( --edfm-orange );
--border-color-progressive--hover: var( --edfm-orange-bright );
--border-color-progressive--active: var( --edfm-orange-bright );

/* Geometry / layout */
--edfm-corner: 10px;
/* Polish-pass bump from 1280px -- article read as slightly too narrow
on large desktop displays, and future reference tables (engineering,
ship stats, colonisation data) will want the room. Still centred
within the workspace via --edfm-gutter below, not stretched
edge-to-edge. */
--edfm-content-max: 1320px;
/* RuneScape.wiki-style integrated rail: wide enough for readable labels,
but joined directly to the page plane. Width and clear match so the
article starts beside the sidebar shadow instead of after a dead gutter. */
--edfm-sidebar-width: 12.75rem;
--edfm-sidebar-clear: 12.75rem;
/* The gutter is whatever's left of the workspace (viewport minus the
sidebar) after the capped content width, split evenly, never
negative. On a screen too narrow to fit sidebar+content-max, this
collapses to 0 and content just fills the workspace edge-to-edge --
see "GLOBAL LAYOUT" below for the full explanation. */
--edfm-gutter: max( 0px, calc( ( 100vw - var( --edfm-sidebar-clear ) - var( --edfm-content-max ) ) / 2 ) );
}

/* ==========================================================================
2. BASE / RESET-ADJACENT
========================================================================== */
html, body {
background-color: var( --edfm-bg-page );
color: var( --edfm-text );
}
body.mediawiki {
color: var( --edfm-text );
font-family: var( --edfm-sans );
font-size: var( --edfm-fs-body );
}
/* Background treatment: a faint technical grid plus a very soft radial
glow centred behind the (now centred) content column, so the composition
still has quiet visual interest in the gutters on ultrawide screens
instead of just flat colour -- both stay under ~3% opacity, this is
texture, not a HUD. Not image assets; pure CSS gradients. */
body {
background-image:
radial-gradient( ellipse 1400px 900px at 50% 0%, rgba( 66, 199, 217, 0.05 ), transparent 60% ),
linear-gradient( rgba( 255, 255, 255, 0.025 ) 1px, transparent 1px ),
linear-gradient( 90deg, rgba( 255, 255, 255, 0.025 ) 1px, transparent 1px );
background-size: auto, 48px 48px, 48px 48px;
background-repeat: no-repeat, repeat, repeat;
background-attachment: fixed, scroll, scroll;
}
/* Full-height sidebar rail: mirrors the RuneScape.wiki behavior where the
left rail has no visible bottom edge. The real #mw-panel only carries the
navigation content; this fixed layer paints the uninterrupted surface,
border, and shadow down the whole viewport. */
body::before {
content: '';
position: fixed;
top: 0;
left: 0;
bottom: 0;
width: var( --edfm-sidebar-width );
background: linear-gradient( 180deg, var( --edfm-surface-1 ) 0%, var( --edfm-bg-deep ) 100% );
border-right: 1px solid var( --edfm-border );
box-shadow: 10px 0 22px rgba( 0, 0, 0, 0.32 );
pointer-events: none;
z-index: 1;
}
@media ( prefers-reduced-motion: reduce ) {
*, *::before, *::after {
animation-duration: 0.001ms !important;
animation-iteration-count: 1 !important;
transition-duration: 0.001ms !important;
scroll-behavior: auto !important;
}
}
/* Focus visibility: applies to every interactive element, not just links. */
a:focus-visible,
button:focus-visible,
input:focus-visible,
textarea:focus-visible,
select:focus-visible,
[tabindex]:focus-visible {
outline: 2px solid var( --edfm-cyan );
outline-offset: 2px;
}

/* Small reusable angular motif: a corner-cut bracket, used sparingly (see
the redesign notes in docs/content-style-guide.md for exactly where) --
deliberately not applied everywhere. */
.edfm-corner-cut {
clip-path: polygon( 0 0, calc( 100% - var( --edfm-corner ) ) 0, 100% var( --edfm-corner ), 100% 100%, 0 100% );
}

/* ==========================================================================
3. TYPOGRAPHY
========================================================================== */
h1, h2, h3, h4, h5, h6 {
color: var( --edfm-text );
border-color: var( --edfm-border );
}
/* !important justified here: MediaWiki core's mediawiki.skinning module
sets heading colour with equal-specificity plain-tag selectors and kept
winning in testing despite this stylesheet loading later -- rather than
keep chasing exact cascade/bundling order, force it. This is a
correctness/contrast fix, not decoration. */
.mw-body h1, .mw-body h2, .mw-body h3, .mw-body h4, .mw-body h5, .mw-body h6,
.mw-heading1, .mw-heading2, .mw-heading3, .mw-heading4, .mw-heading5, .mw-heading6,
h1, h2, h3, h4, h5, h6 {
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
font-family: var( --edfm-mono );
letter-spacing: 0.01em;
line-height: 1.3;
}
#firstHeading {
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-title );
font-weight: 700;
margin-top: 0.15em;
}
/* Section headings (h2): "// " prefix in orange, bright heading text, a
short orange accent segment over the dim full-width divider core
already draws. Substantially more vertical space than a wiki section
normally gets, per the "sections feel packed together" fix -- 3.25rem
(~52px) above, ~1.1rem gap to the first content component below. If a
heading opts into explicit numbering via {{Section number}}, the
automatic "// " is suppressed so the two treatments don't double up. */
.mw-body h2 {
position: relative;
padding-bottom: 0.4em;
margin-top: 3.25rem;
margin-bottom: 1.1rem;
font-size: var( --edfm-fs-h2 );
}
.mw-body h2::before {
content: '// ';
color: var( --edfm-orange );
font-weight: 400;
}
.mw-body h2:has( .edfm-section-number )::before {
content: none;
}
.mw-body h2::after {
content: '';
position: absolute;
left: 0;
bottom: -1px;
width: 3em;
max-width: 100%;
height: 2px;
background: var( --edfm-orange );
}
.edfm-section-number {
color: var( --edfm-orange );
font-weight: 700;
}
.edfm-section-sep {
color: var( --edfm-orange );
margin-right: 0.15em;
}
h3, h4 {
color: var( --edfm-text );
font-size: var( --edfm-fs-h3 );
}
h3::before {
content: '/ ';
color: var( --edfm-text-dim );
font-weight: 400;
}

/* Body text: readable sans-serif, deliberately NOT monospace -- long-form
reading in monospace hurts readability, which stays a hard requirement
even with a more technical visual language elsewhere. */
.mw-body p,
.mw-body li,
.mw-body dd {
line-height: 1.7;
font-size: var( --edfm-fs-body );
}
.mw-body p {
margin: 0 0 1.1em 0;
max-width: 46em; /* comfortable reading measure, not the full column */
}
.mw-body ul,
.mw-body ol {
line-height: 1.7;
margin-bottom: 1.1em;
}
/* MW 1.46 wraps headings in a `.mw-heading2`/`.mw-heading3` div, so the
sibling that immediately follows is that wrapper, not the `h2`/`h3`
itself -- matching both forms since a page could still have a bare
heading in edge cases (e.g. content generated without the wrapper). */
.mw-heading2 + p, .mw-body h2 + p,
.mw-heading3 + p, .mw-body h3 + p,
.mw-heading2 + div, .mw-body h2 + div,
.mw-heading3 + div, .mw-body h3 + div {
margin-top: 0;
}
hr {
background-color: var( --edfm-border );
border-color: var( --edfm-border );
}

/* Quiet, discoverable section-edit controls (logged-in editors only --
MediaWiki only renders these for users who can edit). Keeping the
functionality/keyboard access intact while making sure they don't
compete visually with the heading they're attached to: low opacity at
rest, full opacity on hover/focus of the heading OR the control itself,
brackets hidden (the opacity+letter-spacing treatment already reads as
a distinct control without them). */
.mw-editsection {
margin-left: 1em;
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-utility ) !important;
font-weight: 700;
letter-spacing: 0.05em;
text-transform: uppercase;
opacity: 0.45;
transition: opacity 0.15s ease;
}
.mw-heading:hover .mw-editsection,
.mw-heading:focus-within .mw-editsection,
.mw-editsection:hover,
.mw-editsection:focus-within {
opacity: 1;
}
.mw-editsection a {
color: var( --edfm-text-dim );
}
.mw-editsection a:hover,
.mw-editsection a:focus-visible {
color: var( --edfm-cyan );
}
.mw-editsection-bracket {
display: none;
}
.mw-editsection-divider {
color: var( --edfm-text-dim );
margin: 0 0.3em;
}

/* ==========================================================================
8. LINKS
========================================================================== */
a { color: var( --edfm-link ); transition: color 0.1s ease; }
a:visited { color: var( --edfm-link-visited ); }
a:hover { color: var( --edfm-link-hover ); }
a.new, .new a { color: var( --edfm-link-new ); }
a.external { color: var( --edfm-link-external ); }
/* Core MediaWiki ships `.mw-parser-output a.external`/`a.extiw` (and their
:visited/:hover states) at higher specificity (two classes + a tag) than
a plain `a.external` rule (one class + a tag), so the line above never
actually wins for real article links on its own -- the same underlying
"core selector outranks a naive theme override" gotcha as the tab
:visited fix further down. Matching the same selector shape here (this
stylesheet loads after core skin styles) is what actually applies our
colour to external links in article content. */
.mw-parser-output a.external,
.mw-parser-output a.extiw {
color: var( --edfm-link-external );
}
.mw-parser-output a.external:visited,
.mw-parser-output a.extiw:visited {
color: var( --edfm-link-external-visited );
}
.mw-parser-output a.external:hover,
.mw-parser-output a.extiw:hover {
color: var( --edfm-link-external-hover );
}
.mw-footer a {
color: var( --edfm-link );
}
.mw-footer a:hover {
color: var( --edfm-link-hover );
}

/* ==========================================================================
1. GLOBAL LAYOUT -- centred workspace
========================================================================== */
/* THE fix for "enormous unused region on the right side of wide displays".
Vector legacy's core layout (skins.vector.styles.legacy/layouts/
screen.less) gives `.mw-body` (#content) a left margin to clear the
fixed-width sidebar and otherwise lets it run edge-to-edge to the
browser's right side with no max-width at all -- the first redesign
pass added a max-width but left the column pinned to the sidebar's left
edge, which is *why* it still read as "a column stuck on the left with
dead space on the right" rather than a composed layout.

Fix: instead of a fixed `margin-left: 11em`, compute how much space is
left over in the workspace (viewport minus the sidebar) once the
content has its max-width, and split that leftover evenly between the
left and right margins (via the --edfm-gutter token above) -- so the
article is centred *within the workspace to the right of the sidebar*,
not centred in the full viewport (which would ignore the sidebar and
look off-centre) and not pinned to its left edge either. On a screen
too narrow for sidebar + max-width content, --edfm-gutter naturally
evaluates to 0 and this degrades to the old "fill the workspace"
behaviour -- no separate narrow-screen override needed.

The header/tab bar's own float/absolute-position box (#mw-head) is left
at its native full width deliberately -- rewriting *that* mechanism is
a different, much higher-risk change (it took several rounds to get
right originally) -- but its *contents* (search box, personal tools,
namespace/view tabs) get their own right/left offsets pulled in by the
same --edfm-gutter below, so they still visually line up with the
centred column beneath them instead of hugging the browser edge. */
.mw-body,
#mw-data-after-content,
.mw-footer {
position: relative;
z-index: 2;
margin-left: var( --edfm-sidebar-clear );
margin-right: var( --edfm-gutter );
max-width: var( --edfm-content-max );
box-sizing: border-box;
}
/* Tables, code blocks, and preformatted content are still allowed to be
wider than a comfortable reading measure (technical data often needs
it) -- they scroll horizontally inside the capped column instead of
being force-shrunk or breaking the layout. Ordinary images/galleries
already respect the column via max-width:100% below. */
.mw-body table,
.mw-body pre,
.mw-body .mw-code {
max-width: 100%;
overflow-x: auto;
}
.mw-body table.wikitable,
.mw-body table.mw-datatable {
/* Keep real table layout so header cells and body cells share one column grid.
The earlier display:block + tbody display:table overflow hack made sortable
headers size independently from body columns, which visibly misaligned the
Engineer directory after portrait chips were added. */
display: table;
width: 100%;
table-layout: auto;
}
.mw-body table.wikitable th,
.mw-body table.wikitable td,
.mw-body table.mw-datatable th,
.mw-body table.mw-datatable td {
vertical-align: middle;
}
.mw-body img {
max-width: 100%;
height: auto;
}

/* ==========================================================================
4. ARTICLE MASTHEAD (eyebrow / title / deck)
========================================================================== */
/* Eyebrow line is authored as ordinary wikitext (see Template:Article
header) and, purely as a placement detail, a small script
(MediaWiki:Common.js) moves it directly above #firstHeading on load --
see the comment there for why that needs JS rather than CSS/a template
(the title is rendered by the skin before the article body in the DOM,
so nothing living inside the article body can appear earlier than it
without either moving it in the DOM or abandoning the real semantic H1).
If JS is unavailable the eyebrow still renders, just directly under the
title instead of above it.

The eyebrow/title/deck aren't wrapped in one literal bounding box (they
live at two different DOM depths -- eyebrow is a sibling of #firstHeading,
deck is inside the article body further down -- wrapping them in one
real container would need heavier JS than is justified here), so the
"designed masthead" read comes from a matching top rule above the
eyebrow and bottom rule below the deck, a small angular marker, and the
larger title/subtitle type scale, rather than one drawn box. */
.edfm-eyebrow {
display: flex;
align-items: center;
gap: 0.55em;
margin: 0 0 0.5em 0;
padding-top: 1.1em;
border-top: 1px solid var( --edfm-border );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-meta );
font-weight: 700;
letter-spacing: 0.12em;
text-transform: uppercase;
color: var( --edfm-text-dim );
}
.edfm-eyebrow::before {
content: '';
width: 8px;
height: 8px;
flex-shrink: 0;
background: var( --edfm-orange );
clip-path: polygon( 0 0, 100% 0, 100% 65%, 65% 100%, 0 100% );
}
.edfm-eyebrow .edfm-orange-mark {
color: var( --edfm-orange );
}
.edfm-deck {
color: var( --edfm-text-muted );
font-size: 1.1rem;
line-height: 1.55;
max-width: 42em;
margin: 0.5em 0 1.7em 0;
padding-bottom: 1.6em;
border-bottom: 1px solid var( --edfm-border );
}

/* ==========================================================================
1. SIDEBAR
========================================================================== */
#mw-panel {
background: transparent;
box-sizing: border-box;
width: var( --edfm-sidebar-width );
padding: 0 0.65rem 1.35rem 0.65rem;
border-right: 0;
box-shadow: none;
z-index: 3;
}
/* Logo anchors the sidebar visually. Do not draw a divider on or near
#p-logo: Vector legacy fixes the logo box at 155px high and the EDFM hex
mark reaches that edge, so any horizontal rule in this box cuts through
the lower point of the logo. Navigation spacing below provides the break. */
#p-logo {
box-sizing: border-box;
width: auto;
margin: 0 -0.65rem 1.25rem -0.65rem;
padding: 0.95rem 0.55rem 1.05rem 0.55rem;
border-bottom: 0 !important;
background: radial-gradient( circle at 50% 25%, rgba( 255, 138, 0, 0.08 ), transparent 58% );
}
/* Each nav group gets real breathing room from the one before it instead
of being packed together like a stock wiki sidebar. */

/* Sidebar Discord invite CTA: injected by MediaWiki:Common.js directly below
the logo and above the first generated Vector portlet, matching the compact
community-button placement shown in the reference screenshot. */
.edfm-discord-cta {
display: inline-flex;
align-items: center;
justify-content: center;
gap: 0.42rem;
box-sizing: border-box;
width: calc( 100% - 1.35rem );
min-height: 1.78rem;
margin: 0.35rem 0.675rem 1.05rem 0.675rem;
padding: 0.36rem 0.56rem;
border-radius: 4px;
background: #5865f2;
color: #fff !important;
font-size: 0.76rem;
font-weight: 700;
line-height: 1.1;
text-align: center;
text-decoration: none !important;
box-shadow: 0 2px 5px rgba( 0, 0, 0, 0.35 );
transition: background-color 120ms ease, box-shadow 120ms ease, transform 120ms ease;
}
.edfm-discord-cta:hover,
.edfm-discord-cta:focus {
background: #4752c4;
color: #fff !important;
text-decoration: none !important;
box-shadow: 0 3px 8px rgba( 0, 0, 0, 0.42 );
transform: translateY( -1px );
}
.edfm-discord-cta-icon {
display: inline-flex;
width: 1rem;
height: 1rem;
flex: 0 0 auto;
}
.edfm-discord-cta-icon svg {
display: block;
width: 100%;
height: 100%;
fill: currentColor;
}

#mw-panel .portal,
#mw-panel .vector-menu-portal {
box-sizing: border-box;
width: auto;
max-width: none;
margin-top: 1.45rem;
}
#mw-panel .portal:first-of-type,
#mw-panel .vector-menu-portal:first-of-type {
margin-top: 0;
}
#mw-panel .portal .body,
#mw-panel .portal ul,
#mw-panel .vector-menu-content,
#mw-panel .vector-menu-content-list {
box-sizing: border-box;
width: auto;
max-width: none;
margin-left: 0;
margin-right: 0;
padding-left: 0;
border-color: var( --edfm-border-soft );
}
#mw-panel .portal a {
color: var( --edfm-text-muted );
display: block;
font-size: var( --edfm-fs-sidebar );
line-height: 1.35;
padding: 0.42em 0.55em;
margin: 0.08em -0.35em;
border-left: 2px solid transparent;
border-radius: 2px;
}
#mw-panel .portal a:hover {
color: var( --edfm-cyan );
background: var( --edfm-surface-1 );
}
/* "You are here" -- MediaWiki's sidebar has no built-in current-page
indication; MediaWiki:Common.js adds the .edfm-nav-current class to the
matching list item by comparing hrefs to the current URL. Orange is
reserved for exactly this kind of "important navigation / selected
state" per the colour system, which is why the rest of the sidebar is
deliberately muted rather than orange throughout (an all-orange sidebar
would both fight this indicator and read as visually dominant). */
.edfm-nav-current > a {
color: var( --edfm-orange ) !important;
font-weight: 700;
border-left-color: var( --edfm-orange );
border-left-width: 3px;
background: var( --edfm-surface-2 );
box-shadow: inset 0 0 0 1px rgba( 255, 138, 0, 0.08 );
}
.vector-menu-heading {
color: var( --edfm-text-dim );
font-weight: 700;
font-family: var( --edfm-mono );
letter-spacing: 0.08em;
text-transform: uppercase;
font-size: var( --edfm-fs-utility );
border-left: 2px solid var( --edfm-orange );
padding-left: 0.5em;
margin-left: -0.5em;
margin-bottom: 0.4em;
}

/* ==========================================================================
3. TOP BAR -- two-tier chrome
========================================================================== */
/* Vector legacy's #mw-head naturally has ~2.5em of empty space above the
tabs row (core: `#left-navigation/#right-navigation { margin-top:2.5em }`),
originally reserved just for #p-personal to float in. Painting that same
box with a background gradient that stays transparent for that top
band and then switches to a surface colour for the tabs band creates a
real two-tier read -- "primary chrome" (personal tools/search, over the
page's own background) above "wiki authoring controls" (the tabs, on
their own distinct strip) below -- without touching #mw-head's own
position/width mechanics, which is the same fragile absolute-position
system the very first pass of this project had to debug carefully to
get the persistent sidebar working at all. Not worth re-risking that
for a background change. */
#mw-head {
background-image: linear-gradient(
to bottom,
transparent 0,
transparent 2.35em,
var( --edfm-surface-2 ) 2.35em,
var( --edfm-surface-2 ) 100%
);
border-bottom: 1px solid var( --edfm-border );
}
#mw-page-base {
background-color: var( --edfm-bg-deep );
background-image: none;
}
#mw-head-base {
background-color: var( --edfm-bg-deep );
/* Polish pass: thinned from 2px -- at 2px this competed visually with
the masthead's own orange marker/rule directly below it; a single
thinner accent line still reads as "site identity colour" without
the repetition. */
border-bottom: 1px solid var( --edfm-orange );
}
/* Personal tools (login/logout) and the search box are the "primary
chrome" tier -- pulled in by the same gutter used to centre the article,
so on wide screens they visually line up with the centred column
instead of hugging the browser edge, and given noticeably more visual
weight than the tabs below them. */
#p-personal {
right: calc( 0.75em + var( --edfm-gutter ) );
display: flex;
align-items: center;
gap: 0.75rem;
}
#p-personal ul {
display: flex;
align-items: center;
gap: 0.55rem;
}
#p-personal li {
margin-left: 0;
}
#p-personal a {
color: var( --edfm-text-muted );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-sidebar );
padding: 0.3em 0.2em;
}
#p-personal a:hover {
color: var( --edfm-orange );
}
.edfm-topbar-clocks {
display: inline-flex;
align-items: center;
gap: 0.5rem;
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-sidebar );
line-height: 1;
white-space: nowrap;
}
.edfm-topbar-clock {
display: inline-flex;
align-items: center;
gap: 0.3em;
padding: 0.3em 0.55em;
background: rgba( 66, 199, 217, 0.08 );
border: 1px solid var( --edfm-border-soft );
border-left: 2px solid var( --edfm-cyan );
color: var( --edfm-text );
}
.edfm-topbar-clock-label {
color: var( --edfm-text-dim );
font-size: var( --edfm-fs-utility );
letter-spacing: 0.08em;
text-transform: uppercase;
}
.edfm-topbar-clock time {
color: var( --edfm-cyan );
font-weight: 700;
}
.edfm-topbar-clock-local {
background: rgba( 255, 138, 0, 0.06 );
border-left-color: var( --edfm-orange );
}
.edfm-topbar-clock-local time {
color: var( --edfm-orange-bright );
}
#right-navigation {
margin-right: var( --edfm-gutter );
}
#left-navigation {
margin-left: var( --edfm-sidebar-clear );
}
/* Polish pass: core caps this at `width:20vw; max-width:20em`, which read
as cramped next to the rest of the (now larger-scale) interface --
given more room on desktop, still capped so it can't dominate the bar. */
.vector-search-box-inner {
width: 22vw;
max-width: 24em;
}
.vector-search-box-inner input,
#searchInput {
background-color: var( --edfm-surface-3 );
color: var( --edfm-text );
border: 1px solid var( --edfm-border );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-sidebar );
padding: 0.5em 0.7em;
transition: border-color 0.15s ease, box-shadow 0.15s ease;
}
#searchInput:focus {
border-color: var( --edfm-cyan );
box-shadow: 0 0 0 2px rgba( 66, 199, 217, 0.22 );
outline: none;
}
#searchInput::placeholder {
color: var( --edfm-text-dim );
}
/* Namespace tabs (Main Page / Discussion, left) and view tabs
(Read / Edit / View history, right) both use Vector legacy's
.vector-menu-tabs-legacy markup. Core skin CSS paints every tab `li`
with a gradient fading to white and forces the selected tab to pure
white -- neither is touched by recolouring the link text alone, which is
why these stayed light before this stylesheet covered the `li`
background too. Core also has an `a:visited` rule (higher specificity
than a plain `a` rule, since a pseudo-class counts the same as a class)
that reasserts a near-black "visited" colour meant for a white
background; since these tabs point at pages you've almost always
already visited, without an explicit `:visited` override here the text
goes dark-on-dark. This can't be caught by reading getComputedStyle() in
an automated check -- browsers deliberately report the *unvisited*
colour to JS for privacy reasons, so it only shows up on an actual
screen; verified with real rendered screenshots, including after
genuinely visiting the linked pages first.

These are the "wiki authoring controls" utility tier -- deliberately
smaller (--edfm-fs-utility) and quieter than personal-tools/search
above them, sitting on their own background strip (see #mw-head above).
Selected state stays orange (it's still real navigation, just
secondary); unselected rests dim so the *selected* tab is the one that
reads clearly. */
.vector-menu-tabs-legacy li {
background-image: none;
background-color: transparent;
}
.vector-menu-tabs-legacy li.selected {
background-image: none;
background-color: var( --edfm-surface-1 );
/* Polish pass: a small underline makes the selected tab unambiguous at
a glance instead of relying on the text colour change alone. */
box-shadow: inset 0 -2px 0 var( --edfm-orange );
}
.vector-menu-tabs-legacy li a,
.vector-menu-tabs-legacy li a:visited {
background-color: transparent;
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-utility );
letter-spacing: 0.03em;
text-transform: uppercase;
font-weight: 700;
}
.vector-menu-tabs-legacy li a:hover,
.vector-menu-tabs-legacy li a:visited:hover {
color: var( --edfm-text );
}
.vector-menu-tabs-legacy li.selected a,
.vector-menu-tabs-legacy li.selected a:visited {
color: var( --edfm-orange );
}
.vector-menu-tabs-legacy li.new a,
.vector-menu-tabs-legacy li.new a:visited {
color: var( --edfm-link-new );
}
/* "More" actions dropdown (#p-cactions) sits in the same tab row; same
:visited gotcha applies to its menu items. */
.vector-menu-dropdown .vector-menu-heading {
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
border-left: none;
padding-left: 8px;
margin-left: 0;
margin-bottom: 0;
text-transform: uppercase;
letter-spacing: 0.03em;
font-size: var( --edfm-fs-utility );
font-weight: 700;
}
.vector-menu-dropdown .vector-menu-heading:hover,
.vector-menu-dropdown .vector-menu-heading:focus {
color: var( --edfm-orange );
}
.vector-menu-dropdown .vector-menu-content {
background-color: var( --edfm-surface-3 );
border-color: var( --edfm-border );
}
.vector-menu-dropdown .vector-menu-content a,
.vector-menu-dropdown .vector-menu-content a:visited {
color: var( --edfm-text-muted );
font-size: var( --edfm-fs-sidebar );
}
.vector-menu-dropdown .vector-menu-content li.selected a,
.vector-menu-dropdown .vector-menu-content li.selected a:visited {
color: var( --edfm-orange );
}
.vector-menu-dropdown .vector-menu-content li:hover {
background-color: var( --edfm-surface-4 );
}

/* ==========================================================================
CONTENT / ARTICLE SURFACE
========================================================================== */
.mw-body,
.parsoid-body {
background-color: var( --edfm-surface-1 );
color: var( --edfm-text );
border-color: var( --edfm-border );
font-family: var( --edfm-sans );
}
.mw-body {
border-right: 1px solid var( --edfm-border );
}
#content {
background-color: var( --edfm-surface-1 );
}

/* Site notice chrome. The global disclaimer was moved to its dedicated
legal/disclaimer page, so an empty #siteNotice must not leave behind a
phantom divider at the top of the article surface. */
#siteNotice:empty {
display: none;
}
#siteNotice:not( :empty ) {
font-size: var( --edfm-fs-meta );
line-height: 1.5;
color: var( --edfm-text-dim );
font-style: normal;
padding-bottom: 0.7em;
margin-bottom: 1.4rem;
border-bottom: 1px solid var( --edfm-border-soft );
}
#siteNotice:not( :empty ) em, #siteNotice:not( :empty ) i {
color: var( --edfm-text-muted );
font-style: italic;
}
#siteNotice:not( :empty ) a {
color: var( --edfm-link-external );
}
#siteNotice a:hover {
color: var( --edfm-link-external-hover );
}

/* ==========================================================================
HOME PAGE DASHBOARD
========================================================================== */
.edfm-home-hero {
margin: 0.9rem 0 1.6rem;
padding: 1.35rem 1.55rem;
background:
linear-gradient( 135deg, rgba( 255, 138, 0, 0.16 ), transparent 34% ),
linear-gradient( 315deg, rgba( 66, 199, 217, 0.14 ), transparent 42% ),
var( --edfm-surface-2 );
border: 1px solid var( --edfm-border );
border-left: 4px solid var( --edfm-cyan );
clip-path: polygon( 0 0, calc( 100% - 12px ) 0, 100% 12px, 100% 100%, 0 100% );
}
.edfm-home-hero-kicker,
.edfm-home-card-kicker {
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-meta );
font-weight: 800;
letter-spacing: 0.1em;
text-transform: uppercase;
}
.edfm-home-hero-title {
margin-top: 0.25rem;
color: var( --edfm-text );
font-family: var( --edfm-mono );
font-size: clamp( 1.55rem, 1.1rem + 1.5vw, 2.2rem );
font-weight: 800;
line-height: 1.15;
}
.edfm-home-hero-text {
max-width: 52rem;
margin-top: 0.55rem;
color: var( --edfm-text-muted );
font-size: 1.05rem;
line-height: 1.55;
}
.edfm-home-grid {
display: grid;
gap: 1rem;
margin: 1.2rem 0 2rem;
}
.edfm-home-grid-four {
grid-template-columns: repeat( 4, minmax( 0, 1fr ) );
}
.edfm-home-grid-topics {
grid-template-columns: repeat( 2, minmax( 0, 1fr ) );
}
.edfm-home-grid-two {
grid-template-columns: repeat( 2, minmax( 0, 1fr ) );
}
.edfm-home-card {
background: var( --edfm-surface-2 );
border: 1px solid var( --edfm-border );
border-left: 3px solid var( --edfm-cyan );
padding: 1rem 1.1rem;
box-shadow: 0 12px 24px rgba( 0, 0, 0, 0.2 );
transition: transform 0.15s ease, border-color 0.15s ease, background-color 0.15s ease;
}
.edfm-home-card:hover {
transform: translateY( -2px );
background: var( --edfm-surface-3 );
border-left-color: var( --edfm-orange );
}
.edfm-home-card-primary {
border-left-color: var( --edfm-orange );
}
.edfm-home-card-warning {
border-left-color: var( --edfm-text-dim );
}
.edfm-home-card-title,
.edfm-home-card-title a {
margin-top: 0.35rem;
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
font-size: 1.05rem;
font-weight: 800;
line-height: 1.3;
text-decoration: none;
}
.edfm-home-card-title a:hover {
color: var( --edfm-orange-bright ) !important;
}
.edfm-home-card-text,
.edfm-home-link-list {
margin-top: 0.65rem;
color: var( --edfm-text-muted );
line-height: 1.6;
}
.edfm-home-link-list a {
font-weight: 600;
}
@media ( max-width: 1100px ) {
.edfm-home-grid-four {
grid-template-columns: repeat( 2, minmax( 0, 1fr ) );
}
}
@media ( max-width: 760px ) {
.edfm-home-grid-four,
.edfm-home-grid-topics,
.edfm-home-grid-two {
grid-template-columns: 1fr;
}
}

/* ==========================================================================
HOME PAGE NEWS MODULE
========================================================================== */
.edfm-home-news {
margin: 1.8rem 0 2.2rem;
}
.edfm-news-feature-grid {
display: grid;
grid-template-columns: repeat( 3, minmax( 0, 1fr ) );
gap: 1rem;
margin-bottom: 1rem;
}
.edfm-news-card,
.edfm-news-list {
background: var( --edfm-surface-2 );
border: 1px solid var( --edfm-border );
box-shadow: 0 14px 26px rgba( 0, 0, 0, 0.22 );
overflow: hidden;
}
.edfm-news-card {
display: flex;
flex-direction: column;
min-height: 100%;
transition: transform 0.15s ease, border-color 0.15s ease, background-color 0.15s ease;
}
.edfm-news-card:hover {
transform: translateY( -2px );
border-color: rgba( 255, 138, 0, 0.48 );
background: var( --edfm-surface-3 );
}
.edfm-news-card-art {
display: flex;
align-items: flex-end;
min-height: 7rem;
padding: 0.8rem 1rem;
box-sizing: border-box;
background:
linear-gradient( 135deg, rgba( 255, 138, 0, 0.28 ), transparent 42% ),
linear-gradient( 315deg, rgba( 66, 199, 217, 0.2 ), transparent 48% ),
linear-gradient( 180deg, var( --edfm-surface-4 ), var( --edfm-surface-1 ) );
border-bottom: 1px solid var( --edfm-border );
color: rgba( 237, 240, 242, 0.72 );
font-family: var( --edfm-mono );
font-size: 0.8rem;
font-weight: 800;
letter-spacing: 0.16em;
text-transform: uppercase;
}
.edfm-news-card-primary .edfm-news-card-art {
background:
linear-gradient( 135deg, rgba( 255, 138, 0, 0.38 ), transparent 46% ),
linear-gradient( 315deg, rgba( 79, 159, 232, 0.26 ), transparent 52% ),
var( --edfm-surface-4 );
}
.edfm-news-card-body {
padding: 1rem 1.15rem 1.15rem;
}
.edfm-news-meta {
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-meta );
letter-spacing: 0.04em;
text-transform: uppercase;
margin-bottom: 0.35rem;
}
.edfm-news-title,
.edfm-news-title a {
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
font-size: 1.1rem;
font-weight: 800;
line-height: 1.25;
text-decoration: none;
}
.edfm-news-title a:hover {
color: var( --edfm-orange-bright ) !important;
}
.edfm-news-summary {
color: var( --edfm-text-muted );
line-height: 1.55;
margin-top: 0.65rem;
}
.edfm-news-list {
padding: 1.1rem 1.25rem 1.2rem;
border-left: 4px solid var( --edfm-orange );
}
.edfm-news-list-heading {
color: var( --edfm-text );
font-family: var( --edfm-mono );
font-size: 1.05rem;
font-weight: 800;
letter-spacing: 0.04em;
text-transform: uppercase;
margin-bottom: 0.75rem;
}
.edfm-news-list ul {
margin: 0;
}
.edfm-news-list li {
margin-bottom: 0.55rem;
color: var( --edfm-text-muted );
}
.edfm-news-more {
margin-top: 0.9rem;
padding-top: 0.85rem;
border-top: 1px solid var( --edfm-border-soft );
text-align: right;
font-family: var( --edfm-mono );
font-weight: 800;
letter-spacing: 0.03em;
text-transform: uppercase;
}
@media ( max-width: 900px ) {
.edfm-news-feature-grid {
grid-template-columns: 1fr;
}
}

/* ==========================================================================
10. JUMP NAVIGATION (table of contents)
========================================================================== */
/* A compact navigation strip/tile-grid rather than a traditional TOC box
of small text links -- real MediaWiki anchors/markup untouched, this is
all presentation. "Contents" is kept in the DOM for screen readers/
no-JS/no-CSS fallback (more standard wording there anyway) and visually
replaced with "Jump to" via ::before on the wrapper, with the real
heading text hidden via font-size rather than display:none so it
remains in the accessibility tree. */
#toc, .toc {
display: block;
width: 100%;
box-sizing: border-box;
background: none;
border: none;
color: var( --edfm-text );
padding: 0;
margin: 1.8rem 0;
}
.toctitle {
position: relative;
margin-bottom: 0.7em;
}
.toctitle::before {
content: 'Jump to';
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-meta );
font-weight: 700;
letter-spacing: 0.12em;
text-transform: uppercase;
color: var( --edfm-orange );
}
/* Core ships `.toc h2 { font-size: 100%; ... }` (mediawiki.skinning/toc/
screen.less) at the exact same specificity (one class + one tag) as a
plain `.toctitle h2` rule -- same "tie that doesn't resolve the way
naive source order would suggest" gotcha documented elsewhere in this
file. #toc's own ID makes this one unambiguous instead of relying on
cascade order. */
#toc .toctitle h2,
.toc .toctitle h2 {
font-size: 0 !important;
line-height: 0;
margin: 0;
border: none;
padding: 0;
display: inline;
}
.toctitle h2::before,
.toctitle h2::after {
content: none;
}
.toctogglelabel::before {
color: var( --edfm-text-dim );
}
/* Desktop: a real grid of clickable tiles (3 columns suits this site's
typical 5-8 top-level sections well: commonly 2-3 rows) instead of one
long line of small text. Each tile has its own surface, a visible
boundary via the accent rail (not a full border -- see "stop using a
border around everything"), and an obvious hover state. */
.toc > ul {
display: grid;
grid-template-columns: repeat( 4, 1fr );
gap: 0.45rem;
list-style: none;
margin: 0;
padding: 0;
}
.toc li {
margin: 0;
}
/* 2026-08-08 density pass: reverted to side-by-side number/label (from the
earlier "stacked number-above-label" polish pass) specifically to cut
per-tile height -- with 12 sections on articles like The Dweller, the
stacked layout meant the jump nav alone filled most of the first
viewport. Row layout plus tighter padding/font-size gets noticeably
more sections above the fold without dropping the numbering or shrinking
tap targets below a comfortable size -- see the dedicated mobile padding
bump further down for keeping touch targets safe on small screens
specifically. Whole tile stays one real <a>, so it's still a single
click/focus target and keyboard tab stop either way. */
.toc a {
display: flex;
flex-direction: row;
align-items: center;
gap: 0.5em;
height: 100%;
box-sizing: border-box;
padding: 0.5em 0.75em 0.5em 0.7em;
background: var( --edfm-surface-3 );
/* Left accent rail: matches the orange section numbers and gives each
jump tile a stronger EDFM navigation affordance without boxing the
entire card. */
border-left: 4px solid var( --edfm-orange );
box-shadow: inset 1px 0 0 rgba( 255, 162, 26, 0.35 );
color: var( --edfm-text-muted );
text-decoration: none;
transition: background-color 0.15s ease, border-color 0.15s ease, box-shadow 0.15s ease, color 0.15s ease, transform 0.15s ease;
}
.toc a:hover {
background: var( --edfm-surface-4 );
border-left-color: var( --edfm-cyan );
box-shadow: inset 1px 0 0 rgba( 66, 199, 217, 0.45 );
color: var( --edfm-text );
transform: translateY( -1px );
}
/* Nested sub-levels (rare on this site so far) drop back to a plain
indented block list inside their parent tile's grid cell rather than
trying to stay gridded themselves. */
.toc ul ul {
grid-column: unset;
list-style: none;
margin: 0.3em 0 0 1.2em;
padding: 0;
display: block;
}
.toc ul ul a {
flex-direction: row;
align-items: center;
background: none;
border-left-width: 1px;
padding: 0.3em 0.6em;
}
.toc ul ul .tocnumber {
font-size: 0.85em;
}
.toc ul ul .toctext {
font-size: 0.85em;
}
.tocnumber {
color: var( --edfm-orange );
font-family: var( --edfm-mono );
font-weight: 700;
font-size: 1.05rem;
line-height: 1;
}
.toctext {
color: inherit;
font-size: 0.85rem;
line-height: 1.3;
}
/* 2026-08-08: rebalanced for the 4-column desktop default above -- was
>1150px = 3 cols -> <=1150px = 2 cols -> <=560px = 1 col. A page with
12 sections (e.g. The Dweller) now gets 3 rows at desktop width instead
of 4, so a new <=860px step was added rather than dropping straight
from 3 to 2 columns at 1150px, which left the same "Star systems,
navigation and exploration"-style long labels cramped in the 1024px
range this breakpoint set was originally tuned for. Order stays widest
condition first, narrowest last, so cascade order matches the max-width
overlap correctly at every width. */
@media ( max-width: 1150px ) {
.toc > ul {
grid-template-columns: repeat( 3, 1fr );
}
}
@media ( max-width: 860px ) {
.toc > ul {
grid-template-columns: repeat( 2, 1fr );
}
}
@media ( max-width: 560px ) {
.toc > ul {
grid-template-columns: 1fr;
}
/* Single-column tiles are already full-width here, so there's no
density pressure left -- restore closer to the pre-2026-08-08
padding instead of the tighter desktop value, keeping tap targets
comfortable rather than compacting mobile just because desktop
compacted. */
.toc a {
padding: 0.7em 0.95em;
}
}

/* ==========================================================================
6. PANELS / CALLOUTS, and 11. ARTICLE METADATA / STATUS MODULE
========================================================================== */
/* Deliberately NOT defined here. .edfm-box / .edfm-panel* / .edfm-status* /
.edfm-inline-flag / .edfm-related* are used exclusively by the
editorial templates (see Template:Article status, Template:Draft
warning, Template:Related articles, etc.), which already load
Template:EDFM style/styles.css themselves via <templatestyles>.
Defining the same class names in both this file and that one would
leave their relative precedence dependent on unclear/unstable ordering
between a ResourceLoader "site" stylesheet and a TemplateStyles-injected
<style> tag -- rather than rely on that, there is exactly one definition
of each, living in Template:EDFM style/styles.css. That file freely uses
the --edfm-* custom properties defined above; custom properties resolve
through the DOM regardless of which stylesheet declared vs references
them, so this split costs nothing. */

/* ==========================================================================
7. TABLES (wikitables, and Special: pages' tables)
========================================================================== */
table.wikitable,
table.mw-datatable {
background-color: var( --edfm-surface-2 );
color: var( --edfm-text );
border-color: var( --edfm-border );
font-size: var( --edfm-fs-body );
}
table.wikitable > tr > th,
table.wikitable > * > tr > th {
background-color: var( --edfm-surface-3 );
color: var( --edfm-text );
border-color: var( --edfm-border );
font-family: var( --edfm-mono );
letter-spacing: 0.03em;
text-transform: uppercase;
font-size: var( --edfm-fs-meta );
text-align: left;
padding: 0.6em 0.8em;
}
table.wikitable > tr > td,
table.wikitable > * > tr > td {
border-color: var( --edfm-border-soft );
padding: 0.6em 0.8em;
}
/* Subtle alternating row treatment -- helps scanning wide/dense reference
tables without turning them into cards. */
table.wikitable > tbody > tr:nth-child( even ),
table.wikitable > * > tr:nth-child( even ) {
background-color: var( --edfm-surface-1 );
}

/* ==========================================================================
15. FOOTER
========================================================================== */
/* A real branded footer: a small wordmark line (pure CSS generated
content -- decorative branding only, redundant with the sidebar logo
already visible, so nothing load-bearing depends on it being
selectable), a top rule with more separation from the article above it,
and MediaWiki's real info/places/icon links laid out on a clean grid
with the badges aligned as a group rather than floating alone. */
.mw-footer {
margin-left: var( --edfm-sidebar-clear );
margin-right: var( --edfm-gutter );
margin-top: 2.5rem;
padding-top: 1.6rem;
border-top: 1px solid var( --edfm-border );
display: grid;
grid-template-columns: 1fr auto;
grid-template-areas: "brand brand" "info icons" "places icons";
align-items: center;
column-gap: 2em;
row-gap: 0.4rem;
}
.mw-footer::before {
grid-area: brand;
content: 'EDFM // Elite Dangerous Field Manual';
font-family: var( --edfm-mono );
font-size: 0.85rem;
font-weight: 700;
letter-spacing: 0.06em;
text-transform: uppercase;
color: var( --edfm-text-muted );
margin-bottom: 0.5rem;
}
.mw-footer,
.mw-footer li,
#footer-info,
#footer-info li {
color: var( --edfm-text-dim );
border-color: var( --edfm-border-soft );
font-size: var( --edfm-fs-meta );
}
#footer-info {
grid-area: info;
margin: 0;
line-height: 1.6;
}
#footer-places {
grid-area: places;
margin: 0;
}
/* Same "small uppercase label" treatment used for tags/meta text
elsewhere, so these read as deliberate EDFM navigation rather than
default MediaWiki footer links. */
#footer-places li {
display: inline-block;
margin-right: 1.4em;
}
#footer-places a {
font-family: var( --edfm-mono );
font-weight: 700;
letter-spacing: 0.03em;
text-transform: uppercase;
font-size: 0.78rem;
}
/* A left rule ties the badges to the rest of the footer instead of
letting them read as detached/floating in their own space. */
#footer-icons {
grid-area: icons;
align-self: center;
display: flex;
gap: 0.75em;
margin: 0;
padding-left: 1.6em;
border-left: 1px solid var( --edfm-border-soft );
}
#footer-icons img {
background: var( --edfm-text );
border-radius: 2px;
}
@media ( max-width: 640px ) {
.mw-footer {
grid-template-columns: 1fr;
grid-template-areas: "brand" "info" "places" "icons";
}
#footer-icons {
margin-top: 0.7em;
padding-left: 0;
border-left: none;
border-top: 1px solid var( --edfm-border-soft );
padding-top: 0.7em;
}
}

/* ==========================================================================
MISC MediaWiki UI chrome that ships with light backgrounds by default
========================================================================== */
.catlinks {
background: none !important;
border: none !important;
border-top: 1px solid var( --edfm-border-soft ) !important;
color: var( --edfm-text-dim );
font-size: var( --edfm-fs-meta );
padding: 0.9em 0 0 0 !important;
margin-top: 1.8rem !important;
}
div.thumbinner {
background-color: var( --edfm-surface-2 );
border-color: var( --edfm-border );
}
.thumbimage {
background-color: var( --edfm-surface-1 );
border-color: var( --edfm-border );
}

/* Code / preformatted text (syntaxhighlight uses its own Pygments theme,
set via $wgPygmentsStyle in LocalSettings.php; this covers plain
<pre>/<code> that isn't Pygments-highlighted). */
pre, code, .mw-code {
background-color: var( --edfm-surface-2 );
color: var( --edfm-text );
border-color: var( --edfm-border );
font-family: var( --edfm-mono );
}

/* ==========================================================================
GENERIC INFOBOX -- see Template:Infobox
========================================================================== */
.edfm-infobox {
float: right;
clear: right;
width: 310px;
margin: 0 0 1.2em 1.2em;
border: 1px solid var( --edfm-border );
border-top: 2px solid var( --edfm-orange );
background: var( --edfm-surface-2 );
color: var( --edfm-text );
font-size: 0.92rem;
}
.edfm-infobox-title {
background: var( --edfm-orange );
color: var( --edfm-bg-deep );
font-weight: 700;
font-family: var( --edfm-mono );
letter-spacing: 0.04em;
text-transform: uppercase;
text-align: center;
padding: 0.5em 0.6em;
clip-path: polygon( 0 0, calc( 100% - 14px ) 0, 100% 14px, 100% 100%, 0 100% );
}
.edfm-infobox-image {
text-align: center;
padding: 0.6em;
border-bottom: 1px solid var( --edfm-border );
}
.edfm-infobox-image-placeholder {
display: flex;
align-items: center;
justify-content: center;
height: 160px;
border: 1px dashed var( --edfm-border );
background: var( --edfm-surface-1 );
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-utility );
text-transform: uppercase;
letter-spacing: 0.06em;
text-align: center;
padding: 0.5em;
}
/* Optional section label (Template:Infobox's |groupN=) splitting a long
infobox into scannable groups, e.g. Engineer infoboxes into "ENGINEER"
and "ACCESS" (2026-08-08, part of the Engineer article layout pass). A
shaded band with a bottom rule rather than a full boxed sub-header --
consistent with .edfm-infobox-row's own bottom-rule-only separator, not
a new visual language. */
.edfm-infobox-group {
background: var( --edfm-surface-3 );
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
font-weight: 700;
font-size: var( --edfm-fs-utility );
letter-spacing: 0.08em;
text-transform: uppercase;
padding: 0.35em 0.7em;
border-bottom: 1px solid var( --edfm-border );
}
.edfm-infobox-row {
display: flex;
border-bottom: 1px solid var( --edfm-border-soft );
padding: 0.45em 0.7em;
}
.edfm-infobox-row:last-child {
border-bottom: none;
}
.edfm-infobox-label {
font-weight: 700;
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-meta );
width: 40%;
flex-shrink: 0;
color: var( --edfm-cyan );
}
.edfm-infobox-value {
width: 60%;
}
@media ( max-width: 640px ) {
.edfm-infobox {
float: none;
width: auto;
margin: 1em 0;
}
}

/* ==========================================================================
14. MOBILE
========================================================================== */
/* Vector legacy has NO built-in responsive breakpoint at all (unlike
Vector 2022) -- its entire header region (#mw-head, tabs, search,
personal tools/login) is built with absolute positioning and floats
that all assume a fixed-width sidebar reserving 10-11em on the left,
AND the page's actual DOM order is content-then-navigation-then-footer
(the absolute positioning was doing double duty: both moving the header
visually to the top AND compensating for that DOM order). Simply
removing the positioning stacks things in DOM order, which reads oddly
on a phone (article text, then the nav/sidebar, then the footer).
Confirmed the actual DOM structure directly (not guessed): <body>'s
real children are #mw-page-base, #mw-head-base, #content,
#mw-navigation (which itself contains #mw-head then #mw-panel, already
in the right relative order), #footer. Since all four major regions are
direct children of <body>, flexbox `order` on <body> can reorder them
properly without needing to touch the DOM itself.
Result: header/search/tabs, then sidebar nav, then content, then
footer -- a plain stacked mobile layout, not a collapsible hamburger
menu, but a correct and readable order. */
@media ( max-width: 800px ) {
body::before {
display: none;
}
body {
display: flex;
flex-direction: column;
}
/* #mw-head-base ships with `margin-top: -5em` in Vector legacy's own
CSS -- a trick to sit it behind the absolutely-positioned header.
Now that the header is a normal flex sibling, that negative margin
drags everything after it upward. Neutralize both decorative
strips. */
#mw-page-base,
#mw-head-base {
order: 0;
height: 0;
margin: 0;
min-height: 0;
}
#mw-navigation {
order: 1;
}
#content {
order: 2;
}
.mw-footer {
order: 3;
}

#mw-head {
position: static;
width: auto;
background-image: none;
background-color: var( --edfm-surface-2 );
}
#left-navigation,
#right-navigation {
float: none;
margin: 0 !important;
width: auto;
clear: both;
}
#left-navigation {
margin-top: 0 !important;
}
/* Core Vector legacy floats each tab/dropdown portlet
(.vector-menu-tabs-legacy for Page/Discussion and Read/View
source/View history, .vector-menu-dropdown for the More menu) AND
floats every <li> inside their <ul>, with no wrapping at all -- at
narrow widths the labels just overflow and overlap each other
(confirmed with a real screenshot: "View source" and "More"
overlapped instead of wrapping to a new line). Switching the
portlets to inline-block and their tab lists to flex-wrap lets them
reflow onto as many rows as needed instead. */
#left-navigation .vector-menu-tabs-legacy,
#right-navigation .vector-menu-tabs-legacy,
#right-navigation .vector-menu-dropdown {
float: none;
display: inline-block;
vertical-align: top;
}
.vector-menu-tabs-legacy ul {
float: none;
display: flex;
flex-wrap: wrap;
}
.vector-menu-tabs-legacy li {
float: none;
}
#p-personal {
position: static;
text-align: right;
padding: 0.5em 1em;
margin: 0;
right: auto !important;
top: auto;
}
#p-personal ul {
padding-left: 0;
}
.vector-search-box {
float: none;
margin: 0.5em 1em;
display: block;
}
.vector-search-box-inner {
width: auto;
max-width: none;
}
#mw-panel {
position: static;
width: auto;
padding: 0.5em 1em;
float: none;
background: var( --edfm-bg-deep );
border-top: 1px solid var( --edfm-border );
border-bottom: 1px solid var( --edfm-border );
}
.mw-body,
#mw-data-after-content,
.mw-footer {
margin-left: 0 !important;
margin-right: 0 !important;
max-width: none;
}
.mw-body {
margin-top: 0;
border-width: 0;
padding: 1em;
}
.edfm-status-details {
grid-template-columns: 1fr;
}
/* .toc > ul column count is NOT overridden here -- the dedicated
1150px/560px breakpoints above already cover every width down to
the smallest phones; duplicating a rule here previously fought
those (same specificity, this position in the cascade would have
won and wrongly forced 1 column as low as 561px). */
#firstHeading {
font-size: 1.6rem;
}
.mw-body h2 {
margin-top: 2.25rem;
}
.edfm-eyebrow {
padding-top: 0.9em;
}
}
/* ==========================================================================
16. OOUI DIALOGS -- VisualEditor's save dialog, and any other OOUI
dialog (delete/move/protect confirmations, special-page dialogs).
These render via OOUI's own bundled WikimediaUI theme stylesheet,
entirely outside the .edfm-* component system this file otherwise
covers, so without this they show up starkly white against the rest of
the dark-themed site regardless of any variable/token used elsewhere in
this file. !important is justified the same way as the h1-h6 fix above:
OOUI's own stylesheet loads with equal-or-higher effective specificity,
and this is a correctness/contrast fix, not decoration.
========================================================================== */
.oo-ui-window-frame {
background: var( --edfm-surface-2 ) !important;
color: var( --edfm-text ) !important;
}
.oo-ui-processDialog {
background: rgba( 7, 9, 11, 0.75 ) !important;
}
.oo-ui-processDialog-navigation,
.oo-ui-window-head,
.oo-ui-window-foot {
background: var( --edfm-surface-3 ) !important;
border-color: var( --edfm-border ) !important;
}
.oo-ui-processDialog-title,
.oo-ui-labelElement-label,
.oo-ui-fieldLayout-header,
.oo-ui-fieldLayout .oo-ui-labelElement-label {
color: var( --edfm-text ) !important;
}
.oo-ui-inputWidget-input {
background: var( --edfm-surface-1 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}
.ve-ui-mwSaveDialog-options,
.oo-ui-panelLayout,
.oo-ui-window-body {
background: var( --edfm-surface-2 ) !important;
color: var( --edfm-text ) !important;
}
.oo-ui-popupWidget-popup {
background: var( --edfm-surface-2 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}
.oo-ui-buttonElement:not( .oo-ui-flaggedElement-primary ) > .oo-ui-buttonElement-button {
background: var( --edfm-surface-4 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}
/* ==========================================================================
17. OOUI TOOLBAR -- VisualEditor's persistent editing toolbar and its
dropdown menus (Cite, Insert, paragraph style, etc.), and the equivalent
toolbar/popups used when editing a single section. Same root cause as
16. OOUI DIALOGS above (OOUI's own bundled theme, not touched by
anything else in this file), found separately because it's a different
set of OOUI classes (toolbar chrome, not dialog chrome). Icons are not
overridden here and don't need to be -- they're currentColor-based, so
they pick up the text colour set below automatically.
========================================================================== */
.oo-ui-toolbar-bar,
.oo-ui-toolGroup-tools,
.oo-ui-popupToolGroup-tools {
background: var( --edfm-surface-3 ) !important;
border-color: var( --edfm-border ) !important;
}
.oo-ui-tool-title,
.oo-ui-tool-link,
.oo-ui-toolGroup-tools .oo-ui-optionWidget,
.oo-ui-menuOptionWidget,
.oo-ui-labelElement-label {
color: var( --edfm-text ) !important;
}
.oo-ui-optionWidget.oo-ui-optionWidget-selected,
.oo-ui-optionWidget:hover,
.oo-ui-tool:hover .oo-ui-tool-link {
background: var( --edfm-surface-4 ) !important;
}
/* ==========================================================================
18. OOUI GENERIC MENUS -- .oo-ui-menuSelectWidget is OOUI's general
dropdown/autocomplete menu class (paragraph-style picker, citation-type
picker, link/media search suggestions, etc.) -- a different class from
the toolbar-specific popups in 17. above, confirmed separately via
computed-style inspection to default to the same white OOUI theme
background.
========================================================================== */
.oo-ui-menuSelectWidget {
background: var( --edfm-surface-3 ) !important;
border-color: var( --edfm-border ) !important;
}
.oo-ui-menuOptionWidget {
color: var( --edfm-text ) !important;
}
.oo-ui-menuOptionWidget.oo-ui-optionWidget-highlighted,
.oo-ui-menuOptionWidget:hover {
background: var( --edfm-surface-4 ) !important;
}
/* ==========================================================================
19. OOUI ICONS -- the toolbar/menu icons themselves (Bold, link, list,
Cite, undo/redo, etc.) are rendered as background-image SVGs with a
colour baked into the SVG markup, not currentColor-based masks -- so
16-18 above (which only recolour backgrounds/text) left them dark and
low-contrast against the now-dark surfaces. OOUI ships its own fix for
exactly this, gated behind a narrow accessibility media query
(forced-colors + prefers-color-scheme: dark) that doesn't apply to this
site's own always-on dark theme -- reusing that exact technique
unconditionally rather than inventing a different one. `:not(
.oo-ui-image-invert )` is OOUI's own exclusion for icons already meant
to render light (e.g. on the orange primary-button background) --
inverting those too would flip them back to dark.
========================================================================== */
.oo-ui-iconElement-icon:not( .oo-ui-image-invert ),
.oo-ui-indicatorElement-indicator:not( .oo-ui-image-invert ) {
filter: invert( 1 ) hue-rotate( 180deg );
}
/* ==========================================================================
20. EDIT SOURCE FORM -- MediaWiki core + WikiEditor + CodeMirror

The source editor is not covered by the article/component selectors above:
`action=edit` loads core edit-form CSS, WikiEditor chrome, and sometimes
CodeMirror with their own light neutral surfaces. Force the same EDFM dark
surface stack here so the source page no longer flashes as a white island.
========================================================================== */
.mw-editform,
#editform,
#toolbar,
.editOptions,
.mw-editTools,
.mw-summary-preview,
.mw-datatable,
.wikiEditor-ui,
.wikiEditor-ui-view,
.wikiEditor-ui-text,
.wikiEditor-ui-toolbar,
.wikiEditor-ui-top,
.wikiEditor-ui-controls,
.wikiEditor-ui-tabs,
.wikiEditor-ui-buttons,
.CodeMirror,
.CodeMirror-scroll {
background: var( --edfm-surface-1 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}
.mw-editform textarea,
#wpTextbox1,
#wpSummary,
#wpSummaryWidget input,
#editform input[type='text'],
#editform input[type='search'],
#editform textarea,
.wikiEditor-ui-text textarea,
.CodeMirror-code,
.CodeMirror-lines,
.CodeMirror pre {
background: var( --edfm-bg-deep ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
caret-color: var( --edfm-orange-bright );
}
.wikiEditor-ui-toolbar,
.wikiEditor-ui-toolbar .group,
.wikiEditor-ui-toolbar .tabs,
.wikiEditor-ui-toolbar .page,
.wikiEditor-ui-toolbar .sections,
.wikiEditor-ui-toolbar .section,
.wikiEditor-ui-toolbar .options,
.wikiEditor-ui-toolbar .booklet,
.wikiEditor-ui-toolbar .pages,
.CodeMirror-gutters {
background: var( --edfm-surface-2 ) !important;
color: var( --edfm-text-muted ) !important;
border-color: var( --edfm-border ) !important;
}
.wikiEditor-ui-toolbar a,
.wikiEditor-ui-toolbar .label,
.wikiEditor-ui-toolbar .tab a,
.mw-editTools a,
.editOptions label,
.mw-editform label,
.CodeMirror-linenumber {
color: var( --edfm-text ) !important;
}
.wikiEditor-ui-toolbar .tab a:hover,
.wikiEditor-ui-toolbar .tool-button:hover,
.wikiEditor-ui-toolbar .tool-select:hover,
.wikiEditor-ui-toolbar .page-table th,
.wikiEditor-ui-toolbar .page-table td,
.CodeMirror-activeline-background {
background: var( --edfm-surface-3 ) !important;
color: var( --edfm-text ) !important;
}
.wikiEditor-ui-toolbar .tab.current a,
.wikiEditor-ui-toolbar .section-main,
.CodeMirror-selected {
background: var( --edfm-surface-4 ) !important;
}
.CodeMirror-cursor {
border-left-color: var( --edfm-orange-bright ) !important;
}
.CodeMirror-matchingbracket {
color: var( --edfm-orange-bright ) !important;
}

/* ==========================================================================
21. FILE PAGE CHROME -- #filetoc (the File / File history / File usage /
Metadata nav on File: description pages) is defined in MediaWiki core's
mediawiki.action.view.filepage.less, entirely separate from both the
.edfm-* system and the OOUI fixes in 16-19 above -- a different
subsystem again, only loaded on File: pages, which is why it was never
touched by anything else in this file. Link colour inside it already
correctly inherits the site's normal link blue; only the light neutral
background/border needed overriding.
========================================================================== */
#filetoc {
background: var( --edfm-surface-2 ) !important;
border-color: var( --edfm-border ) !important;
}
/* ==========================================================================
22. FILE PAGE: METADATA TABLE + MEDIA VIEWER BUTTON -- #mw_metadata is
the EXIF-style metadata table (separate from the File history table
above -- that one already carries the .wikitable class and picked up
dark styling from 7. TABLES automatically; this one doesn't have that
class, so it never matched). The "Open in Media Viewer" button is a
Codex component (MultimediaViewer extension) -- a third distinct
styling subsystem from OOUI and MediaWiki core skinning, again never
touched by anything else in this file.
========================================================================== */
#mw_metadata th,
#mw_metadata td {
background: var( --edfm-surface-2 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}
.mw-mmv-view-expanded.cdx-button {
background: var( --edfm-surface-4 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}

/* ===========================================================================
23. RUNE-WIKI-INSPIRED MOBILE APP SHELL
=========================================================================== */
/* Inspired by RuneScape.wiki's mobile ergonomics -- persistent top app bar,
large touch targets, off-canvas navigation, search-forward layout, and
single-column readable article flow -- while preserving EDFM's dark field
manual identity and not copying RuneScape.wiki assets/CSS.
The close button is injected into #mw-panel by Common.js, so it must be
explicitly hidden by default; otherwise a tiny native white button appears
in the desktop sidebar's top-left corner. */
.edfm-mobile-appbar,
.edfm-mobile-scrim,
.edfm-mobile-close-button {
display: none;
}
@media ( max-width: 800px ) {
html {
-webkit-text-size-adjust: 100%;
}
body {
background: var( --edfm-bg-page );
overflow-x: hidden;
}
body.edfm-mobile-menu-open {
overflow: hidden;
}
.edfm-mobile-appbar {
display: grid;
grid-template-columns: 48px 1fr 48px;
align-items: center;
position: sticky;
top: 0;
z-index: 1200;
min-height: 56px;
padding: 0 0.35rem;
background:
linear-gradient( 90deg, rgba( 255, 138, 0, 0.18 ), transparent 38% ),
var( --edfm-surface-2 );
border-bottom: 1px solid var( --edfm-border );
box-shadow: 0 10px 24px rgba( 0, 0, 0, 0.35 );
}
.edfm-mobile-brand {
min-width: 0;
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
font-weight: 800;
letter-spacing: 0.05em;
text-transform: uppercase;
text-decoration: none;
white-space: nowrap;
overflow: hidden;
text-overflow: ellipsis;
}
.edfm-mobile-brand::before {
content: 'EDFM // ';
color: var( --edfm-orange );
}
.edfm-mobile-menu-button,
.edfm-mobile-search-button,
.edfm-mobile-close-button {
appearance: none;
-webkit-appearance: none;
display: inline-flex;
align-items: center;
justify-content: center;
min-width: 44px;
min-height: 44px;
margin: 0;
border: 0;
border-radius: 0;
background: transparent;
color: var( --edfm-text );
font: 700 1.5rem/1 var( --edfm-mono );
cursor: pointer;
}
.edfm-mobile-menu-button:focus-visible,
.edfm-mobile-search-button:focus-visible,
.edfm-mobile-close-button:focus-visible {
outline: 2px solid var( --edfm-cyan );
outline-offset: -4px;
}
.edfm-mobile-menu-button::before {
content: '☰';
color: var( --edfm-orange );
}
.edfm-mobile-search-button::before {
content: '⌕';
font-size: 1.85rem;
color: var( --edfm-cyan );
}
.edfm-mobile-close-button::before {
content: '×';
color: var( --edfm-text );
}
.edfm-mobile-scrim {
display: block;
position: fixed;
inset: 0;
z-index: 1000;
background: rgba( 0, 0, 0, 0.58 );
opacity: 0;
pointer-events: none;
transition: opacity 0.18s ease;
}
body.edfm-mobile-menu-open .edfm-mobile-scrim {
opacity: 1;
pointer-events: auto;
}
#mw-navigation {
background: var( --edfm-surface-2 );
box-shadow: none;
}
#mw-head {
position: relative;
z-index: 1100;
border-bottom: 1px solid var( --edfm-border );
}
#mw-head .vector-search-box {
display: none;
margin: 0;
padding: 0.65rem;
background: var( --edfm-surface-2 );
border-top: 1px solid var( --edfm-border-soft );
}
body.edfm-mobile-search-open #mw-head .vector-search-box {
display: block;
}
#mw-head .vector-search-box-inner,
#mw-head #searchform {
width: 100%;
}
#mw-head #searchInput {
min-height: 44px;
box-sizing: border-box;
width: 100%;
font-size: 1rem;
}
#left-navigation,
#right-navigation {
padding: 0 0.45rem 0.35rem;
background: var( --edfm-surface-2 );
overflow-x: auto;
white-space: nowrap;
-webkit-overflow-scrolling: touch;
}
.vector-menu-tabs-legacy ul {
flex-wrap: nowrap;
}
.vector-menu-tabs-legacy li a,
.vector-menu-tabs-legacy li a:visited,
.vector-menu-dropdown .vector-menu-heading {
min-height: 36px;
display: inline-flex;
align-items: center;
}
#p-personal {
display: none;
}
#mw-panel {
position: fixed;
top: 0;
left: 0;
z-index: 1300;
width: min( 82vw, 22rem );
height: 100dvh;
box-sizing: border-box;
padding: 0;
background: var( --edfm-surface-1 );
border: 0;
border-right: 1px solid var( --edfm-border );
box-shadow: 18px 0 36px rgba( 0, 0, 0, 0.45 );
overflow-y: auto;
-webkit-overflow-scrolling: touch;
transform: translateX( -105% );
transition: transform 0.2s ease;
}
body.edfm-mobile-menu-open #mw-panel {
transform: translateX( 0 );
}
#mw-panel::before {
content: 'EDFM Navigation';
display: block;
position: sticky;
top: 0;
z-index: 1;
padding: 1rem 3.4rem 1rem 1rem;
background: var( --edfm-surface-2 );
border-bottom: 1px solid var( --edfm-border );
color: var( --edfm-orange );
font: 800 0.86rem/1.2 var( --edfm-mono );
letter-spacing: 0.08em;
text-transform: uppercase;
}
#mw-panel .edfm-mobile-close-button {
position: absolute;
top: 0.3rem;
right: 0.35rem;
z-index: 2;
}
#mw-panel .portal,
#mw-panel .vector-menu-portal {
margin: 0;
padding: 0.75rem 0;
border-bottom: 1px solid var( --edfm-border-soft );
}
#mw-panel .vector-menu-heading {
margin: 0.25rem 1rem 0.45rem;
}
#mw-panel .vector-menu-content-list li a,
#mw-panel .vector-menu-content-list li a:visited {
display: flex;
align-items: center;
min-height: 46px;
box-sizing: border-box;
padding: 0.55rem 1rem;
border-left: 3px solid transparent;
color: var( --edfm-text-muted );
font-size: 1rem;
text-decoration: none;
}
#mw-panel .vector-menu-content-list li a:hover,
#mw-panel .vector-menu-content-list li a:focus {
background: var( --edfm-surface-3 );
border-left-color: var( --edfm-cyan );
color: var( --edfm-text );
}
#mw-panel .edfm-nav-current > a,
#mw-panel .edfm-nav-current > a:visited {
background: rgba( 255, 138, 0, 0.12 );
border-left-color: var( --edfm-orange );
color: var( --edfm-orange ) !important;
}
.mw-body {
padding: clamp( 1rem, 4vw, 1.35rem );
font-size: 1rem;
line-height: 1.68;
}
#siteNotice {
margin-bottom: 1rem;
padding-bottom: 0.85rem;
}
#firstHeading {
font-size: clamp( 1.65rem, 8vw, 2.25rem );
line-height: 1.1;
letter-spacing: -0.015em;
}
.mw-body h2 {
font-size: 1.18rem;
line-height: 1.25;
}
.mw-body p,
.mw-body li {
max-width: none;
}
.mw-body img,
.mw-body .thumb,
.mw-body .thumbinner,
.mw-body .thumbimage {
max-width: 100% !important;
height: auto !important;
box-sizing: border-box;
}
.mw-body .thumb,
.mw-body .tright,
.mw-body .tleft {
float: none !important;
clear: both;
width: auto !important;
margin: 1rem 0 !important;
}
.mw-parser-output > table.wikitable,
.mw-parser-output > table.mw-datatable {
display: block;
width: 100% !important;
max-width: 100%;
overflow-x: auto;
-webkit-overflow-scrolling: touch;
white-space: nowrap;
}
.mw-parser-output > table.wikitable th,
.mw-parser-output > table.wikitable td,
.mw-parser-output > table.mw-datatable th,
.mw-parser-output > table.mw-datatable td {
white-space: normal;
min-width: 8rem;
}
.edfm-infobox {
font-size: 0.95rem;
}
.edfm-infobox-row {
display: grid;
grid-template-columns: minmax( 7.5rem, 40% ) 1fr;
gap: 0.5rem;
padding: 0.65rem 0.8rem;
}
.edfm-infobox-label,
.edfm-infobox-value {
width: auto;
}
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type,
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type tbody,
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type tr,
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type th,
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type td {
display: block;
width: 100% !important;
box-sizing: border-box;
}
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type {
overflow: visible;
white-space: normal;
background: transparent;
border: 0;
}
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type th {
margin-top: 0.75rem;
border-left: 3px solid var( --edfm-orange );
}
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type td {
margin-bottom: 0.75rem;
background: var( --edfm-surface-2 );
border-left: 3px solid var( --edfm-border );
}
.mw-footer {
padding: 1rem;
margin-top: 1.5rem;
}
}
@media ( max-width: 430px ) {
.edfm-mobile-brand::before {
content: 'EDFM';
margin-right: 0.45rem;
}
.edfm-mobile-brand {
font-size: 0.88rem;
}
.edfm-infobox-row {
grid-template-columns: 1fr;
gap: 0.2rem;
}
}

/* 22a. Mobile action tabs refinement: keep Vector's page/discussion/read/
source/history controls available, but put them on one compact horizontal
action rail so the first phone viewport feels like a real mobile app shell
instead of two stacked desktop tab bars. */
@media ( max-width: 800px ) {
body:not( .edfm-mobile-search-open ) #mw-head {
display: flex;
align-items: stretch;
gap: 0;
overflow-x: auto;
overflow-y: hidden;
-webkit-overflow-scrolling: touch;
scrollbar-width: thin;
}
body:not( .edfm-mobile-search-open ) #left-navigation,
body:not( .edfm-mobile-search-open ) #right-navigation {
flex: 0 0 auto;
clear: none !important;
float: none !important;
width: auto;
padding: 0 0.25rem;
margin: 0 !important;
border-right: 1px solid var( --edfm-border-soft );
}
body:not( .edfm-mobile-search-open ) .vector-menu-tabs-legacy,
body:not( .edfm-mobile-search-open ) .vector-menu-dropdown {
float: none !important;
display: inline-block;
}
body:not( .edfm-mobile-search-open ) .vector-menu-tabs-legacy li a,
body:not( .edfm-mobile-search-open ) .vector-menu-tabs-legacy li a:visited,
body:not( .edfm-mobile-search-open ) .vector-menu-dropdown .vector-menu-heading {
min-height: 40px;
padding-left: 0.55rem;
padding-right: 0.55rem;
font-size: 0.68rem;
}
body.edfm-mobile-search-open #mw-head {
display: block;
}
}

/* ===========================================================================
24. HARD OVERRIDE: JUMP TILE LEFT RAIL

The earlier border-left rail can be swallowed by ResourceLoader/cascade or
visually read as part of the tile edge. Draw the rail as a high-specificity
gradient on the actual top-level TOC anchors so it is unmistakable on the
live jump grid.
=========================================================================== */
#toc.toc > ul > li > a,
.mw-parser-output #toc > ul > li > a,
.mw-parser-output .toc > ul > li > a {
background-image: linear-gradient( 90deg, var( --edfm-orange ) 0, var( --edfm-orange ) 6px, transparent 6px ) !important;
border-left: 0 !important;
padding-left: 1rem !important;
}
#toc.toc > ul > li > a:hover,
#toc.toc > ul > li > a:focus-visible,
.mw-parser-output #toc > ul > li > a:hover,
.mw-parser-output #toc > ul > li > a:focus-visible,
.mw-parser-output .toc > ul > li > a:hover,
.mw-parser-output .toc > ul > li > a:focus-visible {
background-image: linear-gradient( 90deg, var( --edfm-cyan ) 0, var( --edfm-cyan ) 6px, transparent 6px ) !important;
}

/* ===========================================================================
25. SOURCE EDIT CONFLICT / WIKITEXT DIFF THEME

Source-edit conflict review uses MediaWiki's diff table classes, not the
normal edit textarea/WikiEditor chrome. Without this, unchanged rows and
inline change pills fall back to stark white/yellow/blue defaults. Keep the
old/new meaning, but render it in EDFM's dark surfaces with restrained
orange/cyan accents.
=========================================================================== */
.mw-parser-output table.diff,
table.diff,
.diff {
background: var( --edfm-bg-deep ) !important;
color: var( --edfm-text ) !important;
border-collapse: separate !important;
border-spacing: 0 0.12rem !important;
}
.diff-title,
.diff-otitle,
.diff-ntitle,
#mw-diff-otitle1,
#mw-diff-ntitle1 {
background: var( --edfm-bg-deep ) !important;
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
}
td.diff-lineno,
.diff-lineno {
background: transparent !important;
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
font-weight: 700;
border: 0 !important;
padding: 0.35rem 0.5rem !important;
}
td.diff-marker,
.diff-marker {
background: transparent !important;
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
font-weight: 700;
padding: 0.25rem 0.45rem !important;
text-align: center;
}
td.diff-context,
td.diff-addedline,
td.diff-deletedline,
.diff-context,
.diff-addedline,
.diff-deletedline,
.mw-diff-inline-context,
.mw-diff-inline-added,
.mw-diff-inline-deleted,
.mw-diff-inline-changed,
.mw-diff-inline-moved {
background: var( --edfm-surface-1 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
font-family: var( --edfm-mono );
box-shadow: none !important;
}
td.diff-context:empty,
td.diff-addedline:empty,
td.diff-deletedline:empty,
.diff-context:empty,
.diff-addedline:empty,
.diff-deletedline:empty {
/* Empty diff cells are alignment placeholders. Keep their card boundary so
the two-column source-conflict diff does not look broken, but make them
compact and neutral instead of tall blank blocks. */
background: var( --edfm-surface-1 ) !important;
border-color: var( --edfm-border ) !important;
box-shadow: none !important;
min-height: 0;
padding-top: 0.08rem !important;
padding-bottom: 0.08rem !important;
}
td.diff-deletedline,
.diff-deletedline,
.mw-diff-inline-deleted {
background: rgba( 255, 138, 0, 0.08 ) !important;
border-color: rgba( 255, 138, 0, 0.6 ) !important;
border-left-color: var( --edfm-orange ) !important;
}
td.diff-addedline,
.diff-addedline,
.mw-diff-inline-added {
background: rgba( 66, 199, 217, 0.08 ) !important;
border-color: rgba( 66, 199, 217, 0.6 ) !important;
border-left-color: var( --edfm-cyan ) !important;
}
.diffchange,
.diff-addedline .diffchange,
.diff-deletedline .diffchange,
.mw-diff-inline-added ins,
.mw-diff-inline-changed ins,
.mw-diff-inline-moved ins,
.mw-diff-inline-deleted del,
.mw-diff-inline-changed del,
.mw-diff-inline-moved del {
border-radius: 3px !important;
padding: 0.08rem 0.22rem !important;
font-weight: 700;
text-decoration: none !important;
color: var( --edfm-bg-deep ) !important;
}
.diff-deletedline .diffchange,
.mw-diff-inline-deleted del,
.mw-diff-inline-changed del,
.mw-diff-inline-moved del {
background: var( --edfm-orange-bright ) !important;
}
.diff-addedline .diffchange,
.mw-diff-inline-added ins,
.mw-diff-inline-changed ins,
.mw-diff-inline-moved ins {
background: var( --edfm-cyan ) !important;
}
.mw-explainconflict,
#wpTextbox2,
textarea#wpTextbox2,
textarea.mw-textarea-oldrev {
background: var( --edfm-surface-1 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}

/* Engineer directory portrait chips -- intentionally quiet so table rows still
read like data rows, not card/list hybrids. */
.edfm-engineer-entry {
display: inline-flex;
align-items: center;
gap: 0.45rem;
min-width: max-content;
}
.edfm-engineer-entry .mw-file-element {
width: 30px;
height: 30px;
object-fit: cover;
border-radius: 3px;
border: 1px solid var( --edfm-border );
background: var( --edfm-surface-0 );
box-shadow: none;
}
.edfm-engineer-entry__name {
line-height: 1.2;
}

/* Frontier official news feed image treatment */
.edfm-frontier-news .edfm-news-card-art-image {
display: block;
position: relative;
padding: 0;
min-height: 9.5rem;
background: var( --edfm-surface-4 );
overflow: hidden;
}
.edfm-frontier-news .edfm-news-card-primary .edfm-news-card-art-image {
min-height: 13.5rem;
}
.edfm-frontier-news .edfm-news-card-art-image > span,
.edfm-frontier-news .edfm-news-card-art-image .mw-default-size,
.edfm-frontier-news .edfm-news-card-art-image .mw-file-description {
display: block !important;
position: absolute;
inset: 0;
width: 100% !important;
height: 100% !important;
max-width: none !important;
margin: 0 !important;
}
.edfm-frontier-news .edfm-news-card-art-image .mw-file-element {
display: block !important;
width: 100% !important;
height: 100% !important;
max-width: none !important;
object-fit: cover;
transition: transform 0.2s ease, filter 0.2s ease;
}
.edfm-frontier-news .edfm-news-card:hover .edfm-news-card-art-image .mw-file-element {
filter: brightness( 1.08 ) contrast( 1.05 );
transform: scale( 1.035 );
}
.edfm-frontier-news .edfm-news-source-badge {
display: inline-flex !important;
align-items: center;
position: absolute !important;
left: 0.8rem !important;
right: auto !important;
bottom: 0.75rem !important;
z-index: 2;
max-width: calc( 100% - 1.6rem );
padding: 0.25rem 0.55rem;
background: rgba( 10, 13, 17, 0.82 );
border: 1px solid rgba( 255, 138, 0, 0.48 );
box-shadow: 0 8px 18px rgba( 0, 0, 0, 0.34 );
color: var( --edfm-text );
font-family: var( --edfm-mono );
font-size: 0.68rem;
font-weight: 800;
letter-spacing: 0.08em;
line-height: 1;
text-transform: uppercase;
white-space: nowrap;
pointer-events: none;
}

.edfm-news-attribution {
margin-top: 0.85rem;
padding-top: 0.75rem;
border-top: 1px solid var( --edfm-border-soft );
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-meta );
line-height: 1.45;
}

MediaWiki:Common.css

2026-08-10T04:19:25Z

EDFM Maintenance: Slightly shrink sidebar Discord invite button

/* ==========================================================================
EDFM site-wide styling -- "Elite Dangerous technical field manual" theme.
Original CSS written for this project -- no code or assets copied from
runescape.wiki, Elite Dangerous, or any other site/game, and no Frontier
logo/branding/proprietary fonts/copied HUD elements. Restrained visual
influence only: dark industrial surfaces, subtle angular geometry,
orange/cyan accents used sparingly, information hierarchy first. This is
a reference site, not a HUD -- no glow, no neon, no glassmorphism, no
constant animation.

SKIN NOTE: the site uses Vector "legacy" (2011), not Vector 2022 -- see
the "Why Vector legacy" note in docs/content-style-guide.md (Vector 2022
hard-restricts its pinned sidebar to logged-in users; legacy has no such
restriction). Several rules below exist specifically to beat core Vector
legacy/mediawiki.skinning selectors that are *more specific* than a naive
override would be (documented inline at each occurrence) -- this isn't
guesswork, each one was found by reading the actual core .less source and
confirmed with a real rendered screenshot, not just computed-style checks
(:visited colours in particular are invisible to getComputedStyle by
design -- see the tab-bar note below).

2026-08-07 SECOND PASS: the first redesign pass was judged too close to
stock MediaWiki with a colour change -- this pass changes the actual
visual composition (centred workspace instead of a huge dead gutter,
a two-tier header, a real masthead, a tile-grid TOC, a restructured
status module, larger deliberate type scale, depth via surface
elevation instead of borders-around-everything) while reusing every
working mechanism from the first pass rather than throwing it away --
the tab/:visited fix, the external-link specificity fix, the mobile
reorder fix, and focus-visible/reduced-motion are all still here,
unchanged in mechanism.
========================================================================== */

/* ==========================================================================
1. DESIGN TOKENS
========================================================================== */
:root {
/* Depth system: site (outermost, visible in the sidebar/header/gutters)
-> article surface -> component surfaces, each a deliberate step
brighter so the page reads as having actual depth rather than "one
background colour with slightly lighter boxes everywhere". */
--edfm-bg-deep: #07090b;
--edfm-bg-page: #0a0e11;
--edfm-surface-1: #10171b;
--edfm-surface-2: #161f24;
--edfm-surface-3: #1c272d;
--edfm-surface-4: #233037;

--edfm-border: #26333b;
--edfm-border-soft: rgba( 255, 255, 255, 0.06 );

--edfm-text: #edf0f2;
--edfm-text-muted: #98a5ad;
--edfm-text-dim: #6c7a82;

/* Accents -- orange is reserved for navigation/selection/emphasis/
section numbering; cyan/blue are for links, verification info, and
secondary interface elements. See "Links" and "Colour system" in
docs/content-style-guide.md for the reasoning. */
--edfm-orange: #ff8a00;
--edfm-orange-bright: #ffa21a;
--edfm-cyan: #42c7d9;
--edfm-blue: #4f9fe8;

/* Derived link colours */
--edfm-link: var( --edfm-blue );
--edfm-link-visited: #3f7bb3;
--edfm-link-hover: #8cc4f7;
--edfm-link-external: var( --edfm-cyan );
--edfm-link-external-visited: #2f8f9c;
--edfm-link-external-hover: #7fe0ec;
--edfm-link-new: #e07a7a;

/* Status semantics (article metadata module) -- text label always
present too, never colour-only. */
--edfm-status-positive: var( --edfm-cyan );
--edfm-status-attention: var( --edfm-orange );
--edfm-status-neutral: var( --edfm-text-dim );
--edfm-status-positive-bg: rgba( 66, 199, 217, 0.12 );
--edfm-status-attention-bg: rgba( 255, 138, 0, 0.12 );
--edfm-status-neutral-bg: rgba( 108, 122, 130, 0.12 );

/* Typography -- explicit desktop scale (2026-08-07 pass 2). Sized in
rem against the root's real 16px (Vector legacy's own
@font-size-root is 100%, i.e. browser default -- confirmed by
reading skins.vector.styles.legacy/variables.less, not assumed)
rather than nested em, specifically so component sizes can't
compound smaller than intended inside whatever ambient size an
ancestor happens to set. */
--edfm-fs-title: clamp( 1.9rem, 1.4rem + 2vw, 2.25rem ); /* ~30-36px */
--edfm-fs-h2: 1.35rem; /* ~21.6px */
--edfm-fs-h3: 1.15rem; /* ~18.4px */
--edfm-fs-body: 1rem; /* 16px */
--edfm-fs-resource-name: 1.1rem; /* ~17.6px */
--edfm-fs-meta: 0.8rem; /* ~12.8px */
--edfm-fs-sidebar: 0.9375rem; /* 15px -- polish pass: +1px for readability */
--edfm-fs-utility: 0.72rem; /* ~11.5px */

--edfm-mono: 'JetBrains Mono', 'Fira Code', Consolas, 'SF Mono', Menlo, 'Courier New', monospace;
--edfm-sans: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Helvetica, Arial, sans-serif;

/* Legacy aliases: earlier revisions of this stylesheet used these names
directly and some inline template output/older docs may still refer
to them; keep pointing at the current tokens rather than duplicate
values that could drift out of sync. */
--edfm-orange-hover: var( --edfm-orange-bright );
--edfm-orange-active: var( --edfm-orange-bright );
--color-progressive: var( --edfm-orange );
--color-progressive--hover: var( --edfm-orange-bright );
--color-progressive--active: var( --edfm-orange-bright );
--color-progressive--focus: var( --edfm-orange );
--background-color-progressive: var( --edfm-orange );
--background-color-progressive--hover: var( --edfm-orange-bright );
--background-color-progressive--active: var( --edfm-orange-bright );
--border-color-progressive: var( --edfm-orange );
--border-color-progressive--hover: var( --edfm-orange-bright );
--border-color-progressive--active: var( --edfm-orange-bright );

/* Geometry / layout */
--edfm-corner: 10px;
/* Polish-pass bump from 1280px -- article read as slightly too narrow
on large desktop displays, and future reference tables (engineering,
ship stats, colonisation data) will want the room. Still centred
within the workspace via --edfm-gutter below, not stretched
edge-to-edge. */
--edfm-content-max: 1320px;
/* RuneScape.wiki-style integrated rail: wide enough for readable labels,
but joined directly to the page plane. Width and clear match so the
article starts beside the sidebar shadow instead of after a dead gutter. */
--edfm-sidebar-width: 12.75rem;
--edfm-sidebar-clear: 12.75rem;
/* The gutter is whatever's left of the workspace (viewport minus the
sidebar) after the capped content width, split evenly, never
negative. On a screen too narrow to fit sidebar+content-max, this
collapses to 0 and content just fills the workspace edge-to-edge --
see "GLOBAL LAYOUT" below for the full explanation. */
--edfm-gutter: max( 0px, calc( ( 100vw - var( --edfm-sidebar-clear ) - var( --edfm-content-max ) ) / 2 ) );
}

/* ==========================================================================
2. BASE / RESET-ADJACENT
========================================================================== */
html, body {
background-color: var( --edfm-bg-page );
color: var( --edfm-text );
}
body.mediawiki {
color: var( --edfm-text );
font-family: var( --edfm-sans );
font-size: var( --edfm-fs-body );
}
/* Background treatment: a faint technical grid plus a very soft radial
glow centred behind the (now centred) content column, so the composition
still has quiet visual interest in the gutters on ultrawide screens
instead of just flat colour -- both stay under ~3% opacity, this is
texture, not a HUD. Not image assets; pure CSS gradients. */
body {
background-image:
radial-gradient( ellipse 1400px 900px at 50% 0%, rgba( 66, 199, 217, 0.05 ), transparent 60% ),
linear-gradient( rgba( 255, 255, 255, 0.025 ) 1px, transparent 1px ),
linear-gradient( 90deg, rgba( 255, 255, 255, 0.025 ) 1px, transparent 1px );
background-size: auto, 48px 48px, 48px 48px;
background-repeat: no-repeat, repeat, repeat;
background-attachment: fixed, scroll, scroll;
}
/* Full-height sidebar rail: mirrors the RuneScape.wiki behavior where the
left rail has no visible bottom edge. The real #mw-panel only carries the
navigation content; this fixed layer paints the uninterrupted surface,
border, and shadow down the whole viewport. */
body::before {
content: '';
position: fixed;
top: 0;
left: 0;
bottom: 0;
width: var( --edfm-sidebar-width );
background: linear-gradient( 180deg, var( --edfm-surface-1 ) 0%, var( --edfm-bg-deep ) 100% );
border-right: 1px solid var( --edfm-border );
box-shadow: 10px 0 22px rgba( 0, 0, 0, 0.32 );
pointer-events: none;
z-index: 1;
}
@media ( prefers-reduced-motion: reduce ) {
*, *::before, *::after {
animation-duration: 0.001ms !important;
animation-iteration-count: 1 !important;
transition-duration: 0.001ms !important;
scroll-behavior: auto !important;
}
}
/* Focus visibility: applies to every interactive element, not just links. */
a:focus-visible,
button:focus-visible,
input:focus-visible,
textarea:focus-visible,
select:focus-visible,
[tabindex]:focus-visible {
outline: 2px solid var( --edfm-cyan );
outline-offset: 2px;
}

/* Small reusable angular motif: a corner-cut bracket, used sparingly (see
the redesign notes in docs/content-style-guide.md for exactly where) --
deliberately not applied everywhere. */
.edfm-corner-cut {
clip-path: polygon( 0 0, calc( 100% - var( --edfm-corner ) ) 0, 100% var( --edfm-corner ), 100% 100%, 0 100% );
}

/* ==========================================================================
3. TYPOGRAPHY
========================================================================== */
h1, h2, h3, h4, h5, h6 {
color: var( --edfm-text );
border-color: var( --edfm-border );
}
/* !important justified here: MediaWiki core's mediawiki.skinning module
sets heading colour with equal-specificity plain-tag selectors and kept
winning in testing despite this stylesheet loading later -- rather than
keep chasing exact cascade/bundling order, force it. This is a
correctness/contrast fix, not decoration. */
.mw-body h1, .mw-body h2, .mw-body h3, .mw-body h4, .mw-body h5, .mw-body h6,
.mw-heading1, .mw-heading2, .mw-heading3, .mw-heading4, .mw-heading5, .mw-heading6,
h1, h2, h3, h4, h5, h6 {
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
font-family: var( --edfm-mono );
letter-spacing: 0.01em;
line-height: 1.3;
}
#firstHeading {
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-title );
font-weight: 700;
margin-top: 0.15em;
}
/* Section headings (h2): "// " prefix in orange, bright heading text, a
short orange accent segment over the dim full-width divider core
already draws. Substantially more vertical space than a wiki section
normally gets, per the "sections feel packed together" fix -- 3.25rem
(~52px) above, ~1.1rem gap to the first content component below. If a
heading opts into explicit numbering via {{Section number}}, the
automatic "// " is suppressed so the two treatments don't double up. */
.mw-body h2 {
position: relative;
padding-bottom: 0.4em;
margin-top: 3.25rem;
margin-bottom: 1.1rem;
font-size: var( --edfm-fs-h2 );
}
.mw-body h2::before {
content: '// ';
color: var( --edfm-orange );
font-weight: 400;
}
.mw-body h2:has( .edfm-section-number )::before {
content: none;
}
.mw-body h2::after {
content: '';
position: absolute;
left: 0;
bottom: -1px;
width: 3em;
max-width: 100%;
height: 2px;
background: var( --edfm-orange );
}
.edfm-section-number {
color: var( --edfm-orange );
font-weight: 700;
}
.edfm-section-sep {
color: var( --edfm-orange );
margin-right: 0.15em;
}
h3, h4 {
color: var( --edfm-text );
font-size: var( --edfm-fs-h3 );
}
h3::before {
content: '/ ';
color: var( --edfm-text-dim );
font-weight: 400;
}

/* Body text: readable sans-serif, deliberately NOT monospace -- long-form
reading in monospace hurts readability, which stays a hard requirement
even with a more technical visual language elsewhere. */
.mw-body p,
.mw-body li,
.mw-body dd {
line-height: 1.7;
font-size: var( --edfm-fs-body );
}
.mw-body p {
margin: 0 0 1.1em 0;
max-width: 46em; /* comfortable reading measure, not the full column */
}
.mw-body ul,
.mw-body ol {
line-height: 1.7;
margin-bottom: 1.1em;
}
/* MW 1.46 wraps headings in a `.mw-heading2`/`.mw-heading3` div, so the
sibling that immediately follows is that wrapper, not the `h2`/`h3`
itself -- matching both forms since a page could still have a bare
heading in edge cases (e.g. content generated without the wrapper). */
.mw-heading2 + p, .mw-body h2 + p,
.mw-heading3 + p, .mw-body h3 + p,
.mw-heading2 + div, .mw-body h2 + div,
.mw-heading3 + div, .mw-body h3 + div {
margin-top: 0;
}
hr {
background-color: var( --edfm-border );
border-color: var( --edfm-border );
}

/* Quiet, discoverable section-edit controls (logged-in editors only --
MediaWiki only renders these for users who can edit). Keeping the
functionality/keyboard access intact while making sure they don't
compete visually with the heading they're attached to: low opacity at
rest, full opacity on hover/focus of the heading OR the control itself,
brackets hidden (the opacity+letter-spacing treatment already reads as
a distinct control without them). */
.mw-editsection {
margin-left: 1em;
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-utility ) !important;
font-weight: 700;
letter-spacing: 0.05em;
text-transform: uppercase;
opacity: 0.45;
transition: opacity 0.15s ease;
}
.mw-heading:hover .mw-editsection,
.mw-heading:focus-within .mw-editsection,
.mw-editsection:hover,
.mw-editsection:focus-within {
opacity: 1;
}
.mw-editsection a {
color: var( --edfm-text-dim );
}
.mw-editsection a:hover,
.mw-editsection a:focus-visible {
color: var( --edfm-cyan );
}
.mw-editsection-bracket {
display: none;
}
.mw-editsection-divider {
color: var( --edfm-text-dim );
margin: 0 0.3em;
}

/* ==========================================================================
8. LINKS
========================================================================== */
a { color: var( --edfm-link ); transition: color 0.1s ease; }
a:visited { color: var( --edfm-link-visited ); }
a:hover { color: var( --edfm-link-hover ); }
a.new, .new a { color: var( --edfm-link-new ); }
a.external { color: var( --edfm-link-external ); }
/* Core MediaWiki ships `.mw-parser-output a.external`/`a.extiw` (and their
:visited/:hover states) at higher specificity (two classes + a tag) than
a plain `a.external` rule (one class + a tag), so the line above never
actually wins for real article links on its own -- the same underlying
"core selector outranks a naive theme override" gotcha as the tab
:visited fix further down. Matching the same selector shape here (this
stylesheet loads after core skin styles) is what actually applies our
colour to external links in article content. */
.mw-parser-output a.external,
.mw-parser-output a.extiw {
color: var( --edfm-link-external );
}
.mw-parser-output a.external:visited,
.mw-parser-output a.extiw:visited {
color: var( --edfm-link-external-visited );
}
.mw-parser-output a.external:hover,
.mw-parser-output a.extiw:hover {
color: var( --edfm-link-external-hover );
}
.mw-footer a {
color: var( --edfm-link );
}
.mw-footer a:hover {
color: var( --edfm-link-hover );
}

/* ==========================================================================
1. GLOBAL LAYOUT -- centred workspace
========================================================================== */
/* THE fix for "enormous unused region on the right side of wide displays".
Vector legacy's core layout (skins.vector.styles.legacy/layouts/
screen.less) gives `.mw-body` (#content) a left margin to clear the
fixed-width sidebar and otherwise lets it run edge-to-edge to the
browser's right side with no max-width at all -- the first redesign
pass added a max-width but left the column pinned to the sidebar's left
edge, which is *why* it still read as "a column stuck on the left with
dead space on the right" rather than a composed layout.

Fix: instead of a fixed `margin-left: 11em`, compute how much space is
left over in the workspace (viewport minus the sidebar) once the
content has its max-width, and split that leftover evenly between the
left and right margins (via the --edfm-gutter token above) -- so the
article is centred *within the workspace to the right of the sidebar*,
not centred in the full viewport (which would ignore the sidebar and
look off-centre) and not pinned to its left edge either. On a screen
too narrow for sidebar + max-width content, --edfm-gutter naturally
evaluates to 0 and this degrades to the old "fill the workspace"
behaviour -- no separate narrow-screen override needed.

The header/tab bar's own float/absolute-position box (#mw-head) is left
at its native full width deliberately -- rewriting *that* mechanism is
a different, much higher-risk change (it took several rounds to get
right originally) -- but its *contents* (search box, personal tools,
namespace/view tabs) get their own right/left offsets pulled in by the
same --edfm-gutter below, so they still visually line up with the
centred column beneath them instead of hugging the browser edge. */
.mw-body,
#mw-data-after-content,
.mw-footer {
position: relative;
z-index: 2;
margin-left: var( --edfm-sidebar-clear );
margin-right: var( --edfm-gutter );
max-width: var( --edfm-content-max );
box-sizing: border-box;
}
/* Tables, code blocks, and preformatted content are still allowed to be
wider than a comfortable reading measure (technical data often needs
it) -- they scroll horizontally inside the capped column instead of
being force-shrunk or breaking the layout. Ordinary images/galleries
already respect the column via max-width:100% below. */
.mw-body table,
.mw-body pre,
.mw-body .mw-code {
max-width: 100%;
overflow-x: auto;
}
.mw-body table.wikitable,
.mw-body table.mw-datatable {
/* Keep real table layout so header cells and body cells share one column grid.
The earlier display:block + tbody display:table overflow hack made sortable
headers size independently from body columns, which visibly misaligned the
Engineer directory after portrait chips were added. */
display: table;
width: 100%;
table-layout: auto;
}
.mw-body table.wikitable th,
.mw-body table.wikitable td,
.mw-body table.mw-datatable th,
.mw-body table.mw-datatable td {
vertical-align: middle;
}
.mw-body img {
max-width: 100%;
height: auto;
}

/* ==========================================================================
4. ARTICLE MASTHEAD (eyebrow / title / deck)
========================================================================== */
/* Eyebrow line is authored as ordinary wikitext (see Template:Article
header) and, purely as a placement detail, a small script
(MediaWiki:Common.js) moves it directly above #firstHeading on load --
see the comment there for why that needs JS rather than CSS/a template
(the title is rendered by the skin before the article body in the DOM,
so nothing living inside the article body can appear earlier than it
without either moving it in the DOM or abandoning the real semantic H1).
If JS is unavailable the eyebrow still renders, just directly under the
title instead of above it.

The eyebrow/title/deck aren't wrapped in one literal bounding box (they
live at two different DOM depths -- eyebrow is a sibling of #firstHeading,
deck is inside the article body further down -- wrapping them in one
real container would need heavier JS than is justified here), so the
"designed masthead" read comes from a matching top rule above the
eyebrow and bottom rule below the deck, a small angular marker, and the
larger title/subtitle type scale, rather than one drawn box. */
.edfm-eyebrow {
display: flex;
align-items: center;
gap: 0.55em;
margin: 0 0 0.5em 0;
padding-top: 1.1em;
border-top: 1px solid var( --edfm-border );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-meta );
font-weight: 700;
letter-spacing: 0.12em;
text-transform: uppercase;
color: var( --edfm-text-dim );
}
.edfm-eyebrow::before {
content: '';
width: 8px;
height: 8px;
flex-shrink: 0;
background: var( --edfm-orange );
clip-path: polygon( 0 0, 100% 0, 100% 65%, 65% 100%, 0 100% );
}
.edfm-eyebrow .edfm-orange-mark {
color: var( --edfm-orange );
}
.edfm-deck {
color: var( --edfm-text-muted );
font-size: 1.1rem;
line-height: 1.55;
max-width: 42em;
margin: 0.5em 0 1.7em 0;
padding-bottom: 1.6em;
border-bottom: 1px solid var( --edfm-border );
}

/* ==========================================================================
1. SIDEBAR
========================================================================== */
#mw-panel {
background: transparent;
box-sizing: border-box;
width: var( --edfm-sidebar-width );
padding: 0 0.65rem 1.35rem 0.65rem;
border-right: 0;
box-shadow: none;
z-index: 3;
}
/* Logo anchors the sidebar visually. Do not draw a divider on or near
#p-logo: Vector legacy fixes the logo box at 155px high and the EDFM hex
mark reaches that edge, so any horizontal rule in this box cuts through
the lower point of the logo. Navigation spacing below provides the break. */
#p-logo {
box-sizing: border-box;
width: auto;
margin: 0 -0.65rem 1.25rem -0.65rem;
padding: 0.95rem 0.55rem 1.05rem 0.55rem;
border-bottom: 0 !important;
background: radial-gradient( circle at 50% 25%, rgba( 255, 138, 0, 0.08 ), transparent 58% );
}
/* Each nav group gets real breathing room from the one before it instead
of being packed together like a stock wiki sidebar. */

/* Sidebar Discord invite CTA: injected by MediaWiki:Common.js directly below
the logo and above the first generated Vector portlet, matching the compact
community-button placement shown in the reference screenshot. */
.edfm-discord-cta {
display: inline-flex;
align-items: center;
justify-content: center;
gap: 0.42rem;
box-sizing: border-box;
width: calc( 100% - 1.35rem );
min-height: 1.78rem;
margin: -0.35rem 0.675rem 1.05rem 0.675rem;
padding: 0.36rem 0.56rem;
border-radius: 4px;
background: #5865f2;
color: #fff !important;
font-size: 0.76rem;
font-weight: 700;
line-height: 1.1;
text-align: center;
text-decoration: none !important;
box-shadow: 0 2px 5px rgba( 0, 0, 0, 0.35 );
transition: background-color 120ms ease, box-shadow 120ms ease, transform 120ms ease;
}
.edfm-discord-cta:hover,
.edfm-discord-cta:focus {
background: #4752c4;
color: #fff !important;
text-decoration: none !important;
box-shadow: 0 3px 8px rgba( 0, 0, 0, 0.42 );
transform: translateY( -1px );
}
.edfm-discord-cta-icon {
display: inline-flex;
width: 1rem;
height: 1rem;
flex: 0 0 auto;
}
.edfm-discord-cta-icon svg {
display: block;
width: 100%;
height: 100%;
fill: currentColor;
}

#mw-panel .portal,
#mw-panel .vector-menu-portal {
box-sizing: border-box;
width: auto;
max-width: none;
margin-top: 1.45rem;
}
#mw-panel .portal:first-of-type,
#mw-panel .vector-menu-portal:first-of-type {
margin-top: 0;
}
#mw-panel .portal .body,
#mw-panel .portal ul,
#mw-panel .vector-menu-content,
#mw-panel .vector-menu-content-list {
box-sizing: border-box;
width: auto;
max-width: none;
margin-left: 0;
margin-right: 0;
padding-left: 0;
border-color: var( --edfm-border-soft );
}
#mw-panel .portal a {
color: var( --edfm-text-muted );
display: block;
font-size: var( --edfm-fs-sidebar );
line-height: 1.35;
padding: 0.42em 0.55em;
margin: 0.08em -0.35em;
border-left: 2px solid transparent;
border-radius: 2px;
}
#mw-panel .portal a:hover {
color: var( --edfm-cyan );
background: var( --edfm-surface-1 );
}
/* "You are here" -- MediaWiki's sidebar has no built-in current-page
indication; MediaWiki:Common.js adds the .edfm-nav-current class to the
matching list item by comparing hrefs to the current URL. Orange is
reserved for exactly this kind of "important navigation / selected
state" per the colour system, which is why the rest of the sidebar is
deliberately muted rather than orange throughout (an all-orange sidebar
would both fight this indicator and read as visually dominant). */
.edfm-nav-current > a {
color: var( --edfm-orange ) !important;
font-weight: 700;
border-left-color: var( --edfm-orange );
border-left-width: 3px;
background: var( --edfm-surface-2 );
box-shadow: inset 0 0 0 1px rgba( 255, 138, 0, 0.08 );
}
.vector-menu-heading {
color: var( --edfm-text-dim );
font-weight: 700;
font-family: var( --edfm-mono );
letter-spacing: 0.08em;
text-transform: uppercase;
font-size: var( --edfm-fs-utility );
border-left: 2px solid var( --edfm-orange );
padding-left: 0.5em;
margin-left: -0.5em;
margin-bottom: 0.4em;
}

/* ==========================================================================
3. TOP BAR -- two-tier chrome
========================================================================== */
/* Vector legacy's #mw-head naturally has ~2.5em of empty space above the
tabs row (core: `#left-navigation/#right-navigation { margin-top:2.5em }`),
originally reserved just for #p-personal to float in. Painting that same
box with a background gradient that stays transparent for that top
band and then switches to a surface colour for the tabs band creates a
real two-tier read -- "primary chrome" (personal tools/search, over the
page's own background) above "wiki authoring controls" (the tabs, on
their own distinct strip) below -- without touching #mw-head's own
position/width mechanics, which is the same fragile absolute-position
system the very first pass of this project had to debug carefully to
get the persistent sidebar working at all. Not worth re-risking that
for a background change. */
#mw-head {
background-image: linear-gradient(
to bottom,
transparent 0,
transparent 2.35em,
var( --edfm-surface-2 ) 2.35em,
var( --edfm-surface-2 ) 100%
);
border-bottom: 1px solid var( --edfm-border );
}
#mw-page-base {
background-color: var( --edfm-bg-deep );
background-image: none;
}
#mw-head-base {
background-color: var( --edfm-bg-deep );
/* Polish pass: thinned from 2px -- at 2px this competed visually with
the masthead's own orange marker/rule directly below it; a single
thinner accent line still reads as "site identity colour" without
the repetition. */
border-bottom: 1px solid var( --edfm-orange );
}
/* Personal tools (login/logout) and the search box are the "primary
chrome" tier -- pulled in by the same gutter used to centre the article,
so on wide screens they visually line up with the centred column
instead of hugging the browser edge, and given noticeably more visual
weight than the tabs below them. */
#p-personal {
right: calc( 0.75em + var( --edfm-gutter ) );
display: flex;
align-items: center;
gap: 0.75rem;
}
#p-personal ul {
display: flex;
align-items: center;
gap: 0.55rem;
}
#p-personal li {
margin-left: 0;
}
#p-personal a {
color: var( --edfm-text-muted );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-sidebar );
padding: 0.3em 0.2em;
}
#p-personal a:hover {
color: var( --edfm-orange );
}
.edfm-topbar-clocks {
display: inline-flex;
align-items: center;
gap: 0.5rem;
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-sidebar );
line-height: 1;
white-space: nowrap;
}
.edfm-topbar-clock {
display: inline-flex;
align-items: center;
gap: 0.3em;
padding: 0.3em 0.55em;
background: rgba( 66, 199, 217, 0.08 );
border: 1px solid var( --edfm-border-soft );
border-left: 2px solid var( --edfm-cyan );
color: var( --edfm-text );
}
.edfm-topbar-clock-label {
color: var( --edfm-text-dim );
font-size: var( --edfm-fs-utility );
letter-spacing: 0.08em;
text-transform: uppercase;
}
.edfm-topbar-clock time {
color: var( --edfm-cyan );
font-weight: 700;
}
.edfm-topbar-clock-local {
background: rgba( 255, 138, 0, 0.06 );
border-left-color: var( --edfm-orange );
}
.edfm-topbar-clock-local time {
color: var( --edfm-orange-bright );
}
#right-navigation {
margin-right: var( --edfm-gutter );
}
#left-navigation {
margin-left: var( --edfm-sidebar-clear );
}
/* Polish pass: core caps this at `width:20vw; max-width:20em`, which read
as cramped next to the rest of the (now larger-scale) interface --
given more room on desktop, still capped so it can't dominate the bar. */
.vector-search-box-inner {
width: 22vw;
max-width: 24em;
}
.vector-search-box-inner input,
#searchInput {
background-color: var( --edfm-surface-3 );
color: var( --edfm-text );
border: 1px solid var( --edfm-border );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-sidebar );
padding: 0.5em 0.7em;
transition: border-color 0.15s ease, box-shadow 0.15s ease;
}
#searchInput:focus {
border-color: var( --edfm-cyan );
box-shadow: 0 0 0 2px rgba( 66, 199, 217, 0.22 );
outline: none;
}
#searchInput::placeholder {
color: var( --edfm-text-dim );
}
/* Namespace tabs (Main Page / Discussion, left) and view tabs
(Read / Edit / View history, right) both use Vector legacy's
.vector-menu-tabs-legacy markup. Core skin CSS paints every tab `li`
with a gradient fading to white and forces the selected tab to pure
white -- neither is touched by recolouring the link text alone, which is
why these stayed light before this stylesheet covered the `li`
background too. Core also has an `a:visited` rule (higher specificity
than a plain `a` rule, since a pseudo-class counts the same as a class)
that reasserts a near-black "visited" colour meant for a white
background; since these tabs point at pages you've almost always
already visited, without an explicit `:visited` override here the text
goes dark-on-dark. This can't be caught by reading getComputedStyle() in
an automated check -- browsers deliberately report the *unvisited*
colour to JS for privacy reasons, so it only shows up on an actual
screen; verified with real rendered screenshots, including after
genuinely visiting the linked pages first.

These are the "wiki authoring controls" utility tier -- deliberately
smaller (--edfm-fs-utility) and quieter than personal-tools/search
above them, sitting on their own background strip (see #mw-head above).
Selected state stays orange (it's still real navigation, just
secondary); unselected rests dim so the *selected* tab is the one that
reads clearly. */
.vector-menu-tabs-legacy li {
background-image: none;
background-color: transparent;
}
.vector-menu-tabs-legacy li.selected {
background-image: none;
background-color: var( --edfm-surface-1 );
/* Polish pass: a small underline makes the selected tab unambiguous at
a glance instead of relying on the text colour change alone. */
box-shadow: inset 0 -2px 0 var( --edfm-orange );
}
.vector-menu-tabs-legacy li a,
.vector-menu-tabs-legacy li a:visited {
background-color: transparent;
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-utility );
letter-spacing: 0.03em;
text-transform: uppercase;
font-weight: 700;
}
.vector-menu-tabs-legacy li a:hover,
.vector-menu-tabs-legacy li a:visited:hover {
color: var( --edfm-text );
}
.vector-menu-tabs-legacy li.selected a,
.vector-menu-tabs-legacy li.selected a:visited {
color: var( --edfm-orange );
}
.vector-menu-tabs-legacy li.new a,
.vector-menu-tabs-legacy li.new a:visited {
color: var( --edfm-link-new );
}
/* "More" actions dropdown (#p-cactions) sits in the same tab row; same
:visited gotcha applies to its menu items. */
.vector-menu-dropdown .vector-menu-heading {
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
border-left: none;
padding-left: 8px;
margin-left: 0;
margin-bottom: 0;
text-transform: uppercase;
letter-spacing: 0.03em;
font-size: var( --edfm-fs-utility );
font-weight: 700;
}
.vector-menu-dropdown .vector-menu-heading:hover,
.vector-menu-dropdown .vector-menu-heading:focus {
color: var( --edfm-orange );
}
.vector-menu-dropdown .vector-menu-content {
background-color: var( --edfm-surface-3 );
border-color: var( --edfm-border );
}
.vector-menu-dropdown .vector-menu-content a,
.vector-menu-dropdown .vector-menu-content a:visited {
color: var( --edfm-text-muted );
font-size: var( --edfm-fs-sidebar );
}
.vector-menu-dropdown .vector-menu-content li.selected a,
.vector-menu-dropdown .vector-menu-content li.selected a:visited {
color: var( --edfm-orange );
}
.vector-menu-dropdown .vector-menu-content li:hover {
background-color: var( --edfm-surface-4 );
}

/* ==========================================================================
CONTENT / ARTICLE SURFACE
========================================================================== */
.mw-body,
.parsoid-body {
background-color: var( --edfm-surface-1 );
color: var( --edfm-text );
border-color: var( --edfm-border );
font-family: var( --edfm-sans );
}
.mw-body {
border-right: 1px solid var( --edfm-border );
}
#content {
background-color: var( --edfm-surface-1 );
}

/* Site notice chrome. The global disclaimer was moved to its dedicated
legal/disclaimer page, so an empty #siteNotice must not leave behind a
phantom divider at the top of the article surface. */
#siteNotice:empty {
display: none;
}
#siteNotice:not( :empty ) {
font-size: var( --edfm-fs-meta );
line-height: 1.5;
color: var( --edfm-text-dim );
font-style: normal;
padding-bottom: 0.7em;
margin-bottom: 1.4rem;
border-bottom: 1px solid var( --edfm-border-soft );
}
#siteNotice:not( :empty ) em, #siteNotice:not( :empty ) i {
color: var( --edfm-text-muted );
font-style: italic;
}
#siteNotice:not( :empty ) a {
color: var( --edfm-link-external );
}
#siteNotice a:hover {
color: var( --edfm-link-external-hover );
}

/* ==========================================================================
HOME PAGE DASHBOARD
========================================================================== */
.edfm-home-hero {
margin: 0.9rem 0 1.6rem;
padding: 1.35rem 1.55rem;
background:
linear-gradient( 135deg, rgba( 255, 138, 0, 0.16 ), transparent 34% ),
linear-gradient( 315deg, rgba( 66, 199, 217, 0.14 ), transparent 42% ),
var( --edfm-surface-2 );
border: 1px solid var( --edfm-border );
border-left: 4px solid var( --edfm-cyan );
clip-path: polygon( 0 0, calc( 100% - 12px ) 0, 100% 12px, 100% 100%, 0 100% );
}
.edfm-home-hero-kicker,
.edfm-home-card-kicker {
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-meta );
font-weight: 800;
letter-spacing: 0.1em;
text-transform: uppercase;
}
.edfm-home-hero-title {
margin-top: 0.25rem;
color: var( --edfm-text );
font-family: var( --edfm-mono );
font-size: clamp( 1.55rem, 1.1rem + 1.5vw, 2.2rem );
font-weight: 800;
line-height: 1.15;
}
.edfm-home-hero-text {
max-width: 52rem;
margin-top: 0.55rem;
color: var( --edfm-text-muted );
font-size: 1.05rem;
line-height: 1.55;
}
.edfm-home-grid {
display: grid;
gap: 1rem;
margin: 1.2rem 0 2rem;
}
.edfm-home-grid-four {
grid-template-columns: repeat( 4, minmax( 0, 1fr ) );
}
.edfm-home-grid-topics {
grid-template-columns: repeat( 2, minmax( 0, 1fr ) );
}
.edfm-home-grid-two {
grid-template-columns: repeat( 2, minmax( 0, 1fr ) );
}
.edfm-home-card {
background: var( --edfm-surface-2 );
border: 1px solid var( --edfm-border );
border-left: 3px solid var( --edfm-cyan );
padding: 1rem 1.1rem;
box-shadow: 0 12px 24px rgba( 0, 0, 0, 0.2 );
transition: transform 0.15s ease, border-color 0.15s ease, background-color 0.15s ease;
}
.edfm-home-card:hover {
transform: translateY( -2px );
background: var( --edfm-surface-3 );
border-left-color: var( --edfm-orange );
}
.edfm-home-card-primary {
border-left-color: var( --edfm-orange );
}
.edfm-home-card-warning {
border-left-color: var( --edfm-text-dim );
}
.edfm-home-card-title,
.edfm-home-card-title a {
margin-top: 0.35rem;
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
font-size: 1.05rem;
font-weight: 800;
line-height: 1.3;
text-decoration: none;
}
.edfm-home-card-title a:hover {
color: var( --edfm-orange-bright ) !important;
}
.edfm-home-card-text,
.edfm-home-link-list {
margin-top: 0.65rem;
color: var( --edfm-text-muted );
line-height: 1.6;
}
.edfm-home-link-list a {
font-weight: 600;
}
@media ( max-width: 1100px ) {
.edfm-home-grid-four {
grid-template-columns: repeat( 2, minmax( 0, 1fr ) );
}
}
@media ( max-width: 760px ) {
.edfm-home-grid-four,
.edfm-home-grid-topics,
.edfm-home-grid-two {
grid-template-columns: 1fr;
}
}

/* ==========================================================================
HOME PAGE NEWS MODULE
========================================================================== */
.edfm-home-news {
margin: 1.8rem 0 2.2rem;
}
.edfm-news-feature-grid {
display: grid;
grid-template-columns: repeat( 3, minmax( 0, 1fr ) );
gap: 1rem;
margin-bottom: 1rem;
}
.edfm-news-card,
.edfm-news-list {
background: var( --edfm-surface-2 );
border: 1px solid var( --edfm-border );
box-shadow: 0 14px 26px rgba( 0, 0, 0, 0.22 );
overflow: hidden;
}
.edfm-news-card {
display: flex;
flex-direction: column;
min-height: 100%;
transition: transform 0.15s ease, border-color 0.15s ease, background-color 0.15s ease;
}
.edfm-news-card:hover {
transform: translateY( -2px );
border-color: rgba( 255, 138, 0, 0.48 );
background: var( --edfm-surface-3 );
}
.edfm-news-card-art {
display: flex;
align-items: flex-end;
min-height: 7rem;
padding: 0.8rem 1rem;
box-sizing: border-box;
background:
linear-gradient( 135deg, rgba( 255, 138, 0, 0.28 ), transparent 42% ),
linear-gradient( 315deg, rgba( 66, 199, 217, 0.2 ), transparent 48% ),
linear-gradient( 180deg, var( --edfm-surface-4 ), var( --edfm-surface-1 ) );
border-bottom: 1px solid var( --edfm-border );
color: rgba( 237, 240, 242, 0.72 );
font-family: var( --edfm-mono );
font-size: 0.8rem;
font-weight: 800;
letter-spacing: 0.16em;
text-transform: uppercase;
}
.edfm-news-card-primary .edfm-news-card-art {
background:
linear-gradient( 135deg, rgba( 255, 138, 0, 0.38 ), transparent 46% ),
linear-gradient( 315deg, rgba( 79, 159, 232, 0.26 ), transparent 52% ),
var( --edfm-surface-4 );
}
.edfm-news-card-body {
padding: 1rem 1.15rem 1.15rem;
}
.edfm-news-meta {
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-meta );
letter-spacing: 0.04em;
text-transform: uppercase;
margin-bottom: 0.35rem;
}
.edfm-news-title,
.edfm-news-title a {
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
font-size: 1.1rem;
font-weight: 800;
line-height: 1.25;
text-decoration: none;
}
.edfm-news-title a:hover {
color: var( --edfm-orange-bright ) !important;
}
.edfm-news-summary {
color: var( --edfm-text-muted );
line-height: 1.55;
margin-top: 0.65rem;
}
.edfm-news-list {
padding: 1.1rem 1.25rem 1.2rem;
border-left: 4px solid var( --edfm-orange );
}
.edfm-news-list-heading {
color: var( --edfm-text );
font-family: var( --edfm-mono );
font-size: 1.05rem;
font-weight: 800;
letter-spacing: 0.04em;
text-transform: uppercase;
margin-bottom: 0.75rem;
}
.edfm-news-list ul {
margin: 0;
}
.edfm-news-list li {
margin-bottom: 0.55rem;
color: var( --edfm-text-muted );
}
.edfm-news-more {
margin-top: 0.9rem;
padding-top: 0.85rem;
border-top: 1px solid var( --edfm-border-soft );
text-align: right;
font-family: var( --edfm-mono );
font-weight: 800;
letter-spacing: 0.03em;
text-transform: uppercase;
}
@media ( max-width: 900px ) {
.edfm-news-feature-grid {
grid-template-columns: 1fr;
}
}

/* ==========================================================================
10. JUMP NAVIGATION (table of contents)
========================================================================== */
/* A compact navigation strip/tile-grid rather than a traditional TOC box
of small text links -- real MediaWiki anchors/markup untouched, this is
all presentation. "Contents" is kept in the DOM for screen readers/
no-JS/no-CSS fallback (more standard wording there anyway) and visually
replaced with "Jump to" via ::before on the wrapper, with the real
heading text hidden via font-size rather than display:none so it
remains in the accessibility tree. */
#toc, .toc {
display: block;
width: 100%;
box-sizing: border-box;
background: none;
border: none;
color: var( --edfm-text );
padding: 0;
margin: 1.8rem 0;
}
.toctitle {
position: relative;
margin-bottom: 0.7em;
}
.toctitle::before {
content: 'Jump to';
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-meta );
font-weight: 700;
letter-spacing: 0.12em;
text-transform: uppercase;
color: var( --edfm-orange );
}
/* Core ships `.toc h2 { font-size: 100%; ... }` (mediawiki.skinning/toc/
screen.less) at the exact same specificity (one class + one tag) as a
plain `.toctitle h2` rule -- same "tie that doesn't resolve the way
naive source order would suggest" gotcha documented elsewhere in this
file. #toc's own ID makes this one unambiguous instead of relying on
cascade order. */
#toc .toctitle h2,
.toc .toctitle h2 {
font-size: 0 !important;
line-height: 0;
margin: 0;
border: none;
padding: 0;
display: inline;
}
.toctitle h2::before,
.toctitle h2::after {
content: none;
}
.toctogglelabel::before {
color: var( --edfm-text-dim );
}
/* Desktop: a real grid of clickable tiles (3 columns suits this site's
typical 5-8 top-level sections well: commonly 2-3 rows) instead of one
long line of small text. Each tile has its own surface, a visible
boundary via the accent rail (not a full border -- see "stop using a
border around everything"), and an obvious hover state. */
.toc > ul {
display: grid;
grid-template-columns: repeat( 4, 1fr );
gap: 0.45rem;
list-style: none;
margin: 0;
padding: 0;
}
.toc li {
margin: 0;
}
/* 2026-08-08 density pass: reverted to side-by-side number/label (from the
earlier "stacked number-above-label" polish pass) specifically to cut
per-tile height -- with 12 sections on articles like The Dweller, the
stacked layout meant the jump nav alone filled most of the first
viewport. Row layout plus tighter padding/font-size gets noticeably
more sections above the fold without dropping the numbering or shrinking
tap targets below a comfortable size -- see the dedicated mobile padding
bump further down for keeping touch targets safe on small screens
specifically. Whole tile stays one real <a>, so it's still a single
click/focus target and keyboard tab stop either way. */
.toc a {
display: flex;
flex-direction: row;
align-items: center;
gap: 0.5em;
height: 100%;
box-sizing: border-box;
padding: 0.5em 0.75em 0.5em 0.7em;
background: var( --edfm-surface-3 );
/* Left accent rail: matches the orange section numbers and gives each
jump tile a stronger EDFM navigation affordance without boxing the
entire card. */
border-left: 4px solid var( --edfm-orange );
box-shadow: inset 1px 0 0 rgba( 255, 162, 26, 0.35 );
color: var( --edfm-text-muted );
text-decoration: none;
transition: background-color 0.15s ease, border-color 0.15s ease, box-shadow 0.15s ease, color 0.15s ease, transform 0.15s ease;
}
.toc a:hover {
background: var( --edfm-surface-4 );
border-left-color: var( --edfm-cyan );
box-shadow: inset 1px 0 0 rgba( 66, 199, 217, 0.45 );
color: var( --edfm-text );
transform: translateY( -1px );
}
/* Nested sub-levels (rare on this site so far) drop back to a plain
indented block list inside their parent tile's grid cell rather than
trying to stay gridded themselves. */
.toc ul ul {
grid-column: unset;
list-style: none;
margin: 0.3em 0 0 1.2em;
padding: 0;
display: block;
}
.toc ul ul a {
flex-direction: row;
align-items: center;
background: none;
border-left-width: 1px;
padding: 0.3em 0.6em;
}
.toc ul ul .tocnumber {
font-size: 0.85em;
}
.toc ul ul .toctext {
font-size: 0.85em;
}
.tocnumber {
color: var( --edfm-orange );
font-family: var( --edfm-mono );
font-weight: 700;
font-size: 1.05rem;
line-height: 1;
}
.toctext {
color: inherit;
font-size: 0.85rem;
line-height: 1.3;
}
/* 2026-08-08: rebalanced for the 4-column desktop default above -- was
>1150px = 3 cols -> <=1150px = 2 cols -> <=560px = 1 col. A page with
12 sections (e.g. The Dweller) now gets 3 rows at desktop width instead
of 4, so a new <=860px step was added rather than dropping straight
from 3 to 2 columns at 1150px, which left the same "Star systems,
navigation and exploration"-style long labels cramped in the 1024px
range this breakpoint set was originally tuned for. Order stays widest
condition first, narrowest last, so cascade order matches the max-width
overlap correctly at every width. */
@media ( max-width: 1150px ) {
.toc > ul {
grid-template-columns: repeat( 3, 1fr );
}
}
@media ( max-width: 860px ) {
.toc > ul {
grid-template-columns: repeat( 2, 1fr );
}
}
@media ( max-width: 560px ) {
.toc > ul {
grid-template-columns: 1fr;
}
/* Single-column tiles are already full-width here, so there's no
density pressure left -- restore closer to the pre-2026-08-08
padding instead of the tighter desktop value, keeping tap targets
comfortable rather than compacting mobile just because desktop
compacted. */
.toc a {
padding: 0.7em 0.95em;
}
}

/* ==========================================================================
6. PANELS / CALLOUTS, and 11. ARTICLE METADATA / STATUS MODULE
========================================================================== */
/* Deliberately NOT defined here. .edfm-box / .edfm-panel* / .edfm-status* /
.edfm-inline-flag / .edfm-related* are used exclusively by the
editorial templates (see Template:Article status, Template:Draft
warning, Template:Related articles, etc.), which already load
Template:EDFM style/styles.css themselves via <templatestyles>.
Defining the same class names in both this file and that one would
leave their relative precedence dependent on unclear/unstable ordering
between a ResourceLoader "site" stylesheet and a TemplateStyles-injected
<style> tag -- rather than rely on that, there is exactly one definition
of each, living in Template:EDFM style/styles.css. That file freely uses
the --edfm-* custom properties defined above; custom properties resolve
through the DOM regardless of which stylesheet declared vs references
them, so this split costs nothing. */

/* ==========================================================================
7. TABLES (wikitables, and Special: pages' tables)
========================================================================== */
table.wikitable,
table.mw-datatable {
background-color: var( --edfm-surface-2 );
color: var( --edfm-text );
border-color: var( --edfm-border );
font-size: var( --edfm-fs-body );
}
table.wikitable > tr > th,
table.wikitable > * > tr > th {
background-color: var( --edfm-surface-3 );
color: var( --edfm-text );
border-color: var( --edfm-border );
font-family: var( --edfm-mono );
letter-spacing: 0.03em;
text-transform: uppercase;
font-size: var( --edfm-fs-meta );
text-align: left;
padding: 0.6em 0.8em;
}
table.wikitable > tr > td,
table.wikitable > * > tr > td {
border-color: var( --edfm-border-soft );
padding: 0.6em 0.8em;
}
/* Subtle alternating row treatment -- helps scanning wide/dense reference
tables without turning them into cards. */
table.wikitable > tbody > tr:nth-child( even ),
table.wikitable > * > tr:nth-child( even ) {
background-color: var( --edfm-surface-1 );
}

/* ==========================================================================
15. FOOTER
========================================================================== */
/* A real branded footer: a small wordmark line (pure CSS generated
content -- decorative branding only, redundant with the sidebar logo
already visible, so nothing load-bearing depends on it being
selectable), a top rule with more separation from the article above it,
and MediaWiki's real info/places/icon links laid out on a clean grid
with the badges aligned as a group rather than floating alone. */
.mw-footer {
margin-left: var( --edfm-sidebar-clear );
margin-right: var( --edfm-gutter );
margin-top: 2.5rem;
padding-top: 1.6rem;
border-top: 1px solid var( --edfm-border );
display: grid;
grid-template-columns: 1fr auto;
grid-template-areas: "brand brand" "info icons" "places icons";
align-items: center;
column-gap: 2em;
row-gap: 0.4rem;
}
.mw-footer::before {
grid-area: brand;
content: 'EDFM // Elite Dangerous Field Manual';
font-family: var( --edfm-mono );
font-size: 0.85rem;
font-weight: 700;
letter-spacing: 0.06em;
text-transform: uppercase;
color: var( --edfm-text-muted );
margin-bottom: 0.5rem;
}
.mw-footer,
.mw-footer li,
#footer-info,
#footer-info li {
color: var( --edfm-text-dim );
border-color: var( --edfm-border-soft );
font-size: var( --edfm-fs-meta );
}
#footer-info {
grid-area: info;
margin: 0;
line-height: 1.6;
}
#footer-places {
grid-area: places;
margin: 0;
}
/* Same "small uppercase label" treatment used for tags/meta text
elsewhere, so these read as deliberate EDFM navigation rather than
default MediaWiki footer links. */
#footer-places li {
display: inline-block;
margin-right: 1.4em;
}
#footer-places a {
font-family: var( --edfm-mono );
font-weight: 700;
letter-spacing: 0.03em;
text-transform: uppercase;
font-size: 0.78rem;
}
/* A left rule ties the badges to the rest of the footer instead of
letting them read as detached/floating in their own space. */
#footer-icons {
grid-area: icons;
align-self: center;
display: flex;
gap: 0.75em;
margin: 0;
padding-left: 1.6em;
border-left: 1px solid var( --edfm-border-soft );
}
#footer-icons img {
background: var( --edfm-text );
border-radius: 2px;
}
@media ( max-width: 640px ) {
.mw-footer {
grid-template-columns: 1fr;
grid-template-areas: "brand" "info" "places" "icons";
}
#footer-icons {
margin-top: 0.7em;
padding-left: 0;
border-left: none;
border-top: 1px solid var( --edfm-border-soft );
padding-top: 0.7em;
}
}

/* ==========================================================================
MISC MediaWiki UI chrome that ships with light backgrounds by default
========================================================================== */
.catlinks {
background: none !important;
border: none !important;
border-top: 1px solid var( --edfm-border-soft ) !important;
color: var( --edfm-text-dim );
font-size: var( --edfm-fs-meta );
padding: 0.9em 0 0 0 !important;
margin-top: 1.8rem !important;
}
div.thumbinner {
background-color: var( --edfm-surface-2 );
border-color: var( --edfm-border );
}
.thumbimage {
background-color: var( --edfm-surface-1 );
border-color: var( --edfm-border );
}

/* Code / preformatted text (syntaxhighlight uses its own Pygments theme,
set via $wgPygmentsStyle in LocalSettings.php; this covers plain
<pre>/<code> that isn't Pygments-highlighted). */
pre, code, .mw-code {
background-color: var( --edfm-surface-2 );
color: var( --edfm-text );
border-color: var( --edfm-border );
font-family: var( --edfm-mono );
}

/* ==========================================================================
GENERIC INFOBOX -- see Template:Infobox
========================================================================== */
.edfm-infobox {
float: right;
clear: right;
width: 310px;
margin: 0 0 1.2em 1.2em;
border: 1px solid var( --edfm-border );
border-top: 2px solid var( --edfm-orange );
background: var( --edfm-surface-2 );
color: var( --edfm-text );
font-size: 0.92rem;
}
.edfm-infobox-title {
background: var( --edfm-orange );
color: var( --edfm-bg-deep );
font-weight: 700;
font-family: var( --edfm-mono );
letter-spacing: 0.04em;
text-transform: uppercase;
text-align: center;
padding: 0.5em 0.6em;
clip-path: polygon( 0 0, calc( 100% - 14px ) 0, 100% 14px, 100% 100%, 0 100% );
}
.edfm-infobox-image {
text-align: center;
padding: 0.6em;
border-bottom: 1px solid var( --edfm-border );
}
.edfm-infobox-image-placeholder {
display: flex;
align-items: center;
justify-content: center;
height: 160px;
border: 1px dashed var( --edfm-border );
background: var( --edfm-surface-1 );
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-utility );
text-transform: uppercase;
letter-spacing: 0.06em;
text-align: center;
padding: 0.5em;
}
/* Optional section label (Template:Infobox's |groupN=) splitting a long
infobox into scannable groups, e.g. Engineer infoboxes into "ENGINEER"
and "ACCESS" (2026-08-08, part of the Engineer article layout pass). A
shaded band with a bottom rule rather than a full boxed sub-header --
consistent with .edfm-infobox-row's own bottom-rule-only separator, not
a new visual language. */
.edfm-infobox-group {
background: var( --edfm-surface-3 );
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
font-weight: 700;
font-size: var( --edfm-fs-utility );
letter-spacing: 0.08em;
text-transform: uppercase;
padding: 0.35em 0.7em;
border-bottom: 1px solid var( --edfm-border );
}
.edfm-infobox-row {
display: flex;
border-bottom: 1px solid var( --edfm-border-soft );
padding: 0.45em 0.7em;
}
.edfm-infobox-row:last-child {
border-bottom: none;
}
.edfm-infobox-label {
font-weight: 700;
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-meta );
width: 40%;
flex-shrink: 0;
color: var( --edfm-cyan );
}
.edfm-infobox-value {
width: 60%;
}
@media ( max-width: 640px ) {
.edfm-infobox {
float: none;
width: auto;
margin: 1em 0;
}
}

/* ==========================================================================
14. MOBILE
========================================================================== */
/* Vector legacy has NO built-in responsive breakpoint at all (unlike
Vector 2022) -- its entire header region (#mw-head, tabs, search,
personal tools/login) is built with absolute positioning and floats
that all assume a fixed-width sidebar reserving 10-11em on the left,
AND the page's actual DOM order is content-then-navigation-then-footer
(the absolute positioning was doing double duty: both moving the header
visually to the top AND compensating for that DOM order). Simply
removing the positioning stacks things in DOM order, which reads oddly
on a phone (article text, then the nav/sidebar, then the footer).
Confirmed the actual DOM structure directly (not guessed): <body>'s
real children are #mw-page-base, #mw-head-base, #content,
#mw-navigation (which itself contains #mw-head then #mw-panel, already
in the right relative order), #footer. Since all four major regions are
direct children of <body>, flexbox `order` on <body> can reorder them
properly without needing to touch the DOM itself.
Result: header/search/tabs, then sidebar nav, then content, then
footer -- a plain stacked mobile layout, not a collapsible hamburger
menu, but a correct and readable order. */
@media ( max-width: 800px ) {
body::before {
display: none;
}
body {
display: flex;
flex-direction: column;
}
/* #mw-head-base ships with `margin-top: -5em` in Vector legacy's own
CSS -- a trick to sit it behind the absolutely-positioned header.
Now that the header is a normal flex sibling, that negative margin
drags everything after it upward. Neutralize both decorative
strips. */
#mw-page-base,
#mw-head-base {
order: 0;
height: 0;
margin: 0;
min-height: 0;
}
#mw-navigation {
order: 1;
}
#content {
order: 2;
}
.mw-footer {
order: 3;
}

#mw-head {
position: static;
width: auto;
background-image: none;
background-color: var( --edfm-surface-2 );
}
#left-navigation,
#right-navigation {
float: none;
margin: 0 !important;
width: auto;
clear: both;
}
#left-navigation {
margin-top: 0 !important;
}
/* Core Vector legacy floats each tab/dropdown portlet
(.vector-menu-tabs-legacy for Page/Discussion and Read/View
source/View history, .vector-menu-dropdown for the More menu) AND
floats every <li> inside their <ul>, with no wrapping at all -- at
narrow widths the labels just overflow and overlap each other
(confirmed with a real screenshot: "View source" and "More"
overlapped instead of wrapping to a new line). Switching the
portlets to inline-block and their tab lists to flex-wrap lets them
reflow onto as many rows as needed instead. */
#left-navigation .vector-menu-tabs-legacy,
#right-navigation .vector-menu-tabs-legacy,
#right-navigation .vector-menu-dropdown {
float: none;
display: inline-block;
vertical-align: top;
}
.vector-menu-tabs-legacy ul {
float: none;
display: flex;
flex-wrap: wrap;
}
.vector-menu-tabs-legacy li {
float: none;
}
#p-personal {
position: static;
text-align: right;
padding: 0.5em 1em;
margin: 0;
right: auto !important;
top: auto;
}
#p-personal ul {
padding-left: 0;
}
.vector-search-box {
float: none;
margin: 0.5em 1em;
display: block;
}
.vector-search-box-inner {
width: auto;
max-width: none;
}
#mw-panel {
position: static;
width: auto;
padding: 0.5em 1em;
float: none;
background: var( --edfm-bg-deep );
border-top: 1px solid var( --edfm-border );
border-bottom: 1px solid var( --edfm-border );
}
.mw-body,
#mw-data-after-content,
.mw-footer {
margin-left: 0 !important;
margin-right: 0 !important;
max-width: none;
}
.mw-body {
margin-top: 0;
border-width: 0;
padding: 1em;
}
.edfm-status-details {
grid-template-columns: 1fr;
}
/* .toc > ul column count is NOT overridden here -- the dedicated
1150px/560px breakpoints above already cover every width down to
the smallest phones; duplicating a rule here previously fought
those (same specificity, this position in the cascade would have
won and wrongly forced 1 column as low as 561px). */
#firstHeading {
font-size: 1.6rem;
}
.mw-body h2 {
margin-top: 2.25rem;
}
.edfm-eyebrow {
padding-top: 0.9em;
}
}
/* ==========================================================================
16. OOUI DIALOGS -- VisualEditor's save dialog, and any other OOUI
dialog (delete/move/protect confirmations, special-page dialogs).
These render via OOUI's own bundled WikimediaUI theme stylesheet,
entirely outside the .edfm-* component system this file otherwise
covers, so without this they show up starkly white against the rest of
the dark-themed site regardless of any variable/token used elsewhere in
this file. !important is justified the same way as the h1-h6 fix above:
OOUI's own stylesheet loads with equal-or-higher effective specificity,
and this is a correctness/contrast fix, not decoration.
========================================================================== */
.oo-ui-window-frame {
background: var( --edfm-surface-2 ) !important;
color: var( --edfm-text ) !important;
}
.oo-ui-processDialog {
background: rgba( 7, 9, 11, 0.75 ) !important;
}
.oo-ui-processDialog-navigation,
.oo-ui-window-head,
.oo-ui-window-foot {
background: var( --edfm-surface-3 ) !important;
border-color: var( --edfm-border ) !important;
}
.oo-ui-processDialog-title,
.oo-ui-labelElement-label,
.oo-ui-fieldLayout-header,
.oo-ui-fieldLayout .oo-ui-labelElement-label {
color: var( --edfm-text ) !important;
}
.oo-ui-inputWidget-input {
background: var( --edfm-surface-1 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}
.ve-ui-mwSaveDialog-options,
.oo-ui-panelLayout,
.oo-ui-window-body {
background: var( --edfm-surface-2 ) !important;
color: var( --edfm-text ) !important;
}
.oo-ui-popupWidget-popup {
background: var( --edfm-surface-2 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}
.oo-ui-buttonElement:not( .oo-ui-flaggedElement-primary ) > .oo-ui-buttonElement-button {
background: var( --edfm-surface-4 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}
/* ==========================================================================
17. OOUI TOOLBAR -- VisualEditor's persistent editing toolbar and its
dropdown menus (Cite, Insert, paragraph style, etc.), and the equivalent
toolbar/popups used when editing a single section. Same root cause as
16. OOUI DIALOGS above (OOUI's own bundled theme, not touched by
anything else in this file), found separately because it's a different
set of OOUI classes (toolbar chrome, not dialog chrome). Icons are not
overridden here and don't need to be -- they're currentColor-based, so
they pick up the text colour set below automatically.
========================================================================== */
.oo-ui-toolbar-bar,
.oo-ui-toolGroup-tools,
.oo-ui-popupToolGroup-tools {
background: var( --edfm-surface-3 ) !important;
border-color: var( --edfm-border ) !important;
}
.oo-ui-tool-title,
.oo-ui-tool-link,
.oo-ui-toolGroup-tools .oo-ui-optionWidget,
.oo-ui-menuOptionWidget,
.oo-ui-labelElement-label {
color: var( --edfm-text ) !important;
}
.oo-ui-optionWidget.oo-ui-optionWidget-selected,
.oo-ui-optionWidget:hover,
.oo-ui-tool:hover .oo-ui-tool-link {
background: var( --edfm-surface-4 ) !important;
}
/* ==========================================================================
18. OOUI GENERIC MENUS -- .oo-ui-menuSelectWidget is OOUI's general
dropdown/autocomplete menu class (paragraph-style picker, citation-type
picker, link/media search suggestions, etc.) -- a different class from
the toolbar-specific popups in 17. above, confirmed separately via
computed-style inspection to default to the same white OOUI theme
background.
========================================================================== */
.oo-ui-menuSelectWidget {
background: var( --edfm-surface-3 ) !important;
border-color: var( --edfm-border ) !important;
}
.oo-ui-menuOptionWidget {
color: var( --edfm-text ) !important;
}
.oo-ui-menuOptionWidget.oo-ui-optionWidget-highlighted,
.oo-ui-menuOptionWidget:hover {
background: var( --edfm-surface-4 ) !important;
}
/* ==========================================================================
19. OOUI ICONS -- the toolbar/menu icons themselves (Bold, link, list,
Cite, undo/redo, etc.) are rendered as background-image SVGs with a
colour baked into the SVG markup, not currentColor-based masks -- so
16-18 above (which only recolour backgrounds/text) left them dark and
low-contrast against the now-dark surfaces. OOUI ships its own fix for
exactly this, gated behind a narrow accessibility media query
(forced-colors + prefers-color-scheme: dark) that doesn't apply to this
site's own always-on dark theme -- reusing that exact technique
unconditionally rather than inventing a different one. `:not(
.oo-ui-image-invert )` is OOUI's own exclusion for icons already meant
to render light (e.g. on the orange primary-button background) --
inverting those too would flip them back to dark.
========================================================================== */
.oo-ui-iconElement-icon:not( .oo-ui-image-invert ),
.oo-ui-indicatorElement-indicator:not( .oo-ui-image-invert ) {
filter: invert( 1 ) hue-rotate( 180deg );
}
/* ==========================================================================
20. EDIT SOURCE FORM -- MediaWiki core + WikiEditor + CodeMirror

The source editor is not covered by the article/component selectors above:
`action=edit` loads core edit-form CSS, WikiEditor chrome, and sometimes
CodeMirror with their own light neutral surfaces. Force the same EDFM dark
surface stack here so the source page no longer flashes as a white island.
========================================================================== */
.mw-editform,
#editform,
#toolbar,
.editOptions,
.mw-editTools,
.mw-summary-preview,
.mw-datatable,
.wikiEditor-ui,
.wikiEditor-ui-view,
.wikiEditor-ui-text,
.wikiEditor-ui-toolbar,
.wikiEditor-ui-top,
.wikiEditor-ui-controls,
.wikiEditor-ui-tabs,
.wikiEditor-ui-buttons,
.CodeMirror,
.CodeMirror-scroll {
background: var( --edfm-surface-1 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}
.mw-editform textarea,
#wpTextbox1,
#wpSummary,
#wpSummaryWidget input,
#editform input[type='text'],
#editform input[type='search'],
#editform textarea,
.wikiEditor-ui-text textarea,
.CodeMirror-code,
.CodeMirror-lines,
.CodeMirror pre {
background: var( --edfm-bg-deep ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
caret-color: var( --edfm-orange-bright );
}
.wikiEditor-ui-toolbar,
.wikiEditor-ui-toolbar .group,
.wikiEditor-ui-toolbar .tabs,
.wikiEditor-ui-toolbar .page,
.wikiEditor-ui-toolbar .sections,
.wikiEditor-ui-toolbar .section,
.wikiEditor-ui-toolbar .options,
.wikiEditor-ui-toolbar .booklet,
.wikiEditor-ui-toolbar .pages,
.CodeMirror-gutters {
background: var( --edfm-surface-2 ) !important;
color: var( --edfm-text-muted ) !important;
border-color: var( --edfm-border ) !important;
}
.wikiEditor-ui-toolbar a,
.wikiEditor-ui-toolbar .label,
.wikiEditor-ui-toolbar .tab a,
.mw-editTools a,
.editOptions label,
.mw-editform label,
.CodeMirror-linenumber {
color: var( --edfm-text ) !important;
}
.wikiEditor-ui-toolbar .tab a:hover,
.wikiEditor-ui-toolbar .tool-button:hover,
.wikiEditor-ui-toolbar .tool-select:hover,
.wikiEditor-ui-toolbar .page-table th,
.wikiEditor-ui-toolbar .page-table td,
.CodeMirror-activeline-background {
background: var( --edfm-surface-3 ) !important;
color: var( --edfm-text ) !important;
}
.wikiEditor-ui-toolbar .tab.current a,
.wikiEditor-ui-toolbar .section-main,
.CodeMirror-selected {
background: var( --edfm-surface-4 ) !important;
}
.CodeMirror-cursor {
border-left-color: var( --edfm-orange-bright ) !important;
}
.CodeMirror-matchingbracket {
color: var( --edfm-orange-bright ) !important;
}

/* ==========================================================================
21. FILE PAGE CHROME -- #filetoc (the File / File history / File usage /
Metadata nav on File: description pages) is defined in MediaWiki core's
mediawiki.action.view.filepage.less, entirely separate from both the
.edfm-* system and the OOUI fixes in 16-19 above -- a different
subsystem again, only loaded on File: pages, which is why it was never
touched by anything else in this file. Link colour inside it already
correctly inherits the site's normal link blue; only the light neutral
background/border needed overriding.
========================================================================== */
#filetoc {
background: var( --edfm-surface-2 ) !important;
border-color: var( --edfm-border ) !important;
}
/* ==========================================================================
22. FILE PAGE: METADATA TABLE + MEDIA VIEWER BUTTON -- #mw_metadata is
the EXIF-style metadata table (separate from the File history table
above -- that one already carries the .wikitable class and picked up
dark styling from 7. TABLES automatically; this one doesn't have that
class, so it never matched). The "Open in Media Viewer" button is a
Codex component (MultimediaViewer extension) -- a third distinct
styling subsystem from OOUI and MediaWiki core skinning, again never
touched by anything else in this file.
========================================================================== */
#mw_metadata th,
#mw_metadata td {
background: var( --edfm-surface-2 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}
.mw-mmv-view-expanded.cdx-button {
background: var( --edfm-surface-4 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}

/* ===========================================================================
23. RUNE-WIKI-INSPIRED MOBILE APP SHELL
=========================================================================== */
/* Inspired by RuneScape.wiki's mobile ergonomics -- persistent top app bar,
large touch targets, off-canvas navigation, search-forward layout, and
single-column readable article flow -- while preserving EDFM's dark field
manual identity and not copying RuneScape.wiki assets/CSS.
The close button is injected into #mw-panel by Common.js, so it must be
explicitly hidden by default; otherwise a tiny native white button appears
in the desktop sidebar's top-left corner. */
.edfm-mobile-appbar,
.edfm-mobile-scrim,
.edfm-mobile-close-button {
display: none;
}
@media ( max-width: 800px ) {
html {
-webkit-text-size-adjust: 100%;
}
body {
background: var( --edfm-bg-page );
overflow-x: hidden;
}
body.edfm-mobile-menu-open {
overflow: hidden;
}
.edfm-mobile-appbar {
display: grid;
grid-template-columns: 48px 1fr 48px;
align-items: center;
position: sticky;
top: 0;
z-index: 1200;
min-height: 56px;
padding: 0 0.35rem;
background:
linear-gradient( 90deg, rgba( 255, 138, 0, 0.18 ), transparent 38% ),
var( --edfm-surface-2 );
border-bottom: 1px solid var( --edfm-border );
box-shadow: 0 10px 24px rgba( 0, 0, 0, 0.35 );
}
.edfm-mobile-brand {
min-width: 0;
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
font-weight: 800;
letter-spacing: 0.05em;
text-transform: uppercase;
text-decoration: none;
white-space: nowrap;
overflow: hidden;
text-overflow: ellipsis;
}
.edfm-mobile-brand::before {
content: 'EDFM // ';
color: var( --edfm-orange );
}
.edfm-mobile-menu-button,
.edfm-mobile-search-button,
.edfm-mobile-close-button {
appearance: none;
-webkit-appearance: none;
display: inline-flex;
align-items: center;
justify-content: center;
min-width: 44px;
min-height: 44px;
margin: 0;
border: 0;
border-radius: 0;
background: transparent;
color: var( --edfm-text );
font: 700 1.5rem/1 var( --edfm-mono );
cursor: pointer;
}
.edfm-mobile-menu-button:focus-visible,
.edfm-mobile-search-button:focus-visible,
.edfm-mobile-close-button:focus-visible {
outline: 2px solid var( --edfm-cyan );
outline-offset: -4px;
}
.edfm-mobile-menu-button::before {
content: '☰';
color: var( --edfm-orange );
}
.edfm-mobile-search-button::before {
content: '⌕';
font-size: 1.85rem;
color: var( --edfm-cyan );
}
.edfm-mobile-close-button::before {
content: '×';
color: var( --edfm-text );
}
.edfm-mobile-scrim {
display: block;
position: fixed;
inset: 0;
z-index: 1000;
background: rgba( 0, 0, 0, 0.58 );
opacity: 0;
pointer-events: none;
transition: opacity 0.18s ease;
}
body.edfm-mobile-menu-open .edfm-mobile-scrim {
opacity: 1;
pointer-events: auto;
}
#mw-navigation {
background: var( --edfm-surface-2 );
box-shadow: none;
}
#mw-head {
position: relative;
z-index: 1100;
border-bottom: 1px solid var( --edfm-border );
}
#mw-head .vector-search-box {
display: none;
margin: 0;
padding: 0.65rem;
background: var( --edfm-surface-2 );
border-top: 1px solid var( --edfm-border-soft );
}
body.edfm-mobile-search-open #mw-head .vector-search-box {
display: block;
}
#mw-head .vector-search-box-inner,
#mw-head #searchform {
width: 100%;
}
#mw-head #searchInput {
min-height: 44px;
box-sizing: border-box;
width: 100%;
font-size: 1rem;
}
#left-navigation,
#right-navigation {
padding: 0 0.45rem 0.35rem;
background: var( --edfm-surface-2 );
overflow-x: auto;
white-space: nowrap;
-webkit-overflow-scrolling: touch;
}
.vector-menu-tabs-legacy ul {
flex-wrap: nowrap;
}
.vector-menu-tabs-legacy li a,
.vector-menu-tabs-legacy li a:visited,
.vector-menu-dropdown .vector-menu-heading {
min-height: 36px;
display: inline-flex;
align-items: center;
}
#p-personal {
display: none;
}
#mw-panel {
position: fixed;
top: 0;
left: 0;
z-index: 1300;
width: min( 82vw, 22rem );
height: 100dvh;
box-sizing: border-box;
padding: 0;
background: var( --edfm-surface-1 );
border: 0;
border-right: 1px solid var( --edfm-border );
box-shadow: 18px 0 36px rgba( 0, 0, 0, 0.45 );
overflow-y: auto;
-webkit-overflow-scrolling: touch;
transform: translateX( -105% );
transition: transform 0.2s ease;
}
body.edfm-mobile-menu-open #mw-panel {
transform: translateX( 0 );
}
#mw-panel::before {
content: 'EDFM Navigation';
display: block;
position: sticky;
top: 0;
z-index: 1;
padding: 1rem 3.4rem 1rem 1rem;
background: var( --edfm-surface-2 );
border-bottom: 1px solid var( --edfm-border );
color: var( --edfm-orange );
font: 800 0.86rem/1.2 var( --edfm-mono );
letter-spacing: 0.08em;
text-transform: uppercase;
}
#mw-panel .edfm-mobile-close-button {
position: absolute;
top: 0.3rem;
right: 0.35rem;
z-index: 2;
}
#mw-panel .portal,
#mw-panel .vector-menu-portal {
margin: 0;
padding: 0.75rem 0;
border-bottom: 1px solid var( --edfm-border-soft );
}
#mw-panel .vector-menu-heading {
margin: 0.25rem 1rem 0.45rem;
}
#mw-panel .vector-menu-content-list li a,
#mw-panel .vector-menu-content-list li a:visited {
display: flex;
align-items: center;
min-height: 46px;
box-sizing: border-box;
padding: 0.55rem 1rem;
border-left: 3px solid transparent;
color: var( --edfm-text-muted );
font-size: 1rem;
text-decoration: none;
}
#mw-panel .vector-menu-content-list li a:hover,
#mw-panel .vector-menu-content-list li a:focus {
background: var( --edfm-surface-3 );
border-left-color: var( --edfm-cyan );
color: var( --edfm-text );
}
#mw-panel .edfm-nav-current > a,
#mw-panel .edfm-nav-current > a:visited {
background: rgba( 255, 138, 0, 0.12 );
border-left-color: var( --edfm-orange );
color: var( --edfm-orange ) !important;
}
.mw-body {
padding: clamp( 1rem, 4vw, 1.35rem );
font-size: 1rem;
line-height: 1.68;
}
#siteNotice {
margin-bottom: 1rem;
padding-bottom: 0.85rem;
}
#firstHeading {
font-size: clamp( 1.65rem, 8vw, 2.25rem );
line-height: 1.1;
letter-spacing: -0.015em;
}
.mw-body h2 {
font-size: 1.18rem;
line-height: 1.25;
}
.mw-body p,
.mw-body li {
max-width: none;
}
.mw-body img,
.mw-body .thumb,
.mw-body .thumbinner,
.mw-body .thumbimage {
max-width: 100% !important;
height: auto !important;
box-sizing: border-box;
}
.mw-body .thumb,
.mw-body .tright,
.mw-body .tleft {
float: none !important;
clear: both;
width: auto !important;
margin: 1rem 0 !important;
}
.mw-parser-output > table.wikitable,
.mw-parser-output > table.mw-datatable {
display: block;
width: 100% !important;
max-width: 100%;
overflow-x: auto;
-webkit-overflow-scrolling: touch;
white-space: nowrap;
}
.mw-parser-output > table.wikitable th,
.mw-parser-output > table.wikitable td,
.mw-parser-output > table.mw-datatable th,
.mw-parser-output > table.mw-datatable td {
white-space: normal;
min-width: 8rem;
}
.edfm-infobox {
font-size: 0.95rem;
}
.edfm-infobox-row {
display: grid;
grid-template-columns: minmax( 7.5rem, 40% ) 1fr;
gap: 0.5rem;
padding: 0.65rem 0.8rem;
}
.edfm-infobox-label,
.edfm-infobox-value {
width: auto;
}
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type,
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type tbody,
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type tr,
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type th,
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type td {
display: block;
width: 100% !important;
box-sizing: border-box;
}
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type {
overflow: visible;
white-space: normal;
background: transparent;
border: 0;
}
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type th {
margin-top: 0.75rem;
border-left: 3px solid var( --edfm-orange );
}
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type td {
margin-bottom: 0.75rem;
background: var( --edfm-surface-2 );
border-left: 3px solid var( --edfm-border );
}
.mw-footer {
padding: 1rem;
margin-top: 1.5rem;
}
}
@media ( max-width: 430px ) {
.edfm-mobile-brand::before {
content: 'EDFM';
margin-right: 0.45rem;
}
.edfm-mobile-brand {
font-size: 0.88rem;
}
.edfm-infobox-row {
grid-template-columns: 1fr;
gap: 0.2rem;
}
}

/* 22a. Mobile action tabs refinement: keep Vector's page/discussion/read/
source/history controls available, but put them on one compact horizontal
action rail so the first phone viewport feels like a real mobile app shell
instead of two stacked desktop tab bars. */
@media ( max-width: 800px ) {
body:not( .edfm-mobile-search-open ) #mw-head {
display: flex;
align-items: stretch;
gap: 0;
overflow-x: auto;
overflow-y: hidden;
-webkit-overflow-scrolling: touch;
scrollbar-width: thin;
}
body:not( .edfm-mobile-search-open ) #left-navigation,
body:not( .edfm-mobile-search-open ) #right-navigation {
flex: 0 0 auto;
clear: none !important;
float: none !important;
width: auto;
padding: 0 0.25rem;
margin: 0 !important;
border-right: 1px solid var( --edfm-border-soft );
}
body:not( .edfm-mobile-search-open ) .vector-menu-tabs-legacy,
body:not( .edfm-mobile-search-open ) .vector-menu-dropdown {
float: none !important;
display: inline-block;
}
body:not( .edfm-mobile-search-open ) .vector-menu-tabs-legacy li a,
body:not( .edfm-mobile-search-open ) .vector-menu-tabs-legacy li a:visited,
body:not( .edfm-mobile-search-open ) .vector-menu-dropdown .vector-menu-heading {
min-height: 40px;
padding-left: 0.55rem;
padding-right: 0.55rem;
font-size: 0.68rem;
}
body.edfm-mobile-search-open #mw-head {
display: block;
}
}

/* ===========================================================================
24. HARD OVERRIDE: JUMP TILE LEFT RAIL

The earlier border-left rail can be swallowed by ResourceLoader/cascade or
visually read as part of the tile edge. Draw the rail as a high-specificity
gradient on the actual top-level TOC anchors so it is unmistakable on the
live jump grid.
=========================================================================== */
#toc.toc > ul > li > a,
.mw-parser-output #toc > ul > li > a,
.mw-parser-output .toc > ul > li > a {
background-image: linear-gradient( 90deg, var( --edfm-orange ) 0, var( --edfm-orange ) 6px, transparent 6px ) !important;
border-left: 0 !important;
padding-left: 1rem !important;
}
#toc.toc > ul > li > a:hover,
#toc.toc > ul > li > a:focus-visible,
.mw-parser-output #toc > ul > li > a:hover,
.mw-parser-output #toc > ul > li > a:focus-visible,
.mw-parser-output .toc > ul > li > a:hover,
.mw-parser-output .toc > ul > li > a:focus-visible {
background-image: linear-gradient( 90deg, var( --edfm-cyan ) 0, var( --edfm-cyan ) 6px, transparent 6px ) !important;
}

/* ===========================================================================
25. SOURCE EDIT CONFLICT / WIKITEXT DIFF THEME

Source-edit conflict review uses MediaWiki's diff table classes, not the
normal edit textarea/WikiEditor chrome. Without this, unchanged rows and
inline change pills fall back to stark white/yellow/blue defaults. Keep the
old/new meaning, but render it in EDFM's dark surfaces with restrained
orange/cyan accents.
=========================================================================== */
.mw-parser-output table.diff,
table.diff,
.diff {
background: var( --edfm-bg-deep ) !important;
color: var( --edfm-text ) !important;
border-collapse: separate !important;
border-spacing: 0 0.12rem !important;
}
.diff-title,
.diff-otitle,
.diff-ntitle,
#mw-diff-otitle1,
#mw-diff-ntitle1 {
background: var( --edfm-bg-deep ) !important;
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
}
td.diff-lineno,
.diff-lineno {
background: transparent !important;
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
font-weight: 700;
border: 0 !important;
padding: 0.35rem 0.5rem !important;
}
td.diff-marker,
.diff-marker {
background: transparent !important;
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
font-weight: 700;
padding: 0.25rem 0.45rem !important;
text-align: center;
}
td.diff-context,
td.diff-addedline,
td.diff-deletedline,
.diff-context,
.diff-addedline,
.diff-deletedline,
.mw-diff-inline-context,
.mw-diff-inline-added,
.mw-diff-inline-deleted,
.mw-diff-inline-changed,
.mw-diff-inline-moved {
background: var( --edfm-surface-1 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
font-family: var( --edfm-mono );
box-shadow: none !important;
}
td.diff-context:empty,
td.diff-addedline:empty,
td.diff-deletedline:empty,
.diff-context:empty,
.diff-addedline:empty,
.diff-deletedline:empty {
/* Empty diff cells are alignment placeholders. Keep their card boundary so
the two-column source-conflict diff does not look broken, but make them
compact and neutral instead of tall blank blocks. */
background: var( --edfm-surface-1 ) !important;
border-color: var( --edfm-border ) !important;
box-shadow: none !important;
min-height: 0;
padding-top: 0.08rem !important;
padding-bottom: 0.08rem !important;
}
td.diff-deletedline,
.diff-deletedline,
.mw-diff-inline-deleted {
background: rgba( 255, 138, 0, 0.08 ) !important;
border-color: rgba( 255, 138, 0, 0.6 ) !important;
border-left-color: var( --edfm-orange ) !important;
}
td.diff-addedline,
.diff-addedline,
.mw-diff-inline-added {
background: rgba( 66, 199, 217, 0.08 ) !important;
border-color: rgba( 66, 199, 217, 0.6 ) !important;
border-left-color: var( --edfm-cyan ) !important;
}
.diffchange,
.diff-addedline .diffchange,
.diff-deletedline .diffchange,
.mw-diff-inline-added ins,
.mw-diff-inline-changed ins,
.mw-diff-inline-moved ins,
.mw-diff-inline-deleted del,
.mw-diff-inline-changed del,
.mw-diff-inline-moved del {
border-radius: 3px !important;
padding: 0.08rem 0.22rem !important;
font-weight: 700;
text-decoration: none !important;
color: var( --edfm-bg-deep ) !important;
}
.diff-deletedline .diffchange,
.mw-diff-inline-deleted del,
.mw-diff-inline-changed del,
.mw-diff-inline-moved del {
background: var( --edfm-orange-bright ) !important;
}
.diff-addedline .diffchange,
.mw-diff-inline-added ins,
.mw-diff-inline-changed ins,
.mw-diff-inline-moved ins {
background: var( --edfm-cyan ) !important;
}
.mw-explainconflict,
#wpTextbox2,
textarea#wpTextbox2,
textarea.mw-textarea-oldrev {
background: var( --edfm-surface-1 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}

/* Engineer directory portrait chips -- intentionally quiet so table rows still
read like data rows, not card/list hybrids. */
.edfm-engineer-entry {
display: inline-flex;
align-items: center;
gap: 0.45rem;
min-width: max-content;
}
.edfm-engineer-entry .mw-file-element {
width: 30px;
height: 30px;
object-fit: cover;
border-radius: 3px;
border: 1px solid var( --edfm-border );
background: var( --edfm-surface-0 );
box-shadow: none;
}
.edfm-engineer-entry__name {
line-height: 1.2;
}

/* Frontier official news feed image treatment */
.edfm-frontier-news .edfm-news-card-art-image {
display: block;
position: relative;
padding: 0;
min-height: 9.5rem;
background: var( --edfm-surface-4 );
overflow: hidden;
}
.edfm-frontier-news .edfm-news-card-primary .edfm-news-card-art-image {
min-height: 13.5rem;
}
.edfm-frontier-news .edfm-news-card-art-image > span,
.edfm-frontier-news .edfm-news-card-art-image .mw-default-size,
.edfm-frontier-news .edfm-news-card-art-image .mw-file-description {
display: block !important;
position: absolute;
inset: 0;
width: 100% !important;
height: 100% !important;
max-width: none !important;
margin: 0 !important;
}
.edfm-frontier-news .edfm-news-card-art-image .mw-file-element {
display: block !important;
width: 100% !important;
height: 100% !important;
max-width: none !important;
object-fit: cover;
transition: transform 0.2s ease, filter 0.2s ease;
}
.edfm-frontier-news .edfm-news-card:hover .edfm-news-card-art-image .mw-file-element {
filter: brightness( 1.08 ) contrast( 1.05 );
transform: scale( 1.035 );
}
.edfm-frontier-news .edfm-news-source-badge {
display: inline-flex !important;
align-items: center;
position: absolute !important;
left: 0.8rem !important;
right: auto !important;
bottom: 0.75rem !important;
z-index: 2;
max-width: calc( 100% - 1.6rem );
padding: 0.25rem 0.55rem;
background: rgba( 10, 13, 17, 0.82 );
border: 1px solid rgba( 255, 138, 0, 0.48 );
box-shadow: 0 8px 18px rgba( 0, 0, 0, 0.34 );
color: var( --edfm-text );
font-family: var( --edfm-mono );
font-size: 0.68rem;
font-weight: 800;
letter-spacing: 0.08em;
line-height: 1;
text-transform: uppercase;
white-space: nowrap;
pointer-events: none;
}

.edfm-news-attribution {
margin-top: 0.85rem;
padding-top: 0.75rem;
border-top: 1px solid var( --edfm-border-soft );
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-meta );
line-height: 1.45;
}

MediaWiki:Common.css

2026-08-10T04:05:38Z

EDFM Maintenance: Style sidebar Discord invite button

/* ==========================================================================
EDFM site-wide styling -- "Elite Dangerous technical field manual" theme.
Original CSS written for this project -- no code or assets copied from
runescape.wiki, Elite Dangerous, or any other site/game, and no Frontier
logo/branding/proprietary fonts/copied HUD elements. Restrained visual
influence only: dark industrial surfaces, subtle angular geometry,
orange/cyan accents used sparingly, information hierarchy first. This is
a reference site, not a HUD -- no glow, no neon, no glassmorphism, no
constant animation.

SKIN NOTE: the site uses Vector "legacy" (2011), not Vector 2022 -- see
the "Why Vector legacy" note in docs/content-style-guide.md (Vector 2022
hard-restricts its pinned sidebar to logged-in users; legacy has no such
restriction). Several rules below exist specifically to beat core Vector
legacy/mediawiki.skinning selectors that are *more specific* than a naive
override would be (documented inline at each occurrence) -- this isn't
guesswork, each one was found by reading the actual core .less source and
confirmed with a real rendered screenshot, not just computed-style checks
(:visited colours in particular are invisible to getComputedStyle by
design -- see the tab-bar note below).

2026-08-07 SECOND PASS: the first redesign pass was judged too close to
stock MediaWiki with a colour change -- this pass changes the actual
visual composition (centred workspace instead of a huge dead gutter,
a two-tier header, a real masthead, a tile-grid TOC, a restructured
status module, larger deliberate type scale, depth via surface
elevation instead of borders-around-everything) while reusing every
working mechanism from the first pass rather than throwing it away --
the tab/:visited fix, the external-link specificity fix, the mobile
reorder fix, and focus-visible/reduced-motion are all still here,
unchanged in mechanism.
========================================================================== */

/* ==========================================================================
1. DESIGN TOKENS
========================================================================== */
:root {
/* Depth system: site (outermost, visible in the sidebar/header/gutters)
-> article surface -> component surfaces, each a deliberate step
brighter so the page reads as having actual depth rather than "one
background colour with slightly lighter boxes everywhere". */
--edfm-bg-deep: #07090b;
--edfm-bg-page: #0a0e11;
--edfm-surface-1: #10171b;
--edfm-surface-2: #161f24;
--edfm-surface-3: #1c272d;
--edfm-surface-4: #233037;

--edfm-border: #26333b;
--edfm-border-soft: rgba( 255, 255, 255, 0.06 );

--edfm-text: #edf0f2;
--edfm-text-muted: #98a5ad;
--edfm-text-dim: #6c7a82;

/* Accents -- orange is reserved for navigation/selection/emphasis/
section numbering; cyan/blue are for links, verification info, and
secondary interface elements. See "Links" and "Colour system" in
docs/content-style-guide.md for the reasoning. */
--edfm-orange: #ff8a00;
--edfm-orange-bright: #ffa21a;
--edfm-cyan: #42c7d9;
--edfm-blue: #4f9fe8;

/* Derived link colours */
--edfm-link: var( --edfm-blue );
--edfm-link-visited: #3f7bb3;
--edfm-link-hover: #8cc4f7;
--edfm-link-external: var( --edfm-cyan );
--edfm-link-external-visited: #2f8f9c;
--edfm-link-external-hover: #7fe0ec;
--edfm-link-new: #e07a7a;

/* Status semantics (article metadata module) -- text label always
present too, never colour-only. */
--edfm-status-positive: var( --edfm-cyan );
--edfm-status-attention: var( --edfm-orange );
--edfm-status-neutral: var( --edfm-text-dim );
--edfm-status-positive-bg: rgba( 66, 199, 217, 0.12 );
--edfm-status-attention-bg: rgba( 255, 138, 0, 0.12 );
--edfm-status-neutral-bg: rgba( 108, 122, 130, 0.12 );

/* Typography -- explicit desktop scale (2026-08-07 pass 2). Sized in
rem against the root's real 16px (Vector legacy's own
@font-size-root is 100%, i.e. browser default -- confirmed by
reading skins.vector.styles.legacy/variables.less, not assumed)
rather than nested em, specifically so component sizes can't
compound smaller than intended inside whatever ambient size an
ancestor happens to set. */
--edfm-fs-title: clamp( 1.9rem, 1.4rem + 2vw, 2.25rem ); /* ~30-36px */
--edfm-fs-h2: 1.35rem; /* ~21.6px */
--edfm-fs-h3: 1.15rem; /* ~18.4px */
--edfm-fs-body: 1rem; /* 16px */
--edfm-fs-resource-name: 1.1rem; /* ~17.6px */
--edfm-fs-meta: 0.8rem; /* ~12.8px */
--edfm-fs-sidebar: 0.9375rem; /* 15px -- polish pass: +1px for readability */
--edfm-fs-utility: 0.72rem; /* ~11.5px */

--edfm-mono: 'JetBrains Mono', 'Fira Code', Consolas, 'SF Mono', Menlo, 'Courier New', monospace;
--edfm-sans: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Helvetica, Arial, sans-serif;

/* Legacy aliases: earlier revisions of this stylesheet used these names
directly and some inline template output/older docs may still refer
to them; keep pointing at the current tokens rather than duplicate
values that could drift out of sync. */
--edfm-orange-hover: var( --edfm-orange-bright );
--edfm-orange-active: var( --edfm-orange-bright );
--color-progressive: var( --edfm-orange );
--color-progressive--hover: var( --edfm-orange-bright );
--color-progressive--active: var( --edfm-orange-bright );
--color-progressive--focus: var( --edfm-orange );
--background-color-progressive: var( --edfm-orange );
--background-color-progressive--hover: var( --edfm-orange-bright );
--background-color-progressive--active: var( --edfm-orange-bright );
--border-color-progressive: var( --edfm-orange );
--border-color-progressive--hover: var( --edfm-orange-bright );
--border-color-progressive--active: var( --edfm-orange-bright );

/* Geometry / layout */
--edfm-corner: 10px;
/* Polish-pass bump from 1280px -- article read as slightly too narrow
on large desktop displays, and future reference tables (engineering,
ship stats, colonisation data) will want the room. Still centred
within the workspace via --edfm-gutter below, not stretched
edge-to-edge. */
--edfm-content-max: 1320px;
/* RuneScape.wiki-style integrated rail: wide enough for readable labels,
but joined directly to the page plane. Width and clear match so the
article starts beside the sidebar shadow instead of after a dead gutter. */
--edfm-sidebar-width: 12.75rem;
--edfm-sidebar-clear: 12.75rem;
/* The gutter is whatever's left of the workspace (viewport minus the
sidebar) after the capped content width, split evenly, never
negative. On a screen too narrow to fit sidebar+content-max, this
collapses to 0 and content just fills the workspace edge-to-edge --
see "GLOBAL LAYOUT" below for the full explanation. */
--edfm-gutter: max( 0px, calc( ( 100vw - var( --edfm-sidebar-clear ) - var( --edfm-content-max ) ) / 2 ) );
}

/* ==========================================================================
2. BASE / RESET-ADJACENT
========================================================================== */
html, body {
background-color: var( --edfm-bg-page );
color: var( --edfm-text );
}
body.mediawiki {
color: var( --edfm-text );
font-family: var( --edfm-sans );
font-size: var( --edfm-fs-body );
}
/* Background treatment: a faint technical grid plus a very soft radial
glow centred behind the (now centred) content column, so the composition
still has quiet visual interest in the gutters on ultrawide screens
instead of just flat colour -- both stay under ~3% opacity, this is
texture, not a HUD. Not image assets; pure CSS gradients. */
body {
background-image:
radial-gradient( ellipse 1400px 900px at 50% 0%, rgba( 66, 199, 217, 0.05 ), transparent 60% ),
linear-gradient( rgba( 255, 255, 255, 0.025 ) 1px, transparent 1px ),
linear-gradient( 90deg, rgba( 255, 255, 255, 0.025 ) 1px, transparent 1px );
background-size: auto, 48px 48px, 48px 48px;
background-repeat: no-repeat, repeat, repeat;
background-attachment: fixed, scroll, scroll;
}
/* Full-height sidebar rail: mirrors the RuneScape.wiki behavior where the
left rail has no visible bottom edge. The real #mw-panel only carries the
navigation content; this fixed layer paints the uninterrupted surface,
border, and shadow down the whole viewport. */
body::before {
content: '';
position: fixed;
top: 0;
left: 0;
bottom: 0;
width: var( --edfm-sidebar-width );
background: linear-gradient( 180deg, var( --edfm-surface-1 ) 0%, var( --edfm-bg-deep ) 100% );
border-right: 1px solid var( --edfm-border );
box-shadow: 10px 0 22px rgba( 0, 0, 0, 0.32 );
pointer-events: none;
z-index: 1;
}
@media ( prefers-reduced-motion: reduce ) {
*, *::before, *::after {
animation-duration: 0.001ms !important;
animation-iteration-count: 1 !important;
transition-duration: 0.001ms !important;
scroll-behavior: auto !important;
}
}
/* Focus visibility: applies to every interactive element, not just links. */
a:focus-visible,
button:focus-visible,
input:focus-visible,
textarea:focus-visible,
select:focus-visible,
[tabindex]:focus-visible {
outline: 2px solid var( --edfm-cyan );
outline-offset: 2px;
}

/* Small reusable angular motif: a corner-cut bracket, used sparingly (see
the redesign notes in docs/content-style-guide.md for exactly where) --
deliberately not applied everywhere. */
.edfm-corner-cut {
clip-path: polygon( 0 0, calc( 100% - var( --edfm-corner ) ) 0, 100% var( --edfm-corner ), 100% 100%, 0 100% );
}

/* ==========================================================================
3. TYPOGRAPHY
========================================================================== */
h1, h2, h3, h4, h5, h6 {
color: var( --edfm-text );
border-color: var( --edfm-border );
}
/* !important justified here: MediaWiki core's mediawiki.skinning module
sets heading colour with equal-specificity plain-tag selectors and kept
winning in testing despite this stylesheet loading later -- rather than
keep chasing exact cascade/bundling order, force it. This is a
correctness/contrast fix, not decoration. */
.mw-body h1, .mw-body h2, .mw-body h3, .mw-body h4, .mw-body h5, .mw-body h6,
.mw-heading1, .mw-heading2, .mw-heading3, .mw-heading4, .mw-heading5, .mw-heading6,
h1, h2, h3, h4, h5, h6 {
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
font-family: var( --edfm-mono );
letter-spacing: 0.01em;
line-height: 1.3;
}
#firstHeading {
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-title );
font-weight: 700;
margin-top: 0.15em;
}
/* Section headings (h2): "// " prefix in orange, bright heading text, a
short orange accent segment over the dim full-width divider core
already draws. Substantially more vertical space than a wiki section
normally gets, per the "sections feel packed together" fix -- 3.25rem
(~52px) above, ~1.1rem gap to the first content component below. If a
heading opts into explicit numbering via {{Section number}}, the
automatic "// " is suppressed so the two treatments don't double up. */
.mw-body h2 {
position: relative;
padding-bottom: 0.4em;
margin-top: 3.25rem;
margin-bottom: 1.1rem;
font-size: var( --edfm-fs-h2 );
}
.mw-body h2::before {
content: '// ';
color: var( --edfm-orange );
font-weight: 400;
}
.mw-body h2:has( .edfm-section-number )::before {
content: none;
}
.mw-body h2::after {
content: '';
position: absolute;
left: 0;
bottom: -1px;
width: 3em;
max-width: 100%;
height: 2px;
background: var( --edfm-orange );
}
.edfm-section-number {
color: var( --edfm-orange );
font-weight: 700;
}
.edfm-section-sep {
color: var( --edfm-orange );
margin-right: 0.15em;
}
h3, h4 {
color: var( --edfm-text );
font-size: var( --edfm-fs-h3 );
}
h3::before {
content: '/ ';
color: var( --edfm-text-dim );
font-weight: 400;
}

/* Body text: readable sans-serif, deliberately NOT monospace -- long-form
reading in monospace hurts readability, which stays a hard requirement
even with a more technical visual language elsewhere. */
.mw-body p,
.mw-body li,
.mw-body dd {
line-height: 1.7;
font-size: var( --edfm-fs-body );
}
.mw-body p {
margin: 0 0 1.1em 0;
max-width: 46em; /* comfortable reading measure, not the full column */
}
.mw-body ul,
.mw-body ol {
line-height: 1.7;
margin-bottom: 1.1em;
}
/* MW 1.46 wraps headings in a `.mw-heading2`/`.mw-heading3` div, so the
sibling that immediately follows is that wrapper, not the `h2`/`h3`
itself -- matching both forms since a page could still have a bare
heading in edge cases (e.g. content generated without the wrapper). */
.mw-heading2 + p, .mw-body h2 + p,
.mw-heading3 + p, .mw-body h3 + p,
.mw-heading2 + div, .mw-body h2 + div,
.mw-heading3 + div, .mw-body h3 + div {
margin-top: 0;
}
hr {
background-color: var( --edfm-border );
border-color: var( --edfm-border );
}

/* Quiet, discoverable section-edit controls (logged-in editors only --
MediaWiki only renders these for users who can edit). Keeping the
functionality/keyboard access intact while making sure they don't
compete visually with the heading they're attached to: low opacity at
rest, full opacity on hover/focus of the heading OR the control itself,
brackets hidden (the opacity+letter-spacing treatment already reads as
a distinct control without them). */
.mw-editsection {
margin-left: 1em;
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-utility ) !important;
font-weight: 700;
letter-spacing: 0.05em;
text-transform: uppercase;
opacity: 0.45;
transition: opacity 0.15s ease;
}
.mw-heading:hover .mw-editsection,
.mw-heading:focus-within .mw-editsection,
.mw-editsection:hover,
.mw-editsection:focus-within {
opacity: 1;
}
.mw-editsection a {
color: var( --edfm-text-dim );
}
.mw-editsection a:hover,
.mw-editsection a:focus-visible {
color: var( --edfm-cyan );
}
.mw-editsection-bracket {
display: none;
}
.mw-editsection-divider {
color: var( --edfm-text-dim );
margin: 0 0.3em;
}

/* ==========================================================================
8. LINKS
========================================================================== */
a { color: var( --edfm-link ); transition: color 0.1s ease; }
a:visited { color: var( --edfm-link-visited ); }
a:hover { color: var( --edfm-link-hover ); }
a.new, .new a { color: var( --edfm-link-new ); }
a.external { color: var( --edfm-link-external ); }
/* Core MediaWiki ships `.mw-parser-output a.external`/`a.extiw` (and their
:visited/:hover states) at higher specificity (two classes + a tag) than
a plain `a.external` rule (one class + a tag), so the line above never
actually wins for real article links on its own -- the same underlying
"core selector outranks a naive theme override" gotcha as the tab
:visited fix further down. Matching the same selector shape here (this
stylesheet loads after core skin styles) is what actually applies our
colour to external links in article content. */
.mw-parser-output a.external,
.mw-parser-output a.extiw {
color: var( --edfm-link-external );
}
.mw-parser-output a.external:visited,
.mw-parser-output a.extiw:visited {
color: var( --edfm-link-external-visited );
}
.mw-parser-output a.external:hover,
.mw-parser-output a.extiw:hover {
color: var( --edfm-link-external-hover );
}
.mw-footer a {
color: var( --edfm-link );
}
.mw-footer a:hover {
color: var( --edfm-link-hover );
}

/* ==========================================================================
1. GLOBAL LAYOUT -- centred workspace
========================================================================== */
/* THE fix for "enormous unused region on the right side of wide displays".
Vector legacy's core layout (skins.vector.styles.legacy/layouts/
screen.less) gives `.mw-body` (#content) a left margin to clear the
fixed-width sidebar and otherwise lets it run edge-to-edge to the
browser's right side with no max-width at all -- the first redesign
pass added a max-width but left the column pinned to the sidebar's left
edge, which is *why* it still read as "a column stuck on the left with
dead space on the right" rather than a composed layout.

Fix: instead of a fixed `margin-left: 11em`, compute how much space is
left over in the workspace (viewport minus the sidebar) once the
content has its max-width, and split that leftover evenly between the
left and right margins (via the --edfm-gutter token above) -- so the
article is centred *within the workspace to the right of the sidebar*,
not centred in the full viewport (which would ignore the sidebar and
look off-centre) and not pinned to its left edge either. On a screen
too narrow for sidebar + max-width content, --edfm-gutter naturally
evaluates to 0 and this degrades to the old "fill the workspace"
behaviour -- no separate narrow-screen override needed.

The header/tab bar's own float/absolute-position box (#mw-head) is left
at its native full width deliberately -- rewriting *that* mechanism is
a different, much higher-risk change (it took several rounds to get
right originally) -- but its *contents* (search box, personal tools,
namespace/view tabs) get their own right/left offsets pulled in by the
same --edfm-gutter below, so they still visually line up with the
centred column beneath them instead of hugging the browser edge. */
.mw-body,
#mw-data-after-content,
.mw-footer {
position: relative;
z-index: 2;
margin-left: var( --edfm-sidebar-clear );
margin-right: var( --edfm-gutter );
max-width: var( --edfm-content-max );
box-sizing: border-box;
}
/* Tables, code blocks, and preformatted content are still allowed to be
wider than a comfortable reading measure (technical data often needs
it) -- they scroll horizontally inside the capped column instead of
being force-shrunk or breaking the layout. Ordinary images/galleries
already respect the column via max-width:100% below. */
.mw-body table,
.mw-body pre,
.mw-body .mw-code {
max-width: 100%;
overflow-x: auto;
}
.mw-body table.wikitable,
.mw-body table.mw-datatable {
/* Keep real table layout so header cells and body cells share one column grid.
The earlier display:block + tbody display:table overflow hack made sortable
headers size independently from body columns, which visibly misaligned the
Engineer directory after portrait chips were added. */
display: table;
width: 100%;
table-layout: auto;
}
.mw-body table.wikitable th,
.mw-body table.wikitable td,
.mw-body table.mw-datatable th,
.mw-body table.mw-datatable td {
vertical-align: middle;
}
.mw-body img {
max-width: 100%;
height: auto;
}

/* ==========================================================================
4. ARTICLE MASTHEAD (eyebrow / title / deck)
========================================================================== */
/* Eyebrow line is authored as ordinary wikitext (see Template:Article
header) and, purely as a placement detail, a small script
(MediaWiki:Common.js) moves it directly above #firstHeading on load --
see the comment there for why that needs JS rather than CSS/a template
(the title is rendered by the skin before the article body in the DOM,
so nothing living inside the article body can appear earlier than it
without either moving it in the DOM or abandoning the real semantic H1).
If JS is unavailable the eyebrow still renders, just directly under the
title instead of above it.

The eyebrow/title/deck aren't wrapped in one literal bounding box (they
live at two different DOM depths -- eyebrow is a sibling of #firstHeading,
deck is inside the article body further down -- wrapping them in one
real container would need heavier JS than is justified here), so the
"designed masthead" read comes from a matching top rule above the
eyebrow and bottom rule below the deck, a small angular marker, and the
larger title/subtitle type scale, rather than one drawn box. */
.edfm-eyebrow {
display: flex;
align-items: center;
gap: 0.55em;
margin: 0 0 0.5em 0;
padding-top: 1.1em;
border-top: 1px solid var( --edfm-border );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-meta );
font-weight: 700;
letter-spacing: 0.12em;
text-transform: uppercase;
color: var( --edfm-text-dim );
}
.edfm-eyebrow::before {
content: '';
width: 8px;
height: 8px;
flex-shrink: 0;
background: var( --edfm-orange );
clip-path: polygon( 0 0, 100% 0, 100% 65%, 65% 100%, 0 100% );
}
.edfm-eyebrow .edfm-orange-mark {
color: var( --edfm-orange );
}
.edfm-deck {
color: var( --edfm-text-muted );
font-size: 1.1rem;
line-height: 1.55;
max-width: 42em;
margin: 0.5em 0 1.7em 0;
padding-bottom: 1.6em;
border-bottom: 1px solid var( --edfm-border );
}

/* ==========================================================================
1. SIDEBAR
========================================================================== */
#mw-panel {
background: transparent;
box-sizing: border-box;
width: var( --edfm-sidebar-width );
padding: 0 0.65rem 1.35rem 0.65rem;
border-right: 0;
box-shadow: none;
z-index: 3;
}
/* Logo anchors the sidebar visually. Do not draw a divider on or near
#p-logo: Vector legacy fixes the logo box at 155px high and the EDFM hex
mark reaches that edge, so any horizontal rule in this box cuts through
the lower point of the logo. Navigation spacing below provides the break. */
#p-logo {
box-sizing: border-box;
width: auto;
margin: 0 -0.65rem 1.25rem -0.65rem;
padding: 0.95rem 0.55rem 1.05rem 0.55rem;
border-bottom: 0 !important;
background: radial-gradient( circle at 50% 25%, rgba( 255, 138, 0, 0.08 ), transparent 58% );
}
/* Each nav group gets real breathing room from the one before it instead
of being packed together like a stock wiki sidebar. */

/* Sidebar Discord invite CTA: injected by MediaWiki:Common.js directly below
the logo and above the first generated Vector portlet, matching the compact
community-button placement shown in the reference screenshot. */
.edfm-discord-cta {
display: inline-flex;
align-items: center;
justify-content: center;
gap: 0.42rem;
box-sizing: border-box;
width: calc( 100% - 0.7rem );
min-height: 2rem;
margin: -0.35rem 0.35rem 1.1rem 0.35rem;
padding: 0.46rem 0.68rem;
border-radius: 4px;
background: #5865f2;
color: #fff !important;
font-size: 0.82rem;
font-weight: 700;
line-height: 1.1;
text-align: center;
text-decoration: none !important;
box-shadow: 0 2px 5px rgba( 0, 0, 0, 0.35 );
transition: background-color 120ms ease, box-shadow 120ms ease, transform 120ms ease;
}
.edfm-discord-cta:hover,
.edfm-discord-cta:focus {
background: #4752c4;
color: #fff !important;
text-decoration: none !important;
box-shadow: 0 3px 8px rgba( 0, 0, 0, 0.42 );
transform: translateY( -1px );
}
.edfm-discord-cta-icon {
display: inline-flex;
width: 1.12rem;
height: 1.12rem;
flex: 0 0 auto;
}
.edfm-discord-cta-icon svg {
display: block;
width: 100%;
height: 100%;
fill: currentColor;
}

#mw-panel .portal,
#mw-panel .vector-menu-portal {
box-sizing: border-box;
width: auto;
max-width: none;
margin-top: 1.45rem;
}
#mw-panel .portal:first-of-type,
#mw-panel .vector-menu-portal:first-of-type {
margin-top: 0;
}
#mw-panel .portal .body,
#mw-panel .portal ul,
#mw-panel .vector-menu-content,
#mw-panel .vector-menu-content-list {
box-sizing: border-box;
width: auto;
max-width: none;
margin-left: 0;
margin-right: 0;
padding-left: 0;
border-color: var( --edfm-border-soft );
}
#mw-panel .portal a {
color: var( --edfm-text-muted );
display: block;
font-size: var( --edfm-fs-sidebar );
line-height: 1.35;
padding: 0.42em 0.55em;
margin: 0.08em -0.35em;
border-left: 2px solid transparent;
border-radius: 2px;
}
#mw-panel .portal a:hover {
color: var( --edfm-cyan );
background: var( --edfm-surface-1 );
}
/* "You are here" -- MediaWiki's sidebar has no built-in current-page
indication; MediaWiki:Common.js adds the .edfm-nav-current class to the
matching list item by comparing hrefs to the current URL. Orange is
reserved for exactly this kind of "important navigation / selected
state" per the colour system, which is why the rest of the sidebar is
deliberately muted rather than orange throughout (an all-orange sidebar
would both fight this indicator and read as visually dominant). */
.edfm-nav-current > a {
color: var( --edfm-orange ) !important;
font-weight: 700;
border-left-color: var( --edfm-orange );
border-left-width: 3px;
background: var( --edfm-surface-2 );
box-shadow: inset 0 0 0 1px rgba( 255, 138, 0, 0.08 );
}
.vector-menu-heading {
color: var( --edfm-text-dim );
font-weight: 700;
font-family: var( --edfm-mono );
letter-spacing: 0.08em;
text-transform: uppercase;
font-size: var( --edfm-fs-utility );
border-left: 2px solid var( --edfm-orange );
padding-left: 0.5em;
margin-left: -0.5em;
margin-bottom: 0.4em;
}

/* ==========================================================================
3. TOP BAR -- two-tier chrome
========================================================================== */
/* Vector legacy's #mw-head naturally has ~2.5em of empty space above the
tabs row (core: `#left-navigation/#right-navigation { margin-top:2.5em }`),
originally reserved just for #p-personal to float in. Painting that same
box with a background gradient that stays transparent for that top
band and then switches to a surface colour for the tabs band creates a
real two-tier read -- "primary chrome" (personal tools/search, over the
page's own background) above "wiki authoring controls" (the tabs, on
their own distinct strip) below -- without touching #mw-head's own
position/width mechanics, which is the same fragile absolute-position
system the very first pass of this project had to debug carefully to
get the persistent sidebar working at all. Not worth re-risking that
for a background change. */
#mw-head {
background-image: linear-gradient(
to bottom,
transparent 0,
transparent 2.35em,
var( --edfm-surface-2 ) 2.35em,
var( --edfm-surface-2 ) 100%
);
border-bottom: 1px solid var( --edfm-border );
}
#mw-page-base {
background-color: var( --edfm-bg-deep );
background-image: none;
}
#mw-head-base {
background-color: var( --edfm-bg-deep );
/* Polish pass: thinned from 2px -- at 2px this competed visually with
the masthead's own orange marker/rule directly below it; a single
thinner accent line still reads as "site identity colour" without
the repetition. */
border-bottom: 1px solid var( --edfm-orange );
}
/* Personal tools (login/logout) and the search box are the "primary
chrome" tier -- pulled in by the same gutter used to centre the article,
so on wide screens they visually line up with the centred column
instead of hugging the browser edge, and given noticeably more visual
weight than the tabs below them. */
#p-personal {
right: calc( 0.75em + var( --edfm-gutter ) );
display: flex;
align-items: center;
gap: 0.75rem;
}
#p-personal ul {
display: flex;
align-items: center;
gap: 0.55rem;
}
#p-personal li {
margin-left: 0;
}
#p-personal a {
color: var( --edfm-text-muted );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-sidebar );
padding: 0.3em 0.2em;
}
#p-personal a:hover {
color: var( --edfm-orange );
}
.edfm-topbar-clocks {
display: inline-flex;
align-items: center;
gap: 0.5rem;
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-sidebar );
line-height: 1;
white-space: nowrap;
}
.edfm-topbar-clock {
display: inline-flex;
align-items: center;
gap: 0.3em;
padding: 0.3em 0.55em;
background: rgba( 66, 199, 217, 0.08 );
border: 1px solid var( --edfm-border-soft );
border-left: 2px solid var( --edfm-cyan );
color: var( --edfm-text );
}
.edfm-topbar-clock-label {
color: var( --edfm-text-dim );
font-size: var( --edfm-fs-utility );
letter-spacing: 0.08em;
text-transform: uppercase;
}
.edfm-topbar-clock time {
color: var( --edfm-cyan );
font-weight: 700;
}
.edfm-topbar-clock-local {
background: rgba( 255, 138, 0, 0.06 );
border-left-color: var( --edfm-orange );
}
.edfm-topbar-clock-local time {
color: var( --edfm-orange-bright );
}
#right-navigation {
margin-right: var( --edfm-gutter );
}
#left-navigation {
margin-left: var( --edfm-sidebar-clear );
}
/* Polish pass: core caps this at `width:20vw; max-width:20em`, which read
as cramped next to the rest of the (now larger-scale) interface --
given more room on desktop, still capped so it can't dominate the bar. */
.vector-search-box-inner {
width: 22vw;
max-width: 24em;
}
.vector-search-box-inner input,
#searchInput {
background-color: var( --edfm-surface-3 );
color: var( --edfm-text );
border: 1px solid var( --edfm-border );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-sidebar );
padding: 0.5em 0.7em;
transition: border-color 0.15s ease, box-shadow 0.15s ease;
}
#searchInput:focus {
border-color: var( --edfm-cyan );
box-shadow: 0 0 0 2px rgba( 66, 199, 217, 0.22 );
outline: none;
}
#searchInput::placeholder {
color: var( --edfm-text-dim );
}
/* Namespace tabs (Main Page / Discussion, left) and view tabs
(Read / Edit / View history, right) both use Vector legacy's
.vector-menu-tabs-legacy markup. Core skin CSS paints every tab `li`
with a gradient fading to white and forces the selected tab to pure
white -- neither is touched by recolouring the link text alone, which is
why these stayed light before this stylesheet covered the `li`
background too. Core also has an `a:visited` rule (higher specificity
than a plain `a` rule, since a pseudo-class counts the same as a class)
that reasserts a near-black "visited" colour meant for a white
background; since these tabs point at pages you've almost always
already visited, without an explicit `:visited` override here the text
goes dark-on-dark. This can't be caught by reading getComputedStyle() in
an automated check -- browsers deliberately report the *unvisited*
colour to JS for privacy reasons, so it only shows up on an actual
screen; verified with real rendered screenshots, including after
genuinely visiting the linked pages first.

These are the "wiki authoring controls" utility tier -- deliberately
smaller (--edfm-fs-utility) and quieter than personal-tools/search
above them, sitting on their own background strip (see #mw-head above).
Selected state stays orange (it's still real navigation, just
secondary); unselected rests dim so the *selected* tab is the one that
reads clearly. */
.vector-menu-tabs-legacy li {
background-image: none;
background-color: transparent;
}
.vector-menu-tabs-legacy li.selected {
background-image: none;
background-color: var( --edfm-surface-1 );
/* Polish pass: a small underline makes the selected tab unambiguous at
a glance instead of relying on the text colour change alone. */
box-shadow: inset 0 -2px 0 var( --edfm-orange );
}
.vector-menu-tabs-legacy li a,
.vector-menu-tabs-legacy li a:visited {
background-color: transparent;
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-utility );
letter-spacing: 0.03em;
text-transform: uppercase;
font-weight: 700;
}
.vector-menu-tabs-legacy li a:hover,
.vector-menu-tabs-legacy li a:visited:hover {
color: var( --edfm-text );
}
.vector-menu-tabs-legacy li.selected a,
.vector-menu-tabs-legacy li.selected a:visited {
color: var( --edfm-orange );
}
.vector-menu-tabs-legacy li.new a,
.vector-menu-tabs-legacy li.new a:visited {
color: var( --edfm-link-new );
}
/* "More" actions dropdown (#p-cactions) sits in the same tab row; same
:visited gotcha applies to its menu items. */
.vector-menu-dropdown .vector-menu-heading {
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
border-left: none;
padding-left: 8px;
margin-left: 0;
margin-bottom: 0;
text-transform: uppercase;
letter-spacing: 0.03em;
font-size: var( --edfm-fs-utility );
font-weight: 700;
}
.vector-menu-dropdown .vector-menu-heading:hover,
.vector-menu-dropdown .vector-menu-heading:focus {
color: var( --edfm-orange );
}
.vector-menu-dropdown .vector-menu-content {
background-color: var( --edfm-surface-3 );
border-color: var( --edfm-border );
}
.vector-menu-dropdown .vector-menu-content a,
.vector-menu-dropdown .vector-menu-content a:visited {
color: var( --edfm-text-muted );
font-size: var( --edfm-fs-sidebar );
}
.vector-menu-dropdown .vector-menu-content li.selected a,
.vector-menu-dropdown .vector-menu-content li.selected a:visited {
color: var( --edfm-orange );
}
.vector-menu-dropdown .vector-menu-content li:hover {
background-color: var( --edfm-surface-4 );
}

/* ==========================================================================
CONTENT / ARTICLE SURFACE
========================================================================== */
.mw-body,
.parsoid-body {
background-color: var( --edfm-surface-1 );
color: var( --edfm-text );
border-color: var( --edfm-border );
font-family: var( --edfm-sans );
}
.mw-body {
border-right: 1px solid var( --edfm-border );
}
#content {
background-color: var( --edfm-surface-1 );
}

/* Site notice chrome. The global disclaimer was moved to its dedicated
legal/disclaimer page, so an empty #siteNotice must not leave behind a
phantom divider at the top of the article surface. */
#siteNotice:empty {
display: none;
}
#siteNotice:not( :empty ) {
font-size: var( --edfm-fs-meta );
line-height: 1.5;
color: var( --edfm-text-dim );
font-style: normal;
padding-bottom: 0.7em;
margin-bottom: 1.4rem;
border-bottom: 1px solid var( --edfm-border-soft );
}
#siteNotice:not( :empty ) em, #siteNotice:not( :empty ) i {
color: var( --edfm-text-muted );
font-style: italic;
}
#siteNotice:not( :empty ) a {
color: var( --edfm-link-external );
}
#siteNotice a:hover {
color: var( --edfm-link-external-hover );
}

/* ==========================================================================
HOME PAGE DASHBOARD
========================================================================== */
.edfm-home-hero {
margin: 0.9rem 0 1.6rem;
padding: 1.35rem 1.55rem;
background:
linear-gradient( 135deg, rgba( 255, 138, 0, 0.16 ), transparent 34% ),
linear-gradient( 315deg, rgba( 66, 199, 217, 0.14 ), transparent 42% ),
var( --edfm-surface-2 );
border: 1px solid var( --edfm-border );
border-left: 4px solid var( --edfm-cyan );
clip-path: polygon( 0 0, calc( 100% - 12px ) 0, 100% 12px, 100% 100%, 0 100% );
}
.edfm-home-hero-kicker,
.edfm-home-card-kicker {
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-meta );
font-weight: 800;
letter-spacing: 0.1em;
text-transform: uppercase;
}
.edfm-home-hero-title {
margin-top: 0.25rem;
color: var( --edfm-text );
font-family: var( --edfm-mono );
font-size: clamp( 1.55rem, 1.1rem + 1.5vw, 2.2rem );
font-weight: 800;
line-height: 1.15;
}
.edfm-home-hero-text {
max-width: 52rem;
margin-top: 0.55rem;
color: var( --edfm-text-muted );
font-size: 1.05rem;
line-height: 1.55;
}
.edfm-home-grid {
display: grid;
gap: 1rem;
margin: 1.2rem 0 2rem;
}
.edfm-home-grid-four {
grid-template-columns: repeat( 4, minmax( 0, 1fr ) );
}
.edfm-home-grid-topics {
grid-template-columns: repeat( 2, minmax( 0, 1fr ) );
}
.edfm-home-grid-two {
grid-template-columns: repeat( 2, minmax( 0, 1fr ) );
}
.edfm-home-card {
background: var( --edfm-surface-2 );
border: 1px solid var( --edfm-border );
border-left: 3px solid var( --edfm-cyan );
padding: 1rem 1.1rem;
box-shadow: 0 12px 24px rgba( 0, 0, 0, 0.2 );
transition: transform 0.15s ease, border-color 0.15s ease, background-color 0.15s ease;
}
.edfm-home-card:hover {
transform: translateY( -2px );
background: var( --edfm-surface-3 );
border-left-color: var( --edfm-orange );
}
.edfm-home-card-primary {
border-left-color: var( --edfm-orange );
}
.edfm-home-card-warning {
border-left-color: var( --edfm-text-dim );
}
.edfm-home-card-title,
.edfm-home-card-title a {
margin-top: 0.35rem;
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
font-size: 1.05rem;
font-weight: 800;
line-height: 1.3;
text-decoration: none;
}
.edfm-home-card-title a:hover {
color: var( --edfm-orange-bright ) !important;
}
.edfm-home-card-text,
.edfm-home-link-list {
margin-top: 0.65rem;
color: var( --edfm-text-muted );
line-height: 1.6;
}
.edfm-home-link-list a {
font-weight: 600;
}
@media ( max-width: 1100px ) {
.edfm-home-grid-four {
grid-template-columns: repeat( 2, minmax( 0, 1fr ) );
}
}
@media ( max-width: 760px ) {
.edfm-home-grid-four,
.edfm-home-grid-topics,
.edfm-home-grid-two {
grid-template-columns: 1fr;
}
}

/* ==========================================================================
HOME PAGE NEWS MODULE
========================================================================== */
.edfm-home-news {
margin: 1.8rem 0 2.2rem;
}
.edfm-news-feature-grid {
display: grid;
grid-template-columns: repeat( 3, minmax( 0, 1fr ) );
gap: 1rem;
margin-bottom: 1rem;
}
.edfm-news-card,
.edfm-news-list {
background: var( --edfm-surface-2 );
border: 1px solid var( --edfm-border );
box-shadow: 0 14px 26px rgba( 0, 0, 0, 0.22 );
overflow: hidden;
}
.edfm-news-card {
display: flex;
flex-direction: column;
min-height: 100%;
transition: transform 0.15s ease, border-color 0.15s ease, background-color 0.15s ease;
}
.edfm-news-card:hover {
transform: translateY( -2px );
border-color: rgba( 255, 138, 0, 0.48 );
background: var( --edfm-surface-3 );
}
.edfm-news-card-art {
display: flex;
align-items: flex-end;
min-height: 7rem;
padding: 0.8rem 1rem;
box-sizing: border-box;
background:
linear-gradient( 135deg, rgba( 255, 138, 0, 0.28 ), transparent 42% ),
linear-gradient( 315deg, rgba( 66, 199, 217, 0.2 ), transparent 48% ),
linear-gradient( 180deg, var( --edfm-surface-4 ), var( --edfm-surface-1 ) );
border-bottom: 1px solid var( --edfm-border );
color: rgba( 237, 240, 242, 0.72 );
font-family: var( --edfm-mono );
font-size: 0.8rem;
font-weight: 800;
letter-spacing: 0.16em;
text-transform: uppercase;
}
.edfm-news-card-primary .edfm-news-card-art {
background:
linear-gradient( 135deg, rgba( 255, 138, 0, 0.38 ), transparent 46% ),
linear-gradient( 315deg, rgba( 79, 159, 232, 0.26 ), transparent 52% ),
var( --edfm-surface-4 );
}
.edfm-news-card-body {
padding: 1rem 1.15rem 1.15rem;
}
.edfm-news-meta {
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-meta );
letter-spacing: 0.04em;
text-transform: uppercase;
margin-bottom: 0.35rem;
}
.edfm-news-title,
.edfm-news-title a {
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
font-size: 1.1rem;
font-weight: 800;
line-height: 1.25;
text-decoration: none;
}
.edfm-news-title a:hover {
color: var( --edfm-orange-bright ) !important;
}
.edfm-news-summary {
color: var( --edfm-text-muted );
line-height: 1.55;
margin-top: 0.65rem;
}
.edfm-news-list {
padding: 1.1rem 1.25rem 1.2rem;
border-left: 4px solid var( --edfm-orange );
}
.edfm-news-list-heading {
color: var( --edfm-text );
font-family: var( --edfm-mono );
font-size: 1.05rem;
font-weight: 800;
letter-spacing: 0.04em;
text-transform: uppercase;
margin-bottom: 0.75rem;
}
.edfm-news-list ul {
margin: 0;
}
.edfm-news-list li {
margin-bottom: 0.55rem;
color: var( --edfm-text-muted );
}
.edfm-news-more {
margin-top: 0.9rem;
padding-top: 0.85rem;
border-top: 1px solid var( --edfm-border-soft );
text-align: right;
font-family: var( --edfm-mono );
font-weight: 800;
letter-spacing: 0.03em;
text-transform: uppercase;
}
@media ( max-width: 900px ) {
.edfm-news-feature-grid {
grid-template-columns: 1fr;
}
}

/* ==========================================================================
10. JUMP NAVIGATION (table of contents)
========================================================================== */
/* A compact navigation strip/tile-grid rather than a traditional TOC box
of small text links -- real MediaWiki anchors/markup untouched, this is
all presentation. "Contents" is kept in the DOM for screen readers/
no-JS/no-CSS fallback (more standard wording there anyway) and visually
replaced with "Jump to" via ::before on the wrapper, with the real
heading text hidden via font-size rather than display:none so it
remains in the accessibility tree. */
#toc, .toc {
display: block;
width: 100%;
box-sizing: border-box;
background: none;
border: none;
color: var( --edfm-text );
padding: 0;
margin: 1.8rem 0;
}
.toctitle {
position: relative;
margin-bottom: 0.7em;
}
.toctitle::before {
content: 'Jump to';
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-meta );
font-weight: 700;
letter-spacing: 0.12em;
text-transform: uppercase;
color: var( --edfm-orange );
}
/* Core ships `.toc h2 { font-size: 100%; ... }` (mediawiki.skinning/toc/
screen.less) at the exact same specificity (one class + one tag) as a
plain `.toctitle h2` rule -- same "tie that doesn't resolve the way
naive source order would suggest" gotcha documented elsewhere in this
file. #toc's own ID makes this one unambiguous instead of relying on
cascade order. */
#toc .toctitle h2,
.toc .toctitle h2 {
font-size: 0 !important;
line-height: 0;
margin: 0;
border: none;
padding: 0;
display: inline;
}
.toctitle h2::before,
.toctitle h2::after {
content: none;
}
.toctogglelabel::before {
color: var( --edfm-text-dim );
}
/* Desktop: a real grid of clickable tiles (3 columns suits this site's
typical 5-8 top-level sections well: commonly 2-3 rows) instead of one
long line of small text. Each tile has its own surface, a visible
boundary via the accent rail (not a full border -- see "stop using a
border around everything"), and an obvious hover state. */
.toc > ul {
display: grid;
grid-template-columns: repeat( 4, 1fr );
gap: 0.45rem;
list-style: none;
margin: 0;
padding: 0;
}
.toc li {
margin: 0;
}
/* 2026-08-08 density pass: reverted to side-by-side number/label (from the
earlier "stacked number-above-label" polish pass) specifically to cut
per-tile height -- with 12 sections on articles like The Dweller, the
stacked layout meant the jump nav alone filled most of the first
viewport. Row layout plus tighter padding/font-size gets noticeably
more sections above the fold without dropping the numbering or shrinking
tap targets below a comfortable size -- see the dedicated mobile padding
bump further down for keeping touch targets safe on small screens
specifically. Whole tile stays one real <a>, so it's still a single
click/focus target and keyboard tab stop either way. */
.toc a {
display: flex;
flex-direction: row;
align-items: center;
gap: 0.5em;
height: 100%;
box-sizing: border-box;
padding: 0.5em 0.75em 0.5em 0.7em;
background: var( --edfm-surface-3 );
/* Left accent rail: matches the orange section numbers and gives each
jump tile a stronger EDFM navigation affordance without boxing the
entire card. */
border-left: 4px solid var( --edfm-orange );
box-shadow: inset 1px 0 0 rgba( 255, 162, 26, 0.35 );
color: var( --edfm-text-muted );
text-decoration: none;
transition: background-color 0.15s ease, border-color 0.15s ease, box-shadow 0.15s ease, color 0.15s ease, transform 0.15s ease;
}
.toc a:hover {
background: var( --edfm-surface-4 );
border-left-color: var( --edfm-cyan );
box-shadow: inset 1px 0 0 rgba( 66, 199, 217, 0.45 );
color: var( --edfm-text );
transform: translateY( -1px );
}
/* Nested sub-levels (rare on this site so far) drop back to a plain
indented block list inside their parent tile's grid cell rather than
trying to stay gridded themselves. */
.toc ul ul {
grid-column: unset;
list-style: none;
margin: 0.3em 0 0 1.2em;
padding: 0;
display: block;
}
.toc ul ul a {
flex-direction: row;
align-items: center;
background: none;
border-left-width: 1px;
padding: 0.3em 0.6em;
}
.toc ul ul .tocnumber {
font-size: 0.85em;
}
.toc ul ul .toctext {
font-size: 0.85em;
}
.tocnumber {
color: var( --edfm-orange );
font-family: var( --edfm-mono );
font-weight: 700;
font-size: 1.05rem;
line-height: 1;
}
.toctext {
color: inherit;
font-size: 0.85rem;
line-height: 1.3;
}
/* 2026-08-08: rebalanced for the 4-column desktop default above -- was
>1150px = 3 cols -> <=1150px = 2 cols -> <=560px = 1 col. A page with
12 sections (e.g. The Dweller) now gets 3 rows at desktop width instead
of 4, so a new <=860px step was added rather than dropping straight
from 3 to 2 columns at 1150px, which left the same "Star systems,
navigation and exploration"-style long labels cramped in the 1024px
range this breakpoint set was originally tuned for. Order stays widest
condition first, narrowest last, so cascade order matches the max-width
overlap correctly at every width. */
@media ( max-width: 1150px ) {
.toc > ul {
grid-template-columns: repeat( 3, 1fr );
}
}
@media ( max-width: 860px ) {
.toc > ul {
grid-template-columns: repeat( 2, 1fr );
}
}
@media ( max-width: 560px ) {
.toc > ul {
grid-template-columns: 1fr;
}
/* Single-column tiles are already full-width here, so there's no
density pressure left -- restore closer to the pre-2026-08-08
padding instead of the tighter desktop value, keeping tap targets
comfortable rather than compacting mobile just because desktop
compacted. */
.toc a {
padding: 0.7em 0.95em;
}
}

/* ==========================================================================
6. PANELS / CALLOUTS, and 11. ARTICLE METADATA / STATUS MODULE
========================================================================== */
/* Deliberately NOT defined here. .edfm-box / .edfm-panel* / .edfm-status* /
.edfm-inline-flag / .edfm-related* are used exclusively by the
editorial templates (see Template:Article status, Template:Draft
warning, Template:Related articles, etc.), which already load
Template:EDFM style/styles.css themselves via <templatestyles>.
Defining the same class names in both this file and that one would
leave their relative precedence dependent on unclear/unstable ordering
between a ResourceLoader "site" stylesheet and a TemplateStyles-injected
<style> tag -- rather than rely on that, there is exactly one definition
of each, living in Template:EDFM style/styles.css. That file freely uses
the --edfm-* custom properties defined above; custom properties resolve
through the DOM regardless of which stylesheet declared vs references
them, so this split costs nothing. */

/* ==========================================================================
7. TABLES (wikitables, and Special: pages' tables)
========================================================================== */
table.wikitable,
table.mw-datatable {
background-color: var( --edfm-surface-2 );
color: var( --edfm-text );
border-color: var( --edfm-border );
font-size: var( --edfm-fs-body );
}
table.wikitable > tr > th,
table.wikitable > * > tr > th {
background-color: var( --edfm-surface-3 );
color: var( --edfm-text );
border-color: var( --edfm-border );
font-family: var( --edfm-mono );
letter-spacing: 0.03em;
text-transform: uppercase;
font-size: var( --edfm-fs-meta );
text-align: left;
padding: 0.6em 0.8em;
}
table.wikitable > tr > td,
table.wikitable > * > tr > td {
border-color: var( --edfm-border-soft );
padding: 0.6em 0.8em;
}
/* Subtle alternating row treatment -- helps scanning wide/dense reference
tables without turning them into cards. */
table.wikitable > tbody > tr:nth-child( even ),
table.wikitable > * > tr:nth-child( even ) {
background-color: var( --edfm-surface-1 );
}

/* ==========================================================================
15. FOOTER
========================================================================== */
/* A real branded footer: a small wordmark line (pure CSS generated
content -- decorative branding only, redundant with the sidebar logo
already visible, so nothing load-bearing depends on it being
selectable), a top rule with more separation from the article above it,
and MediaWiki's real info/places/icon links laid out on a clean grid
with the badges aligned as a group rather than floating alone. */
.mw-footer {
margin-left: var( --edfm-sidebar-clear );
margin-right: var( --edfm-gutter );
margin-top: 2.5rem;
padding-top: 1.6rem;
border-top: 1px solid var( --edfm-border );
display: grid;
grid-template-columns: 1fr auto;
grid-template-areas: "brand brand" "info icons" "places icons";
align-items: center;
column-gap: 2em;
row-gap: 0.4rem;
}
.mw-footer::before {
grid-area: brand;
content: 'EDFM // Elite Dangerous Field Manual';
font-family: var( --edfm-mono );
font-size: 0.85rem;
font-weight: 700;
letter-spacing: 0.06em;
text-transform: uppercase;
color: var( --edfm-text-muted );
margin-bottom: 0.5rem;
}
.mw-footer,
.mw-footer li,
#footer-info,
#footer-info li {
color: var( --edfm-text-dim );
border-color: var( --edfm-border-soft );
font-size: var( --edfm-fs-meta );
}
#footer-info {
grid-area: info;
margin: 0;
line-height: 1.6;
}
#footer-places {
grid-area: places;
margin: 0;
}
/* Same "small uppercase label" treatment used for tags/meta text
elsewhere, so these read as deliberate EDFM navigation rather than
default MediaWiki footer links. */
#footer-places li {
display: inline-block;
margin-right: 1.4em;
}
#footer-places a {
font-family: var( --edfm-mono );
font-weight: 700;
letter-spacing: 0.03em;
text-transform: uppercase;
font-size: 0.78rem;
}
/* A left rule ties the badges to the rest of the footer instead of
letting them read as detached/floating in their own space. */
#footer-icons {
grid-area: icons;
align-self: center;
display: flex;
gap: 0.75em;
margin: 0;
padding-left: 1.6em;
border-left: 1px solid var( --edfm-border-soft );
}
#footer-icons img {
background: var( --edfm-text );
border-radius: 2px;
}
@media ( max-width: 640px ) {
.mw-footer {
grid-template-columns: 1fr;
grid-template-areas: "brand" "info" "places" "icons";
}
#footer-icons {
margin-top: 0.7em;
padding-left: 0;
border-left: none;
border-top: 1px solid var( --edfm-border-soft );
padding-top: 0.7em;
}
}

/* ==========================================================================
MISC MediaWiki UI chrome that ships with light backgrounds by default
========================================================================== */
.catlinks {
background: none !important;
border: none !important;
border-top: 1px solid var( --edfm-border-soft ) !important;
color: var( --edfm-text-dim );
font-size: var( --edfm-fs-meta );
padding: 0.9em 0 0 0 !important;
margin-top: 1.8rem !important;
}
div.thumbinner {
background-color: var( --edfm-surface-2 );
border-color: var( --edfm-border );
}
.thumbimage {
background-color: var( --edfm-surface-1 );
border-color: var( --edfm-border );
}

/* Code / preformatted text (syntaxhighlight uses its own Pygments theme,
set via $wgPygmentsStyle in LocalSettings.php; this covers plain
<pre>/<code> that isn't Pygments-highlighted). */
pre, code, .mw-code {
background-color: var( --edfm-surface-2 );
color: var( --edfm-text );
border-color: var( --edfm-border );
font-family: var( --edfm-mono );
}

/* ==========================================================================
GENERIC INFOBOX -- see Template:Infobox
========================================================================== */
.edfm-infobox {
float: right;
clear: right;
width: 310px;
margin: 0 0 1.2em 1.2em;
border: 1px solid var( --edfm-border );
border-top: 2px solid var( --edfm-orange );
background: var( --edfm-surface-2 );
color: var( --edfm-text );
font-size: 0.92rem;
}
.edfm-infobox-title {
background: var( --edfm-orange );
color: var( --edfm-bg-deep );
font-weight: 700;
font-family: var( --edfm-mono );
letter-spacing: 0.04em;
text-transform: uppercase;
text-align: center;
padding: 0.5em 0.6em;
clip-path: polygon( 0 0, calc( 100% - 14px ) 0, 100% 14px, 100% 100%, 0 100% );
}
.edfm-infobox-image {
text-align: center;
padding: 0.6em;
border-bottom: 1px solid var( --edfm-border );
}
.edfm-infobox-image-placeholder {
display: flex;
align-items: center;
justify-content: center;
height: 160px;
border: 1px dashed var( --edfm-border );
background: var( --edfm-surface-1 );
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-utility );
text-transform: uppercase;
letter-spacing: 0.06em;
text-align: center;
padding: 0.5em;
}
/* Optional section label (Template:Infobox's |groupN=) splitting a long
infobox into scannable groups, e.g. Engineer infoboxes into "ENGINEER"
and "ACCESS" (2026-08-08, part of the Engineer article layout pass). A
shaded band with a bottom rule rather than a full boxed sub-header --
consistent with .edfm-infobox-row's own bottom-rule-only separator, not
a new visual language. */
.edfm-infobox-group {
background: var( --edfm-surface-3 );
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
font-weight: 700;
font-size: var( --edfm-fs-utility );
letter-spacing: 0.08em;
text-transform: uppercase;
padding: 0.35em 0.7em;
border-bottom: 1px solid var( --edfm-border );
}
.edfm-infobox-row {
display: flex;
border-bottom: 1px solid var( --edfm-border-soft );
padding: 0.45em 0.7em;
}
.edfm-infobox-row:last-child {
border-bottom: none;
}
.edfm-infobox-label {
font-weight: 700;
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-meta );
width: 40%;
flex-shrink: 0;
color: var( --edfm-cyan );
}
.edfm-infobox-value {
width: 60%;
}
@media ( max-width: 640px ) {
.edfm-infobox {
float: none;
width: auto;
margin: 1em 0;
}
}

/* ==========================================================================
14. MOBILE
========================================================================== */
/* Vector legacy has NO built-in responsive breakpoint at all (unlike
Vector 2022) -- its entire header region (#mw-head, tabs, search,
personal tools/login) is built with absolute positioning and floats
that all assume a fixed-width sidebar reserving 10-11em on the left,
AND the page's actual DOM order is content-then-navigation-then-footer
(the absolute positioning was doing double duty: both moving the header
visually to the top AND compensating for that DOM order). Simply
removing the positioning stacks things in DOM order, which reads oddly
on a phone (article text, then the nav/sidebar, then the footer).
Confirmed the actual DOM structure directly (not guessed): <body>'s
real children are #mw-page-base, #mw-head-base, #content,
#mw-navigation (which itself contains #mw-head then #mw-panel, already
in the right relative order), #footer. Since all four major regions are
direct children of <body>, flexbox `order` on <body> can reorder them
properly without needing to touch the DOM itself.
Result: header/search/tabs, then sidebar nav, then content, then
footer -- a plain stacked mobile layout, not a collapsible hamburger
menu, but a correct and readable order. */
@media ( max-width: 800px ) {
body::before {
display: none;
}
body {
display: flex;
flex-direction: column;
}
/* #mw-head-base ships with `margin-top: -5em` in Vector legacy's own
CSS -- a trick to sit it behind the absolutely-positioned header.
Now that the header is a normal flex sibling, that negative margin
drags everything after it upward. Neutralize both decorative
strips. */
#mw-page-base,
#mw-head-base {
order: 0;
height: 0;
margin: 0;
min-height: 0;
}
#mw-navigation {
order: 1;
}
#content {
order: 2;
}
.mw-footer {
order: 3;
}

#mw-head {
position: static;
width: auto;
background-image: none;
background-color: var( --edfm-surface-2 );
}
#left-navigation,
#right-navigation {
float: none;
margin: 0 !important;
width: auto;
clear: both;
}
#left-navigation {
margin-top: 0 !important;
}
/* Core Vector legacy floats each tab/dropdown portlet
(.vector-menu-tabs-legacy for Page/Discussion and Read/View
source/View history, .vector-menu-dropdown for the More menu) AND
floats every <li> inside their <ul>, with no wrapping at all -- at
narrow widths the labels just overflow and overlap each other
(confirmed with a real screenshot: "View source" and "More"
overlapped instead of wrapping to a new line). Switching the
portlets to inline-block and their tab lists to flex-wrap lets them
reflow onto as many rows as needed instead. */
#left-navigation .vector-menu-tabs-legacy,
#right-navigation .vector-menu-tabs-legacy,
#right-navigation .vector-menu-dropdown {
float: none;
display: inline-block;
vertical-align: top;
}
.vector-menu-tabs-legacy ul {
float: none;
display: flex;
flex-wrap: wrap;
}
.vector-menu-tabs-legacy li {
float: none;
}
#p-personal {
position: static;
text-align: right;
padding: 0.5em 1em;
margin: 0;
right: auto !important;
top: auto;
}
#p-personal ul {
padding-left: 0;
}
.vector-search-box {
float: none;
margin: 0.5em 1em;
display: block;
}
.vector-search-box-inner {
width: auto;
max-width: none;
}
#mw-panel {
position: static;
width: auto;
padding: 0.5em 1em;
float: none;
background: var( --edfm-bg-deep );
border-top: 1px solid var( --edfm-border );
border-bottom: 1px solid var( --edfm-border );
}
.mw-body,
#mw-data-after-content,
.mw-footer {
margin-left: 0 !important;
margin-right: 0 !important;
max-width: none;
}
.mw-body {
margin-top: 0;
border-width: 0;
padding: 1em;
}
.edfm-status-details {
grid-template-columns: 1fr;
}
/* .toc > ul column count is NOT overridden here -- the dedicated
1150px/560px breakpoints above already cover every width down to
the smallest phones; duplicating a rule here previously fought
those (same specificity, this position in the cascade would have
won and wrongly forced 1 column as low as 561px). */
#firstHeading {
font-size: 1.6rem;
}
.mw-body h2 {
margin-top: 2.25rem;
}
.edfm-eyebrow {
padding-top: 0.9em;
}
}
/* ==========================================================================
16. OOUI DIALOGS -- VisualEditor's save dialog, and any other OOUI
dialog (delete/move/protect confirmations, special-page dialogs).
These render via OOUI's own bundled WikimediaUI theme stylesheet,
entirely outside the .edfm-* component system this file otherwise
covers, so without this they show up starkly white against the rest of
the dark-themed site regardless of any variable/token used elsewhere in
this file. !important is justified the same way as the h1-h6 fix above:
OOUI's own stylesheet loads with equal-or-higher effective specificity,
and this is a correctness/contrast fix, not decoration.
========================================================================== */
.oo-ui-window-frame {
background: var( --edfm-surface-2 ) !important;
color: var( --edfm-text ) !important;
}
.oo-ui-processDialog {
background: rgba( 7, 9, 11, 0.75 ) !important;
}
.oo-ui-processDialog-navigation,
.oo-ui-window-head,
.oo-ui-window-foot {
background: var( --edfm-surface-3 ) !important;
border-color: var( --edfm-border ) !important;
}
.oo-ui-processDialog-title,
.oo-ui-labelElement-label,
.oo-ui-fieldLayout-header,
.oo-ui-fieldLayout .oo-ui-labelElement-label {
color: var( --edfm-text ) !important;
}
.oo-ui-inputWidget-input {
background: var( --edfm-surface-1 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}
.ve-ui-mwSaveDialog-options,
.oo-ui-panelLayout,
.oo-ui-window-body {
background: var( --edfm-surface-2 ) !important;
color: var( --edfm-text ) !important;
}
.oo-ui-popupWidget-popup {
background: var( --edfm-surface-2 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}
.oo-ui-buttonElement:not( .oo-ui-flaggedElement-primary ) > .oo-ui-buttonElement-button {
background: var( --edfm-surface-4 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}
/* ==========================================================================
17. OOUI TOOLBAR -- VisualEditor's persistent editing toolbar and its
dropdown menus (Cite, Insert, paragraph style, etc.), and the equivalent
toolbar/popups used when editing a single section. Same root cause as
16. OOUI DIALOGS above (OOUI's own bundled theme, not touched by
anything else in this file), found separately because it's a different
set of OOUI classes (toolbar chrome, not dialog chrome). Icons are not
overridden here and don't need to be -- they're currentColor-based, so
they pick up the text colour set below automatically.
========================================================================== */
.oo-ui-toolbar-bar,
.oo-ui-toolGroup-tools,
.oo-ui-popupToolGroup-tools {
background: var( --edfm-surface-3 ) !important;
border-color: var( --edfm-border ) !important;
}
.oo-ui-tool-title,
.oo-ui-tool-link,
.oo-ui-toolGroup-tools .oo-ui-optionWidget,
.oo-ui-menuOptionWidget,
.oo-ui-labelElement-label {
color: var( --edfm-text ) !important;
}
.oo-ui-optionWidget.oo-ui-optionWidget-selected,
.oo-ui-optionWidget:hover,
.oo-ui-tool:hover .oo-ui-tool-link {
background: var( --edfm-surface-4 ) !important;
}
/* ==========================================================================
18. OOUI GENERIC MENUS -- .oo-ui-menuSelectWidget is OOUI's general
dropdown/autocomplete menu class (paragraph-style picker, citation-type
picker, link/media search suggestions, etc.) -- a different class from
the toolbar-specific popups in 17. above, confirmed separately via
computed-style inspection to default to the same white OOUI theme
background.
========================================================================== */
.oo-ui-menuSelectWidget {
background: var( --edfm-surface-3 ) !important;
border-color: var( --edfm-border ) !important;
}
.oo-ui-menuOptionWidget {
color: var( --edfm-text ) !important;
}
.oo-ui-menuOptionWidget.oo-ui-optionWidget-highlighted,
.oo-ui-menuOptionWidget:hover {
background: var( --edfm-surface-4 ) !important;
}
/* ==========================================================================
19. OOUI ICONS -- the toolbar/menu icons themselves (Bold, link, list,
Cite, undo/redo, etc.) are rendered as background-image SVGs with a
colour baked into the SVG markup, not currentColor-based masks -- so
16-18 above (which only recolour backgrounds/text) left them dark and
low-contrast against the now-dark surfaces. OOUI ships its own fix for
exactly this, gated behind a narrow accessibility media query
(forced-colors + prefers-color-scheme: dark) that doesn't apply to this
site's own always-on dark theme -- reusing that exact technique
unconditionally rather than inventing a different one. `:not(
.oo-ui-image-invert )` is OOUI's own exclusion for icons already meant
to render light (e.g. on the orange primary-button background) --
inverting those too would flip them back to dark.
========================================================================== */
.oo-ui-iconElement-icon:not( .oo-ui-image-invert ),
.oo-ui-indicatorElement-indicator:not( .oo-ui-image-invert ) {
filter: invert( 1 ) hue-rotate( 180deg );
}
/* ==========================================================================
20. EDIT SOURCE FORM -- MediaWiki core + WikiEditor + CodeMirror

The source editor is not covered by the article/component selectors above:
`action=edit` loads core edit-form CSS, WikiEditor chrome, and sometimes
CodeMirror with their own light neutral surfaces. Force the same EDFM dark
surface stack here so the source page no longer flashes as a white island.
========================================================================== */
.mw-editform,
#editform,
#toolbar,
.editOptions,
.mw-editTools,
.mw-summary-preview,
.mw-datatable,
.wikiEditor-ui,
.wikiEditor-ui-view,
.wikiEditor-ui-text,
.wikiEditor-ui-toolbar,
.wikiEditor-ui-top,
.wikiEditor-ui-controls,
.wikiEditor-ui-tabs,
.wikiEditor-ui-buttons,
.CodeMirror,
.CodeMirror-scroll {
background: var( --edfm-surface-1 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}
.mw-editform textarea,
#wpTextbox1,
#wpSummary,
#wpSummaryWidget input,
#editform input[type='text'],
#editform input[type='search'],
#editform textarea,
.wikiEditor-ui-text textarea,
.CodeMirror-code,
.CodeMirror-lines,
.CodeMirror pre {
background: var( --edfm-bg-deep ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
caret-color: var( --edfm-orange-bright );
}
.wikiEditor-ui-toolbar,
.wikiEditor-ui-toolbar .group,
.wikiEditor-ui-toolbar .tabs,
.wikiEditor-ui-toolbar .page,
.wikiEditor-ui-toolbar .sections,
.wikiEditor-ui-toolbar .section,
.wikiEditor-ui-toolbar .options,
.wikiEditor-ui-toolbar .booklet,
.wikiEditor-ui-toolbar .pages,
.CodeMirror-gutters {
background: var( --edfm-surface-2 ) !important;
color: var( --edfm-text-muted ) !important;
border-color: var( --edfm-border ) !important;
}
.wikiEditor-ui-toolbar a,
.wikiEditor-ui-toolbar .label,
.wikiEditor-ui-toolbar .tab a,
.mw-editTools a,
.editOptions label,
.mw-editform label,
.CodeMirror-linenumber {
color: var( --edfm-text ) !important;
}
.wikiEditor-ui-toolbar .tab a:hover,
.wikiEditor-ui-toolbar .tool-button:hover,
.wikiEditor-ui-toolbar .tool-select:hover,
.wikiEditor-ui-toolbar .page-table th,
.wikiEditor-ui-toolbar .page-table td,
.CodeMirror-activeline-background {
background: var( --edfm-surface-3 ) !important;
color: var( --edfm-text ) !important;
}
.wikiEditor-ui-toolbar .tab.current a,
.wikiEditor-ui-toolbar .section-main,
.CodeMirror-selected {
background: var( --edfm-surface-4 ) !important;
}
.CodeMirror-cursor {
border-left-color: var( --edfm-orange-bright ) !important;
}
.CodeMirror-matchingbracket {
color: var( --edfm-orange-bright ) !important;
}

/* ==========================================================================
21. FILE PAGE CHROME -- #filetoc (the File / File history / File usage /
Metadata nav on File: description pages) is defined in MediaWiki core's
mediawiki.action.view.filepage.less, entirely separate from both the
.edfm-* system and the OOUI fixes in 16-19 above -- a different
subsystem again, only loaded on File: pages, which is why it was never
touched by anything else in this file. Link colour inside it already
correctly inherits the site's normal link blue; only the light neutral
background/border needed overriding.
========================================================================== */
#filetoc {
background: var( --edfm-surface-2 ) !important;
border-color: var( --edfm-border ) !important;
}
/* ==========================================================================
22. FILE PAGE: METADATA TABLE + MEDIA VIEWER BUTTON -- #mw_metadata is
the EXIF-style metadata table (separate from the File history table
above -- that one already carries the .wikitable class and picked up
dark styling from 7. TABLES automatically; this one doesn't have that
class, so it never matched). The "Open in Media Viewer" button is a
Codex component (MultimediaViewer extension) -- a third distinct
styling subsystem from OOUI and MediaWiki core skinning, again never
touched by anything else in this file.
========================================================================== */
#mw_metadata th,
#mw_metadata td {
background: var( --edfm-surface-2 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}
.mw-mmv-view-expanded.cdx-button {
background: var( --edfm-surface-4 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}

/* ===========================================================================
23. RUNE-WIKI-INSPIRED MOBILE APP SHELL
=========================================================================== */
/* Inspired by RuneScape.wiki's mobile ergonomics -- persistent top app bar,
large touch targets, off-canvas navigation, search-forward layout, and
single-column readable article flow -- while preserving EDFM's dark field
manual identity and not copying RuneScape.wiki assets/CSS.
The close button is injected into #mw-panel by Common.js, so it must be
explicitly hidden by default; otherwise a tiny native white button appears
in the desktop sidebar's top-left corner. */
.edfm-mobile-appbar,
.edfm-mobile-scrim,
.edfm-mobile-close-button {
display: none;
}
@media ( max-width: 800px ) {
html {
-webkit-text-size-adjust: 100%;
}
body {
background: var( --edfm-bg-page );
overflow-x: hidden;
}
body.edfm-mobile-menu-open {
overflow: hidden;
}
.edfm-mobile-appbar {
display: grid;
grid-template-columns: 48px 1fr 48px;
align-items: center;
position: sticky;
top: 0;
z-index: 1200;
min-height: 56px;
padding: 0 0.35rem;
background:
linear-gradient( 90deg, rgba( 255, 138, 0, 0.18 ), transparent 38% ),
var( --edfm-surface-2 );
border-bottom: 1px solid var( --edfm-border );
box-shadow: 0 10px 24px rgba( 0, 0, 0, 0.35 );
}
.edfm-mobile-brand {
min-width: 0;
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
font-weight: 800;
letter-spacing: 0.05em;
text-transform: uppercase;
text-decoration: none;
white-space: nowrap;
overflow: hidden;
text-overflow: ellipsis;
}
.edfm-mobile-brand::before {
content: 'EDFM // ';
color: var( --edfm-orange );
}
.edfm-mobile-menu-button,
.edfm-mobile-search-button,
.edfm-mobile-close-button {
appearance: none;
-webkit-appearance: none;
display: inline-flex;
align-items: center;
justify-content: center;
min-width: 44px;
min-height: 44px;
margin: 0;
border: 0;
border-radius: 0;
background: transparent;
color: var( --edfm-text );
font: 700 1.5rem/1 var( --edfm-mono );
cursor: pointer;
}
.edfm-mobile-menu-button:focus-visible,
.edfm-mobile-search-button:focus-visible,
.edfm-mobile-close-button:focus-visible {
outline: 2px solid var( --edfm-cyan );
outline-offset: -4px;
}
.edfm-mobile-menu-button::before {
content: '☰';
color: var( --edfm-orange );
}
.edfm-mobile-search-button::before {
content: '⌕';
font-size: 1.85rem;
color: var( --edfm-cyan );
}
.edfm-mobile-close-button::before {
content: '×';
color: var( --edfm-text );
}
.edfm-mobile-scrim {
display: block;
position: fixed;
inset: 0;
z-index: 1000;
background: rgba( 0, 0, 0, 0.58 );
opacity: 0;
pointer-events: none;
transition: opacity 0.18s ease;
}
body.edfm-mobile-menu-open .edfm-mobile-scrim {
opacity: 1;
pointer-events: auto;
}
#mw-navigation {
background: var( --edfm-surface-2 );
box-shadow: none;
}
#mw-head {
position: relative;
z-index: 1100;
border-bottom: 1px solid var( --edfm-border );
}
#mw-head .vector-search-box {
display: none;
margin: 0;
padding: 0.65rem;
background: var( --edfm-surface-2 );
border-top: 1px solid var( --edfm-border-soft );
}
body.edfm-mobile-search-open #mw-head .vector-search-box {
display: block;
}
#mw-head .vector-search-box-inner,
#mw-head #searchform {
width: 100%;
}
#mw-head #searchInput {
min-height: 44px;
box-sizing: border-box;
width: 100%;
font-size: 1rem;
}
#left-navigation,
#right-navigation {
padding: 0 0.45rem 0.35rem;
background: var( --edfm-surface-2 );
overflow-x: auto;
white-space: nowrap;
-webkit-overflow-scrolling: touch;
}
.vector-menu-tabs-legacy ul {
flex-wrap: nowrap;
}
.vector-menu-tabs-legacy li a,
.vector-menu-tabs-legacy li a:visited,
.vector-menu-dropdown .vector-menu-heading {
min-height: 36px;
display: inline-flex;
align-items: center;
}
#p-personal {
display: none;
}
#mw-panel {
position: fixed;
top: 0;
left: 0;
z-index: 1300;
width: min( 82vw, 22rem );
height: 100dvh;
box-sizing: border-box;
padding: 0;
background: var( --edfm-surface-1 );
border: 0;
border-right: 1px solid var( --edfm-border );
box-shadow: 18px 0 36px rgba( 0, 0, 0, 0.45 );
overflow-y: auto;
-webkit-overflow-scrolling: touch;
transform: translateX( -105% );
transition: transform 0.2s ease;
}
body.edfm-mobile-menu-open #mw-panel {
transform: translateX( 0 );
}
#mw-panel::before {
content: 'EDFM Navigation';
display: block;
position: sticky;
top: 0;
z-index: 1;
padding: 1rem 3.4rem 1rem 1rem;
background: var( --edfm-surface-2 );
border-bottom: 1px solid var( --edfm-border );
color: var( --edfm-orange );
font: 800 0.86rem/1.2 var( --edfm-mono );
letter-spacing: 0.08em;
text-transform: uppercase;
}
#mw-panel .edfm-mobile-close-button {
position: absolute;
top: 0.3rem;
right: 0.35rem;
z-index: 2;
}
#mw-panel .portal,
#mw-panel .vector-menu-portal {
margin: 0;
padding: 0.75rem 0;
border-bottom: 1px solid var( --edfm-border-soft );
}
#mw-panel .vector-menu-heading {
margin: 0.25rem 1rem 0.45rem;
}
#mw-panel .vector-menu-content-list li a,
#mw-panel .vector-menu-content-list li a:visited {
display: flex;
align-items: center;
min-height: 46px;
box-sizing: border-box;
padding: 0.55rem 1rem;
border-left: 3px solid transparent;
color: var( --edfm-text-muted );
font-size: 1rem;
text-decoration: none;
}
#mw-panel .vector-menu-content-list li a:hover,
#mw-panel .vector-menu-content-list li a:focus {
background: var( --edfm-surface-3 );
border-left-color: var( --edfm-cyan );
color: var( --edfm-text );
}
#mw-panel .edfm-nav-current > a,
#mw-panel .edfm-nav-current > a:visited {
background: rgba( 255, 138, 0, 0.12 );
border-left-color: var( --edfm-orange );
color: var( --edfm-orange ) !important;
}
.mw-body {
padding: clamp( 1rem, 4vw, 1.35rem );
font-size: 1rem;
line-height: 1.68;
}
#siteNotice {
margin-bottom: 1rem;
padding-bottom: 0.85rem;
}
#firstHeading {
font-size: clamp( 1.65rem, 8vw, 2.25rem );
line-height: 1.1;
letter-spacing: -0.015em;
}
.mw-body h2 {
font-size: 1.18rem;
line-height: 1.25;
}
.mw-body p,
.mw-body li {
max-width: none;
}
.mw-body img,
.mw-body .thumb,
.mw-body .thumbinner,
.mw-body .thumbimage {
max-width: 100% !important;
height: auto !important;
box-sizing: border-box;
}
.mw-body .thumb,
.mw-body .tright,
.mw-body .tleft {
float: none !important;
clear: both;
width: auto !important;
margin: 1rem 0 !important;
}
.mw-parser-output > table.wikitable,
.mw-parser-output > table.mw-datatable {
display: block;
width: 100% !important;
max-width: 100%;
overflow-x: auto;
-webkit-overflow-scrolling: touch;
white-space: nowrap;
}
.mw-parser-output > table.wikitable th,
.mw-parser-output > table.wikitable td,
.mw-parser-output > table.mw-datatable th,
.mw-parser-output > table.mw-datatable td {
white-space: normal;
min-width: 8rem;
}
.edfm-infobox {
font-size: 0.95rem;
}
.edfm-infobox-row {
display: grid;
grid-template-columns: minmax( 7.5rem, 40% ) 1fr;
gap: 0.5rem;
padding: 0.65rem 0.8rem;
}
.edfm-infobox-label,
.edfm-infobox-value {
width: auto;
}
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type,
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type tbody,
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type tr,
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type th,
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type td {
display: block;
width: 100% !important;
box-sizing: border-box;
}
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type {
overflow: visible;
white-space: normal;
background: transparent;
border: 0;
}
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type th {
margin-top: 0.75rem;
border-left: 3px solid var( --edfm-orange );
}
body.page-Main_Page .mw-parser-output > table.wikitable:first-of-type td {
margin-bottom: 0.75rem;
background: var( --edfm-surface-2 );
border-left: 3px solid var( --edfm-border );
}
.mw-footer {
padding: 1rem;
margin-top: 1.5rem;
}
}
@media ( max-width: 430px ) {
.edfm-mobile-brand::before {
content: 'EDFM';
margin-right: 0.45rem;
}
.edfm-mobile-brand {
font-size: 0.88rem;
}
.edfm-infobox-row {
grid-template-columns: 1fr;
gap: 0.2rem;
}
}

/* 22a. Mobile action tabs refinement: keep Vector's page/discussion/read/
source/history controls available, but put them on one compact horizontal
action rail so the first phone viewport feels like a real mobile app shell
instead of two stacked desktop tab bars. */
@media ( max-width: 800px ) {
body:not( .edfm-mobile-search-open ) #mw-head {
display: flex;
align-items: stretch;
gap: 0;
overflow-x: auto;
overflow-y: hidden;
-webkit-overflow-scrolling: touch;
scrollbar-width: thin;
}
body:not( .edfm-mobile-search-open ) #left-navigation,
body:not( .edfm-mobile-search-open ) #right-navigation {
flex: 0 0 auto;
clear: none !important;
float: none !important;
width: auto;
padding: 0 0.25rem;
margin: 0 !important;
border-right: 1px solid var( --edfm-border-soft );
}
body:not( .edfm-mobile-search-open ) .vector-menu-tabs-legacy,
body:not( .edfm-mobile-search-open ) .vector-menu-dropdown {
float: none !important;
display: inline-block;
}
body:not( .edfm-mobile-search-open ) .vector-menu-tabs-legacy li a,
body:not( .edfm-mobile-search-open ) .vector-menu-tabs-legacy li a:visited,
body:not( .edfm-mobile-search-open ) .vector-menu-dropdown .vector-menu-heading {
min-height: 40px;
padding-left: 0.55rem;
padding-right: 0.55rem;
font-size: 0.68rem;
}
body.edfm-mobile-search-open #mw-head {
display: block;
}
}

/* ===========================================================================
24. HARD OVERRIDE: JUMP TILE LEFT RAIL

The earlier border-left rail can be swallowed by ResourceLoader/cascade or
visually read as part of the tile edge. Draw the rail as a high-specificity
gradient on the actual top-level TOC anchors so it is unmistakable on the
live jump grid.
=========================================================================== */
#toc.toc > ul > li > a,
.mw-parser-output #toc > ul > li > a,
.mw-parser-output .toc > ul > li > a {
background-image: linear-gradient( 90deg, var( --edfm-orange ) 0, var( --edfm-orange ) 6px, transparent 6px ) !important;
border-left: 0 !important;
padding-left: 1rem !important;
}
#toc.toc > ul > li > a:hover,
#toc.toc > ul > li > a:focus-visible,
.mw-parser-output #toc > ul > li > a:hover,
.mw-parser-output #toc > ul > li > a:focus-visible,
.mw-parser-output .toc > ul > li > a:hover,
.mw-parser-output .toc > ul > li > a:focus-visible {
background-image: linear-gradient( 90deg, var( --edfm-cyan ) 0, var( --edfm-cyan ) 6px, transparent 6px ) !important;
}

/* ===========================================================================
25. SOURCE EDIT CONFLICT / WIKITEXT DIFF THEME

Source-edit conflict review uses MediaWiki's diff table classes, not the
normal edit textarea/WikiEditor chrome. Without this, unchanged rows and
inline change pills fall back to stark white/yellow/blue defaults. Keep the
old/new meaning, but render it in EDFM's dark surfaces with restrained
orange/cyan accents.
=========================================================================== */
.mw-parser-output table.diff,
table.diff,
.diff {
background: var( --edfm-bg-deep ) !important;
color: var( --edfm-text ) !important;
border-collapse: separate !important;
border-spacing: 0 0.12rem !important;
}
.diff-title,
.diff-otitle,
.diff-ntitle,
#mw-diff-otitle1,
#mw-diff-ntitle1 {
background: var( --edfm-bg-deep ) !important;
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
}
td.diff-lineno,
.diff-lineno {
background: transparent !important;
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
font-weight: 700;
border: 0 !important;
padding: 0.35rem 0.5rem !important;
}
td.diff-marker,
.diff-marker {
background: transparent !important;
color: var( --edfm-text ) !important;
font-family: var( --edfm-mono );
font-weight: 700;
padding: 0.25rem 0.45rem !important;
text-align: center;
}
td.diff-context,
td.diff-addedline,
td.diff-deletedline,
.diff-context,
.diff-addedline,
.diff-deletedline,
.mw-diff-inline-context,
.mw-diff-inline-added,
.mw-diff-inline-deleted,
.mw-diff-inline-changed,
.mw-diff-inline-moved {
background: var( --edfm-surface-1 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
font-family: var( --edfm-mono );
box-shadow: none !important;
}
td.diff-context:empty,
td.diff-addedline:empty,
td.diff-deletedline:empty,
.diff-context:empty,
.diff-addedline:empty,
.diff-deletedline:empty {
/* Empty diff cells are alignment placeholders. Keep their card boundary so
the two-column source-conflict diff does not look broken, but make them
compact and neutral instead of tall blank blocks. */
background: var( --edfm-surface-1 ) !important;
border-color: var( --edfm-border ) !important;
box-shadow: none !important;
min-height: 0;
padding-top: 0.08rem !important;
padding-bottom: 0.08rem !important;
}
td.diff-deletedline,
.diff-deletedline,
.mw-diff-inline-deleted {
background: rgba( 255, 138, 0, 0.08 ) !important;
border-color: rgba( 255, 138, 0, 0.6 ) !important;
border-left-color: var( --edfm-orange ) !important;
}
td.diff-addedline,
.diff-addedline,
.mw-diff-inline-added {
background: rgba( 66, 199, 217, 0.08 ) !important;
border-color: rgba( 66, 199, 217, 0.6 ) !important;
border-left-color: var( --edfm-cyan ) !important;
}
.diffchange,
.diff-addedline .diffchange,
.diff-deletedline .diffchange,
.mw-diff-inline-added ins,
.mw-diff-inline-changed ins,
.mw-diff-inline-moved ins,
.mw-diff-inline-deleted del,
.mw-diff-inline-changed del,
.mw-diff-inline-moved del {
border-radius: 3px !important;
padding: 0.08rem 0.22rem !important;
font-weight: 700;
text-decoration: none !important;
color: var( --edfm-bg-deep ) !important;
}
.diff-deletedline .diffchange,
.mw-diff-inline-deleted del,
.mw-diff-inline-changed del,
.mw-diff-inline-moved del {
background: var( --edfm-orange-bright ) !important;
}
.diff-addedline .diffchange,
.mw-diff-inline-added ins,
.mw-diff-inline-changed ins,
.mw-diff-inline-moved ins {
background: var( --edfm-cyan ) !important;
}
.mw-explainconflict,
#wpTextbox2,
textarea#wpTextbox2,
textarea.mw-textarea-oldrev {
background: var( --edfm-surface-1 ) !important;
color: var( --edfm-text ) !important;
border-color: var( --edfm-border ) !important;
}

/* Engineer directory portrait chips -- intentionally quiet so table rows still
read like data rows, not card/list hybrids. */
.edfm-engineer-entry {
display: inline-flex;
align-items: center;
gap: 0.45rem;
min-width: max-content;
}
.edfm-engineer-entry .mw-file-element {
width: 30px;
height: 30px;
object-fit: cover;
border-radius: 3px;
border: 1px solid var( --edfm-border );
background: var( --edfm-surface-0 );
box-shadow: none;
}
.edfm-engineer-entry__name {
line-height: 1.2;
}

/* Frontier official news feed image treatment */
.edfm-frontier-news .edfm-news-card-art-image {
display: block;
position: relative;
padding: 0;
min-height: 9.5rem;
background: var( --edfm-surface-4 );
overflow: hidden;
}
.edfm-frontier-news .edfm-news-card-primary .edfm-news-card-art-image {
min-height: 13.5rem;
}
.edfm-frontier-news .edfm-news-card-art-image > span,
.edfm-frontier-news .edfm-news-card-art-image .mw-default-size,
.edfm-frontier-news .edfm-news-card-art-image .mw-file-description {
display: block !important;
position: absolute;
inset: 0;
width: 100% !important;
height: 100% !important;
max-width: none !important;
margin: 0 !important;
}
.edfm-frontier-news .edfm-news-card-art-image .mw-file-element {
display: block !important;
width: 100% !important;
height: 100% !important;
max-width: none !important;
object-fit: cover;
transition: transform 0.2s ease, filter 0.2s ease;
}
.edfm-frontier-news .edfm-news-card:hover .edfm-news-card-art-image .mw-file-element {
filter: brightness( 1.08 ) contrast( 1.05 );
transform: scale( 1.035 );
}
.edfm-frontier-news .edfm-news-source-badge {
display: inline-flex !important;
align-items: center;
position: absolute !important;
left: 0.8rem !important;
right: auto !important;
bottom: 0.75rem !important;
z-index: 2;
max-width: calc( 100% - 1.6rem );
padding: 0.25rem 0.55rem;
background: rgba( 10, 13, 17, 0.82 );
border: 1px solid rgba( 255, 138, 0, 0.48 );
box-shadow: 0 8px 18px rgba( 0, 0, 0, 0.34 );
color: var( --edfm-text );
font-family: var( --edfm-mono );
font-size: 0.68rem;
font-weight: 800;
letter-spacing: 0.08em;
line-height: 1;
text-transform: uppercase;
white-space: nowrap;
pointer-events: none;
}

.edfm-news-attribution {
margin-top: 0.85rem;
padding-top: 0.75rem;
border-top: 1px solid var( --edfm-border-soft );
color: var( --edfm-text-dim );
font-family: var( --edfm-mono );
font-size: var( --edfm-fs-meta );
line-height: 1.45;
}

MediaWiki:Common.js

2026-08-10T04:05:38Z

EDFM Maintenance: Add sidebar Discord invite button

/* EDFM: small, purely presentational enhancements. None are required
* for the site to function -- all degrade gracefully with JS off -- and
* none are achievable in pure CSS, which is why they exist here instead
* of in MediaWiki:Common.css. Kept deliberately tiny: no framework, no
* build step, vanilla DOM APIs only.
*/
( function () {
'use strict';

/* 1. Eyebrow placement (see Template:Article header, .edfm-eyebrow in
* Common.css). MediaWiki always renders the real #firstHeading (the
* page's H1) before the article body in the DOM -- there is no
* template or CSS hook that lets wikitext content appear earlier than
* that. The eyebrow is authored as ordinary wikitext at the top of the
* article; this just moves that already-rendered, already-accessible
* element to sit visually above the title instead of below it. If this
* script doesn't run for any reason, the eyebrow still renders --
* directly under the title rather than above it -- so nothing breaks,
* this only affects placement.
*/
function placeEyebrow() {
var eyebrow = document.querySelector( '.edfm-eyebrow' );
var heading = document.getElementById( 'firstHeading' );
if ( eyebrow && heading && heading.parentNode ) {
heading.parentNode.insertBefore( eyebrow, heading );
}
}

/* 2. "You are here" sidebar highlighting. MediaWiki's default sidebar
* has no built-in current-page indication -- this compares each
* sidebar link's URL to the current page and flags the match so
* Common.css can style it (see .edfm-nav-current). Wrapped in try/catch
* per-link only so one malformed href can't stop the rest from being
* checked.
*/
function highlightCurrentNavLink() {
var links = document.querySelectorAll( '#mw-panel .vector-menu-content-list a[href]' );
/* Compare pathname *and* query string, not just pathname. Most
* content pages use clean /wiki/Page_Name URLs where pathname alone
* is unambiguous, but action views (edit, history, diff, page
* info, ...) all route through the same /index.php pathname and
* are only distinguished by their query string (?action=edit vs
* ?action=info etc.) -- comparing pathname only would wrongly
* highlight every sidebar link that happens to also point at
* /index.php, e.g. "Page information" while actually viewing the
* edit-source screen.
*/
var here = window.location.pathname + window.location.search;
for ( var i = 0; i < links.length; i++ ) {
var a = links[ i ];
try {
var target = new URL( a.href, window.location.href );
if ( target.pathname + target.search === here ) {
a.parentNode.classList.add( 'edfm-nav-current' );
}
} catch ( e ) {
/* malformed href on this one link -- skip it, not fatal */
}
}
}

/* 3. Jump-nav label shortening (2026-08-08, Engineer article layout
* pass). MediaWiki's native table of contents always mirrors a
* section's real ==Heading== text exactly -- there's no template or
* markup mechanism for a heading to carry a separate "short nav
* label". Article headings stay full and descriptive (e.g. "How to
* Receive an Invitation") since that's what reads well in the article
* body; this only shortens the *jump-nav tile* text afterwards, so the
* dense tile grid doesn't force long headings to wrap across two
* lines. Keyed by exact heading text, shared across all Engineer
* articles (same section names throughout, see Template:New engineer
* page) rather than being specific to any one page. Anything not in
* this list is left exactly as MediaWiki rendered it -- this only ever
* shortens, never invents nav text for a heading it doesn't recognise.
*/
var TOC_SHORT_LABELS = {
'How to Discover This Engineer': 'Discovery',
'How to Receive an Invitation': 'Invitation',
'How to Unlock This Engineer': 'Unlock',
'Engineer Unlock Chain': 'Unlock Chain',
'Available Engineering': 'Engineering',
'Experimental Effects': 'Experimentals',
'Increasing Engineer Reputation': 'Reputation',
'Recommended Blueprint to Pin': 'Blueprint Pinning'
};

function shortenTocLabels() {
var toctexts = document.querySelectorAll( '#toc .toctext, .toc .toctext' );
for ( var i = 0; i < toctexts.length; i++ ) {
var el = toctexts[ i ];
var full = el.textContent.trim();
if ( Object.prototype.hasOwnProperty.call( TOC_SHORT_LABELS, full ) ) {
el.textContent = TOC_SHORT_LABELS[ full ];
}
}
}

/* 4. Desktop top-bar clocks. RuneScape.wiki has a compact utility strip
* in the personal-toolbar tier; EDFM only needs time readouts there.
* UTC is synced once from MediaWiki's API curtimestamp (server-side UTC)
* and then advanced locally each second; local time uses the visitor's
* browser timezone. If the API request fails, the UTC clock falls back to
* the browser clock in UTC rather than leaving a blank control.
*/
function initTopBarClocks() {
var personal = document.getElementById( 'p-personal' );
if ( !personal || document.querySelector( '.edfm-topbar-clocks' ) ) {
return;
}

var clocks = document.createElement( 'div' );
clocks.className = 'edfm-topbar-clocks';
clocks.setAttribute( 'aria-label', 'Current time' );

var utcClock = document.createElement( 'span' );
utcClock.className = 'edfm-topbar-clock edfm-topbar-clock-utc';
utcClock.innerHTML = '<span class="edfm-topbar-clock-label">UTC</span> <time>--:--</time>';

var localClock = document.createElement( 'span' );
localClock.className = 'edfm-topbar-clock edfm-topbar-clock-local';
localClock.innerHTML = '<span class="edfm-topbar-clock-label">Local</span> <time>--:--</time>';

clocks.appendChild( utcClock );
clocks.appendChild( localClock );
personal.insertBefore( clocks, personal.firstChild );

var utcOffset = 0;
var utcTime = utcClock.querySelector( 'time' );
var localTime = localClock.querySelector( 'time' );

function twoDigits( number ) {
return String( number ).padStart( 2, '0' );
}
function render() {
var localNow = new Date();
var utcNow = new Date( Date.now() + utcOffset );
var utcText = twoDigits( utcNow.getUTCHours() ) + ':' + twoDigits( utcNow.getUTCMinutes() );
var localText = twoDigits( localNow.getHours() ) + ':' + twoDigits( localNow.getMinutes() );

utcTime.textContent = utcText;
utcTime.setAttribute( 'datetime', utcNow.toISOString() );
utcTime.setAttribute( 'title', 'Server time (UTC): ' + utcNow.toUTCString() );

localTime.textContent = localText;
localTime.setAttribute( 'datetime', localNow.toISOString() );
localTime.setAttribute( 'title', 'Your local time: ' + localNow.toLocaleString() );
}

function syncServerTime() {
if ( !window.fetch || !window.mw || !mw.util ) {
render();
return;
}
var apiUrl = mw.util.wikiScript( 'api' ) + '?action=query&format=json&curtimestamp=1';
fetch( apiUrl, { credentials: 'same-origin' } )
.then( function ( response ) { return response.json(); } )
.then( function ( data ) {
if ( data && data.curtimestamp ) {
utcOffset = Date.parse( data.curtimestamp ) - Date.now();
}
render();
} )
.catch( render );
}

syncServerTime();
window.setInterval( render, 1000 );
}

/* 5. Sidebar Discord invite button. This mirrors the RuneScape.wiki-style
* sidebar community CTA placement: directly below the logo and above the
* first navigation group. It is injected rather than placed in
* MediaWiki:Sidebar so it stays outside the generated portlet lists and
* can keep button semantics/styling without affecting nav highlighting.
*/
function initSidebarDiscordButton() {
var panel = document.getElementById( 'mw-panel' );
var logo = document.getElementById( 'p-logo' );
if ( !panel || !logo || document.querySelector( '.edfm-discord-cta' ) ) {
return;
}

var button = document.createElement( 'a' );
button.className = 'edfm-discord-cta';
button.href = 'https://discord.gg/5rjebvgd8C';
button.target = '_blank';
button.rel = 'nofollow noopener noreferrer';
button.setAttribute( 'aria-label', 'Chat on Discord' );
button.innerHTML = '<span class="edfm-discord-cta-icon" aria-hidden="true">' +
'<svg viewBox="0 0 24 24" focusable="false"><path d="M19.54 5.23a16.73 16.73 0 0 0-4.13-1.28.06.06 0 0 0-.07.03c-.18.32-.39.74-.53 1.07a15.47 15.47 0 0 0-4.62 0 10.9 10.9 0 0 0-.54-1.07.07.07 0 0 0-.07-.03A16.64 16.64 0 0 0 5.45 5.23a.06.06 0 0 0-.03.03C2.8 9.18 2.08 13 2.43 16.78c0 .02.01.04.03.05a16.8 16.8 0 0 0 5.06 2.56.07.07 0 0 0 .08-.03c.39-.53.73-1.09 1.03-1.69a.07.07 0 0 0-.04-.09 10.92 10.92 0 0 1-1.58-.75.07.07 0 0 1-.01-.11c.11-.08.21-.16.31-.24a.06.06 0 0 1 .07-.01c3.3 1.51 6.88 1.51 10.14 0a.06.06 0 0 1 .07.01c.1.08.2.16.31.24a.07.07 0 0 1-.01.11c-.5.3-1.03.55-1.58.75a.07.07 0 0 0-.04.09c.3.6.64 1.16 1.03 1.69a.07.07 0 0 0 .08.03 16.75 16.75 0 0 0 5.06-2.56.07.07 0 0 0 .03-.05c.42-4.37-.7-8.16-2.99-11.52a.05.05 0 0 0-.03-.03ZM8.68 14.48c-.99 0-1.81-.91-1.81-2.03s.8-2.03 1.81-2.03c1.02 0 1.83.92 1.81 2.03 0 1.12-.8 2.03-1.81 2.03Zm6.65 0c-.99 0-1.81-.91-1.81-2.03s.8-2.03 1.81-2.03c1.02 0 1.83.92 1.81 2.03 0 1.12-.8 2.03-1.81 2.03Z"/></svg>' +
'</span><span>Chat on Discord</span>';

if ( logo.nextSibling ) {
panel.insertBefore( button, logo.nextSibling );
} else {
panel.appendChild( button );
}
}

/* 6. Mobile app shell. Vector legacy was built for desktop; this adds a
* small progressive-enhancement shell on phones: hamburger drawer using
* the real #mw-panel links, a search button that reveals/focuses the
* existing MediaWiki search input, ESC/scrim close behavior, and ARIA
* state updates. With JS off the CSS fallback remains the existing stacked
* Vector mobile layout.
*/
function initMobileChrome() {
var navigation = document.getElementById( 'mw-navigation' );
var panel = document.getElementById( 'mw-panel' );
var searchInput = document.getElementById( 'searchInput' );
if ( !navigation || !panel || document.querySelector( '.edfm-mobile-appbar' ) ) {
return;
}

var appbar = document.createElement( 'div' );
appbar.className = 'edfm-mobile-appbar';

var menuButton = document.createElement( 'button' );
menuButton.type = 'button';
menuButton.className = 'edfm-mobile-menu-button';
menuButton.setAttribute( 'aria-label', 'Open navigation menu' );
menuButton.setAttribute( 'aria-controls', 'mw-panel' );
menuButton.setAttribute( 'aria-expanded', 'false' );

var brand = document.createElement( 'a' );
brand.className = 'edfm-mobile-brand';
brand.href = mw && mw.util ? mw.util.getUrl( 'Main Page' ) : '/wiki/Main_Page';
brand.textContent = 'Field Manual';

var searchButton = document.createElement( 'button' );
searchButton.type = 'button';
searchButton.className = 'edfm-mobile-search-button';
searchButton.setAttribute( 'aria-label', 'Search the Field Manual' );
searchButton.setAttribute( 'aria-expanded', 'false' );

appbar.appendChild( menuButton );
appbar.appendChild( brand );
appbar.appendChild( searchButton );
navigation.insertBefore( appbar, navigation.firstChild );

var closeButton = document.createElement( 'button' );
closeButton.type = 'button';
closeButton.className = 'edfm-mobile-close-button';
closeButton.setAttribute( 'aria-label', 'Close navigation menu' );
panel.insertBefore( closeButton, panel.firstChild );

var scrim = document.createElement( 'button' );
scrim.type = 'button';
scrim.className = 'edfm-mobile-scrim';
scrim.setAttribute( 'aria-label', 'Close navigation menu' );
document.body.appendChild( scrim );

function setMenuOpen( open ) {
document.body.classList.toggle( 'edfm-mobile-menu-open', open );
menuButton.setAttribute( 'aria-expanded', open ? 'true' : 'false' );
}
function setSearchOpen( open ) {
document.body.classList.toggle( 'edfm-mobile-search-open', open );
searchButton.setAttribute( 'aria-expanded', open ? 'true' : 'false' );
if ( open && searchInput ) {
window.setTimeout( function () { searchInput.focus(); }, 0 );
}
}

menuButton.addEventListener( 'click', function () { setMenuOpen( true ); } );
closeButton.addEventListener( 'click', function () { setMenuOpen( false ); } );
scrim.addEventListener( 'click', function () { setMenuOpen( false ); } );
searchButton.addEventListener( 'click', function () {
setSearchOpen( !document.body.classList.contains( 'edfm-mobile-search-open' ) );
} );
panel.addEventListener( 'click', function ( event ) {
if ( event.target && event.target.closest && event.target.closest( 'a' ) ) {
setMenuOpen( false );
}
} );
document.addEventListener( 'keydown', function ( event ) {
if ( event.key === 'Escape' ) {
setMenuOpen( false );
setSearchOpen( false );
}
} );
}

if ( document.readyState === 'loading' ) {
document.addEventListener( 'DOMContentLoaded', function () {
placeEyebrow();
highlightCurrentNavLink();
shortenTocLabels();
initTopBarClocks();
initSidebarDiscordButton();
initMobileChrome();
} );
} else {
placeEyebrow();
highlightCurrentNavLink();
shortenTocLabels();
initTopBarClocks();
initSidebarDiscordButton();
initMobileChrome();
}
}() );

Zacariah Nemo

2026-08-08T21:30:54Z

EDFM Maintenance: Third pass: remove remaining repeated community-source phrasing from Engineer body text

{{Article header|eyebrow=EDFM // Engineer|deck=Fragment Cannon specialist based in the Yoru system.}}
{{Article status|status=Needs review|mode=Both|version=Live and Legacy; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Location and specialty cross-referenced against Inara's Engineers listing; prerequisite/discovery/invitation/unlock detail drawn primarily from a single community unlock-chain guide — see Sources|uncertainty=Maximum engineering grade and full blueprint names were not found in the sources checked; the prerequisite/discovery/invitation chain is single-sourced and not yet directly verified.}}

{{Infobox
|name = Zacariah Nemo
|label1 = Engineer type |row1 = Ship (weapon)
|label2 = System |row2 = Yoru
|label3 = Facility |row3 = Nemo Cyber Party Base
|label4 = Specialties |row4 = Fragment Cannon
|label5 = Prerequisite Engineer |row5 = Not yet confirmed
|label6 = Discovery requirement |row6 = Not yet confirmed
|label7 = Invitation requirement |row7 = Not yet confirmed
|label8 = Unlock requirement |row8 = Deliver 25 units of Xihe Companions
}}

Zacariah Nemo specialises in fragment cannon modifications.<ref name="inara-list" />

== Location ==
* '''System:''' Yoru
* '''Facility:''' Nemo Cyber Party Base

== How to Discover This Engineer ==
Not yet confirmed.<ref name="wanderer-chain">[https://wanderer-toolbox.com/guides/engineering-unlock/ Engineering Unlock Guide], Wanderer's Toolbox, accessed 2026-08-07.</ref><ref name="inara-list">[https://inara.cz/elite/engineers/ Engineers], Inara, accessed 2026-08-07.</ref>

== How to Receive an Invitation ==
Not yet confirmed.<ref name="wanderer-chain" />

== How to Unlock This Engineer ==
# Meet the invitation requirement: not yet confirmed.
# Travel to Nemo Cyber Party Base in Yoru.
# Deliver **25 units of Xihe Companions**.
# Confirm access at the Engineer's terminal.

== Engineer Unlock Chain ==
''No verified multi-Engineer chain to display for this Engineer.''

Zacariah Nemo's prerequisite Engineer is not yet confirmed, and available chain guides list no further Engineer unlocks from him.<ref name="wanderer-chain" />

== Available Engineering ==
{| class="wikitable"
! Module !! Notes !! Maximum grade
|-
| Fragment Cannon || Damage and other variants || To be confirmed
|}
Full blueprint names and maximum grades were not confirmed to the same depth as the core chain pages for this pass — see [[Elite Dangerous Field Manual:Engineering Architecture]] for the site's policy on not inventing unconfirmed specifics.<ref name="wanderer-chain" />

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at their workshop, in line with the general mechanic covered on the main [[Engineering]] page.

== Blueprint Pinning ==
'''Fact:''' Zacariah Nemo's confirmed specialties are Fragment Cannon, per [[#Available Engineering|Available Engineering]] above.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the maximum-grade and full blueprint data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
''No related Engineers confirmed for this pass.''

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Weapon Engineering]]
[[Category:Engineering]]

Tiana Fortune

2026-08-08T21:30:52Z

EDFM Maintenance: Third pass: remove remaining repeated community-source phrasing from Engineer body text

{{Article header|eyebrow=EDFM // Engineer|deck=Scanner and limpet controller specialist based in the Achenar system, reachable through Hera Tani.}}
{{Article status|status=Needs review|mode=Both|version=Live and Legacy; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Location and specialty cross-referenced against Inara's Engineers listing; prerequisite/discovery/invitation/unlock detail drawn primarily from a single community unlock-chain guide — see Sources|uncertainty=Maximum engineering grade and full blueprint names were not found in the sources checked.}}

{{Infobox
|name = Tiana Fortune
|label1 = Engineer type |row1 = Ship (utility)
|label2 = System |row2 = Achenar
|label3 = Facility |row3 = Fortune's Loss
|label4 = Specialties |row4 = Scanners, Limpet Controllers
|label5 = Prerequisite Engineer |row5 = [[Hera Tani]]
|label6 = Discovery requirement |row6 = Referral from Hera Tani
|label7 = Invitation requirement |row7 = Not yet confirmed
|label8 = Unlock requirement |row8 = Deliver 50 units of Decoded Emission Data
}}

Tiana Fortune specialises in scanners, limpet controllers modifications. They're reached through [[Hera Tani]].<ref name="inara-list" />

== Location ==
* '''System:''' Achenar
* '''Facility:''' Fortune's Loss

== How to Discover This Engineer ==
Referral from Hera Tani.<ref name="wanderer-chain">[https://wanderer-toolbox.com/guides/engineering-unlock/ Engineering Unlock Guide], Wanderer's Toolbox, accessed 2026-08-07.</ref><ref name="inara-list">[https://inara.cz/elite/engineers/ Engineers], Inara, accessed 2026-08-07.</ref>

== How to Receive an Invitation ==
Not yet confirmed.<ref name="wanderer-chain" />

== How to Unlock This Engineer ==
# Have [[Hera Tani]] unlocked and build reputation with them to trigger the referral.
# Meet the invitation requirement: not yet confirmed.
# Travel to Fortune's Loss in Achenar.
# Deliver **50 units of Decoded Emission Data** — a data-type material rather than a cargo commodity.
# Confirm access at the Engineer's terminal.

== Engineer Unlock Chain ==
''No verified multi-Engineer chain to display for this Engineer.''

Tiana Fortune is listed as reachable through [[Hera Tani]] alongside [[Broo Tarquin]], but that specific relationship still needs direct verification — see the note on [[Hera Tani]]'s own page.<ref name="wanderer-chain" />

== Available Engineering ==
{| class="wikitable"
! Module !! Notes !! Maximum grade
|-
| Scanners || Range and other variants || To be confirmed
|-
| Limpet Controller || Range and other variants || To be confirmed
|}
Full blueprint names and maximum grades were not confirmed to the same depth as the core chain pages for this pass — see [[Elite Dangerous Field Manual:Engineering Architecture]] for the site's policy on not inventing unconfirmed specifics.<ref name="wanderer-chain" />

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at their workshop, in line with the general mechanic covered on the main [[Engineering]] page.

== Blueprint Pinning ==
'''Fact:''' Tiana Fortune's confirmed specialties are Scanners, Limpet Controllers, per [[#Available Engineering|Available Engineering]] above.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the maximum-grade and full blueprint data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
{{Related articles|label=Related Engineers|[[Hera Tani]]}}

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Utility Engineering]]
[[Category:Engineering]]

Lori Jameson

2026-08-08T21:30:49Z

EDFM Maintenance: Third pass: remove remaining repeated community-source phrasing from Engineer body text

{{Article header|eyebrow=EDFM // Engineer|deck=Scanner and utility module specialist based at Jameson Base in the Shinrarta Dezhra system.}}
{{Article status|status=Needs review|mode=Both|version=Live and Legacy; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Location and specialty cross-referenced against Inara's Engineers listing; prerequisite/discovery/invitation/unlock detail drawn primarily from a single community unlock-chain guide — see Sources|uncertainty=Maximum engineering grade and full blueprint names were not found in the sources checked; the prerequisite/discovery/invitation chain is single-sourced and not yet directly verified.}}

{{Infobox
|name = Lori Jameson
|label1 = Engineer type |row1 = Ship (utility)
|label2 = System |row2 = Shinrarta Dezhra
|label3 = Facility |row3 = Jameson Base
|label4 = Specialties |row4 = Scanners, Utility modules
|label5 = Prerequisite Engineer |row5 = Not yet confirmed
|label6 = Discovery requirement |row6 = Not yet confirmed
|label7 = Invitation requirement |row7 = Elite-level rank requirement in an unspecified activity
|label8 = Unlock requirement |row8 = Deliver 25 units of Kongga Ale
}}

Lori Jameson specialises in scanners, utility modules modifications.<ref name="inara-list" />

== Location ==
* '''System:''' Shinrarta Dezhra
* '''Facility:''' Jameson Base

== How to Discover This Engineer ==
Not yet confirmed.<ref name="wanderer-chain">[https://wanderer-toolbox.com/guides/engineering-unlock/ Engineering Unlock Guide], Wanderer's Toolbox, accessed 2026-08-07.</ref><ref name="inara-list">[https://inara.cz/elite/engineers/ Engineers], Inara, accessed 2026-08-07.</ref>

== How to Receive an Invitation ==
Elite-level rank requirement in an unspecified activity.<ref name="wanderer-chain" />

== How to Unlock This Engineer ==
# Meet the invitation requirement: Elite-level rank requirement in an unspecified activity.
# Travel to Jameson Base in Shinrarta Dezhra.
# Deliver **25 units of Kongga Ale** — a rare regional commodity.
# Confirm access at the Engineer's terminal.

== Engineer Unlock Chain ==
''No verified multi-Engineer chain to display for this Engineer.''

Lori Jameson's prerequisite Engineer is not yet confirmed.<ref name="wanderer-chain" />

== Available Engineering ==
{| class="wikitable"
! Module !! Notes !! Maximum grade
|-
| Scanners || Range and other variants || To be confirmed
|}
Full blueprint names and maximum grades were not confirmed to the same depth as the core chain pages for this pass — see [[Elite Dangerous Field Manual:Engineering Architecture]] for the site's policy on not inventing unconfirmed specifics.<ref name="wanderer-chain" />

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at their workshop, in line with the general mechanic covered on the main [[Engineering]] page.

== Blueprint Pinning ==
'''Fact:''' Lori Jameson's confirmed specialties are Scanners, Utility modules, per [[#Available Engineering|Available Engineering]] above.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the maximum-grade and full blueprint data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
''No related Engineers confirmed for this pass.''

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Utility Engineering]]
[[Category:Engineering]]

Liz Ryder

2026-08-08T21:30:48Z

EDFM Maintenance: Third pass: remove remaining repeated community-source phrasing from Engineer body text

{{Article header|eyebrow=EDFM // Engineer|deck=Explosives and armour specialist based in the Eurybia system, and a starting point for the chain leading to Hera Tani and Broo Tarquin.}}
{{Article status|status=Needs review|mode=Both|version=Live and Legacy; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Cross-referenced across Inara and community unlock-chain guides for the requirements below; not first-party tested|uncertainty=Maximum engineering grade was not found in the sources checked — see Available Engineering}}

{{Engineer infobox
|name = Liz Ryder
}}

Liz Ryder specialises in explosive weapons and defensive armour — missiles, mine launchers, torpedo pylons, and hull reinforcement/armour plating. She's a second independent starting point alongside [[Felicity Farseer]] (the two don't require each other), and is the Engineer you need before [[Hera Tani]] and, further down the chain, [[Broo Tarquin]] become reachable.<ref name="inara-liz">[https://inara.cz/elite/engineer/5 Liz Ryder — engineer], Inara, accessed 2026-08-07.</ref>

== Location ==
* '''System:''' Eurybia
* '''Facility:''' Demolition Unlimited

== How to Discover This Engineer ==
No discovery step applies — Liz Ryder is known from public sources without needing a referral from another Engineer.<ref name="inara-liz" />

== How to Receive an Invitation ==
Reach '''Cordial''' or '''Friendly''' reputation with the Eurybia Blue Mafia minor faction.<ref name="inara-liz" />

== How to Unlock This Engineer ==
# Reach Cordial or Friendly standing with the Eurybia Blue Mafia.
# Travel to Demolition Unlimited in Eurybia.
# Deliver '''200 units of Landmines''' — a manufactured commodity rather than cargo bought from a market; commonly sourced by destroying other Landmines or from mission rewards.
# Confirm access at the Engineer's terminal.

== Engineer Unlock Chain ==
{{Unlock chain|Liz Ryder|Hera Tani|Broo Tarquin}}

Liz Ryder has no prerequisite Engineer. Reputation grade 3–4 with her opens the referral to [[Hera Tani]], who in turn leads to [[Broo Tarquin]] and [[Tiana Fortune]] — the latter relationship still needs direct verification.<ref name="wanderer-chain">[https://wanderer-toolbox.com/guides/engineering-unlock/ Engineering Unlock Guide], Wanderer's Toolbox, accessed 2026-08-07.</ref>

== Available Engineering ==
{| class="wikitable"
! Module !! Blueprint !! Maximum grade
|-
| Abrasion Blaster || Far-reaching || To be confirmed
|-
| Enzyme Missile Rack || High-yield || To be confirmed
|-
| Hull Reinforcement Package || Blast resistant, Heavy duty, Kinetic resistant, Lightweight, Thermal resistant || To be confirmed
|-
| Armour || Blast resistant, Heavy duty, Kinetic resistant, Lightweight, Thermal resistant || To be confirmed
|-
| Mine Launcher || High capacity, Lightweight, Rapid fire, Sturdy || To be confirmed
|-
| Missile Rack || High capacity, Lightweight, Rapid fire, Sturdy || To be confirmed
|-
| Seeker Missile Rack || Drag, High capacity, Lightweight, Lightweight thermal, Lockdown, Rapid fire, Sturdy || To be confirmed
|-
| Torpedo Pylon || Lightweight, Sturdy || To be confirmed
|}
Maximum grade per blueprint wasn't stated on the source checked.<ref name="inara-liz" />

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at her workshop, in line with the general mechanic covered on the main [[Engineering]] page.

== Blueprint Pinning ==
'''Fact:''' Liz Ryder's confirmed specialties are missile/mine/torpedo weapon variants and hull reinforcement/armour modifications, per [[#Available Engineering|Available Engineering]] above.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the maximum-grade data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
{{Related articles|label=Related Engineers|[[Hera Tani]] [[Broo Tarquin]]}}

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Weapon Engineering]]
[[Category:Engineering]]

Hera Tani

2026-08-08T21:30:46Z

EDFM Maintenance: Third pass: remove remaining repeated community-source phrasing from Engineer body text

{{Article header|eyebrow=EDFM // Engineer|deck=Power systems and scanner specialist based in the Kuwemaki system, and the link between Liz Ryder and Broo Tarquin.}}
{{Article status|status=Needs review|mode=Both|version=Live and Legacy; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Cross-referenced across Inara and community unlock-chain guides for the requirements below; not first-party tested|uncertainty=Maximum engineering grade was not found in the sources checked — see Available Engineering}}

{{Engineer infobox
|name = Hera Tani
}}

Hera Tani specialises in power systems (Power Plant and Power Distributor modifications) and scanning equipment. She sits between [[Liz Ryder]] and [[Broo Tarquin]] in the Engineer network, and is the Engineer to unlock next once Liz Ryder is available.<ref name="inara-tani">[https://inara.cz/elite/engineer/12/ Hera Tani — engineer], Inara, accessed 2026-08-07.</ref>

== Location ==
* '''System:''' Kuwemaki
* '''Facility:''' The Jet's Hole

== How to Discover This Engineer ==
Hera Tani becomes known as a referral once you've built reputation with [[Liz Ryder]] (typically around approximately grade 3–4 standing with her).<ref name="inara-tani" /><ref name="wanderer-chain">[https://wanderer-toolbox.com/guides/engineering-unlock/ Engineering Unlock Guide], Wanderer's Toolbox, accessed 2026-08-07.</ref>

== How to Receive an Invitation ==
Reach Empire rank '''Outsider''' or higher.<ref name="inara-tani" /><ref name="wanderer-chain" />

== How to Unlock This Engineer ==
# Have [[Liz Ryder]] unlocked and build enough reputation with her to trigger the referral.
# Reach Empire rank Outsider or higher.
# Travel to The Jet's Hole in Kuwemaki.
# Deliver '''50 units of Kamitra Cigars''' — a rare commodity, typically bought a few tons at a time from Hammel Terminal in the Kamitra system.
# Confirm access at the Engineer's terminal.

Station services may not appear immediately after unlocking — relogging may make them available.<ref name="inara-tani" />

== Engineer Unlock Chain ==
{{Unlock chain|Liz Ryder|Hera Tani|Broo Tarquin}}

Hera Tani's only confirmed prerequisite is Liz Ryder. She in turn leads to [[Broo Tarquin]]; chain guides also list [[Tiana Fortune]] as reachable from Hera Tani, but that specific relationship still needs direct verification.<ref name="wanderer-chain" />

== Available Engineering ==
{| class="wikitable"
! Module !! Blueprint !! Maximum grade
|-
| Detailed Surface Scanner || Expanded probe scanning radius, Long range detailed || To be confirmed
|-
| Power Distributor || Balanced, Charge enhanced, Engine focused, High charge capacity, Shielded, Support focused, System focused, Weapon focused || To be confirmed
|-
| Power Plant || Armoured, Low emissions, Overcharged || To be confirmed
|-
| Sensors || Lightweight, Long range, Wide angle || To be confirmed
|}
Maximum grade per blueprint wasn't stated on the source checked.<ref name="inara-tani" />

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at her workshop, in line with the general mechanic covered on the main [[Engineering]] page.

== Blueprint Pinning ==
'''Fact:''' Hera Tani's confirmed specialties are Power Plant, Power Distributor, Sensors, and Detailed Surface Scanner modifications, per [[#Available Engineering|Available Engineering]] above.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the maximum-grade data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
{{Related articles|label=Related Engineers|[[Liz Ryder]] [[Broo Tarquin]]}}

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Core Internal Engineering]]
[[Category:Engineering]]

Felicity Farseer

2026-08-08T21:30:45Z

EDFM Maintenance: Third pass: remove remaining repeated community-source phrasing from Engineer body text

{{Article header|eyebrow=EDFM // Engineer|deck=Frame Shift Drive specialist based in the Deciat system, and one of the earliest Engineers most commanders unlock.}}
{{Article status|status=Needs review|mode=Both|version=Live and Legacy; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Cross-referenced across Inara and community unlock-chain guides for the requirements below; not first-party tested|uncertainty=Maximum engineering grade and the full named list of blueprints beyond module/upgrade counts were not found in the sources checked — see Available Engineering}}

{{Engineer infobox
|name = Felicity Farseer
}}

Felicity Farseer is one of the first Engineers most commanders reach, and is a common starting point for the wider Engineer network — several other Engineers are ultimately reached only after unlocking her.<ref name="inara-farseer">[https://inara.cz/elite/engineer/1/ Felicity Farseer — engineer], Inara, accessed 2026-08-07.</ref><ref name="wanderer-chain">[https://wanderer-toolbox.com/guides/engineering-unlock/ Engineering Unlock Guide], Wanderer's Toolbox, accessed 2026-08-07.</ref>

== Location ==
* '''System:''' Deciat
* '''Facility:''' Farseer Inc
* '''Navigation notes:''' Deciat is a frequently-visited system for new commanders reaching their first Engineer; be aware it has a reputation as a location where player-vs-player interdiction is more common than average.<ref name="frontier-farseer-thread">[https://forums.frontier.co.uk/threads/engineers-in-this-case-felicity-farseer.602520/ Engineers (in this case Felicity Farseer)], Frontier Forums, accessed 2026-08-07.</ref>

== How to Discover This Engineer ==
No discovery step applies — Felicity Farseer is known from public data sources without needing a referral from another Engineer.<ref name="inara-farseer" />

== How to Receive an Invitation ==
Reach Exploration rank '''Scout''' or higher.<ref name="inara-farseer" /><ref name="wanderer-chain" />

== How to Unlock This Engineer ==
# Reach Exploration rank Scout or higher.
# Travel to Farseer Inc in Deciat.
# Deliver '''1 unit of Meta-Alloys''' — an encoded/manufactured material rather than a purchasable commodity.
# Confirm access at the Engineer's terminal.

station services (including the ability to actually place engineering orders) may not appear immediately after unlocking — relogging may make them available.<ref name="inara-farseer" />

== Engineer Unlock Chain ==
Felicity Farseer has no prerequisite Engineer — she's a starting point for the network rather than partway along a chain.<ref name="inara-farseer" /> [[Liz Ryder]] is also independently available from the start; the two are separate entry points, not sequential.<ref name="inara-liz">[https://inara.cz/elite/engineer/5 Liz Ryder — engineer], Inara, accessed 2026-08-07.</ref>

== Available Engineering ==
{| class="wikitable"
! Module !! Blueprint count (per Inara) !! Maximum grade
|-
| Detailed Surface Scanner || 2 variants || To be confirmed
|-
| Frame Shift Drive || 3 variants || To be confirmed
|-
| Frame Shift Drive Interdictor || 2 variants || To be confirmed
|-
| Power Plant || 3 variants || To be confirmed
|-
| Sensors || 3 variants || To be confirmed
|-
| Shield Booster || 5 variants || To be confirmed
|-
| Thrusters || 3 variants || To be confirmed
|}
The source checked for this pass gave module coverage and variant counts but not the specific blueprint name for each variant or the maximum grade — listing invented blueprint names here would risk stating something not actually confirmed, so this table intentionally stops at what was verifiable.<ref name="inara-farseer" />

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at her workshop, or by selling exploration data there.<ref name="inara-farseer" /> Reputation mechanics common to all Engineers are covered on the main [[Engineering]] page rather than repeated here.

== Blueprint Pinning ==
'''Fact:''' Felicity Farseer's confirmed specialties are Frame Shift Drive, Power Plant, Sensors, Shield Booster, Thrusters, Detailed Surface Scanner, and FSD Interdictor modifications.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the maximum-grade and specific-blueprint data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
{{Related articles|label=Related Engineers|[[Liz Ryder]]}}

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Core Internal Engineering]]
[[Category:Engineering]]

Elvira Martuuk

2026-08-08T21:30:44Z

EDFM Maintenance: Third pass: remove remaining repeated community-source phrasing from Engineer body text

{{Article header|eyebrow=EDFM // Engineer|deck=Frame Shift Drive specialist based in the Khun system, reached after Felicity Farseer.}}
{{Article status|status=Needs review|mode=Both|version=Live and Legacy; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Location and specialty cross-referenced against Inara's Engineers listing; prerequisite/discovery/invitation/unlock detail drawn primarily from a single community unlock-chain guide — see Sources|uncertainty=Maximum engineering grade and full blueprint names were not found in the sources checked.}}

{{Infobox
|name = Elvira Martuuk
|label1 = Engineer type |row1 = Ship (core internal)
|label2 = System |row2 = Khun
|label3 = Facility |row3 = Long Sight Base
|label4 = Specialties |row4 = Frame Shift Drive
|label5 = Prerequisite Engineer |row5 = [[Felicity Farseer]]
|label6 = Discovery requirement |row6 = Referral from Felicity Farseer
|label7 = Invitation requirement |row7 = Not yet confirmed
|label8 = Unlock requirement |row8 = Deliver 3 units of Soontil Relics
}}

Elvira Martuuk specialises in frame shift drive modifications. They're reached through [[Felicity Farseer]]. See Engineer Unlock Chain below for their relationship to [[Marco Qwent]].<ref name="inara-list" />

== Location ==
* '''System:''' Khun
* '''Facility:''' Long Sight Base

== How to Discover This Engineer ==
Referral from Felicity Farseer.<ref name="wanderer-chain">[https://wanderer-toolbox.com/guides/engineering-unlock/ Engineering Unlock Guide], Wanderer's Toolbox, accessed 2026-08-07.</ref><ref name="inara-list">[https://inara.cz/elite/engineers/ Engineers], Inara, accessed 2026-08-07.</ref>

== How to Receive an Invitation ==
Not yet confirmed.<ref name="wanderer-chain" />

== How to Unlock This Engineer ==
# Have [[Felicity Farseer]] unlocked and build reputation with them to trigger the referral.
# Meet the invitation requirement: not yet confirmed.
# Travel to Long Sight Base in Khun.
# Deliver **3 units of Soontil Relics** — a rare, region-specific commodity.
# Confirm access at the Engineer's terminal.

== Engineer Unlock Chain ==
{{Unlock chain|Felicity Farseer|Elvira Martuuk|Marco Qwent}}

Elvira Martuuk sits between [[Felicity Farseer]] and [[Marco Qwent]]. She is also listed as the referral source for [[Mel Brandon]] in Colonia; that specific relationship still needs direct verification.<ref name="wanderer-chain" />

== Available Engineering ==
{| class="wikitable"
! Module !! Notes !! Maximum grade
|-
| Frame Shift Drive || Increased range and other variants || To be confirmed
|}
Full blueprint names and maximum grades were not confirmed to the same depth as the core chain pages for this pass — see [[Elite Dangerous Field Manual:Engineering Architecture]] for the site's policy on not inventing unconfirmed specifics.<ref name="wanderer-chain" />

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at their workshop, in line with the general mechanic covered on the main [[Engineering]] page.

== Blueprint Pinning ==
'''Fact:''' Elvira Martuuk's confirmed specialties are Frame Shift Drive, per [[#Available Engineering|Available Engineering]] above.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the maximum-grade and full blueprint data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
{{Related articles|label=Related Engineers|[[Felicity Farseer]] [[Marco Qwent]]}}

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Core Internal Engineering]]
[[Category:Engineering]]

Zacariah Nemo

2026-08-08T21:29:27Z

EDFM Maintenance: Second pass: streamline Engineer verification caveat wording

{{Article header|eyebrow=EDFM // Engineer|deck=Fragment Cannon specialist based in the Yoru system.}}
{{Article status|status=Needs review|mode=Both|version=Live and Legacy; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Location and specialty cross-referenced against Inara's Engineers listing; prerequisite/discovery/invitation/unlock detail drawn primarily from a single community unlock-chain guide — see Sources|uncertainty=Maximum engineering grade and full blueprint names were not found in the sources checked; the prerequisite/discovery/invitation chain is single-sourced and not yet directly verified.}}

{{Infobox
|name = Zacariah Nemo
|label1 = Engineer type |row1 = Ship (weapon)
|label2 = System |row2 = Yoru
|label3 = Facility |row3 = Nemo Cyber Party Base
|label4 = Specialties |row4 = Fragment Cannon
|label5 = Prerequisite Engineer |row5 = Not yet confirmed
|label6 = Discovery requirement |row6 = Not yet confirmed
|label7 = Invitation requirement |row7 = Not yet confirmed
|label8 = Unlock requirement |row8 = Deliver 25 units of Xihe Companions
}}

Zacariah Nemo specialises in fragment cannon modifications.<ref name="inara-list" />

== Location ==
* '''System:''' Yoru
* '''Facility:''' Nemo Cyber Party Base

== How to Discover This Engineer ==
Not yet confirmed.<ref name="wanderer-chain">[https://wanderer-toolbox.com/guides/engineering-unlock/ Engineering Unlock Guide], Wanderer's Toolbox, accessed 2026-08-07.</ref><ref name="inara-list">[https://inara.cz/elite/engineers/ Engineers], Inara, accessed 2026-08-07.</ref>

== How to Receive an Invitation ==
Not yet confirmed.<ref name="wanderer-chain" />

== How to Unlock This Engineer ==
# Meet the invitation requirement: not yet confirmed.
# Travel to Nemo Cyber Party Base in Yoru.
# Deliver **25 units of Xihe Companions**.
# Confirm access at the Engineer's terminal.

== Engineer Unlock Chain ==
''No verified multi-Engineer chain to display for this Engineer.''

Zacariah Nemo's prerequisite Engineer is not yet confirmed, and chain guides describe him as not leading to any further Engineer.<ref name="wanderer-chain" />

== Available Engineering ==
{| class="wikitable"
! Module !! Notes !! Maximum grade
|-
| Fragment Cannon || Damage and other variants || To be confirmed
|}
Full blueprint names and maximum grades were not confirmed to the same depth as the core chain pages for this pass — see [[Elite Dangerous Field Manual:Engineering Architecture]] for the site's policy on not inventing unconfirmed specifics.<ref name="wanderer-chain" />

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at their workshop, in line with the general mechanic covered on the main [[Engineering]] page.

== Blueprint Pinning ==
'''Fact:''' Zacariah Nemo's confirmed specialties are Fragment Cannon, per [[#Available Engineering|Available Engineering]] above.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the maximum-grade and full blueprint data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
''No related Engineers confirmed for this pass.''

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Weapon Engineering]]
[[Category:Engineering]]

Yi Shen

2026-08-08T21:29:26Z

EDFM Maintenance: Second pass: streamline Engineer verification caveat wording

{{Article header|eyebrow=EDFM // Odyssey Engineer|deck=Stealth and perception specialist at Eidolon Hold in the Einheriar system, Colonia region.}}
{{Article status|status=Needs review|mode=Live|version=Odyssey on-foot Engineering; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Location and specialty cross-referenced against Inara's Engineers listing only; discovery, invitation, and unlock requirements have not yet been researched|uncertainty=Discovery requirement, invitation requirement, unlock requirement, prerequisite Engineer, maximum grade, and specific modification names are all not yet researched. Only location and general specialty area are confirmed.}}

{{Infobox
|name = Yi Shen
|label1 = Engineer type |row1 = Odyssey (suit / weapon)
|label2 = System |row2 = Einheriar
|label3 = Settlement |row3 = Eidolon Hold
|label4 = Specialties |row4 = Stealth and perception
|label5 = Prerequisite Engineer |row5 = Not yet researched
|label6 = Discovery requirement |row6 = Not yet researched
|label7 = Invitation requirement |row7 = Not yet researched
|label8 = Unlock requirement |row8 = Not yet researched
}}

Yi Shen specialises in stealth and perception modifications for suits and handheld weapons.<ref name="inara-list" />

Odyssey Engineering is a separate system from ship Engineering — it modifies suits and handheld weapons rather than ship modules, and exists only in Live (there is no Legacy equivalent). See [[Engineers]] for how the two systems are organised.

== Location ==
* '''System:''' Einheriar
* '''Settlement:''' Eidolon Hold
* '''Region:''' Colonia — this Engineer is only reachable after making the long journey to the Colonia region, separate from the core bubble.

== How to Discover This Engineer ==
Not yet researched.<ref name="inara-list">[https://inara.cz/elite/engineers/ Engineers], Inara, accessed 2026-08-07.</ref>

== How to Receive an Invitation ==
Not yet researched.

== How to Unlock This Engineer ==
# Meet the invitation requirement: not yet researched.
# Travel to Eidolon Hold in Einheriar.
# Meet the unlock requirement: not yet researched.
# Confirm access at the Engineer's terminal.

== Engineer Unlock Chain ==
''No verified multi-Engineer chain to display for this Engineer.''

Prerequisite Engineer, if any, not yet researched.

== Available Engineering ==
{{Draft warning}}
Specific suit/weapon modification names and maximum grades were not confirmed in the sources checked for this pass — see [[Elite Dangerous Field Manual:Engineering Architecture]] for the site's policy on not inventing unconfirmed specifics. Confirmed specialty area: Stealth and perception.

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at their workshop, in line with the general mechanic covered on the main [[Engineering]] page.

== Blueprint Pinning ==
'''Fact:''' Yi Shen's confirmed specialty area is Stealth and perception.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the specific modification and maximum-grade data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
''No related Engineers confirmed for this pass.''

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Odyssey Engineering]]
[[Category:Engineering]]

Yarden Bond

2026-08-08T21:29:25Z

EDFM Maintenance: Second pass: streamline Engineer verification caveat wording

{{Article header|eyebrow=EDFM // Odyssey Engineer|deck=Movement and stealth specialist at Salamander Bank in the Bayan system.}}
{{Article status|status=Needs review|mode=Live|version=Odyssey on-foot Engineering; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Location and specialty cross-referenced against Inara's Engineers listing only; discovery, invitation, and unlock requirements have not yet been researched|uncertainty=Discovery requirement, invitation requirement, unlock requirement, prerequisite Engineer, maximum grade, and specific modification names are all not yet researched. Only location and general specialty area are confirmed.}}

{{Infobox
|name = Yarden Bond
|label1 = Engineer type |row1 = Odyssey (suit / weapon)
|label2 = System |row2 = Bayan
|label3 = Settlement |row3 = Salamander Bank
|label4 = Specialties |row4 = Movement and stealth
|label5 = Prerequisite Engineer |row5 = Not yet researched
|label6 = Discovery requirement |row6 = Not yet researched
|label7 = Invitation requirement |row7 = Not yet researched
|label8 = Unlock requirement |row8 = Not yet researched
}}

Yarden Bond specialises in movement and stealth modifications for suits and handheld weapons.<ref name="inara-list" />

Odyssey Engineering is a separate system from ship Engineering — it modifies suits and handheld weapons rather than ship modules, and exists only in Live (there is no Legacy equivalent). See [[Engineers]] for how the two systems are organised.

== Location ==
* '''System:''' Bayan
* '''Settlement:''' Salamander Bank

== How to Discover This Engineer ==
Not yet researched.<ref name="inara-list">[https://inara.cz/elite/engineers/ Engineers], Inara, accessed 2026-08-07.</ref>

== How to Receive an Invitation ==
Not yet researched.

== How to Unlock This Engineer ==
# Meet the invitation requirement: not yet researched.
# Travel to Salamander Bank in Bayan.
# Meet the unlock requirement: not yet researched.
# Confirm access at the Engineer's terminal.

== Engineer Unlock Chain ==
''No verified multi-Engineer chain to display for this Engineer.''

Prerequisite Engineer, if any, not yet researched.

== Available Engineering ==
{{Draft warning}}
Specific suit/weapon modification names and maximum grades were not confirmed in the sources checked for this pass — see [[Elite Dangerous Field Manual:Engineering Architecture]] for the site's policy on not inventing unconfirmed specifics. Confirmed specialty area: Movement and stealth.

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at their workshop, in line with the general mechanic covered on the main [[Engineering]] page.

== Blueprint Pinning ==
'''Fact:''' Yarden Bond's confirmed specialty area is Movement and stealth.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the specific modification and maximum-grade data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
''No related Engineers confirmed for this pass.''

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Odyssey Engineering]]
[[Category:Engineering]]

Wellington Beck

2026-08-08T21:29:24Z

EDFM Maintenance: Second pass: streamline Engineer verification caveat wording

{{Article header|eyebrow=EDFM // Odyssey Engineer|deck=Tactical equipment specialist at Beck Facility in the Jolapa system.}}
{{Article status|status=Needs review|mode=Live|version=Odyssey on-foot Engineering; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Location and specialty cross-referenced against Inara's Engineers listing only; discovery, invitation, and unlock requirements have not yet been researched|uncertainty=Discovery requirement, invitation requirement, unlock requirement, prerequisite Engineer, maximum grade, and specific modification names are all not yet researched. Only location and general specialty area are confirmed.}}

{{Infobox
|name = Wellington Beck
|label1 = Engineer type |row1 = Odyssey (suit / weapon)
|label2 = System |row2 = Jolapa
|label3 = Settlement |row3 = Beck Facility
|label4 = Specialties |row4 = Tactical equipment
|label5 = Prerequisite Engineer |row5 = Not yet researched
|label6 = Discovery requirement |row6 = Not yet researched
|label7 = Invitation requirement |row7 = Not yet researched
|label8 = Unlock requirement |row8 = Not yet researched
}}

Wellington Beck specialises in tactical equipment modifications for suits and handheld weapons.<ref name="inara-list" />

Odyssey Engineering is a separate system from ship Engineering — it modifies suits and handheld weapons rather than ship modules, and exists only in Live (there is no Legacy equivalent). See [[Engineers]] for how the two systems are organised.

== Location ==
* '''System:''' Jolapa
* '''Settlement:''' Beck Facility

== How to Discover This Engineer ==
Not yet researched.<ref name="inara-list">[https://inara.cz/elite/engineers/ Engineers], Inara, accessed 2026-08-07.</ref>

== How to Receive an Invitation ==
Not yet researched.

== How to Unlock This Engineer ==
# Meet the invitation requirement: not yet researched.
# Travel to Beck Facility in Jolapa.
# Meet the unlock requirement: not yet researched.
# Confirm access at the Engineer's terminal.

== Engineer Unlock Chain ==
''No verified multi-Engineer chain to display for this Engineer.''

Prerequisite Engineer, if any, not yet researched.

== Available Engineering ==
{{Draft warning}}
Specific suit/weapon modification names and maximum grades were not confirmed in the sources checked for this pass — see [[Elite Dangerous Field Manual:Engineering Architecture]] for the site's policy on not inventing unconfirmed specifics. Confirmed specialty area: Tactical equipment.

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at their workshop, in line with the general mechanic covered on the main [[Engineering]] page.

== Blueprint Pinning ==
'''Fact:''' Wellington Beck's confirmed specialty area is Tactical equipment.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the specific modification and maximum-grade data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
''No related Engineers confirmed for this pass.''

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Odyssey Engineering]]
[[Category:Engineering]]

Uma Laszlo

2026-08-08T21:29:23Z

EDFM Maintenance: Second pass: streamline Engineer verification caveat wording

{{Article header|eyebrow=EDFM // Odyssey Engineer|deck=Combat effectiveness specialist at Laszlo's Resolve in the Xuane system.}}
{{Article status|status=Needs review|mode=Live|version=Odyssey on-foot Engineering; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Location and specialty cross-referenced against Inara's Engineers listing only; discovery, invitation, and unlock requirements have not yet been researched|uncertainty=Discovery requirement, invitation requirement, unlock requirement, prerequisite Engineer, maximum grade, and specific modification names are all not yet researched. Only location and general specialty area are confirmed.}}

{{Infobox
|name = Uma Laszlo
|label1 = Engineer type |row1 = Odyssey (suit / weapon)
|label2 = System |row2 = Xuane
|label3 = Settlement |row3 = Laszlo's Resolve
|label4 = Specialties |row4 = Combat effectiveness
|label5 = Prerequisite Engineer |row5 = Not yet researched
|label6 = Discovery requirement |row6 = Not yet researched
|label7 = Invitation requirement |row7 = Not yet researched
|label8 = Unlock requirement |row8 = Not yet researched
}}

Uma Laszlo specialises in combat effectiveness modifications for suits and handheld weapons.<ref name="inara-list" />

Odyssey Engineering is a separate system from ship Engineering — it modifies suits and handheld weapons rather than ship modules, and exists only in Live (there is no Legacy equivalent). See [[Engineers]] for how the two systems are organised.

== Location ==
* '''System:''' Xuane
* '''Settlement:''' Laszlo's Resolve

== How to Discover This Engineer ==
Not yet researched.<ref name="inara-list">[https://inara.cz/elite/engineers/ Engineers], Inara, accessed 2026-08-07.</ref>

== How to Receive an Invitation ==
Not yet researched.

== How to Unlock This Engineer ==
# Meet the invitation requirement: not yet researched.
# Travel to Laszlo's Resolve in Xuane.
# Meet the unlock requirement: not yet researched.
# Confirm access at the Engineer's terminal.

== Engineer Unlock Chain ==
''No verified multi-Engineer chain to display for this Engineer.''

Prerequisite Engineer, if any, not yet researched.

== Available Engineering ==
{{Draft warning}}
Specific suit/weapon modification names and maximum grades were not confirmed in the sources checked for this pass — see [[Elite Dangerous Field Manual:Engineering Architecture]] for the site's policy on not inventing unconfirmed specifics. Confirmed specialty area: Combat effectiveness.

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at their workshop, in line with the general mechanic covered on the main [[Engineering]] page.

== Blueprint Pinning ==
'''Fact:''' Uma Laszlo's confirmed specialty area is Combat effectiveness.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the specific modification and maximum-grade data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
''No related Engineers confirmed for this pass.''

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Odyssey Engineering]]
[[Category:Engineering]]

Tod "The Blaster" McQuinn

2026-08-08T21:29:23Z

EDFM Maintenance: Second pass: streamline Engineer verification caveat wording

{{Article header|eyebrow=EDFM // Engineer|deck=Cannon and Rail Gun specialist based in the Wolf 397 system.}}
{{Article status|status=Needs review|mode=Both|version=Live and Legacy; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Location and specialty cross-referenced against Inara's Engineers listing; prerequisite/discovery/invitation/unlock detail drawn primarily from a single community unlock-chain guide — see Sources|uncertainty=Maximum engineering grade and full blueprint names were not found in the sources checked; the prerequisite/discovery/invitation chain is single-sourced and not yet directly verified.}}

{{Infobox
|name = Tod "The Blaster" McQuinn
|label1 = Engineer type |row1 = Ship (weapon)
|label2 = System |row2 = Wolf 397
|label3 = Facility |row3 = Trophy Camp
|label4 = Specialties |row4 = Cannons, Rail Guns
|label5 = Prerequisite Engineer |row5 = Not yet confirmed
|label6 = Discovery requirement |row6 = Not yet confirmed
|label7 = Invitation requirement |row7 = Requires 15 or more bounty vouchers redeemed before the referral appears
|label8 = Unlock requirement |row8 = Deliver bounty vouchers worth 100,000 CR
}}

Tod "The Blaster" McQuinn specialises in cannons, rail guns modifications. See Engineer Unlock Chain below for their relationship to [[Selene Jean]] and [[Petra Olmanova]].<ref name="inara-list" />

== Location ==
* '''System:''' Wolf 397
* '''Facility:''' Trophy Camp

== How to Discover This Engineer ==
Not yet confirmed.<ref name="wanderer-chain">[https://wanderer-toolbox.com/guides/engineering-unlock/ Engineering Unlock Guide], Wanderer's Toolbox, accessed 2026-08-07.</ref><ref name="inara-list">[https://inara.cz/elite/engineers/ Engineers], Inara, accessed 2026-08-07.</ref>

== How to Receive an Invitation ==
Requires 15 or more bounty vouchers redeemed before the referral appears.<ref name="wanderer-chain" />

== How to Unlock This Engineer ==
# Meet the invitation requirement: 15 or more bounty vouchers redeemed before the referral appears.
# Travel to Trophy Camp in Wolf 397.
# Redeem or deliver **bounty vouchers worth 100,000 CR total** at his facility.
# Confirm access at the Engineer's terminal.

== Engineer Unlock Chain ==
''No verified multi-Engineer chain to display for this Engineer.''

Tod McQuinn's own prerequisite Engineer is not yet confirmed. He is the referral source for both [[Selene Jean]] and [[Petra Olmanova]] (the latter in Colonia).<ref name="wanderer-chain" />

== Available Engineering ==
{| class="wikitable"
! Module !! Notes !! Maximum grade
|-
| Cannon || Damage and other variants || To be confirmed
|-
| Rail Gun || Damage and other variants || To be confirmed
|}
Full blueprint names and maximum grades were not confirmed to the same depth as the core chain pages for this pass — see [[Elite Dangerous Field Manual:Engineering Architecture]] for the site's policy on not inventing unconfirmed specifics.<ref name="wanderer-chain" />

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at their workshop, in line with the general mechanic covered on the main [[Engineering]] page.

== Blueprint Pinning ==
'''Fact:''' Tod "The Blaster" McQuinn's confirmed specialties are Cannons, Rail Guns, per [[#Available Engineering|Available Engineering]] above.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the maximum-grade and full blueprint data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
{{Related articles|label=Related Engineers|[[Selene Jean]] [[Petra Olmanova]]}}

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Weapon Engineering]]
[[Category:Engineering]]

Tiana Fortune

2026-08-08T21:29:22Z

EDFM Maintenance: Second pass: streamline Engineer verification caveat wording

{{Article header|eyebrow=EDFM // Engineer|deck=Scanner and limpet controller specialist based in the Achenar system, reachable through Hera Tani.}}
{{Article status|status=Needs review|mode=Both|version=Live and Legacy; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Location and specialty cross-referenced against Inara's Engineers listing; prerequisite/discovery/invitation/unlock detail drawn primarily from a single community unlock-chain guide — see Sources|uncertainty=Maximum engineering grade and full blueprint names were not found in the sources checked.}}

{{Infobox
|name = Tiana Fortune
|label1 = Engineer type |row1 = Ship (utility)
|label2 = System |row2 = Achenar
|label3 = Facility |row3 = Fortune's Loss
|label4 = Specialties |row4 = Scanners, Limpet Controllers
|label5 = Prerequisite Engineer |row5 = [[Hera Tani]]
|label6 = Discovery requirement |row6 = Referral from Hera Tani
|label7 = Invitation requirement |row7 = Not yet confirmed
|label8 = Unlock requirement |row8 = Deliver 50 units of Decoded Emission Data
}}

Tiana Fortune specialises in scanners, limpet controllers modifications. They're reached through [[Hera Tani]].<ref name="inara-list" />

== Location ==
* '''System:''' Achenar
* '''Facility:''' Fortune's Loss

== How to Discover This Engineer ==
Referral from Hera Tani.<ref name="wanderer-chain">[https://wanderer-toolbox.com/guides/engineering-unlock/ Engineering Unlock Guide], Wanderer's Toolbox, accessed 2026-08-07.</ref><ref name="inara-list">[https://inara.cz/elite/engineers/ Engineers], Inara, accessed 2026-08-07.</ref>

== How to Receive an Invitation ==
Not yet confirmed.<ref name="wanderer-chain" />

== How to Unlock This Engineer ==
# Have [[Hera Tani]] unlocked and build reputation with them to trigger the referral.
# Meet the invitation requirement: not yet confirmed.
# Travel to Fortune's Loss in Achenar.
# Deliver **50 units of Decoded Emission Data** — a data-type material rather than a cargo commodity.
# Confirm access at the Engineer's terminal.

== Engineer Unlock Chain ==
''No verified multi-Engineer chain to display for this Engineer.''

Chain guides list Tiana Fortune as reachable through [[Hera Tani]] alongside [[Broo Tarquin]], but that specific relationship hasn't been independently checked for this pass — see the note on [[Hera Tani]]'s own page.<ref name="wanderer-chain" />

== Available Engineering ==
{| class="wikitable"
! Module !! Notes !! Maximum grade
|-
| Scanners || Range and other variants || To be confirmed
|-
| Limpet Controller || Range and other variants || To be confirmed
|}
Full blueprint names and maximum grades were not confirmed to the same depth as the core chain pages for this pass — see [[Elite Dangerous Field Manual:Engineering Architecture]] for the site's policy on not inventing unconfirmed specifics.<ref name="wanderer-chain" />

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at their workshop, in line with the general mechanic covered on the main [[Engineering]] page.

== Blueprint Pinning ==
'''Fact:''' Tiana Fortune's confirmed specialties are Scanners, Limpet Controllers, per [[#Available Engineering|Available Engineering]] above.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the maximum-grade and full blueprint data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
{{Related articles|label=Related Engineers|[[Hera Tani]]}}

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Utility Engineering]]
[[Category:Engineering]]

The Sarge

2026-08-08T21:29:21Z

EDFM Maintenance: Second pass: streamline Engineer verification caveat wording

{{Article header|eyebrow=EDFM // Engineer|deck=Limpet controller specialist based in the Beta-3 Tucani system, reachable through Juri Ishmaak.}}
{{Article status|status=Needs review|mode=Both|version=Live and Legacy; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Location and specialty cross-referenced against Inara's Engineers listing; prerequisite/discovery/invitation/unlock detail drawn primarily from a single community unlock-chain guide — see Sources|uncertainty=Maximum engineering grade and full blueprint names were not found in the sources checked.}}

{{Infobox
|name = The Sarge
|label1 = Engineer type |row1 = Ship (utility)
|label2 = System |row2 = Beta-3 Tucani
|label3 = Facility |row3 = The Beach
|label4 = Specialties |row4 = Limpet Controllers
|label5 = Prerequisite Engineer |row5 = [[Juri Ishmaak]]
|label6 = Discovery requirement |row6 = Referral from Juri Ishmaak
|label7 = Invitation requirement |row7 = Not yet confirmed
|label8 = Unlock requirement |row8 = Deliver 50 units of Aberrant Shield Pattern Analysis
}}

The Sarge specialises in limpet controllers modifications. They're reached through [[Juri Ishmaak]].<ref name="inara-list" />

== Location ==
* '''System:''' Beta-3 Tucani
* '''Facility:''' The Beach

== How to Discover This Engineer ==
Referral from Juri Ishmaak.<ref name="wanderer-chain">[https://wanderer-toolbox.com/guides/engineering-unlock/ Engineering Unlock Guide], Wanderer's Toolbox, accessed 2026-08-07.</ref><ref name="inara-list">[https://inara.cz/elite/engineers/ Engineers], Inara, accessed 2026-08-07.</ref>

== How to Receive an Invitation ==
Not yet confirmed.<ref name="wanderer-chain" />

== How to Unlock This Engineer ==
# Have [[Juri Ishmaak]] unlocked and build reputation with them to trigger the referral.
# Meet the invitation requirement: not yet confirmed.
# Travel to The Beach in Beta-3 Tucani.
# Deliver **50 units of Aberrant Shield Pattern Analysis** — a data-type material.
# Confirm access at the Engineer's terminal.

== Engineer Unlock Chain ==
''No verified multi-Engineer chain to display for this Engineer.''

The Sarge is reachable through [[Juri Ishmaak]].<ref name="wanderer-chain" />

== Available Engineering ==
{| class="wikitable"
! Module !! Notes !! Maximum grade
|-
| Limpet Controller || Range and other variants || To be confirmed
|}
Full blueprint names and maximum grades were not confirmed to the same depth as the core chain pages for this pass — see [[Elite Dangerous Field Manual:Engineering Architecture]] for the site's policy on not inventing unconfirmed specifics.<ref name="wanderer-chain" />

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at their workshop, in line with the general mechanic covered on the main [[Engineering]] page.

== Blueprint Pinning ==
'''Fact:''' The Sarge's confirmed specialties are Limpet Controllers, per [[#Available Engineering|Available Engineering]] above.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the maximum-grade and full blueprint data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
{{Related articles|label=Related Engineers|[[Juri Ishmaak]]}}

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Utility Engineering]]
[[Category:Engineering]]

The Dweller

2026-08-08T21:29:20Z

EDFM Maintenance: Second pass: streamline Engineer verification caveat wording

{{Article header|eyebrow=EDFM // Engineer|deck=The Dweller is a ship Engineer based at Black Hide in the Wyrd system, specialising in Power Distributor engineering.}}
{{Article status|status=Needs review|mode=Both|version=Live and Legacy; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Location/specialty cross-referenced against Inara; prerequisite/discovery/invitation/unlock detail is single-sourced from a community guide — see Sources|uncertainty=prerequisite, discovery, invitation, and complete blueprint availability — details are treated as community-reported until directly verified; see Sources}}

{{Engineer infobox
|name = The Dweller
}}

The Dweller specialises in Power Distributor modifications for ship-based Engineering.<ref name="inara-list" />

== Location ==
* '''System:''' Wyrd
* '''Facility:''' Black Hide

== How to Discover This Engineer ==
Professor Palin is the referral source for The Dweller.<ref name="wanderer-chain">[https://wanderer-toolbox.com/guides/engineering-unlock/ Engineering Unlock Guide], Wanderer's Toolbox, accessed 2026-08-07.</ref><ref name="inara-list">[https://inara.cz/elite/engineers/ Engineers], Inara, accessed 2026-08-07.</ref>

== How to Receive an Invitation ==
Sell exploration or other data at 5 black markets.<ref name="wanderer-chain" />

== How to Unlock This Engineer ==
# Meet the invitation requirement: sell exploration or other data at 5 black markets.
# Travel to Black Hide in Wyrd.
# Pay '''500,000 CR''' directly at the Engineer's terminal, rather than deliver a physical commodity.
# Confirm access at the Engineer's terminal.

== Engineer Unlock Chain ==
The Dweller's own prerequisite Engineer is not yet verified. He is the referral source for both [[Lei Cheung]] and [[Marsha Hicks]] (the latter in Colonia).<ref name="wanderer-chain" />

== Available Engineering ==
'''Blueprint data pending verification.''' The Dweller's general specialty (Power Distributor) is established, but individual blueprint names and maximum grades have not yet passed EDFM verification — see [[Elite Dangerous Field Manual:Engineering Architecture]] for the site's policy on not inventing unconfirmed specifics. This table will be restored once blueprint-level data is confirmed.<ref name="wanderer-chain" />

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Engineering modifications performed at this workshop increase Engineer reputation through the standard Engineering reputation system. See [[Engineering#Engineer Reputation]] for details.

== Blueprint Pinning ==
{{Fact|1=The Dweller's confirmed specialty is Power Distributor.}}

{{Field manual recommendation|1=Not yet made — a pinning recommendation needs the maximum-grade and full blueprint data filled in first. See [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.}}

== Related Engineers ==
{{Related articles|label=Related Engineers|[[Lei Cheung]] [[Marsha Hicks]]}}

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Core Internal Engineering]]
[[Category:Engineering]]

Terra Velasquez

2026-08-08T21:29:19Z

EDFM Maintenance: Second pass: streamline Engineer verification caveat wording

{{Article header|eyebrow=EDFM // Odyssey Engineer|deck=Mobility and evasion specialist at Rascal's Choice in the Shou Xing system.}}
{{Article status|status=Needs review|mode=Live|version=Odyssey on-foot Engineering; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Location and specialty cross-referenced against Inara's Engineers listing only; discovery, invitation, and unlock requirements have not yet been researched|uncertainty=Discovery requirement, invitation requirement, unlock requirement, prerequisite Engineer, maximum grade, and specific modification names are all not yet researched. Only location and general specialty area are confirmed.}}

{{Infobox
|name = Terra Velasquez
|label1 = Engineer type |row1 = Odyssey (suit / weapon)
|label2 = System |row2 = Shou Xing
|label3 = Settlement |row3 = Rascal's Choice
|label4 = Specialties |row4 = Mobility and evasion
|label5 = Prerequisite Engineer |row5 = Not yet researched
|label6 = Discovery requirement |row6 = Not yet researched
|label7 = Invitation requirement |row7 = Not yet researched
|label8 = Unlock requirement |row8 = Not yet researched
}}

Terra Velasquez specialises in mobility and evasion modifications for suits and handheld weapons.<ref name="inara-list" />

Odyssey Engineering is a separate system from ship Engineering — it modifies suits and handheld weapons rather than ship modules, and exists only in Live (there is no Legacy equivalent). See [[Engineers]] for how the two systems are organised.

== Location ==
* '''System:''' Shou Xing
* '''Settlement:''' Rascal's Choice

== How to Discover This Engineer ==
Not yet researched.<ref name="inara-list">[https://inara.cz/elite/engineers/ Engineers], Inara, accessed 2026-08-07.</ref>

== How to Receive an Invitation ==
Not yet researched.

== How to Unlock This Engineer ==
# Meet the invitation requirement: not yet researched.
# Travel to Rascal's Choice in Shou Xing.
# Meet the unlock requirement: not yet researched.
# Confirm access at the Engineer's terminal.

== Engineer Unlock Chain ==
''No verified multi-Engineer chain to display for this Engineer.''

Prerequisite Engineer, if any, not yet researched.

== Available Engineering ==
{{Draft warning}}
Specific suit/weapon modification names and maximum grades were not confirmed in the sources checked for this pass — see [[Elite Dangerous Field Manual:Engineering Architecture]] for the site's policy on not inventing unconfirmed specifics. Confirmed specialty area: Mobility and evasion.

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at their workshop, in line with the general mechanic covered on the main [[Engineering]] page.

== Blueprint Pinning ==
'''Fact:''' Terra Velasquez's confirmed specialty area is Mobility and evasion.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the specific modification and maximum-grade data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
''No related Engineers confirmed for this pass.''

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Odyssey Engineering]]
[[Category:Engineering]]

Selene Jean

2026-08-08T21:29:19Z

EDFM Maintenance: Second pass: streamline Engineer verification caveat wording

{{Article header|eyebrow=EDFM // Engineer|deck=Armour and hull reinforcement specialist based in the Kuk system, reached after Tod McQuinn.}}
{{Article status|status=Needs review|mode=Both|version=Live and Legacy; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Location and specialty cross-referenced against Inara's Engineers listing; prerequisite/discovery/invitation/unlock detail drawn primarily from a single community unlock-chain guide — see Sources|uncertainty=Maximum engineering grade and full blueprint names were not found in the sources checked; the prerequisite/discovery/invitation chain is single-sourced and not yet directly verified.}}

{{Infobox
|name = Selene Jean
|label1 = Engineer type |row1 = Ship (optional internal)
|label2 = System |row2 = Kuk
|label3 = Facility |row3 = Prospector's Rest
|label4 = Specialties |row4 = Armour, Hull Reinforcement Package
|label5 = Prerequisite Engineer |row5 = [[Tod "The Blaster" McQuinn]]
|label6 = Discovery requirement |row6 = Referral from Tod McQuinn
|label7 = Invitation requirement |row7 = Mine or refine 500 or more tonnes of ore
|label8 = Unlock requirement |row8 = Deliver 10 units of Painite
}}

Selene Jean specialises in armour, hull reinforcement package modifications. They're reached through [[Tod "The Blaster" McQuinn]]. See Engineer Unlock Chain below for their relationship to [[Bill Turner]] and [[Didi Vatermann]].<ref name="inara-list" />

== Location ==
* '''System:''' Kuk
* '''Facility:''' Prospector's Rest

== How to Discover This Engineer ==
Referral from Tod McQuinn.<ref name="wanderer-chain">[https://wanderer-toolbox.com/guides/engineering-unlock/ Engineering Unlock Guide], Wanderer's Toolbox, accessed 2026-08-07.</ref><ref name="inara-list">[https://inara.cz/elite/engineers/ Engineers], Inara, accessed 2026-08-07.</ref>

== How to Receive an Invitation ==
Mine or refine 500 or more tonnes of ore.<ref name="wanderer-chain" />

== How to Unlock This Engineer ==
# Have [[Tod "The Blaster" McQuinn]] unlocked and build reputation with them to trigger the referral.
# Meet the invitation requirement: mine or refine 500 or more tonnes of ore.
# Travel to Prospector's Rest in Kuk.
# Deliver **10 units of Painite** — a mineable commodity.
# Confirm access at the Engineer's terminal.

== Engineer Unlock Chain ==
{{Unlock chain|Tod "The Blaster" McQuinn|Selene Jean|Bill Turner}}

Selene Jean sits between [[Tod "The Blaster" McQuinn]] and both [[Bill Turner]] and [[Didi Vatermann]] — the latter two are parallel referrals from her, not a further single-line chain.<ref name="wanderer-chain" />

== Available Engineering ==
{| class="wikitable"
! Module !! Notes !! Maximum grade
|-
| Armour || Resistance and other variants || To be confirmed
|-
| Hull Reinforcement Package || Resistance and other variants || To be confirmed
|}
Full blueprint names and maximum grades were not confirmed to the same depth as the core chain pages for this pass — see [[Elite Dangerous Field Manual:Engineering Architecture]] for the site's policy on not inventing unconfirmed specifics.<ref name="wanderer-chain" />

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at their workshop, in line with the general mechanic covered on the main [[Engineering]] page.

== Blueprint Pinning ==
'''Fact:''' Selene Jean's confirmed specialties are Armour, Hull Reinforcement Package, per [[#Available Engineering|Available Engineering]] above.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the maximum-grade and full blueprint data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
{{Related articles|label=Related Engineers|[[Tod "The Blaster" McQuinn]] [[Bill Turner]] [[Didi Vatermann]]}}

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Optional Internal Engineering]]
[[Category:Engineering]]

Rosa Dayette

2026-08-08T21:29:18Z

EDFM Maintenance: Second pass: streamline Engineer verification caveat wording

{{Article header|eyebrow=EDFM // Odyssey Engineer|deck=Range and targeting specialist at Rosa's Shop in the Kojeara system, Colonia region.}}
{{Article status|status=Needs review|mode=Live|version=Odyssey on-foot Engineering; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Location and specialty cross-referenced against Inara's Engineers listing only; discovery, invitation, and unlock requirements have not yet been researched|uncertainty=Discovery requirement, invitation requirement, unlock requirement, prerequisite Engineer, maximum grade, and specific modification names are all not yet researched. Only location and general specialty area are confirmed.}}

{{Infobox
|name = Rosa Dayette
|label1 = Engineer type |row1 = Odyssey (suit / weapon)
|label2 = System |row2 = Kojeara
|label3 = Settlement |row3 = Rosa's Shop
|label4 = Specialties |row4 = Range and targeting
|label5 = Prerequisite Engineer |row5 = Not yet researched
|label6 = Discovery requirement |row6 = Not yet researched
|label7 = Invitation requirement |row7 = Not yet researched
|label8 = Unlock requirement |row8 = Not yet researched
}}

Rosa Dayette specialises in range and targeting modifications for suits and handheld weapons.<ref name="inara-list" />

Odyssey Engineering is a separate system from ship Engineering — it modifies suits and handheld weapons rather than ship modules, and exists only in Live (there is no Legacy equivalent). See [[Engineers]] for how the two systems are organised.

== Location ==
* '''System:''' Kojeara
* '''Settlement:''' Rosa's Shop
* '''Region:''' Colonia — this Engineer is only reachable after making the long journey to the Colonia region, separate from the core bubble.

== How to Discover This Engineer ==
Not yet researched.<ref name="inara-list">[https://inara.cz/elite/engineers/ Engineers], Inara, accessed 2026-08-07.</ref>

== How to Receive an Invitation ==
Not yet researched.

== How to Unlock This Engineer ==
# Meet the invitation requirement: not yet researched.
# Travel to Rosa's Shop in Kojeara.
# Meet the unlock requirement: not yet researched.
# Confirm access at the Engineer's terminal.

== Engineer Unlock Chain ==
''No verified multi-Engineer chain to display for this Engineer.''

Prerequisite Engineer, if any, not yet researched.

== Available Engineering ==
{{Draft warning}}
Specific suit/weapon modification names and maximum grades were not confirmed in the sources checked for this pass — see [[Elite Dangerous Field Manual:Engineering Architecture]] for the site's policy on not inventing unconfirmed specifics. Confirmed specialty area: Range and targeting.

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at their workshop, in line with the general mechanic covered on the main [[Engineering]] page.

== Blueprint Pinning ==
'''Fact:''' Rosa Dayette's confirmed specialty area is Range and targeting.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the specific modification and maximum-grade data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
''No related Engineers confirmed for this pass.''

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Odyssey Engineering]]
[[Category:Engineering]]

Ram Tah

2026-08-08T21:29:17Z

EDFM Maintenance: Second pass: streamline Engineer verification caveat wording

{{Article header|eyebrow=EDFM // Engineer|deck=Defensive and utility module specialist based in the Meene system, reachable through Lei Cheung.}}
{{Article status|status=Needs review|mode=Both|version=Live and Legacy; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Location and specialty cross-referenced against Inara's Engineers listing; prerequisite/discovery/invitation/unlock detail drawn primarily from a single community unlock-chain guide — see Sources|uncertainty=Maximum engineering grade and full blueprint names were not found in the sources checked.}}

{{Infobox
|name = Ram Tah
|label1 = Engineer type |row1 = Ship (optional internal)
|label2 = System |row2 = Meene
|label3 = Facility |row3 = Phoenix Base
|label4 = Specialties |row4 = Frame Shift Drive Interdictor, Kill Warrant Scanner
|label5 = Prerequisite Engineer |row5 = [[Lei Cheung]]
|label6 = Discovery requirement |row6 = Referral from Lei Cheung
|label7 = Invitation requirement |row7 = Not yet confirmed
|label8 = Unlock requirement |row8 = Deliver 50 units of Classified Scan Databanks
}}

Ram Tah specialises in frame shift drive interdictor, kill warrant scanner modifications. They're reached through [[Lei Cheung]].<ref name="inara-list" />

== Location ==
* '''System:''' Meene
* '''Facility:''' Phoenix Base

== How to Discover This Engineer ==
Referral from Lei Cheung.<ref name="wanderer-chain">[https://wanderer-toolbox.com/guides/engineering-unlock/ Engineering Unlock Guide], Wanderer's Toolbox, accessed 2026-08-07.</ref><ref name="inara-list">[https://inara.cz/elite/engineers/ Engineers], Inara, accessed 2026-08-07.</ref>

== How to Receive an Invitation ==
Not yet confirmed.<ref name="wanderer-chain" />

== How to Unlock This Engineer ==
# Have [[Lei Cheung]] unlocked and build reputation with them to trigger the referral.
# Meet the invitation requirement: not yet confirmed.
# Travel to Phoenix Base in Meene.
# Deliver **50 units of Classified Scan Databanks** — a data-type material.
# Confirm access at the Engineer's terminal.

== Engineer Unlock Chain ==
''No verified multi-Engineer chain to display for this Engineer.''

Ram Tah is reachable through [[Lei Cheung]].<ref name="wanderer-chain" />

== Available Engineering ==
{| class="wikitable"
! Module !! Notes !! Maximum grade
|-
| Kill Warrant Scanner || Range and other variants || To be confirmed
|}
Full blueprint names and maximum grades were not confirmed to the same depth as the core chain pages for this pass — see [[Elite Dangerous Field Manual:Engineering Architecture]] for the site's policy on not inventing unconfirmed specifics.<ref name="wanderer-chain" />

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at their workshop, in line with the general mechanic covered on the main [[Engineering]] page.

== Blueprint Pinning ==
'''Fact:''' Ram Tah's confirmed specialties are Frame Shift Drive Interdictor, Kill Warrant Scanner, per [[#Available Engineering|Available Engineering]] above.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the maximum-grade and full blueprint data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
{{Related articles|label=Related Engineers|[[Lei Cheung]]}}

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Optional Internal Engineering]]
[[Category:Engineering]]

Professor Palin

2026-08-08T21:29:16Z

EDFM Maintenance: Second pass: streamline Engineer verification caveat wording

{{Article header|eyebrow=EDFM // Engineer|deck=Thruster specialist based in the Arque system, reached after Marco Qwent.}}
{{Article status|status=Needs review|mode=Both|version=Live and Legacy; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Location and specialty cross-referenced against Inara's Engineers listing; prerequisite/discovery/invitation/unlock detail drawn primarily from a single community unlock-chain guide — see Sources|uncertainty=Maximum engineering grade and full blueprint names were not found in the sources checked.}}

{{Infobox
|name = Professor Palin
|image = Professorpalin.png
|label1 = Engineer type |row1 = Ship (core internal)
|label2 = System |row2 = Arque
|label3 = Facility |row3 = Abel Laboratory
|label4 = Specialties |row4 = Thrusters
|label5 = Prerequisite Engineer |row5 = [[Marco Qwent]]
|label6 = Discovery requirement |row6 = Referral from Marco Qwent
|label7 = Invitation requirement |row7 = Travel 5,000 Ly from your starting location before the referral triggers
|label8 = Unlock requirement |row8 = Deliver 25 units of Sensor Fragments
}}

Professor Palin specialises in thrusters modifications. They're reached through [[Marco Qwent]].<ref name="inara-list" />

== Location ==
* '''System:''' Arque
* '''Facility:''' Abel Laboratory

== How to Discover This Engineer ==
Referral from Marco Qwent.<ref name="wanderer-chain">[https://wanderer-toolbox.com/guides/engineering-unlock/ Engineering Unlock Guide], Wanderer's Toolbox, accessed 2026-08-07.</ref><ref name="inara-list">[https://inara.cz/elite/engineers/ Engineers], Inara, accessed 2026-08-07.</ref>

== How to Receive an Invitation ==
Travel 5,000 Ly from your starting location before the referral triggers.<ref name="wanderer-chain" />

== How to Unlock This Engineer ==
# Have [[Marco Qwent]] unlocked and build reputation with them to trigger the referral.
# Meet the invitation requirement: travel 5,000 Ly from your starting location before the referral triggers.
# Travel to Abel Laboratory in Arque.
# Deliver **25 units of Sensor Fragments** — the same requirement reported for [[Chloe Sedesi]].
# Confirm access at the Engineer's terminal.

== Engineer Unlock Chain ==
{{Unlock chain|Marco Qwent|Professor Palin}}

Professor Palin is reached through [[Marco Qwent]]. No further Engineer has been confirmed as reachable specifically through Professor Palin in the sources checked this pass.<ref name="wanderer-chain" />

== Available Engineering ==
{| class="wikitable"
! Module !! Notes !! Maximum grade
|-
| Thrusters || Speed and other variants || To be confirmed
|}
Full blueprint names and maximum grades were not confirmed to the same depth as the core chain pages for this pass — see [[Elite Dangerous Field Manual:Engineering Architecture]] for the site's policy on not inventing unconfirmed specifics.<ref name="wanderer-chain" />

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at their workshop, in line with the general mechanic covered on the main [[Engineering]] page.

== Blueprint Pinning ==
'''Fact:''' Professor Palin's confirmed specialties are Thrusters, per [[#Available Engineering|Available Engineering]] above.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the maximum-grade and full blueprint data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
{{Related articles|label=Related Engineers|[[Marco Qwent]]}}

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Core Internal Engineering]]
[[Category:Engineering]]

Petra Olmanova

2026-08-08T21:29:16Z

EDFM Maintenance: Second pass: streamline Engineer verification caveat wording

{{Article header|eyebrow=EDFM // Engineer|deck=Defensive module specialist based at Sanctuary in the Colonia region, reachable through Tod McQuinn.}}
{{Article status|status=Needs review|mode=Both|version=Live and Legacy; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Location and specialty cross-referenced against Inara's Engineers listing; prerequisite/discovery/invitation/unlock detail drawn primarily from a single community unlock-chain guide — see Sources|uncertainty=Maximum engineering grade and full blueprint names were not found in the sources checked; the prerequisite/discovery/invitation chain is single-sourced and not yet directly verified.}}

{{Infobox
|name = Petra Olmanova
|label1 = Engineer type |row1 = Ship (optional internal)
|label2 = System |row2 = Asura
|label3 = Facility |row3 = Sanctuary
|label4 = Specialties |row4 = Hull Reinforcement Package, Module Reinforcement Package
|label5 = Prerequisite Engineer |row5 = [[Tod "The Blaster" McQuinn]]
|label6 = Discovery requirement |row6 = Referral from Tod McQuinn
|label7 = Invitation requirement |row7 = Combat rank Expert or higher
|label8 = Unlock requirement |row8 = Deliver 200 units of Progenitor Cells
}}

Petra Olmanova specialises in hull reinforcement package, module reinforcement package modifications. They're reached through [[Tod "The Blaster" McQuinn]].<ref name="inara-list" />

== Location ==
* '''System:''' Asura
* '''Facility:''' Sanctuary
* '''Region:''' Colonia — this Engineer is only reachable after making the long journey to the Colonia region, separate from the core bubble.

== How to Discover This Engineer ==
Referral from Tod McQuinn.<ref name="wanderer-chain">[https://wanderer-toolbox.com/guides/engineering-unlock/ Engineering Unlock Guide], Wanderer's Toolbox, accessed 2026-08-07.</ref><ref name="inara-list">[https://inara.cz/elite/engineers/ Engineers], Inara, accessed 2026-08-07.</ref>

== How to Receive an Invitation ==
Combat rank Expert or higher.<ref name="wanderer-chain" />

== How to Unlock This Engineer ==
# Have [[Tod "The Blaster" McQuinn]] unlocked and build reputation with them to trigger the referral.
# Meet the invitation requirement: combat rank Expert or higher.
# Travel to Sanctuary in Asura.
# Deliver **200 units of Progenitor Cells**.
# Confirm access at the Engineer's terminal.

== Engineer Unlock Chain ==
''No verified multi-Engineer chain to display for this Engineer.''

Petra Olmanova is reachable through [[Tod "The Blaster" McQuinn]].<ref name="wanderer-chain" />

== Available Engineering ==
{| class="wikitable"
! Module !! Notes !! Maximum grade
|-
| Hull Reinforcement Package || Resistance and other variants || To be confirmed
|}
Full blueprint names and maximum grades were not confirmed to the same depth as the core chain pages for this pass — see [[Elite Dangerous Field Manual:Engineering Architecture]] for the site's policy on not inventing unconfirmed specifics.<ref name="wanderer-chain" />

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at their workshop, in line with the general mechanic covered on the main [[Engineering]] page.

== Blueprint Pinning ==
'''Fact:''' Petra Olmanova's confirmed specialties are Hull Reinforcement Package, Module Reinforcement Package, per [[#Available Engineering|Available Engineering]] above.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the maximum-grade and full blueprint data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
{{Related articles|label=Related Engineers|[[Tod "The Blaster" McQuinn]]}}

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Optional Internal Engineering]]
[[Category:Engineering]]

Oden Geiger

2026-08-08T21:29:15Z

EDFM Maintenance: Second pass: streamline Engineer verification caveat wording

{{Article header|eyebrow=EDFM // Odyssey Engineer|deck=Accuracy and optics specialist at Ankh's Promise in the Candiaei system.}}
{{Article status|status=Needs review|mode=Live|version=Odyssey on-foot Engineering; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Location and specialty cross-referenced against Inara's Engineers listing only; discovery, invitation, and unlock requirements have not yet been researched|uncertainty=Discovery requirement, invitation requirement, unlock requirement, prerequisite Engineer, maximum grade, and specific modification names are all not yet researched. Only location and general specialty area are confirmed.}}

{{Infobox
|name = Oden Geiger
|label1 = Engineer type |row1 = Odyssey (suit / weapon)
|label2 = System |row2 = Candiaei
|label3 = Settlement |row3 = Ankh's Promise
|label4 = Specialties |row4 = Accuracy and optics
|label5 = Prerequisite Engineer |row5 = Not yet researched
|label6 = Discovery requirement |row6 = Not yet researched
|label7 = Invitation requirement |row7 = Not yet researched
|label8 = Unlock requirement |row8 = Not yet researched
}}

Oden Geiger specialises in accuracy and optics modifications for suits and handheld weapons.<ref name="inara-list" />

Odyssey Engineering is a separate system from ship Engineering — it modifies suits and handheld weapons rather than ship modules, and exists only in Live (there is no Legacy equivalent). See [[Engineers]] for how the two systems are organised.

== Location ==
* '''System:''' Candiaei
* '''Settlement:''' Ankh's Promise

== How to Discover This Engineer ==
Not yet researched.<ref name="inara-list">[https://inara.cz/elite/engineers/ Engineers], Inara, accessed 2026-08-07.</ref>

== How to Receive an Invitation ==
Not yet researched.

== How to Unlock This Engineer ==
# Meet the invitation requirement: not yet researched.
# Travel to Ankh's Promise in Candiaei.
# Meet the unlock requirement: not yet researched.
# Confirm access at the Engineer's terminal.

== Engineer Unlock Chain ==
''No verified multi-Engineer chain to display for this Engineer.''

Prerequisite Engineer, if any, not yet researched.

== Available Engineering ==
{{Draft warning}}
Specific suit/weapon modification names and maximum grades were not confirmed in the sources checked for this pass — see [[Elite Dangerous Field Manual:Engineering Architecture]] for the site's policy on not inventing unconfirmed specifics. Confirmed specialty area: Accuracy and optics.

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at their workshop, in line with the general mechanic covered on the main [[Engineering]] page.

== Blueprint Pinning ==
'''Fact:''' Oden Geiger's confirmed specialty area is Accuracy and optics.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the specific modification and maximum-grade data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
''No related Engineers confirmed for this pass.''

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Odyssey Engineering]]
[[Category:Engineering]]

Mel Brandon

2026-08-08T21:29:14Z

EDFM Maintenance: Second pass: streamline Engineer verification caveat wording

{{Article header|eyebrow=EDFM // Engineer|deck=Laser and shield specialist based at The Brig in the Colonia region, reachable through Elvira Martuuk.}}
{{Article status|status=Needs review|mode=Both|version=Live and Legacy; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Location and specialty cross-referenced against Inara's Engineers listing; prerequisite/discovery/invitation/unlock detail drawn primarily from a single community unlock-chain guide — see Sources|uncertainty=Maximum engineering grade and full blueprint names were not found in the sources checked; the prerequisite/discovery/invitation chain is single-sourced and not yet directly verified.}}

{{Infobox
|name = Mel Brandon
|label1 = Engineer type |row1 = Ship (weapon / optional internal)
|label2 = System |row2 = Luchtaine
|label3 = Facility |row3 = The Brig
|label4 = Specialties |row4 = Lasers, Shields
|label5 = Prerequisite Engineer |row5 = [[Elvira Martuuk]]
|label6 = Discovery requirement |row6 = Referral from Elvira Martuuk
|label7 = Invitation requirement |row7 = Requires a Colonia Council invitation, obtained by selling exploration data at Dove Enigma in Colonia
|label8 = Unlock requirement |row8 = Deliver bounty vouchers worth 100,000 CR
}}

Mel Brandon specialises in lasers, shields modifications. They're reached through [[Elvira Martuuk]].<ref name="inara-list" />

== Location ==
* '''System:''' Luchtaine
* '''Facility:''' The Brig
* '''Region:''' Colonia — this Engineer is only reachable after making the long journey to the Colonia region, separate from the core bubble.

== How to Discover This Engineer ==
Referral from Elvira Martuuk.<ref name="wanderer-chain">[https://wanderer-toolbox.com/guides/engineering-unlock/ Engineering Unlock Guide], Wanderer's Toolbox, accessed 2026-08-07.</ref><ref name="inara-list">[https://inara.cz/elite/engineers/ Engineers], Inara, accessed 2026-08-07.</ref>

== How to Receive an Invitation ==
Requires a Colonia Council invitation, obtained by selling exploration data at Dove Enigma in Colonia.<ref name="wanderer-chain" />

== How to Unlock This Engineer ==
# Have [[Elvira Martuuk]] unlocked and build reputation with them to trigger the referral.
# Meet the invitation requirement: a Colonia Council invitation, obtained by selling exploration data at Dove Enigma in Colonia.
# Travel to The Brig in Luchtaine.
# Redeem or deliver **bounty vouchers worth 100,000 CR total**.
# Confirm access at the Engineer's terminal.

== Engineer Unlock Chain ==
''No verified multi-Engineer chain to display for this Engineer.''

Mel Brandon is reachable through [[Elvira Martuuk]]. Like the other Colonia Engineers, reaching him also requires the long trip to the Colonia region itself.<ref name="wanderer-chain" />

== Available Engineering ==
{| class="wikitable"
! Module !! Notes !! Maximum grade
|-
| Beam Laser || Damage and other variants || To be confirmed
|-
| Shield Generator || Strength and other variants || To be confirmed
|}
Full blueprint names and maximum grades were not confirmed to the same depth as the core chain pages for this pass — see [[Elite Dangerous Field Manual:Engineering Architecture]] for the site's policy on not inventing unconfirmed specifics.<ref name="wanderer-chain" />

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at their workshop, in line with the general mechanic covered on the main [[Engineering]] page.

== Blueprint Pinning ==
'''Fact:''' Mel Brandon's confirmed specialties are Lasers, Shields, per [[#Available Engineering|Available Engineering]] above.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the maximum-grade and full blueprint data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
{{Related articles|label=Related Engineers|[[Elvira Martuuk]]}}

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Weapon Engineering]]
[[Category:Optional Internal Engineering]]
[[Category:Engineering]]

Marsha Hicks

2026-08-08T21:29:13Z

EDFM Maintenance: Second pass: streamline Engineer verification caveat wording

{{Article header|eyebrow=EDFM // Engineer|deck=Kinetic weapon specialist based at The Watchtower in the Colonia region, reachable through The Dweller.}}
{{Article status|status=Needs review|mode=Both|version=Live and Legacy; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Location and specialty cross-referenced against Inara's Engineers listing; prerequisite/discovery/invitation/unlock detail drawn primarily from a single community unlock-chain guide — see Sources|uncertainty=Maximum engineering grade and full blueprint names were not found in the sources checked; the prerequisite/discovery/invitation chain is single-sourced and not yet directly verified.}}

{{Infobox
|name = Marsha Hicks
|label1 = Engineer type |row1 = Ship (weapon)
|label2 = System |row2 = Tir
|label3 = Facility |row3 = The Watchtower
|label4 = Specialties |row4 = Multi-Cannon, Kinetic weapons
|label5 = Prerequisite Engineer |row5 = [[The Dweller]]
|label6 = Discovery requirement |row6 = Referral from The Dweller
|label7 = Invitation requirement |row7 = Exploration rank Surveyor or higher
|label8 = Unlock requirement |row8 = Deliver 10 tonnes of mined Osmium
}}

Marsha Hicks specialises in multi-cannon, kinetic weapons modifications. They're reached through [[The Dweller]].<ref name="inara-list" />

== Location ==
* '''System:''' Tir
* '''Facility:''' The Watchtower
* '''Region:''' Colonia — this Engineer is only reachable after making the long journey to the Colonia region, separate from the core bubble.

== How to Discover This Engineer ==
Referral from The Dweller.<ref name="wanderer-chain">[https://wanderer-toolbox.com/guides/engineering-unlock/ Engineering Unlock Guide], Wanderer's Toolbox, accessed 2026-08-07.</ref><ref name="inara-list">[https://inara.cz/elite/engineers/ Engineers], Inara, accessed 2026-08-07.</ref>

== How to Receive an Invitation ==
Exploration rank Surveyor or higher.<ref name="wanderer-chain" />

== How to Unlock This Engineer ==
# Have [[The Dweller]] unlocked and build reputation with them to trigger the referral.
# Meet the invitation requirement: exploration rank Surveyor or higher.
# Travel to The Watchtower in Tir.
# Deliver **10 tonnes of mined Osmium**.
# Confirm access at the Engineer's terminal.

== Engineer Unlock Chain ==
''No verified multi-Engineer chain to display for this Engineer.''

Marsha Hicks is reachable through [[The Dweller]].<ref name="wanderer-chain" />

== Available Engineering ==
{| class="wikitable"
! Module !! Notes !! Maximum grade
|-
| Multi-Cannon || Damage and other variants || To be confirmed
|}
Full blueprint names and maximum grades were not confirmed to the same depth as the core chain pages for this pass — see [[Elite Dangerous Field Manual:Engineering Architecture]] for the site's policy on not inventing unconfirmed specifics.<ref name="wanderer-chain" />

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at their workshop, in line with the general mechanic covered on the main [[Engineering]] page.

== Blueprint Pinning ==
'''Fact:''' Marsha Hicks's confirmed specialties are Multi-Cannon, Kinetic weapons, per [[#Available Engineering|Available Engineering]] above.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the maximum-grade and full blueprint data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
{{Related articles|label=Related Engineers|[[The Dweller]]}}

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Weapon Engineering]]
[[Category:Engineering]]

Marco Qwent

2026-08-08T21:29:13Z

EDFM Maintenance: Second pass: streamline Engineer verification caveat wording

{{Article header|eyebrow=EDFM // Engineer|deck=Power Plant specialist based in the Sirius system, reached after Elvira Martuuk.}}
{{Article status|status=Needs review|mode=Both|version=Live and Legacy; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Location and specialty cross-referenced against Inara's Engineers listing; prerequisite/discovery/invitation/unlock detail drawn primarily from a single community unlock-chain guide — see Sources|uncertainty=Maximum engineering grade and full blueprint names were not found in the sources checked; the prerequisite/discovery/invitation chain is single-sourced and not yet directly verified.}}

{{Infobox
|name = Marco Qwent
|label1 = Engineer type |row1 = Ship (core internal)
|label2 = System |row2 = Sirius
|label3 = Facility |row3 = Qwent Research Base
|label4 = Specialties |row4 = Power Plant
|label5 = Prerequisite Engineer |row5 = [[Elvira Martuuk]]
|label6 = Discovery requirement |row6 = Referral from Elvira Martuuk
|label7 = Invitation requirement |row7 = Requires a Sirius Corporation system permit in addition to the referral; specific reputation threshold not yet confirmed
|label8 = Unlock requirement |row8 = Deliver 25 units of Modular Terminals
}}

Marco Qwent specialises in power plant modifications. They're reached through [[Elvira Martuuk]]. See Engineer Unlock Chain below for their relationship to [[Professor Palin]] and [[Chloe Sedesi]].<ref name="inara-list" />

== Location ==
* '''System:''' Sirius
* '''Facility:''' Qwent Research Base

== How to Discover This Engineer ==
Referral from Elvira Martuuk.<ref name="wanderer-chain">[https://wanderer-toolbox.com/guides/engineering-unlock/ Engineering Unlock Guide], Wanderer's Toolbox, accessed 2026-08-07.</ref><ref name="inara-list">[https://inara.cz/elite/engineers/ Engineers], Inara, accessed 2026-08-07.</ref>

== How to Receive an Invitation ==
Requires a Sirius Corporation system permit in addition to the referral; specific reputation threshold not yet confirmed.<ref name="wanderer-chain" />

== How to Unlock This Engineer ==
# Have [[Elvira Martuuk]] unlocked and build reputation with them to trigger the referral.
# Meet the invitation requirement: a Sirius Corporation system permit in addition to the referral; specific reputation threshold not yet confirmed.
# Travel to Qwent Research Base in Sirius.
# Deliver **25 units of Modular Terminals**.
# Confirm access at the Engineer's terminal.

== Engineer Unlock Chain ==
{{Unlock chain|Elvira Martuuk|Marco Qwent|Professor Palin}}

Marco Qwent sits between [[Elvira Martuuk]] and [[Professor Palin]]. He's also the referral source for [[Chloe Sedesi]] near the Witch Head Nebula.<ref name="wanderer-chain" />

== Available Engineering ==
{| class="wikitable"
! Module !! Notes !! Maximum grade
|-
| Power Plant || Output and other variants || To be confirmed
|}
Full blueprint names and maximum grades were not confirmed to the same depth as the core chain pages for this pass — see [[Elite Dangerous Field Manual:Engineering Architecture]] for the site's policy on not inventing unconfirmed specifics.<ref name="wanderer-chain" />

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at their workshop, in line with the general mechanic covered on the main [[Engineering]] page.

== Blueprint Pinning ==
'''Fact:''' Marco Qwent's confirmed specialties are Power Plant, per [[#Available Engineering|Available Engineering]] above.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the maximum-grade and full blueprint data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
{{Related articles|label=Related Engineers|[[Elvira Martuuk]] [[Professor Palin]] [[Chloe Sedesi]]}}

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Core Internal Engineering]]
[[Category:Engineering]]

Lori Jameson

2026-08-08T21:29:12Z

EDFM Maintenance: Second pass: streamline Engineer verification caveat wording

{{Article header|eyebrow=EDFM // Engineer|deck=Scanner and utility module specialist based at Jameson Base in the Shinrarta Dezhra system.}}
{{Article status|status=Needs review|mode=Both|version=Live and Legacy; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Location and specialty cross-referenced against Inara's Engineers listing; prerequisite/discovery/invitation/unlock detail drawn primarily from a single community unlock-chain guide — see Sources|uncertainty=Maximum engineering grade and full blueprint names were not found in the sources checked; the prerequisite/discovery/invitation chain is single-sourced and not yet directly verified.}}

{{Infobox
|name = Lori Jameson
|label1 = Engineer type |row1 = Ship (utility)
|label2 = System |row2 = Shinrarta Dezhra
|label3 = Facility |row3 = Jameson Base
|label4 = Specialties |row4 = Scanners, Utility modules
|label5 = Prerequisite Engineer |row5 = Not yet confirmed
|label6 = Discovery requirement |row6 = Not yet confirmed
|label7 = Invitation requirement |row7 = Elite-level rank requirement in an unspecified activity
|label8 = Unlock requirement |row8 = Deliver 25 units of Kongga Ale
}}

Lori Jameson specialises in scanners, utility modules modifications.<ref name="inara-list" />

== Location ==
* '''System:''' Shinrarta Dezhra
* '''Facility:''' Jameson Base

== How to Discover This Engineer ==
Not yet confirmed.<ref name="wanderer-chain">[https://wanderer-toolbox.com/guides/engineering-unlock/ Engineering Unlock Guide], Wanderer's Toolbox, accessed 2026-08-07.</ref><ref name="inara-list">[https://inara.cz/elite/engineers/ Engineers], Inara, accessed 2026-08-07.</ref>

== How to Receive an Invitation ==
Elite-level rank requirement in an unspecified activity.<ref name="wanderer-chain" />

== How to Unlock This Engineer ==
# Meet the invitation requirement: community sources report an Elite-level rank requirement in an unspecified activity.
# Travel to Jameson Base in Shinrarta Dezhra.
# Deliver **25 units of Kongga Ale** — a rare regional commodity.
# Confirm access at the Engineer's terminal.

== Engineer Unlock Chain ==
''No verified multi-Engineer chain to display for this Engineer.''

Lori Jameson's prerequisite Engineer is not yet confirmed.<ref name="wanderer-chain" />

== Available Engineering ==
{| class="wikitable"
! Module !! Notes !! Maximum grade
|-
| Scanners || Range and other variants || To be confirmed
|}
Full blueprint names and maximum grades were not confirmed to the same depth as the core chain pages for this pass — see [[Elite Dangerous Field Manual:Engineering Architecture]] for the site's policy on not inventing unconfirmed specifics.<ref name="wanderer-chain" />

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at their workshop, in line with the general mechanic covered on the main [[Engineering]] page.

== Blueprint Pinning ==
'''Fact:''' Lori Jameson's confirmed specialties are Scanners, Utility modules, per [[#Available Engineering|Available Engineering]] above.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the maximum-grade and full blueprint data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
''No related Engineers confirmed for this pass.''

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Utility Engineering]]
[[Category:Engineering]]

Liz Ryder

2026-08-08T21:29:11Z

EDFM Maintenance: Second pass: streamline Engineer verification caveat wording

{{Article header|eyebrow=EDFM // Engineer|deck=Explosives and armour specialist based in the Eurybia system, and a starting point for the chain leading to Hera Tani and Broo Tarquin.}}
{{Article status|status=Needs review|mode=Both|version=Live and Legacy; exact patch scope not yet directly verified|reviewed=2026-08-07|reviewer=Desk research; pending direct in-game verification — see Sources|source_quality=Cross-referenced across Inara and community unlock-chain guides for the requirements below; not first-party tested|uncertainty=Maximum engineering grade was not found in the sources checked — see Available Engineering}}

{{Engineer infobox
|name = Liz Ryder
}}

Liz Ryder specialises in explosive weapons and defensive armour — missiles, mine launchers, torpedo pylons, and hull reinforcement/armour plating. She's a second independent starting point alongside [[Felicity Farseer]] (the two don't require each other), and is the Engineer you need before [[Hera Tani]] and, further down the chain, [[Broo Tarquin]] become reachable.<ref name="inara-liz">[https://inara.cz/elite/engineer/5 Liz Ryder — engineer], Inara, accessed 2026-08-07.</ref>

== Location ==
* '''System:''' Eurybia
* '''Facility:''' Demolition Unlimited

== How to Discover This Engineer ==
No discovery step applies — Liz Ryder is known from public sources without needing a referral from another Engineer.<ref name="inara-liz" />

== How to Receive an Invitation ==
Reach '''Cordial''' or '''Friendly''' reputation with the Eurybia Blue Mafia minor faction.<ref name="inara-liz" />

== How to Unlock This Engineer ==
# Reach Cordial or Friendly standing with the Eurybia Blue Mafia.
# Travel to Demolition Unlimited in Eurybia.
# Deliver '''200 units of Landmines''' — a manufactured commodity rather than cargo bought from a market; commonly sourced by destroying other Landmines or from mission rewards.
# Confirm access at the Engineer's terminal.

== Engineer Unlock Chain ==
{{Unlock chain|Liz Ryder|Hera Tani|Broo Tarquin}}

Liz Ryder has no prerequisite Engineer. Reputation grade 3–4 with her opens the referral to [[Hera Tani]], who in turn leads to [[Broo Tarquin]] and, per community chain guides, [[Tiana Fortune]] — the latter relationship hasn't been independently checked for this pass.<ref name="wanderer-chain">[https://wanderer-toolbox.com/guides/engineering-unlock/ Engineering Unlock Guide], Wanderer's Toolbox, accessed 2026-08-07.</ref>

== Available Engineering ==
{| class="wikitable"
! Module !! Blueprint !! Maximum grade
|-
| Abrasion Blaster || Far-reaching || To be confirmed
|-
| Enzyme Missile Rack || High-yield || To be confirmed
|-
| Hull Reinforcement Package || Blast resistant, Heavy duty, Kinetic resistant, Lightweight, Thermal resistant || To be confirmed
|-
| Armour || Blast resistant, Heavy duty, Kinetic resistant, Lightweight, Thermal resistant || To be confirmed
|-
| Mine Launcher || High capacity, Lightweight, Rapid fire, Sturdy || To be confirmed
|-
| Missile Rack || High capacity, Lightweight, Rapid fire, Sturdy || To be confirmed
|-
| Seeker Missile Rack || Drag, High capacity, Lightweight, Lightweight thermal, Lockdown, Rapid fire, Sturdy || To be confirmed
|-
| Torpedo Pylon || Lightweight, Sturdy || To be confirmed
|}
Maximum grade per blueprint wasn't stated on the source checked.<ref name="inara-liz" />

== Experimental Effects ==
To be added — not confirmed in the sources checked for this pass.

== Increasing Engineer Reputation ==
Reputation increases through crafting modifications at her workshop, in line with the general mechanic covered on the main [[Engineering]] page.

== Blueprint Pinning ==
'''Fact:''' Liz Ryder's confirmed specialties are missile/mine/torpedo weapon variants and hull reinforcement/armour modifications, per [[#Available Engineering|Available Engineering]] above.

'''EDFM recommendation:''' Not yet made. A pinning recommendation needs the maximum-grade data above filled in first — see [[Elite Dangerous Field Manual:Engineering Architecture]] for why EDFM treats pinning guidance as editorial judgement, not a database fact.

== Related Engineers ==
{{Related articles|label=Related Engineers|[[Hera Tani]] [[Broo Tarquin]]}}

== Related Guides ==
{{Related articles|[[Engineering]] [[Engineer Unlock Guide]]}}

== Sources ==
<references />

{{Engineering nav}}

[[Category:Engineers]]
[[Category:Weapon Engineering]]
[[Category:Engineering]]