AT Protocol Syndication
Publish EmDash content into AT Protocol and standard.site-style syndication workflows.
Plugin
AT Protocol Syndication
Publish EmDash content into AT Protocol and standard.site-style syndication workflows.
This plugin connects EmDash publishing to AT Protocol distribution paths so structured CMS content can participate in protocol-based ecosystems—not only traditional HTML pages. The package lives under packages/plugins/atproto; credentials, posting modes, and supported record types are defined there for each release.
Installation
- Create or use an AT Protocol identity (for example, a Bluesky-compatible account) dedicated to syndication—not your personal handle unless that is intentional.
- Enable the AT Protocol plugin in EmDash and supply app passwords or OAuth-style credentials exactly as the plugin README specifies. Never commit secrets to Git.
- In a staging environment, post a short test article and verify it appears on the expected ATProto-backed surface before you wire production content.
Configuration
You will typically configure:
- Which content types syndicate — posts only, or also pages and notes.
- Mapping fields — title, summary, canonical link back to your site, and hashtags or labels.
- Rate limits and retries — backoff when the network is busy.
Example (conceptual): a weekly changelog might syndicate as a thread: first skeet with the headline and URL, follow-ups with bullet highlights, all generated from the same EmDash post so you are not double-typing in another app.
Usage scenarios
- Cross-network reach — meet readers where they already participate without abandoning your owned site.
- Protocol experiments — try standard.site-style flows alongside traditional RSS.
- Brand accounts — keep messaging consistent when multiple editors publish through EmDash.
Operational tips
- Syndication amplifies mistakes; add an editorial “go live” checklist for networked posts.
- Monitor account status and API changes in the AT ecosystem; pin plugin versions during critical campaigns.
- Keep canonical URLs pointing at your domain for SEO and attribution.