<1​23bob123:matrix.org> But its pretty

adding hooks to our github repo so that weblate can make pull requests automagically seems cool no? monero-project/monero-site #1907

a "Desired setup" table is here docs.weblate.org/en/latest/admin/continuous.html

I think worth another look

<c​hch3003:monero.social> You are talking about the current website right ?

Me? Im talking about 1907

<p​lowsof:matrix.org> take this PR for example : monero-project/monero-site #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<clipped message>

<p​lowsof:matrix.org> ntaining everything from the previous month(s)

<p​lowsof:matrix.org> "do it then" -> but i don't want to go to weblate school :(

Not you, lol

We can "hire" someone

What ever happened to netrik anyway? Ccs completed?

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

<c​hch3003:monero.social> 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.

<c​hch3003:monero.social> In Astro we can use astro-i18n or astro-i18next for web pages. Locales can be in yaml or json

<p​lowsof:matrix.org> 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 github.com/plowsof/userguide-drafts…ee/main/helper-scripts/make-a-guide

<1​23bob123:matrix.org> Why not just submitted the markdown guide

<1​23bob123:matrix.org> Otherwise it would be a website full of links to other repos