· 6 minute read
The Content Library
How keeping and developing your ideas can make them useful beyond the platform where you first shared them.
A content library collects ideas you've developed and written down over time. It includes perspectives, named frameworks, tested arguments, positions you refined through doing the work.
It might be the most important asset you can build right now, because it's the one thing that survives when platforms shift.
Example library. Titles, dates and reuse counts below are illustrative.
The idea came from Nicolas Cole. He was being interviewed about his next book, which is built around this concept of helping writers develop a content library. I was listening on a dog walk and kept thinking about the idea afterwards.
A week later, a longer video from Cole about the future of X. Same concept, but reframed: the content library as the setup, the distribution channel as the payoff. That helped me connect it to my own work. Because this wasn't just a creator strategy being described. It was an editorial philosophy I'd been circling, in conversations about how content teams should evolve, in the practice of writing essays on this website, in the slow realization that all of these threads were pointing at the same thing.
The same idea can be useful in several formats and on several platforms.
Most people create for a platform. The blog post is for the blog. The thread is for Twitter. The video is for YouTube. The format shapes the thinking from the start. And when the platform declines, which they all do, the content feels stranded. It belonged to that place.
With a content library, you develop the argument first, then decide where and how to share it.
The cycle that keeps repeating
I have watched writers build audiences on Quora, Medium, Substack and X. These platforms overlap rather than neatly replace one another. Their appeal and distribution rules change, which makes me wary of keeping all my work in one place.
Every few years, the smartest platform bet shifts. Writers rebuild.
The version of this that hits closest to home isn't any of those platforms. It's search. I've spent ten years writing long-form content, building websites, bringing people to those sites through search. That was the reliable channel. Steady once you earned real estate in the search results. More dependable than any social platform. And now AI overviews and AI-generated answers are reshaping that entire landscape. I can no longer assume that channel will keep working as it did.
That vulnerability, the realization that your distribution channel can shift underneath you, is exactly why the library matters. The creators who adapt to these changes aren't starting over each time. They already have the thinking. They just need new packaging.
Theses, not topics
Not everything qualifies for a library.
An article explaining "how to set up Google Analytics" is useful, but it expires. The interface changes, the steps change. That's maintaining information, not building a body of thought.
The distinction I keep coming back to: a topic tells people what the content is about. A thesis tells them what it argues. Anyone can write about a topic like marathon training. A thesis ("Running a marathon is mental, not physical") belongs to the person who arrived at it. I wrote more about this distinction in why helpful content gets forgotten.
A thesis gives you an argument to revisit and develop, rather than just a subject to cover again.
This matters because theses are what make deployment work. I developed a perspective on the difference between being tracked and choosing to see yourself, a thesis I arrived at through five years of daily time tracking and then building my own tool around that philosophy. That thinking can become an essay, a podcast episode, a conference talk, an X article, or a chapter in a book. Each format requires adaptation, but the core argument already exists. I can adapt the argument instead of starting again.
A topic ("time tracking tips") can't travel like that. I'd still need to decide what I wanted to say about it.
The depreciation problem
I've noticed how quickly I forget ideas I haven't written down.
A conversation helps you see a connection between two ideas or understand why something worked. In the moment, it feels vivid. A week later, the edges blur. A month later, you remember having the insight but not the insight itself. Six months later, it's gone.
Good ideas are easy to lose when you don't record them. They stay in conversations or half-formed thoughts that are hard to revisit.
And it's not just unwritten thinking. Partially-written thinking depreciates too. A brief at 70% completion, a half-formed doc and notes from a brainstorm can become harder to understand once the team moves on. The edges blur. The context fades. A year later, you're re-deriving insights you already had.
Deciding to publish makes me finish the argument. Making an essay or video public means explaining it to people who weren't part of the original conversation. I have to explain the connections. The argument has to hold for someone who doesn't share your context. Things have to be named precisely enough that a stranger could follow.
This essay is a good example. The conversation that led to it started in a completely different place, an analysis of my existing essays, a question about audience, an observation about what the writing had in common. The content library concept emerged through the dialogue, then evolved through the drafting, and the argument you're reading now is significantly different from where I began. Writing doesn't just capture thinking. It develops it.
The content library is what accumulates when this becomes a practice. Each finished piece gives me something I can return to. And over time, the collection becomes more valuable than any individual piece, because it represents how your understanding of the subject has developed.
What a deep library makes possible
The library reframes the daily question.
The old question: What should I create for this platform? Starting from scratch, shaped by the platform's constraints. The post lives and dies there.
The library question: Which piece of my existing thinking fits this format?
An essay on how story triggers activate psychological responses? That becomes a Twitter thread breaking down one trigger with a film example. A podcast episode going deeper into the research. An X article with the full argument. A workshop exercise for a content team. Different packaging, same thinking.
A library gives you somewhere to look before starting a new piece. You may already have an argument worth adapting.
A library on your own website also gives search engines something to discover. Useful, accessible pages may continue bringing people in over time. Owning the domain or having a clear thesis does not guarantee traffic, and the library still needs maintenance.
The platforms will keep shifting. Something that doesn't exist yet will have its moment in 2028. When that happens, I want to have ideas ready to adapt.
That's what I'm building the library for.
This is a working document. The content library as a concept is still forming, as a personal practice and as an editorial philosophy. This essay will probably look different in six months as more of the thinking gets tested through deployment.