3 Commits

Author	SHA1	Message	Date
admin	fe80548144	website: the header mark had no white fill — wrong source file (and R-916 corrected) ... I used assets/logo_notext.svg for the header mark. That file is the LIGHT-BACKGROUND variant: it has SEVEN #00408d fills and ZERO #ffffff, so on the dark nav the cloud rendered as a hollow outline. The operator caught it. logo_notext_white.svg is not the answer either -- it is a white OUTLINE version, also unfilled. Rendered all four candidates side by side on the real nav background to see it rather than infer it: only logo.svg (and logo.png) carry the real artwork -- white cloud, #051343 house and servers, #008ddf swoosh. FIX: assets/logo-mark.svg, cut from logo.svg -- keep <defs>, path6 and g2; drop the five wordmark paths and the two empty <text> elements; viewBox cropped to the mark (70 0 505 295). Vector, correct fills, no text. All 18 pages point at it; site.css cache-bust v7 -> v8. The CSS comment now says which file NOT to swap back in, and why. AND A CORRECTION THAT REMOVES AN OPERATOR TASK (R-916). That row says the project has no usable vector master because logo.svg "sets felhom.eu as live text" in 'M+ 2c'/'Vremena Grotesk', and it waits on "the machine with the fonts". MEASURED today, while cutting the mark out of that very file: - all five wordmark elements are <path> with real d= geometry - NO <text> element has any content; the two present are empty leftovers - the font-family strings the row cites are Inkscape METADATA left on CONVERTED paths (-inkscape-font-specification). A grep for font-family finds them and reads as live text -- the likeliest way the original diagnosis went wrong. - proof from a renderer that lacks both fonts: Chrome draws logo.svg's lettering identical to logo.png's, side by side. NOT re-tested: librsvg specifically -- DooPlex has no rsvg-convert, inkscape or cairosvg installed today, so the original librsvg/DejaVu observation could not be reproduced either way. It does not change the structural fact: there is no font left to substitute. Consequence: the 645x408 PNG is not the only faithful copy and does not cap picture size. R-916 state -> READY with "re-check before doing any work: this may need nothing from the operator at all", rather than closed on my say-so.	2026-10-09 14:28:22 +02:00
admin	625d38645c	website: one brand lockup in the header, and footer links that look like links ... HEADER. logo.png carries its OWN "felhom.eu" lettering under the mark, so putting it next to a typed <span class="logo-text"> said the name twice and squeezed the mark down to 40px to make room. Now: - the mark alone, bigger: assets/logo_notext.svg at 54px (44px under 600px). Vector, so it stays crisp. Its two <text> elements are EMPTY, so R-916's missing-font problem does not apply to this file -- checked, not assumed. - the name beside it is the brand's OWN lettering, cropped from logo.png to the new assets/logo-wordmark.png (632x108, tight bbox). Why an image and not text: the wordmark's face is "M+ 2c"/"Vremena Grotesk" (R-916). Nothing here has it, and the site deliberately loads NO external font -- the privacy notice published this morning states exactly that, so pulling in Google Fonts to match a logo would have made a published claim false. Using the artwork is also what the Facebook covers already do. The white/blue split the operator asked for is in the artwork itself. Accessibility kept: the mark is alt="" aria-hidden (decorative), the wordmark carries alt="felhom.eu", so the link still has its accessible name. FOOTER. The legal links were unstyled, so the browser painted them default blue and PURPLE once visited. They now follow the site's own convention (.page-kapcsolat .sidebar-card a): --blue-bright, no underline, underline on hover. :visited is pinned to the same colour deliberately -- a legal link that changes colour after one read looks like it stopped working. The same fix applied to .legal a on the two new legal pages, which had --blue instead of --blue-bright. 18 of 18 pages carry the new lockup; the English pages keep their /en/ logo href. site.css cache-bust v6 -> v7 on all 18, per the website rules. Verified rendered in a browser on both a Hungarian and an English page: both images load, no .logo-text left anywhere, footer links computed rgb(46,168,245). site_gates OK (nav/footer per language, BOM, cache-busting, twins).	2026-10-09 13:47:22 +02:00
admin	30b932bb10	website: publish the closed-test legal set (R-813 narrowed) ... Two new Hungarian pages, live on push: /adatkezeles (privacy notice) and /feltetelek (what the free closed test is, and is not). Operator rulings of 2026-10-09: no company exists yet, so the operator is named as a PRIVATE PERSON with no postal address and no phone; publish before the lawyer has seen it, because the site was collecting data with no notice at all; the full ASZF, the impresszum and the review wait for the company (R-802, R-809). - All 18 pages carry the operator, info@felhom.eu and both links in the footer. Counted, not assumed: 18 pages found = 18 with both links = 18 structurally valid. English footers say the legal texts are Hungarian. - The contact form stopped claiming something untrue. The old consent said "az adatokat harmadik felnek nem adjuk ki" while Resend, Cloudflare and Google carry the message. Both languages replaced; the link opens in a new tab so a filled form is not lost. - site_gates.py NO_TWIN gains the two pages ON PURPOSE, with the reason in a comment: an unreviewed English legal text would be worse than an honest pointer from the English footer. - documentation/legal/{adatkezelesi-tajekoztato,feltetelek}-1.0.md are the text of record, DERIVED from the published HTML so they cannot drift. The drafts are kept and marked superseded for the closed test. FOUR LOAD-BEARING CLAIMS WERE MEASURED, not copied from a vendor or a README: cookies zero, and no local storage - checked in the browser WITH A POSITIVE CONTROL (a probe cookie WAS visible to the same method) after the tracker fired; no Set-Cookie on any response beacon the exact Umami payload: site id, screen, language, title, url, referrer - no visitor identifier Cloudflare DNS only: the public A record 37.191.56.193 is not a Cloudflare address, so site traffic cannot be proxied fsn1 Falkenstein, Germany (Hetzner's own location list) Also measured: felhom-ep0-copy-gc.timer is installed and RAN SUCCESSFULLY (2026-10-09 08:00, exit 0), so "deleted within 30 days" is true today where on 2026-10-08 it was written but not switched on. Three retentions are stated as having NO deadline, deliberately and with the operator's word: website statistics, web server logs and contact messages have no automatic deletion, and the pages say so instead of promising a date nothing enforces. Every other period is enforced by configuration and cited. No placeholder survived onto either page (0 of "[[", control: the draft still has 36). The impresszum and the full ASZF are NOT published. R-813 -> NARROWED. R-915 unblocked: the operator enters the two URLs in the Meta app's Basic settings; the Live switch stays a separate decision. R-917 and R-920 -> DEFERRED on the operator's (c): park, publish as posts once posting starts.	2026-10-09 12:11:37 +02:00