First commit on the local Gitea server, made after moving the tree off the Windows machine. Build outputs, node_modules and the AI models stay out (see .gitignore); everything the installer build needs is tracked. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
3.9 KiB
3.9 KiB
GitHub Search Guide for NLT Bible Data
🎯 Exact Search Terms to Use
Primary Searches:
- "NLT bible JSON" - Most likely to find complete datasets
- "bible data NLT" - Alternative search term
- "scripture NLT" - Broader search
- "new living translation JSON" - Full name search
- "bible-api NLT" - API-related datasets
Secondary Searches:
- "bible translations JSON" - May include NLT
- "scripture database NLT" - Database format
- "bible text NLT" - Text format
- "holy bible NLT" - Alternative terms
📋 Specific Repositories to Check
Known Bible Data Repositories:
-
https://github.com/scrollmapper/bible_databases
- Large collection of Bible databases
- May have NLT in various formats
-
https://github.com/bibleapi/bibleapi-bibles-json
- Bible API project
- Multiple translations including NLT
-
https://github.com/scrollmapper/bible_versions
- Bible versions repository
- Check for NLT data
-
https://github.com/JohnRDOrazio/LiturgicalCalendar
- May have Bible data as part of larger project
-
https://github.com/openbibleinfo/Bible-Data
- Open Bible Info project
- Various Bible datasets
🔍 How to Search Effectively
Step 1: Use GitHub Advanced Search
- Go to: https://github.com/search
- Use these search terms in order:
NLT bible JSONbible data NLTscripture NLT
Step 2: Filter Results
- Language: JavaScript, JSON, or All
- Sort by: Most stars or Recently updated
- Size: Look for repositories > 1MB (likely to have complete data)
Step 3: Check Repository Contents
Look for files like:
nlt.jsonNLT.jsonbible-nlt.jsonnew-living-translation.jsonscriptures/nlt/data/nlt/
📁 What to Look For
Good Signs:
- ✅ Repository size > 1MB
- ✅ Recent updates
- ✅ Multiple stars
- ✅ Clear documentation
- ✅ JSON or JavaScript files
- ✅ Mentions "NLT" or "New Living Translation"
Avoid:
- ❌ Very small repositories (< 100KB)
- ❌ No recent activity
- ❌ No documentation
- ❌ Binary files only
🚀 Quick Action Plan
Search Order:
- Search:
"NLT bible JSON" - Search:
"bible data NLT" - Check the specific repositories listed above
- Look for files with "nlt" in the name
Download Process:
- Find a repository with NLT data
- Look for JSON files
- Download the raw JSON file
- Convert to the format needed for nlt-data.js
📝 Expected File Formats
Format 1: Book-based JSON
{
"Genesis": {
"1": {
"1": "In the beginning God created the heavens and the earth.",
"2": "The earth was formless and empty..."
}
}
}
Format 2: Verse-based JSON
[
{
"book": "Genesis",
"chapter": 1,
"verse": 1,
"text": "In the beginning God created the heavens and the earth."
}
]
Format 3: API-style JSON
{
"verses": [
{
"verse": 1,
"text": "In the beginning God created the heavens and the earth."
}
]
}
🎯 Success Indicators
You've found good NLT data when:
- ✅ File contains all 66 books
- ✅ Has verse numbers
- ✅ Text is properly formatted
- ✅ No missing verses
- ✅ File size is reasonable (1-5MB)
🔧 Conversion Process
Once you find the data:
- Download the JSON file
- Check the format
- Convert to match nlt-data.js structure
- Test with the implementation guide
- Replace placeholder data
📞 Need Help?
If you find a repository but need help:
- Share the repository URL
- Describe the file format
- I'll help you convert it to the right format
This guide should help you find complete NLT Bible data quickly!