Merge pull request #28 from mapachurro/refactor-loc

Refactor backend re: locale file structure, make term names on explore feature human readable

Author: mapachurro

README.md

@@ -115,7 +115,7 @@ If there doesn't seem to be an appropriate locale for the user, the root index f
 *Note: the above functionality probably has a bad impact on SEO, and we should consider disabling it.*
 
 These homepages are created by `build-homepages.js`, which runs during the build process.
-This script ingests `index-template.html`, and applies UI translation strings found in `./l10n/<four-letter-dash-locale-code>/translation.json` to the elements that need to contain human-readable information.
+This script ingests `index-template.html`, and applies UI translation strings found in `./locales<four-letter-dash-locale-code>/translation.json` to the elements that need to contain human-readable information.
 
 ### The Navbar and language switching
 
@@ -261,7 +261,7 @@ There is a cross-locale mapping function present in this script, which should li
 
 wordsofweb3 should always prioritize human-readability over concessions to the conventions of machines, even when that sucks for technical reasons.
 
-An example of this: we do not have paths like `/es-419/cuenta.html`; no, we have `/nederlands/ethereum.html`. This does mean that, at times, we have to leverage functions available in the `l10n.js` script to convert between different formats of language codes. This script leverages a .json file which contains several different formats, at `./l10n/language-codes.json`:
+An example of this: we do not have paths like `/es-419/cuenta.html`; no, we have `/nederlands/ethereum.html`. This does mean that, at times, we have to leverage functions available in the `l10n.js` script to convert between different formats of language codes. This script leverages a .json file which contains several different formats, at `./public/assets/language-codes.json`:
 
 ```json
 {