Graph-First, Not Feed-First
Feeds reward recency. Graphs reward relevance. We chose the graph — and it changed everything about how we design features.
Every platform you use today is organized around a feed. New things at the top, old things gone. It works because it's simple — but it also means the most valuable thing someone posted three months ago is functionally invisible.
We decided early on that Madless wouldn't work this way.
The feed assumption
Feeds assume that what matters most is what happened most recently. That's true for news. It's terrible for knowledge.
If you're running a community around design systems, someone's deep-dive into token naming conventions doesn't expire after 48 hours. It might be the most useful thing in the entire space — but a feed buries it under yesterday's casual questions.
The feed is a publishing primitive. It optimizes for content creation, not content value.
What a graph gives you
When you organize around a graph instead of a timeline, every piece of content has a position — not just an age. A note about API design sits near other notes about API design, regardless of when it was written.
This changes three things:
- Discovery becomes structural. You find things by navigating relations, not scrolling.
- Old content stays alive. A well-connected node from six months ago surfaces naturally when you explore its neighborhood.
- Context is automatic. When you view something, you see what it relates to — not just what was posted around the same time.
How this shaped our features
Every feature in Madless passes through a simple filter: does this make the graph richer?
Sponge (our knowledge layer) is the graph itself — concepts, relations, layers. When you create a note, you're not posting to a feed. You're placing a node in a space.
Ocean (community discussions) feeds back into the graph. Conversations don't just disappear — insights from them can be absorbed into Sponge, becoming permanent structure.
Drive stores files, but files are nodes too. An uploaded PDF about typography lives near your notes about typography, near conversations about typography.
Nothing exists in isolation. Everything has neighbors.
The tradeoff
Graphs are harder to build and harder to explain. A feed is immediately intuitive — everyone knows how to scroll. A graph requires a different kind of interaction, and we've spent months getting the UX right.
But the payoff is that your space gets more valuable over time, not less. A feed-first community gets noisier with age. A graph-first community gets smarter.
That's the bet we're making.