Where do I start with translation/localization for accessibility?

Topic

Hiya,

I would like to look into contributing to p5.js by translating the website to Dutch, my own native language.

Can anyone point me into the right direction on where to start on this process? I'm familiar with how localization works for websites, but there are a couple things that are less clear to me:

• When do you consider support 'finished' enough for it to be added to the website? I know you guys want the tool to feel consistent, so I'm not sure if you have any strict rulings on this. Does all content need to be translated or, say, mainly the 'references' section? What about news articles. about pages, etc?
• Do I need to make a commitment to keep updating future pages for a localization PR to be accepted? What is the general consensus on maintaining a language?
• Is there a page I have missed that guides contributors into the specific localization process for the p5.js website? I'm talking both conceptually (e.g. addresses the above questions) and technically (e.g. addresses the specific technical specifications for the localization process of the p5js website).

Thanks in advance, and I'm keen to see if I can help contribute.

The issue names no files, tests, or entry points. Start by locating the p5.js website's existing localization documentation and implementation, then document the contribution process, translation scope, acceptance expectations, and maintenance responsibilities for Dutch support.