<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Arnaud Prioul (Mome)</title>
    <description>The latest articles on DEV Community by Arnaud Prioul (Mome) (@m0me_).</description>
    <link>https://dev.to/m0me_</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1490142%2F13fac81a-82a5-40c4-a9a3-e429b66932df.jpg</url>
      <title>DEV Community: Arnaud Prioul (Mome)</title>
      <link>https://dev.to/m0me_</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/m0me_"/>
    <language>en</language>
    <item>
      <title>Vue i18n dahsboard</title>
      <dc:creator>Arnaud Prioul (Mome)</dc:creator>
      <pubDate>Sat, 21 Mar 2026 02:09:18 +0000</pubDate>
      <link>https://dev.to/m0me_/vue-i18n-dahsboard-l6l</link>
      <guid>https://dev.to/m0me_/vue-i18n-dahsboard-l6l</guid>
      <description>&lt;h1&gt;
  
  
  I built a Vue i18n dashboard to stop editing JSON files
&lt;/h1&gt;

&lt;p&gt;Working with vue-i18n has always been a bit frustrating.&lt;/p&gt;

&lt;p&gt;Every time I needed to update a translation, I had to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;open JSON files&lt;/li&gt;
&lt;li&gt;search for keys&lt;/li&gt;
&lt;li&gt;reload the app to see changes&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It breaks the development flow.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem
&lt;/h2&gt;

&lt;p&gt;Managing translations becomes even harder when:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;you have multiple languages&lt;/li&gt;
&lt;li&gt;multiple projects&lt;/li&gt;
&lt;li&gt;or a team working on translations&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Most existing solutions require migrating to a proprietary system or using a SaaS.&lt;/p&gt;

&lt;h2&gt;
  
  
  The idea
&lt;/h2&gt;

&lt;p&gt;I wanted something simple:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;works with vue-i18n&lt;/li&gt;
&lt;li&gt;no migration&lt;/li&gt;
&lt;li&gt;usable locally&lt;/li&gt;
&lt;li&gt;but scalable if needed&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The solution
&lt;/h2&gt;

&lt;p&gt;So I built a dashboard that allows you to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;edit translations live&lt;/li&gt;
&lt;li&gt;automatically detect keys from your code&lt;/li&gt;
&lt;li&gt;manage multiple projects&lt;/li&gt;
&lt;li&gt;use an API instead of JSON files if needed&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Two ways to use it
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Local mode
&lt;/h3&gt;

&lt;p&gt;Run it inside your project:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;edit translations&lt;/li&gt;
&lt;li&gt;export JSON files&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Server mode
&lt;/h3&gt;

&lt;p&gt;Run it as a platform:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;manage multiple projects&lt;/li&gt;
&lt;li&gt;sync with Git&lt;/li&gt;
&lt;li&gt;serve translations via API&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why it’s different
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;No vendor lock-in&lt;/li&gt;
&lt;li&gt;Works with existing vue-i18n setup&lt;/li&gt;
&lt;li&gt;Fully self-hosted&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Looking for feedback
&lt;/h2&gt;

&lt;p&gt;This is still an early version, and I’d love feedback from developers.&lt;/p&gt;

&lt;p&gt;👉 GitHub: &lt;a href="https://github.com/arnaudprioul/i18n-dashboard" rel="noopener noreferrer"&gt;https://github.com/arnaudprioul/i18n-dashboard&lt;/a&gt;&lt;/p&gt;

</description>
      <category>vue</category>
      <category>i18n</category>
    </item>
  </channel>
</rss>
