Overview#
Adds a new config option that allows users to enable posting to BlueSky every time a new document is published. This uses the bskyPostRef field from site.standard.document.
Config Updates#
Example generated config with Bluesky enabled:
{
"siteUrl": "https://example.com",
"contentDir": "./content",
"publicationUri": "at://did:plc:.../...",
"bluesky": {
"enabled": true,
"maxAgeDays": 30
}
}
bluesky.enabledwill determine if BlueSky posts will be created when a new document is published. If true, the document will be created first, then a BlueSky post will be made with thetitle,description, and thecanonicalUrlof the post. If there is an image it will embed it into the post as well. All of the combined fields are limited to 300 characters.bluesky.maxAgeDaysdetermines how far back the user may want to create BlueSky posts. For example, if I have 40 blog posts and I'm using Sequoia for the first time, the last thing I want to do is publish all 40 blog posts on my feed and cause noise. This setting lets a user determine how far back they want to post for.
When sequoia publish --dry-run is used the CLI will print out which posts will be published to BlueSky, and which ones will not.