On May 28, 2026, Bluesky rolled out enhanced, dynamic links cards powered by Standard.site.

v1.122 is rolling out today, featuring a better way to discover and share articles, blog posts and newsletters across the Atmosphere via new, dynamic Standard.site link cards. 🧵

[image or embed]
— Bluesky (@bsky.app) May 28, 2026 at 8:09 PM

It basically means that blogs with Standard.site implementation have link cards of their posts enhanced - the link cards contain your publication name, icon, and reading time. How to implement them At the moment of writing this post, there are only three blogging services that are based on AT Protocol and support Standard.site link cards: - Leaflet, - pckt.blog, - Offprint However it is not a problem - it is possible to implement the enhanced link cards into any website. You will have to use an AT Protocol explorer, e.g. atproto.at, PDSls and log in with your Bluesky handle. If you use a static site generator (SSG), use Sequoia.pub instead. Standard.site has its documention on implementing these enhanced link cards; you may want to (or even should) read it at standard.site/docs/quick-start. Step 1: Create your publication record A publication record remains the same for your website, unlike document records that have to be generated for each page (one document record = one page) because they contain information about a page, not a entire website. Publication records are not required but recommended 1. Click Create record. 2. In the Collection field, type site.standard.publication. 3. In the editor, replace everything with A publication requires a url and name. 4. Click Create. Copy the AT-URI. The AT-URI should look like this: > [!NOTE] > You may want to save the AT-URI somewhere as you will have to add it to each page. Step 2: Create a verification file and verify the publication 1. Create a directory named .well-known in your root directory (if you don't have one) of your website and create a file named site.standard.publication in it. The URL should look like this: 2. Paste the AT-URI into it and save it. 3. Add a tag below to your website and replace the AT-URI with yours: Step 3: Create a document record and verify the document Document records have to be generated for each page - they do not remain the same, unlike publication records, because they contain information about a page, not about an entire website. 1. Click Create record. 2. In the Collection field, type site.standard.document. 3. In the editor, replace everything with Documents require site, title, and publishedAt. 4. Add a tag to a page: Step 4: Add your website's icon to your link card This is optional but recommended. In my case, I had to add my icon because there was a letter, instead of my website's icon. You can use either your Bluesky profile picture or use a different icon. --- Use your Bluesky profile picture 1. Find the app.bsky.actor.profile collection and open it. > [!NOTE] > If necessary, click self to proceed. 2. Open the editor or switch the view of the file to RAW. 3. Find the image array and copy this part: 4. Go back to site.standard.publication, insert your part into the JSON file, and replace image with icon. Your JSON file should look like this: 5. Save. Use a different icon You will have to post an image that you would like to use as an icon. You can limit interacting with the post either before posting the image or after. Make sure that the image is square and its size is at least 256x256. The steps are very similar to those in part 4. --- 1. Post the image. 2. Go to app.bsky.feed.post and find the newest record which is a post with the image. 3. Open the editor or switch the view of the file to RAW. 4. Find the image array and copy this part: 5. Go back to site.standard.publication, insert your part into the JSON file, and replace image with icon. Your JSON file should look like this: 6. Save. Step 5 (optional): VuePress + Sequoia.pub + Cloudflare Pages configuration experimental At the moment of writing this post, Sequoia.pub does not (officially) support Vue and Cloudflare Pages for deploying, however there are workarounds. If you use VuePress for your website and Cloudflare Pages for building and deploying your website, this part is for you. > [!NOTE] > I use npm as my package manager, therefore some commands may be different. 1. Go to the Sequoia.pub documentation. 2. Follow the steps to set it up. You may want to use the sequoia login command to use a web browser to authenticate with your ATProto account. 3. If you already have document records created and link tags added to each page of your website, use the sequoia sync command. This command will use your ATProto handle to look through all of the site.standard.document records on your PDS, and pull down the records that are for the publication in the configuration. 4. Copy or write down your account's DID or handle and generate an app password at bsky.app/settings/app-passwords and copy it. You will need them for Cloudflare Pages - to add them as environment variables in the project settings of your website. 5. Go to your Cloudflare Pages project and open its settings. 6. Look for Variables and Secrets and click Add. 7. You will add the following variables: | Variables | Description | |:---------:|:-----------:| | ATP_IDENTIFIER | Your ATProto handle or DID
(e.g. alice.bsky.social, did:plc:z72i7hdynmk6r22z27h6tvur) | | ATP_APP_PASSWORD | Your ATProto app password | Your DID or handle and generated app password are values. > [!WARNING] > Your ATProto handle and DID are public so you can feel free to add any of them as plain text, however your generated app password is not - it is private and is meant to be private so you should add it as Secret. 8. Once you have added the variables, click Save. Changes will take effect on the next deployment. 9. Open the package.json file in the root directory of your website and modify it: - Add "sequoia-cli": "latest", to devDependencies, - Add npx sequoia publish && before the vuepress-vite build command and add && npx sequoia inject after the build command to this command that you use for Cloudflare Pages to deploy your website. The part of the build command should look like this: 10. Open terminal, go to the root directory of your website, and install all dependencies to update the package-lock.json file: 11. Deploy your website, along with package.json, package-lock.json, sequoia.json, and .sequoia-state.json. 12. Done! > [!NOTE] > You may want to check the build log of the deployment to make sure that your website has been successfully deployed and document records have been applied. Sources & credits 1. Putting my Neocities blog on ATProto | Hannah's Web log 2. Standard.site

Tag: AT Proto

Substratum.cloud comes to life

Enhanced link cards on Bluesky of my blog posts