The latest articles on DEV Community by solsol platform digital (@weerawat_poseeya_aed34138). https://dev.to/weerawat_poseeya_aed34138 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4082458%2F5a93ec62-3eff-434f-b3c9-6d501e793b41.png https://dev.to/weerawat_poseeya_aed34138 en solsol platform digital Tue, 18 Aug 2026 10:59:36 +0000 https://dev.to/weerawat_poseeya_aed34138/stop-fixing-translation-tickets-how-in-context-i18n-saves-web-developers-hours-1pig https://dev.to/weerawat_poseeya_aed34138/stop-fixing-translation-tickets-how-in-context-i18n-saves-web-developers-hours-1pig <p>Every web developer knows the routine: you build a multilingual website for a client, ship it, and within 48 hours your inbox is flooded with tickets:</p> <ul> <li>"Can you fix this typo on the homepage in French?"</li> <li>"The German text broke the navbar layout."</li> <li>"Here is an updated CSV of 200 strings, please re-upload."</li> </ul> <h2> Why Traditional i18n Sucks for Client Work </h2> <ol> <li> <strong>Context loss</strong> — Translators look at spreadsheet rows without seeing where the text actually goes.</li> <li> <strong>Layout shifts</strong> — Translators don't know German runs ~40% longer until you deploy.</li> <li> <strong>Dev bottleneck</strong> — Every minor typo requires a git commit and a full CI/CD run.</li> </ol> <h2> The Solution: In-Context Localization </h2> <p><a href="https://verba.solsol.app/" rel="noopener noreferrer">Verba</a> introduces a simple developer-to-client loop:</p> <ul> <li>Developers keep standard keys in components: </li> </ul> <div class="highlight js-code-highlight"> <pre class="highlight jsx"><code><span class="p">&lt;</span><span class="nt">h1</span><span class="p">&gt;</span><span class="si">{</span><span class="nf">t</span><span class="p">(</span><span class="dl">'</span><span class="s1">home.hero.title</span><span class="dl">'</span><span class="p">)</span><span class="si">}</span><span class="p">&lt;/</span><span class="nt">h1</span><span class="p">&gt;</span> </code></pre> </div> <ul> <li>Clients and translators install a Chrome extension, open the live website, hover, and edit copy right on the rendered page.</li> <li>Hit <strong>Save</strong> → live instantly, no developer deployment required.</li> </ul> <p>The result: translators see layout and context while they work, and you stop being the bottleneck for every typo fix.</p> <p>Check out the free tier at <a href="https://verba.solsol.app/" rel="noopener noreferrer">verba.solsol.app</a> and let me know your thoughts!</p> webdev javascript react nextjs