{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigoyjp4xfhsbh4de3js56pxnnq76hvay67rcyvcer7gww4zzazab4",
    "uri": "at://did:plc:e7a2hfyyyyeteek2enffctcg/app.bsky.feed.post/3mn6latx5uc2w"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreihivbjdhyzx25t5uap6leikcdwxhbche2hksqdiyqzyfwvdreszvm"
    },
    "mimeType": "image/png",
    "size": 218012
  },
  "description": "Autoblue 2.0 is out now! This is a big release, and it brings one of the most exciting additions to Autoblue so far: support for publishing your WordPress posts asstandard.site documents on the AT Protocol. That might sound a bit technical, and honestly, it is. But the idea behind it is simple: your website should […]",
  "path": "/autoblue-2-0-is-here-with-standard-site-support-3",
  "publishedAt": "2026-05-31T22:07:23+00:00",
  "site": "at://did:plc:e7a2hfyyyyeteek2enffctcg/site.standard.publication/3mn5fekab4e2f",
  "textContent": "Autoblue 2.0 is out now! This is a big release, and it brings one of the most exciting additions to Autoblue so far: support for publishing your WordPress posts asstandard.site documents on the AT Protocol. That might sound a bit technical, and honestly, it is. But the idea behind it is simple: your website should not just be something that posts to Bluesky. It should alsobe able to participate more directly in the wider AT Protocol ecosystem. With Autoblue 2.0, posts you share to Bluesky can now also be written to your PDS as site.standard.document records. This means other standard.site-aware apps and readerscan discover your posts as first-class AT Protocol content, while still linking back to your original WordPress site. ## Why standard.site? One of the things I’m most excited about with Bluesky and the AT Protocol is that it opens the door to many different kinds of apps, not just social timelines. Blogs, readers, comments, newsletters, directories, discovery tools: all of these can exist on top of the same protocol. standard.site is a step in that direction forwebsites and long-form posts. WordPress already powers a huge part of the web, so it feels natural to connect it more deeply to the AT Protocol. Your WordPress site should remain the source of truth,but Autoblue can now also publish a document record to your PDS so other apps can understand and discover it. In practical terms, Autoblue 2.0 adds a new standard.site option to the settings. Once enabled, you can choose whether individual posts should also be published asstandard.site documents when they’re shared to Bluesky. ## More than just posts This release also adds support for sharing from additional public post types. Previously, Autoblue was focused on regular WordPress posts. With 2.0, it can support morepublic content types, which makes it a better fit for sites that use custom post types for articles, resources, projects, or other content. There are also a few smaller but important improvements: Expired Bluesky connections are now shown more clearly in the admin UI.Connection API responses no longer expose JWT values.Silent cron share failures are now surfaced in the logs.Autoblue is tested up to WordPress 7.0. Some of these aren’t flashy, but they make Autoblue more reliable and easier to debug. That matters, especially as the plugin starts doing more behind the scenes. ## What’s next? Autoblue started as a way to automatically share WordPress posts to Bluesky and display replies back on your site. That’s still the core idea, but this release is animportant step toward something broader: making WordPress feel at home on the AT Protocol. I’m still figuring out exactly where this goes next, and I’m sure standard.site itself will keep evolving too. For now, I’m excited to get this out there and see howpeople use it. As always, if you run into anything weird or have ideas for what Autoblue should support next, please ping me on Bluesky!",
  "title": "Autoblue 2.0 is here, with standard.site support"
}