feat: Multilingual sites as a first-class citizen

[jaredcwhite]

There's no good reason not to support multiple languages and locales out of the box. So we should first document a few common use cases for what would be expected features and workflows for adding new languages (and things like date formats) to a site, and then pick the most obvious, low-hanging fruit as the first item to tackle. And the more we can make this process familiar to devs coming from other frameworks or CMSes, the better IMHO.

Also a point to remember: however this all gets implemented, it should be done in a way that makes it easy for plugins to integrate with any such enhancements. For example, what if there were a plugin that could call an API like Google Translate and provide a new language variant of a page on-demand?

[jaredcwhite]

Started on new features here in 0.17, want to keep the momentum going in 0.17.1 0.18…

[goulvench]

Just landed here from the Ruby Weekly newsletter, and this project looks very promising!
I'm currently using Jekyll, and have wrestled with it to implement a few of the features you're looking at implementing, I'll see if I can lend a hand.

One thing to note: many websites are not multilingual, but require a locale other than English. I'd love being able to set locale: 'fr' (or whatever) in config and have dates come out localized at the other end without any more work. This may be simpler and faster to achieve than full multilingual sites from the get-go, and a good first step.

[jaredcwhite]

Hello @goulvench — my sincere apologies, I somehow missed seeing this message before. Yes I'd love any input you might have — I know language and locale often get lumped into a single concept but they're not quite the same thing, My perspective is sadly limited somewhat as a U.S. citizen, so I'd definitely appreciate international folks providing context.

[jaredcwhite]

There are a number of aspects to the new Resource content engine first added to 0.20, so we'll focus our efforts there from this point forward.

[jaredcwhite]

This issue has been addressed in Bridgetown 1.1. I'm sure we'll have some follow-up work to do but that can be dealt with via new issues.