feat: Japanese translations

.toolkit-mdrc

@@ -1,4 +1,5 @@
 {
+  "contentDir": "website/docs",
   "ai": {
     "model": "us.anthropic.claude-3-7-sonnet-20250219-v1:0",
     "maxTokens": 8000,
@@ -7,7 +8,12 @@
       "tokens": 160000
     },
     "contextStrategy": "siblings",
-    "styleGuides": ["./docs/style_guide.md"],
-    "exemplars": ["./website/docs/security/iam-roles-for-service-accounts"]
+    "styleGuides": [
+      "./docs/style_guide.md",
+      "i18n"
+    ],
+    "exemplars": [
+      "./website/docs/security/iam-roles-for-service-accounts"
+    ]
   }
-}
+}

i18n/style.ja.md

@@ -0,0 +1,43 @@
+# Style Guide - Japanese Translation
+
+The following are style guidelines specific to the Japanese language.
+
+The term "Shared Responsibility Model" should be translated as 責任共有モデル
+
+Where describing workloads/components of the sample application being deployed keep these in the original English. For example:
+
+- Catalog
+- Checkout
+- Orders
+- Carts
+- Assets
+
+ALWAYS keep these technical terms in the origin English instead of translation to Japanese:
+
+- VS Code Terminal
+- Terraform state
+
+There are some technical terms that should be translated, for example:
+
+- Port forwarding: ポートフォワーディング
+
+ALWAYS keep AWS service names in the original English instead of translating to Japanese. This also includes AWS and EKS technical terms like:
+
+- Elastic IP or EIP
+- IAM role
+
+ALWAYS keep Kubernetes terminology in the original English instead of translating to Japanese:
+
+- EKS Auto Mode or just "Auto Mode"
+- Kubernetes
+- Ingress
+- Pod Topology Spread Constraints
+- PodDisruptionBudget
+- NodePool
+- general-purpose
+- StatefulSet
+- StorageClass
+- Horizontal Pod Autoscaling
+- Custom Resource Definition (CRD)
+- Taint
+- Toleration

website/docs/observability/high-availability/01-scale.md

@@ -98,6 +98,6 @@ $ timeout 10s ~/$SCRIPT_DIR/get-pods-by-az.sh | head -n 30
 For more information on these changes, check out these sections:
 
 - [Chaos Mesh](https://chaos-mesh.org/)
-- [Pod Affinity and Anti-Affinity](/docs/fundamentals/compute/managed-node-groups/basics/affinity/)
+- [Pod Affinity and Anti-Affinity](../../fundamentals/compute/managed-node-groups/basics/affinity/)
 
 :::

website/docs/troubleshooting/workernodes/index.md

@@ -5,7 +5,7 @@ description: "Bring worker nodes in an Amazon EKS Managed Nodegroup back to heal
 sidebar_custom_props: { "module": true }
 ---
 
-In the following scenarios for worker nodes we will learn how to troubleshoot various AWS EKS worker node issues. The different scenarios will walk through what is causing nodes fail to join the cluster or stay in 'Not Ready' status, then fixing with a solution. Before you begin, if you want to learn more about how worker nodes are deployed as part of managed node groups see [Fundamentals module](/docs/fundamentals/compute/managed-node-groups).
+In the following scenarios for worker nodes we will learn how to troubleshoot various AWS EKS worker node issues. The different scenarios will walk through what is causing nodes fail to join the cluster or stay in 'Not Ready' status, then fixing with a solution. Before you begin, if you want to learn more about how worker nodes are deployed as part of managed node groups see [Fundamentals module](../../fundamentals/compute/managed-node-groups).
 
 :::tip Before you start
 Prepare your environment for this section:
@@ -16,13 +16,13 @@ $ prepare-environment troubleshooting/workernodes
 
 You can view the Terraform that applies these changes [here](https://github.com/VAR::MANIFESTS_OWNER/VAR::MANIFESTS_REPOSITORY/tree/VAR::MANIFESTS_REF/manifests/modules/troubleshooting/workernodes/.workshop/terraform).
 
-
 :::
 :::info
 
-The preparation of the lab might take a couple of minutes and it will make the following changes to your lab environment: 
-- Create a new managed node groups called new_nodegroup_1, new_nodegroup_2, new_nodegroup_3 with desired managed node group count to 1 
-- Introduce a problem to the managed node groups which causes node join failure and ready issue 
+The preparation of the lab might take a couple of minutes and it will make the following changes to your lab environment:
+
+- Create a new managed node groups called new_nodegroup_1, new_nodegroup_2, new_nodegroup_3 with desired managed node group count to 1
+- Introduce a problem to the managed node groups which causes node join failure and ready issue
 - Deploy resource kubernetes resources (deployment, daemonset, namespace, configmaps, priority-class)
 
 :::

website/docusaurus.config.js

@@ -20,7 +20,7 @@ const manifestsOwner = process.env.MANIFESTS_OWNER || "aws-samples";
 const manifestsRepository =
   process.env.MANIFESTS_REPOSITORY || "eks-workshop-v2";
 
-const labTimesEnabled = process.env.LAB_TIMES_ENABLED || false;
+const labTimesEnabled = false;
 
 const baseUrl = process.env.BASE_URL || "";
 
@@ -54,7 +54,7 @@ const config = {
 
   i18n: {
     defaultLocale: "en",
-    locales: ["en"],
+    locales: ["en", "ja"],
   },
 
   presets: [
@@ -163,6 +163,10 @@ const config = {
             position: "left",
             label: "Troubleshooting",
           },
+          {
+            type: "localeDropdown",
+            position: "right",
+          },
           {
             href: "https://github.com/aws-samples/eks-workshop-v2",
             position: "right",

website/i18n/en/code.json

@@ -0,0 +1,10 @@
+{
+  "terminal.copyCommand": {
+    "message": "Copy command",
+    "description": "The button on terminal component to copy a command"
+  },
+  "terminal.copyAllCommands": {
+    "message": "Copy all commands",
+    "description": "The button on terminal component to copy all commands"
+  }
+}