Giter Club home page Giter Club logo

chat-widget's Introduction

@papercups-io/chat-widget

Papercups chat widget

NPM Downloads JavaScript Style Guide

Demo

Available at https://app.papercups.io/demo

demo

Install

npm install --save @papercups-io/chat-widget

Usage

First, sign up at https://app.papercups.io/register to get your account token. Your account token is what you will use to pass in as the accountId prop below.

Using in HTML

Paste the code below between your <head> and </head> tags:

<script>
  window.Papercups = {
    config: {
      // Pass in your Papercups account token here after signing up
      token: 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx',
      // Specify a Papercups inbox
      inbox: 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx',
      title: 'Welcome to Papercups!',
      subtitle: 'Ask us anything in the chat window below 😊',
      newMessagePlaceholder: 'Start typing...',
      primaryColor: '#13c2c2',
      // Optionally pass in a default greeting
      greeting: 'Hi there! How can I help you?',
      // Optionally pass in metadata to identify the customer
      customer: {
        name: 'Test User',
        email: '[email protected]',
        external_id: '123',
        metadata: {version: 1, plan: 'premium'}, // Custom fields go here
      },
      // Optionally specify the base URL
      baseUrl: 'https://app.papercups.io',
      // Add this if you want to require the customer to enter
      // their email before being able to send you a message
      requireEmailUpfront: true,
      // Add this if you want to indicate when you/your agents
      // are online or offline to your customers
      showAgentAvailability: true,
    },
  };
</script>
<script
  type="text/javascript"
  async
  defer
  src="https://app.papercups.io/widget.js"
></script>

Using in React

Place the code below in any pages on which you would like to render the widget. If you'd like to render it in all pages by default, place it in the root component of your app.

import React from 'react';

import {ChatWidget} from '@papercups-io/chat-widget';

// You can also import the following in v1.1.0 and above:
// import {ChatWidget, ChatWindow, Papercups} from '@papercups-io/chat-widget';
//
// The `ChatWindow` component allows you to embed the chat however you want,
// and the `Papercups` object provides access to functions that can programmatically
// open/close the chat widget, e.g.:
//
// `Papercups.open()` // => opens the chat widget
// `Papercups.close()` // => closes the chat widget
// `Papercups.toggle()` // => toggles (opens or closes) the chat widget

const ExamplePage = () => {
  return (
    <>
      {/*
        Put <ChatWidget /> at the bottom of whatever pages you would
        like to render the widget on, or in your root/router component
        if you would like it to render on every page
      */}
      <ChatWidget
        // Pass in your Papercups account token here after signing up
        token='xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx'
        // Specify a Papercups inbox
        inbox='xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx'
        title='Welcome to Papercups!'
        subtitle='Ask us anything in the chat window below 😊'
        newMessagePlaceholder='Start typing...'
        primaryColor='#13c2c2'
        // Optionally pass in a default greeting
        greeting='Hi there! How can I help you?'
        // Optionally pass in metadata to identify the customer
        customer={{
          name: 'Test User',
          email: '[email protected]',
          external_id: '123',
          metadata: {version: 1, plan: 'premium'}, // Custom fields go here
        }}
        // Optionally specify the base URL
        baseUrl='https://app.papercups.io'
        // Add this if you want to require the customer to enter
        // their email before being able to send you a message
        requireEmailUpfront
        // Add this if you want to indicate when you/your agents
        // are online or offline to your customers
        showAgentAvailability
      />
    </>
  );
};

Options

These are the props you can pass into your <ChatWidget /> React component, or the fields you can specify in your Papercups.config:

Prop Type Value Default
token string Your Papercups account token N/A
inbox string The Papercups inbox you would like messages to flow into (defaults to your primary inbox) N/A
accountId (deprecated) string Your Papercups account token (deprecated: use token field instead) N/A
title string The title in the header of your chat widget Welcome!
subtitle string The subtitle in the header of your chat widget How can we help you?
newMessagePlaceholder string The placeholder text in the new message input Start typing...
emailInputPlaceholder string The placeholder text in the optional email input Enter your email
newMessagesNotificationText string The notification text when new messages arrive and the chat window is closed View new messages
primaryColor string The theme color of your chat widget 1890ff
greeting string An optional initial message to greet your customers with N/A
awayMessage string Replaces the greeting message if outside working hours N/A
showAgentAvailability boolean If you want to show whether you (or your agents) are online or not false
agentAvailableText string The text shown when you (or your agents) are online We're online right now!
agentUnavailableText string The text shown when you (and your agents) are offline We're away at the moment.
customer object Identifying information for the customer, including name, email, external_id, and metadata (for any custom fields) N/A
baseUrl string The base URL of your API if you're self-hosting Papercups https://app.papercups.io
iframeUrlOverride string An override of the iframe URL we use to render the chat, if you chose to self-host that as well https://chat-widget.papercups.io
requireEmailUpfront boolean If you want to require unidentified customers to provide their email before they can message you false
isOpenByDefault boolean If you want the chat widget to open as soon as it loads false
persistOpenState boolean Persists the open state of the chat across pages false
hideToggleButton boolean Hides the toggle button in case you want to open/close programmatically false
hideOutsideWorkingHours boolean Hides the chat widget outside of working hours set in Papercups false
popUpInitialMessage boolean | number Pops up the initial greeting after number milliseconds (or immediately if true) false
customIconUrl string A link to a custom icon image URL N/A
iconVariant 'outlined' | 'filled' The style of the default icon outlined
position 'right' | 'left' The position of the chat on the page right
styles object Inline style overrides for chatContainer, toggleContainer, and toggleButton {}
onChatLoaded ({open, close, identify}) => void Callback fired when chat is loaded, returning some utility functions N/A
onChatOpened () => void Callback fired when chat is opened N/A
onChatClosed () => void Callback fired when chat is closed N/A
onMessageSent (message: Message) => void Callback fired when message is sent N/A
onMessageReceived (message: Message) => void Callback fired when message is received N/A

Development

To build the project, run npm start in the root directory. (If you're running it for the first time, you'll have to run npm install first.)

npm install
npm start

To test it out, use the /example directory:

cd example
npm install
npm start

This will start a development server on http://localhost:3000 by default, and open up the example app in your browser.

Important notes

By default, the example widget points at development servers for the Papercups API (which runs at http://localhost:4000) and the Papercups chat window (which runs at http://localhost:8080). These values are set with the baseUrl and iframeUrlOverride props respectively.

If you want to develop against your account in production, you can update these values to the following:

  • baseUrl: http://app.papercups.io
  • iframeUrlOverride: https://chat-widget.papercups.io

(Note that you can also simply remove these props, since the values above are the defaults.)

You'll also want to update your account token to point to your own account. If you haven't already, create a free account at https://app.papercups.io/register to get started.

Once you have your account token, update the accountId prop to point at yours.

Questions?

If you're having any trouble getting started or just want to say hi, join us on Slack! πŸ‘‹

Submitting a PR

We welcome any contributions! Please create an issue before submitting a pull request.

When creating a pull request, be sure to include a screenshot! 🎨

License

MIT Β© Papercups

chat-widget's People

Contributors

cheeseblubber avatar jyggiz avatar reichert621 avatar shunkakinoki avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

chat-widget's Issues

Papercups widget on React no longer working - Element type is invalid

Server Error

Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.

This error happened while generating the page. Any console logs will be displayed in the terminal window.

Source

../../pages/_document.tsx (91:33) @ Function.getInitialProps

  89 |     }
  90 | 
> 91 |     const { html, head } = await ctx.renderPage({ enhanceApp })
     |                                 ^
  92 |     const styles = [...flush()]
  93 |     return { html, head, styles }
  94 |   }

Call Stack

Function.getInitialProps

pages/_document.js (5:40)

Difficult to find (X) close button

A potential UX issue --- the (X) in the bottom right to close the chat is at an unexpected place

difficult to find close button

I was like "how do I close this?" and kept looking around (my eyes didn't even saccade to the bottom right of the screen as I don't expect actions to be there)

[React Native, Expo] UI elements slide up when keyboard opens?

Encountered this somewhat puzzling UI behaviour: when you start typing and the keyboard slides up, the header and previous messages slide up out of view too?
Would be great to keep as much context as possible for the user - is there a way to do this?

Note this is in React Native on iOS with Expo.

Before:

After:

React Native Support

Hi, I can see that this project uses theme-ui for it's UI. I think it can easily be ported to the react-native using theme-ui-native. It can be on a separate repo but that would mean maintaining the same codebase twice.

And because there are no native modules for this to work, it can be used with expo too. There are not that many chat products that work on the expo.

Timezone issue

I can see Papercups Β· Sent 5 hours ago whenever I open the chat widget (see screenshot attached). I am in IST, so I guess it defaults to GMT.

Screenshot 2020-10-30 at 9 57 55 PM

Typing indicator

It would be really handy to see when the other party is typing.

As the site owner, it might also be nice to see what the user is typing so that I can provide a faster reply.

Widget scrolling broken in Firefox 82 OSX

Scroll behavior is broken in Firefox due to different way it implements flexbox.
Resulting in a double scrollbar and the window is not auto scrolled to the bottom when a client messages.

image

Cause:
#__next, body, html {
display: flex;
flex-direction: column;
}

Fix:
#__next{
display: flex;
flex-direction: column;
}
body, html {
display: flex;
flex-direction: row;
}

Tested in Firefox, Chrome and Safari

Add `styles` prop for easier customization

Rather than requiring devs to override CSS classes, let's add a styles prop that enabled overriding the chat container properties as well as the chat toggle button properties.

For example, something like this should allow devs to render the widget on the left side of the page rather than the right:

styles={{
  container: {left: 20, right: 'auto'},
  button: {left: 20, right: 'auto'}
}}

Support for react 18+

Seems like the widget only has support for react between 16 and 17

When can we expect support for react 18? In the meantime we'll use the raw JS script to add it in as a workaround

npm ERR! node_modules/react
npm ERR!   react@"18.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.0.0 || ^17.0.0" from @papercups-io/[email protected]
npm ERR! node_modules/@papercups-io/chat-widget
npm ERR!   @papercups-io/chat-widget@"*" from the root project

Style newMessagesNotificationText

Would be nice to be able to style "View new messages" component as well. For example to override the primary color or add the background color to the container so you can style it in case you have a different background as I have here

Screenshot 2021-05-07 at 17 34 25

I can imagine it adding it styles attribute newMessagesNotificationContainer like this:

                    <ChatWidget
                            styles={{
                                toggleContainer: {...},
                                chatContainer: {...},
                                toggleButton: {...},
                                newMessagesNotificationContainer: {
                                    color: "#ffffff"
                                },
                            }}

Error: "Attempted to send event papercups:plan with payload {"plan":null} before iframeRef was ready"

Seems like this happens only within the React component implementation, particularly when hooks are being used (e.g. useEffect, useContext)

My suspicion is that the message passing between the iframe and the wrapper component cause this to happen when the component is re-rendered in rapid succession.

Potential solutions:

  • Short term: change error to warning so it doesn't clutter up Sentry
  • Pass some kind of unique identifier to/from the iframe so that we can verify the "correct" iframe is loaded

Add ability to parse Markdown images

Right now if you send an image in markdown (e.g. ![image](https://i.imgur.com/XC13fLf.png)) you get an empty message:

image

Eventhough the papercups backend does not (yet) support uploading images it would be nice to have the ability to send images from a 3rd party service such as Imgur and have them render correctly. This could also be good preparation for when the backend does support images.

Cannot read property 'contentWindow' of undefined

I'm using React with react-helmet to include the scripts and getting a lot of errors via Sentry:

Cannot read property 'contentWindow' of undefined

undefined is not an object (evaluating 'n.iframeRef.contentWindow')

It looks like it's tracing back to

const el = this.iframeRef as any;
el.contentWindow.postMessage({event, payload}, this.getIframeUrl());

<Helmet>
<script>
        {`
          window.Papercups = {
            config: {
              accountId: 'my-account-id',
              title: 'Welcome!',
              subtitle: 'Ask us anything in the chat window below 😊',
              primaryColor: '#1c64f2',
              greeting: '',
              newMessagePlaceholder: 'Start typing...',
              baseUrl: 'https://app.papercups.io'
            },
          };
        `}
      </script>
      <script
        type="text/javascript"
        async
        defer
        src="https://app.papercups.io/widget.js"
      ></script>
    </Helmet>

Does my config look right? Should I switch over to @papercups-io/chat-widget?

Reduce size of bundle

A couple things to try:

  • find a bundle analyzer to let us know what dependencies are the largest
  • try switching from react to preact
  • remove all unused code!

Anything else?

Font customization

Hi. Thanks for your work. I woud like to have a way to set the font (Google fonts) and size to harmonize the design of the chat with the site. See here https://ecordl.ca

Fix/Improve UX on mobile

From email:

I tested this on a physical iphone 6s and it seems that the chat widget doesn’t work. It does not display the keyboard when you try to click and type some text.

High vulnerability detected for axios dependency

When I run yarn audit I get the following high vulnerability report:

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ high          β”‚ Incorrect Comparison in axios                                β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ Package       β”‚ axios                                                        β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ Patched in    β”‚ >=0.21.2                                                     β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ Dependency of β”‚ frontend                                                     β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ Path          β”‚ frontend > @papercups-io/chat-widget > @papercups-io/browser β”‚
β”‚               β”‚ > axios                                                      β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ More info     β”‚ https://www.npmjs.com/advisories/1005018                     β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Add option to hide widget outside working hours

Let's add a new prop: hideOutsideWorkingHours.

If this is true, we'll check the widget settings settings.account?.is_outside_working_hours and completely hide the widget if this value is true.

Only render ~20 most recent messages

(Note: the code for this lives in the https://github.com/papercups-io/chat-window repo)

Only load the remaining messages if the customer scrolls up.

The problem we're trying to solve is that when too many messages are rendered, it slows down the animation of new messages being displays. So my thinking is that even if we have 100 messages in this.state.messages, we don't need to render them all.

Open to other solutions as well!

Using the chat widget with different backends like Twilio

I'm a Twilio user and looking to provide a chat experience on our web platform. The widget looks awesome, would it be possible to use it outside of the Papercup ecosystem - ie integrate with Twilio APIs for the messaging layer?

Persist open/closed state across pages

If a user opens/closes the chat widget on one page and then navigates to another page, it should remain in the same state.

(This is particularly important when defaulting the chat to "open", because it's annoying to have to keep closing it on every new page.)

[Question] Is there a way to have multiple chats for a single user's browser session?

I am trying to let a single browser user have multiple, isolated chat sessions at once, on different web pages on the same domain. Is there a way to force this to happen? I am happy for them, for the moment, to appear as multiple customers.

I have tried to provide a different external_id in the config in each place when I would like an isolated/seperate chat session. The call to https://app.papercups.io/api/customers/identify sends the unique external_id but then always returns the same customer_id.

It's a great piece of software -- looking forward to using it more!

Fix some potential iframe security issues

Google Ads is flagging the widget for some reason, need to figure out exactly what is causing this...

TODOs:

React: Could not resolve dependency

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"^17.0.2" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.0.0" from @papercups-io/[email protected]
npm ERR! node_modules/@papercups-io/chat-widget
npm ERR!   @papercups-io/chat-widget@"^1.1.10" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See C:\Users\karti\AppData\Local\npm-cache\eresolve-report.txt for a full report.

Installing with --legacy-peer-deps breaks craco

Add sound on new notifications

It's hard to tell sometimes if a new message has arrived in the chat widget. Let's add a small sound like we do in the dashboard.

Export ChatWindow component

Hello there!

My team is using this module to talk to a custom papercups instance.

We'd like to make sure our users aren't running external code as much as possible, which is why we chose papercups.

However when using this module, we noticed that the window is placed in a separate domain. We'd like to place the ChatWindow component within our app code (possibly even using React.lazy and suspense to only load it ondemand much like what the iframe achieved)

The workaround we're currently evaluating is to add this line to the package.json dependencies field:

"chat-widget-raw": "papercups-io/chat-widget#0293e84"

And include that chat-widget-raw module in our typescript loader configuration.

Is there a plan to expose this component in the future?

Thanks in advance :)

Build widget.js

Is there any documentation on how to build the widget.js for HTML sites?

Security concerns

Is the accountId the only thing protecting hackers from accessing our papercups account? Coz that is totally insecure.

Seems to me the best solution for you would be some kind of Auth0 integration.

Chat content does not display correctly in Firefox

Using Firefox 80.0 (64-bit) on a mac, I try to load the chat widget on this page and this is what I see:

no chat contents

Its weird because the iframe src URL seems to have the right content when opened in a separate window.

Some more context about js lib versions:

yarn list --depth 0 | grep '\(webpack\|paper\|react\)'
β”œβ”€ @mdx-js/[email protected]
β”œβ”€ @papercups-io/[email protected]
β”œβ”€ [email protected]
β”œβ”€ [email protected]
β”œβ”€ [email protected]
β”œβ”€ [email protected]
β”œβ”€ [email protected]
β”œβ”€ [email protected]
β”œβ”€ [email protected]
β”œβ”€ [email protected]
β”œβ”€ [email protected]
β”œβ”€ [email protected]
β”œβ”€ [email protected]
β”œβ”€ [email protected]
β”œβ”€ [email protected]
β”œβ”€ [email protected]
β”œβ”€ [email protected]
β”œβ”€ [email protected]

Widget is not working on IE11

Seems like our widget is breaking on Internet Explorer 😒

(Seems to be related to the framer-motion dependency)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.