A private tool for LDS bishopric coordination — sacrament meeting planning, calling pipeline, interview tracking, missionary pipeline, member needs, and more.

Built with React 19 + TypeScript + Tailwind CSS v4, deployed on Cloudflare Pages with Cloudflare D1 (SQLite) as the database.

• Sacrament Meeting Planning — speakers, music, prayers, themes, announcements; past/current/future split view
• Current Sacrament Agenda — live drag-and-drop agenda builder with printable view; past meetings show frozen snapshots
• Calling Pipeline — track callings and releases through each step with assigned-to bishopric member
• Interview Pipeline — recommend expiry dates, interview scheduling, and status tracking
• Missionary Pipeline — pre-mission through return, linked to farewell/homecoming sacrament talks
• Member Needs — confidential pastoral notes
• Bishop Schedule — weekly calendar with drag-to-resize appointments
• Important Links — shared team link library
• Users & Roles — app roles (admin/editor) and church roles (bishop, counselors, clerk, etc.)

• Node.js 18+
• Cloudflare account (free tier is sufficient)
• Wrangler CLI: npm install -g wrangler
• GitHub CLI (optional, for Claude-assisted setup)

git clone https://github.com/YOUR_USERNAME/bishopric-hub.git
cd bishopric-hub
npm install

wrangler login
wrangler d1 create bishopric-hub-db

Copy the database_id from the output.

cp wrangler.jsonc.example wrangler.jsonc

Edit wrangler.jsonc and fill in your database_name and database_id.

Apply all migration files in order:

for f in migrations/*.sql; do
  npx wrangler d1 execute bishopric-hub-db --remote --file="$f"
done

Or run them one at a time:

npx wrangler d1 execute bishopric-hub-db --remote --file=migrations/0001_schema.sql
npx wrangler d1 execute bishopric-hub-db --remote --file=migrations/0002_sessions.sql
# ... continue through all migration files in order

Use the Wrangler CLI to insert an admin user. Generate a SHA-256 hash of your chosen password first:

node -e "const c=require('crypto');console.log(c.createHash('sha256').update('yourpassword').digest('hex'))"

Then insert the user:

npx wrangler d1 execute bishopric-hub-db --remote --command="INSERT INTO users (name, email, password_hash, role) VALUES ('Your Name', 'your@email.com', 'PASTE_HASH_HERE', 'admin');"

For GitHub Actions deployment (see Deployment), the D1 binding must be set in the Cloudflare dashboard:

1. Go to Cloudflare Dashboard → Workers & Pages → bishopric-hub → Settings → Bindings
2. Add a D1 Database binding: Variable name DB, Database = your database name

npm run build
npx wrangler pages deploy dist --branch main

Cloudflare will print a deployment URL. After this first manual deploy, push to master on GitHub to trigger automatic deployments (once you complete the GitHub Actions setup in Deployment).

Start the Vite dev server:

npm run dev

For full API support locally (Cloudflare Worker runtime + D1), run in a separate terminal after building:

npm run build
npx wrangler pages dev dist --d1 DB=YOUR_DATABASE_NAME

Replace YOUR_DATABASE_NAME with the database_name value from your wrangler.jsonc.

Every push to master automatically builds and deploys via .github/workflows/deploy.yml. One-time setup:

1. Create a Cloudflare API token

   • Go to Cloudflare Dashboard → My Profile → API Tokens → Create Token
   • Use the Edit Cloudflare Workers template, or create a custom token with Cloudflare Pages: Edit permission
   • Copy the token value

2. Find your Cloudflare Account ID

   • Any Cloudflare dashboard page → right sidebar shows Account ID

3. Add secrets to GitHub

   • Go to your repo → Settings → Secrets and variables → Actions → New repository secret
   • Add CLOUDFLARE_API_TOKEN (the token from step 1)
   • Add CLOUDFLARE_ACCOUNT_ID (from step 2)

After that, every git push deploys automatically. No local build step needed.

npm run build
npx wrangler pages deploy dist --branch main

This project was built and is maintained with Claude Code. To continue development with AI assistance:

1. Install Claude Code: download the desktop app from claude.ai/code or install the VS Code extension
2. Open the project directory in Claude Code
3. Claude has full context of the architecture and can add features, fix bugs, run migrations, build, and deploy

Example prompts that work well with Claude Code:

• "Add a new page for tracking [X]"
• "Run the migration and deploy"
• "Scan for defects"
• "Make sure the code has no personal information before I push to GitHub"
• "Split the sacrament planning view into past, current, and future sections"

Claude can read and edit source files, run migrations against your remote D1 database, build the project, and deploy — all in one conversation without switching terminals.

Migrations live in migrations/ and are numbered sequentially (0001_schema.sql, 0002_sessions.sql, …). Run them in order. There is no auto-migration runner — apply each file explicitly:

npx wrangler d1 execute bishopric-hub-db --remote --file=migrations/XXXX_name.sql

Schema migrations (*_schema.sql, *_add_*.sql, etc.) define tables and columns and are committed to the repo.

Data import migrations (files ending in _import.sql or _seed.sql) contain ward-specific data — member names, events, callings — and are gitignored. These are generated locally (or by Claude) when importing from external sources and are not shared. Run them against your own database but do not commit them.

• All personal data (member names, callings, notes) lives only in the database — nothing is hardcoded in source code
• Cloudflare D1 encrypts data at rest and in transit (TLS) by default
• Sessions use HTTP-only cookies with a 30-day expiry
• wrangler.jsonc is gitignored — it contains your database ID and must not be committed
• Data import/seed migrations (*_import.sql, *_seed.sql) are gitignored — they may contain member names and ward-specific event details
• The scripts/ directory is gitignored for the same reason
• .env and .env.* files are gitignored — never commit API keys or secrets
• Data exports (*.csv, exports/, data-export/) are gitignored — CSV/JSON dumps may contain member data
• Ward-specific image assets should not be committed to a public repo

bishopric-hub/
├── functions/
│   └── api/
│       └── [[route]].ts      # Cloudflare Pages Function — all API routes in one file
├── migrations/               # D1 SQL migrations, applied in numeric order
├── src/
│   ├── components/           # Layout, Modal, FormFields, StatusBadge, etc.
│   ├── lib/                  # api.ts (types + fetch), auth.tsx, useTable.ts, constants.ts
│   └── pages/                # One file per feature page
├── wrangler.jsonc.example    # Copy to wrangler.jsonc and fill in your D1 details
└── vite.config.ts

MIT — free to use, modify, and deploy for your own ward or unit.