- Enhance Bible service to support ESV API HTML-formatted passages - Add download-on-demand functionality for Bible content - Implement automatic chapter note creation in vault - Update settings to include ESV API token and download options - Improve Bible reference parsing and content retrieval - Add CSS styles for rich HTML Bible passage rendering |
||
|---|---|---|
| src | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc | ||
| .gitignore | ||
| .npmrc | ||
| esbuild.config.mjs | ||
| esv2.json | ||
| LICENSE | ||
| main.ts | ||
| manifest.json | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| styles.css | ||
| tsconfig.json | ||
| version-bump.mjs | ||
| versions.json | ||
Disciples Journal - Bible Verse Reference Plugin for Obsidian
This plugin enhances your Bible study and journaling in Obsidian by rendering Bible verse references and passages directly in your notes.
Features
Inline Verse References
Type a Bible reference in an inline code block like this:
`Genesis 1:1`
The plugin will transform it into a clickable link. When you:
- Hover over the reference: Shows a preview of the verse text
- Click on the reference: Opens or creates a note for that chapter in your vault
Full Passage Rendering
For longer passages, use a code block with the "bible" language specifier:
```bible
Genesis 1:1-10
```
This will render the entire passage directly in your note, displaying all verses in the range.
Enhanced ESV HTML Format Support
The plugin now supports ESV's HTML formatted passages, providing richer rendering with:
- Proper typesetting for poetic passages
- Section headings
- Footnotes and cross-references
- Proper formatting for special text
Download on Demand
With an ESV API token, the plugin can automatically download Bible passages that aren't already in your local library:
- Enter your ESV API token in the plugin settings
- Enable the "Download on Demand" option
- When you reference a passage that isn't already available, it will be downloaded automatically
- Downloaded passages are saved locally for future use
- Chapter notes are created in your vault automatically for easy navigation
Organized Content Structure
Downloaded Bible content is saved in an organized folder structure:
Bible/ESV/
├── Genesis/
│ ├── Genesis 1.md
│ ├── Genesis 2.md
│ └── ...
├── Exodus/
│ ├── Exodus 1.md
│ └── ...
└── ...
You can customize this path in the settings to fit your vault organization.
Supported Reference Formats
The plugin supports various Bible reference formats:
- Single verses:
Genesis 1:1,John 3:16 - Verse ranges in the same chapter:
Genesis 1:1-10,John 3:16-18 - Entire chapters:
Genesis 1,Psalm 23 - Multi-chapter passages:
Matthew 5:3-7:29 - Books with spaces:
1 Corinthians 13:4-7,Song of Solomon 2:1
Settings
Access plugin settings in Settings → Disciples Journal:
-
Display Settings:
- Display Inline Verses: Toggle inline verse reference rendering
- Display Full Passages: Toggle full passage code block rendering
- Verse Font Size: Customize the font size for displayed verses
-
Bible Version Settings:
- Currently only supports the English Standard Version (ESV)
-
Bible Content Vault Path:
- Specify the vault directory where chapter files will be saved
- Default is
Bible/ESV - Each book will get its own subdirectory (e.g.,
Bible/ESV/Genesis/)
-
ESV API Settings:
- ESV API Token: Enter your token from api.esv.org
- Download on Demand: Enable automatic downloading of requested passages
-
Diagnostics:
- Check Bible data loading status
- Reload Bible data if needed
Installation
- In Obsidian, go to Settings → Community plugins → Browse
- Search for "Disciples Journal"
- Click Install, then Enable
Manual Installation
- Download the latest release from the releases page
- Extract the zip file to your Obsidian plugins folder:
.obsidian/plugins/ - Make sure the
ESV.jsonfile is in thesrcdirectory within the plugin folder - For enhanced rendering, place ESV API HTML-formatted JSON files in the
src/data/esvdirectory - Enable the plugin in Obsidian's community plugins settings
Using ESV API HTML Format
There are two ways to use the enhanced HTML format:
Manual Method
- Obtain passage data from the ESV API (requires an API key)
- Request passages using the HTML format endpoint
- Save the response JSON files in the
src/data/esvdirectory - Name files according to their reference (e.g.,
Genesis 1.json,John 3.json)
Automatic Method
- Get an ESV API token from api.esv.org
- Enter the token in the plugin settings
- Enable "Download on Demand"
- The plugin will automatically download and save passages when needed
The plugin will automatically detect and use these files when available, providing rich HTML rendering of the passages.
Getting an ESV API Token
To use the download-on-demand feature, you'll need an ESV API token:
- Go to api.esv.org and create an account
- Log in and create a new API key
- Copy the token and paste it into the plugin settings
- Your token will look something like:
5bea343abb51ab0434a6e929081ab1c4964feef7
Chapter Notes in Vault
When you click on a Bible reference or download a chapter, the plugin creates a well-formatted note in your vault:
- Notes are stored in the path specified in settings (default:
Bible/ESV/[Book]/[Chapter].md) - Each book has its own folder for organization
- Notes include a
biblecode block that renders the passage - Notes are automatically opened when you click on a reference
Troubleshooting
Bible Data Not Loading
This plugin requires either the ESV.json file, HTML-formatted chapter files, or an ESV API token to be properly configured. If you see an error about Bible data not loading, try these steps:
- Go to Settings → Disciples Journal → Diagnostics
- Click the "Reload Bible Data" button
- If that doesn't work, verify that either:
- The
ESV.jsonfile exists in the plugin'ssrcdirectory, or - HTML-formatted chapter files exist in the plugin's
src/data/esvdirectory, or - You have entered a valid ESV API token and enabled "Download on Demand"
- The
- Restart Obsidian and try again
Verse References Not Working
If your verse references aren't being processed correctly:
- Make sure the plugin is enabled
- Check that you're using the correct format (e.g.,
Genesis 1:1inside backticks) - For code blocks, ensure you're using the "bible" language specification
- Try reloading the plugin through Settings → Disciples Journal → Diagnostics
Chapter Notes Not Being Created
If chapter notes aren't being created or opened when you click on references:
- Check that the vault path specified in settings exists or can be created
- Make sure you have permission to write to that directory
- Try manually creating the directory structure if needed
- Ensure "Download on Demand" is enabled if you're using the ESV API
Scripture Copyright
Scripture quotations marked "ESV" are from the ESV® Bible (The Holy Bible, English Standard Version®), copyright © 2001 by Crossway, a publishing ministry of Good News Publishers. Used by permission. All rights reserved.
Feedback and Contributions
If you encounter any issues or have suggestions for improvements, please open an issue on GitHub.
License
This project is licensed under the MIT License - see the LICENSE file for details.