OpenAtlas » OpenAtlas Discovery

Currently we are using vue i18n and it works well. I've discovered https://v8.i18n.nuxtjs.org/ which might be usefull if we want better SEO depending on the language as well as a few other features, though I'm not sure if it is necessary for our use case.
E.g. it also allows for persisting the language selection. However, it does so through the use of cookies, so I'm not sure if we want that.

It might also be a good idea to use this: https://github.com/olizilla/lol
For creating a list of locales to select from. Especially when adapting OAD for a different Project with more supported languages.

I kind of avoid SEO and cookie topics in the backend but of course you are right, for presentation sites this absolutely makes sense.
SEO can't hurt for public available websites that present project results, when using cookies we will need a cookie disclaimer thingy but I guess, we will need that in the long run anyway.

Sadly I can't comment on the technical site of things but I added other frontend developers as watcher, maybe they want to comment too. You can always add watcher yourself in case you think this might be interesting for others.
Thank you for looking into this.

At the moment new locales can only be added by us in the main repository. Should it be possible for our partners to add their own .json files containing other locales? At the moment that would be needed to enable them to add support for multiple languages.
Additionally: How do we handle content in other languages that aren't supported in the user interface. Do we allow it?

I would say for completion of this issue it should be possible to set a default display language in the user managed configuration.
Adding additional content languages even if no user interface translations are available has no high priority so I created an extra issue in the wishlist (#2044).