admin
8664cbda78
Ran marketing/facebook/TASK-page-setup-windows.md from the Windows workstation through Claude in Chrome. Evidence in documentation/audits/facebook-page-setup-2026-10-08/, report in REPORT-facebook-page-setup.md. Done, each read back from a different channel than the edit: the intro is COPY.md §1 (Graph `about` hex-equal, 99 chars); the action button is "További információ" to https://felhom.eu/; the Messenger welcome is COPY.md §3 (hex-equal) and the automation is on; the username is felhom.eu, so the Page answers at facebook.com/felhom.eu. Not done: COPY.md §2 has no field to go in — Facebook's current Pages experience has no long-description field and the Graph `description` is null and unwritable with the robot key's scopes. R-917, four options, operator's call; no Hungarian copy was shortened. Phase A read Meta's size page first-hand: it carries none of the 820x312 / 640x360 figures our README asserted, and its own two ratios contradict the file it recommends. README's grade and comparison rewritten; what we build is unchanged. Phase C measured the computer width (cover whole, no crop, profile circle 16 px clear). The 390 px phone check was NOT performed: narrowing a desktop browser never gives Facebook's phone layout. R-918. Nothing posted; no ad, no boost, no Meta Verified; the Meta app stays in development mode; no host, guest, box or hub touched.
4.5 KiB
marketing/facebook — the Felhom.eu Facebook Page's pictures and texts
Files the operator uploads and pastes by hand. Nothing here talks to Facebook (the robot posting path is R-914).
Rebuild
python3 marketing/facebook/build.py
One command makes every PNG and out/preview.html, and runs the checks: the profile circle (no logo pixel
outside 0.42 x width; shown failing first on today's shape), the cover safe area (content inside what computer
AND phone show, clear of the profile circle), and the sizes read back from the files. Exit 0 = all passed.
Needs Python 3 + Pillow only. Brand source: website/assets/logo.png (the logo master — see below),
website/assets/site.css tokens, website/assets/fonts/ (Plus Jakarta Sans).
What goes where
| File | Where on the Page |
|---|---|
out/profile-dark.png (recommended) or out/profile-white.png |
Profile picture |
out/cover-a.png / cover-b.png / cover-c.png — pick one |
Cover photo |
COPY.md §1 |
Intro / Bemutatkozás (≤ 100 characters) |
COPY.md §2 |
Nowhere today — the field is gone (R-917). Facebook's current Pages experience has no long-description field: not in the Page's „Névjegy" tab, not in Business Suite's „Oldal módosítása", not in Page settings; the Graph description reads null and writing it needs pages_manage_metadata, which the robot key does not have. Checked 2026-10-08. |
COPY.md §3 |
Messenger welcome message |
COPY.md §4 |
The first three posts, each with its picture |
Open out/preview.html (download it from Gitea, open locally — it is self-contained) to see each picture the way
Facebook shows it.
Sizes used (READ, Meta's help page — and it does NOT confirm most of ours)
Meta's own help page (facebook.com/help/125379114252045) was read first-hand on 2026-10-08 from the Windows
workstation, quoted verbatim in documentation/audits/facebook-page-setup-2026-10-08/A-meta-sizes.md. It does
not carry most of the figures this section used to assert. What it does say: cover 16:9 on a computer and
2,4:1 on a phone, minimum 400 x 150 either way, fastest-loading file sRGB JPG 851 x 315 under 100 kB;
profile picture shown 176 x 176 on a computer, 196 x 196 on a smartphone, 36 x 36 on a feature phone,
best source 320 x 320, cropped to a circle; the profile circle overlaps the cover by about 40 px on mobile;
and PNG beats JPG when the picture carries a logo or text. Meta's page contradicts itself — it gives two
ratios and then recommends one 2,70:1 file for both — so the figures below are kept as ours, not as Meta's.
The second-hand figures this section used to carry (cover shown 820 x 312 on computers, 640 x 360 on phones, profile circle over the cover at 16 px / 176 px and 24 px / 196 px; sources postfa.st, linearity.io, fasturtle.com) appear nowhere on Meta's page; only the 176 px profile size matched. The mobile overlap we assumed, 24 px, is smaller than the ~40 px Meta states.
What we build is unchanged and still safe: the cover at 2 x, 1640 x 624, well above both stated minimums, as PNG; the profile picture 932 x 932, larger than Meta's 320 x 320 recommendation and therefore downscaled, not enlarged. MEASURED on the live Page 2026-10-08 at a 1435 px viewport: the cover renders whole — no crop, no distortion — and the profile circle sits 16 px below the cover, so it covers no cover text. The phone rendering was not measured (R-918); the same audit explains why a narrowed desktop browser cannot show it.
Page about = 100 characters: developers.facebook.com/docs/graph-api/reference/page/ (Meta, first-hand). The
Page's own „Bemutatkozás" editor counts to 255 (seen on screen 2026-10-08); §1 is 99 characters, so neither
limit bites.
The logo master
website/assets/logo.svg is not usable as a master: its „felhom.eu" lettering is live text in the fonts
„M+ 2c" and „Vremena Grotesk", which DooPlex does not have, so any renderer here draws other letters. The PNG
(645 x 408) is placed unscaled, so the profile picture is 932 x 932 — sharp, not enlarged. A vector master with the
lettering converted to paths (Inkscape: Path → Object to Path, on the machine that has the fonts) is R-916.
Cover C
Uses website/assets/dashboard-backups-hu.webp (demo box, already public on the website). The demo box's domain
chip next to the title is covered with the page colour in the copy; the source file is unchanged. No third-party
logo appears in it (app names are text). The Launcher and Apps pictures were not used: they show app logos.