add multiple language selection

[lcxfs1991]

Preview:

Fixes #966

[lcxfs1991]

@bebraw Please take a look

[skipjack]

Ok so two things right off the bat:

• The build is failing because you can't import a stylesheet within antwar's <Interactive> component. I know you're not using <Interactive> directly but the Navigation component is. You'll have move the import './drop-down-style'; into the Site component (where you'll see a bunch of other style imports.
• Also, did you test this on the mid-range breakpoint (from 768 to 1024)? The main navigation section is already a bit crowded and I have a feeling adding another large link will either break the layout or make things look even more tight. I've been giving this some thought since you opened the issue and I think a tighter menu like this or this (maybe using abbreviations instead of flags) would be the right approach.

Once the import is resolved and we discuss the layout I'd be happy to do a fuller review/test. If need be, I can definitely help with this to get it across the finish line. Aside from the points I mentioned there's a few other design tweaks I might make but that can be done in a separate PR.

[skipjack]

@bebraw @sokra @TheLarkInn @lcxfs1991 also, from a higher level, how does internationalization play out in terms of issue management, prs, etc?

I know right now there's a translation branch in this repo and there's been some talk of using locki, #295, but I'm not sure where we're at with that. It seems there's a separate repo for the chinese fork (which I think makes sense for management purposes) but then what's the local translation branch for?

[lcxfs1991]

Local translation branch is for a separate management just like webpack-china since we have to fetch plugin/loader readme and put them under /content/ folder. However, the master branch generate directly. It is a bit hard for us to make a diff if we simply follow what master do.

I think we can try locki. But we need to ensure the performance and we'd better keep a local copy of data.

We can then compare two approaches, locki or webpack-china, and decide which one we should pick up for localization.

[skipjack]

@lcxfs1991 ah ok thanks for the clarification, I did see something about that in #722 I think. In terms of the getting this PR merged please see my comments above.

@bebraw any reason we can't just keep that change in the master branch? I actually kind of like having all site content, including fetched content, in the /content directory. Is this to keep a visual distinction for contributors so they know not to edit it?

[lcxfs1991]

Let me fix this tonight.

[skipjack]

Ok great, no rush.

[lcxfs1991]

width: 768

width: 1024

hover:

@skipjack pls check.

[skipjack]

@lcxfs1991 awesome work, I will review again (and hopefully merge) shortly!