Core comes with translations out-of-the-box, using the i18n-js package. Certain components take i18nScope props to point to custom translation path keys. These can be custom, or the default Core keys can be overwritten. The user-provided translations are deeply merged with the Core defaults, and the user's translations will be favored in any merge collisions.