You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Lingo.dev automates software localization end-to-end using latest LLM models.
34
+
Lingo.dev is a community-driven, open-source CLI for AI-powered web and mobile app localization.
34
35
35
-
It produces authentic translations instantly, eliminating manual work and management overhead. Lingo.dev Localization Engine understands product context, creating perfected translations that native speakers expect across 60+ languages. As a result, teams do localization 100x faster, with state-of-the-art quality, shipping features to more paying customers worldwide.
36
+
Lingo.dev is designed to produce authentic translations instantly, eliminating manual work and management overhead. As a result, teams do accurate localization 100x faster, shipping features to more happy users worldwide. It can be used with your own LLM or with Lingo.dev-managed Localization Engine.
37
+
38
+
> **Little-known fact:** Lingo.dev began as a small project at a student hackathon back in 2023! Many iterations later, we got accepted into Y Combinator in 2024, and we're now hiring! Interested in building the next-gen localization tools? Send your CV to careers@lingo.dev 🚀
39
+
40
+
## 📑 In This Guide
41
+
42
+
-[Quickstart](#-quickstart) - Get started in minutes
-[GitHub Action](#-github-action) - Automate localization in CI/CD
45
+
-[Features](#-supercharged-features) - What makes Lingo.dev powerful
46
+
-[Documentation](#-documentation) - Detailed guides and references
47
+
-[Contribute](#-contribute) - Join our community
36
48
37
49
## 💫 Quickstart
38
50
39
-
1. Create an account on [the website](https://lingo.dev)
51
+
Lingo.dev CLI is designed to work with both your own LLM, and Lingo.dev-managed Localization Engine built on top of latest SOTA (state-of-the-art) LLMs.
52
+
53
+
### Using Your Own LLM (BYOK or Bring Your Own Key)
54
+
55
+
1. Create an `i18n.json` configuration file:
56
+
57
+
```json
58
+
{
59
+
"version": 1.5,
60
+
"provider": {
61
+
"id": "anthropic",
62
+
"model": "claude-3-7-sonnet-latest",
63
+
"prompt": "You're translating text from {source} to {target}."
64
+
},
65
+
"locale": {
66
+
"source": "en",
67
+
"targets": ["es", "fr", "de"]
68
+
}
69
+
}
70
+
```
71
+
72
+
2. Set your API key as an environment variable:
73
+
74
+
```bash
75
+
export ANTHROPIC_API_KEY=your_anthropic_api_key
76
+
# or for OpenAI
77
+
export OPENAI_API_KEY=your_openai_api_key
78
+
```
40
79
41
-
2. Initialize your project:
80
+
3. Run the localization:
42
81
43
-
```bash
44
-
npx lingo.dev@latest init
45
-
```
82
+
```bash
83
+
npx lingo.dev@latest i18n
84
+
```
46
85
47
-
3. Check out our docs: [docs.lingo.dev](https://docs.lingo.dev)
86
+
### Using Lingo.dev Cloud
87
+
88
+
Oftentimes, production-grade apps require features like translation memory, glossary support, and localization quality assurance. Also, sometimes, you want an expert to decide for you which LLM provider and model to use, and to update the model automatically when new ones are released. Lingo.dev is a managed Localization Engine that provides these features:
89
+
90
+
1. Create an `i18n.json` configuration file (without provider node):
91
+
92
+
```json
93
+
{
94
+
"version": 1.5,
95
+
"locale": {
96
+
"source": "en",
97
+
"targets": ["es", "fr", "de"]
98
+
}
99
+
}
100
+
```
101
+
102
+
2. Authenticate with Lingo.dev:
103
+
104
+
```bash
105
+
npx lingo.dev@latest auth --login
106
+
```
48
107
49
-
4. Localize your app (takes seconds):
50
-
```bash
51
-
npx lingo.dev@latest i18n
52
-
```
108
+
3. Run localization:
109
+
110
+
```bash
111
+
npx lingo.dev@latest i18n
112
+
```
113
+
114
+
## 📖 Documentation
115
+
116
+
For detailed guides and API references, visit the [documentation](https://lingo.dev/go/docs).
117
+
118
+
## 🔒 Caching with `i18n.lock`
119
+
120
+
Lingo.dev uses an `i18n.lock` file to track content checksums, ensuring only changed text gets translated. This improves:
- 🧠 **AI Localization Engine**: Translations that truly fit your product
74
-
- 📊 **Format Flexible**: Supports JSON, YAML, CSV, Markdown, and more
140
+
## ⚡️ Lingo.dev's Superpowers
75
141
76
-
## 🛠️ Supercharged features
142
+
## ⚡️ Lingo.dev's Superpowers
77
143
78
-
- ⚡️ **Lightning-Fast**: AI localization in seconds
79
-
- 🔄 **Auto-Updates**: Syncs with the latest content
80
-
- 🌟 **Native Quality**: Translations that sound authentic
81
-
- 👨💻 **Developer-Friendly**: CLI that integrates with your workflow
82
-
- 📈 **Scalable**: For growing startups and enterprise teams
83
-
84
-
## 📚 Documentation
85
-
86
-
For detailed guides and API references, visit the [documentation](https://lingo.dev/go/docs).
144
+
- 🔥 **Instant integration**: Works with your codebase in minutes
145
+
- 🔄 **CI/CD Automation**: Set it and forget it
146
+
- 🌍 **Global reach**: Ship to users everywhere
147
+
- 🧠 **AI-powered**: Uses latest language models for natural translations
148
+
- 📊 **Format-agnostic**: JSON, YAML, CSV, Markdown, Android, iOS, and many more
149
+
- 🔍 **Clean diffs**: Preserves your file structure exactly
150
+
- ⚡️ **Lightning-fast**: Translations in seconds, not days
151
+
- 🔄 **Always synced**: Automatically updates when content changes
152
+
- 🌟 **Human quality**: Translations that don't sound robotic
153
+
- 👨💻 **Built by devs, for devs**: We use it ourselves daily
154
+
- 📈 **Grows with you**: From side project to enterprise scale
87
155
88
156
## 🤝 Contribute
89
157
90
-
Interested in contributing, even if you aren't a customer?
91
-
92
-
Check out the [Good First Issues](https://github.com/lingodotdev/lingo.dev/labels/good%20first%20issue) and read the [Contributing Guide](./CONTRIBUTING.md).
93
-
94
-
## 👨💻 Team
158
+
Lingo.dev is community-driven, so we welcome all contributions!
95
159
96
-
- **[Veronica](https://github.com/vrcprl)**
97
-
- **[Max](https://github.com/maxprilutskiy)**
98
-
- **[Matej](https://github.com/mathio)**
160
+
Have an idea for a new feature? Create a GitHub issue!
0 commit comments