A static, GitHub Pages-compatible personal Bible study site.
- Push this entire folder to a GitHub repository.
- Go to Settings → Pages → set Source to
mainbranch, root/. - Your site will be live at
https://yourusername.github.io/your-repo/.
index.html ← The entire app (single file)
data/
index.json ← Manifest — lists all books & chapters ← YOU MAINTAIN THIS
genesis/
overview.md ← Book introduction page
1/
guide.md ← Chapter 1 study guide
2/
guide.md ← Chapter 2 study guide
john/
overview.md
1/
guide.md
data/
romans/
overview.md
1/
guide.md
{
"books": [
{
"id": "romans",
"name": "Romans",
"testament": "NT",
"chapters": [
{ "id": "1", "title": "Chapter 1 — The Gospel of God" },
{ "id": "2", "title": "Chapter 2 — God's Righteous Judgment" }
]
}
]
}idmust match the folder name exactly (lowercase, no spaces).testamentis optional ("OT"or"NT"). When present, the sidebar splits into Old / New Testament sections.chaptersis an array of objects. Add each chapter after you write its guide.
Use standard Markdown. Suggested sections:
# Book Name
## Overview
Brief description of the book.
## Key Themes
- Theme 1
- Theme 2
## Key Verse
> "Verse text here." — Reference
## Structure
| Section | Chapters | Focus |
|---------|----------|-------|
| ... | ... | ... |# Book Chapter — Title
## Key Verses
> "Verse..." — Reference
## Context
Background and setting.
## Study Notes
### Sub-topic
Content...
## Discussion Questions
1. Question one?
2. Question two?
## Cross References
- **Reference** — brief noteThe search bar (or Ctrl/Cmd + K) searches all registered books and chapter titles from index.json. It does not search file content — only titles.
- No build step required. Everything runs in the browser.
- Markdown is rendered client-side via marked.js.
- The site fetches files with
fetch()— this works on GitHub Pages but not from a localfile://path. Use a local server (e.g.,python3 -m http.server) for local testing.