chore: add metadata JSON file for website configuration

[3w36zj6]

cf. #233

This pull request introduces a metadata configuration system for the website, centralizing site-wide settings into a new JSON file and schema. It refactors how metadata and translation settings are loaded, making the site easier to configure for different languages and deployments.

[Copilot]

Pull Request Overview

This PR introduces a centralized metadata configuration system for the website, replacing hardcoded values with a JSON-based configuration approach. The changes enable easier configuration for different languages and deployments by consolidating site-wide settings into a single metadata file.

• Replaces hardcoded metadata values with a JSON configuration file and TypeScript schema
• Implements dynamic language switching based on metadata configuration
• Removes version from package.json in favor of metadata-driven versioning

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
website/src/translation/index.tsx	Updates translation system to dynamically select language based on metadata configuration
website/src/metadata.ts	Refactors to load all metadata from JSON file instead of hardcoded values
website/package.json	Removes version field, now managed through metadata.json
website/metadata.schema.json	Adds JSON schema for metadata validation
website/metadata.json	Introduces centralized configuration file with all site metadata

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[3w36zj6]

Could you please do a quick review? @YDX-2147483647 @Its-Just-Nans

[Its-Just-Nans]

Yes it's good

Another options would be to use an array destructuring, but the order will be important

const [Translation, translation] = (() => {
  switch (language) {
    case "ja-JP":
      return [JaJPTranslation, jaJPTranslation];
    case "en-US":
      return [EnUSTranslation, enUSTranslation];
    default:
      throw new Error(`Unsupported language: ${language}`);
  }
})();

[YDX-2147483647]

as unknown is not necessary here.
Additionally, I remove it and find displayTranslationStatus is missing in metadata.json. 😸

[YDX-2147483647]

I think [^/]+ should be replaced with .+. Otherwise, it won't allow /foo/bar/.

[YDX-2147483647]

If properly set up, then this can be simplified to await import(`./locales/${language}.tsx`). Not sure if it's worth it, though.

https://github.com/rollup/plugins/tree/master/packages/dynamic-import-vars

Properly set up:

1. Enable top-level await for TypeScript.

   Add "target": "es2017" (or newer) to website/tsconfig.json

2. Enable dynamic import for Vite.

   • Add a new dependency @rollup/plugin-dynamic-import-vars
   • Add dynamicImportVars({ include: "src/translation/", errorWhenNoFilesFound: true }) (or maybe just dynamicImportVars()) to defineConfig(plugins: [...]) in website/vite.config.ts

3. Mitigate limitations.

   • Put {ja-JP,en-US}.tsx into a dedicated directory, because variable imports cannot import their own directory.

   • Annotate { Translation: TranslationComponent; translation: TranslationObject }, because it's too hard for typescript to infer the type.

[YDX-2147483647]

LGTM!
The comments are for reference only and can be ignored.