i18n: work on our first second-language about suitedocs HOT 3 CLOSED

Things that need to be done:

• translate site strings (like the menu options)
• have a plan for how to deal with an incomplete second language (the Spanish site will start with about 10% of the English site)
• decide whether the Blog will be multilingual or not
• ...

from suitedocs.

Just a note with information:

• changes to Website UI (menus, etc.) go in the i18n (internationalization) directory, with names like es.toml. Copy the existing format with the unchanged label name for category and edit the other value.

• name translated files exactly the same as their English counterparts, only with a language code before the extension, so setup.adoc changes to setup.es.adoc for Spanish.

• use the dropdown on the bottom of the sidebar to navigate between languages

from suitedocs.

This is done, we now have a partial Spanish User Guide, and Spanish menus.

from suitedocs.