Config: Add default Hugo and Languages config

[marcuspollio]

Description

• Add default Hugo config: baseURL, project title, defaultContentLanguage, main and footer menus, taxonomies, some permalinks and cascade overrides, module mounts for assets pipeline and some languages fallback and tweak some other settings. Refer to Hugo official docs for details or ask here.
• Add default Languages config: some 13 languages for now with only 7 enabled for testing. As soon as we have more contributors in different languages, we can gradually enable and add more.

If wanting to review or just curious, I suggest to have a look at these two:

• Content collection paths in hugo.yaml#menus: the name chosen (e.g. features, download, news, etc) can be still changed, but better now than later. The collection labels displayed on the website can be different and translated (Title field), but sticking to an agreed path scheme is easier moving forward. For example, we could have about instead of features or resources instead of docs.
• If you are native speaker of one of the 13 languages, please do check the respective values are correct.

Issues

Part of Website migration

PR Checklist

• This change is verified to work as described.
• This change complies with the repository Guidelines.

[marcuspollio]

FYI @maxwxyz @chennes @yorikvanhavre @PhoneDroid @hyarion

[chennes]

Is the long-term plan to manage the included languages manually, as shown here? FreeCAD itself, and the current FreeCAD website, are translated on CrowdIn, and a small script downloads and applies those translations automatically when the translation percentage exceeds 50% (see https://github.com/FreeCAD/FreeCAD-Homepage/blob/main/updatefromcrowdin.py).

[marcuspollio]

Hi @chennes thanks for asking.

The new website is designed to not use any external service such as CrowdIn, but rely instead on the build-in languages and translations support of the Static Site Generator and Content Management System. There are several reasons for that I previously explained in a few places (I can provide them again if wanted).
While we will loose some translation features available via such external platforms and may deter some accustomed translators, it will make content management much easier as always in full context (full page access, almost WYSIWYG, editorial workflow, etc) and can be expanded in the future to more website bits (documentation).

So yes, currently for this migration phase, the included languages are managed manually, as it still is a testing bed. Then when we advertise this project more broadly and request for translation contributions from the community, I plan to include a small CI script based on a few simple rules also present in the contribution guidelines (i.e. top-level sections/collections content fully translated, theme i18n, proof-reader designated, etc). I still need to upload translation templates though.