feat(footer): render the global footer from the shared web component

[ch264]

Stacked on #195 (navbar), so the diff below is templates/footer.hbs only. #195 adds the bundle that registers this element — merge it first.

Replaces ~360 lines of hand-inlined markup that duplicated the marketing site's footer with the shared <postman-footer> from postman-eng/marketing-global-navbar-footer.

Client-mounted, unlike the navbar

There is no prerendered fragment here. The footer is below the fold and not LCP-critical, so the element reserves height via --pm-footer-min-height and fills in on mount.

That reserve is partial, not exact — an earlier draft of this description claimed "no layout shift", which measurement doesn't support. The component's default reserve is 320px, while the mounted footer is ~647px on desktop and ~1348px on mobile, so mount grows the page. Because it's below the fold this costs scroll position rather than CLS on the initial view.

Not a regression from this PR or from the version bump: the same 320px default under-reserved at 1.0.6 too, by more (682 / 1517px). Left unfixed here on purpose — a per-consumer override bakes in a number that goes stale on the next parity change, and every consumer would pick their own. It belongs in the component's default. If support needs it solved sooner, the note in footer.hbs says what to do (override behind a media query, not one value for both breakpoints).

It needs no script of its own: the bundle that hydrates the navbar in templates/document_head.hbs registers both elements.

No host attribute — it falls back to location.origin, and support.postman.com is not www-family, so internal links resolve absolute to https://www.postman.com/….

emit-jsonld stays on (the default). Unlike the docs site, this help center has no competing SiteNavigationElement data of its own, so letting the component emit it is a net gain rather than a duplicate.

language-switcher stays off (also the default) — see below.

Carried over: Do Not Sell / Share

Projected into the component's privacy slot, unchanged — same handleDoNotSellClick, same viewState: 'DoNotSellExplainer', same Transcend guard.

That guard is not decorative. script.js injects airgap.js async (gated on the TR param), so a fast click can beat window.transcend into existence; the console.warn path is what the previous footer did too. Behaviour is identical.

Deliberately not carried over

The Privacy Policy link and the copyright line. The shared footer renders both, to the same privacy.postman.com/policies/ target, and computes the year itself — which also retires the DOMContentLoaded script that patched #current-year. Worth noting the old markup had it hardcoded to 2024, so this is a fix, not just a move.

Destination diff

Walked the real data structures rather than grepping for href — the shared footer's links are objects resolved through resolveHref, and social links use a flat url, so a regex under-reports. 49 destinations vs 53 today.

Mostly this help center's copy was stale and the shared footer is what www.postman.com serves now:

Renamed	case-studies → customer-stories · trust → security · product/what-is-postman → product · youtube.com/c/Postman → youtube.com/postman
New	product/agent-mode · product/api-catalog · events · outbound buildwithfern.com
Dropped, no equivalent	product/governance · product/postbot · product/tools · student-program · templates

Those five dropped links are the ones worth a support opinion — they're gone because www's own footer no longer lists them, but if support traffic depends on any of them, say so and they can be added to the shared footer for every property rather than re-inlined here. The new outbound buildwithfern.com link is also worth a look if third-party links in the footer are a concern.

One cosmetic inconsistency inherited from the shared data: explore/mcp-servers has no trailing slash while this footer used explore/mcp-servers/. It redirects; I'd rather fix it upstream than diverge here.

Re-checked against 3.0.0 and the table above is unchanged — still 49 destinations, same five columns, every rename / addition / drop still exactly as listed, mcp-servers trailing slash included.

Pinned version

Inherits 3.0.0 from #195. The follow-up this section used to describe — "bump to 1.0.8 once tagged" — is done and then some; see #195 for what's in the range and for the one breakpoint change that affects the theme.

Two things in that range touch the footer specifically:

Labels changed, targets didn't. 2.0.0 split the visible label from the JSON-LD name, so the footer now reads "App Security" / "About" / "Academy" where it read "App Security APIs" / "About Postman" / "Postman Academy" — matching what www.postman.com renders. The longer SEO names survive in the emitted SiteNavigationElement. (The old long labels were also an EN-only bug: Japanese read the translation bundle and already rendered the short form, so the two locales disagreed about what the footer said.)

A built-in language switcher exists now, and this PR leaves it off. It's opt-in, so saying nothing already gives the right behaviour — but "never considered" and "considered and declined" look identical in a diff, so: its options resolve to the locale's site root on a foreign host, not to a translation of the current page. On a support page that control would read as a page-language toggle and actually be an exit to www.postman.com/jp/. Worth turning on only alongside a decision about localized /hc/ URLs.

Verified against the live 3.0.0 bundle

Headless Chromium, templates rendered the way Zendesk would: mounts with all five columns and 50 anchors (the 49 destinations above plus the logo's link home), the Do Not Sell button is assigned to the privacy slot and visible, JSON-LD emitted exactly once, copyright computes 2026, no language switcher rendered, no page errors at 1440 / 1180 / 390px.

How to test this PR with an AI prompt

Paste this into Claude Code at the repo root:

Check out this branch and start the theme preview with npm run dev (needs ZAT; see README), then start local preview at https://<subdomain>/hc/admin/local_preview/start. Verify: (1) the footer renders at the bottom of a help center article with all its link columns; (2) measure the mount jump — reload with DevTools network throttling and record how far the page grows when the footer fills in; expect roughly 320px reserved against ~647px desktop / ~1348px mobile actual, and confirm that below-the-fold growth is acceptable rather than a visible jump on the first screen; (3) every internal link points at absolute https://www.postman.com/…, not a support.postman.com path; (4) the "Do Not Sell or Share My Personal Information" button opens the Transcend consent manager, and if you block transcend-cdn.com in the Network tab it logs a warning instead of throwing; (5) the copyright line shows the current year, not 2024; (6) exactly one Privacy Policy link is present, not two; (7) document.querySelectorAll('script[type="application/ld+json"]') contains one SiteNavigationElement block and the page has no other one competing with it; (8) no language switcher control appears in the footer. Report anything that fails with the console output.

Open question

Same as #195: does this help center serve translated content? If it's English-only in practice, both elements want translate="false". The footer renders English today either way, since locale is unset and no /hc/en-us/ path parses as a locale prefix — so this is a declaration to make, not a bug to fix.