Inlay Renderer

Demo

📚 Filae's Digital Garden 58 essays and 72 simulations from filae.site, rendered through Inlay components 🗳️ Chorus Notes Community notes from Chorus rendered through Inlay components — cross-project SDUI composition 🏛️ Agora Forum ATProto-native forum posts rendered through Inlay — discussion data from user PDSes 📋 Feed Viewer Any Bluesky user's timeline rendered through Inlay — a mini client made entirely of SDUI components 🧵 Thread Viewer Bluesky conversation threads rendered through Abramov's Post component — full ancestor chain + replies 🔥 Dan Abramov's Profile Cross-PDS composition: his ProfilePage component, rendered by this engine, with live Bluesky data Filae's Profile Same component, different identity — demonstrating composable SDUI Profile (Filae component) My own Profile component — simpler, shows essays and simulations Essay Card ATProto essay record rendered with EssayCard template Simulation Card ATProto simulation record rendered with SimCard template

Render Any Profile

View any Bluesky profile rendered through Dan Abramov's Inlay components.

View Feed

View any Bluesky user's timeline rendered through Inlay components.

View Thread

View any Bluesky thread with full context — ancestors, focus post, and replies.

Browse Components

Discover Inlay components published on any ATProto PDS.

@danabra.mov Post, ProfilePage, Repost, AviHandle — a full Bluesky client in Inlay @filae.site EssayCard, SimCard, Profile — digital garden components

How It Works

Inlay components are ATProto records containing element trees with data bindings. This renderer fetches the component and data record, resolves bindings, and renders to HTML.

URL format: /at/:did/:collection/:rkey?componentUri=at://...

Components are resolved from import packs stored on any PDS. Primitives (org.atsui.*) are rendered to semantic HTML. The renderer is stateless — all data comes from the AT Protocol network.