10.0.2 • Public • Published

o-share MIT licensed

Social media buttons.


  • Provides the ability to share a URL provided by the product
  • Uses a standard set of social media icons.


Check out how to include Origami components in your project to get started with o-share.


Include the complete markup, available in the Origami registry directly to:

<!-- see the registry demos for full markup -->
<div data-o-component="o-share" class="o-share">
  <!-- a share to X action example -->
  <!-- href tag is not shown, see the registry demos for full markup  -->
  <li class="o-share__action">
   <a class="o-share__icon o-share__icon--x"
    <span class="o-share__text">X</span>
  <!-- more o-share actions -->

The different social networks are (in the order suggested by the design team):

  • Twitter
  • Facebook (note: Facebook doesn't accept meta data attributes in the same way as the other sharing services, instead the Facebook Crawler uses internal heuristics to make a best guess about the title, description, and preview image for your content. You can provide specifics for these attributes to facebook by using Open Graph meta tags)
  • Linkedin
  • Whatsapp (note: this link does nothing if Whatsapp is not installed)
  • Pinterest


Add the o-share--small class for smaller icons. This is useful when including multiple instances of o-share to share items within a page, rather than to share the current page itself.

-<div data-o-component="o-share" class="o-share">
+<div data-o-component="o-share" class="o-share o-share--small">
 <!-- more o-share markup -->

Open In A New Tab

Social share actions open in the same frame, but you may add target="_blank" to the <a> element if your project requires share links are opened in a new tab/window where supported.

Text Labels

Add the o-share__action--labelled class to any share action to display the action text alongside the icon. We recommend this for custom actions which are less recognisable compared with big social media brands, as shown below.

-<li class="o-share__action">
+<li class="o-share__action o-share__action--labelled">

Custom Actions

Form markup is allowed within the o-share__action label to to handle custom share actions.

<!-- see the registry demos for full markup -->
<li class="o-share__action o-share__action--labelled">
  <!-- demo only: forms with a submit button may be used for custom actions -->
  <form method="post" action="#">
    <button type="submit" class="o-share__icon o-share__icon--share" title="[Describe your custom action]" aria-label="[Describe your custom action]">
      <span class="o-share__icon__image">
        <!-- custom svg icon -->
      <span class="o-share__text" data-variant-label="">Custom Action</span>

The share icon is made available by default for custom share features as shown in the Origami registry demos.


@import '@financial-times/o-share/main';

The oShare mixin is used to output the o-share styles.

@include oShare();

We recommend passing the oShare mixin an optional argument $opts, to specify styles granularly and keep your CSS bundle small.

For example:

@include oShare($opts: (
 'sizes': ('small'), // output styles for a small variation of o-share i.e. o-share--small
 'vertical': true, // output styles for a vertical o-share i.e. o-share--vertical
 'icons': ('x', 'facebook', 'whatsapp') // output styles for select share icons

All $opts options include:

  • icons (list) a list of social share icons to output. One or more of the following, or any o-icon name:
    • x
    • facebook
    • linkedin
    • link
    • share
    • mail
    • pinterest
    • whatsapp
  • sizes (list, optional) output styles for different size variants of o-share
    • small - a variant to make o-share smaller than default, i.e. o-share--small
  • vertical (boolean) - Whether to output styles for the vertical variant, i.e o-share--vertical
  • inverse (boolean) - Whether to output the inverse theme for dark backgrounds, i.e o-share--inverse

Colour Usecases

o-share sets custom colour usecases for matching the colour of share buttons. These usecases are limited, for example they do not provide colours for the inverse variant, and not recommended for new projects (it is possible to output custom icons using the oShare mixin, without matching colours).

Usecase Property Uses
o-share/default-icon background, border, text Default colours, used by icons without a state (e.g. before hover).
o-share/ft-icon background, border, text Colours to highlight FT icon social buttons like email (e.g. on hover).
o-share/[social-icon-name]-icon background, border, text Colours to highlight social buttons with a brand, like Twitter (e.g. o-share/x-icon on hover).

Use the oColorsByUsecase mixin from o-colors to retrieve custom colour usecases set by o-share.

.my-icon:hover {
 background-color: oColorsByUsecase('o-share/ft-icon', 'background');


To instantiate the JavaScript:

import oShare from '@financial-times/o-share';
var oShareInstance = new oShare(document.querySelector('[data-o-component=o-share]'));

The markup will be generated for that instance of o-share.

You can also instantiate all instances in your page by running oShare.init which returns an array with all of them.

Alternatively, an o.DOMContentLoaded event can be dispatched on the document to run #init():

document.addEventListener("DOMContentLoaded", function() {
 document.dispatchEvent(new CustomEvent('o.DOMContentLoaded'));

Check out the API docs


The following events are fired by o-share.


oShare.ready fires when a o-share instance has been initialised.

The event provides the following properties:

  • detail.share - The initialised o-share instance.


oShare.open fires when a social network share action is triggered, to open a new window.

The event provides the following properties:

  • detail.share - The o-share instance.
  • detail.action - The kind of share i.e. "social".
  • detail.url - The social share url opened.

TSX Template

o-share component publishes TSX templates to NPM and can be consumed by importing tsx template from our source directory:

import { Share } from "@financial-times/o-share/src/tsx/share";
import { ShareIcon } from "@financial-times/o-share/src/tsx/shareIcon";

<Share {...ShareProps}>
 <ShareIcon {...ShareIconProps} />

The prop Types for each component:

interface ShareProps {
 small?: boolean;
 vertical?: boolean;
 inverse?: boolean;

interface ShareIconProps {
 icon: "x" | "facebook" | "linkedin" | "whatsapp";
 urlProps: {
  url: string;
  title: string;
  titleExtra: string;
  summary: string;
  relatedXAccounts: string;
 showLabel?: boolean;
 label?: string;

TSX template doesn't import styles and doesn't initialise javaScript by itself. For implementation examples we recommend to look at our storybook code.

Migration guide

State Major Version Last Minor Release Migration guide
✨ active 9 N/A migrate to v10
⚠ maintained 9 9.0 migrate to v9
╳ deprecated 8 8.3 migrate to v8
╳ deprecated 7 7.6 migrate to v7
╳ deprecated 6 6.5 migrate to v6
╳ deprecated 5 5.0 migrate to v5
╳ deprecated 4 4.0 migrate to v4
╳ deprecated 3 3.0 migrate to v3
╳ deprecated 2 2.1 -
╳ deprecated 1 1.7 -


If you have any questions or comments about this component, or need help using it, please either raise an issue, visit #origami-support or email Origami Support.


This software is published by the Financial Times under the MIT licence.

Package Sidebar


npm i @financial-times/o-share

Weekly Downloads






Unpacked Size

59 kB

Total Files


Last publish


  • robgodfrey
  • robertboulton
  • seraph2000
  • hamza.samih
  • notlee
  • emmalewis
  • aendra
  • the-ft
  • rowanmanning
  • chee
  • alexwilson