







No need to store rkeys in your YAML frontmatter – just derive them from your existing URL paths.
Publishing My Eleventy Blog to the ATmosphere with Standard.site
A walkthrough of how I wired up Standard.site AT Protocol lexicons into this 11ty blog: from writing a custom publish script to migrating to Sequoia, with code for the link tags, and handle verification.

First thoughts on integrating with standard.site
Notes on the limitations and unresolved design questions encountered while integrating a blog with standard.site.

substandard.blog: read. more. blogs.
A browser extension to help you find https://standard.site publishers online.

Introducing Sequoia: Publishing for the Open Web
Today I'm excited to release a new tool for the AT Protocol: Sequoia. This is a CLI tool that can take your existing self-hosted blog and publish it to the ATmosphere using Standard.site lexicons.

to the @standard.site folks, adding a field to `site.standard.publication` which declares where the RSS feed is would help in constructing subscription OPMLs or /blogroll pages indieweb.org/blogroll
blogroll
indieweb.orgHad fun adding support for @standard.site to my blog. The richer preview card on #bsky looks neat. Another benefit is, since all the entries now live in the #ATmosphere, all kinds of #ATProto apps can index and display them. See pckt example: pckt.blog/read?search=rednafi rednafi.com/misc/standard-site/
Putting this blog on ATProto with standard.site
rednafi.comI wrote out how I created my Hugo blog to then connect to @standard.site so that I could push my site to places like @standard-reader.app and other services that utilize ATProto. danarel.com/posts/blog-on-standard-site/
Pushing this blog to ATProto through standard.site
danarel.comNew: special subscribe route for *any* @standard.site publication…useful as an embeddable form! leaflet-hosted: `pub_domain/subscribe` e.g. lab.leaflet.pub/subscribe any: `leaflet.pub/subscribe/[did]/[rkey]` e.g. @wil.to's blog: leaflet.pub/subscribe/did:plc:mlmtsmr3fcb…
jared
been meaning to do this so whipped one up real quick! You can get it at leaflet.pub + /subscribe/[did]/[rkey] or at pub_domain/subscribe if you're hosted by us!
I've been working on a jekyll plugin to make it easier to implement @standard.site: github.com/andrew/jekyll-standard-site
GitHub - andrew/jekyll-standard-site: Jekyll plugin that emits standard.site verification artifacts
github.com@standard.site Is there a reason that rkeys must be tids, rather than arbitrary string rkeys?
I kind of want to make a @standard.site format for characters..... Would be useful for adoptables and roleplayers and TTRPG people I think.
New: special subscribe route for *any* @standard.site publication…useful as an embeddable form! leaflet-hosted: `pub_domain/subscribe` e.g. lab.leaflet.pub/subscribe any: `leaflet.pub/subscribe/[did]/[rkey]` e.g. @wil.to's blog: leaflet.pub/subscribe/did:plc:mlmtsmr3fcb…
jared
been meaning to do this so whipped one up real quick! You can get it at leaflet.pub + /subscribe/[did]/[rkey] or at pub_domain/subscribe if you're hosted by us!
it's easier than ever to turn your standard.site writing into your own website! your posts are atproto records you own. fetch & render them anywhere, in any framework, with your own styles. live demo, try any handle 👇 standard-publication-viewer.wisp.place?handle=erlend.sh
okay, introducing standard.horse! an editor for simple @standard.site publications if you've hand-rolled your standard.site blog, this provides a simple markdown editor and publication management interface
standard.horse
standard.horseI think this breaking change for standard.site needs to become an ecosystem-wide conversation and convention. Any web page that represents a corresponding AT record needs to include a meta tag that includes that record. <meta name=“at:uri” content=“at://…” \>
rich harris
atproto/@standard.site friends: any thoughts on this issue? This... <link rel="site.standard.publication" href="at://..."> ...is invalid HTML, per html.spec.whatwg.org/multipage/semantics.html#the-…, because DIDs aren't hostnames. This causes problems with some tools. Issue here: github.com/sveltejs/kit/issues/15935
Blog posts and guides from folks who have integrated standard.site into their website
I Moved My Website to Leaflet - Norbert Woehnl Photography
Hello, Leaflet 👋🏼🍃 - augment
New: special subscribe route for *any* @standard.site publication…useful as an embeddable form! leaflet-hosted: `pub_domain/subscribe` e.g…

How to publish multiple Standard Site publications on one domain

Putting my Neocities blog on ATProto

Understanding Standard.Site