https://kaivalya.eu/projects/trainUs/en/developers/Recent content in Developers on TrainUsHugo -- gohugo.ioenTue, 16 Jun 2026 00:00:00 +0000https://kaivalya.eu/projects/trainUs/en/developers/getting-started/Tue, 16 Jun 2026 00:00:00 +0000https://kaivalya.eu/projects/trainUs/en/developers/getting-started/What You’ll Need Node.js ≥ 18 Python ≥ 3.10 (only needed to run the test suite) A modern browser — Firefox 111+, Chrome 102+, or Safari 16.4+. TrainUs relies on OPFS (Origin Private File System) for its database, which doesn’t exist in older browsers or in private/incognito windows. Clone and Install git clone <repo-url> cd trainUs npm install Run the App npm run dev This starts the Vite dev server at http://localhost:5173.https://kaivalya.eu/projects/trainUs/en/developers/how-to-guides/Tue, 16 Jun 2026 00:00:00 +0000https://kaivalya.eu/projects/trainUs/en/developers/how-to-guides/Add a New Language TrainUs already ships three languages today — English, French, and Danish (da) — not just the EN/FR pair the project website emphasizes. The steps below walk through adding one more, using Spanish (es) as the worked example. Adding a language requires four touch points: a new locale file, wiring it into the i18n initializer, a selector option in Settings, and a decision-log entry. src/i18n/locales/<code>.json — create the translation file src/i18n/index.https://kaivalya.eu/projects/trainUs/en/developers/technical/Tue, 16 Jun 2026 00:00:00 +0000https://kaivalya.eu/projects/trainUs/en/developers/technical/This page describes every part of TrainUs in detail: tech stack, schema, routes, composables. For a guided first run, see Getting Started; for concrete tasks, see How-to Guides; for the “why” behind the choices, see Understanding the Architecture. AI authorship. The vast majority of the source code in this project was written by AI assistants (primarily Claude). The human author directed the architecture, reviewed every change, guided the implementation, and made all design and product decisions — but in terms of who typed the lines, that credit belongs mostly to the AI.https://kaivalya.eu/projects/trainUs/en/developers/understanding-the-architecture/Tue, 16 Jun 2026 00:00:00 +0000https://kaivalya.eu/projects/trainUs/en/developers/understanding-the-architecture/This page explains why TrainUs is built the way it is. For the facts — schema, routes, exact fields — see Reference. Why No Backend? Many fitness apps run on an account and a central server. TrainUs makes the opposite choice: it’s a Progressive Web Application that runs entirely in the browser, with all data stored locally via SQLite WASM and OPFS. There’s no server to operate, no account system to build and secure, and the app keeps working — fully — with no network connection at all.