How do I use DevOps-style i18n
Doloc is an API-first localization tool designed to integrate seamlessly into existing development workflows. It allows developers to manage translations without the need for complex platforms or heavy onboarding processes. By keeping localization files within the repository, doloc ensures that translations can be reviewed and managed like code changes.
- ▪Doloc translates localization files using context-aware AI and returns them in the same structure and format.
- ▪The tool supports common localization formats such as XLIFF, JSON, and Android XML resources.
- ▪Doloc can be integrated into CI/CD pipelines, allowing translations to stay updated as applications evolve.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/marrouchi/how-do-i-use-devops-style-i18n-5edm |
| Publication time | Tue, 19 May 2026 08:20:54 +0000 |
| Retrieval time | 2026-05-19T08:34:57.460Z |
| Last seen | 2026-05-19T08:34:57.460Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | ENvl8xoUzgN6 |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 945989) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Med Marrouchi Posted on May 19 How do I use DevOps-style i18n #webdev #javascript #productivity #development Localization is one of those things every serious product eventually needs, but many teams still treat it as a separate, heavy process. You extract strings from your app, send them somewhere, wait for translations, copy files back, fix formatting issues, review inconsistencies, and repeat the same process every time the product changes.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
