Simple Mode
Git in plain language — with the real terms always in view
Simple Mode never hides Git. Every action shows its plain-language label prominently, the real Git term beneath it, and a one-line explanation. Your team learns the vocabulary while getting work done.
The terminology map
This is the exact mapping the product uses — rendered from the same configuration file that drives the interface.
| Plain language | Git term | What it means |
|---|---|---|
| Save changes | Commit | A commit is a saved snapshot of your project at a point in time. You can always come back to it. |
| Create a separate version | Branch | A branch is a parallel copy of the project where you can work without affecting the main version. |
| Request a review | Pull request | A pull request asks teammates to review your changes before they join the main version. |
| Combine versions | Merge | Merging brings the changes from one version into another. |
| Download project | Clone | Cloning downloads a full copy of the project to your computer, still connected to the shared one. |
| Project history | Commit history | Every saved change, who made it, and when — nothing is ever lost. |
| Upload your changes | Push | Pushing sends the changes saved on your computer up to the shared project. |
| What changed | Diff | A side-by-side comparison showing exactly which lines were added or removed. |
| Undo to an earlier point | Revert | Creates a new saved change that restores the project to how it was before. |
| Project | Repository | A repository holds your project's files and their entire history. |
| Overlapping edits | Merge conflict | Two versions changed the same lines. Someone needs to choose which edits to keep — we'll walk you through it. |
11 terms, rendered directly from the shared terminology configuration.
How it behaves in practice
Progressive learning
Every plain-language label carries the real Git term and a tooltip explanation. People absorb the vocabulary from doing the work — no course, no rebase etiquette lecture.
One-click rollback
“Undo to an earlier point” creates a new saved change (a revert) that restores the project — history is never rewritten and nothing is ever lost.
Plain-language merge conflicts
A conflict is presented as “overlapping edits”: two versions changed the same lines, and the interface walks you through choosing which edits to keep.
Developer Mode is always one toggle away
Interface mode is a per-user preference, not a workspace setting. Your developer sees a conventional Git host; your cofounder sees plain language. Both operate on the same repositories through the same server-side rules — branch protection, permissions, and history are identical in both modes.