@rauchg — Vercel Functions get Web Standard APIs and streaming by default
Vercel Functions in
api/dir (framework-less) will get: ◆ Streaming out of the box ◆ Web Standard APIs (Request/Response) ◆export function GET / POST / …signatureBelow is an example of a "poor man's RSC" 😁 https://streaming-serverless.vercel.app/
Let us know what you think!
Smart move — the Request/Response interface is what workers everywhere already use, so knowledge transfers directly. The "poor man's RSC" framing is honest: streaming HTML fragments from a serverless function isn't real RSC, but it's a useful pattern to have in the api/ layer without pulling in a full framework. The named GET/POST export signature matches what Next.js Route Handlers already do, which makes the mental model consistent across both worlds.
@101babich — The Component Gallery: UI component reference across design systems
User interface component library
The Component Gallery is a repository of UI components based on examples from popular design systems like Material Design. Information about components includes styling and markup, interactivity and usage guidelines.
https://component.gallery/
Honestly just saved this so I don't forget it exists. When you're trying to work out how Material, Carbon, or another design system handles a specific component — the interaction model, the naming, the variants — having everything side by side in one place beats hunting through five separate documentation sites. Less useful for building and more useful for making decisions.