A link preview is what posts show about one or more embedded links, e.g. a headline, image, summary from the link destination.
Consider showing a link-preview so your reader has some expectation of what they're going to get when they click a link.
How to publish
If you do the usual mark-up your posts with h-entry, specifically:
"p-author h-card"(with at least
And for photo posts, the usual:
Then link-preview parsers will be able to use those to generate link previews of your posts.
How to parse
To parse a link for information to show in its link-preview, do the usual
- parse for an h-entry
Then get the following information from the following microformats parsed properties:
summary(if any), otherwise, text-only value of
content, elided as necessary
A few indieweb sites are figuring out how to better support embedding:
- Tantek: I'm thinking of improving the posting UI on my site, so that when I'm previewing a post before PuSHing and syndicating it out, the post preview UI retrieves the link preview(s) on the server, and then shows them to me as part of the overall post preview before I hit the "Publish" button. When I hit the "Publish" button, the same logic which makes a syndicated copy to Twitter (by calling the Twitter API), and then saves the Twitter copy permalink in my data store, can also save the link preview(s) in the same data store accordingly. just piggybacking the same data store write to file call.
- This is similar to another thing I’ve had on my implementation list for a while, which is a better quoting UI. Specifically, my posting UI detects URIs in my content, loads up previews, allows me to D&D in for link previews, perhaps load the content and allow me to select, D&D for quotations --Waterpigs.co.uk 13:23, 7 March 2013 (PST)
- Kevin Marks built a utopian idea that iframes the site itself as a preview, relying on it using responsive design
Various social network silos (e.g. Facebook, Twitter, Google+) show link previews underneath notes and comments that have one or more URLs, by extracting information from those URLs content and showing a title/summary/photo for those URLs underneath the posted note/comment.
- Supports showing a link-preview of a tweet link, including text of tweet and image in tweet if any, e.g. with one image: 
Facebook has a number of guidelines regarding images in their documentation:
They show different link-preview layouts for images of different resolutions!
- Large ( > 600x315px - both dimensions? > 1200 x 630 preferred "for the best display on high resolution devices")
- image is shown above text from link preview
- Small ( < 600x315px - either dimension? but > 200x200px both dimensions?)
- image is shown next to text from link preview
- None ( < 200x200px - either dimension? )
- no image preview possibly?
There are third-party guidelines that does not follow Facebook's own though:
- AddThis: http://support.addthis.com/customer/portal/articles/1399895-adding-open-graph-tags-using-blogger Suggest including Blogger-thumbnail as image, which by default is 72x72px.
As of (2015?) Twitter *does* support showing a link-preview of a tweet link, e.g. https://twitter.com/t/status/520758106838818816 (they previously didn't)
However, Twitter fails to show a link-preview for many links, resulting in odd link-only cross-posts from Facebook, where presumably the author did see a link-preview (because Facebook looks at far more information for the link-preview than Twitter does)
- ... who's next to make up their own site-specific link preview markup convention?
There have been a couple of open standards created explicitly for information for link previews.
- oEmbed - since 2009. However it requires an extra endpoint (URL, different language(s) etc.)
- OGP - far more well established since it works in HTML, and Facebook immediately shows results using it.
See http://microformats.org/wiki/link-preview-formats for more prior art research.
h-entry is a useful building block for this. E.g.
<body class="h-entry"> is a good simple baseline way to markup data for link previews.
For more details towards the development of a simple link preview standard, see:
Beyond h-entry's existing properties, there may be a need for additional properties to satisfy the same use-cases as documented by the "existing silo support" above.
E.g. most commonly, a thumbnail image to put next to a post, or rather as a publisher to provide a thumbnail / representative / featured image for others to display as part of a link-preview.
WordPress has good prior art here:http://codex.wordpress.org/Post_Thumbnails:
Post Thumbnail, now Featured Image, is an image that is chosen as the representative image for Posts, Pages or Custom Post Types. The display of this image is up to the theme. This is especially useful for "magazine-style" themes where each post has an image.Emphasis and emphasis added.
Thus we can learn from the WordPress's experience and go with their naming of "Featured Image" - although we can simplify that - why limit to an image when some may (and do!) want to feature a video, or an audio playback stream, etc. as demonstrated by the variety of Twitter Cards?
Thus we can introduce a "featured" property for this use-case, expected to be used as a "u-featured" property inside an h-entry that is a URL to the asset to feature for that post. Handling of different types is up to the link-preview displaying client. E.g. it could do different things based on
Content-Type of the URL when requested, or check its file extension (e.g. .gif .jpg .png .mov .mpeg .mp4 .mp3) and provide markup accordingly, just as existing autoembed solutions do.
It seems like an indieweb implementation of a "link preview" feature would need:
- Open way to markup the info on pages that we want to go into a preview (obv min: name, summary, photo). See "simple link preview standard" above.
- OSS library that retrieves a page and generates simple embeddable preview markup. Such a library would return you the markup snippet with preview name/summary/photo - you just need to store that however you store information in your posts, so you can retrieve it from your store rather than the external URL. Ideally the markup snippet returned would support the same format as in #1 so it is completely re-usable without loss of fidelity.
- Exercise for each indieweb implementer: code to store/cache that embeddable markup in your personal post data store so that you can redisplay it without having to rerequest the external URL (has the advantage of snapshotting the preview as of the time you posted the note in case the external URL content changes or dies).
- Link preview validator/previewer - a validator which would parse a URL and show you what preview might result. Note that Twitter has a Twitter Card validator (login required) - we just need to build an indieweb version of it (and not require login).