sently 0.9.2 → 1.0.0

package/site/content/docs/channels/index.mdx

@@ -6,7 +6,7 @@ source: "README.md"
 ---
 
 Choose a channel sender for the kind of message your application sends.
-Each sender accepts a provider transport, so delivery providers can change without rewriting send calls.
+Each sender accepts a provider transport — retry, fallback, and `SentlyError` codes stay the same as you add channels.
 
 <Callout title="The one rule">Application code calls a sently channel sender; provider-specific code stays in its transport.</Callout>
 
@@ -18,7 +18,7 @@ Each sender accepts a provider transport, so delivery providers can change witho
 | Email | `createMailer` or `createSMTPMailer` | Sender, recipient, subject, and body. |
 | SMS | `createSmsSender` | Recipient number and body. |
 | WhatsApp | `createWhatsAppSender` | Template or text message. |
-| Push | `createPushSender` | Browser subscription, title, and body. |
+| Push | `createPushSender` | Web Push subscription or FCM token, plus title and body. |
 
   </Step>
   <Step title="Wire in a transport">
@@ -52,7 +52,7 @@ await sms.send({
 | `createSMTPMailer` | Yes | Email configured with SMTP host, port, and authentication. |
 | `createSmsSender` | No | SMS with an `SmsTransport`. |
 | `createWhatsAppSender` | No | WhatsApp with a `WhatsAppTransport`. |
-| `createPushSender` | No | Web Push with a `PushTransport`. |
+| `createPushSender` | No | Web Push or FCM with a `PushTransport`. |
 
 ## Troubleshooting
 
@@ -68,6 +68,8 @@ await sms.send({
 ## Learn more
 
 - [Choose an entrypoint](../get-started/entrypoints)
+- [Support matrix](../get-started/support-matrix)
+- [Failover](../guides/failover)
 - [Browse transports](../transports)
 
 ## Next

package/site/content/docs/channels/push.mdx

@@ -1,14 +1,16 @@
 ---
 title: Push
-description: Send encrypted Web Push notifications through a push transport.
+description: Send Web Push or FCM notifications through a push transport.
 icon: Bell
 source: "src/push.ts"
 ---
 
-Use Web Push for browser notifications after a browser has granted permission and returned a subscription.
-The sender passes the subscription and notification payload to a push transport.
+Use push for browser Web Push subscriptions or FCM device tokens.
+The sender passes the target and notification payload to a push transport.
 
-<Callout title="The one rule">Treat subscription endpoints as secrets: they are long-lived delivery tokens.</Callout>
+<Callout title="The one rule">Treat subscription endpoints and device tokens as secrets — they are long-lived delivery credentials.</Callout>
+
+## Quick start
 
 <Steps>
   <Step title="Create a Push sender">
@@ -27,10 +29,11 @@ const push = createPushSender({
 ```
 
   </Step>
-  <Step title="Send to a stored browser subscription">
+  <Step title="Send to a browser subscription or FCM token">
 
 ```ts
-const result = await push.send({
+// Web Push
+await push.send({
   subscription: {
     endpoint: "https://fcm.googleapis.com/fcm/send/example",
     keys: { p256dh: "browser-public-key", auth: "browser-auth-secret" },
@@ -39,7 +42,12 @@ const result = await push.send({
   body: "Your weekly report is ready to view.",
 });
 
-console.log(result.status);
+// FCM (with FcmTransport)
+await push.send({
+  token: deviceRegistrationToken,
+  title: "Report ready",
+  body: "Your weekly report is ready to view.",
+});
 ```
 
   </Step>
@@ -53,15 +61,16 @@ console.log(result.status);
 | `plugins` | `PushPlugin[]` | Optional transforms run before delivery. |
 | `hooks` | `PushHooks` | Optional callbacks for delivery activity. |
 
-## Push and VAPID options
+## Options shapes
 
-| Option | Type | Meaning |
+`PushOptions` is a union:
+
+| Shape | Required target | Transport |
 | --- | --- | --- |
-| `subscription` | `PushSubscription` | Required browser endpoint plus `p256dh` and `auth` keys. |
-| `title`, `body` | `string` | Required notification content. |
-| `data`, `icon` | `Record<string, unknown>`, `string` | Optional application payload and icon URL. |
-| `ttl` | `number` | Optional delivery lifetime in seconds. |
-| `subject` | `string` | Required Web Push contact URI for the VAPID transport. |
+| Web Push | `subscription` | `WebPushTransport` |
+| FCM | `token` | `FcmTransport` |
+
+Shared fields: `title`, `body`, optional `data`, `icon`, `ttl`, `messageId`.
 
 ## Troubleshooting
 
@@ -69,24 +78,25 @@ console.log(result.status);
   <Accordion title="Why does the transport reject my endpoint?">
     Web Push validates subscription endpoint hosts before sending. Add only exact private relay hostnames with `allowedEndpointHosts` when needed.
   </Accordion>
-  <Accordion title="Why is the endpoint redacted in hooks?">
-    The endpoint path can contain a long-lived delivery token, so hook context keeps only a redacted form.
+  <Accordion title="Why does FCM reject my subscription object?">
+    `FcmTransport` requires `token`. Pass a Web Push `subscription` only to `WebPushTransport`.
   </Accordion>
-  <Accordion title="What does verify do?">
-    `push.verify()` delegates to the transport when available; the Web Push transport checks its VAPID credential shape.
+  <Accordion title="Why is the endpoint redacted in hooks?">
+    Endpoint paths and FCM tokens are long-lived credentials, so hook context keeps only a redacted fingerprint.
   </Accordion>
 </Accordions>
 
 ## Learn more
 
 - [Push options](../reference/push-options)
-- [Transport contracts](../reference/transport-contracts)
-- [Web Push interoperability](../guides/webpush-interop)
+- [Web Push](../transports/webpush)
+- [FCM](../transports/fcm)
+- [Failover](../guides/failover)
 - [Hooks](./hooks)
 
 ## Next
 
 <Cards>
   <Card title="Web Push transport" href="/docs/transports/webpush" />
-  <Card title="All transports" href="/docs/transports" />
+  <Card title="FCM transport" href="/docs/transports/fcm" />
 </Cards>

package/site/content/docs/channels/sms.mdx

@@ -77,12 +77,15 @@ Twilio also accepts a default `from` or `messagingServiceSid` when you construct
 ## Learn more
 
 - [SMS options](../reference/sms-options)
-- [Transport contracts](../reference/transport-contracts)
+- [Unifonic](../transports/unifonic)
+- [Decorators](../decorators) — retry / fallback across SMS providers
+- [Channel send result](../reference/channel-result)
 - [Hooks](./hooks)
 
 ## Next
 
 <Cards>
+  <Card title="Unifonic" href="/docs/transports/unifonic" />
   <Card title="SMS transports" href="/docs/transports" />
   <Card title="Provider OTP extras" href="/docs/guides/vendor-extras-otp" />
 </Cards>

package/site/content/docs/decorators/fallback.mdx

@@ -1,34 +1,66 @@
 ---
 title: Fallback
-description: Fail over across ordered email transports.
+description: Fail over through an ordered list of channel transports.
 icon: GitBranch
 source: "src/transports/fallback.ts"
 ---
 
-Fail over across ordered email transports.
+Fail over through an ordered list of transports when the current one errors.
+Works with email, SMS, WhatsApp, and push.
 
-<Callout title="The one rule">Permanent client errors do not fall through by default.</Callout>
+<Callout title="The one rule">Wrap each entry in `RetryTransport` when you want in-provider retries before failover.</Callout>
 
-## Configuration
+## Quick start
 
-Pass a non-empty transport array; options include `shouldFallback`, `onFallback`, and `cooldownMs`.
-
-<Steps><Step title="Wrap an email transport">
+<Steps>
+  <Step title="Build a chain">
 
 ```ts
 import { FallbackTransport } from "sently/transports/fallback";
+import { TaqnyatSmsTransport } from "sently/transports/taqnyat-sms";
+import { UnifonicTransport } from "sently/transports/unifonic";
 
-const transport = new FallbackTransport([primary, secondary], { cooldownMs: 300_000 });
+const transport = new FallbackTransport(
+  [
+    new TaqnyatSmsTransport({ bearerToken: process.env.TAQNYAT_TOKEN!, sender: "MyBrand" }),
+    new UnifonicTransport({ appSid: process.env.UNIFONIC_APPSID!, senderId: "MyBrand" }),
+  ],
+  { cooldownMs: 300_000 },
+);
 ```
 
-</Step><Step title="Create the mailer">
+  </Step>
+  <Step title="Use the matching sender">
 
 ```ts
-const mailer = await createMailer({ transport });
+import { createSmsSender } from "sently/sms";
+
+const sms = createSmsSender({ transport });
 ```
 
-</Step></Steps>
+  </Step>
+</Steps>
+
+## Result fields
+
+Successful sends include `provider` and `providerIndex` for the transport that handled the message.
+
+## Troubleshooting
+
+<Accordions>
+  <Accordion title="Why did it not fail over on 400?">
+    Permanent client errors (400 / 401 / 403) do not fail over by default — they usually fail on every provider.
+  </Accordion>
+</Accordions>
+
+## Learn more
+
+- [Failover guide](/docs/guides/failover) — retry-then-fallback recipes across channels
 
-<Accordions><Accordion title="Does this replace the inner provider?">No. It delegates sends to the wrapped transport.</Accordion></Accordions>
+## Next
 
-<Cards><Card title="Email channel" href="/docs/channels/email" /></Cards>
+<Cards>
+  <Card title="Failover guide" href="/docs/guides/failover" />
+  <Card title="Weighted fallback" href="/docs/decorators/weighted-fallback" />
+  <Card title="Retry" href="/docs/decorators/retry" />
+</Cards>

package/site/content/docs/decorators/index.mdx

@@ -1,25 +1,27 @@
 ---
 title: Decorators
-description: Wrap an email transport with retry, fallback, preview, or idempotency.
+description: Wrap any channel transport with retry, fallback, preview, or idempotency.
 icon: Layers
 source: "src/transports/retry.ts"
 ---
 
-Decorators wrap another email transport. The mailer still calls `send` the same way — only the transport path changes.
+Decorators wrap another transport. The channel sender still calls `send` the same way — only the transport path changes.
+Retry, fallback, and weighted fallback work for email, SMS, WhatsApp, and push.
+Preview and idempotency remain email-oriented.
 
-<Callout title="The one rule">Pass the outermost decorator to `createMailer`. Inner transports stay providers (or other decorators).</Callout>
+<Callout title="The one rule">Pass the outermost decorator to the matching channel sender (`createMailer`, `createSmsSender`, …).</Callout>
 
 ## Available decorators
 
-| Decorator | Import |
-| --- | --- |
-| [Preview](./preview) | `sently/transports/preview` |
-| [Retry](./retry) | `sently/transports/retry` |
-| [Fallback](./fallback) | `sently/transports/fallback` |
-| [Weighted fallback](./weighted-fallback) | `sently/transports/weighted-fallback` |
-| [Idempotency](./idempotency) | `sently/idempotency` |
+| Decorator | Import | Channels |
+| --- | --- | --- |
+| [Preview](./preview) | `sently/transports/preview` | Email |
+| [Retry](./retry) | `sently/transports/retry` | Email, SMS, WhatsApp, Push |
+| [Fallback](./fallback) | `sently/transports/fallback` | Email, SMS, WhatsApp, Push |
+| [Weighted fallback](./weighted-fallback) | `sently/transports/weighted-fallback` | Email, SMS, WhatsApp, Push |
+| [Idempotency](./idempotency) | `sently/idempotency` | Email |
 
-## Typical stack
+## Typical stack (email)
 
 ```ts
 import { createMailer } from "sently/mailer";
@@ -35,16 +37,32 @@ const transport = new FallbackTransport([
 const mailer = await createMailer({ transport });
 ```
 
+## Typical stack (SMS)
+
+```ts
+import { createSmsSender } from "sently/sms";
+import { FallbackTransport } from "sently/transports/fallback";
+import { TaqnyatSmsTransport } from "sently/transports/taqnyat-sms";
+import { UnifonicTransport } from "sently/transports/unifonic";
+
+const sms = createSmsSender({
+  transport: new FallbackTransport([
+    new TaqnyatSmsTransport({ bearerToken: process.env.TAQNYAT_TOKEN!, sender: "MyBrand" }),
+    new UnifonicTransport({ appSid: process.env.UNIFONIC_APPSID!, senderId: "MyBrand" }),
+  ]),
+});
+```
+
 ## Learn more
 
+- [Failover recipe](../guides/failover) — retry inside a provider, then fail over
 - [Transports](../transports)
-- [Email channel](../channels/email)
 - [Hooks](../channels/hooks)
 
 ## Next
 
 <Cards>
+  <Card title="Failover guide" href="/docs/guides/failover" />
   <Card title="Retry" href="/docs/decorators/retry" />
   <Card title="Fallback" href="/docs/decorators/fallback" />
-  <Card title="Transports" href="/docs/transports" />
 </Cards>

package/site/content/docs/decorators/preview.mdx

@@ -6,29 +6,72 @@ source: "src/transports/preview.ts"
 ---
 
 Write email previews to disk instead of delivering them.
+Use this when you want a local `.eml` or HTML file for the welcome email without a mail server.
 
 <Callout title="The one rule">Preview is for development, not delivery.</Callout>
 
-## Configuration
-
-`outDir`, `open`, and `format` are optional; defaults are `./.emails`, false, and `eml`.
+## Quick start
 
-<Steps><Step title="Wrap an email transport">
+<Steps>
+  <Step title="Create the preview transport">
 
 ```ts
+import { createMailer } from "sently/mailer";
 import { PreviewTransport } from "sently/transports/preview";
 
 const transport = new PreviewTransport({ outDir: ".emails", open: true });
+const mailer = await createMailer({ transport });
 ```
 
-</Step><Step title="Create the mailer">
+  </Step>
+  <Step title="Send and open the file">
 
 ```ts
-const mailer = await createMailer({ transport });
+await mailer.send({
+  from: "dev@example.com",
+  to: "you@example.com",
+  subject: "Welcome",
+  text: "Thanks for joining.",
+});
 ```
 
-</Step></Steps>
+Files land under `outDir` (default `./.emails`). With `open: true`, the OS opens the written file.
+
+  </Step>
+</Steps>
+
+## Configuration
+
+| Option | Type | Default | Meaning |
+| --- | --- | --- | --- |
+| `outDir` | `string` | `"./.emails"` | Directory for preview files |
+| `open` | `boolean` | `false` | Open the file after write |
+| `format` | `"eml" \| "html"` | `"eml"` | Full MIME or HTML body only |
+
+`provider` is `"preview"`. `verify()` always succeeds.
+
+For a real SMTP catcher with a web UI, use [Mailpit](/docs/transports/mailpit) instead.
+
+## Troubleshooting
+
+<Accordions>
+  <Accordion title="Does Preview wrap another transport?">
+    No. `PreviewTransport` is the delivery transport — it writes to disk and does not call a provider.
+  </Accordion>
+  <Accordion title="Where is the file?">
+    Check `outDir` (default `./.emails`). The console logs `[sently preview] Written: …` on each send.
+  </Accordion>
+</Accordions>
+
+## Learn more
+
+- [Mailpit](/docs/transports/mailpit) — local SMTP catcher with inbox API
+- [Email channel](/docs/channels/email) — `createMailer` contract
 
-<Accordions><Accordion title="Does this replace the inner provider?">No. It delegates sends to the wrapped transport.</Accordion></Accordions>
+## Next
 
-<Cards><Card title="Email channel" href="/docs/channels/email" /></Cards>
+<Cards>
+  <Card title="Mailpit" href="/docs/transports/mailpit" />
+  <Card title="Email channel" href="/docs/channels/email" />
+  <Card title="Decorators" href="/docs/decorators" />
+</Cards>

package/site/content/docs/decorators/retry.mdx

@@ -1,11 +1,12 @@
 ---
 title: Retry
-description: Retry failed email sends with configurable backoff.
+description: Retry failed sends with configurable backoff on any channel transport.
 icon: RotateCw
 source: "src/transports/retry.ts"
 ---
 
-Retry failed email sends with configurable backoff.
+Retry failed sends with configurable backoff.
+Works with email, SMS, WhatsApp, and push transports.
 
 <Callout title="The one rule">Authentication errors are not retried.</Callout>
 
@@ -13,22 +14,44 @@ Retry failed email sends with configurable backoff.
 
 `maxAttempts`, `backoff`, `baseDelay`, `retryOn`, and `onRetry` are optional.
 
-<Steps><Step title="Wrap an email transport">
+## Quick start
+
+<Steps>
+  <Step title="Wrap a transport">
 
 ```ts
 import { RetryTransport } from "sently/transports/retry";
+import { TaqnyatSmsTransport } from "sently/transports/taqnyat-sms";
 
-const transport = new RetryTransport(new ResendTransport({ apiKey: "..." }), { maxAttempts: 3 });
+const transport = new RetryTransport(
+  new TaqnyatSmsTransport({ bearerToken: "...", sender: "MyBrand" }),
+  { maxAttempts: 3 },
+);
 ```
 
-</Step><Step title="Create the mailer">
+  </Step>
+  <Step title="Pass it to the channel sender">
 
 ```ts
-const mailer = await createMailer({ transport });
+import { createSmsSender } from "sently/sms";
+
+const sms = createSmsSender({ transport });
 ```
 
-</Step></Steps>
+  </Step>
+</Steps>
+
+## Troubleshooting
+
+<Accordions>
+  <Accordion title="Does this replace the inner provider?">
+    No. It delegates sends to the wrapped transport.
+  </Accordion>
+</Accordions>
 
-<Accordions><Accordion title="Does this replace the inner provider?">No. It delegates sends to the wrapped transport.</Accordion></Accordions>
+## Next
 
-<Cards><Card title="Email channel" href="/docs/channels/email" /></Cards>
+<Cards>
+  <Card title="Fallback" href="/docs/decorators/fallback" />
+  <Card title="Hooks" href="/docs/channels/hooks" />
+</Cards>

package/site/content/docs/decorators/weighted-fallback.mdx

@@ -6,6 +6,7 @@ source: "src/transports/weighted-fallback.ts"
 ---
 
 Choose a weighted primary transport and fail over on errors.
+Works with email, SMS, WhatsApp, and push.
 
 <Callout title="The one rule">At least one entry with positive total weight is required.</Callout>
 
@@ -13,22 +14,42 @@ Choose a weighted primary transport and fail over on errors.
 
 Each entry has `transport` and positive `weight`; it accepts fallback options and optional `random`.
 
-<Steps><Step title="Wrap an email transport">
+## Quick start
+
+<Steps>
+  <Step title="Build weighted entries">
 
 ```ts
 import { WeightedFallbackTransport } from "sently/transports/weighted-fallback";
 
-const transport = new WeightedFallbackTransport([{ transport: primary, weight: 80 }, { transport: secondary, weight: 20 }]);
+const transport = new WeightedFallbackTransport([
+  { transport: primary, weight: 80 },
+  { transport: secondary, weight: 20 },
+]);
 ```
 
-</Step><Step title="Create the mailer">
+  </Step>
+  <Step title="Pass it to the channel sender">
 
 ```ts
 const mailer = await createMailer({ transport });
+// or createSmsSender / createWhatsAppSender / createPushSender
 ```
 
-</Step></Steps>
+  </Step>
+</Steps>
+
+## Troubleshooting
+
+<Accordions>
+  <Accordion title="Does this replace the inner provider?">
+    No. It delegates sends to the wrapped transports.
+  </Accordion>
+</Accordions>
 
-<Accordions><Accordion title="Does this replace the inner provider?">No. It delegates sends to the wrapped transport.</Accordion></Accordions>
+## Next
 
-<Cards><Card title="Email channel" href="/docs/channels/email" /></Cards>
+<Cards>
+  <Card title="Fallback" href="/docs/decorators/fallback" />
+  <Card title="Decorators" href="/docs/decorators" />
+</Cards>

package/site/content/docs/get-started/entrypoints.mdx

@@ -54,26 +54,27 @@ const mailer = await createSMTPMailer({
 
 | Import | Exports | Use |
 | ------ | ------- | --- |
-| `sently` | Shared factories, types, OAuth2, errors, Fallback / WeightedFallback / Cloudflare Email | General email entrypoint. |
+| `sently` | Shared factories, types, OAuth2, errors, `toChannelSendResult`, Fallback / WeightedFallback / Cloudflare Email | General email + shared helpers. |
 | `sently/mailer` | `createMailer` | Email with an explicit transport (smallest HTTP path). |
 | `sently/smtp` | `createSMTPMailer` | SMTP relay configuration. |
 | `sently/sms` | `createSmsSender` | SMS sender. |
 | `sently/whatsapp` | `createWhatsAppSender` | WhatsApp sender. |
-| `sently/push` | `createPushSender` | Web Push sender. |
+| `sently/push` | `createPushSender` | Push sender (Web Push or FCM). |
+| `sently/channel-result` | `toChannelSendResult` | Shared `{ messageId, provider, accepted }` mapping. |
 
 ## Supporting entrypoints
 
 | Import | Use |
 | ------ | --- |
-| `sently/transports/*` | One provider or email decorator transport. |
-| `sently/webhooks/<provider>` | One webhook parser (smallest graph). |
+| `sently/transports/*` | One provider or decorator transport (retry / fallback work across channels). |
+| `sently/webhooks/<provider>` | One webhook parser (email, SMS, or WhatsApp). |
 | `sently/webhooks` | Convenience barrel of all webhook helpers. |
 | `sently/errors` | Stable sently error classes and codes. |
 | `sently/plugins/template` | Template plugin and simple engine. |
 | `sently/auth/oauth2` | SMTP OAuth2 client. |
 | `sently/pool` | SMTP connection pool. |
 | `sently/dkim` | DKIM signing entrypoint. |
-| `sently/idempotency` | Idempotency transport and memory store. |
+| `sently/idempotency` | Idempotency transport and memory store (email). |
 
 ## Troubleshooting
 
@@ -87,7 +88,7 @@ No. `createMailer` requires a transport. Import `createSMTPMailer` from `sently/
 
 <Accordion title="Where do provider transports come from?">
 
-Import the concrete transport from its exported `sently/transports/*` subpath, such as `sently/transports/sndr` or `sently/transports/resend`.
+Import the concrete transport from its exported `sently/transports/*` subpath, such as `sently/transports/sndr`, `sently/transports/resend`, or `sently/transports/mailpit`.
 
 </Accordion>
 
@@ -102,13 +103,15 @@ HTTP providers were removed from the main barrel so bare Node/Deno imports do no
 ## Learn more
 
 - [Export reference](/docs/reference/exports) — full entrypoint map
+- [Support matrix](/docs/get-started/support-matrix) — Supported vs Available
+- [Stability policy](/docs/get-started/stability) — frozen entrypoints at 1.x
 - [All transports](/docs/transports) — providers by channel
-- [Bundle size](/docs/guides/bundle-size) — keep stacks small
+- [Bundle size](/docs/guides/bundle-size) — keep stacks small on Workers
 
 ## Next
 
 <Cards>
   <Card title="Exports reference" description="Public package entrypoints." href="/docs/reference/exports" />
+  <Card title="Support matrix" description="Production support promise." href="/docs/get-started/support-matrix" />
   <Card title="Email channel" description="createMailer and MailOptions." href="/docs/channels/email" />
-  <Card title="SNDR" description="HTTP email via SNDR." href="/docs/transports/sndr" />
 </Cards>

package/site/content/docs/get-started/index.mdx

@@ -5,10 +5,16 @@ icon: FolderOpen
 source: "README.md"
 ---
 
-Install sently and send your first message.
+Install sently and send your first message. Learn the channel model once, then add SMS or push without a new failure model.
 
 <Cards>
   <Card title="Introduction" href="/docs/get-started/introduction" />
   <Card title="Installation" href="/docs/get-started/installation" />
-  <Card title="Quick start" href="/docs/quick-start" />
+  <Card title="Entrypoints" href="/docs/get-started/entrypoints" />
+  <Card title="Runtimes" href="/docs/get-started/runtimes" />
+  <Card title="Channels" href="/docs/channels" />
+  <Card title="Migrate from Nodemailer" href="/docs/get-started/migrate-nodemailer" />
+  <Card title="Stability policy" href="/docs/get-started/stability" />
+  <Card title="Support matrix" href="/docs/get-started/support-matrix" />
+  <Card title="Non-goals" href="/docs/get-started/non-goals" />
 </Cards>

package/site/content/docs/get-started/installation.mdx

@@ -5,7 +5,7 @@ icon: Package
 source: "package.json"
 ---
 
-sently is an ESM package for applications that send email, SMS, WhatsApp, or browser push.
+sently is an ESM package for applications that send email, SMS, WhatsApp, or push (Web Push / FCM).
 Install it in the application that owns your delivery credentials and provider transport configuration.
 
 <Callout title="The one rule">Import the narrowest sently entrypoint that contains the sender or transport you use.</Callout>
@@ -52,7 +52,8 @@ const mailer = await createMailer({
 | Email over SMTP | `sently/smtp` |
 | SMS | `sently/sms` |
 | WhatsApp | `sently/whatsapp` |
-| Web Push | `sently/push` |
+| Push (Web Push or FCM) | `sently/push` |
+| Shared send-result mapping | `sently/channel-result` |
 
 ## Troubleshooting
 

package/site/content/docs/get-started/introduction.mdx

@@ -5,8 +5,8 @@ icon: Compass
 source: "README.md"
 ---
 
-sently sends email, SMS, WhatsApp, and browser push without making provider SDK calls your application API.
-Choose the channel sender first, then attach the provider transport that performs delivery.
+sently is the channel-delivery layer for email, SMS, WhatsApp, and push (Web Push or FCM).
+Choose a channel sender first, then attach a provider transport — so adding SMS or push later does not invent a new error and retry model in your app.
 
 <Callout title="The one rule">Use `createMailer`, `createSmsSender`, `createWhatsAppSender`, or `createPushSender` in app code; swap transports when provider configuration changes.</Callout>
 
@@ -67,11 +67,15 @@ Email factories are asynchronous. The other channel factories return their sende
 
 - [Install sently](./installation)
 - [Choose an entrypoint](./entrypoints)
+- [Stability policy](./stability)
+- [Support matrix](./support-matrix)
+- [Compare](/docs/guides/compare)
 - [Explore channels](../channels)
 
 ## Next
 
 <Cards>
-  <Card title="Email quick start" href="/docs/quick-start/email" />
+  <Card title="Email channel" href="/docs/channels/email" />
+  <Card title="Support matrix" href="/docs/get-started/support-matrix" />
   <Card title="Channels" href="/docs/channels" />
 </Cards>