Embed a share in another page
Show a share inline in a blog post, a wiki or a doc, with a ready-made embed snippet or a plain link.
A share can also be dropped into another page (a blog post, a Notion doc, a CMS article, an internal wiki), so the content shows up inline instead of as a link the reader has to click. Every share URL has an embeddable twin at /embed:
<iframe src="https://yardmaster.io/s/<token>/embed" width="600"
height="400" frameborder="0" loading="lazy" title="Your share label"></iframe>Copy an embed snippet#
You don't have to type the snippet.
Open Shares in the sidebar and select the share.
Next to Copy URL in the detail pane's header, click Copy embed code.
Paste the ready-to-paste
<iframe>into the other page. It is sized 600×400, with your share's label as the frame title.
The button only appears when the share is actually embeddable: add a password, turn on Google sign-in, hit the view cap, revoke it or let it expire and the button disappears.
What does an embedded share look like?#
The embedded view is the same content with the chrome trimmed down: no Yardmaster header, just your artifact and a thin footer with an Open in Yardmaster link that opens the full share in a new tab.
It runs no scripts of its own, and it follows the host page's light/dark setting rather than forcing its own, so it looks native in a dark blog and native in a light one. Embedded views don't count against a View cap; only someone actually opening the share page does.
The /embed address is the only part of a share that any other site is allowed to frame. Every other share URL refuses to load inside someone else's page, which is what stops a look-alike site from wrapping your share in its own branding or clickjacking a viewer.
Why won't a locked share embed?#
A share that is password protected, Google sign-in only, revoked, expired, or at its view cap will not embed. Instead of your content the frame gets a short refusal page: "This share is not available to embed" for a password-protected, Google sign-in only or view-capped share, and the ordinary revoked / expired notice for the other two.
(Most browsers will show the host page's blocked-frame treatment rather than the notice itself, because a refusal page is not allowed to be framed either.)
The rule is simply that gating a share always beats embedding it: if the gate would stop someone opening the link directly, putting the link in a frame must not get them past it. The preview card is different because it never contains any of your content in the first place, so a locked share can still unfurl, it just can't be embedded.
Some publishing platforms can embed a link with no snippet at all: you paste the plain URL and the platform works out how to render it. That's a standard called oEmbed, and Yardmaster supports it.
Every share page Yardmaster composes advertises the endpoint in its markup, so a platform that speaks oEmbed discovers it on its own. Paste the ordinary share URL there and you get the embedded view, sized 600×400, with the preview card as its thumbnail.
If a platform asks for the older XML flavour of oEmbed instead of JSON, Yardmaster politely declines: JSON is the only format it speaks.
For the preview card a link shows in chat apps, see Send a share.
Related
- Share a conversation as a linkTurn an AI session, one message or a highlighted part into a read-only web page anyone can open.
- Share a file or page as a linkPublish a file or pasted content as a public link anyone can open in a browser, and find everything else you can do with a share.
- Choose who can open a shareSet an expiry, a password, a view cap or Google sign-in on a share, and revoke or delete it when you are done.