@deployed.md/dpd-implementation-partner-sdk 0.1.0 → 0.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +9 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,6 +1,14 @@
|
|
|
1
1
|
# @deployed.md/dpd-implementation-partner-sdk
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
The official SDK for **Deployed implementation partners**. Add one call to your sign-up flow, and Deployed can help the companies adopting your product roll it out successfully.
|
|
4
|
+
|
|
5
|
+
When a user signs up for your product, your backend sends Deployed their email (plus an optional name and any extra details you choose). Then:
|
|
6
|
+
|
|
7
|
+
- **Every sign-up is recorded** with Deployed under your API key, along with any details you send.
|
|
8
|
+
- **Work emails** (e.g. `jane@acme.com`) get one short introduction from Deployed, your official implementation partner, offering help getting started with your product. Each address is contacted at most once, however many times it signs up.
|
|
9
|
+
- **Personal emails** (Gmail, Outlook, Yahoo, …) are recorded but never emailed.
|
|
10
|
+
|
|
11
|
+
Your sign-up flow never waits on the email: it's sent in the background, and repeat sign-ups are de-duplicated automatically.
|
|
4
12
|
|
|
5
13
|
```
|
|
6
14
|
Your user signs up ──► your server ──(DeployedImplementationSDK + API key/secret)──► Deployed
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@deployed.md/dpd-implementation-partner-sdk",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.1",
|
|
4
4
|
"description": "Record user sign-ups from your app with Deployed: every email is captured and enterprise emails get a Deployed introduction.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"deployed",
|