I Contributed to Chroma's Open-Source Docs — Here's What I Changed and What I Learned

Chroma is one of the most widely used open-source vector databases in the AI ecosystem. It's the backbone of countless RAG pipelines, semantic search systems, and AI agent memory layers — including projects I've built myself. So when I found issue #3111 on their GitHub — a request to update their Haystack integration documentation — I decided to take it on.

The issue was straightforward: the existing docs were outdated, lacked clear installation steps, and had almost no practical examples for ChromaDocumentStore. But when I looked closer, I found two already-open PRs. That's where it got interesting.

The Existing PRs

Before writing anything, I checked what others had already done. There were two open PRs for this exact issue:

PR #3112: Deleted the entire documentation file. The contributor decided the best way to "update" the docs was to remove them entirely. This doesn't help users — it just creates a dead link.