Internationalization (i18n)

[dreglad]

Have you read the Contributing Guidelines on issues?

• I have read the Contributing Guidelines on issues.

Description

Being able to translate the UI would be a great feature that could make adoption more appealing to a broader user base.

While I am aware that implementing this might not be a priority for the core team due to the significant changes it would require in the UI development and maintenance workflow, and the addition of at least one extra step to the build pipeline, I am considering contributing to this effort myself.

I'd like to propose a PR to add internationalization (i18n) to the application. However, before proceeding, I would like to understand how likely it is that such a contribution would be accepted. I'm also eager to know if there are any specific conditions or considerations that the authors believe I should take into account to ensure my contribution aligns well with the project's goals and existing structure.

Motivation

The ideal mental model for users to conceptualize domain-specific aspects of a software system tends to be pretty culture/language dependent. Being able to align EventCatalog's UI language with the domain's primary language and terminology may result in a more uniform and enjoyable experience, especially when sharing with non-developer stakeholders.