docs: japanese translation v2

crowdin.yml

@@ -0,0 +1,10 @@
+project_id: '619760'
+api_token: 71920d310ddf281a4d742dbeae5fba47c3f3c577bbd243c98f2dbfd917dd166e11aa6bcf4235b4e8
+preserve_hierarchy: true
+files:
+  # JSON translation files
+  - source: /i18n/en/**/*
+    translation: /i18n/%two_letters_code%/**/%original_file_name%
+  # Docs Markdown files
+  - source: /docs/**/*
+    translation: /i18n/%two_letters_code%/docusaurus-plugin-content-docs/current/**/%original_file_name%

docs/best-practices/account-types.mdx → docs/configuration/account-types.mdx

@@ -1,7 +1,7 @@
 ---
 title: Bucketeer account types
 # sidebar_position:
-slug: /best-practice/account-types
+slug: /configuration/account-types
 description: This page describes the existing account types available on Bucketter.
 tags: ['guide', 'account', 'account-types']
 ---

docs/feature-flags/api-keys.mdx → docs/configuration/api-keys.mdx

@@ -1,7 +1,7 @@
 ---
 title: API keys
 # sidebar_position:
-slug: /feature-flags/api-keys
+slug: /configuration/api-keys
 description: Describes what API keys are, what they are used for, and how to create them.
 tags: ['integration', 'feature-flag']
 ---

docs/configuration/configuration.md

@@ -0,0 +1,17 @@
+---
+id: configuration
+title: Configuration
+slug: /configuration
+---
+
+# Configurations
+
+In this category, you will find information regarding complementary settings you can do when using the Bucketeer dashboard. The configurations available on these pages support the feature flag creation and usage. Below, you find the links and a brief description for each section.
+
+## API keys
+
+The [API keys](/configuration/api-keys) describe what they're and how they're used to authenticate and control access to the Bucketeer system.
+
+## Account types
+
+The [Account types](/configuration/account-types) present the different account types available on Bucketeer. You can use these different account types to provide different access levels to each team member.

docs/feature-flags/index.md

@@ -15,10 +15,6 @@ This section presents the necessary information to use Bucketeer feature flags.
 - [Evaluate results](../feature-flags/creating-feature-flags/evaluate-results): Explore how to evaluate and analyze the usage of your flags.
 - [Other flag settings](../feature-flags/creating-feature-flags/settings-and-history): Explore additional settings and options for your flags.
 
-## API keys
-
-The [API keys](/feature-flags/api-keys) describe what they're and how they're used to authenticate and control access to the Bucketeer system.
-
 ## Testing with flags
 
 The [Testing with flags](../feature-flags/testing-with-flags) will cover the three components used to perform tests on the Bucketeer system:

docs/getting-started/create-an-account.md

@@ -7,7 +7,7 @@ tags: ['guide', 'account', 'create']
 
 import CenteredImg from '@site/src/components/centered-img/CenteredImg';
 
-Bucketeer allows you to manage and track data related to different environments. To begin using Bucketeer, you need an account. For additional information regarding the available account types on Bucketeer, check the [Bucketeer account types](../best-practice/account-types). Ask the project administrator to create an account if you're a new team member.
+Bucketeer allows you to manage and track data related to different environments. To begin using Bucketeer, you need an account. For additional information regarding the available account types on Bucketeer, check the [Bucketeer account types](../configuration/account-types). Ask the project administrator to create an account if you're a new team member.
 
 The following steps show how to create an account as an Admin.
 

docs/getting-started/index.mdx

@@ -51,7 +51,7 @@ Flags also enable A/B testing, allowing developers to compare different feature
 
 Additionally, feature flags align with trunk-based development, enabling developers to merge changes to a shared codebase without affecting production users. This practice ensures a releasable codebase, fostering collaboration within large teams.
 
-To learn how to use and take advantage of flags on Bucketeer, check the [Using Feature Flags](#) section.
+To learn how to use and take advantage of flags on Bucketeer, check the [Using Feature Flags](/feature-flags) section.
 
 ## Member roles on Bucketeer
 
@@ -68,7 +68,7 @@ Bucketeer was designed to accommodate different types of members. Below you find
   <p>
     To get started, you will need to set up feature flags on the Bucketeer
     dashboard. You can refer to the
-    <a href="#"> Using Feature Flags</a> guide to learn more
+    <a href="/feature-flags"> Using Feature Flags</a> guide to learn more
     about the process. Once you have your credentials and have created a feature
     flag, you can choose an SDK that best suits your application. The <a href="/sdk">
       SDK
@@ -97,7 +97,7 @@ Bucketeer was designed to accommodate different types of members. Below you find
     First and foremost, it's important to understand how to enable or disable
     feature flags. Familiarize yourself with managing flags and the mechanisms
     for toggling them on and off with the
-    <a href="#"> Using Feature Flags</a> guide.
+    <a href="/feature-flags"> Using Feature Flags</a> guide.
   </p>
   <p>
     In addition to managing flags, you play a crucial role in designing and
@@ -111,7 +111,7 @@ Bucketeer was designed to accommodate different types of members. Below you find
     Utilizing feature flags enables you to conduct various types of testing,
     such as A/B testing. For more detailed information on experimentation,
     please refer to the
-    <a href="#/testing-with0flags"> Testing with flags </a>
+    <a href="/feature-flags#testing-with-flags"> Testing with flags </a>
     resource.
   </p>
   <p>
@@ -150,11 +150,9 @@ Bucketeer was designed to accommodate different types of members. Below you find
     platform. This includes tasks such as adding or removing members, assigning
     appropriate roles and permissions, and ensuring that the right level of
     access is granted to individuals based on their responsibilities. Check{' '}
-    <a href="/getting-started/create-an-account">
-      Create Bucketeer's account
-    </a>{' '}
+    <a href="/getting-started/create-an-account">Create Bucketeer's account</a>{' '}
     to learn more about account creation or access the{' '}
-    <a href="#">Bucketeer account types</a> to
-    learn more about the existing roles.
+    <a href="/configuration/account-types">Bucketeer account types</a> to learn
+    more about the existing roles.
   </p>
 </details>

docs/getting-started/quickstart/create-an-api-key.mdx

@@ -25,4 +25,4 @@ The Bucketeer team recommends naming the API key based on the system where it wi
   wSize="100%"
 />
 
-After creating the API key, it will appear on the **API Keys** page, and its state will be **ON**, meaning it's ready for use. Now you can move on to the next step and [create your first feature flag](/getting-started/quickstart/create-your-first-flag). However, if you want to learn more about the usage of the API keys, check the [API keys](#) page.
+After creating the API key, it will appear on the **API Keys** page, and its state will be **ON**, meaning it's ready for use. Now you can move on to the next step and [create your first feature flag](/getting-started/quickstart/create-your-first-flag). However, if you want to learn more about the usage of the API keys, check the [API keys](/configuration/api-keys) page.

docs/sdk/client-side/android/index.md

@@ -325,7 +325,7 @@ In regular use, you don't need to call the flush method because the events are s
 
 ### User attributes configuration
 
-This feature will give you robust and granular control over what users can see on your application. You can add rules using these attributes on the console UI's feature flag's targeting tab. [See more](#).
+This feature will give you robust and granular control over what users can see on your application. You can add rules using these attributes on the console UI's feature flag's targeting tab. [See more](/feature-flags/creating-feature-flags/targeting#user-attributes).
 
 <Tabs>
 <TabItem value="kt" label="Kotlin">
@@ -382,7 +382,7 @@ This updating method will override the current data.
 
 ### Getting user information
 
-This method will return the current user configured in the SDK. This is useful when you want to check the current user id and attributes before updating them through [updateUserAttributes](#updating-user-attributes).
+This method will return the current user configured in the SDK. This is useful when you want to check the current user id and attributes before updating them through [updateUserAttributes](android#updating-user-attributes).
 
 <Tabs>
 <TabItem value="kt" label="Kotlin">
@@ -408,7 +408,7 @@ val evaluationDetails = client.evaluationDetails("YOUR_FEATURE_FLAG_ID")
 
 :::caution
 
-Do not call this method without calling the [Evaluating user method](#evaluating-user). The Evaluating user method must always be called because it generates analytics events that will be sent to the server.
+Do not call this method without calling the [Evaluating user method](android#evaluating-user). The Evaluating user method must always be called because it generates analytics events that will be sent to the server.
 
 :::
 

docs/sdk/client-side/flutter/index.md

@@ -275,7 +275,7 @@ In regular use, you don't need to call the flush method because the events are s
 
 ### User attributes configuration
 
-This feature will give you robust and granular control over what users can see on your application. You can add rules using these attributes on the console UI's feature flag's targeting tab. [See more](#).
+This feature will give you robust and granular control over what users can see on your application. You can add rules using these attributes on the console UI's feature flag's targeting tab. [See more](/feature-flags/creating-feature-flags/targeting#user-attributes).
 
 <Tabs>
 <TabItem value="dart" label="Dart">
@@ -331,7 +331,7 @@ This updating method will override the current data.
 
 ### Getting user information
 
-This method will return the current user configured in the SDK. This is useful when you want to check the current user id and attributes before updating them through [updateUserAttributes](#getting-user-information).
+This method will return the current user configured in the SDK. This is useful when you want to check the current user id and attributes before updating them through [updateUserAttributes](flutter#updating-user-attributes).
 
 <Tabs>
 <TabItem value="dart" label="Dart">

docs/sdk/client-side/ios/index.md

@@ -389,7 +389,7 @@ In regular use, you don't need to call the flush method because the events are s
 
 ### User attributes configuration
 
-This feature will give you robust and granular control over what users can see on your application. You can add rules using these attributes on the console UI's feature flag's targeting tab. [See more](#).
+This feature will give you robust and granular control over what users can see on your application. You can add rules using these attributes on the console UI's feature flag's targeting tab. [See more](/feature-flags/creating-feature-flags/targeting#user-attributes).
 
 <Tabs>
 <TabItem value="swift" label="Swift">
@@ -454,7 +454,7 @@ This updating method will override the current data.
 
 ### Getting user information
 
-This method will return the current user configured in the SDK. This is useful when you want to check the current user id and attributes before updating them through [updateUserAttributes](#getting-user-information).
+This method will return the current user configured in the SDK. This is useful when you want to check the current user id and attributes before updating them through [updateUserAttributes](ios#updating-user-attributes).
 
 <Tabs>
 <TabItem value="swift" label="Swift">
@@ -480,7 +480,7 @@ let evaluationDetails = client.evaluationDetails(featureId: "YOUR_FEATURE_FLAG_I
 
 :::caution
 
-Do not call this method without calling the [Evaluating user method](#evaluating-user). The Evaluating user method must always be called because it generates analytics events that will be sent to the server.
+Do not call this method without calling the [Evaluating user method](ios#evaluating-user). The Evaluating user method must always be called because it generates analytics events that will be sent to the server.
 
 :::
 

docs/sdk/client-side/javascript/index.md

@@ -251,7 +251,7 @@ In regular use, you don't need to call the flush method because the events are s
 
 ### User attributes configuration
 
-This feature will give you robust and granular control over what users can see on your application. You can add rules using these attributes on the console UI's feature flag's targeting tab. [See more](#).
+This feature will give you robust and granular control over what users can see on your application. You can add rules using these attributes on the console UI's feature flag's targeting tab. [See more](/feature-flags/creating-feature-flags/targeting#user-attributes).
 
 <Tabs>
 <TabItem value="js" label="JavaScript">
@@ -306,7 +306,7 @@ This updating method will override the current data.
 
 ### Getting user information
 
-This method will return the current user configured in the SDK. This is useful when you want to check the current user id and attributes before updating them through [updateUserAttributes](#getting-user-information).
+This method will return the current user configured in the SDK. This is useful when you want to check the current user id and attributes before updating them through [updateUserAttributes](javascript#updating-user-attributes).
 
 <Tabs>
 <TabItem value="js" label="JavaScript">

docusaurus.config.js

@@ -33,6 +33,14 @@ const config = {
   i18n: {
     defaultLocale: 'en',
     locales: [ 'en', 'ja' ],
+    localeConfigs: {
+      en: {
+        label: 'English',
+      },
+      ja: {
+        label: 'Japanese',
+      },
+    },
   },
 
   presets: [
@@ -135,6 +143,11 @@ const config = {
             className: 'header-slack-link',
             'aria-label': 'Bucketeer Slack - Join the conversation',
           },
+          {
+            type: 'localeDropdown',
+            position: 'right',
+            className: 'language_dropdown'
+          },
         ],
       },
       prism: {