Thank you for taking interest in bringing
these articles to a wider audience.
Within the articles folder you'll find the English
writings, while translated articles are found in the
translations subdirectory.
To start localizing, please visit our Crowdin page,
choose a language + article and let Crowdin guide
you through the process.
Additional files to be translated:
resources/generations.yamlresources/strings.tomlarticles/_index.md
When you finish translating a document, please drop
me an email (address in the website) or open an issue
here so I can review it and deploy it.
Feel free to ask me for help if you need.
Translating can get messy, so these are the
guidelines to help keep the content consistent:
-
Common tech terminology is tricky to translate,
sometimes it can be translated, sometimes not.If in doubt, just leave it as is.
-
Some unique names may seem 'translatable'
( i.e. the 'Scalar Unit' of the Nintendo 64 )
however they shoudln't be translated, since
it's a term used to identify that component
and no other. -
Some sentences structures may only sound
natural in English, in those cases feel free to
re-construct them if you find a better form in
your language. -
Blocks of Hugo syntax only require
name=""
andalt=""values to be translated, the rest
should stay as it is.
I hope I don't sound bossy with this, I'm actually very
grateful to anyone that helps me improve the site!
Finally, don't forget to sign the Authors
log with your name and, again, feel free
to give me a shout if you need help.
It's not very often, but I may add some new content to
an existing article that has been translated already.
In this case, I can only maintain:
EnglishSpanishCatalan
For the rest of languages, Crowdin can notify previous
translators whenever there's new changes detected.
As a rule of thumb, please check beforehand that the
article you are interested in translating doesn't have
many issues logged, this way you'll see which ones
are meant to stay as they are.
Thanks!