Web Social Share is a Web Component to share urls and content on social networks.

The component will present a dialog which will contains the different sharing options you selected.

• Web Social Share
  • Goals
  • Installation
  • Integration
  • Getting Started
    • show
    • share
      • Example
      • Vanilla JS
  • Slots
    • Styling your icons
  • Theming
  • Events
  • Fallback and detection
  • Web Share API
  • Showcase
  • Theming
  • Credits
  • License

The idea behind this web component was to add a "social share" feature to Progressive Web Apps (pwa).

Nowadays, the Web Share API is supported by most recent mobile OS. Even though, it may remain interesting to use such a component for the desktop version of web apps.

$ npm install web-social-share

This Web Component is developed with Stencil.

The Stencil documentation provide examples of Javascript and framework integration for Angular, React, Vue and Ember.

The Web Social Share Component can be use like following:

<web-social-share show="true" share="options"></web-social-share>

or in an Angular application:

<web-social-share [show]="true" [share]="options" (closed)="close()"></web-social-share>

Both show and share are mandatory.

Trigger the display or closing of the action sheet presenting the social-share options you have selected.

show is a boolean parameter

The following share options are supported:

• Facebook
• Twitter
• Email
• Linkedin
• Pinterest
• Reddit
• WhatsApp
• Hacker News
• Copy (to clipboard)

For details about them you could have a look to the interface WebSocialShareInput located under folder src/types/web-social-share/.

share is a parameter of type WebSocialShareInput

For example, if you would like to allow your users to share a website thru Facebook and Twitter, you could define basic options like following:

const share = {
    config: [{
          facebook: {
            socialShareUrl: 'https://peterpeterparker.io'
          }
        },{
          twitter: {
            socialShareUrl: 'https://peterpeterparker.io'
          }
    }]
};

If you would like to display the action default name, you could extend your configuration using the attribute displayNames like the following:

const share = {
    displayNames: true,
    config: [{
          facebook: {
            socialShareUrl: 'https://peterpeterparker.io'
          }
        },{
          twitter: {
            socialShareUrl: 'https://peterpeterparker.io'
          }
    }]
};

Worth to notice, you could also provide your own custom brand name, for example in case you would translate the word Email, for example:

const share = {
    displayNames: true,
    config: [{
          email: {
            brandName: 'E-Mail-Adresse',
            socialShareTo: '[email protected]',
            socialShareBody: 'https://peterpeterparker.io'
          }
    }]
};

For an example of Vanilla JS use, you could have a look to the index.html demo located in this repo under folder src.

Slots has to be used to inject the icons for your actions in the component.

The available slots are: facebook, twitter, pinterest, linkedin, reddit, email, copy and whatsapp.

NOTE: Slot names MUST be lower case.

<web-social-share show="false">
    <i class="fab fa-reddit" slot="reddit" style="color: #cee3f8;"></ion-icon>
</web-social-share>

const share = [{
    reddit: {
      socialShareUrl: 'https://peterpeterparker.io',
      socialSharePopupWidth: 300,
      socialSharePopupHeight: 500
    }
  }
}];

Note that currently you may have to add the style="display: block" on the slotted elements, notably if you would use <ion-icon/>, for them to be shown.

The style of your icons is up to you and have to be applied on the icons provided as slots.

For example:

<web-social-share show="false">
    <i class="fab fa-twitter" slot="twitter" style="color: #00aced; width: 1.4rem;"></i>
</web-social-share>    

The following CSS variables are exposed by the component:

The component trigger an event closed when the modal is close. It is emitted regardless if the user shared or not aka "just" closed it.

@Event() closed(void);

Typically, this use case can be used to post process the data you pass to the component. For example, I use a store to handle these and listen to the event to clean it afterwards.

In an Angular application, the event can be bind as following:

<web-social-share [show]="true" [share]="options" (closed)="close()"></web-social-share>

In Vanilla you need to add a listener:

document.querySelector('web-social-share').addListener('onClosed', () => console.log('Something)');

This component is a dumb component. It don't proceed detection or fallback to anything in case one of the share options would not be supported by the device or browser where the component is used.

For example, the share options "Copy (to clipboard)" use the Web Api Clipboard​.write​Text() which might not be supported. Anyway the action will be displayed and if used by the user, nothing will happen.

When I develop web apps I generally develop a mixed solution between Web Share API and this component. If the Web Share API is supported, and maybe sometimes in combination to detecting desktop or mobile, I use the browser API. But if not supported, I fallback on this component.

If interested to implement such a solution, check out the blog post I published about it

A showcase is available at https://websocialshare.com

The above showcase is the www folder of this project deployed in Firebase. If you clone the repository you could run it locally using npm run start.

I didn't want to reinvent the wheel when it comes to the sharing actions themselves. Therefore I forked the features of angular-socialshare. Kudos to 45kb 👍

MIT © David Dal Busco