Skip to content

Embed a published career on another site - #119

Merged
SoryAK merged 1 commit into
feat/career-history-cleanupfrom
feat/publication-embed
Oct 18, 2026
Merged

SoryAK merged 1 commit into
feat/career-history-cleanupfrom
feat/publication-embed

Conversation

@SoryAK

@SoryAK SoryAK commented Oct 18, 2026

Copy link
Copy Markdown
Owner

A published career can be framed on another site.

  • publicationEmbed in core/ builds the frame address and the iframe snippet. A frame is offered only for a career anyone with the address can open. Private and access-controlled careers get none, and neither does a career without a slug or a known relay address.
  • The publish panel shows the snippet with a Copy frame button, or says why there is no frame.
  • The relay serves ?embed=1 in a compact layout that fits its frame. Its List and Journey links keep the embed view, and public pages send Content-Security-Policy: frame-ancestors * so they can be framed.
  • RELAY_URL sets the public relay address used in the snippet. It reaches the screen as relayOrigin on /api/work-map.

Builds on #118 for its core/index.ts and WorkMap.tsx edits. Merge that first. This PR then shows only the embed changes.

Tests: 327 pass. Type check: only the existing GmailSettings.tsx errors.

The publish panel offers the snippet only for a career anyone with the address can open, and says why otherwise. The relay serves a compact embed view that keeps its List and Journey links, and allows framing.

Co-authored-by: Cursor <cursoragent@cursor.com>
@SoryAK
SoryAK merged commit 027cab5 into feat/career-history-cleanup Oct 18, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant