Consider switching from Jekyll to Hugo about monero-site HOT 3 CLOSED

Having had some light experience with translations on -site - if what you say is true with regards to Hugos advantages in this area then i consider the switch vital to the future of the Monero project. (e,g, If existing guides can be edited easier)

There was also a push to move to a https://monerodocs.org/ style of guides (and others which i can't remember right now).

My domain expertise in this area is lacking but i'm available to provide effort where possible. Thank you for raising this issue.

from monero-site.

I have no previous experience with Jekyll or Hugo.

However Hugo does seem too new for site of scale as getmonero.org at this point.

https://github.com/kurtsson/jekyll-multiple-languages-plugin - Plugin we are currently using seems to be out of a date for year

But I see there is successor of that plugin - https://github.com/untra/polyglot on github says "Jekyll doesn't provide native support for multi-language blogs. This plugin was modeled after the jekyll-multiple-languages-plugin, whose implementation I liked, but execution I didn't."

It seems that above plugin is up to date and well maintained, I am not sure how much cross compatible and easy to apply in our scenario.

I would make sure we exhaust all options on current setup before switching to someone new because there might not be guarantee that will be alive in next year or two.

Maybe better to invite some of these people to open CCS funding to keep language plugin up to date if only language plugin is causing issues.

from monero-site.

because there might not be guarantee that will be alive in next year or two

I see this as much more probable with the fork of the jekyll plugin than with Hugo, a project with a team behind that has already been around for years, while the fork is a personal project that is currently not listed as raccomended from Jekyll. I wouldn't switch to the polyglot plugin.

from monero-site.