Skip to content
DiscipleGo
Staging

Bible Reading Plan

First release

The private, admin-only /bible reader uses a reviewed JSON snapshot of the user's 2026 260 Plan.xlsx from Dropbox/Team.Share/Archive/Resources/Bible Plans. The original workbook is unchanged. This is a read-only reader, not a completed tracking system or database import. Dates use America/Chicago for the shared Today schedule.

The snapshot preserves all 260 numbered dates, four category references, Jesus Said statements and references, and primary calendar-week memory references. Source sheets were compared with all numbered presentation rows. The reader still uses translation providers for display; the separately imported KJV is canonical reference and administrative data.

Memory weeks follow the workbook calendar, not groups of five readings. Week 53 is memory review; December 31 is catch-up/reflection, as approved. Weekends have no new assignment. Unsupported years do not silently repeat the 2026 plan.

One official Biblia Embedded Bible iframe opens the selected passage, requesting NET (gs-netbible). The app cannot inspect cross-origin contents, guarantee a translation, mark reading completion from iframe activity, or control the iframe's styling. A direct fallback opens the same official reader. The embed makes a third-party request to Biblia; do not send private reflections or account data in its URL.

Embed documentation: https://biblia.com/plugins/EmbeddedBible

Translation roadmap

  • Verify NET availability while signed out, exact NET edition, passage-range behavior, and full translation-note availability in the embed. Never silently label a fallback translation as NET.
  • NET is the preferred default. Future DBS comparison should offer NET, NLT, and NKJV tabs, preserving the passage when switching.
  • Add user-selected default translation and ordered comparison preferences after authorized sources are verified.
  • Evaluate the official NET API and obtain clarity on full translation-note access, attribution, caching, local hosting, offline use, and church-branded distribution. API documentation: https://labs.bible.org/api_web_service
  • Evaluate authorized NLT/NKJV sources, including API.Bible, and review each translation's terms for the intended use.
  • Audit resources/xml in dgosocial for provenance, edition, text integrity, and rights before importing. Existing NET/NLT/NKJV XML has verse text but no structured notes or pericope headings. File possession does not establish redistribution rights.
  • Keep references and completion independent of translation/provider. Replace the iframe through a dedicated reader component/provider boundary when moving to an API.
  • Render NET notes in a desktop side panel/mobile sheet when authorized access is available.

Next build steps

  • Add repeatable validated import tooling and source-row provenance. Reject missing/duplicate days and unresolved formula errors rather than silently repairing source content.
  • Review the eight supplemental memory references, unlabelled Sheet1, and video columns separately. These are not imported into this first reader. Media columns contain both URLs and editorial notes.
  • Add section completion/undo and private reflections with ownership tests; opening an iframe does not mean a passage was read.
  • Add weekly browsing, memory practice, shared-day links, and calendar reminders. Keep personal data out of shared links.
  • Add plan authoring, duplication/versioning, and explicit schedule publication through Filament. Preserve historical progress when content changes.
  • Continue editing canonical DGO pericope boundaries in Filament, keeping editorial headings distinct from Scripture and allowing manual passage overrides.
  • Test mobile scrolling, signed-out Biblia behavior, network failure, multi-book references, and the eventual mobile wrapper before production use.

Live embed verification: September 22, 2026

The initial resource identifier netbible returned Not Found. Correcting it to gs-netbible successfully displayed NET text and note links without signing in. The iframe is enabled by default; set BIBLIA_EMBED_ENABLED=false to use the external NET reader fallback. Exact edition, full note behavior, multi-book passages, and mobile-wrapper support still require verification.

Reader navigation

The reader now has three top-level sections: Daily Reading, Jesus Said, and Memory. Daily category controls sit above one shared iframe. Jesus Said and Memory load their Scripture automatically and provide an explicit Read below anchor. Memory weeks can be browsed independently without changing the selected daily date; This week restores the week of that selected date. Memory practice remains available on weekends. The date picker is collapsed under Choose date to keep the main controls compact. Inline Scripture rendering remains deferred until an API is adopted.

Native NET reader (supersedes the iframe)

The active reader now uses the official Bible.org NET API server-side with formatting=para. It renders returned verses as escaped text, with verse labels and paragraph boundaries, in the app's layout. No iframe, nested scrolling, or permanent Scripture-text import is used. Requests have bounded timeouts; unavailable or malformed responses show a fallback link. Text size can be adjusted in the reader. The old Biblia configuration is no longer used by this screen.

Live checks covered Mark 15:21-41 and a multi-book passage. The API supplies note markers in full mode, not a verified full note service; notes remain an external NET link. Poetry indentation and inline emphasis are not fully preserved by this first text renderer. The API's exact edition is not asserted.

Permissions reviewed: https://netbible.com/copyright/ permits noncommercial text use with attribution, but does not include notes in that grant. Attribution and a linked NET designation are displayed. This implementation remains private/admin-only. Reassess permissions before monetization, paid church branding, offline distribution, or adding hosted notes. API documentation: https://labs.bible.org/api_web_service

NLT second translation

NET remains the default; NLT is the second reader tab. Translation links retain the selected date, category, section, and memory week. Daily/category/week navigation retains the translation. NKJV is the next planned provider, not an enabled tab yet.

NLT uses Tyndale's official https://api.nlt.to/api/passages endpoint and NLT_API_KEY from server-side configuration. Never place the key in a browser URL, source control, error context, or logs. Provider transport errors are replaced with generic exceptions without the original authenticated URL. No persistent text caching is implemented.

The NLT adapter extracts verse text and removes embedded note controls and editorial headings; these are not mixed into Scripture. Text is escaped by Blade. Full poetry formatting, notes, and richer formatting remain follow-up work. Copyright attribution is translation-specific. Verify any commercial, offline, or church-branded redistribution terms before launch. Documentation: https://api.nlt.to/Documentation

NKJV third translation

NKJV is now the third tab, following NET and NLT, using the account-verified API.Bible edition 63097d2a0a2f7db3-01. API_BIBLE_KEY remains server-side and is sent only in an API header. NIV and CSB are not enabled yet.

Passage reference search supports the plan's multi-book references. The adapter returns escaped verse text in the existing reader and displays provider copyright attribution. Potentially truncated responses at the documented 200-verse ceiling fail visibly rather than being labeled complete; chunking longer readings remains follow-up work. No persistent Scripture caching is used. API failures have a translation-specific external fallback.

NKJV views load API.Bible's FUMS usage-reporting script and report the provider-issued view token. This third-party reporting collects passage and anonymous device/session usage; no notes, email, name, or API key is supplied. Include this in launch privacy disclosures. Review current tracking/licensing requirements before public launch. Noncommercial NKJV access has a 5,000 monthly-end-user restriction; revisit licensing before expanding or monetizing.

Live checks passed for Mark 15:21-41 (21 verses) and Nehemiah 13; Esther 1-2 (76 verses). Full poetry typography and notes remain future improvements.