/* Heathen skin for Forgejo (git.heathen.group) — added 2026-07-22, matching the storefront's own
   design tokens (docs/infra/wordpress-bridge/plugin/heathen-account-bridge, --mt-* variables):
   dark background, blue as the primary accent, amber reserved ONLY for the "// Lesser Header"
   text treatment — never as a structural/border color. First pass — Forgejo's real per-page
   markup wasn't fully verified live (local sign-in is intentionally disabled site-wide, so an
   authenticated fetch to check exact classes wasn't done without weakening that), so the "big
   header" selectors below are a best-effort guess at common Fomantic-UI/Forgejo patterns; the
   "// Members"-style rule IS confirmed against real markup (fetched from the public /user/login
   page, which uses the identical `.ui.top.attached.header` component Forgejo reuses for boxed
   section titles like Members/Teams/Labels).
 *
 * REVISED 2026-07-22, same day: the first pass set `--color-secondary` globally to amber, not
 * realizing Forgejo's own theme uses that same variable for ordinary structural borders and
 * table dividers throughout the UI (row/column lines, box outlines), not just the one heading
 * accent it was meant for — result was amber bleeding into places it was never intended (every
 * table cell border, every sidebar box outline). Fixed by: never setting `--color-secondary` at
 * all, applying amber only as an explicit `color` on the specific heading text, and explicitly
 * taming ordinary dividers/borders to something subtle instead of leaving them at Forgejo's
 * (now blue-tinted) default. Outer box borders are now transparent by default — the one visual
 * separator kept is a subtle top blue gradient line, matching the WP storefront's own card style
 * (`.heathen-pricing-card::before` / `.heathen-account-card::before`), not a full outline.
 */

@import url('https://fonts.googleapis.com/css2?family=JetBrains+Mono:wght@400;500;600;700&display=swap');

:root {
	--color-primary: #38bdf8 !important;
	--color-primary-dark-1: #0ea5e9 !important;
	--color-primary-dark-2: #0284c7 !important;
	--color-primary-light-1: #7dd3fc !important;
	/* Deliberately NOT overriding --color-secondary (see revision note above) — amber is applied
	   explicitly, only where intended, further down. */
}

body {
	font-family: "JetBrains Mono", ui-monospace, SFMono-Regular, "SF Mono", Menlo, Consolas, monospace;
}

a, a:visited { color: #38bdf8; }
a:hover { color: #7dd3fc; }

/* Subtle dividers everywhere by default — table row/column lines, list separators, generic
   Fomantic segment borders. Low-contrast dark, not a saturated color of any kind. Deliberately
   broad (covers the markdown-rendered tables in repo READMEs/the org profile too, which use
   plain <table>/<th>/<td>, not Fomantic classes). */
table, th, td,
.ui.segment,
.ui.attached.segment,
.ui.table,
.ui.table td,
.ui.table th {
	border-color: #1c232c !important;
}

/* Outer box borders — non-existent by default (transparent), replaced with a single subtle top
   accent line in the site's blue, same visual language as the WP storefront's cards. Applies to
   the two most common "boxed section" containers: Fomantic segments (Members/Teams/repo info
   boxes) and top-attached-header combos. */
.ui.segment,
.ui.attached.segment {
	border-left-color: transparent !important;
	border-right-color: transparent !important;
	border-bottom-color: transparent !important;
}
.ui.top.attached.header {
	border-color: transparent !important;
	background: transparent !important;
	border-top: 2px solid #38bdf8 !important;
	padding-top: 0.6em;
}

/* "Lesser headers" — Members, Teams, Labels, and other boxed-section titles all use this same
   Fomantic-UI component. Amber "// " PREFIX ONLY (fixed 2026-07-25, was amber on the whole
   heading text including the word "Members"/"Teams" itself, not just the prefix), heading text
   stays near-white to match the storefront's own heading style
   (.heathen-pricing-card-heading, .heathen-account-heading) — no border/background color
   comes from this rule (see the top-line treatment above instead). */
.ui.top.attached.header {
	color: #f0f4f9 !important;
}
.ui.top.attached.header::before {
	content: "// ";
	color: #fbbf24;
	font-family: "JetBrains Mono", ui-monospace, SFMono-Regular, monospace;
}

/* "Big" page/section headers — repo name, org name. REVISED 2026-07-22: the first two passes at
   this were guesses (`.organization-profile .ui.header`, `.markdown h1/h2`, etc.) that didn't
   match anything real and silently did nothing. Fixed properly this time by pulling Forgejo's
   actual template source for this exact version (v16.0.0) from codeberg.org/forgejo/forgejo
   rather than guessing a third time:
     - Org name ("Heathen Engineering") is a real `<h1>` inside `.org-title`
       (templates/org/header.tmpl) — `.org-title h1` is correct, not the fabricated
       `.organization-profile .ui.header` from the first pass.
     - Repo name ("owner/repo") is NOT an h1 at all — it's two `<a>` tags inside
       `.repo-header .flex-item-title` (templates/repo/header.tmpl).
     - README/markup content (including the org `.profile` page) renders inside a `.markup` div
       (templates/org/home.tmpl: `<div id="readme_profile" class="markup">`) — the previous rule
       targeted `.markdown`, which isn't a real class in this codebase at all. */
.org-title h1,
.repo-header .flex-item-title,
.markup h1,
.markup h2 {
	color: #f0f4f9 !important;
}
.org-title h1::before,
.repo-header .flex-item-title::before,
.markup h1::before,
.markup h2::before {
	content: "[ ";
	color: #38bdf8;
	font-weight: 400;
}
.org-title h1::after,
.repo-header .flex-item-title::after,
.markup h1::after,
.markup h2::after {
	content: " ]";
	color: #38bdf8;
	font-weight: 400;
}