
Security News
The Changelog Podcast: Practical Steps to Stay Safe on npm
Learn the essential steps every developer should take to stay secure on npm and reduce exposure to supply chain attacks.
@automattic/social-previews
Advanced tools
A suite of components to generate previews for a post for both social and search engines.
This package contains low level components that can be used to display an approximation of how a given post might like look when viewed on various social media / search platforms.
At the current time there are components to display previews for:
Your application must be able to load Sass/SCSS files. You may implement this however you like.
node-sass or read the
CRA documentation on
sass for more
info.Here's a simple usage example using the preview component for Facebook:
import { FacebookPreviews } from '@automattic/social-previews';
<FacebookPreviews
title="Five for the Future"
description="Launched in 2014, Five for the Future encourages organizations to contribute five percent of their resources to WordPress development. WordPress co-founder Matt Mullenweg proposed this benchmark to maintain a “golden ratio” of contributors to users."
url="https://wordpress.org/five-for-the-future/"
user={ { displayName: 'Matt Mullenweg' } }
/>;
Here is another example using the Search result component:
import { GoogleSearchPreview } from '@automattic/social-previews';
<GoogleSearchPreview
title="Five for the Future"
description="Launched in 2014, Five for the Future encourages organizations to contribute five percent of their resources to WordPress development. WordPress co-founder Matt Mullenweg proposed this benchmark to maintain a “golden ratio” of contributors to users."
url="https://wordpress.org/five-for-the-future/"
siteTitle="Five for the Future"
/>;
Twitter previews support the same properties for previewing a single tweet, but can also preview multiple tweets in the form of a Twitter thread. For that, the tweets property takes an array of tweets. Each item in this array can take additional information about the tweet, giving the preview a more native feel.
import { TwitterPreviews } from '@automattic/social-previews';
const tweetTemplate = {
date: Date.now(),
name: 'My Account Name',
profileImage: 'https://abs.twimg.com/sticky/default_profile_images/default_profile_bigger.png',
screenName: '@myAccount',
};
<TwitterPreviews
tweets={ [
{
...tweetTemplate,
text: 'This is the first tweet in a thread, it only has text in it.',
},
{
...tweetTemplate,
text: 'The second tweet has some images attached, too!',
media: [
{
alt: 'The alt text for the first image.',
url: 'https://url.for.the/first/image.png',
type: 'image/png',
},
{
alt: 'The alt text for the second image.',
url: 'https://url.for.the/second/image.png',
type: 'image/png',
},
],
},
] }
/>;
An example of LinkedIn preview
import { LinkedInPreviews } from '@automattic/social-previews';
<LinkedInPreviews
jobTitle="Job Title (Company Name)"
image="https://url.for.the/image.png"
name="LinkedIn Account Name"
profileImage="https://static.licdn.com/sc/h/1c5u578iilxfi4m4dvc4q810q"
title="Post title goes here"
text="The text of the post goes here."
/>;
Tumblr preview
import { TumblrPreviews } from '@automattic/social-previews';
<TumblrPreviews
title="Five for the Future"
description="Launched in 2014, Five for the Future encourages organizations to contribute five percent of their resources to WordPress development. WordPress co-founder Matt Mullenweg proposed this benchmark to maintain a “golden ratio” of contributors to users."
image="https://url.for.the/image.png"
url="https://wordpress.org/five-for-the-future/"
user={ { displayName: 'Matt Mullenweg' } }
customText="Some custom text here"
/>;
There are a number of common properties used across all components:
title - the title of the post being previewed.description - a longer description of the post being previewed.url - the full URL of the post being previewed.In addition each individual component accepts optional additional properties that may be specific to their given platform (eg: image, author...etc).
Note that due to limits enforced by each given platform some strings may need to be truncated. Each component has its individual rules governing the number of characters in a given field allowed before truncation occurs. Limits are typically higher for description fields and shorter for title fields. Truncation by SPACE character is preferred, but where that is not possible a hard truncation is imposed. In both cases an ellipsis character (…)`is appended to the end of the string to indicate that a truncation has occurred.
FAQs
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Learn the essential steps every developer should take to stay secure on npm and reduce exposure to supply chain attacks.

Security News
Experts push back on new claims about AI-driven ransomware, warning that hype and sponsored research are distorting how the threat is understood.

Security News
Ruby's creator Matz assumes control of RubyGems and Bundler repositories while former maintainers agree to step back and transfer all rights to end the dispute.