Guide · Tech
Build a Topic System That Never Runs Dry — So You Never Face a Blank Page
Every creator knows the dread: it's posting day, the slot is empty, and you're staring at a blank page, trying to think of something. That panic is the symptom of a missing system. The fix isn't more inspiration — it's a place inspiration goes, and a process that turns it into your next video. Liu Weipeng's Dark Time isn't about content at all; it's about how thinking actually works — that your best ideas form in the background hours while you do other things, that knowledge you can retrieve beats knowledge you reread, and that you only truly understand what you can teach. Point those ideas at a topic engine and the blank page disappears for good. This guide builds one: a small, reusable system that captures sparks in your dark time, banks them as a network, and hands you the next thing to make — so you never start from zero again.
Before you start
- One note app or notebook you genuinely keep with you — phone notes, a paper pad, whatever you'll actually open in three seconds. The tool matters far less than the reflex.
- A few minutes a week for upkeep. A topic system isn't a one-time build; it's a habit with a home, and it pays back most when you tend it lightly and often.
- Optional but powerful: your analytics from past videos. The system gets sharper when last week's numbers tell it what to bank more of — if you've read the analytics guide, this is where that loop closes.
Give every spark a home — capture in the dark time
Your best topics don't arrive when you sit down to find them. They arrive in the shower, mid-commute, halfway through someone else's video — what Liu Weipeng calls your dark time, the background hours when your mind keeps working while you do something else. The catch is that a spark has a half-life of about ninety seconds before it's gone. So the first piece of the system isn't clever — it's a single, always-reachable inbox and one rule: every spark goes in within seconds, unjudged, half-formed, ugly. Don't evaluate, don't format, just catch it. A year of these compounds into something no blank-page session can match, because real investment is time multiplied by attention, and the dark time is attention you're already spending.
Catch first, judge laterThe moment you start deciding whether an idea is good is the moment you stop capturing. Separate the two: capture is a reflex, judging is a scheduled job.
Bank it as a network, not a list
A flat list of a hundred ideas is where topics go to die — you scroll it once, feel nothing, and never open it again. A network is alive. As you bank each spark, tag it with the one audience question it answers ("how do I start X?", "why does Y happen?") and link it to anything related you've already noted. Liu Weipeng's point about memory is that you keep what you've retrieved and connected, not what you've reread — and the same is true of ideas. Most of your best topics won't be single sparks; they'll be the new thing that appears when two old notes touch. The network is what makes that collision possible.
Topics live in the linksA lone note is inert. The same note wired to a reader's question and three neighbors becomes a topic you can actually write. Connect on the way in, not someday later.
Bank questions, not just answers
Here's the habit that separates a rich system from a generic one: when you hit something you don't fully understand, resist the reflex to instantly google it away. Write the question into your bank as an open loop — a hole waiting to be filled. Liu Weipeng's rule is that an answer only sticks when the question dug the hole first; an answer you grabbed in two seconds leaves nothing behind. A question you've carried for a week becomes a topic with a real point of view, something only you could write. The answer everyone instantly searches becomes the content everyone already has.
Don't google the loop shutEvery time you instantly look something up, you trade a topic you'd have owned for an answer anyone can find. Bank the question first, let it nag, and write from the nagging.
Filter by "can you teach it?"
Not every captured spark deserves to be made, and the filter is sharper than "is this interesting?" It's this: can you explain it to a beginner without hand-waving? Liu Weipeng's test is blunt — if you can't teach it clearly, you almost certainly don't understand it yet. But a fail here isn't a reject. It's a signal: this topic needs you to go and actually learn it first, and that learning is the article — the most honest kind, written by someone who just crossed the gap. Pull the few you can teach today; leave the rest banked and marked "learn first", a to-do list for your own curiosity.
Can't explain it = not ready yetThe teach test does double duty: it picks today's topics and flags tomorrow's homework. A topic you can't yet teach isn't dead; it's an assignment.
Use writing to turn a spark into a topic
A captured note still isn't a topic — it's a hunch. To find out whether there's a real article inside it, write it out, badly, for five minutes: state the premise, the assumption underneath it, the logic, the conclusion. Liu Weipeng's line is that writing is for thinking, not just for recording what you already thought — and it's brutally honest. The spot where you catch yourself writing "anyway" or "obviously" is exactly where your logic has a hole. Either you fix it, and now you have a stronger piece than you started with, or you discover there's nothing there, and you've saved yourself a wasted video. Five messy minutes of writing sorts the topics from the vibes.
Write to find outDon't wait to understand before you write; write to discover whether you understand. The draft is the test, not the trophy.
Wire it into a loop that runs without willpower
The last piece turns a pile of notes into a system: make it visible, and make it feed itself. Give your ideas a simple pipeline you can see — captured → banked → drafting → shipped — and one fixed slot a week to move things along. Liu Weipeng's advice to design your own progress bar is the quiet engine here: visible progress sustains a habit that willpower can't. Then close the loop. After you ship, listen to what actually worked — your retention, your traffic, the comments — and feed that back into what you bank more of. The system you build, not any single viral idea, is the asset that compounds; willpower runs out, but a pipeline just keeps turning.
Build the system, not the streakMotivation is a bad engine — it's gone by Wednesday. A visible pipeline that feeds on its own results keeps producing long after the inspiration fades.
Watch it run for a week. Monday, mid-shower, you think "why do my long videos hold people better than my short ones?" — straight into the inbox, ninety seconds, done. Tuesday you bank it under the question "how long should my videos be?" and link it to an old note on pacing. Wednesday you almost google "ideal video length", stop, and leave it as an open loop instead — you want your answer, not everyone's. Thursday you try to explain the hunch to a friend, can't quite, and realize you need to look at your own retention data first, so it gets marked "learn first". Friday you spend five messy minutes writing it out, hit an "anyway" right where your logic was thin, and patch it. By the weekend you don't have a blank page — you have a drafted topic with a real point of view, pulled from a system that was working in the background all week. Next week the bank is fuller than this one. That's the whole point.
Check your work
- I have one always-reachable inbox, and a rule that every spark goes in within seconds — unjudged.
- I bank each idea linked to the audience question it answers and to related notes, not as a flat list.
- I write down questions I don't fully understand as open loops, instead of instantly googling them away.
- I filter topics by whether I can actually teach them — and mark the rest "learn first".
- I spend a few messy minutes writing a spark out before deciding it's a real topic.
- I have a visible pipeline and a weekly slot, and I feed last week's results back into what I bank.
The one line to keep
Inspiration isn't something you wait for — it's a system you build. Capture in the dark time, bank it as a network, and you'll never face a blank page again.
Framework drawn from Liu Weipeng's Dark Time — the idea of dark time (the background hours when your mind keeps working), that retrieved-and-connected knowledge outlasts what you merely reread, that thinking first beats instantly searching, that you only understand what you can teach, that writing is a tool for thinking, and that a visible progress bar sustains a habit better than willpower. Dark Time is a book about learning and thinking, not content creation; the application to a creator's topic system is this guide's own. A popular-science, how-to reading; intellectual property belongs to the original author. © vlog.bluecatbot.com 2026.