How to turn your notes into published articles and books using the Obsidian app with Eleanor Konik

Turning raw reading notes into publishable articles isn’t about collecting more information—it’s about filtering for a purpose, converting highlights into structured “atomic” claims, then using Obsidian to assemble those claims into drafts and topic maps that can be rediscovered later. Eleanor Konik’s workflow treats note-taking as a pipeline: capture what matters, process it into usable statements, and then connect it to an article-ready structure. The payoff is practical: her article output increases, freelance writing opportunities follow, and her research becomes a reusable creative engine rather than a pile of excerpts.

Konik frames the process around a specific goal: she doesn’t highlight everything in a textbook because that guarantees endless storage without production. Instead, she reads with an intended product in mind—she’s often writing about history infrastructure and how societies formed. While reading “Beyond the Blue Horizon,” she deliberately ignores memorization-style details (dates, places, conversions) and hunts for patterns that can become claims. When she finds a passage about navigation challenges in the North Atlantic—storms, rocks, strong tides, and onshore winds—she highlights it not as trivia but as story fuel and as material for later synthesis. She tags it (e.g., “MOC for difficult sailing conditions”) so it can be turned into lists, maps of context, or fiction obstacles.

The next step is converting Kindle/PDF highlights into Obsidian-ready notes. She exports highlights into Markdown, then organizes them into a literature-notes folder—while still using links and tags as first-class structure. She emphasizes repetition and pruning: she revisits notes over time to delete what doesn’t earn its keep and to ensure the ideas still make sense. Her Kindle annotations become structured entries with headings and unique identifiers (she uses “location” numbers as searchable anchors). She also uses a “backlink dump” note as a scratchpad for connections—collecting ideas that later become blog posts or articles—then deletes entries once they’ve been promoted into forward links.

A major theme is synthesis through “maps of content” (MOCs). Konik uses these topic hubs to let ideas “battle” and interact, creating a workbench for drafting. She also uses Dataview to avoid manually maintaining indexes: each note carries YAML metadata (like type, market/outlet, and status such as “seed” vs “published”), and Dataview queries generate tables of candidate article drafts. That turns Obsidian into a retrieval system: when deadlines hit, she can pull up the most finished “seed” items without digging through backlinks.

Finally, she argues for imperfect but functional organization. She keeps raw literature notes long when splitting them would slow production, paraphrases and trims excerpts into atomic claims, and sometimes leaves content in place to avoid citation/linking overhead. Her philosophy is explicit: don’t let “perfect notes” block “good enough” writing. The system’s purpose is to produce—whether for nonfiction, fiction worldbuilding, or articles—by repeatedly turning reading into publishable structure and then reflecting monthly on what truly mattered.