Skip to content

Commit 062fb4f

Browse files
committed
Updated screenshot.
1 parent 0c31cd0 commit 062fb4f

File tree

3 files changed

+2
-2
lines changed

3 files changed

+2
-2
lines changed
Binary file not shown.
-27.9 KB
Loading

src/pages/docs/push/getting-started/nextjs.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -382,8 +382,6 @@ await client.push.admin.publish(
382382
```
383383
</Code>
384384

385-
![Screenshot of the Next.js push tutorial application showing push notifications received](../../../../images/content/screenshots/getting-started/nextjs-push-getting-started-guide.png)
386-
387385
<Aside data-type='note'>
388386
Sending push notifications using `deviceId` or `clientId` requires the `push-admin` capability on your API key. In production, send push notifications from your backend server rather than from the client.
389387
</Aside>
@@ -486,6 +484,8 @@ Sending push notifications via a channel publish requires the `push` object to b
486484
- `notification`: Contains `title` and `body` displayed in the browser notification.
487485
- `data`: Custom key-value pairs delivered to the service worker but not shown directly.
488486

487+
![Screenshot of the Next.js push tutorial application showing push notifications received](../../../../images/content/screenshots/getting-started/nextjs-push-getting-started-guide.png)
488+
489489
## Browser compatibility <a id="browser-compatibility"/>
490490

491491
Web Push notification support varies across browsers:

0 commit comments

Comments
 (0)