Say which embed targets we actually verified, and which we only expect to work
The hand-off doc said "Verified places a pasted embed works" and listed seven platforms. The repo holds an artifact for exactly one of them: check:wp-embed renders the real WordPress shortcode against the real built manifest, asserts it emits the same SRI hash the catalog ships, and carries a negative case for a malformed integrity value. Squarespace, Wix, Google Sites, Notion and Trello have no artifact anywhere -- they are third-party platforms nobody here has an account on. The platforms are plausible and the mechanism is identical everywhere: each accepts an HTML snippet or a URL embed over https, which is all the embed code needs. So the list stays, split into what we proved and what we expect. The word "verified" was the part that overreached, and in a doc an inheritor reads as ground truth it means "someone tried this" when nobody did. Worth recording how nearly this hid: grepping the repo for "Squarespace" returns nineteen files and "Wix" twenty-two, which reads like evidence. They are bundled copies of this very paragraph inside built .js files. The claim was confirming itself -- the same shape as a pgrep that matches its own command line.
This commit is contained in:
parent
ad223d3b1a
commit
239a983471
1 changed files with 13 additions and 5 deletions
|
|
@ -157,11 +157,19 @@ The learn‑by‑doing use case this bundler was built for. Five steps, trainabl
|
|||
4. **Embed everywhere.** Press the map's **Share button**: *Share Link* is the map's own page,
|
||||
*Add to Your Website* is the embed code — both carry the full URL of whatever host serves your
|
||||
maps (plus a `utm_source` tag on the generated pages, so every site's traffic is measurable).
|
||||
Verified places a pasted embed works: team websites and WordPress (Custom HTML block),
|
||||
Squarespace (Code block — iframes need a Business or Commerce plan), Wix (Add → Embed → HTML
|
||||
iframe), Google Sites (Insert → Embed → By URL), Notion (`/embed` + the Share Link), and internal
|
||||
boards with an iframe add-on (e.g. Trello's *Card Frames* Power-Up). Rule of thumb: anywhere that
|
||||
accepts an HTML snippet or a URL embed, over https.
|
||||
**WordPress is verified here**: `bun run check:wp-embed` renders the real shortcode against the
|
||||
real built manifest and asserts it emits the same SRI hash the catalog ships, with a negative
|
||||
case for a malformed integrity value. It runs in the build, needs no MySQL or Docker, and is the
|
||||
one embed target this repo can prove on its own.
|
||||
**Expected to work, not tested by us** — each accepts an HTML snippet or a URL embed over https,
|
||||
which is all the embed code needs: Squarespace (Code block — iframes need a Business or Commerce
|
||||
plan), Wix (Add → Embed → HTML iframe), Google Sites (Insert → Embed → By URL), Notion (`/embed`
|
||||
plus the Share Link), and internal boards with an iframe add-on (e.g. Trello's *Card Frames*
|
||||
Power-Up). Rule of thumb: anywhere that accepts an HTML snippet or a URL embed, over https.
|
||||
*(This paragraph said "Verified places a pasted embed works" and listed all seven. Corrected
|
||||
2026-09-23: the repo holds an artifact for exactly one of them. The platforms are plausible and
|
||||
the mechanism is the same everywhere; the word "verified" was the part that overreached, and in a
|
||||
hand-off doc it reads as "someone tried this" when nobody did.)*
|
||||
5. **Train the trainer.** Teach each team to use the Share button to embed the map — then teach
|
||||
them to train the *next* team the same way. The movement doesn't hang on one mobilization
|
||||
team: every team that carries the map can multiply it.
|
||||
|
|
|
|||
Loading…
Reference in a new issue