GitLocalizeGitLocalize
Editor
Get a token
Deploy
Architecture
Setup
Security
Repository
Editor
Get a token
Deploy
Architecture
Setup
Security
Repository

GitLocalize

A translation platform with no server, no database and no backend. GitHub is the backend.

Open the editorHow it works

Git is the database

Translations live in the repository. The translation workspace is the i18n branch, reviewed through pull requests.

GitHub API is the application API

The browser talks to api.github.com directly. Your token never leaves the tab.

Actions are the workers

Sync, pull request automation and Pages deployment run as GitHub Actions workflows.

What this is

GitLocalize turns a GitHub repository into a translation platform. Translators open a static site hosted on GitHub Pages, edit translations in a focused single-string editor, and commit the result to the i18n branch. Automation then opens a pull request against main for review.

Nothing is deployed except a static site. There is no VPS, no Express server, no database, no OAuth broker.

The loop

Translator → editor on GitHub Pages → commit to i18n
          → GitHub Actions → pull request i18n → main
          → maintainer review → merge main
          → sync main → i18n → Pages rebuild

Try it without a token

The editor ships with an in-memory GitHub stand-in so the interface can be exercised offline: open /Editor/?mock=1 and sign in with any token.

MIT Licensed