README

This is the ATmosphere plugin repo.

Publish your WordPress posts to the AT Protocol network — cross-post to Bluesky, register your articles as standard.site documents on your PDS, use your domain as your Bluesky handle, and mirror replies and reposts back into WordPress as native comments.

Documentation

• Developer Documentation — entry point for developers extending or integrating with ATmosphere.
• Development Environment — wp-env setup, prerequisites, troubleshooting, coverage.
• PHP Coding Standards — naming, escaping, error handling, performance, cron rules.
• Class Structure — directory layout, namespaces, architectural patterns.
• Code Linting — PHPCS rules and common fixes.
• Pull Request Guide — branching, pre-PR checklist, commit format.
• Release Process — npm run release, patch releases, GitHub Release UI.
• Translations — text domain, GlotPress, translator-friendly strings.
• Content Formats — AT Protocol content types for site.standard.document.
• org.wordpress.html Lexicon — the rendered-HTML content type schema.
• Integrations — registering custom Content_Parser implementations.
• Contributor instructions — directory structure, commands, conventions, and skills/agents.

Protocol Support

ATmosphere implements the AT Protocol natively — no third-party proxy or intermediary service. Authentication uses OAuth 2.1 with PKCE and DPoP. Records are written to your PDS via com.atproto.repo.applyWrites.

Currently supported record types:

• app.bsky.feed.post — Bluesky posts and reply threads.
• site.standard.publication — your site as a publication record.
• site.standard.document — one document record per WordPress post.

See docs/content-formats.md for more on the content union used by site.standard.document.

Support

If you need help, check the issue tracker on GitHub or open a new bug report.

Contribute

Contributions are welcome — bug fixes, new features, integrations, translations.

• Keep issues focused. Use the issue tracker for specific bugs or concrete proposals. Tangential ideas are best as GitHub Discussions.
• Stay within scope. Open issues should relate directly to the plugin.
• Be concise. Short, actionable descriptions are easier to respond to.

Before opening a pull request, please read AGENTS.md for directory layout, coding conventions, and the release workflow.

Security

Found a security issue? Report it via Automattic's security page or our HackerOne bug-bounty program at https://hackerone.com/automattic.

License

ATmosphere is licensed under the GPL v2 or later.