<div style="display: flex; flex-wrap: wrap; white-space: pre-wrap; align-items: center; "><img height="20" width="20" style="border-radius:50%; margin-right: 4px;" decoding="async" src="https://avatars.githubusercontent.com/u/360803?s=20&v=4" /><strong>gravitystorm</strong> created an issue <a href="https://github.com/openstreetmap/openstreetmap-website/issues/6550">(openstreetmap/openstreetmap-website#6550)</a></div>
<p dir="auto">As part of our <a href="https://github.com/openstreetmap/openstreetmap-website/blob/74a41d95fa146523bd856cd63452e1ed3c462696/config/i18n.yml">i18n-js configuration</a>, we currently create a top-level <code class="notranslate">i18n</code> directory. It's used to hold <a href="https://github.com/openstreetmap/openstreetmap-website/tree/74a41d95fa146523bd856cd63452e1ed3c462696/i18n/templates">a single template file under source control</a>, and a number of intermediate <code class="notranslate">.json</code> files created while generating the corresonding <code class="notranslate">.js</code> files in <code class="notranslate">app/assets/javascripts/i18n/</code></p>
<p dir="auto">From a developer experience point of view, it would be great to move these elsewhere, because:</p>
<ul dir="auto">
<li>we've already got a lot of top-level directories, that e.g. push our readme far down the page</li>
<li>these files aren't important enough to warrant a top-level directory of their own</li>
<li>more importantly, it can mislead developers to think that this is where to look for translation-related matters, when the vast majority of the time they should look elsewhere e.g. <code class="notranslate">config/locales/</code>.</li>
</ul>
<p dir="auto">As far as I can tell we get free choice over the directory used, but I haven't tested to see if i18n-js has any built-in reasons to prefer that specific directory.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />Reply to this email directly, <a href="https://github.com/openstreetmap/openstreetmap-website/issues/6550">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAK2OLPU2XXBYBNNODKXLST35XURTAVCNFSM6AAAAACMW3J23WVHI2DSMVQWIX3LMV43ASLTON2WKOZTGY2DQMBXHEYTKNA">unsubscribe</a>.<br />You are receiving this because you are subscribed to this thread.<img src="https://github.com/notifications/beacon/AAK2OLOGLMSHZNNSM4YXDCD35XURTA5CNFSM6AAAAACMW3J23WWGG33NNVSW45C7OR4XAZNFJFZXG5LFVJRW63LNMVXHIX3JMTHNS4KFGI.gif" height="1" width="1" alt="" /><span style="color: transparent; font-size: 0; display: none; visibility: hidden; overflow: hidden; opacity: 0; width: 0; height: 0; max-width: 0; max-height: 0; mso-hide: all">Message ID: <span><openstreetmap/openstreetmap-website/issues/6550</span><span>@</span><span>github</span><span>.</span><span>com></span></span></p>

<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/openstreetmap/openstreetmap-website/issues/6550",
"url": "https://github.com/openstreetmap/openstreetmap-website/issues/6550",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>