abettermap
commented
3 years ago I don't think the plugin would be an option since it's for a widget meant to be used in WP land. It might work on a page-level basis rather than site-wide, but have my doubts. If the widget output is available in GraphQL then maaaaybe it's usable, but I'm skeptical that mixing the WP sorcery with Next JS would go very well.
The manual translation is actually what I've seen the most in the research I did today. Next supports internationalization and there's a plug-in to generate the static content for each language (and a new set of URLs to go along with them), but it sounds like a serious undertaking. I don't think it's meant for 200-ish page websites, but it seems possible for single pages.
Another option for sitewide translation might be the Google Translate API that the WP plugin uses.
Lots of work either way, so gonna have to call this a good candidate for indefinite wishlist unless I have any solution revelations.
rperlin-ela
WISHLIST. With apologies for not raising this earlier, we're wondering if we can add a WP Google Translate plug-in (at least for a small set of languages) without it being too much trouble or requiring any real rearranging? To the right of the Get Involved button? From a quick look, a plug-in like GTranslate could be good— mostly free, decent reviews, simple to use— but we're open. First priority would be having an easy dropdown for users to translate as much of the site as can easily be translated. We realize that won't be everything, but it seems more doable than with the language map, right? A second priority, if it's possible, would be to allow manual translations that we could do for specific pages (e.g. a Wakhi translation of the Wakhi page), but we're less clear on how that should be done.