# marketing — CHANGELOG ## facebook — the Page's settings set by hand, and Meta's size page read first-hand (2026-10-08, evening) Ran `marketing/facebook/TASK-page-setup-windows.md` from the Windows workstation through Claude in Chrome. Evidence: `documentation/audits/facebook-page-setup-2026-10-08/`; report: `REPORT-facebook-page-setup.md`. - **Done, each read back from a different channel than the edit.** Intro → `COPY.md` §1 (Graph `about` now hex-equal to §1, 99 chars); action button → „További információ" at `https://felhom.eu/`; Messenger welcome → `COPY.md` §3, hex-equal, automation **on**; Page username → **`felhom.eu`**, so the Page now answers at `facebook.com/felhom.eu` (Graph `username` confirms it). The operator typed the password Facebook demanded for the username; nothing else needed a human. - **Not done — `COPY.md` §2 has no field to go in.** Facebook's current Pages experience has no long-description field anywhere, and the Graph `description` reads `null` and is not writable with the robot key's scopes. Filed **R-917** with four options; §2 stays in `COPY.md` unused. `facebook/README.md`'s „What goes where" row says so. - **`facebook/README.md` sizes grade: „READ, second-hand" → „READ, Meta's help page" — and the comparison went the other way.** Meta's page (facebook.com/help/125379114252045, quoted verbatim in the audit) carries **none** of the 820 x 312 / 640 x 360 figures the section asserted; only the 176 px profile size matched, and Meta's mobile profile overlap is ~40 px where we assumed 24. Meta's own page contradicts itself (16:9 on a computer, 2,4:1 on a phone, one 2,70:1 file recommended for both). What we build is unchanged. - **Measured on the live Page** at a 1435 px viewport: the cover renders whole — no crop, no distortion — the container caps at 1250 px, and the profile circle sits 16 px clear below the cover. The **phone** check was **not** performed: narrowing a desktop browser never gives Facebook's phone layout (**R-918**). - **Gotcha, fixed in the session, no row.** In Business Suite the automatic-reply editor refused the first save with „A módosítás nincs mentve." **and still created the automation and switched it on — carrying Meta's default Hungarian greeting, not ours.** A red error toast was therefore a partial write. Reopening the now-existing automation, pasting §3 again and saving gave „Mentve."; the reopened automation reads back hex-equal. Anyone editing this screen must reopen it and read the text back, not trust either toast. - Nothing was posted; no ad, no boost, no Meta Verified; the Meta app stays in development mode. ## facebook — the Page's pictures and texts (2026-10-08) - `marketing/facebook/build.py` (Pillow only) makes `out/profile-dark.png` + `out/profile-white.png` (932 x 932, the logo PNG placed unscaled), three covers `out/cover-{a,b,c}.png` (1640 x 624) and `out/preview.html` (self-contained). Checks in the build: profile circle (today's shape 6823 pixels outside radius 0.42 x width → new pictures 0), cover safe area + profile-circle clearance (content layer only), sizes read back from the files. The site's tokens and font. - `COPY.md`: intro (99 of 100 characters), long description, Messenger welcome, three first posts — each claim cites its website page; no price. - Fixed in the session: covers B and C first failed the safe-area check (text in the phone profile circle's corner, the frame past the phone crop) and were moved; `logo.svg` renders with the wrong lettering here, so the PNG is the master (R-916).