Thanks for the link sgp_. I have in my todo lists some optimizations that will make getmonero more accessible (and therefor, give us better SEO)

An update about Weblate:

As i said before, we can easily translate the core of the website (LANG.yml files in _i18n) without much effort. The strings that are more problematic seem to be parsed correctly everywhere, so yay!

The roadmap can be easily translated on weblate as well

I don't think would be a good idea to put the dev guides on Weblate. They are full of code and terminology that should be kept in english. Translators would freak out trying to understand what's code and what needs to be translated

so those will have to be translated on gitlab manually

Footers and navigation (the menus) files in the current form cannot be translated on weblate, unless we remove all the links from the files.

That would make the files useless and the entire structure of the menus borked. I cannot think of a way to link each string with a link without bloating the pages with liquid syntax. I will look more into it, but i'm not optimist

The Moneropedia is problematic, but with some tweaks, doable. For some tweaks a i mean that the content of the entry itself can be easily translated on weblate (needs some scripting first, but no biggy), but the front matter should be translated manually on gitlab

or we will have in the front matter both keys and values translated, when the values must stay as they are. This will need some intenstive testing

The user guides should be easy to work on using a converter and some scripting

So, soon i will add to weblate the "Getmonero" project with 2 components: "monero-site", which will be the core of the website (the LANG.yml files in _i18n) and "roadmap", which guess guess.. it's the roadmap.

let's test those two, which are the most straightforward (but still, i will have to write some warnings and edit the weblate guide on github, because some workflows will have to change).

In the meantime i will work on the user guides, the rest will follow

Oh, i forgot to give a timeline: After all the current PR adding/removing/translating strings will be merged and i posted the updates to the guide for Weblate, i will add the new project and components

the roadmap will probably be not translatable until we update it. Now enough text :P

.merges

luigi1111 could you merge if you are back? i don't want to make too many PR based on other PR

Yes will today

rehrar: I've been looking into repo.getmonero.org/monero-project/monero-site/issues/925 for a good amount of time, but i can't figure what's happening. I mean, clearly jekyll is not being able to show those values at that level of depth,

but the question is: did the meta tags in head.html use to work after the change to the new multilang website?

because if thy did, i don't understand what broke them. If they didn't, that's just jekyll not being able to go through that variable in the front matter (which AFAIU, is expected)

in meta property="og:title" for example, the only elsif that seems to work is {% elsif page.title %} and loads properly only when the 'title' key is declared in the front matter. If it needs to pick it from the language files, it will just show the key, as is visible in the issue and with any meta tags checker

Maybe i'm just missing something, but i don't understand what and to test it i would have to build the website on a server first. Unless it's possible to check opengraph metadata locally

<rehrar> Yes, that broke at some point, and to my knowledge it worked initially.

<rehrar> I've tinkered with it several times before, and never found a solution.

.merges

is there more discussion about 1195? I don't see that message on the subreddit

1205 conflicts

ErCiccione[m]: looks like my Gitlab CI fix worked

thanks for merging :)

Looks like 1202 conflicts as well

Should I wait for more merges and then rebase?

I'll just mark it WIP for now