Files
felhom.eu/marketing/facebook/README.md
T
admin a76207945e
gates / gates (push) Successful in 4m31s
marketing/facebook: the phone check ran after all — the cover IS cut on phones (R-919)
Your suggestion to use DevTools device mode was right; "cannot be checked" was
too quick a conclusion. On an emulated Pixel 9 (412x924, mobile UA, with a
reload so Facebook serves the mobile bundle) the Page's mobile header renders
412x274 = 1.504:1. Facebook keeps the cover's full height and shows only the
centre 938 px of its 1640 px width -- 351 px off each side. build.py's safe
area leaves 306 px clear per side, 45 px too few, and the light text in
cover-c.png runs x333..x997 against a left crop edge of x351, so 18 px are lost:
the headline reads "aját szabályaid" and the wordmark "elhom.eu" on every phone.

Nothing re-cropped on Facebook (the task's fence). The fix is build.py's safe
area (<=938 px, ~900 for margin) plus the measured 172 px centred phone profile
circle, then a hand re-upload. R-919 opened; R-918 closed and moved to
CLOSED-ITEMS with the recipe that made the check possible.

Meta's help page is wrong about Meta's own rendering: it states 2.4:1 for the
mobile cover where the header measures 1.504:1, so this session's first-pass
arithmetic -- explicitly labelled arithmetic, not a check -- under-predicted the
crop about fivefold. That is recorded rather than quietly deleted.

Also: the evidence secret scan needed --exclude=README.md, because that README
quotes the search strings and was matching itself (4 false EAA hits, 1 false
access_token); with the exclusion, control 1 -> 0 and no real hit. And the
Business & legal section header was already miscounted before this session
(said 9/P2 4, actually held 10/P2 5) -- corrected; five other section headers
drift too and are named in the report, left for a session that owns the register.
2026-10-08 21:50:57 +02:00

84 lines
5.7 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# 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: 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, both widths:**
- **Computer (1435 px viewport): fine.** The cover renders whole — no crop, no distortion — the cover container
caps at 1250 px, and the profile circle sits 16 px *below* the cover, so it covers no cover text.
- **Phone (emulated Pixel 9, 412 x 924): the cover is CUT — R-919.** The mobile Page header is
**412 x 274 = 1,504:1**, so Facebook keeps the full height and shows only the **centre 938 px of the 1640 px
width (57,2 %)** — **351 px cut from each side**. The safe area below is the centre 1028 x 544, i.e. 306 px
clear of each edge, which is **45 px per side too wide**. In `out/cover-c.png` the light text runs x 333 to
x 997 against a left crop edge of x 351, so **18 px of it are cut**: the headline reads „aját szabályaid" and
the wordmark „elhom.eu" on every phone. The mobile profile circle is **172 px and centred**, hiding source
x 637–1030 x y 369–624 — part of the dashboard picture, no text.
**So `build.py`'s safe area is wrong for phones** and needs narrowing to the centre **≤ 938 px at full height**
(use ~900 px for margin), with the phone profile-circle exclusion widened to the measured centred 172 px shape —
shown failing on today's covers first. **Meta's stated mobile ratio of 2,4:1 is not what the Page header does**
(1,504:1 measured), which is why a figure from Meta's page is not a substitute for looking at the Page. Getting
Facebook's phone layout at all needs DevTools device mode **plus a reload**; the audit's README has the recipe.
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.