It keeps confusing me that the main call to action in these cards (the button) does NOT go to the article but to the main website Is it just me that finds this weird...? The main visual CTA for a card about an article should go to that article no...?
daniel r(ooooooh) 👻
don't be nice.
Sep 19, 2026 at 10:57 PM
[Question] Why does the spec require a browser to select the presentation device · Issue #526 · w3c/presentation-api
I've been reading the closed issues and I've skimmed through the spec before posting this. I don't really understand why I'm not allowed to get a list of objects containing the pres...
Accessible faux-nested interactive controls
A really common user interface pattern is a big clickable area, such as a card. Sometimes you need controls within that card that are also clickable. There's lots of ways to do it wrong, but fret not, Eric is here to show you how to do it right.
Make links to your blog render the custom "View publication" card + CTA
Short guide. The mechanism is simpler than it looks, and it doesn't involve any /.well-known file or DNS TXT record.
4 Design Patterns That Violate “Back” Button UX Expectations – 59% of Sites Get It Wrong – Baymard
Our large-scale usability testing reveals that users expect the "Back" button to take them back to what they perceive to be their previous page, which often differs from site behavior.
I just made a pitch deck in @leaflet.pub and it felt so right to make a series of pages (slides) strung together that way in a cohesive story. The only thing I'm missing is left-right keyboard shortcuts for going to the next/previous page.
we're working on the v2 of our standard.site link cards. these cards currently link to both the article (top part) and publication (bottom part). they show a "Subscribe" button when possible, otherwise a "View Publication" button. what changes would you all like to see in the next version?
Guido X Jansen
It keeps confusing me that the main call to action in these cards (the button) does NOT go to the article but to the main website Is it just me that finds this weird...? The main visual CTA for a card about an article should go to that article no...?
I just got the lovely new @standard.site link cards working with pages made in @neocities.org! And it wasn't hard! Here is a quick guide.
Putting my Neocities blog on ATProto
hannahshelley.neocities.orgThe Standard Reader browser extension is out for Chrome. Save articles and follow publications on the standard.site network — from whatever tab you're already in. ...and all our other features! chromewebstore.google.com/detail/standard-reader/hfjgpb…
The Standard Reader browser extension is out for Chrome. Save articles and follow publications on the standard.site network — from whatever tab you're already in. ...and all our other features! chromewebstore.google.com/detail/standard-reader/hfjgpb…
this is also a thing, but separate from the basic website stuff anna is talking about. the at:// potential is sort of about navigating to that sort of URI in browser bar. but I think more realistically, having anchor links. <a atref="at://..."> (or more realistically: data-atp="at://...")
Introducing Newsrooms v1 in @mu.social. Launching with 15 publications to choose from. Try it out from the News icon in the left menu.
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. 🧵
Had 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.comwe’re rolling out the first phase of the Bluesky + standard.site integration today! now, when you share an article from writing platforms that support standard.site (like @leaflet.pub, @pckt.blog, @offprint.app), you’ll notice the link card has more to it than a typical link card.
Bluesky
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. 🧵
I 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
