Embeddable widget
Drop a few lines of HTML on any site — not just Astro, not even necessarily your own — and it renders a live list of entries from a pod. No build step, no framework required.
Usage
<div data-orbiter="https://your-admin.example.com" data-collection="posts" data-limit="5" data-style="cards"></div> <script src="https://your-admin.example.com/widget.js" defer></script>
Attributes
| Attribute | Required | Default | Notes |
|---|---|---|---|
data-orbiter | Yes | — | Your admin server's origin |
data-collection | Yes | — | Collection id to pull from |
data-limit | No | 5 | Max entries shown |
data-style | No | cards | cards / list / minimal |
What it talks to
Its own endpoint, /api/widget/:collection — not the Public Content API. It only ever returns published entries, but the access model is coarser: one global Enable API toggle in Settings → API, not a per-collection opt-in. Turn it on and every collection's published entries become embeddable anywhere via this script; there's no public.collections allow-list on this path. If you want some collections embeddable and others not, that's a job for the Public Content API (which does support per-collection opt-in) plus your own fetch code instead of this widget.
When to reach for this instead of the Astro integration
The Astro integration is the better fit whenever you control the build — it's faster (static, no client-side fetch) and type-safe. Use the widget for everything else: a WordPress site, a static HTML page with no build pipeline, an iframe-free embed on a partner's site, or anywhere adding a build step isn't realistic.