The substrate
This method runs on the Bible Reference community plugin for Obsidian. Install it, choose your preferred translation (mine is the KJV), and turn on Expert Settings, and select an option for Add a Chapter Outgoing Links. I use Header. That wikilink is what eventually weaves every verse you capture into your vault’s graph.
The trigger syntax is two hyphens followed by the reference. Typing --Acts 1:1-2 produces a formatted callout with the verse text and a wikilink to the chapter note. If you’re on mobile or without a keyboard, the same command is available through the Obsidian command palette.
The parallel reader
You also need a digital Bible with quick Strong’s lookup. I use Olive Tree on Android with a Strong’s-hyperlinked edition, but the specific app doesn’t matter. What matters is that you can tap a word and see its Strong’s entry in one or two motions. Logos, Blue Letter Bible, e-Sword, and others all work. The point is speed during live listening.
The capture rhythm
A pastor names a reference. You key it in. The callout appears. You glance at the parallel reader to see the original language, and you mark what catches you using Obsidian’s ==highlight== syntax inside the callout.
There are two reasons to highlight, and it’s worth being clear about them:
Homiletical highlighting marks what the preacher emphasized, the phrase he returned to, the sentence he pulled out as the heart of the passage. You highlight it because it carried weight in the room.
Linguistic highlighting marks individual words where the original language caught your attention. A Greek word with a richer texture than the English translation conveys. A Hebrew verb with an aspect that changes what the verse is doing. You highlight it because the word itself is interesting.
Same mechanic, two motives. They often overlap, but they don’t have to.
The Strong’s appendix
Directly below the verse callout, in plain text rather than another callout, I add a formatted Strong’s entry for each linguistically highlighted word, in the order they appear in the verse. The format looks like this:
The wikilinked Strong’s ID at the front is what closes the loop. The lexemes sit outside the callout on purpose. Nested callouts are visually noisy, and the lexemes are dependent on the verse above rather than freestanding, so plain text below preserves the verse as a clean visual unit while keeping the lexemes clearly subordinate.
You can get the formatted text from Claude or copy it from your Bible app. Either works.
One nice property of Obsidian: the wikilink to the lexeme works whether or not the lexeme note exists yet. You can adopt this method today and let your Strong’s corpus grow organically as you encounter words worth keeping.
What the graph gives you
Every captured verse backlinks to its chapter note. Every Strong’s entry backlinks to its lexeme. Open a chapter note and you can see every place in your vault where you’ve engaged with that chapter. Open a lexeme and you can see every verse where the word caught your attention.
Over time, this builds something that no app can give you: a record of how you have encountered scripture, with the original language present, indexed by both reference and root word, and growing denser every time you sit under preaching.
Worked example
Putting the pieces together, here is what a captured verse looks like in raw markdown:
> [!bible]+ Luke 24:12 - KJV [[Luke 24]]
> 12. Then arose Peter, and ran unto the sepulchre; and stooping down, he beheld the linen clothes laid by themselves, and departed, ==wondering== in himself at that which was come to pass.
[[g2296]]. θαυμάζω thaumazō; from 2295; to wonder; by implication, to admire: — admire, have in admiration, marvel, wonder.
Rendered in Obsidian, with the callout styling applied and the wikilinks resolved, it looks like this.