13:23:21 <1​7lifers:mikuplushfarm.ovh> submitted 13:43:52 Ty! 14:26:45 clipboard.png 14:27:04 Monero means money should be behind it (not shown) 14:39:19 some Tor Browser quirk ig, will have a look later 14:45:19 oh yeah, just checked with firefox, works fine 14:45:21 sorting out stuff with i18n, do we want to keep the existing .yamls from the current page? 14:45:37 plowsof 14:46:05 im looking at integrating Paraglide for it's tooling, makes dealing with localization less of a nightmare but it's .json based 14:46:51 dynamic language routes are live though on the i18n branch 14:46:54 no tls yet 14:47:11 monero will be using Weblate for translations, so it works great with such workflow and fully supported then ok 14:47:42 monero will be using Weblate for translations, so if it works great with such workflow and fully supported then ok 14:48:07 https://docs.weblate.org/en/latest/formats/json.html 14:48:08 guess fine? 14:57:18 Yeah, i18next in this case 16:31:32 luigi1111: ping regarding hashes.txt.sig 18:28:49 btw I would suggest removing the website git source from source code link in footer, just put the github org link instead https://github.com/monero-project 18:46:25 How come? Seems intuitive that the source link on the website would lead to the source code of the website 18:53:09 u don't visit getmonero.org to look at website's source code, only relevant stuff for Monero 🤷 18:54:08 monero core 18:55:13 u wouldn't like seeing a closed source app showing in footer "source code" (gives false sense of openess) and it just links to website source code while their product is actually proprietary 18:57:56 Source code and link to github for GUI or CLI can be listed next to GUI and CLI 18:57:57 As can source for the other downloads on the website. 18:59:04 Can probably _add_ a link to the github org, but to remove the website link? NACK 18:59:18 then remove the mention of source code in footer, no need 19:00:46 No 19:01:27 Btw, source links to CLI and GUI are already listed on the downloads page 19:57:34 I'll just keep it as is for now then, all links in the footer mirror the existing site, if we some meeting later about the page content to reach consensus, easy change 20:03:11 Localization support is live on the deployment 20:03:11 TL;DR: 20:03:13 - dynamic language route generation on build 20:03:15 - uses i18next for translation strings + namespaces for context management, should be Weblate compatible rando 20:03:17 - single source of truth for localization data & configs: src/i18n 20:03:19 - responsive language dropdown, images in the PR: https://github.com/redsh4de/monero-site/pull/2 20:05:54 Currently added some dummy machine translations for just the index page, just to see that it works as intended 20:10:23 btw we are aiming for 0 JS 20:12:21 This implementation is static only, shouldn't be a single script tag anywhere 20:12:56 This implementation is static only, the built version shouldn't be a single script tag anywhere 20:14:34 the language selection needs js 20:15:27 you can see the one in https://www.privacyguides.org/en/basics/why-privacy-matters/ 20:15:33 it can work without js 20:15:42 they are using mkdocs material 20:16:14 I mean people that want to set a local can just append at end of url their local or when using search engine it can find it 20:16:30 but of course it would be better to have non-js version if possible. 20:16:40 Really? It shouldnt 20:17:09 I would also get rid of country flags https://www.flagsarenotlanguages.com/blog/why-flags-do-not-represent-language/ 20:17:17 yes, try tor browser safest mode 20:20:31 I see it, seems like a Tor specific bug on the index page, must be related to why the dropdown also appeared under the hero text 20:20:31 Does it work when you navigate to the downloads page and then press the language selector? 20:21:15 There should be no JavaScript dependency anywhere as all the routes are generated as static files in the end, the JS in the source only runs on build time 20:21:35 In order to create route files, fill in the templates with translations etc 20:21:37 oh it does indeed, cool 20:24:55 fairs, current page doesn't have them either 20:45:36 nuked the flags, trying to figure out why there are rendering issues only on the index page on Tor 21:35:50 ended up being the noscript extension 21:45:16 should be fine now rando