01:52:20 the current website is built from his github repo. You can probably send prs there for now, else you can definitely send to the monero-project repo once finishef 11:35:22 what do you think about the dependency update prs? 2574 2575 2576 12:10:56 pretend they dont exist and get dockerise deploy ready to merge https://github.com/monero-project/monero-site/pull/2454 12:13:09 ready for testing, i just fixed some nitpicks in the workflow 12:14:58 namely this action that outputs a string of "true" "false" and i was matching on a boolean true so always rebuilding container https://github.com/dorny/paths-filter?tab=readme-ov-file#outputs 12:24:01 .merges 12:24:01 -xmr-pr- 2259 2472 2502 2550 2563 12:26:40 .merge+ 2454 12:26:40 Added 13:25:05 I prefer not modifying our branding just to be consistent with other icon set > <@redsh4de:matrix.org> Visual consistency with the rest of the icon set - i did put the og in there first to see how it looked, was even weirder 13:25:45 unless there is some contrast issues (not the case with light theme), we should just use the same logo as-is 14:22:51 Updates: 14:22:51 * Added template files for Markdown content: src/content/blog/_template.md and src/content/moneropedia/_template.md. Markdown files starting with _ will be ignored by the build process 14:22:51 * For Blog Pages: The "Recent Posts" sidebar will now populate - it will filter out the page you are currently on, shows up to 4 posts with title and date 14:22:51 * For Blog Cards: If a image thumbnail is not defined in the markdown, a text thumbnail will be generated from the first tag of the post[... more lines follow, see https://mrelay.p2pool.observer/e/7KP4y80KRnB0SzRT ] 14:28:19 https://mrelay.p2pool.observer/m/matrix.org/rntWwOonDntXkTuFjBZGQYNd.png (image.png) 14:28:42 https://mrelay.p2pool.observer/m/matrix.org/hKFcssHVlWfzeQGiasKJRYfC.png (image.png) 14:31:36 https://mrelay.p2pool.observer/m/matrix.org/QFyuyXvzWqNWjZVVqNRmwLJW.png (image.png) 16:50:24 Might sound funny given the chat in research lounge chat lol, but there also is a scalability concern with the blog i'd like to get some opinions on 16:50:24 The new website by default localizes absolutely everything. Currently for locale routes in the blog, the exact same blog content will be recreated again and again for each language, the only differences being the header, footer and UI element languages. 16:50:24 The blog posts themselves aren't localized (only UI elements are), so we're duplicating identical blog content across locales.[... more lines follow, see https://mrelay.p2pool.observer/e/38CU0M0KU19BV2lV ] 16:55:28 id argue that blog posts dont need to be localized 17:09:24 Having the blog pages be generated just for the English locale, and having the other language post routes direct to the English one does reduce duplication 17:09:24 However it would impact UX slightly, as all of a sudden from the French language context, you are moved to the English context due to opening a blog post - footer, header and all UI would all be in English too and direct you to the English versions, instead of the locale you just were on. This would be especially jarring for RTL locales imo 17:09:24 Unless the user navigates back using the browser back button, they would have to change the language via the dropdown again every time[... more lines follow, see https://mrelay.p2pool.observer/e/6JPa0M0KRDJQTmM5 ] 17:11:13 I’ll make a Github issue, later will compare the size of the built website for between both approaches after moving over all posts and locales from current website 17:11:13 Maybe it won’t be that significant of a difference to matter 17:11:14 cant you soft link the pages? 17:11:48 So its not truly duplicated 17:13:15 Yes, i can make Astro generate a 302 redirect page which throws you to the English blog post page - but because everything is static and there is no server side magic happening, the UI elements would still be in the language of the context you are moved into 17:24:05 this only effects the built time of the website? 17:24:44 When i spoke of soft linking, i meant on the repo 18:05:59 @ofrnxmr:xmr.mx: Build time and size of the built site, yes - performance unimpacted 18:10:00 @ofrnxmr:xmr.mx: Soft linking won’t work here, as all routes are generated dynamically 18:10:00 In the code itself there is no duplication of content for locales (unless for explicitly translated content), nearly all of the heavy lifting is done by the build process 18:13:45 --limit-posts 1 18:18:46 @redsh4de:matrix.org: Im only referring to the size of the repo 18:18:51 Not the build of the website 18:22:35 Yeah, repo size completely unimpacted 18:22:58 You dont need to manually copy paste the same blog post in the code for every language 20:12:57 we can also host blog on a subdomain... > <@redsh4de:matrix.org> Might sound funny given the chat in research lounge chat lol, but there also is a scalability concern with the blog i'd like to get some opinions on 20:17:58 .merge- 2563 20:17:58 Removed 20:23:15 @basses:matrix.org: and the home button/monero logo will return to that subdomain to homepage so user knows that he is stuck here, but still pain UX. 21:07:19 found https://redlib.catsarch.com/r/webdev/comments/195x5yj/astro_and_i18n_insights/n3qvlkd/?context=3#n3qvlkd , idk if useful 21:08:55 @basses:matrix.org: Yeah tbh i think its best to keep it as is, the UX is good that way 21:09:51 https://mrelay.p2pool.observer/m/matrix.org/GHcHharZqBtOUfkZTirinSPy.png (clipboard.png) 21:09:57 tried even using brave AI as last resort, sounds like bs/irrelevant? 21:10:25 all other "non-solutions" were to use JS, SSR or set a cookie. 21:10:31 Yeah nah all of this i researched and handled last month, Astro's defaults kind of suck 21:10:55 which is not relevant at all for our case as we are trting to stay away from all of taht 21:12:51 The top solutions offered also always required setting up a dynamic route exclusively for locales... which means duplicating all the .astro pages, which violates the DRY principle and wasn't going to have that 21:14:22 @redsh4de:matrix.org: but will have to use rel="canonical" to not mess up with seo and think it is a diff content per locale. Also, with the amount of current monero blogs and expected rate of blogs, when can it be a concern? 21:19:35 Actually just checked... severely overestimated how much space the blog content takes up 21:19:35 The text content is only 7.1 mb, total for all the blogs from 2014 until now 21:19:35 There are 23 locales supported by the current monero website, so if we port all of the blogs and all locales over, the blog would take up 7.1*23 = 163MB, with 7.1MB added per new locale 21:19:53 Thats nothing 21:21:18 i think we can live with that? 21:21:41 given that new posts dont get added that often anyway 21:22:32 can it make the website slower? 21:22:53 no - only thing that would be slower is generating the website from the source code 21:22:57 client performance unimpacted 21:23:07 *user 21:23:39 we will probably only have like 10 max locale as the threshold to add new locale will be 90-95% translation of website > <@redsh4de:matrix.org> Actually just checked... severely overestimated how much space the blog content takes up 21:24:13 good threshold to have 21:24:34 so plowsof and ofrn only, not a problem lol > <@redsh4de:matrix.org> no - only thing that would be slower is generating the website from the source code 21:25:12 splendid 21:27:22 subtle change for the blog - it will now also use nested date directories for posts like in the current site 21:27:22 Minor difference is that i have made everything pertaining to the blog nested under the /blog folder: https://beta.monerodevs.org/blog/2025/11/14/monero-GUI-0.18.4.4-released/ 21:28:01 same post on the current getmonero page: https://www.getmonero.org/2025/11/14/monero-GUI-0.18.4.4-released.html 21:30:10 Backwards compatibility can be a issue - but that should be solved at the nginx/apache level via a rewrite rule 21:31:04 what about users cloning the repo and building the website? slow and about 200mb size? > <@redsh4de:matrix.org> no - only thing that would be slower is generating the website from the source code 21:31:38 nah - the duplication happens after they clone and build 21:32:37 whole repo right now is barely 47 MB 21:33:09 @basses:matrix.org: And coolify does it automatically anyway 21:34:33 @ofrnxmr:xmr.mx: coolify is selfhosted, right? 21:34:51 dont want $100k bill randomly 21:35:48 Yup, selfhosted 21:37:34 When it goes to getmonero.org it will likely go behind cloudflare caching 21:41:30 @ofrnxmr:xmr.mx: I forgot to visit getmonero.org when CF was done lol 21:41:41 was it impacted? 21:43:28 @redsh4de:matrix.org if you are interested into similar setup to current getmonero website, https://gitlab.com/fdroid/fdroid-website/ is the closest thing, they also have locale blog post and sometimes publish localized blog posts 21:44:10 @basses:matrix.org: Yes 21:44:25 Only for some ppl tho. It loaded over tor for me but not cleaenet 21:48:14 @basses:matrix.org: would they have similar problems? website contribution is almost non existent as it is very outdated and complex setup. 21:48:33 contributions* 21:50:22 Nah, it was only a concern because the new website is built for localization from the ground up - but since the output is a static site, the same pages will get generated for all languages 21:50:22 If you dont care about localization that much - not that much of a problem