Single or multiple translation.json files for i18n?
<p>I'm working a project in Aurelia and using the aurelia-i18n plugin.  So far it looks great and translation is working and instantly updating interface language when I change locale.</p>

<p>Question: is there a logical, organizational or performance advantage to using multiple translation files vs. a single translation file?  For instance:</p>

<p>Should I just put everything into one file?</p>

<pre><code>my-aurelia/locales/en/translation.json
my-aurelia/locales/es/translation.json
</code></pre>

<p>Or should I separate into multiple translation files?</p>

<pre><code>my-aurelia/locales/en/nav.json
my-aurelia/locales/en/words.json
my-aurelia/locales/en/phrases.json

my-aurelia/locales/es/nav.json
my-aurelia/locales/es/words.json
my-aurelia/locales/es/phrases.json
</code></pre>

<p>Here's how I have instantiated the plugin for this example (inside the <code>export function configure(aurelia) {</code> of  <strong>my-aurelia/src/main.js</strong>, but I'm at an important design crossroads.</p>

<pre><code>aurelia.use.plugin('aurelia-i18n', (instance) =&gt; {
    // register backend plugin
    instance.i18next.use(XHR);

    // adapt options to your needs (see http://i18next.com/docs/options/)
    instance.setup({
      backend: {                                  
        loadPath: '/locales/{{lng}}/{{ns}}.json',
      },
      lng : 'es',
      ns: ['words','phrases','nav'],
      defaultNS: 'words',
      attributes : ['t','i18n'],
      fallbackLng : 'en',
      debug : false
    });
  });
</code></pre>

<p>One json language file or multiple json language files?  Any additional advice?</p>