PWV Portfolio Feed

Today we're shipping ten free design system taste packages.

Inspired from industry best examples like:
Figma, Vercel, Apple, Claude, Spotify, Uber

Pull one of these and build UIs that look yours.

Try now!!
↳ npx taste pull 
Read thread to download

1.0 doesn't mean done, and it doesn't mean perfect. It means most developers can quickly feel at home in Zed. If you tried it a while back and bounced because something was missing, this is our invitation to try again.

Zed 1.0 is a complete code editor built from scratch in Rust, running on Mac, Windows, and Linux. Five years of work by our team and community, exceeding a million lines of code. More capable than it's ever been, and still more performant.

You include `author` in your MongoDB query, but TypeScript still makes you prove it exists somewhere else.

Prisma Next makes the result type follow the query, so loaded data is typed where you use it.

i now understand how priority queues work

Thanks Dave, means a lot.

the deno contribution charts are looking very funky. lots of commits, mostly from ~3 humans and 3 robots

Six years is a long time, and we don't want to lose you over pricing without at least taking a look. There's almost always something we can do on usage or plan structure that gets the bill closer to where it needs to be. Mind if someone from our team reaches out to dig in before you go?

Netlify Database is live.

Fully integrated Postgres as a new core primitive on our platform.

This works for whoever is building.

A designer prompting an app into existence gets the same safety net as a team of engineers running migrations through Drizzle. Same workflow, same guarantees, no extra setup.

How a schema change flows end to end:

1. Agent writes code and a migration file
2. Preview build runs the migration on your branch
3. You test. Break things. Add junk data
4. Publish when ready
5. Netlify applies the right migrations to production

No 2am rollbacks.

The agent literally cannot modify production. Not a permission flag, not a toggle. It just cannot reach it.

It writes SQL migration files as it works. Those run against your branch during preview builds. Production is only modified when you go live.

When you start an agent run, Netlify provisions a Postgres branch based on the latest production data. Schema changes, test records, half-baked experiments, all contained.

Production stays untouched until you choose to publish.

Years ago, Deploy Previews changed how we ship code. Safe to break things, easy to roll back, every branch isolated.

The database layer never got that treatment. One environment, shared, always a little broken.

That's what we fixed.