bibleit/Documentation

BIBLEIT / Documentation

Build your first Live.

Read Scripture, prepare a presentation, and share it with every screen in the room. Start in your browser, then explore the protocol.

Get started →Bibleit Shell ↗

Get started

A verse on screen in four steps

01

Create your account

Sign in with Google, GitHub, or email. Choose your username to finish onboarding. Every new personal account starts on Starter.

Create an account →
02

Enable a translation

Open Translations in your dashboard, choose an available edition, and add it to your library. It must be enabled before you can read, search, or present it.

Translations →
03

Find your passage

Open Reader. Select your translation, book, chapter, and verse. Use a second translation to compare the same passage.

Reader →
04

Create, present, and share

Create a named Live from your dashboard. Select an enabled translation in its controller, find the passage, and present it. Open the viewer link in a second tab to confirm the verse is visible, then share that link with your audience.

Open dashboard →

Choose your next step

1Build your first Live.Read Scripture, prepare a presentation, and share it with every screen in the room. Start in your browser, then explore the protocol.2GuidesPractical workflows for your library, presentations, and team. Each guide starts with what you need and ends with what you should see.3Protocol referenceThe version 1 command protocol is shared by SSH and the HTTP command endpoint. Keywords are case-insensitive. Quote arguments containing spaces. Start with HELP to discover commands allowed for your identity.4HTTP & WebSocketSend one command per HTTP request. Use SSH for long-lived protocol subscriptions and WebSockets for browser Live events.5CLI · coming soonThe CLI is in development. Installation, flags, output formats, and exit codes will be documented against the first published release. Use the dashboard, SSH, or HTTP today.6DevelopersRun and contribute to the Erlang/OTP service. Start with the development guide; keep runtime contracts in the reference and operational procedures in their own documents.7TroubleshootingStart with the exact response, then check the account, translation, or Live state involved. Include the command and error when asking for help; remove credentials.8Bibleit ShellExplore protocol responses without installing anything. Example mode uses fixed fixtures; account mode runs read-only commands as your signed-in account.