Welcome!

Imagine Alice creates a module for fetching calendar data from
a Microsoft Exchange Web Service API. However, she's not very good
at UI, and let's the module be used as a library, rather than bind
it to UI components.

Along comes Bob. He's an expert in creating traditionally laid out
calendar UI's, but thinks Ajax, web-API's and authentication is
difficult to work with. He just wants to subscribe to live events
from the calendar to keep the UI up to date.

If Alice and Bob add the option to communicate through NanoQueue,
they will be able to communicate with eachother's modules, even though they
have never talked or met. This means that you can use both of their
modules on your page, with minimal setup, and have them communicate
messages.

Let's see some code:

// Include on the page in the header, before any modules
<head>
...
<script src="nanoqueue.js"></script>
<script src="moduleA.js"></script>
<script src="moduleB.js"></script>
...
</head>
...