Skip to content

Commit ffb7f31

Browse files
committed
The Drop Times and Sponsorship Data
1 parent 749cc01 commit ffb7f31

1 file changed

Lines changed: 62 additions & 0 deletions

File tree

Lines changed: 62 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
---
2+
title: "From a Single Chat to a Live Sponsorship Feed: DDEV's Sponsorship Data Story"
3+
pubDate: 2026-03-27
4+
summary: "How a request from TheDropTimes to track DDEV sponsorship data led to a web component, a public data feed, and live sponsor displays across DDEV properties."
5+
author: Randy Fay
6+
featureImage:
7+
src: /img/blog/2026/03/sponsorship-data.png
8+
alt: DDEV sponsorship data displayed across web properties
9+
categories:
10+
- Community
11+
- Announcements
12+
---
13+
14+
<!--
15+
TODO:
16+
* So much thanks to Anoop for the support and the inspiration
17+
* So much thanks to The Drop Times for continuing to promote
18+
* Banner: The Drop Times banner
19+
-->
20+
In January 2025, Anoop John of [TheDropTimes](https://www.thedroptimes.com/) sent a message that sparked something bigger than any of us expected:
21+
22+
> "Happy New Year. I was thinking we could put a live sponsorship tracker for DDEV on TDT. We should ask for people for $5 per month and we need 1000 people to hit the target right? What do you think?"
23+
24+
That single message set off a chain of events that ended with live, auto-updating DDEV sponsor displays on multiple web properties, a public data repository, and a reusable web component—all feeding from a single source of truth.
25+
26+
## The Challenge
27+
28+
DDEV's financial sustainability depends entirely on sponsorships (we have no other income). Communicating that need—and showing progress toward goals—requires getting accurate, up-to-date data in front of people where they already spend time. But manually updating sponsor lists across multiple sites is tedious and error-prone.
29+
30+
What we needed was a data feed that could be consumed anywhere, updated automatically, and displayed consistently.
31+
32+
## The sponsorship-data Repository
33+
34+
The first piece was a public repository: [ddev/sponsorship-data](https://github.com/ddev/sponsorship-data). This repository aggregates sponsorship information from GitHub Sponsors and other sources, and is updated automatically on a daily schedule. The data is available as structured JSON that any site or tool can consume.
35+
36+
The pull request that kicked this off: [ddev/sponsorship-data#5](https://github.com/ddev/sponsorship-data/pull/5).
37+
38+
## Mark Conroy's Web Component
39+
40+
[Mark Conroy](https://mark.ie/) stepped up with a reusable web component that reads from the sponsorship-data feed and renders a live sponsor display. The component lives at [web-components.mark.ie](https://web-components.mark.ie/) and is open source at [markconroy/web-components](https://github.com/markconroy/web-components).
41+
42+
The feature request that started that work: [markconroy/web-components#1](https://github.com/markconroy/web-components/issues/1).
43+
44+
The component makes it trivial to embed a live sponsor list on any site—no backend required, no manual updates.
45+
46+
## Integration into DDEV Web Properties
47+
48+
With the data feed and component in place, we integrated the live sponsor display into ddev.com. The work to add this is tracked in [ddev/ddev.com#339](https://github.com/ddev/ddev.com/issues/339).
49+
50+
Now, when sponsors join or leave, the displays update automatically. No manual edits to site content, no stale lists.
51+
52+
## What `ddev start` Shows
53+
54+
The data feed also powers what users see when they run `ddev start`. The daily update cycle means the sponsor information shown in the CLI is never more than a day old. Users see current sponsors every time they start a project.
55+
56+
## Why This Matters
57+
58+
The sponsorship situation for DDEV is real: the project needs ongoing financial support to continue development and remain free for everyone. Getting that message in front of people—accurately and consistently—helps.
59+
60+
The path from Anoop's January email to live sponsor feeds across multiple properties took a few months of collaboration between community members who cared. That's how open-source sustainability work actually gets done.
61+
62+
If you use DDEV and find it valuable, consider sponsoring at [github.com/sponsors/ddev](https://github.com/sponsors/ddev). Even $5/month adds up when enough people participate.

0 commit comments

Comments
 (0)