Welcome to GospeLib
GospeLib is a scripture study platform powered by a knowledge graph. It combines LDS canonical texts (Bible, Book of Mormon, Doctrine & Covenants, Pearl of Great Price) with deep original-language scholarship — interlinear Hebrew & Greek, manuscript witnesses, pseudepigraphical texts, and an AI study assistant — all woven together in a navigable knowledge graph.
What You Can Build Here
The platform is a polyglot microservices monorepo:
- 3 frontend apps — Next.js web app, Next.js admin dashboard, Expo mobile app
- 8 backend services — Go and Python microservices covering API gateway, content queries, auth, billing, AI features, notifications, plugin registry, and data ingestion
- 9 shared packages — TypeScript libraries for core, types, UI components, SDK, config, schemas, scripture-ref, plugin-sdk, and testing
- 4 data stores — FalkorDB (graph), PostgreSQL (relational), Redis (cache), Typesense (search)
Everything is orchestrated with Nx + pnpm workspaces, with Go modules and Python's uv managing their respective ecosystems.
How to Use These Docs
Follow these pages in order to go from zero to a working dev environment and your first merged PR:
| Step | Page | What You'll Do |
|---|---|---|
| 1 | Prerequisites | Install required tools |
| 2 | Local Dev Setup | Clone, install dependencies, start services |
| 3 | Repository Tour | Understand what lives where |
| 4 | Your First PR | Branch, commit, and open a pull request |
| 5 | Port Map & Services | Quick reference for all services and ports |
Already comfortable with the basics? Jump directly to the Architecture section for system design details, or Guides for task-oriented how-to pages.
Architecture at a Glance
The architecture thesis: buildable by one person on day one, never requiring a rewrite to reach enterprise scale. Services are logically separated with their own API contracts from the start. In Phase 1, they can share a process; in Phase 2+, they split into separate containers — without changing any public interface.
All external API traffic enters through the Gateway (port 8080), which handles JWT validation, rate limiting, and reverse-proxies to downstream services. No service is exposed directly to the internet.
Next Step
Head to Prerequisites to install the tools you'll need.