website: the tester pages get the design system, and content links stop turning purple
gates / gates (push) Successful in 6m34s

Root cause of "no formatting for the points": .info-card and .highlight-box are
scoped per page (.page-technologiak / .page-biztonsagimentes) and the new pages
carry .page-teszteles, so NONE of the card chrome applied - the sections were
unstyled text runs. The tester pages now join the technologiak scope, whose h3
is a flex row (these headings carry an icon).

Three more gaps the new pages exposed, all fixed site-wide rather than patched:
  - There was no base `a` rule at all, so an inline link in body copy fell back
    to the browser default and changed colour once visited. .legal was the only
    place this had been fixed. /gyik, /technologiak and /biztonsagimentes each
    carry such links and had the same bug.
  - `code` was styled only under .legal.
  - A <ul> inside an info-card was unstyled: wrong colour, wrong indent.

Justified body copy on the tester pages, as asked. NOTE: no other page
justifies today, so this is deliberately scoped to .page-teszteles and can be
rolled out site-wide or dropped in one edit. hyphens:auto, because Hungarian
sets badly when justified without it.

site.css -> v=10 on all 20 pages.

sitemap.xml: BOM removed. Search Console shows the freshly submitted clean
sitemap as "Sikertelen lekeres" with an empty last-read, and a BOM before the
XML declaration is a known irritant for its parser. The file is otherwise valid
(18 <url>, parses, served 200 as application/xml). No gate covers sitemap.xml
and the BOM rule is for website/*.html only.

Facts corrected - there are NO testers (operator, this evening): "Tester 1" is a
disposable virtual box and "Tester 2" is a friend whose machine is unassembled
and switched off. The page said "Nehany hely mar betoltve", which was untrue; it
now says the test is starting and all 5 places are open. Same correction in
OUTREACH.md (five people needed, not three), CONTEXT.md, and the terms-1.1 mail,
which in practice has one recipient, not two. No scheduled post claimed a
filled place, so none needed editing.
This commit is contained in:
2026-10-10 20:40:41 +02:00
parent 8ef7c3a7e2
commit 69035f4af5
25 changed files with 127 additions and 43 deletions
+86 -10
View File
@@ -1191,15 +1191,18 @@ footer a:hover, footer a:focus-visible { text-decoration: underline; }
transition: color 0.2s ease;
}
.page-technologiak .toc-links a:hover { color: var(--text-1); }
.page-technologiak .info-card {
.page-technologiak .info-card,
.page-teszteles .info-card {
background: var(--bg-1);
border: 1px solid var(--line);
border-radius: var(--radius);
padding: 40px;
margin-bottom: 32px;
}
.page-technologiak .info-card:last-child { margin-bottom: 0; }
.page-technologiak .info-card h3 {
.page-technologiak .info-card:last-child,
.page-teszteles .info-card:last-child { margin-bottom: 0; }
.page-technologiak .info-card h3,
.page-teszteles .info-card h3 {
font-size: 1.4rem;
margin-bottom: 20px;
color: var(--text-1);
@@ -1207,23 +1210,29 @@ footer a:hover, footer a:focus-visible { text-decoration: underline; }
align-items: center;
gap: 12px;
}
.page-technologiak .info-card h3 .icon { font-size: 1.6rem; }
.page-technologiak .info-card p {
.page-technologiak .info-card h3 .icon,
.page-teszteles .info-card h3 .icon { font-size: 1.6rem; }
.page-technologiak .info-card p,
.page-teszteles .info-card p {
color: var(--text-2);
font-size: 1rem;
line-height: 1.8;
margin-bottom: 16px;
}
.page-technologiak .info-card p:last-child { margin-bottom: 0; }
.page-technologiak .highlight-box {
.page-technologiak .info-card p:last-child,
.page-teszteles .info-card p:last-child { margin-bottom: 0; }
.page-technologiak .highlight-box,
.page-teszteles .highlight-box {
background: var(--blue-dim);
border: 1px solid var(--blue);
border-radius: var(--radius);
padding: 20px 24px;
margin: 20px 0;
}
.page-technologiak .highlight-box p { color: var(--text-1); margin: 0; }
.page-technologiak .highlight-box strong { color: var(--blue-bright); }
.page-technologiak .highlight-box p,
.page-teszteles .highlight-box p { color: var(--text-1); margin: 0; }
.page-technologiak .highlight-box strong,
.page-teszteles .highlight-box strong { color: var(--blue-bright); }
.page-technologiak .warning-box {
background: var(--bg-1);
border: 1px solid var(--warn);
@@ -1405,7 +1414,8 @@ footer a:hover, footer a:focus-visible { text-decoration: underline; }
.page-technologiak .flow-arrow { transform: rotate(90deg); }
}
@media (max-width: 600px) {
.page-technologiak .info-card { padding: 24px; }
.page-technologiak .info-card,
.page-teszteles .info-card { padding: 24px; }
}
@media (max-width: 900px) {
body.menu-open {
@@ -2126,6 +2136,72 @@ footer a:hover, footer a:focus-visible { text-decoration: underline; }
.legal strong { color: var(--text-1); }
.legal code { font-size: 0.93em; color: var(--text-1); }
.legal a, .legal a:link, .legal a:visited { color: var(--blue-bright); text-decoration: none; }
/* Inline links in body copy, site-wide. There was no base `a` rule at all, so a link inside a
paragraph fell through to the browser default: blue, underlined, and a DIFFERENT colour once
visited. The legal pages were the only place this had been fixed, which is why `/gyik`,
`/technologiak`, `/biztonsagimentes` and `/teszteles` each showed a stray purple link.
Scoped to text containers on purpose: it must not touch the nav, the footer, `.cta-button`,
the contact links or the picture-gallery openers (which wrap an <img> and carry no text). */
.content-section p a:not(.cta-button),
.content-section li a:not(.cta-button),
.info-card a:not(.cta-button),
.highlight-box a:not(.cta-button),
.page-header p a:not(.cta-button) {
color: var(--blue-bright);
text-decoration: none;
border-bottom: 1px solid transparent;
transition: border-color 0.2s ease;
}
.content-section p a:not(.cta-button):visited,
.content-section li a:not(.cta-button):visited,
.info-card a:not(.cta-button):visited,
.highlight-box a:not(.cta-button):visited,
.page-header p a:not(.cta-button):visited { color: var(--blue-bright); }
.content-section p a:not(.cta-button):hover,
.content-section li a:not(.cta-button):hover,
.info-card a:not(.cta-button):hover,
.highlight-box a:not(.cta-button):hover,
.page-header p a:not(.cta-button):hover,
.content-section p a:not(.cta-button):focus-visible,
.content-section li a:not(.cta-button):focus-visible,
.info-card a:not(.cta-button):focus-visible,
.highlight-box a:not(.cta-button):focus-visible { border-bottom-color: var(--blue-bright); }
/* Lists inside an info-card. The card rules styled only h3 and p, so a <ul> fell back to the
browser default: full-strength black-on-dark bullets at the wrong indent. Mirrors `.legal`. */
.info-card ul { margin: 0 0 16px 22px; }
.info-card li { color: var(--text-2); line-height: 1.8; margin-bottom: 9px; }
.info-card li:last-child { margin-bottom: 0; }
.info-card ul:last-child { margin-bottom: 0; }
.info-card strong { color: var(--text-1); }
.info-card em { color: var(--text-2); }
/* `code` was styled only under `.legal`, so an inline code span elsewhere fell back to the
browser's default serif-ish monospace at full size. */
.info-card code,
.content-section p code {
font-family: var(--font-data);
font-size: 0.93em;
color: var(--text-1);
background: var(--bg-2);
border: 1px solid var(--line-soft);
border-radius: var(--radius);
padding: 1px 6px;
}
/* Justified body copy on the tester pages (operator, 2026-10-10). NOTE: no other page justifies
today — this is deliberately scoped so it can be rolled out site-wide in one edit, or dropped,
without touching any page's markup. Hungarian sets badly when justified without hyphenation,
so `hyphens` is on and the pages carry lang="hu"/lang="en" for the dictionary. */
.page-teszteles .info-card p,
.page-teszteles .info-card li,
.page-teszteles .highlight-box p {
text-align: justify;
hyphens: auto;
-webkit-hyphens: auto;
}
.legal a:hover, .legal a:focus-visible { text-decoration: underline; }
.legal-version { padding: 12px 16px; border: 1px solid var(--line); border-radius: var(--radius); }
.legal-callout { padding: 16px; border: 1px solid var(--blue); border-radius: var(--radius); }