00:35:20 <123bob123:matrix.org> But its pretty 06:44:43 adding hooks to our github repo so that weblate can make pull requests automagically seems cool no? https://github.com/monero-project/monero-site/issues/1907 06:47:19 a "Desired setup" table is here https://docs.weblate.org/en/latest/admin/continuous.html 13:49:45 I think worth another look 13:51:01 You are talking about the current website right ? 14:27:07 Me? Im talking about 1907 14:55:45 take this PR for example : https://github.com/monero-project/monero-site/pull/2230/files , which adds some new texts to translate (added only in en.yml). if we had webhooks setup. if/when this PR is merged, weblate will immediately make a pull request adding the empty placeholders to all lang files, instead of, when a translation coordinator of sorts makes a PR with +7000 diffs co 14:55:46 ntaining everything from the previous month(s) 14:56:48 "do it then" -> but i don't want to go to weblate school :( 15:08:19 Not you, lol 15:08:26 We can "hire" someone 15:09:09 What ever happened to netrik anyway? Ccs completed? 15:15:11 in netriks eyes the ccs was completed but unclaimed, i asked him to make a claim for the payout so people could discuss if it was actually completed or not. he did not try to claim the funds after that conversation dated 22nd august 15:52:31 Regarding the website I started I think I will do the same as current one. Blog post are in Markdown, other web pages content is in YAML. 15:52:31 In Astro we can use astro-i18n or astro-i18next for web pages. Locales can be in yaml or json 16:01:11 also, 'how do people submit a user-guide.. moneropedia article... how can the manual labour be reduced' should play into a 'new site'. example: a script to help with this on current site https://github.com/plowsof/userguide-drafts/tree/main/helper-scripts/make-a-guide 20:20:18 <123bob123:matrix.org> Why not just submitted the markdown guide 20:20:44 <123bob123:matrix.org> Otherwise it would be a website full of links to other repos