Translate the website

[bitigchi]

Lack of website localisation is not ideal. At least the main page and the download pages should be translated.

It would be nice if blog post translations would be available as well. Community members can translate the blog posts as they please, and the translated versions would appear.

There should be a mechanism to make sure all the markdown pages (Development etc.) are properly translated though (without omissions).

[jt15s]

I think Hugo does have support for translations - I think we can hook the website up to something like Pootle and it'll work. Though, we will have to consult the documentation and see if our site needs any changes to make it work.

[bitigchi]

Also this might be a good chance to move the documentation on the website to a separate wiki and have a core informative website that is focused on marketing.

[jt15s]

That would take a lot of work and redirecting (remember that a lot of the blog posts and news items link to the documentation) - additionally, I don't think having one more thing to maintain would be good for the sysadmins. The plan is to reorganise all the documentation in the website without moving anything out of the website elsewhere.

If we want wiki-like editing functionality, we can always set up Forestry or NetlifyCMS (I personally think this one is more ideal since it's FOSS) - these provide WYSIWYG editors that tie into the website repos.

[bitigchi]

There is already a wiki on Trac, it just needs more copy-pasting from the main website.

It’s just pointless to worry about broken links, it will eventually happen. Those said blog posts and news items also would be well outdated at this point. A general redirect with a Trac search query would find the most relevant item with great probability anyway.

Last but not least, it’s unrealistic to expect translators to translate the whole documentation, it will scare people off. Just have a core static website and shove the documentation to Trac.