HealthLog/CONTRIBUTING.md

Contributing to HealthLog

Contributions are welcome. This guide covers how to set up the project and submit changes.

Prerequisites

• Node.js 22+
• pnpm
• PostgreSQL 16+ (or Docker)
• Git

Setup

git clone https://github.com/MBombeck/HealthLog.git
cd HealthLog
cp .env.example .env

Edit .env and configure at minimum:

POSTGRES_PASSWORD=<hex, 32 bytes>
DATABASE_URL="postgresql://healthlog:${POSTGRES_PASSWORD}@db:5432/healthlog"
ENCRYPTION_KEY=<64-char hex>
API_TOKEN_HMAC_KEY=<64-char hex>

Generate the three secrets:

echo "POSTGRES_PASSWORD=$(openssl rand -hex 32)" >> .env
echo "ENCRYPTION_KEY=$(openssl rand -hex 32)"       >> .env
echo "API_TOKEN_HMAC_KEY=$(openssl rand -hex 32)"   >> .env

With Docker (database only)

docker compose up -d db
pnpm install
pnpm db:generate
pnpm db:migrate
pnpm dev

Full Docker

docker compose up -d

Development Workflow

pnpm dev             # Start dev server (http://localhost:3000)
pnpm lint            # ESLint
pnpm format:check    # Prettier (check)
pnpm typecheck       # TypeScript strict mode
pnpm test            # Vitest
pnpm build           # Next.js production build

All five checks must pass before submitting a PR. The full one-liner that mirrors CI:

pnpm typecheck && pnpm lint && pnpm test && pnpm format:check && pnpm build

Code Conventions

• TypeScript strict mode -- avoid any. Where it's truly unavoidable (e.g. variadic Next.js handler signatures in src/lib/api-handler.ts), document the reason inline.
• English-default UI -- the default locale is English. German is user-selectable. Code, comments, commit messages, and docs are English. All user-facing strings go through t("key") with translations in both messages/en.json and messages/de.json. The i18n-locale-integrity.test.ts suite blocks merges if keys drift between locales or duplicate at any nesting depth.
• API responses follow the { data, error } envelope via apiSuccess() / apiError() in src/lib/api-response.ts. Wrap every route handler in apiHandler() (src/lib/api-handler.ts) for error handling, structured Wide-Event logging, and x-request-id propagation.
• Zod v4 (import { ... } from "zod/v4") for input validation in API routes and forms.
• shadcn/ui components (new-york style) for UI primitives.
• Dracula theme -- dark mode is the default; a light/system toggle is exposed in the topbar. Chart and accent colors use the --dracula-* CSS tokens so both themes stay coherent.

See CONTRIBUTING-AI.md for detailed architecture and patterns.

Database Changes

# After modifying prisma/schema.prisma:
pnpm db:migrate     # Creates a new migration
pnpm db:generate    # Regenerates Prisma client

Always include the migration file in your PR.

Branch Model

HealthLog is trunk-based: main is the single long-lived branch and is always releasable. There is no develop branch.

   feature/* ──┐
   fix/*    ──┼──► PR ──► main ──► tag vX.Y.Z ──► GHCR build ──► deploy
              │
   release/vX.Y.Z ──► PR (merge-commit) ──► main ──► tag vX.Y.Z ──► GHCR build ──► deploy

The rules:

• main always builds, passes CI, and is deployable. Every commit on it is a release commit (chore(release): vX.Y.Z), a release-branch merge, or a maintenance commit (docs, gitignore, audit findings) applied directly.
• A release is built on a short-lived release/vX.Y.Z branch cut off main, then opened as a PR release/vX.Y.Z → main with green CI, merged as a merge-commit, and tagged vX.Y.Z. The tag push triggers the GHCR multi-arch image build (and :latest). Deploy is manual. Delete the release branch after merge.
• Small standalone changes (a single fix, a docs touch) go through a short-lived fix/X / feat/X branch + PR targeting main.
• Hotfixes branch from main and merge straight back to main. There is no second long-lived line to forward-port to.
• Never force-push main or any release branch.

End users: track the latest v* tag (or :latest on GHCR). The main branch always equals the latest release.

Contributors: branch off main; PRs target main.

Pull Requests

1. Fork the repository
2. Create a feature branch off main (git checkout -b feat/your-feature main)
3. Make your changes
4. Ensure all checks pass (pnpm typecheck && pnpm lint && pnpm test && pnpm format:check && pnpm build)
5. Submit a PR against main with a clear description of the changes

Translations

HealthLog ships with English (en) and German (de) maintained by the project, plus French (fr), Spanish (es), Italian (it), Polish (pl), Korean (ko), Dutch (nl), and Brazilian Portuguese (pt-BR) that are AI-initial, community-maintained. The maintained locales are reviewed line-by-line; the community-maintained ones surface a small banner inviting users to improve them.

Improving an existing locale

Translation files live at messages/<locale>.json. Each key matches the same key in messages/en.json (which is the source-of-truth — never delete a key here without coordinating).

To suggest a fix or improvement:

1. Fork the repository.
2. Create a branch like i18n-fr/<area> (e.g. i18n-fr/coach-prompts, i18n-pl/dashboard).
3. Edit messages/<locale>.json. Keep the JSON valid; the i18n integrity test will flag missing or extra keys against en.json before CI accepts the PR.
4. Open a PR titled i18n(<locale>): <area>. Describe what was unclear, awkward, or wrong in the previous wording.

Translating in the browser

Every locale can be edited in Fink, inlang's browser editor, without cloning the repository. Fink reads project.inlang/settings.json, which points it at messages/<locale>.json, shows each message next to its translations, and flags strings that are missing or use other placeholders than English.

1. Open the link and sign in with GitHub.
2. Without write access to this repository, choose Fork. Fink asks you to install the Inlang GitHub App on your own account so it can push to your fork.
3. Edit, then choose Push. Fink commits to the fork; Open pull request takes you to GitHub's compare page, where you submit the change against main.

Fink writes the same nested JSON this repository uses and changes only the lines you edited. A string you add for a key the locale did not have yet goes to the end of its section instead of the position it has in en.json, which is harmless.

What a reviewer checks on a translation pull request:

• Only messages/*.json changed, and only the strings the description names.
• Every {placeholder} of the English string is still there and spelled the same. The i18n integrity test fails the build otherwise.
• Medical terms are the ones the language's clinical guidelines use, and the register matches the rest of the locale (du in German, você in Brazilian Portuguese).
• Words the app or the Telegram bot matches literally stay as they are: slash commands, taken <name>, and the unit symbols.
• Machine translation is fine as a first draft, but someone who reads the language has gone through every string before the pull request is opened, and the description says so.
• Validated questionnaire items (the PHQ-9, GAD-7, WHO-5 and SCI items, their answer options and their stems under mentalHealth.items, mentalHealth.options, mentalHealth.gad7Options, mentalHealth.who5Options, mentalHealth.sciOptions, mentalHealth.stems, mentalHealth.functional*) are never translated freely, not even as a draft. A language gets them only from a published, licensed validated version, copied verbatim and named in src/lib/mental-health/instruments.ts; until then the app shows the English original and the bundle carries none of those keys, which the i18n tests enforce.

To run the checks Fink shows on a local checkout: npx @inlang/cli@3.4.4 check --project ./project.inlang. It reads the files and changes nothing.

Adding a new locale

If you want to introduce a locale that isn't shipped (e.g. sv, cs):

1. Open an issue first using the Translation request template. We'll confirm the locale is in scope and decide whether it joins the AI-initial-community-maintained tier or the maintained tier.
2. Copy messages/en.json to messages/<locale>.json, then delete the questionnaire wording the new language has no validated version of (the test output lists the keys).
3. Translate. AI assistance is welcome as a starting point but the PR description should note whether it's an AI-initial pass or a fully human-reviewed one — that information drives the banner state.
4. Add the locale to locales in src/lib/i18n/config.ts and to locales in project.inlang/settings.json, then run pnpm typecheck. Every per-locale table that still lacks the new locale fails to compile, and that list is the work: date and number formatting, the reply-language footers of the Coach and insights prompts, the outbound safety banks, the prose-grounding patterns and the no-key fallback copy. Include those in the same PR.
5. Run pnpm test before submitting. The i18n guards hold the new bundle to the English keys and placeholders.

Style guide for translators

• Tone: warm but reserved, curious not pushy. Examples in EN: "Your blood pressure has settled into the green zone" — not "Awesome, your BP is amazing!"
• Numbers and units stay numeric: "120/80 mmHg" stays "120/80 mmHg" in every locale.
• Brand terms stay untranslated: HealthLog, Coach, Tagesbriefing (the DE Coach term — leave as-is in EN if it appears).
• Medical terms: prefer the language community's native medical vocabulary (e.g. "Blutdruck" in DE, "tensión arterial" in ES, "ciśnienie krwi" in PL). When in doubt, mirror the style used in the country's clinical guidelines.
• Avoid US-specific units (lb, oz, °F) — HealthLog is metric-first.
• No PII in copy. No real names, no real readings. Sample data uses round numbers.

Long-term

Fink covers browser editing today. It edits the files in this repository directly and keeps no copy of the translations anywhere else. If the community outgrows it, a self-hosted Weblate instance remains the fallback. Tracking issue: v1.6 — Weblate self-hosted on edge-01.

Code of Conduct

This project follows the Contributor Covenant 2.1. By participating, you agree to uphold its standards. Reports of unacceptable behavior go to conduct@bombeck.io.

Security

If you find a security vulnerability, do not open a public issue. See SECURITY.md for responsible disclosure instructions.

License

The project is licensed under the PolyForm Noncommercial License 1.0.0. By contributing, you agree that your contributions are submitted under the project license.