惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

C
Check Point Blog
Microsoft Security Blog
Microsoft Security Blog
aimingoo的专栏
aimingoo的专栏
V
V2EX
博客园 - 【当耐特】
T
Tailwind CSS Blog
Apple Machine Learning Research
Apple Machine Learning Research
量子位
MyScale Blog
MyScale Blog
Hugging Face - Blog
Hugging Face - Blog
大猫的无限游戏
大猫的无限游戏
The Cloudflare Blog
月光博客
月光博客
I
InfoQ
WordPress大学
WordPress大学
Martin Fowler
Martin Fowler
T
The Blog of Author Tim Ferriss
爱范儿
爱范儿
小众软件
小众软件
罗磊的独立博客
Recent Announcements
Recent Announcements
Blog — PlanetScale
Blog — PlanetScale
J
Java Code Geeks
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC

Sanity.io

A Board Game agent built using Sanity Context and Vercel's AI SDK | Sanity Build a prototype with Claude Code that your whole team can edit | Sanity What’s New - May 2026 | Sanity I built a London pub guide with v0 and the Sanity MCP in six hours. Here's what I learned. | Sanity Build a conference concierge with Agent Context and Anthropic | Sanity Build a content-aware Telegram agent with Vercel AI SDK and Chat SDK | Sanity How I used Agent API to generate photos for my family’s recipes | Sanity What’s New April - 2026 | Sanity Better context, better matches: An AI love story (for dogs) | Sanity How to write for an agent | Sanity Content Agent, meet Slack: AI content operations in your workflow | Sanity Structure powers intelligence | Sanity Your agent needs better content. Here's how to give it. | Sanity How to serve content to agents (a field guide) | Sanity Sanity TypeGen GA: Automatic TypeScript types for content and GROQ | Sanity Sanity is now available on the Vercel Marketplace | Sanity The logo soup problem (and how to solve it) | Sanity Content Releases: From scattered updates to coordinated publishing | Sanity What's New - February 2026 | Sanity How we solved the agent memory problem | Sanity v0 Builder Challenge: The winners | Sanity Introducing: Sanity Agent Skills | Sanity Content Agent: Days of work in one conversation | Sanity Our Sanity Values | Sanity v0 builder challenge: $3000 in prizes | Sanity Why AI Breaks Without Structured Content Operations | Sanity What’s New January - 2026 | Sanity BFCM 2025: What teams built when infrastructure stopped being the problem | Sanity How AI shaped holiday shopping and what it means for content in 2026 | Sanity Sanity Studio v5: Embracing React 19 | Sanity
Open Source Pledge 2025: Stepping up when it matters | Sa...
Knut Melvær · 2026-01-09 · via Sanity.io

In 2024, we joined the Open Source Pledge, committing to pay $2,000 per year per full-time developer directly to open source maintainers. We're proud to announce we're not just continuing that commitment: we're expanding it to $146,000 (we hired more developers since then, and are still).

But first, we need to talk about Tailwind.

When open source sustainability becomes real

Some days ago, Adam Wathan announced that Tailwind Labs had to lay off 75% of their engineering team. The reason? Despite Tailwind CSS being more popular than ever, used by over 617,000 websites and downloaded 75 million times per month, their revenue dropped 80%.

According to Adam, the culprit is AI. As developers increasingly use tools like Claude, ChatGPT, and Cursor to generate Tailwind CSS directly, traffic to the official documentation dropped 40% since early 2023. That documentation was how developers discovered Tailwind's commercial products: the revenue that funded framework development.

"There's just no correlation between making Tailwind easier to use and making development of the framework more sustainable," Adam writes on GitHub. "If I can't fix that this project is going to become unmaintained abandonware when there is no one left employed to work on it."

This is the paradox we're now living in: a project can be wildly successful and completely unsustainable at the same time.

Why we doubled our Tailwind sponsorship to $60,000

Tailwind CSS isn't just popular, it's essential to how we build at Sanity. From our marketing sites to our documentation to internal tools, Tailwind gives us a fast path to delightful UI/UX.

We use it. Our customers use it. It makes developers productive.

Earlier in 2025, we'd already committed $30,000 to Tailwind as part of our Open Source Pledge. When we learned about the layoffs, we doubled that to $60,000 total: the largest single sponsorship in our pledge. (Yes, we’re currently writing this in 2026, but Sanity budgets operates in the fiscal year that ends at Jan 31).

A check from Sanity US Inc to TAILWIND LABS INC for $30,000, dated Jan 8, 2026, with "FOR BEING AWESOME" in the memo.

This isn't charity. It's recognizing that the tools we depend on need sustainable business models, especially as AI reshapes how developers discover and use software. If companies that benefit from open source don't step up, the projects we rely on won't survive.

Open Source Pledge 2025 breakdown

For 2025, we pledged $146,000 across projects that power Sanity and our community. Here's where the money is going: Tailwind, Motion, Vite, Tanstack, Zod, Babel, libvips, pnpm, Rollup, markdown-it, go-chi, eslint, Vitest, Storybook, pmndrs, Prettier, XState, and Simon Willison.

We're proud to stand on the shoulders of these projects (and many more). Each one represents countless hours of work by maintainers who often don't get the recognition, or compensation, they deserve.

Our other open source contributions

Beyond financial support, we continue to contribute to open source in other ways:

The AI-era wake-up call

The Tailwind situation is a warning for our entire industry. Documentation isn't going away - if anything, it's more important than ever as the source of truth that AI tools learn from and reference. But the business model that sustained open source through documentation seems to be breaking. Developers still benefit from well-documented projects, but they're not visiting the sites where discovery happened.

We don't have all the answers. But we know that companies benefiting from open source need to fund it directly - not because it feels good, but because it's the only way these projects survive the transition to whatever comes next.

If your company uses Tailwind, or Vite, or any of open source projects that make modern development possible, consider joining the Open Source Pledge. The maintainers building your infrastructure need you.

We urge other companies to join the Open Source Pledge and examine how they can support the open source ecosystem in a meaningful way. The future of the tools we depend on depends on it.